Connection drop out issue with JMS

[Former Member]

Hi all.

I have a strange error while communicating to JMS Server.

The message when sent for the first time says Connection Drop Out error in JMS Channel monitoring.

When the channel is stopped and started again, the message flows through JMS.

What could be the problem?

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Error in committing JMS session for connector:

DestinationInvocations=[], MessageInvocations=[], DestinationName=null, User=, Password=, isJmsSessionTransacted=true, InitialContextEnvironment={}, LookupConnectionFactory=null, LookupDestination=null, SerializedConnectionFactoryPath=c:/temp/bindingConnectionFactory1.sjo, SerializedDestinationPath=c:/temp/bindingQueue.sjo, Flags=0000000000000000000000000000000000000000000000000000010000000001 } }: javax.jms.JMSException: Could not commit, connection may be dropped

Any ideas are appreciated? Traffic also looks fine.

Thankyou

Kiran

[naveen_chichili]

HI kiran,

create connection on keep alive configure on SAP JMS side you need to have enough TCP/IP port on receiver side. For example if you have default 0 value for this it means every message will create own TCP / IP connection and for that you should have enough TCP/IP port. Earlier XI was only having one connection for one channel but here one channel can have several connections. Depending on JMS configuration you should review your total TCP/IP port and need to increase them as per requirement.

Check this:/people/sunil.ojha5/blog/2010/08/31/review-of-sap-pi-jms-adapter-on-demand-connection-feature

Regards,

Naveen

[former_member854360]

Hi Kiran ,

You can handle the pending messages.

Below is a typical procedure for handling pending messages:

...

1. The default setting for the parameter of the receiver JMS adapter is Throw Exception.

2. You see the following exception in the message or adapter monitor:

The channel is configured to throw a recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards.

3. Make sure that no further messages are sent through this communication channel by deactivating the corresponding sender channel.

4. Check whether the message or messages have arrived in the JMS environment.

a. If the message has arrived in the JMS environment, select Mark Message as Delivered (Message Loss Possible).

b. If the message has not arrived in the JMS environment, select Bypass Pending Warning and Send Message to JMS (Duplicates Possible).

c. Choose Repeat in message monitoring.

If some messages have arrived in the JMS environment and some have not, you must perform the procedure twice and resend the respective messages in each case.

5. Reset the parameter in the communication channel to Throw Exception.

6. Activate the corresponding sender communication channel.

http://help.sap.com/saphelp_nwpi71/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm