When Sending Work Orders through ASAP, Weblogic raised the following Error: Illegal Service Sequence Number

(Doc ID 790939.1)

Last updated on FEBRUARY 09, 2012

Applies to:

Oracle Communications ASAP - Version: 4.7.1 to 5.2.4 - Release: 4.7 to 5.2
Information in this document applies to any platform.
***Checked for relevance on 09-02-2012***

Symptoms

When Work  orders are being sent through  ASAP using the following  queues:

System.52.ApplicationType.ServiceActivation.Application.1-0;5-2;ASAP.Comp.TopicConnectionFactory
System.52.ApplicationType.ServiceActivation.Application.1-0;5-2;ASAP.Comp.JVTEventTopic
System.52.ApplicationType.ServiceActivation.Application.1-0;5-2;ASAP.Comp.JVTHome
weblogic.jndi.WLInitialContextFactory
javax.oss.order.CreateOrderValue


the following error is received.:

<Failed to load log for order 454_4518_stefania. Error: Illegal service sequence number>
<micare.connector.activation5.GetFromA5.getHistory(GetFromA5.java:234)>
javax.oss.IllegalArgumentException: Illegal service sequence number
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:195)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
at
com.mslv.asap.oss.activation.JVTActivation_ccenww_EOImpl_921_WLStub.queryManagedEntities(Unknown
Source)

Caused by: javax.oss.IllegalArgumentException: Illegal service sequence number
at com.mslv.asap.activation.srp.WorkOrderQueryBean.queryServiceHistory(WorkOrderQueryBean.java:1401)
at
com.mslv.asap.activation.srp.WorkOrderQuery_t8aew6_ELOImpl.queryServiceHistory(WorkOrderQuery_t8aew6
_ELOImpl.java:226)
at com.mslv.asap.oss.activation.JVTActivationBean.queryManagedEntities(JVTActivationBean.java:350)
at
com.mslv.asap.oss.activation.JVTActivation_ccenww_EOImpl.queryManagedEntities(JVTActivation_ccenww_E
OImpl.java:970)
at com.mslv.asap.oss.activation.JVTActivation_ccenww_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:548)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:438)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:434)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:57)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:965)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)



What can cause this error and what is the workaround in order to fix this problem?




Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms