cancel
Showing results for 
Search instead for 
Did you mean: 

adapter Engine error- messages are stuck

Former Member
0 Kudos

Hi Friends,

Please find the below adapter error. any body help me. what is the solution.

       


 

Number of Messages In To Be
  Delivered Status


 

 

85


 

 

53


 

 

492


 

 

587


 

Messages are stuck in Adapter Engine.

error

----------

Delivering the message to the application
using connection CIDXAdapter failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
javax.ejb.EJBTransactionRolledbackException: Exception raised from
invocation of public void
com.sap.aii.af.sdk.cidx.impl.choreography.listeners.MSCIDXListenerLocalBean.onMessage(com.sap.engine.interfaces.messaging.api.Message)
throws
com.sap.engine.interfaces.messaging.api.exception.MessagingException
method on bean instance
com.sap.aii.af.sdk.cidx.impl.choreography.listeners.MSCIDXListenerLocalBean@20ea2132
for bean
sap.com/com.sap.aii.adapter.ispeak.app*xml|com.sap.aii.adapter.ispeak.messageListener.ejb.jar*xml|MSCIDXListenerLocalBean;
nested exception is: java.lang.NullPointerException; nested exception
is: javax.ejb.EJBException: Exception raised from invocation of public
void
com.sap.aii.af.sdk.cidx.impl.choreography.listeners.MSCIDXListenerLocalBean.onMessage(com.sap.engine.interfaces.messaging.api.Message)
throws
com.sap.engine.interfaces.messaging.api.exception.MessagingException
method on bean instance
com.sap.aii.af.sdk.cidx.impl.choreography.listeners.MSCIDXListenerLocalBean@20ea2132
for bean
sap.com/com.sap.aii.adapter.ispeak.app*xml|com.sap.aii.adapter.ispeak.messageListener.ejb.jar*xml|MSCIDXListenerLocalBean;
nested exception is: java.lang.NullPointerException.

Regards,

Soma

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member185326
Active Participant
0 Kudos

Hi Soma,

Please check thread usage of CIDXAdapter in "Engine" status. Navigate to RWB - "Component Status" --> Select "Adapter Engine" -> in below section click on "Engine Status" and check how many threads are currently used and how many allocated. Messages turn into "Delivering" or "To be delivered" if the total no.of threads allocated for that adapter are exhausted.

Also, restart your communication channel to see if there is movement in message processing.

Regards,

Shahid Ahmed

praveen_sutra
Active Contributor
0 Kudos

Hi Soma,

Please try to make a dummy change in the channel and try to resend the messages as I can see already 492 messages successfully processed so hopefully channel configuration is appropriate.

Hope that resolves the issue.

thanks and regards,

Praveen T

Former Member
0 Kudos

Hi Praveen,

Thanks for your replay. where & how to change dummy changes.

can you please explain.

Thanks,

Soma

Former Member
0 Kudos

Hi

Error category: XI_J2EE_MESSAGING_SYSTEM

any body explain

Thanks,

Soma

Former Member
0 Kudos

Hi Soma,

open the respective comm channel in ID and click the change button,

add some description in the comm channel then save it and activate(This means a dummy chage to comm channel).

Then try to resend the messages.

Regards,

Santhi

praveen_sutra
Active Contributor
0 Kudos

Hi Soma,

Just open the channel related to the scenario and just add something on description and then save and activate.

hope this helps.

thanks and regards,

Praveen T

Former Member
0 Kudos

Hello Soma,

As the messages are shown in "To be delivered state".

It means there is some problem in CC which is trying to post the message.

From description it looks that you are using CIDX adapter,So kindly check if all the parameters are maintained correctly.Also check if the certificates are exchanged and all key are maintained properly.

And also if target server is up and running.

After checking try to resend the message from here only,hopefully it should work.

Regards

Naveen

Former Member
0 Kudos

Hello Naveen,

As the message are shown in "System Error"

Now where I will check. still now to To Be Delivered messages are increase.

pls explain me.

Thanks,

Soma