Error during processing local bean: localejbs/RfcAFBean

[Former Member]

Hi everybody

we currently trying to perform a RFC Call to our developpment system. The scenario is a simple File to RFC Scenario and it worked until yesterday. Since today the Messages stuck in the RFC receiver Adapter with the following errors in the audit log:

[...]

MP: exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.

Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback.

Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..

[...]

The deffaultTrace.trc show the following entries. Looks like an error in localejbs/RfcAFBean:

RfcFunctionName:ZPSCD_INTERFACE_XXXXX

Date : 07/13/2007

Time : 9:32:39:301

Message :

[EXCEPTION]

com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:118)

at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)

at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)

at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:267)

at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103)

at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:306)

at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1034)

at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:392)

at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:86)

at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)

at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: java.lang.NoSuchMethodError: com.sap.aii.af.rfc.core.config.RfcConfigManager.isPPActive(Lcom/sap/aii/af/service/cpa/Channel;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Z

at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.isPPActive(RfcAFBean.java:385)

at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(RfcAFBean.java:240)

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)

... 14 more

Severity : Error

Category :

Location : com.sap.engine.services.ejb

Application : sap.com/com.sap.aii.adapter.rfc.app

Thread : SAPEngine_Application_Thread[impl:3]_44

Datasource : 312846850:/usr/sap/XDS/DVEBMGS31/j2ee/cluster/server0/log/defaultTrace.trc

Message ID : 0003BA5D1D27006D000002BF0000653B000435201DA336D6

Source Name : com.sap.engine.services.ejb

Argument Objs : com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:118)

at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)

at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)

at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:267)

at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103)

at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:306)

at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1034)

at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:392)

at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:86)

at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)

at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: java.lang.NoSuchMethodError: com.sap.aii.af.rfc.core.config.RfcConfigManager.isPPActive(Lcom/sap/aii/af/service/cpa/Channel;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Z

at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.isPPActive(RfcAFBean.java:385)

at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(RfcAFBean.java:240)

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)

... 14 more

,

Arguments : com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:118)

at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)

at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)

at com.sap.aii.af.listener.AFWListenerBean.onMessage(AFWListenerBean.java:267)

at com.sap.aii.af.listener.AFWListenerLocalObjectImpl0_0.onMessage(AFWListenerLocalObjectImpl0_0.java:103)

at com.sap.aii.af.ra.ms.impl.ServicesImpl.deliver(ServicesImpl.java:306)

at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1034)

at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(ReceiveConsumer.java:392)

at com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.onMessage(ReceiveConsumer.java:86)

at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:848)

at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Caused by: java.lang.NoSuchMethodError: com.sap.aii.af.rfc.core.config.RfcConfigManager.isPPActive(Lcom/sap/aii/af/service/cpa/Channel;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Z

at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.isPPActive(RfcAFBean.java:385)

at com.sap.aii.af.rfc.afcommunication.ejb.RfcAFBean.process(RfcAFBean.java:240)

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)

... 14 more

,

Dsr Component :

Dsr Transaction : 3bdbc330311311dcb33b0003ba5d1d27

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 1

Relatives :

Resource Bundlename :

Session : 0

Source : com.sap.engine.services.ejb

ThreadObject : SAPEngine_Application_Thread[impl:3]_44

Transaction : SAP J2EE Engine JTA Transaction : [12ffffffa5ffffffaa200435f]

User : J2EE_GUEST

Date : 07/13/2007

Time : 9:32:39:304

Message : Error during processing local bean: localejbs/RfcAFBean

Severity : Error

Category :

Location : com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)

Application : sap.com/com.sap.aii.af.app

Thread : SAPEngine_Application_Thread[impl:3]_44

Datasource : 312846850:/usr/sap/XDS/DVEBMGS31/j2ee/cluster/server0/log/defaultTrace.trc

Message ID : 0003BA5D1D27006D000002C00000653B000435201DA33A4D

Source Name : com.sap.aii.af.mp.ejb.ModuleProcessorBean

Argument Objs :

Arguments :

Dsr Component :

Dsr Transaction : 3bdbc330311311dcb33b0003ba5d1d27

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 0

Relatives :

Resource Bundlename :

Session : 0

Source : com.sap.aii.af.mp.ejb.ModuleProcessorBean

ThreadObject : SAPEngine_Application_Thread[impl:3]_44

Transaction : SAP J2EE Engine JTA Transaction : [12ffffffa5ffffffaa200435f]

User : J2EE_GUEST

Date : 07/13/2007

Time : 9:32:39:306

Message : Rolling back transaction for message 38d82020-3113-11dc-c07b-0003ba5d1d27(INBOUND) due to: Exception thrown in method process. The transaction is marked for rollback.

Severity : Error

Category :

Location : com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer.invokeHandler(QueueMessage, MessageController, Services)

Application :

Thread : SAPEngine_Application_Thread[impl:3]_44

Datasource : 312846850:/usr/sap/XDS/DVEBMGS31/j2ee/cluster/server0/log/defaultTrace.trc

Message ID : 0003BA5D1D27006D000002C10000653B000435201DA341C8

Source Name : com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer

Argument Objs : 38d82020-3113-11dc-c07b-0003ba5d1d27(INBOUND),Exception thrown in method process. The transaction is marked for rollback.,

Arguments : 38d82020-3113-11dc-c07b-0003ba5d1d27(INBOUND),Exception thrown in method process. The transaction is marked for rollback.,

Dsr Component :

Dsr Transaction : 3bdbc330311311dcb33b0003ba5d1d27

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 1

Relatives :

Resource Bundlename :

Session : 0

Source : com.sap.aii.af.ra.ms.impl.core.queue.ReceiveConsumer

ThreadObject : SAPEngine_Application_Thread[impl:3]_44

Transaction : SAP J2EE Engine JTA Transaction : [12ffffffa5ffffffaa200435f]

User : J2EE_GUEST

It looks like the JCO Bean has an error. Any Ideas

Regards Oliver

[Former Member]

Hi everybody

The error was caused by a different patch level of the components SAP_XIAF and SAP-XIAFC. These components have to have the some patch level.

Kind regards and thanks for you help.

Oliver

[Former Member]

Hi Oliver,

Where can I check the patch levels mentioned?

Regards,

Leanne

[Former Member]

Hi Leanne

Goto http://<port>:5<systemnumber>;

--> System information --> Software Components -> all components.

Make use of the j2ee_admin user while login on.

Hope this will help you

Regards Oliver

[Former Member]

Hi oliver.

thanks for your answer.

but the url that u had given was not understandable.

so can you give me in clear.

waiting for your response.

cheers.

seeta ram.

[Former Member]

Sorry, my mistake:

http://<host>:5<systemnumber>00/index.html

Example:

http://dev01:51900/index.html

Regards Oliver

[Former Member]

Hi oliver.

thanks for your answer.

but we cont understand what u r saying.

so can you just tell me where we should go for.

is that under SLD orRWB r ?

waiting for your response.

cheers.

seeta ram.

[Former Member]

Hi Oliver.

yes we did searched for SAP_XIAF and SAP-XIAFC in administration but they both had versions 3.0ans 7.0 for each.

so what we need to do now.

waiting for your great idea.

cheers.

seeta ram.

[Former Member]

The patch level of the stacks are also relevant. For example we need to have the following:

sap.com SAP-XIAFC 7.00 SP11 (1000.7.00.11.0.20070201154900 )

sap.com SAP_XIAF 7.00 SP11 (1000.7.00.11.0.20070201154900 )

The "0" after 7.00.11 shows the patch level. The patches are only on the same level if the complete number is equal.

Regards Oliver

[Former Member]

Hi oliver.

thanks for your response.

but they both SAP_XIAF and SAP-XIAFC have versions 7.0 and 3.0 for each .

so we need to look at 7.0 is that what you saying.

please confirm that and also lets take an instance like if we look at sap_xiaf and sap-xiafc and they both had same patches after 0 what we have to do and if they both had different then what can we do.

waiting for your response.

bye.

regards.

seeta ram.

[Former Member]

Hi Seeta,

Can you please post the complete package number including the brackets at the end?

Regards Oliver

[Former Member]

Hi Oliver.

Below are the patche leves you have requested.

sap.com SAP-XIAFC 7.00 SP11 (1000.7.00.11.6.20070729011709)

sap.com SAP_XIAF 7.00 SP11 (1000.7.00.11.1.20070327143000) .

so can you help me by looking at these patches.

waiting for your reply.

cheers.

seeta ram.

[Former Member]

Hi Seeta

It looks like you have different patches of the AF components.

Here are mine:

sap.com SAP-XIAFC 7.00 SP11 (1000.7.00.11.0.20070201154900)

sap.com SAP_XIAF 7.00 SP11 (1000.7.00.11.0.20070201154900)

Yours are 6 and 1. So I would recommend you to apply the latest patches for it and see if it helps.

Regards Oliver

[Former Member]

Hi Oliver,

Thanks for the feedback, you were 100% correct, applying the same patch level sorted out my issue.

Thanks,

Leanne

[Former Member]

Any suggestions?

Regards Oliver

[bhavesh_kantilal]

hmm.. Try to make some dummy changes to the Receiver RFC adapter and activate it and then cjheck if things work fine.

Regards

Bhavesh

[Former Member]

Hi Bhavesh

First thanks that you had a look. Seems to be a harder problem.

I did a lot of dummy changes on the CCh and I also create a new one. Do you know were exactly can I see the cache entry for it and may be a status for the channel? I had a look into SXI_Cache for the Adapter Framework, but did not see any strange stuff. For me it looks like a cache problem.

Regards Oliver

[bhavesh_kantilal]

Oliver,

You have mentioned that it worked first and then things did not work.

Can you check in the RFC adapter's History status in ID and see if there was any change that was made in the RFC adapter setting after which it stopped working.

Revert to the older version and see if it works now?

Also check the Cache Notifications in the ID to see if all are in Green!

Regards

Bhavesh

[henrique_pinto]

Refresh the cache in Java XI Administrator screen (http://<hostname>:<port>/rep/support/admin/).

You can reset caches for repository, directory and runtime, from this screen.

Make sure to log with pisuper user.

Regards,

Henrique.

[Former Member]

Hi Henrique

As Bhavesh suggested I switche to the very first version of the Adpter, the notifications are showing no errors and I did all cache refreshes you suggested. Unfortunately no result and the Adapter issues the same error message as before.

Any further ideas?

Regards Oliver

[Former Member]

Hi Bhavesh

I found some more interesting log entries and it seems to be a user password problem:

Retries exceded, set message 38f10280-3388-11dc-9c91-0003ba5d1d27(INBOUND) to status NON_DELIVERED.

Name or password is incorrect (repeat logon)

JCoClient connection missingHost:xdsci_XDS_31|AdapterType:MessagingSystem|Sender::FileServer|Receiver::PSCD_CDD|Interface:ZPSCD_INTERFACE_DECLAR_TVA:urn:sap-com:document:sap:rfc:functions|MsgID:38f10280-3388-11dc-9c91-0003ba5d1d27

Is this the user/password of the channel or is it service user for the JCO?

Regards Oliver

[henrique_pinto]

Seems like user of the RFC.

try to log with it in R/3 system.

Regards,

Henrique.

[Former Member]

Hi Henrique

Yes you are right. We found in the receiving system an error in sm21 that the user is in lower case an less than 8 digits. This was also described in a note. Therefore we changed the user to a system user an 9 digit upper case password, but unfortunately the error still remains.

Could this be a user/password problem of one of the internal xi users? Do you know which user the JCO uses.

Regards Oliver

[henrique_pinto]

The JCo is just a interface for connections between abap and java worlds. When it say it is a JCo connection, it could be in any connection between java and abap (SLD, RFC adapter, RDC destination etc.).

Did you try to log with the user in R/3?

Did it log with no problems?

Regards,

Henrique.