Problem with JMS Dispatcher in 10.1.3

When we try to set up the JMS Dispatcher in Oracle SES 10.1.3, we always get an error while starting the SES:
Missing class: oracle.edge.impl.dispatcher.JMSEventDispatcher
Any ideas how to make JMS Dispatcher working under 10.1.3? It is quite urgent...
Thank you!!!
DM

Hi DM,
We had some problems with the new JMS framework.
We are working on it.
I'll post any news once we have them.
Regards,
Ron

Similar Messages

  • WebLogic 9 and Antlr problem with JMS Messages

    Hi all,
    I'm facing a problem and your help would be very appreciated.
    We've got an EAR application deployed on a WebLogic 9.x. As we use Hibernate3, when we put it into WebLogic 10, we needed to add "antlr" library to our "weblogic-application.xml" as "prefer-application-packages" (This is because of the well-known error of ClassNotFoundException of the HqlToken class).
    The version of Antlr we have is 2.7.7, and works perfectly in WebLogic 10.
    Now, we want to have an EAR that can be installed in both WebLogic 9.x and 10. But we're getting a fatal exception when we want to create a JMS consumer with a JMS selector in WebLogic 9.x(this is for listening only for the message we need in the queue).
    So, in WebLogic 10 it works with "antlr" in the prefer-application-packages, but in WebLogic 9.x doesn't. And if we don't put it there, it works in WL 9 but not in WL 10.
    The best would be to have the library in the weblogic-application.xml so WebLogic put our library first in the classpath. But in WL 9 we've got this exception:
    javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
         at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:2659)
         at weblogic.jms.client.JMSSession.setupConsumer(JMSSession.java:2432)
         at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2379)
         at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2359)
         at weblogic.jms.client.WLSessionImpl.createConsumer(WLSessionImpl.java:800)
         at crm.appl.cat.CatUtil.enviarMensajeSync(CatUtil.java:244)
         at crm.appl.cat.mar.CatMessageReceiver.receive(CatMessageReceiver.java:571)
         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
         at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
         at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:496)
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
         at crm.appl.cat.mar.CatServlet.service(CatServlet.java:108)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at crm.appl.cat.mar.CatFilter.doFilter(CatFilter.java:33)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3212)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:63)
         at weblogic.jms.dispatcher.Request.getResult(Request.java:51)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:895)
         at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:178)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
         ... 35 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
         at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:255)
         at weblogic.jms.frontend.FESession$2.run(FESession.java:966)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:962)
         at weblogic.jms.frontend.FESession.invoke(FESession.java:2824)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:759)
         ... 37 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:63)
         at weblogic.jms.dispatcher.Request.getResult(Request.java:51)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:895)
         at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:178)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
         ... 44 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.backend.BEQueueImpl.createFilterExpression(BEQueueImpl.java:155)
         at weblogic.jms.backend.BEQueueImpl.createConsumer(BEQueueImpl.java:182)
         at weblogic.jms.backend.BESessionImpl.createBEConsumer(BESessionImpl.java:368)
         at weblogic.jms.backend.BESessionImpl.createConsumer(BESessionImpl.java:378)
         at weblogic.jms.backend.BESessionImpl.invoke(BESessionImpl.java:289)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:759)
         ... 46 more
    Check that "invocationId" is a JMS String Property that we're adding in the messages. Our same source code works perfect in WL 9 without "antlr" as an prefered application package. You know that in WL 9, the antlr library was bundled into the weblogic.jar, so WL has it in his System classpath.
    Someone has an idea how we can solve this? The final solution may be having 2 EARs (one for WL 9 and one for WL 10, with the only change of the weblogic-application.xml), but it's not a nice solution.
    Thank you a lot in advance.
    Ariel Cassan
    Argentina

    Hi all,
    I'm facing a problem and your help would be very appreciated.
    We've got an EAR application deployed on a WebLogic 9.x. As we use Hibernate3, when we put it into WebLogic 10, we needed to add "antlr" library to our "weblogic-application.xml" as "prefer-application-packages" (This is because of the well-known error of ClassNotFoundException of the HqlToken class).
    The version of Antlr we have is 2.7.7, and works perfectly in WebLogic 10.
    Now, we want to have an EAR that can be installed in both WebLogic 9.x and 10. But we're getting a fatal exception when we want to create a JMS consumer with a JMS selector in WebLogic 9.x(this is for listening only for the message we need in the queue).
    So, in WebLogic 10 it works with "antlr" in the prefer-application-packages, but in WebLogic 9.x doesn't. And if we don't put it there, it works in WL 9 but not in WL 10.
    The best would be to have the library in the weblogic-application.xml so WebLogic put our library first in the classpath. But in WL 9 we've got this exception:
    javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
         at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:2659)
         at weblogic.jms.client.JMSSession.setupConsumer(JMSSession.java:2432)
         at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2379)
         at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2359)
         at weblogic.jms.client.WLSessionImpl.createConsumer(WLSessionImpl.java:800)
         at crm.appl.cat.CatUtil.enviarMensajeSync(CatUtil.java:244)
         at crm.appl.cat.mar.CatMessageReceiver.receive(CatMessageReceiver.java:571)
         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
         at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
         at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:133)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
         at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:496)
         at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:245)
         at crm.appl.cat.mar.CatServlet.service(CatServlet.java:108)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at crm.appl.cat.mar.CatFilter.doFilter(CatFilter.java:33)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3212)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:63)
         at weblogic.jms.dispatcher.Request.getResult(Request.java:51)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:895)
         at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:178)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
         ... 35 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
         at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:255)
         at weblogic.jms.frontend.FESession$2.run(FESession.java:966)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:962)
         at weblogic.jms.frontend.FESession.invoke(FESession.java:2824)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:759)
         ... 37 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.dispatcher.Request.handleThrowable(Request.java:63)
         at weblogic.jms.dispatcher.Request.getResult(Request.java:51)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:895)
         at weblogic.messaging.dispatcher.DispatcherImpl.dispatchSync(DispatcherImpl.java:178)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:43)
         ... 44 more
    Caused by: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "invocationId = '124567585'"
         at weblogic.jms.backend.BEQueueImpl.createFilterExpression(BEQueueImpl.java:155)
         at weblogic.jms.backend.BEQueueImpl.createConsumer(BEQueueImpl.java:182)
         at weblogic.jms.backend.BESessionImpl.createBEConsumer(BESessionImpl.java:368)
         at weblogic.jms.backend.BESessionImpl.createConsumer(BESessionImpl.java:378)
         at weblogic.jms.backend.BESessionImpl.invoke(BESessionImpl.java:289)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:759)
         ... 46 more
    Check that "invocationId" is a JMS String Property that we're adding in the messages. Our same source code works perfect in WL 9 without "antlr" as an prefered application package. You know that in WL 9, the antlr library was bundled into the weblogic.jar, so WL has it in his System classpath.
    Someone has an idea how we can solve this? The final solution may be having 2 EARs (one for WL 9 and one for WL 10, with the only change of the weblogic-application.xml), but it's not a nice solution.
    Thank you a lot in advance.
    Ariel Cassan
    Argentina

  • 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
              

  • Problem with JMS in a Cluster

    In summary I am having a problem with my application when it is running on the server that does not contain the JMS.
              Setup:
              2 machines:- Server 1 with the Admin Server and a Managed Server with JMS and a Distributed Queue. Second machine (Server 2) with a managed server. The two managed servers are in a Cluster.
              The connection factory has xa enabled.
              The queue is a distributed queue, with one member queue - on server 1.
              Scenario 1 (works):
              Deploy my application on Server 1 only
              Scenario 2 (works):
              Deploy my application on Server 1 and Server 2
              When the application puts messages on the JMS queue, the messages are processed round robin by the MDB on both Server 1 and Server 2 - as expected.
              Scenario 3 - Does not work
              Deploy my application on Server 2 only
              The application successfully sends a message to the queue - I can see it in queue through the console.
              However the MDB never processes the message. On the queue, I can see 0 consumers.
              Essentially the MDB appears to deploy correctly from the server log but never appears as a consumer on the queue.
              I know the above information is very brief, however I can provide more configuration details and detailed logging if required.

    On a further look through the logs, I have found the following Warning message which may point to the reason why my MDB is not receiving messages from JMS:
              <25-Apr-2005 17:26:01 o'clock IST> <Warning> <EJB> <BEA-010220> <The jms destination 'AsyncMessageQueue' is a distributed destination and it has no physical destination(s) on the current weblogic server. As per distributed destination co-location rules, no pool was creted for the MDB 'AsyncMessage(Application: m3-j2ee_Weblogic21apr_2, EJBComponent: ejb_framework.jar)' on this weblogic server. Hence the MDB 'AsyncMessage(Application: m3-j2ee_Weblogic21apr_2, EJBComponent: ejb_framework.jar)' cannot receive any messages on this server.>
              I have created a Destination on the JMS Server ("Replicate JNDI Name In Cluster" is set), and I have created a Distributed Destination, which has as its member the Destination associated with the JMS Server.
              If the JMS is not on the same server as the deployed application, how do I get the MDB to connect to the physical destination?
              Do I always need a Physical Destination on the the same server as my deployed application? If so, how do I create a Physical Destination on the server that does not have the JMS?
              Any help appreciated.

  • Is there a problem with JMS and Weblogic?

              Hi,
              I am using JMS and Weblogic (Not Message Driven bean).
              My problem is that after some time my listeners disappears.
              I am sending them a message and instead of 6 listeners
              I get only 4 messages.
              So, My question is: Is there any problem working with JMS
              and Weblogic???
              Thanks,
              Tal.
              

    Too little information and a very vague question. Need more info.
              "Tal" <[email protected]> wrote in message
              news:[email protected]..
              >
              > Hi,
              > I am using JMS and Weblogic (Not Message Driven bean).
              > My problem is that after some time my listeners disappears.
              > I am sending them a message and instead of 6 listeners
              > I get only 4 messages.
              > So, My question is: Is there any problem working with JMS
              > and Weblogic???
              > Thanks,
              > Tal.
              

  • Problems with JMS: Error JMS BEA-040368

    Hi,
    I have run into a problem using JMS on BEA. It appears to happen when we run huge amounts of messages through the queue (100 000+).
    Once this error occurs, we cant get rid of it. Restarting server, re-dployment, nothing works. Every subsequent message sent to the JMS produces this error.
    According to the error message, we have exceeded the maximum allowed transactions for the server, but how do we reset the transactions? And what is causing the error to appear in the first place? Somthing I forget to close or flush?
    I have QueueConnection, QueueSession and QueueRecevier objects open for all transactions, and close them when the bean is destroyed. Should I rather create and close them for each transaction?
    Here is the exception:
    <15.jun.2005 kl 14.55 CEST> <Error> <JMS> <BEA-040368> <The following exception has occurred:
    java.lang.RuntimeException: [EJB:010166]Error occurred while starting transaction: javax.transaction.SystemException: Exceeded maximum allowed transactions on server 'myserver'.
    at weblogic.ejb20.internal.MDListener.perhapsBeginTransaction()V(MDListener.java:325)
    at weblogic.ejb20.internal.MDListener.execute(Lweblogic.kernel.ExecuteThread; )V(MDListener.java:339)
    at weblogic.ejb20.internal.MDListener.onMessage(Ljavax.jms.Message; )V(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(Ljavax.jms.MessageListener;Lweblogic.jms.common.MessageImpl; )V(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(Lweblogic.kernel.ExecuteThread; )V(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest; )V(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
    at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread; )V(Unknown Source)
    >

    Developments
    It turned out that my "client" used: this.queueSession = queueConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
    While the "server" used: this.queueSession = queueConnection.createQueueSession(true, Session.AUTO_ACKNOWLEDGE);
    Now changing both sessions to use transactions (createQueueSession(true, Session.AUTO_ACKNOWLEDGE)) and fortifying the use of QueueSession.commit() when sending and receiving messages seemed to solve the problem... for a while.
    After a few new tests the problem appeared again, this time on the "client" side. It is obvious that transaction are somehow not commited correctly even though Session.commit() is called after each and every message is sent and received.
    Btw. To make the app "clean up" hanging transactions faster you can change the value in the console at:
    Mydomain --> Services --> JTA --> Abandon Timeout Seconds
    weblogic.jms.common.TransactionRolledBackException: Exceeded maximum allowed transactions on server 'myserver':error beginning transacted session's internal transaction
    at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
    at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:137)
    at weblogic.jms.dispatcher.DispatcherImpl_814_WLStub.dispatchSyncNoTranFuture(Unknown Source)
    at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:472)
    at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:391)
    at weblogic.jms.client.JMSProducer.send(JMSProducer.java:186)
    at no.nrk.returia.test.TestSMSInAdapter.send(TestSMSInAdapter.java:133)
    at no.nrk.returia.test.TestSMSInAdapter.main(TestSMSInAdapter.java:206)

  • Problem with JMS from session bean

     

    My guess is that in your effort to work around the
    clustering/ejb/jndi problems, you have a producer
    sending on one topic, and a consumer listening on
    another topic. You can check to see if they are the
    same destination using the (uncompiled) code snippets
    below at both the producer and consumer ends.
    import weblogic.jms.common.DestinationImpl;
    Topic topic;
    DestinationImpl destination = (DestinationImpl) topic;
    System.out.println("name = " + destination.getServerName() + "/" +
    destination.getName());
    System.out.println("back-end id = " + destination.getBackEndId());
    System.out.println("destination id = " + destination.getDestinationId());
    _sjz.
    "Malcolm Robbins" <[email protected]> wrote in message
    news:[email protected]...
    >
    This was also posted to the EJB newsgroup and was asked to post the secondissue
    here. Please focus on the second issue, but the first providesbackground.
    >
    >
    I have discovered two significant problems in WLS6.0 with JNDi and JMSthat do
    not occur in the Sun Reference implementation (1.3 Beta).
    Attached is some code you can try to see the problem.
    I have developed a JmsClient that simply looks up a session bean andpasses it
    a string to publish. The session bean is meant to publish to a JMS topic.
    However I have discovered two problems:
    1) In teh ejbCreate() method I look up the topic connection factory andtopic
    in JNDI. These are referenced as "java:comp/env/jms/JmsConnectionFactory"and
    "java:comp/env/jms/JmsTopic" respectively. Here's a fragment of theejb-jar
    descriptor
    <resource-ref>
    <description>The (probably durable) Topic Connection Factory to connectto</description>
    <res-ref-name>jms/JmsConnectionFactory</res-ref-name>
    <res-type>javax.jms.TopicConnectionFactory</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    <resource-env-ref>
    <description>The Jms Source Topic to publish to</description>
    <resource-env-ref-name>jms/JmsTopic</resource-env-ref-name>
    <resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
    </resource-env-ref>
    As you can see they are resource references and resoruce environmentreferences
    respectively. The weblogic-ejb-jar maps these to the real JNDI names"TopicConnectionFactory"
    amd "SchemaTopic" respectively as shown below by the fragment:
    <weblogic-ejb-jar>
    ...etc...
    <reference-descriptor>
    <resource-description>
    <res-ref-name>jms/JmsConnectionFactory</res-ref-name>
    <jndi-name>TopicConnectionFactory</jndi-name>
    </resource-description>
    <resource-env-description>
    <res-env-ref-name>jms/JmsTopic</res-env-ref-name>
    <jndi-name>SchemaTopic</jndi-name>
    </resource-env-description>
    </reference-descriptor>
    Now here's the first problem. When this is deployed the resourceenvironment
    "logical" name (JNDI linkref) for the topic is not defined. The code willhappily
    find the connection factory (presuming you've set these administeredobjects at
    the console).
    2) The second problem now arises. In the code I have ahcked it so thatwhen
    the JNDI lookup fails it tries looking up the real topic in JNDI(SchemaTopic)
    directly.
    This works and teh bean now appears to work, albeit with a directlyhardcoded
    JNDI reference in it. However, if you hook up a standard JMS consumer tothat
    topic it will not consuem the message that is published!!! While thestats clock
    up at the console the message appears to go into a black hole. I canprovdie
    a stadnard consumer if you need one.
    I have the code working fine as-is in teh Sun Reference implementation soI presume
    these are bugs with WL6.0.
    Can anyone advise workarounds and/or fix the problem?

  • Problem with JMS stores in 8.1 sp2

              Hi
              Everytime I use the wizard to create a JMS server/Queue and a store I get this
              kind of error. Am not able to figure out why this happens - why is the store assigned
              to this
              <WSReliableDeliveryPolicy Name="RMDefaultPolicy" Store="clsstore"
              DefaultRetryCount="10" DefaultTimeToLive="60000"/>
              guy? I never configured it! I am attaching the config.xml with this mail. Can
              anyone tell me what I doing wrong?
              error trace---------------------------
              <Mar 10, 2004 12:37:18 PM EST> <Notice> <Management> <BEA-140005> <Loading domai
              n configuration from configuration repository at C:\bea8\user_projects\domains\m
              yclsdomain\.\config.xml.>
              The WebLogic Server did not start up properly.
              Exception raised: 'weblogic.management.configuration.ConfigurationException: Set
              ting attribute Targets with values
              myclsdomain:Name=merlin_1,Type=Server
              for mbean myclsdomain:Name=clsjmsserver,Type=JMSServer - with nested exception:
              [javax.management.InvalidAttributeValueException: One of the stores configured
              f
              or JMS Server "clsjmsserver" is already configured for use by a reliable deliver
              y policy on a different server (A JMS store may only be used once).]'
              Reason: weblogic.management.configuration.ConfigurationException: Setting attrib
              ute Targets with values
              myclsdomain:Name=merlin_1,Type=Server
              for mbean myclsdomain:Name=clsjmsserver,Type=JMSServer - with nested exception:
              [javax.management.InvalidAttributeValueException: One of the stores configured
              f
              or JMS Server "clsjmsserver" is already configured for use by a reliable deliver
              y policy on a different server (A JMS store may only be used once).]
              thanks
              Anamitra
              [config.xml]
              

              Hi Dongbo
              I didnt configure any WS reliable messaging - it got the entry by default and
              am not sure whether this is a bug of the configure app or anything related to
              JMS config. But this happens consistently - I have tried on several different
              installation of WLS 8.1 sp2 and happens everywhere. What do I have to do to not
              have it?
              Also in ur reply I didnt quite get what u meant by this----------------
              This would be fine if the JMSServer and
              >the Web Services
              >policy is on the same server. The problem is that they are on two different
              >WebLogic
              >Servers.
              do let me know if this is a bug as all I am doing is setting up a Queue using
              the config wizard.
              thanks
              Anamitra
              Dongbo Xiao <[email protected]> wrote:
              >Hi Anamitra,
              >
              >I don't know how you instructed the wizard, however, it looks like that
              >the wizard
              >somehow configured the same JMS file to be used for both a JMSServer
              >and a policy for Web
              >Service's Reliable Messaging. This would be fine if the JMSServer and
              >the Web Services
              >policy is on the same server. The problem is that they are on two different
              >WebLogic
              >Servers.
              >Thanks,
              >Dongbo
              >
              >Anamitra wrote:
              >
              >> Hi
              >> Everytime I use the wizard to create a JMS server/Queue and a store
              >I get this
              >> kind of error. Am not able to figure out why this happens - why is
              >the store assigned
              >> to this
              >>
              >> <WSReliableDeliveryPolicy Name="RMDefaultPolicy" Store="clsstore"
              >> DefaultRetryCount="10" DefaultTimeToLive="60000"/>
              >>
              >> guy? I never configured it! I am attaching the config.xml with this
              >mail. Can
              >> anyone tell me what I doing wrong?
              >>
              >> error trace---------------------------
              >>
              >> <Mar 10, 2004 12:37:18 PM EST> <Notice> <Management> <BEA-140005> <Loading
              >domai
              >> n configuration from configuration repository at C:\bea8\user_projects\domains\m
              >> yclsdomain\.\config.xml.>
              >> ***************************************************************************
              >> The WebLogic Server did not start up properly.
              >> Exception raised: 'weblogic.management.configuration.ConfigurationException:
              >Set
              >> ting attribute Targets with values
              >> myclsdomain:Name=merlin_1,Type=Server
              >> for mbean myclsdomain:Name=clsjmsserver,Type=JMSServer - with nested
              >exception:
              >>
              >> [javax.management.InvalidAttributeValueException: One of the stores
              >configured
              >> f
              >> or JMS Server "clsjmsserver" is already configured for use by a reliable
              >deliver
              >> y policy on a different server (A JMS store may only be used once).]'
              >> Reason: weblogic.management.configuration.ConfigurationException: Setting
              >attrib
              >> ute Targets with values
              >> myclsdomain:Name=merlin_1,Type=Server
              >> for mbean myclsdomain:Name=clsjmsserver,Type=JMSServer - with nested
              >exception:
              >>
              >> [javax.management.InvalidAttributeValueException: One of the stores
              >configured
              >> f
              >> or JMS Server "clsjmsserver" is already configured for use by a reliable
              >deliver
              >> y policy on a different server (A JMS store may only be used once).]
              >> ***************************************************************************
              >>
              >> ----------------------------------------------------------------------
              >>
              >> thanks
              >> Anamitra
              >>
              >> ------------------------------------------------------------------------
              >> Name: config.xml
              >> config.xml Type: XML Document (text/xml)
              >> Encoding: base64
              >
              

  • Problem with Web Dispatcher with Double Stack

    We have the latest version of Web Dispatcher - 7.0 with latest patch.
    I'm having a problem where I am trying to use the web dispatcher for load balancing in a double stack (ABAP/JAVA) system.  The person who did the install pointed the installation to the wrong server (which I assume can be easily changed in the profile).  However, on the page where it indicates to activate the SICF services he left the box unchecked (but I checked that necessary ones were activated per note 552286).  I now get these kind of errors when pointing to the http message server on a different system (he installed it assuming it was just for portal (java):
    [Thr  5] *** ERROR => ICP_StructValue: illegal struct reference: wdisp_host_info.capacityIsFi
    xed [icpvalue_mt. 257]
    [Thr  5] *** ERROR => caught ICP exception (eval): ICP_StructValue: illegal struct reference:
    wdisp_host_info.capacityIsFixed [icpvalue_mt.cpp 257] [http_adm_mt. 1488]
    I get the above error when I go to "monitor server" groups in the web dispatcher admin console.
    Here is my profile:
    SAPSYSTEMNAME = PW4
    SAPSYSTEM = 01
    INSTANCE_NAME = W01
    DIR_CT_RUN = $(DIR_EXE_ROOT)/run
    DIR_EXECUTABLE = $(DIR_CT_RUN)
    Accesssability of Message Server
    rdisp/mshost = <fully qualified hostname>
    ms/http_port = 8101
    Configuration for medium scenario
    icm/max_conn = 500
    icm/max_sockets = 1024
    icm/req_queue_len = 500
    icm/min_threads = 10
    icm/max_threads = 50
    mpi/total_size_MB = 80
    SAP Web Dispatcher Ports
    icm/server_port_0 = PROT=HTTP,PORT=81$$
    Any insight is greatly appreciated!!

    Hi,
    I've never seen this error but some thing seems strange to me :
    You use the same port (8101) for the listening port of the web dispatcher and the listening port of the message server of you back office system.
    Is it really the case ?
    Is PW4 the SID of you web disptcher ?
    Is SAPSYSTEM = 01 the sysnr of your web dispatcher ?
    I hope that the info of the web disptcher is not mixed up with the back office info ?
    Regards,
    Olivier

  • Problem with jms tutorial

    I try to run Chapter 7 simple example with j2ee in sun's jms tutorial.
    I followed instruction in tutorial to compile,create queue, create MDBApp.ear, run j2ee server and depoly message-driven ejb. But there is a strange thing
    On the client terminal
    Initiating login ...
    Binding name:'java:comp/env/jms/QueueName"
    Binding name: 'java:comp/env/jms/MyQueueConnectionFactory"
    Java(TM) Message Service 1.0.2 Reference Implementation (build b14)
    Sending message: This is message 1
    then client stop
    But on the j2ee server side, nothing happened.
    still display
    Deploying message driven bean MessageBean, consuming from jms/MyQueue
    Application SampleMDBApp deployed.
    I even tried run
    runclient -client SampleMDBApp.ear -name SimpleClient
    but the result is same.

    I'm having a similar problem when I tried to publish some message to
    my client. EJB seems to send the message but client never receives it.
    Anyone care to shed some light?

  • Weblogic: problem with JMS foreign server and Transaction

    Hello everyone,
    I am working with an enterprise application with Web Application Server Logic 10.3. L 'application uses the following components:
    1) MDB 2.0
    2) FOREIGN JMS SERVER -> WebSpereMQ
    3) EJB SESSION
    L 'MDB calls the session bean which uses in its ejb-jar.xml using a Wrapper for JMS QueueConnectionFactory with res-ref:
    <resource- ref>
    <res-ref-name> jms / iss / QCFIXP </ res-ref-name>
    <res-auth> Container </ res-auth>
    <res-sharing -scope> Shareable </ res-sharing-scope>
    <resource- ref>
    The MDB is CMT
    <transaction-type> Container </ transaction-type>
    while the session bean is BMT
    <transaction-type> Bean </ transaction-type>
    to call the QCFIXP in its transaction.
    The QCFIXP ii an XA resource
    When there is a rollback operation in SessionBean also in 'MDB
    There 'an operation setRollbackOnly:
    getMessageDrivenContext (). setRollbackOnly ();
    After this operation on the MDB I do a JNDI look up the QueueConnectionFactory but sending the message on a queue I get the following exception:
    javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA:
    But if not using the "wrapper jms" in the session bean I did not take any exception and the application don' t have any error.
    My doubt is :
    Why if I use the JMS wrapper I get an error javax.jms.JMSException: [JMSPool: 169809] An error occurred while registering the JMS connection with JTA?
    Thanks in advance.
    Michele
    Edited by: user3501731 on 11-mag-2011 3.16

    Hi Tom,
    Thanks very much for your responses and careful analysis you've done.
    Following the source code of the MDB where error occurs.
    Marked In bold the line where the exception is thrown.
         public void onMessage(Message msg) {
    //          Utility.logger(AP.DEBUG, "Partito MDB 2");
              processa(msg);
              protected void processa(Message msg) {
              Utility.logger(
                   AP.DEBUG,
                   "IXPReceiverMDB7.processa(Message msg) partito");
              try {
                   long start = System.currentTimeMillis();
    /*               Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB.processa(Message msg) effettuo lookup");*/
                   ejb = myEjbLocalHome.create();
                   // individuo l'identificativo del messaggio in ricezione
                   String msgid = msg.getJMSMessageID();
                   Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB7.processa(Message msg) elaboro messaggio:"
                             + msgid);
                   String charset = msg.getStringProperty("JMS_IBM_Character_Set");
                   Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB7.processa Charset:" + charset );
                   // invoco il processo di ricezione
                   boolean commitRequested = ejb.processa(ctlReq, encoding, msg);
                   // il valore di ritorno del processo di ricezione identifica o meno
                   // la necessita' di effettuare il rollback dell'intero processo
                   if (!commitRequested) {
                        getMessageDrivenContext().setRollbackOnly();
                   if (ctlReq) {
                        Utility.logger(
                             AP.INFO,
                             "IXPReceiverMDB7.processa(Message msg) spedisco il messaggio pilota del 'cleaning' con JMSCorrelationID = '"
                                  + msgid
                                  + "'");
                        msg.setJMSCorrelationID(msgid);
                        // Viene creata la QueueConnection
                        QueueConnectionFactory factory =
                             JmsFactoryDispenser.getSingleton().getFactory();
                        QueueConnection connection = factory.createQueueConnection();
                        // Viene ottenuta la 'session'
                        QueueSession session =
                             connection.createQueueSession(
                                  false,
                                  Session.AUTO_ACKNOWLEDGE);
                        // spedisco il messaggio sulla coda abbinata al processo di 'cleaning'
                        // della coda di controllo
                        IXPMessageManager msgManager = new IXPMessageManager(session);
                        msgManager.spedisci(msg, AP.PILOTQUEUE, "J", AP.STD_MESSAGE);                    session.close();
                        connection.close();
                   long end = System.currentTimeMillis();
                   Long durata = new Long (end - start);
                   Utility.logger(
                        AP.INFO,
                        "IXPReceiverMDB7 Tempo totale elaborazione messaggio: " +
                        msgid + " " +
                        durata.toString() + " mill" );
                   Utility.logger(
                        AP.DEBUG,
                        "IXPReceiverMDB7.processa(Message msg) terminato");
              } catch (Throwable e) {
                   getMessageDrivenContext().setRollbackOnly();
                   try {
                        Utility.myExceptionHandler(
                             "E",
                             "1",
                             "4028",
                             "IXPReceiverMDB.onMessage()",
                             e);
                   } catch (Throwable ex) {
                        ex.printStackTrace();
    Thanks in advance.
    Edited by: serpichetto on 16-mag-2011 1.24

  • Problem with JMS Adapter after upgrade to 7.1

    Hi All,
    After an upgrade the JMS adapter connecting IBM Websphere MQ gives the following error:
    Error connecting due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Ensure that all resources required are present in the JMS provider library: aii_af_jmsproviderlib.sda
    Since we are now on PI 7.1, the directory the JMS adapter should be looking for the libraries should be com.sap.aii.adapter.lib.sda. Has anyone else come across this problem after an upgrade? Should we remove the old aii_af_jmsproviderlib.sda?
    Edited by: Luqman on Oct 31, 2008 5:39 PM

    does following JAR files in place in aii_af_jmsproviderlib.sda.
    ●      com.ibm.mq.jar
    ●      com.ibm.mqbind.jar
    ●      com.ibm.mqjms.jar
    ●      connector.jar (use the JAR file from the J2EE client directory)
    can u check n confirm.
    i hopw u have followed the proper deployement process.
    chirag

  • Problem with JMS Correlation i Async/Sync bridge

    This is my scenario:
    I’m receiving a request message from the JMS-adapter and forward this via a async/sync bridge to CRM. I’m using a synchronous proxy in CRM. I want to send the response from this proxy back to MQ via the JMS adapter and put my original JMS Message ID in the JMS Correlation ID in the response message.
    I’ve read about how to configure this in the pdf-document “How to Correlate JMS messages”.
    I did as suggested and that is as follows.
    1.     In my receiver channel I set the Correlation Setting “Set XI Conversation ID To”=JMSMessageID.
    2.     In my integration process (“async/sync-bridge”) I set the Conversation ID in my async send step to the Conversation ID of my request message.
    3.     In my sender channel I set the Correlation Setting “Set JMSCorrelationID To”=XI Conversation ID.
    When I test my scenario I get the following error:
    “New JMS message cannot be correlated with the XI message although it is configured. Unable to set because correlation value is null. Correlation rule: XI_CONVERSATIONID, correlated property: JMSCorrelationID”
    I thought that my Conversation ID should carry the value of my initial JMS Message ID. I know that this is not null.
    Can somebody please help me?
    Kind regards.
    /Helé

    Hi Wallace,
    I tried to set the Conversation ID to the Correlation ID instead but I still get the same error.
    The sending application needs to correlate the request message with the corresponding response and since we are using MQ this is the way to do it.
    regards.
    /Helé

  • Problem with CL_GUI_CFW= DISPATCH

    hi experts,
    when I double click on a node , the dispatch metod :
    CALL METHOD CL_GUI_CFW=>DISPATCH
      IMPORTING
    RETURN_CODE = RETURN_CODE.
    returns ' -1'. ( RETURN_CODE = -1 ).
    means no event triggered, but I have double click on the node.
    Please tell me what could be the reason.
    Thanks.

    Check with below links :
    About CL_GUI_ALV_GRID's event-handling & PAI/PBO
    ALV REPORTS
    Thanks
    Seshu

  • Esb parallel processing problems with jms adapter and bpel

    Hi,
    I have esb project which dequeues from a jms adapter and then the esb router calls a bpel process. This bpel process takes about 10 seconds. The first step this bpel does is to return true ( to the client) to the esb router so the ESB thinks he is ready. This does not work.
    Now if I use in the esb router asyn routing rule to the bpel ws then the esb dequeus all the messages from the queue. All the esb entries are green. But the esb starts one for one the bpel process and then updates the esb entry with a new start time ( very strange) .
    If I use a sync routing rule then it dequeues and call the bpel process one for one.
    How I can parallel proces the jms messages ,because I have 2 quad cores cpu's . Async routing rules looks like the solution.
    How can the esb detects the bpel is still running even with the first action in bpel is to return true. I expected when the esb retrieves true from the bpel ws it ends the current esb entry and goes on with the next. So the total esb time takes a few seconds and not so long as the last the bpel proces finishes.
    And why is he updating the starting time.
    Thanks Edwin
    Message was edited by:
    biemond

    I have esb project which dequeues from a jms adapter
    and then the esb router calls a bpel process. This
    bpel process takes about 10 seconds. The first step
    this bpel does is to return true ( to the client) to
    the esb router so the ESB thinks he is ready. This
    does not work. I am not sure if it can ever work, if you reply and then still proceed with your BPEL process.
    Here is something I would like to suggest:
    Can you try ESB -- (sync) --> BPEL, where BPEL process itself is Async. In that case, esb will consume all the messages very fast and BPEL will get that message and put in Delivery Queue and reply back to ESB. Now BPEL will process them simultaniously based Receiver/Worker threads defined in your env.
    HTH,
    Chintan

Maybe you are looking for

  • SRM PO- BBP_DOC_CHANGE_BADI - Code not effective when the SRM PO is created

    Hi Experts, We are using SRM 5.0 Classic and Extended classic scenario and the SRM local PO(Extended classic scenario) is created for special cateogries only. The SRM Local PO is created automatically after the SC is completely approved. The SC(one l

  • Problem with rendering h:command_link

    <h:command_link action="sayHello">Say Hello</h:command_link> is rendered into Say Hello<a href="# onmousedown="......"></a><input type="hidden" name="helloForm:_id4" /> So, the link title is out of tag. Is this just a bug or I miss something? Using <

  • Creating a slide show from an event reordering slides

    I'm trying to take a event imported into iPhoto from a cd reorder the slides and do a slideshow to export to iDVD. I'm having a time at getting the slide show to start on the slide I set to the key slide and go through each photo in the order they ap

  • Intrastat Output File doesnot contain VAT number and Document Number

    Hi experts, While creating a output file from Intrastat Dispacth, I am not getting Document number and VAT number in output file. I can see the Document number in Display of selection log. Can someone help me? Thanks Arpit

  • Analzing log files with external tools?

    Hi, is there any way to use web analytics software like Webtrends with EP? In other words, does EP produce an access log file with date, URL, user, referrer, etc.? Thanks in advance, Stefan.