Messages waiting in the queue for long time.

[Former Member]

Hi Experts,

We are having some Production issue - messages were waiting in the queue for long time and we found the errors in defaultTrace.12.trc file -

Please help how to solve this issue its production and we need to move forward and solve this issue asap.

XI AF API call failed. Module exception: (No information available). Cause Ex

ception: 'JDBC Adapter configuration not initialized: null'.

Thrown:

com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: (No information available). Cause Exception: 'JDBC Adapter configuration not

initialized: null'.

at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214)

at com.sap.aii.af.service.api.AdapterAccess.call(AdapterAccess.java:99)

at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:87)

at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:47)

at com.sap.aii.mapping.lookup.SystemAccessor.call(SystemAccessor.java:115)

at com.sony.pi.sp.StoredProceduresHandler.runScalarStoredProcedure(StoredProceduresHandler.java:86)

at com.sap.xi.tf._MyPage_Invoice_SAP_to_Loyalty_MM_.invokePROC_CUSTOMER_DEDUP$(_MyPage_Invoice_SAP_to_Loyalty_MM_.java:1272)

at sun.reflect.GeneratedMethodAccessor384.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.aii.mappingtool.tf3.rt.C2CFunctionWrapper.cacheContext(C2CFunctionWrapper.java:91)

at com.sap.aii.mappingtool.tf3.rt.C2CFunctionWrapper.gotoNextContext(C2CFunctionWrapper.java:44)

at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.cacheQueue(Q2QFunctionWrapper.java:86)

at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.gotoNextContext(Q2QFunctionWrapper.java:41)

at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.cacheQueue(Q2QFunctionWrapper.java:74)

at com.sap.aii.mappingtool.tf3.rt.Q2QFunctionWrapper.gotoNextContext(Q2QFunctionWrapper.java:41)

at com.sap.aii.mappingtool.flib3.CollapseContexts.gotoNextValue(CollapseContexts.java:52)

at com.sap.aii.mappingtool.flib3.CollapseContexts.gotoNextContext(CollapseContexts.java:37)

at com.sap.aii.mappingtool.tf3.rt.AResIterator.gotoNextContext(AResIterator.java:37)

at com.sap.aii.mappingtool.tf3.rt.FunctionWrapper.gotoNextContext(FunctionWrapper.java:37)

at com.sap.aii.mappingtool.flib3.IfWithoutElse.gotoNextContext(IfWithoutElse.java:58)

at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:266)

at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:326)

at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:326)

at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:415)

at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142)

at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118)

at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)

at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92)

at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)

at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)

at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)

[Former Member · Accepted solution]

Thanks for your response.

Do we need to perform full or delta CPACache refresh, I tried with delta mode.

Please let me know which mode do i need to go for.

Thanks in advance.

Gary.

[Former Member · Accepted solution]

HI Gary

Its preferred to have full cache refresh. Deactivate adapter first and then do cache refresh. After refreshing activate the adapter

Another thing is Check with your JDBC configurations and table from where its reading the content. This is a production system and issue can be while reading the data JDBC was not able to read it. Check if you have any DB locks as well. It can happen when multiple application access data at same time.

Thanks

Gaurav

[former_member192295]

Hi,

I think this problem is duel to queue, few messages are stucked in Adapter engine. First clear adapter and integration engine queues in Runtime Work bench window. It will sort our esily.

[Former Member]

Need alternative and the parmanent solution for the problem.

[Former Member]

Hi All,

CPACache refresh worked for one day and the same problem repeated again next day, but need to have parmanent fix and should know the root cause of the problem so that the problem can not be repeated again.

Is there any solution other than CPACache refresh and JDBC adapter stop and start to fix the issue.

And also found some entries in SM12 lock entry list during the same schedule time when the messages was triggered and remains for long time. Let me know whether we can delete those locks ?

user PIAFUSER

Lock mode E

and table SXMSPMAST

with lock argument ......

Any suggestions and tips help us alot in fixing this issue.

Thanks in advance

Gary.

[Former Member]

Hi All,

Thanks for your help.

CPACache Refresh worked.

Gary.

[SudhirT]

Hi Gary,

check the configuration of JDBC adapter communication channel once again.

[Former Member]

Hi Gary,

try CPA Cache refresh and starting and stopping JDBC adapter from Visual Admin.

It should resolve your JDBC problem.

Thanks,

Pooja

[Former Member]

Hi gary,

Try deactivate & activating JDBC adapter again.

-- > Try CPA Cache refresh.

--> Try starting and stopping the JDBC adapter from Visual Admin.

regards

Ganga