JMS restarting

Hi,
we are currently running EP7 SP11 in cluster (1 CI and 1 DI).
We are experiencing the following issue related to JMS connection. This
occured after an upgrade from EP6.0 SP19 to EP7.0 SP11.
The error occurs (only on the DI) every second, directly after a
restart of the cluster. And after
around 1h30 the WAS automatically restarts itself.
Hints & remarks:
- If we look at the error, it seems that the DI cannot connect to the
CI ("Participant 256,632,450 is not available", this represents the
Java server on the CI).
- This error seems related to RTMF (Real-Time messaging) which is not
used here.
- The JMS severity for the log is already on DEBUG.
This is quite urgent for us since the system mentioned in a production
system going live tomorrow. Could you please have a look at it?
#1.5#02004C4F4F5001580000000000000DBC000432C547BD6FAC#1181722812087#com.
sap.jms#sap.com/irj#com.sap.jms.server.sessioncontainer.InboundBus
instance=default#Guest#0####e7e10c70198611dc8d7002004c4f4f50#Thread
[Thread-336,5,SAPEngine_Application_Thread[impl:3]_Group]
##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerCommunication
Exception: Communication exception.
            at
com.sap.jms.server.JMSServerContainer.sendToRemoteRouterSynchronously
(JMSServerContainer.java:873)
            at
com.sap.jms.server.JMSServerContainer.sendToRemoteDestinationContainerSy
nchronously(JMSServerContainer.java:966)
            at
com.sap.jms.server.routingcontainer.RoutingContainer.sendToDestinationCo
ntainerSynchronously(RoutingContainer.java:227)
            at
com.sap.jms.server.service.impl.RoutingServiceImpl.sendToDestinationCont
ainerSynchronously(RoutingServiceImpl.java:57)
            at
com.sap.jms.server.sessioncontainer.handler.ProducerHandler.onCreateRequ
est(ProducerHandler.java:130)
            at
com.sap.jms.server.sessioncontainer.handler.ProducerHandler.process
(ProducerHandler.java:67)
            at com.sap.jms.server.sessioncontainer.InboundBus.process
(InboundBus.java:144)
            at com.sap.jms.server.sessioncontainer.InboundBus.enqueue
(InboundBus.java:117)
            at
com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatch
er(SessionContainer.java:63)
            at
com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatch
er(RoutingContainer.java:447)
            at com.sap.jms.server.JMSServerContainer.dispatchRequest
(JMSServerContainer.java:572)
            at com.sap.jms.server.SynchronousNetworkAdapter.sendAndWait
(SynchronousNetworkAdapter.java:135)
            at com.sap.jms.client.connection.Connection.sendPacket
(Connection.java:657)
            at com.sap.jms.client.session.Session.createProducer
(Session.java:2395)
            at com.sap.jms.client.session.QueueSession.createSender
(QueueSession.java:81)
            at
com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run
(RTMFMessaging.java:1189)
            at java.lang.Thread.run(Thread.java:534)
Caused by:
com.sap.engine.frame.cluster.message.DestinationNotAvailableException:
Participant 256,632,450 is not available.
            at
com.sap.engine.core.cluster.impl6.lazy.ConnectionsRepository.create
(ConnectionsRepository.java:237)
            at
com.sap.engine.core.cluster.impl6.lazy.ConnectionsRepository.get
(ConnectionsRepository.java:73)
            at
com.sap.engine.core.cluster.impl6.lazy.LazyConnectorImpl.getConnection
(LazyConnectorImpl.java:417)
            at
com.sap.engine.core.cluster.impl6.lazy.LazyConnectorImpl.sendRequest
(LazyConnectorImpl.java:167)
            at
com.sap.engine.core.cluster.impl6.ClusterManagerImpl.ms_sendRequest
(ClusterManagerImpl.java:2423)
            at
com.sap.engine.core.service630.context.cluster.message.MessageContextImp
l.sendAndWaitForAnswer(MessageContextImpl.java:93)
            at
com.sap.jms.server.JMSServerContainer.sendToRemoteRouterSynchronously
(JMSServerContainer.java:851)
            ... 16 more
#1.5#02004C4F4F5001580000000200000DBC000432C547BD76B2#1181722812087#com.
sap.jms.client.session.Session#sap.com/irj#com.sap.jms.client.session.Se
ssion#Guest#0####e7e10c70198611dc8d7002004c4f4f50#Thread[Thread-
336,5,SAPEngine_Application_Thread[impl:3]_Group]
##0#0#Error##Java###checkReceivedPacket
[EXCEPTION]
#1#javax.jms.JMSException: Communication exception.
            at
com.sap.jms.protocol.notification.ServerExceptionResponse.getException
(ServerExceptionResponse.java:271)
            at com.sap.jms.client.session.Session.checkReceivedPacket
(Session.java:2613)
            at com.sap.jms.client.session.Session.createProducer
(Session.java:2396)
            at com.sap.jms.client.session.QueueSession.createSender
(QueueSession.java:81)
            at
com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run
(RTMFMessaging.java:1189)
            at java.lang.Thread.run(Thread.java:534)
#1.5#02004C4F4F5001580000000300000DBC000432C547BD780C#1181722812087#com.
sap.ip.collaboration.rtc#sap.com/irj#com.sap.ip.collaboration.rtc.class
com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.run
()#Guest#0####e7e10c70198611dc8d7002004c4f4f50#Thread[Thread-
336,5,SAPEngine_Application_Thread[impl:3]_Group]
##0#0#Error##Java###!!!!!!!!!!!!!!!!! restarting
JMS !!!!!!!!!!!!!!!!!!!!!!!!!:
[EXCEPTION]
#1#javax.jms.JMSException: Communication exception.
            at
com.sap.jms.protocol.notification.ServerExceptionResponse.getException
(ServerExceptionResponse.java:271)
            at com.sap.jms.client.session.Session.checkReceivedPacket
(Session.java:2613)
            at com.sap.jms.client.session.Session.createProducer
(Session.java:2396)
            at com.sap.jms.client.session.QueueSession.createSender
(QueueSession.java:81)
            at
com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run
(RTMFMessaging.java:1189)
            at java.lang.Thread.run(Thread.java:534)
Thanks in advance,
Eric

Similar Messages

JMS Restart : using closed dispatcher

Hi,
          I have my app which publishes messages to JMS Topic on WLS 8.1 SP4. Everything works fine. But to test the failover, I gracefully shutdown OR kill the WLS server; restart and then RECONNECT to JMS. After reconnecting when I try to Publish messages I get the following exception. Once Jms is up, do I need to get connections and reconnect specificaly? I tried both ways but get same exception. I use the weblogic.jar. Please help...
          INFO: CONNECTED TO JMS...
          INFO: Publish...
          weblogic.jms.common.JMSException: using closed dispatcher
          at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:366)
          at weblogic.jms.client.JMSProducer.send(JMSProducer.java:186)
          at weblogic.jms.client.JMSProducer.publish(JMSProducer.java:243)
          at com.bofa.hyr.server.PublishingHelper.publish(PublishingHelper.java:110)
          at com.bofa.hyr.server.PositionChangeNotifier$ChangeListener.run(PositionChangeNotifier.java:160)
          at java.lang.Thread.run(Thread.java:534)
          Sep 28, 2005 2:59:25 PM com.bofa.hyr.server.PublishingHelper connectJMS
          INFO: CONNECTED TO JMS...

Hello Tom,
          To answer your questions:
          1. SOAP over HTTP
          2. The Web Service has a web method that instantiates a listener that is also a Durable Subscriber - that is all I know for now, I can get more details on this.
          3. Client and Server are same version, WLS 10.0.0
          4. There are no exceptions generated whatsoever. I was monitoring the console. After the 2nd call (which there is no response it appears), the ClientID inside WL console is "Failed". And there are no pending messages in the topic. According to the console, all messages had been processed.
          I'm wondering why the ClientID shows up as failed (no error messages though). If we restart the JMS domain, the ClientIDs show up as Active.
          Thanks
          Chris

Error in JMS-Receiver-Adapter when restarting MQ-Channel

Dear all,
we've configured a scenario with a JMS-Receiver (MQ-Series). When the MQ-Channel or the MQ-Queue-Manageris restarted, the connection to MQ get lost and is not re-established even when we restart the communication channel. When we restart the whole J2EE-Server things work fine, but we can't do this in productive environment.
Could this be a configuration issue? How can we solve this?
Kind regards, Stefan

solved by ourselves

JMS Queue loosing messages on Server restart

Hi ,
We are having a problem with a queue that is loosing pending messages if the server is restarted.
We have following setup of Oracle Weblogic version 9.2 mp1.
The JMS Server is backed up by a DB based persistent store.we are having a message driven bean that process the message in the queue asynchronously.
the message that is delivered to the queue has Delivery Mode 'persistent'
and the mdb using transactionType=MessageDriven.MessageDrivenTransactionType.CONTAINER.
What is strange that we are loosing pending message in the queue , when server is restarted .even checking in the xxx'_WLSSTORE table in db i can see the message
was persisted.
If anyone of you have seen this situation kindly let me know.
thanks in advance.
Rgds
roy

You can follow this article to troubleshoot pending message issues.
http://weblogic-wonders.com/weblogic/2011/01/10/working-with-jms-and-the-standard-issues-in-jms/
-Faisal

JMS Queue is not accepting requests after restarting the weblogic server

Hi,
JMS queue is able to receive message after redeploying the application or restarting the weblogic server. It is intermittent , not happening every time.
Please suggest how to resolve this issue. do we missed any configuration settings we are missing at clinet side or server side.
we are using Weblogic 92 MP2 version.
thanks.
[email protected]

I assume you meant "is unable to receive messages".
Are you getting any exceptions in the code, or errors in the log, or is nothing happening when you know there's a message on the queue to be read?
Are you perhaps reading from a distributed destination?

JMS destinations disappear from JNDI after appserv restart

I am using the PE 8.1 2005Q1 application server. I create a jms resource as jms/myQueue and I can see it using the JNDI browser.
However, after restarting the application server, my destinations still show up under JMS Destinations & Admin Object Resources, but disappear from the JNDI browser and are unavailable to clients!
Do I need to perform an addtional step in order to get the appserver to persist these jndi registrations? There appears to be a disconnect between JMS and JNDI. Any help is greatly appreciated.

JMS has a ForeignJMSProvider config option to do this I believe. 9.0 will also support this more generally.

JMS Messages lost after server restart

Hi All,
We have an environment where Oracle SOA 11g is configured to use Weblogic JMS (Database persistence). The JDBC stores have been created to hold the persistent JMS messages. However we have observed that after server restart the messages are getting lost from the queue (non consumed messages as well).
Is there any configuration which we are missing?
Regards
Subhankar

Hello Subhankar,
Which Weblogic version are you using? What are the configuration parameters of the JMS queue you defined? During server shutdown/restart, do you see any errors in the server log?
I would suggest you to raise a case with support as it may require an inspection of your environment and settings to find out the root cause.
Regards,
Anuj

How to Clear JMS pending message withour restarting weblogic

Hi All,
We are using JMS concept in our weblogic for asynchronous backend. We have pollJMS OSB service that process the JMS message to async target.
For some reason messages are pilling up in queue and poll service is not able to send the messages to target.
Is there any way if we can clear the queue without restarting the weblogic.
Any help on this would really be appreciable.
Thanks,

Try through WLST
connect('weblogic', 'weblogic', 't3://HOST:PORT')
serverRuntime()
cd('/JMSRuntime/ManagedSrv1.jms/JMSServers/MyAppJMSServer/Destinations/MyAppJMSModule!QueueNameToClear')
cmo.deleteMessages('')
To use Java/WLST to delete JMS Message refer below link
How to purge/delete message from weblogic JMS queue - Stack Overflow
Cheers,
Sahil

Is there a requirement to restart the JMS/Weblogc Server everytime when the DB goes down?

Question:
When the Database is shutdown gracefully everything was fine.
But when the Database is brought down with shutdown abort the MDB consumer will never consume messages from the topic again. And we need to restart the WebLogic Server in order to get the messages consumed again.
So is there a requirement to restart the JMS/Weblogc Server everytime when the DB goes down? If not, what type of failures will require the JMS/WLS restart?

On a DB failure, a WL JDBC store service will make a brief attempt to reconnect before shutting itself down along with any services that depend on the store.
It isn't necessary to restart the entire WebLogic Server JVM to bring the affected service(s) back if you can use the Automatic Service Migration feature. ASM can automatically restart a failed service on a different WL Server in the same cluster, and/or can try a restart-in-place for the service if the service's original host WL Server JVM is still running. The Automatic Service Migration (pdf) white-paper has a thorough discussion of this area.
In addition to ASM, there's also a "whole server migration" option that can automatically restart or migrate an entire WL server.
Tom

MDB unable to listen anymore after remote JMS server crashed and restarted

I'm running Weblogic Server 8.1 SP4 on a Win 2k server. My remote JMS server is running Sonic 6.0 on a Win 2k server. Both are connected in the same network. My problem is that whenever I restart the JMS server after it crashes (improper shutdown), my MDBs will not be able to listen to any messages sent to the topic/queue. WL console does not display any error about MDB unable to connect to the topic/queue as if the JMS server was never down. I have to re-deploy my apps in order to get the MDBs working. Is there a workaround or patch for this 'bug'?

The options I can think of are:
          (1) Configure a WebLogic messaging bridge that runs in "synchronous" mode for forwarding messages from Sonic to a WL destination. Then change MDB to refer to the WL destination. Alternatively, if you haven't already, try using a transactional MDB - which may or may not use synchronous receives to get messages from Sonic (depends on the version of Sonic I believe). The reason I think this might help in either method is that I think the use of synchronous receives may yield a better chance of detecting failures in Sonic.
          (2) See if Sonic itself requires a patch.
          (3) Try out WL 9.2 instead of WL 8.1 (it may be that the Sonic work-around I vaguely recall isn't in 8.1???)
          (4) Contact customer support.

JMS server needs restart after client app restarts

Hello everyone,
          I have a client who has two domains - one for JMS and one for client (web service in this case). They are noticing that when the client domain is restarted (for various reasons), the client can make one, and only one, call to the JMS server. After that first call, the topic appears inactive from within the Weblogic console, however the console reports that there are no messages pending. So what happened? there is no error on the side of the client. Client just states that the message was submitted, but no response.
          They are using durable subsribers.
          So the question is, why, after a restart of the client domain, does a query to the JMS topic only work once?
          The workaround we have right now is to restart the domain hosting JMS and everything is fine.
          Thank you
          Chris

Hello Tom,
          To answer your questions:
          1. SOAP over HTTP
          2. The Web Service has a web method that instantiates a listener that is also a Durable Subscriber - that is all I know for now, I can get more details on this.
          3. Client and Server are same version, WLS 10.0.0
          4. There are no exceptions generated whatsoever. I was monitoring the console. After the 2nd call (which there is no response it appears), the ClientID inside WL console is "Failed". And there are no pending messages in the topic. According to the console, all messages had been processed.
          I'm wondering why the ClientID shows up as failed (no error messages though). If we restart the JMS domain, the ClientIDs show up as Active.
          Thanks
          Chris

JMS Client Eeconnect After JMS Server Restart

Hi,
How can I force the JMS clients to reconnect again, when JMS Server restarts.
thx in advance for any help!

Pass an ExceptionListener into the Connection and when onException is called, start a reconnect cycle (wait x seconds and try to reconnect x times).

Reconfigure or Restart JMS service !!!

Hi
<b>Reconfigure or Restart JMS service !!!</b>
This we have observed while going through AF logs.
Should we restart JMS Connector and JMS Provider services in Visual Admin?
We tried though but to no avail.
Any suggestions...
Regards,
Varun

yes the drivertool.bat does it for me
<?xml version="1.0" encoding="UTF-8"?>
<provider-descriptor>
    <display-name>com.sap.aii.af.jmsproviderlib</display-name>
    <component-name>com.sap.aii.af.jmsproviderlib</component-name>
    <major-version>7</major-version>
    <minor-version>0</minor-version>
    <micro-version>6</micro-version>
    <provider-name>sap.com</provider-name>
      <references>
         <reference type="library" strength="weak">jms</reference>
      <reference type="library" strengh="weak">com.sap.aii.messaging.runtime</reference></references>
    <jars>
    <jar-name>sonic_Client.jar</jar-name><jar-name>sonic_XA.jar</jar-name></jars>
<
At this moment i am receiving the following error on the communication channel
Exception caught by adapter framework: The JMS channel with channel ID f055fe2451203cd5b39d81c7647b281e is errornous. Details:Error during channel initialization; exception trace: javax.jms.JMSException: java.io.IOException: Invalid broker response.: HTTP://progressow1.XXXXXXXXXXX.com:2600 at progress.message.jimpl.JMSExceptionUtil.createJMSException(Unknown Source) at progress.message.jimpl.Connection.(Unknown Source) at progress.message.jimpl.QueueConnection.(Unknown Source) ... [104] progress.message.client.ENetworkFailure: java.io.IOException: Invalid broker response.: HTTP://progressow1.XXXXXXXXXXX.com:260

JMS connection from SAP PI to Oracle AQ via JNDI...

Hi,
I am currently working on a project that requires connections between PI and Oracle AQ. It was advised that we shoule use PI JMS adpater with JNDI driver. However, it seems that not many people have tried this approach.
Has anyone had similar solutions in production ? How repliable it is ?
Your help is very much appreciated
Tim

Hi Tim,
We implemented a similar scenario and now itu2019s still working.
You have to configure a JNDI connection, but not directly with the Oracle AQ. The Oracle AQ are just queues, and you need a JMS provider in order to establish the connection with these queues. The solution we implemented was:
1. Configure one OC4J server as JMS provider for the Oracle AQ queues.
2. Configure JMS communication channels in SAP PI to establish the connection with the OC4J server.
Maybe you can use a different and newer JMS provider, as BEA Weblogic or SAP WAS (I donu2019t know if itu2019s possible).
We implement the scenario in SAP PI 7.0, and with this version we had a problem: When the communication between JMS adapter and the queues was broken (the DDBB fell down for example), the channel failed, itu2019s normal. But when the DDBB was already running the channel stayed in an error state, and we had to restart the channel manually. The response of SAP to this issue was that the channel behavior was correct because the connection failed.
But this problem occurred rarely, maybe once a month. The solution is very reliable, we exchange a lot of message with this solution, and support messages of any size with an excellent performance.
Best Regards,
Roberto

Problem with JMS migration when using Ctrl+C to stop the managed server in cluster

          Hi,
          I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
          uses JMS as a asynchrous communication. We have MDB which listens to these JMS
          messages.
          If something is being processed on Managed Server 1 and while the request is in
          process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
          After this, i go to admin console and migrate teh JTA and JMS. After this, i am
          expecting other running Managed Server should restart the incomplete transaction.
          But this is not happening. The Managed Serve2 doesn't process the requst.
          But when i restart teh MAnaged SErver 1 again, it takes up the same request and
          processes it.
          Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
          Please note that the same thing is working fine when i stop the server using Admin
          console(Normal shutdown OR forced shutdown).
          Any comments in this regards are apprecciated.
          Thanks,
          Naresh


          Hi,
          I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
          uses JMS as a asynchrous communication. We have MDB which listens to these JMS
          messages.
          If something is being processed on Managed Server 1 and while the request is in
          process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
          After this, i go to admin console and migrate teh JTA and JMS. After this, i am
          expecting other running Managed Server should restart the incomplete transaction.
          But this is not happening. The Managed Serve2 doesn't process the requst.
          But when i restart teh MAnaged SErver 1 again, it takes up the same request and
          processes it.
          Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
          Please note that the same thing is working fine when i stop the server using Admin
          console(Normal shutdown OR forced shutdown).
          Any comments in this regards are apprecciated.
          Thanks,
          Naresh

JMS restarting

Similar Messages

Maybe you are looking for