Concurrent nodes reading from JMS topic (cluster environment)

Hi.
Need some help on this:
Concurrent nodes reading from JMS topic (cluster environment)
Thanks
Denis

After some thinking, I noted the following:
1 - It's correct that only one node subscribes to a topic at a time. Otherwise, the same message would be processed by the nodes many times.
2 - In order to solve the load balancing problem, I think that the Topic should be changed by a Queue. This way, each BPEL process from the node would poll for a message, and as soon as the message arrives, only one BPEL node gets the message and take if off the Queue.
The legacy JMS provider I mentioned in the post above is actually the Retek Integration Bus (RIB). I'm integrating Retek apps with E-Business Suite.
I'll try to configure the RIB to provide both a Topic (for the existing application consumers) and a Queue (an exclusive channel for BPEL)
Do you guys have already tried to do an integration like this??
Thanks
Denis

Similar Messages

Re:How can we delete the concurrent node entry from the FND_NODE table

HI ,
11.5.10.2 on Oracle Solaris on SPARC (64-bit) .
How can we delete the concurrent node entry from the FND_NODES table without running Autoconfig.
Currently we are having 3 nodes RAC and we are deciding to remove one node from the RAC and all 3 nodes are registered as concurrent node with application but concurrent manager is running only on one node.
Lot of the custom configuration we did it at application web tire level. If we run the Autoconfig at that time we need to redo those changes again that we are trying to avoid.
Regards .

we are trying to avoid to run FND_CLONE.setup_clean because it will delete all the nodes entries from the FND_NODES.If those entries are invalid then they should be deleted.
Running AutoConfig after purging the table will populate it with the correct entries.
In order to populate the nodes entries again we need to run autoconfig and it will change the server id in fnd_nodes and then we need to redo the ADI client configuration on users PC and redo all the changes that we made in jserv and webserver.For ADI Clients, you should use the correct server ids which will be populated in the table for you once you run AutoConfig.
For jserv configuration, you can refer to (Customizing an AutoConfig Environment [ID 270519.1]) to make the preserve all your custom setup/configuration after running AutoConfig.
If there any custom script to delete only one node from the fnd_node so that we don't need to run autoconfig after that, then I really appreciate.No.
Thanks,
Hussein

Error in Applet reading a JMS topic

I have an applet trying to read a JMS topic. It connects fine, but as
          soon as a message is written into the topic (that the applet is
          subscribed to), I get the following error on the server:
          <Apr 26, 2002 2:46:39 PM PDT> <Error> <RJVM> <Unsolicited error
          response for: '-1'>
          The applet shows the following stacktrace:
          <Apr 26, 2002 2:40:26 PM PDT> <Warning> <Dispatcher> <Error thrown by
          rmi server: 'weblogic.rmi.internal.BasicServerRef@101 - jvmid:
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          oid: '257', implementation:
          'weblogic.jms.dispatcher.DispatcherImpl@2c3327''
          weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          generate the Skeleton on the server for:
          weblogic.jms.dispatcher.DispatcherImpl_WLSkel ]
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
               at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
               at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          <Apr 26, 2002 2:40:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
          rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          oid: '2', implementation:
          'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
          weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          generate the Skeleton on the server for:
          weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
               at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
               at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.Kernel.execute(Kernel.java:235)
               at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
               at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
               at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
               at weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.java:42)
               at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
               at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
               at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
               at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
               at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          <Apr 26, 2002 2:41:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
          rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          oid: '2', implementation:
          'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
          weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          generate the Skeleton on the server for:
          weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
               at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
               at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
               at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.Kernel.execute(Kernel.java:235)
               at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
               at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
               at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
               at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
               at weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.java:42)
               at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
               at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
               at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
               at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
               at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          Thanks in advance for suggestions/help.
          Raj


Is it with 7.0 GA or beta?
          Do you know whether the classpath servlet is open or not?
          Can you run this url from a browser and update this issue please.
          http://host:port/bea_wls_internal/classes/weblogic/jms/dispatcher/Dispatcher
          Impl_WLSkel.class
          You should get a downloaded file to be saved. Otherwise your server need to
          open the classpathservlet.
          use -Dweblogic.servlet.ClasspathServlet.disableStrictCheck=true to open the
          classpath servlet.
          Attach the applet code, so that it will help us to nail down the issue.
          Cheers,
          ..maruthi
          "theist" <[email protected]> wrote in message
          news:[email protected]...
          > I have an applet trying to read a JMS topic. It connects fine, but as
          > soon as a message is written into the topic (that the applet is
          > subscribed to), I get the following error on the server:
          >
          > <Apr 26, 2002 2:46:39 PM PDT> <Error> <RJVM> <Unsolicited error
          > response for: '-1'>
          >
          >
          > The applet shows the following stacktrace:
          >
          > <Apr 26, 2002 2:40:26 PM PDT> <Warning> <Dispatcher> <Error thrown by
          > rmi server: 'weblogic.rmi.internal.BasicServerRef@101 - jvmid:
          >
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
          7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          > oid: '257', implementation:
          > 'weblogic.jms.dispatcher.DispatcherImpl@2c3327''
          > weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          > generate the Skeleton on the server for:
          > weblogic.jms.dispatcher.DispatcherImpl_WLSkel ]
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
          scriptor.java:296)
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
          tor.java:309)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          > at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
          > at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > >
          > <Apr 26, 2002 2:40:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
          > rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
          >
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
          7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          > oid: '2', implementation:
          > 'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
          > weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          > generate the Skeleton on the server for:
          > weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
          scriptor.java:296)
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
          tor.java:309)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          > at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
          > at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.Kernel.execute(Kernel.java:235)
          > at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
          > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
          > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
          > at
          weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
          a:42)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at
          weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
          > at
          weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
          > at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > >
          > <Apr 26, 2002 2:41:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
          > rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
          >
          '-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
          7001,7002,7002,7001,7002,-1]:mydomain:myserver',
          > oid: '2', implementation:
          > 'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
          > weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
          > generate the Skeleton on the server for:
          > weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
          scriptor.java:296)
          > at
          weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
          tor.java:309)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          > at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
          > at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
          2)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.Kernel.execute(Kernel.java:235)
          > at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
          > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
          > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
          > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
          > at
          weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
          a:42)
          > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
          > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
          > at
          weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
          > at
          weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
          > at
          weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > >
          >
          >
          > Thanks in advance for suggestions/help.
          > Raj

Error encountered while collecting the data from JMS topic bus

Iam encountering a problem while collecting the data from JMS topic bus and pushing the data to BAM.On the DesignStudio window, after I click on “update” button in the plan window to run the plan I get the following exception messages:
IMessageSourceReceiver->messageReceive:
javax.naming.CommunicationException: Connection refused: connect
     at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:292)
     at
com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at
iteration.enterpriselink.sources.JMSConsumer.start(JMSConsumer.java:85)
     at
iteration.enterpriselink.sources.JMSMessageSourceReceiverImpl.jmsConsumerS
tart(JMSMessageSourceReceiverImpl.java:1001)
     at
iteration.enterpriselink.sources.JMSMessageSourceReceiverImpl.messageRecei
ve(JMSMessageSourceReceiverImpl.java:326)
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
     at java.net.Socket.connect(Socket.java:426)
     at java.net.Socket.connect(Socket.java:376)
     at java.net.Socket.<init>(Socket.java:291)
     at java.net.Socket.<init>(Socket.java:147)
     at
com.evermind.server.rmi.RMIClientConnection.createSocket(RMIClientConnecti
on.java:682)
     at
oracle.oc4j.rmi.ClientSocketRmiTransport.createNetworkConnection(ClientSoc
ketRmiTransport.java:58)
     at
oracle.oc4j.rmi.ClientRmiTransport.connectToServer(ClientRmiTransport.java
:78)
     at
oracle.oc4j.rmi.ClientSocketRmiTransport.connectToServer(ClientSocketRmiTr
ansport.java:68)
     at
com.evermind.server.rmi.RMIClientConnection.connect(RMIClientConnection.ja
va:646)
     at
com.evermind.server.rmi.RMIClientConnection.sendLookupRequest(RMIClientCon
nection.java:190)
     at
com.evermind.server.rmi.RMIClientConnection.lookup(RMIClientConnection.jav
a:174)
     at com.evermind.server.rmi.RMIClient.lookup(RMIClient.java:283)
     ... 5 more
[Oracle BAM Enterprise Link error code: 0x75 -- 0x1, 0x75 -- 0x3A]
Error during Message Receive operation.
[Oracle BAM Enterprise Link error code: 0x75 -- 0x1, 0x75 -- 0x3B]

The error msg says that your BAM server cannot connect to your JMS provider. Make sure your configs are all ok, in EL DesignStudio, BAMArchitect EMSdefinition, etc. You can refer to the samples and technotes and tutorials to understand these details. If you are following the steps in the technote etc. pl verify your oc4j container is running, and oc4j version and 'jndi path' is ok. Give the doc name, pg number and step where you are getting this error.

Jms adapter not polling messages from jms topic

Hi
We have a jms adapter configured in BPEL process which need to poll messages from JMS topic.Unfortunately its not polling message from JMS Topic if we add Message Selector and Durable Subscriber properties in jca file.Please find jca file content below
<adapter-config name="SyncCustomerPartyListCDHJMSConsumer" adapter="JMS Adapter" wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/CDH/V1/ProviderABCS/SyncCustomerPartyListCDHProvABCSImpl.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/jms/aia/syncCustomerParty_cf" UIJmsProvider="WLSJMS" UIConnectionName="Dev"/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
    <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
      
      <property name="PayloadType" value="TextMessage"/>
      
      <property name="UseMessageListener" value="true"/>
      <property name="DestinationName" value="jms/aia/Topic.jms.COMMON.CustomerParty.PUBLISH"/>
    </activation-spec>
</endpoint-activation>
</adapter-config>
If we remove Durable subscriber and message selector properties,its able to poll messages.
Any pointer will help
thanks in advance
Baji

After changing below property in jca file.JMS adapter is able to poll messages from JMS Topic.
<property name="UseMessageListener" value="false"/>
But if i un comment below line and deploy my code again, it stop pulling the messages from topic.
<property name="DurableSubscriber" value="XYZ"/>
If i bounce the server after above change and deployment ,it will start polling the message.I am not sure why i need to restart my server after adding above property.
Thanks
Baji

Unable to read from JMS queue on Solaris

Hi all,
I am experiencing a strange issue with JMS and Oracle 10gR2 (single server) on Solaris.
The design is simple, 1 server multiple clients communication via 2 queues (P2P domain). Each client has a session ID and can read messages from the queue that have been tagged with the proper session ID.
I guess is simpler to show the code involved:
@Override
public void becomeSender(String queueName) throws JMSException {
setDestination(((AQjmsSession) getSession()).getQueue(null, queueName));
((AQjmsDestination) getDestination()).start(getSession(), true, true);
setProducer(((AQjmsSession) getSession()).createSender((Queue) getDestination()));
getProducer().setDeliveryMode(DeliveryMode.NON_PERSISTENT);
@Override
public void becomeReceiver(String queueName, String sessionID) throws JMSException, JMSConnectorException {
setDestination(((AQjmsSession) getSession()).getQueue(null, queueName));
((AQjmsDestination) getDestination()).start(getSession(), true, true);
setConsumer(((AQjmsSession) getSession()).createReceiver((Queue) getDestination(), getReceiverSessionPredicate(sessionID)));
getConnection().start();
public static final String jmsReceiverSessionProperty = "msgReceiverSession";
public static final String jmsSenderSessionProperty = "msgSenderSession";
public static String getReceiverSessionPredicate(String sessionID) throws JMSConnectorException {
if (sessionID == null) {
throw new JMSConnectorException("Session ID must be provided!");
return jmsReceiverSessionProperty + " = '" + sessionID + "' OR " + jmsReceiverSessionProperty + " = '" + TransferMessage.TARGET_ANY_RECEIVER + "'";
and the code that sends the message
public void sendMessage(TransferMessage aMessage) throws JMSException, IOException {
BytesMessage aMsg = createBytesMessage();
aMsg.setStringProperty(jmsReceiverSessionProperty, aMessage.getReceiverSessionID());
aMsg.setStringProperty(jmsSenderSessionProperty, getSessionID());
sendMessage(aMsg);
Everything works great in Windows XP/7/2008 server 64 virtual machine or not but it fails in Solaris.
The messages are written to the queue as I can see them in the queue table but they never get read from the queue...Oh I missed a bit of information, I use onMessage to handle new message on queues.
The Solaris server is at client environment and I have no remote access to it.
I can run my my simple connectivity tests on a Solaris instance if anyone care to provide me with credentials and 2 queues or even better I can send the jars to run on local environment.
Any help would be much appreciated. Thanks,
Eddie

Moderator Action:
This post has been moved from the Java Message Service (JMS),
to the suggested Database Advanced Queuing forum, for closer topic alignment.

Get back the Message from JMS Topic

Hi,
I want to Process message came to the JMS topic (say for past 10 days) in PRODUCTION environment . Is there any way i can get those messages from Persistent Store(File/JDBC).Any sugesstions????
thanks in advance...

As far as I think you can not directly read messages from persistence store without putting the message integrity at stake.
Also, do you know if the messages are actually in the persistence store? Messages will persisted by the Topic only if there is any durable subscriber is there which has not read those messages. If there are no durable subscribers or if all durable subscribers have read their copy of the message from Topic the messages will be removed from persistence storage.

Getting DOM Parsing Exception in translator while Dequeuing the message from JMS topic

Hi All,
Hope you all doing good.
I have an issue.
I am running on 11.1.1.5 SOA suite version on Linux.
In my aplication I have 4 projects which are connected by with topic/queue.
But in one of the communication, the JMS topic throws me the below error in the log, but dequeue happend perfectly fine and the application runs smoothly.
[ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@530c530c] [userId: <anonymous>
] [ecid: 5552564bd7cf9140:-117a2347:142149c715a:-8000-00000000069dd133,0] [APP: soa-infra] JMSAdapter <project1>
JmsConsumer_sendInboundMessage:[des
tination = <TOPIC NAME> subscriber = <Consumer project name>
Error (DOM Parsing Exception in translator.[[
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
) while preparing to send XMLRecord JmsXMLRecord
[ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@530c530c] [userId: <anonymous>
] [ecid: 5552564bd7cf9140:-117a2347:142149c715a:-8000-00000000069dd133,0] [APP: soa-infra] JMSAdapter <project name>
java.lang.Exception: DOM Parsing Exception in translator.
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
        at oracle.tip.adapter.jms.inbound.JmsConsumer.translateFromNative(JmsConsumer.java:603)
        at oracle.tip.adapter.jms.inbound.JmsConsumer.sendInboundMessage(JmsConsumer.java:403)
        at oracle.tip.adapter.jms.inbound.JmsConsumer.send(JmsConsumer.java:1161)
        at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:1048)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
But when I try putting the archived data on this topic, it throws me the same error but even dequeuing doesnt happen.
I have extracted the payload and validated against the xsd, it looks fine and even the validator doesnt throw me any error.
But I guess I am missing something, which I am immediately not getting.
Please let me know, if I am soemthing here which is causing this erro.
Thanks,
Chandru

I searched about this error, but no luck.
First time when the message dequeues, the consumer can consume the message but throws the error in the log.
But when I put the message back into queue from archive directory, the consumer doesnt consume message and throws me the same error.
Does anyone faced this sort of issue.
I checked my xsd throughly, and validated it externally. but didnt fine any error.
if anyone knows, suggest me how to resolve this issue.
thanks & regards
Chandru

Receive asynchronous message from JMS topic over web service

Hi,
I have a JMS topic and I want to expose it as a web service so that clients can
make durable subcription to the topic and receive messages asynchronously. What
is the best way of doing this ? Is there a portable (to other containers) way
of do this ? If not, is there a web logic specific way of doing this ?
Thanks,
Siva

So you expect clients to be receiving SOAP messages over HTTP? In this
case, the clients are really servers that are capable of servicing SOAP
requests, correct? And how about the senders: are they also using
SOAP/HTTP to send messages that are delivered to the receivers?
It should be possible to write this yourself using JMS not as the
transport, but as a mechanism for distributing the message to a set of
clients. You'll need to implement a Web Service for publishing to a
topic, an operation for registering an end point to recieve messages,
and an MDB (or other form of JMS subscriber) executing on the server to
relay the message to the end point.
Siva wrote:
Hi,
I have a JMS topic and I want to expose it as a web service so that clients can
make durable subcription to the topic and receive messages asynchronously. What
is the best way of doing this ? Is there a portable (to other containers) way
of do this ? If not, is there a web logic specific way of doing this ?
Thanks,
Siva

Consume from JMS Topic SOA 10g

I have a BPEL that is supposed to run when something is enqueued to a topic. It is supposed to dequeue it and then transform it etc.
I enqueue something onto that topic, but it is never dequeued by my service. I'm sure there are many reasons why this could be happening, but I don't know what they are.
Could someone please list the reasons this could be happening, and also ways to fix it.

Hi,
It is usually a configuration problem, have a look at the .jca file, see what is in there for "location" and for "destination", compare those with the jndi name of your topic. There is configuration to be done in your jms adapter on weblogic admin console, check the configuration of your jms adapter under deployments.
Cheers,
Vlad

1 "simple" JMS topic and 2 cluster elements with OSB

Hi,
I have 1 simple jms topic (not distributed, not on migratable target) and cluster with 2 members - OSB as main application. My OSB proxy service reads from this topic and saves data to file.
The problem is that reading from topic appears twice - once by each cluster member. How to configure topic or proxy service for only one reading?

FYI - At this year's Oracle OpenWorld, which is being held in conjunction with this year's JavaOne, Oracle will be announcing a set of enhancements that are designed to cover this exact use case.
Tom Barnes
Session ID: S317469
Title: New Service-Oriented Architecture Patterns with Enterprise Grid Messaging
Abstract: Messaging systems are essential in enabling the flexibility and loosely coupled nature of a service-oriented architecture (SOA). Oracle WebLogic Java Message Service (JMS) includes new pub-sub capabilities that make architectures more adaptable, allowing message producers to be ignorant of who is the consumer of a message or how many consumers there are. It also enables easy scale out and dynamic adaptability through clustering and message-driven bean (MDB) enhancements, all while still guaranteeing strict message ordering. This session will outline new JMS capabilities and show how they enable new designs with Oracle WebLogic Server and Oracle Service Bus.
Speaker(s): Dongbo Xiao, Oracle, Principal Member of Technical Staff
Biography not available.
David Cabelus, Oracle USA, Senior Principal Product Manager
Dave Cabelus is a Senior Principal Product Manager in the WebLogic Server group at Oracle. Dave's responsibilities include product strategy and direction for various pieces of WebLogic Server, including Java Messaging, Operations and Management, Diagnostics, and various other initiatives, and previously included database connectivity, transactions, and Web tier integration. In the industry since 1996 and involved in Java since 1999, Dave worked at various software companies including Logic Works, Platinum Software, Kana, and a few startups before coming to Oracle (BEA) in 2001.
Event: JavaOne and Oracle Develop
Stream(s): ORACLE DEVELOP, DEVELOP
Track(s): Application Grid and Oracle WebLogic
Tags: Add
Session Type: Conference Session
Session Category: Features
Duration: 60 min.
Schedule: Thursday, September 23, 11:00AM | Hotel Nikko, Nikko Ballroom II Available
Edited by: TomB on Aug 12, 2010 1:21 PM

Messages posted to JMS Topic from OSB disappear even when not subscribed

Hi,
We are using an OSB service to publish xml messages to a weblogic JMS Topic. Message is persistent. There are no consumers for the Topic. There is no expiration limit set.
We are able to see the message from OSB reach the Topic. It stays in the Topic for a few seconds and then disappears.
The State of the message shows up as "send transaction" on the Topic in the weblogic console. And it shows up as Message Pending instead of Message Current.
Is there a way to ensure that the message stays in the Topic till it is consumed by a subscriber?
Thanks,
Senthil

Hi Senthil,
The topic persists messages only for subscribers, if there is no subscribers, then it is not necessary to persist the message.
This is the same case for you as well, as there are no subscribers the message gets deleted.
So first you need to have atleast one subscriber first (A dummy proxy that is reading from the topic) and then post to the topic (through your OSB service or hermes jms tool, etc .. ) . Then if you try to go and check the topic you will be able to see the message.
Hope this information helps.
Thanks,
Patrick
Edited by: Patrick Taylor on May 13, 2011 2:40 PM

How to read JMS Topic in Oracle E-Bussiness suite R12

We have to read JMS Topic in Oracle E-Bussiness suite R12. JMS Topic is created by SOA and name of JNDI and connection factory details are provided by SOA. Please let me know the steps to read the JMS Topic.

Hi,
SOA and Weblogic documentation can be found at (Search for JMS):
Documentation for Oracle SOA Suite
http://www.oracle.com/technology/products/soa/soasuite/collateral/documentation.html
Oracle WebLogic Server Documentation
http://download.oracle.com/docs/cd/E14571_01/wls.htm
Thanks,
Hussein

Newbie question about JMS topic and OSB

So here is what I want to achieve:
I want to "front" a JMS topic on WLS using OSB 10g. I want the users (producers and subscribers) to be access the topic via proxy services. The way I picture this is that a producer will invoke a proxy to publish a message. The subscriber will (asynchronously) invoke another proxy to pickup the message.
Is this possible and how do I go about doing this?
thanks
Edited by: user10341230 on Apr 28, 2010 8:49 AM

Hi there,
user10341230 wrote:
I want to "front" a JMS topic on WLS using OSB 10g. I want the users (producers and subscribers) to be access the topic via proxy services. > it's not really clear what you want to achieve here.
you say
user10341230 wrote:
The way I picture this is that a producer will invoke a proxy to publish a message.you need a proxy with whatever inbound protocol you like (http, file, mail...), which through a jms business service push the message to the Topic.
you say
user10341230 wrote:
The subscriber will (asynchronously) invoke another proxy to pickup the messagethe subscriber can be either asyncrhnous, in which case you need a proxy service with inbound protocol jms. or as you probably need a synchronous one
in which case you need another proxy with whatever inbound protocol you like whch once called in its pipeline calls some pojo class to read from this topic synchrnously (you need a durable subsciber).
Regards,
Tony
ps: have a look http://download-llnw.oracle.com/docs/cd/E11035_01/wls100/jms/design_best_practices.html#wp1058694

MDB,MDB container or JMS adapter stops processing messages from JMS queue

Hi guys,
we have created a component using Enterprise Java Beans, let's say a product catalog, deployed it on a Glassfish v2 instance, and connected it to a legacy system using JMS and Sun MQ v4.1 as messaging system. The catalog component thus starts one MDB that listens on a JMS queue, let's say a queue named catalog_business_events_in, and waits for incoming messages, i.e. in our case update events. The problem is, that in general this approach works well, but sometimes the MDBs/JMS adapter stops for some reason fetching and processing messages from the JMS queue. We don't know why - no exceptions, etc.. Seems to be a Glassfish EJB container, JMS adapter or Sun MQ configuration issue. It seems to be that our component is not the problem.
The messages are compressed/uncompressed by Sun MQ automatically. We actually have 2 Sun MQ instances in clustered mode running to have some kind of failover - no HA cluster, yet. Sun MQ instances are accessed from Glassfish instances running in different Glassfish clusters - so we have a dedicated Sun MQ cluster not a Sun MQ instance per Glassfish instance. Each Glassfish instance is configured such that it knows both Sun MQ instances to allow automatic failover.
Has someone an idea, why the MDBs/ MDB container/ JMS adapter - stops processing messages? We are kind of puzzled as it happens more often now and apparently when traffic is (very) low not high!
Thanks for your help.
Cheers,
Martin
Edited by: east1979 on Jan 13, 2009 8:06 AM

Hi Manoj,
I have a very similar if not identical issue,
Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
15/11/12 09:10:08 JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
TION TO CONTINUE.
15/11/12 09:10:15 Communication Error. See real time job log for details.
Dump available:
https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
Version of DS:14.0.3.273
Any comments?
Thansk and kind Regards,
Kenneth

Concurrent nodes reading from JMS topic (cluster environment)

Similar Messages

Maybe you are looking for