How to subscribe to a JMS topic with a selector

I'd like to receive messages on a JMS topic satifying a selector.
I'm trying examples\webservices\message. The ConsumerClient
receives messages on "examples.soap.msgService.MsgSend". But if
I want to sepcify a selector, how do I do it? Thanks!
Kevin

I think Mediator by default participates in a same transaction and if the webservice calls fails, it would rollback the message to queue.
I would suggest you to setup fault policy in mediator for the webservice invoke and catch the fault and do the retries or human intervention depends on your need.
Also, my personal suggestion is to use BPEL in place of ESB in this scenario as you have more persistence and fault handling capabilities in BPEL over ESB.

Similar Messages

How to put message in JMS topic

Hello,
AnyOne can tell me how to put messages in JMS topic ?? Any sample / example available on it ?? I am using Oracle SOA 10g.
Thanks

Try this link:-
http://jamessmith73.wordpress.com/oracle-soa-bpm-11g/bpm-and-jms-adapters/
It have a good example on JMS Consumer and producer.

How to creat an Weblogic JMS configuration with authentication

I have to configure a weblogic jms topic in such a way when a remote sender send a message it has to connect using some authentication. Like when creating the initial context or the connectionFactory. But nowhere I got the steps for configuring it that way. Can you please let me know what is the out-of-the-box steps for achieving it. I am using all out-of the-box tools(no foreign jndi provider).

Simple answer, you are in the WRONG forum, this is the Application Express (APEX) support forum..
Thank you,
Tony Miller
Webster, TX

How do I use a JMS MessageSelector with application-specific properties

According to a couple of JMS references (Sun, Oreilly) and the oracle documentation (under the heading "Using Oracle Java Messaging Service (JMS) to Access AQ", page 102 of 1082 , Application Developers Guide - Advanced Queuing, Release 2 (8.1.6))
Standard JMS Features
"Message selection based on message header fields/properties"
Is there a special syntax for using application-specific (user defined) JMS message properties as message selectors in Oracle 8.1.7?
I've tried to create a message selector based on a custom property that I set, i.e. "username != 'William'". (example from O'Reilly JMS book, pg. 44)
I always get a JMS-159: Invalid selector Selector Parse error unless the property is a JMS-Defined property. i.e., " JMSMessageID = 'ID:9789D65E215B3613E034080020B1456E' " works fine.
From the docs and the oter examples, I figure application-specific (user-defined) properties are legal.
Thans for any help in advance.

Well I found an article in another forum that states in oracle 8i, message selectors are only supported on JMSCorrelationID and JMSMessageID
(9i will have/has the full JMS spec support for message selectors , or so the response to the message says)
Thanks anyway
(Aricle Is In Products > Database > Oracle Advanced Queueing
Title is JMS AQ: selector in createReceiver does not work)

Distributed JMS Topic consumer reconnection... How???

Hi!
          I'm trying to develop a JMS consumer that is connected to a distributed topic located in a 2-machine cluster. The client knows the address of the two servers, so the idea is to catch the JMSException (JMS destination shutdown) with a ExceptionListener (or something like that) if one server fails, and then try to connect to the other one...
          I've been browsing Weblogic docs but I didn't find any example for this.
          How do I implement my consumer? Is there any other approach to my problem?
          Thanks a lot!
          Jorge Granado


          Hi Tom:
          Finally I've been able to reconnect my consumer. I took a "clean" one (mine was
          getting too complicated :-) and it worked. I took the TopicReceive sample from
          bea samples and added a "reconnect" method following your recommendations about
          reusing existing ConnectionFactory. I'm beginning to think I was forgetting to
          start the connection, but anyway now it works great. Thanks a lot!
          BTW, could you explain to me how can I change (if possible) in "real-time" the
          MessageSelector properies for an existing consumer? Suppose that I have a consumer
          connected to a topic with a selector like "priority >=2" and I'd like to change
          it to "priority >=3" without restarting the application... Is it possible??
          Thanks again
          Jorge
          Tom Barnes <[email protected].bea.com>
          wrote:
          >Seems like your following the recipe correctly. :-)
          >
          >Could you try this on a platform other than AIX?
          >
          >Are you using the same version of WL jars for client and server?
          >
          >Are you using the new 8.1 "thin client" jars for the client? If
          >so try using weblogic.jar instead (don't put both kinds
          >of jars in your classpath).
          >
          >
          >"Jorge Granado" jorge.granadoATatosorigin.com wrote:
          >
          >> Hi again!
          >>
          >> Well, maybe there's something I don't get, but what I'm trying to do
          >is:
          >>
          >> -Create a topic consumer and connect it to the distributed topic (standard
          >process...)
          >> -Shutdown the server where the consumer is connected...
          >> -Capture the exception
          >> -Close the topic connection
          >> -Create a new one reusing existing topic connection factory (as you
          >told me there's
          >> no need to make a lookup again...)
          >> -Create a topic session over the new topic connection
          >> -Create a subscriber
          >> -Read messages... :-)
          >>
          >> But in 5th step what I get is a new Exception... "Error creating connection
          >to
          >> the server"
          >>
          >> I'm sure I've misunderstood something... :-(
          >>
          >> Thanks again for your patience :-)
          >>
          >> Jorge
          >>
          >> Tom Barnes <[email protected].bea.com>
          >> wrote:
          >>
          >>>No, I don't know what is happening. I wonder if you are
          >>>somehow multi-threading the session? Try closing
          >>>the old connection before reconnecting. And note that
          >>>there is no need to lookup up the CF again, as the old CF
          >>>should work fine (it is a clusterable RMI reference,
          >>>so it can survive failures).
          >>>
          >>>"Jorge Granado" jorge.granadoATatosorigin.com wrote:
          >>>
          >>>>Now I've created a consumer, and when catching the session exception
          >>>
          >>>and try to
          >>>
          >>>>reconnect to another WL instance, when I make the JNDI lookup to my
          >>>
          >>>connection
          >>>
          >>>>factory, instead of getting a weblogic.jms.client.JMSConnectionFactory
          >>>
          >>>what I
          >>>
          >>>>get is an weblogic.jms.frontend.FEConnectionFactory_812_WLStub_812_WLStub.
          >>>
          >>>>This causes a ClassCastException and I can't connect to it. Any idea
          >>>
          >>>what is happening?
          >>>
          >>>>Thanx again :-)
          >>>>
          >>>> Jorge
          >>>>
          >>>>BTW, I'm using WL 8.1 SP2 (AIX platform)
          >>>>
          >>>>Tom Barnes <[email protected].bea.com>
          >>>>wrote:
          >>>>
          >>>>
          >>>>>Hi Jorge,
          >>>>>
          >>>>>Registering exception-listeners and retrying on failure
          >>>>>seems like the right approach. I'm not sure what you
          >>>>>are looking for in an example.
          >>>>>
          >>>>>For more information on JMS clustering, I recommend reading
          >>>>>the JMS Performance Guide white-paper on dev2dev:
          >>>>>
          >>>>>http://dev2dev.bea.com/technologies/jms/index.jsp
          >>>>>
          >>>>>Tom, BEA
          >>>>>
          >>>>>P.S. One thing to realize is that WebLogic distinguishes between
          >>>>>"session" exceptions and "ccnnection" exceptions. Shutting
          >>>>>down JMS without shutting down a client connection's WL
          >>>>>server only generates session exceptions, as the connection
          >>>>>is still valid. To monitor session exceptions, register
          >>>>>a session exception listener (see the weblogic.jms.extensions
          >>>>>package).
          >>>>>
          >>>>>Jorge Granado wrote:
          >>>>>
          >>>>>
          >>>>>
          >>>>>>Hi!
          >>>>>>
          >>>>>>I'm trying to develop a JMS consumer that is connected to a distributed
          >>>>>
          >>>>>topic located in a 2-machine cluster.
          >>>>>
          >>>>>
          >>>>>>The client knows the address of the two servers, so the idea is
          >to
          >>>>>
          >>>>>catch the JMSException (JMS destination shutdown)
          >>>>>
          >>>>>with a ExceptionListener (or something like that) if one server fails,
          >>>>>
          >>>>>and then try to connect to the other one...
          >>>>>
          >>>>>
          >>>>>>I've been browsing Weblogic docs but I didn't find any example for
          >>>>>
          >>>>>this.
          >>>>>
          >>>>>
          >>>>>>How do I implement my consumer? Is there any other approach to my
          >>>
          >>>problem?
          >>>
          >>>>>>Thanks a lot!
          >>>>>>
          >>>>>> Jorge Granado
          >>>>>
          >>
          >

Get MDB to subscribe to JMS topic deployed on different server instance

Can you do this?
I have 2 servers.
I want to Have the MDB deployed to one server subscribe to the JMS topic deployed on the second server.
This seems like it should be possible. Is it?

Hi, I have the similar situation.
On the OC4J1 I have topic (jms/MojTopic) and factory (jms/MojTopicFactory), and my client (on the same OC4J) send some messages on that topic.
I used this solution because the client can always send messages, regardless of network failure...
On the OC4J2 I have MDB that is setup like this (orion-ejb-jar.xml):
<?xml version = '1.0' encoding = 'UTF-8'?>
<orion-ejb-jar>
<enterprise-beans>
<message-driven-deployment name="LogBean"
destination-location="jms/MojTopic"
connection-factory-location="jms/MojTopicFactory">
</message-driven-deployment>
</enterprise-beans>
</orion-ejb-jar>
I configured jms/MojTopicFactory to the host of OC4J1, but still don't understand why I have to set up jms/MojTopic?
Ok, this way I can send messages to OC4J1 and OC4J2 pick up that messages, BUT, when I disconnect OC4J2 from the network I get the following error (application.log from OC4J2):
06/12/27 11:48:35.171 10.1.3.1.0 Started
06/12/27 11:51:34.687 Error in MessageDrivenBean 'LogBean': javax.jms.JMSException: deqMessage
javax.jms.JMSException: deqMessage
at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1072)
at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1152)
at com.evermind.server.jms.TCPJMSRemoteServer.shutdownForce(TCPJMSRemoteServer.java:295)
at com.evermind.server.jms.TCPJMSRemoteServer.execute(TCPJMSRemoteServer.java:202)
at com.evermind.server.jms.JMSRemoteServer.deqMessage(JMSRemoteServer.java:575)
at com.evermind.server.jms.EvermindSession.receive(EvermindSession.java:1254)
at com.evermind.server.jms.EvermindSession.getOneMessage(EvermindSession.java:1151)
at com.evermind.server.jms.EvermindMessageConsumer.getOneMessage(EvermindMessageConsumer.java:444)
at com.evermind.server.jms.EvermindMessageConsumer.receive(EvermindMessageConsumer.java:192)
at com.evermind.server.ejb.MessageDrivenConsumer.receiveMessage(MessageDrivenConsumer.java:424)
at com.evermind.server.ejb.MessageDrivenConsumer.processMessages(MessageDrivenConsumer.java:213)
at com.evermind.server.ejb.MessageDrivenConsumer.run(MessageDrivenConsumer.java:169)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at java.io.DataInputStream.readInt(DataInputStream.java:353)
at com.evermind.server.jms.JMSRemoteServer.processFlag(JMSRemoteServer.java:612)
at com.evermind.server.jms.JMSRemoteServer.getMessage(JMSRemoteServer.java:632)
at com.evermind.server.jms.JMSRemoteServer.access$300(JMSRemoteServer.java:72)
at com.evermind.server.jms.JMSRemoteServer$19.getReply(JMSRemoteServer.java:592)
at com.evermind.server.jms.JMSRemoteServer.readResponse(JMSRemoteServer.java:648)
at com.evermind.server.jms.TCPJMSRemoteServer.execute(TCPJMSRemoteServer.java:189)
... 10 more
When I connect OC4J2 again, the MDB doesn't pick up those messages, so my mission of 100% sure sending of messages fails :(
Any help?
Thanx,
Vanja

Messages in JMS Topic Error destination

Hi,
I have a JMS Topic with an error destination queue configured. Now, In our scenario , there are two subscribers of topic for the same message. Suppose for a message published to topic, subscriber1 is able to processes message successfully but subscriber2 throws errors when processing the same message.
1. Once the redelivery limit is reached and subscriber2 continues to throw exception, Will the message get en queued to Error Destination (in spite of the fact that subscriber 1 has processed the same message successfully) ?
2. For a consumer (e.g MDB) listening to Error destination and consuming error messages, Is it possible to determine which topic subscriber was unable to process the message ?
Please let me know
Regards,
Arif

Here it depends on the state of the message, if the message is visible then the message would be available for consumption, else it is not. In case the subscriber 2 failed to consume the message and the message is still visible then a retry would be made, else the message would not be retried.
In case the message is visible then the message would be move to the error queue based on the configured redelivery attempts.
Additionally, an MDB can find the destination using the getJMSDestination() call. But as per my understanding we will only be able to get the name of the last destination which in this case would be error queue:
http://docs.oracle.com/javaee/1.4/api/javax/jms/Message.html#getJMSDestination%28%29

OSB(11.1.1.4) errors when ServiceProxy configured to AQ JMS Topic(not Q)

Hi,
I have a situation as follows:
AQ JMS Topic --> OSB Proxy Service --> Invoke some business service.
I have configured WLS with AQ Foreign JMS server. I know my WLS/AQ configuration is correct as I can publish to AQ topic from OSB(no bpel) business service. But when I try to get an inbound xml(not soap) messages from AQ and let OSB Proxy Service subscribe to the JMS topic(not queue). I get the following message in WLS console
WLS Console Error message:
<Warning> <EJB> <BEA-010081> <The message-driven bean RequestEJB-3836792044197546800-63c4ae90.12e4efaf8e2.-7fbf was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
Also the messages does not get picked up from AQ topic and when I look at AQ there is no subscriber created to the JMS topic. I did set the subscriber name, XA etc. in the OSB JMS Transport advanced section.
============================================================================
In the console log I get:
<Feb 22, 2011 4:25:07 PM CST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda is unable to connect to the JMS destination: jms.etBannerFromRMS. The Error was:
oracle.jms.AQjmsException: ORA-24047: invalid agent name RequestEJB-6379926953434238165, agent name should be of the form NAME
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 6234
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_AQJMS", line 129
ORA-06512: at line 1
Nested exception: java.sql.SQLException: ORA-24047: invalid agent name RequestEJB-6379926953434238165, agent name should be of the form NAME
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 6234
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_AQJMS", line 129
ORA-06512: at line 1
>
<Feb 22, 2011 4:25:17 PM CST> <Warning> <EJB> <BEA-010081> <The message-driven bean RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
<Feb 22, 2011 4:25:17 PM CST> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda is unable to connect to the JMS destination or bind to JCA resource adapter: jms.etBannerFromRMS. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
<Feb 22, 2011 4:25:17 PM CST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda is unable to connect to the JMS destination: jms.etBannerFromRMS. The Error was:
oracle.jms.AQjmsException: ORA-24047: invalid agent name RequestEJB-6379926953434238165, agent name should be of the form NAME
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 6234
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_AQJMS", line 129
ORA-06512: at line 1
Nested exception: java.sql.SQLException: ORA-24047: invalid agent name RequestEJB-6379926953434238165, agent name should be of the form NAME
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 6234
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_AQJMS", line 129
ORA-06512: at line 1
>
<Feb 22, 2011 4:25:27 PM CST> <Warning> <EJB> <BEA-010081> <The message-driven bean RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
<Feb 22, 2011 4:25:37 PM CST> <Warning> <EJB> <BEA-010081> <The message-driven bean RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
<Feb 22, 2011 4:25:47 PM CST> <Warning> <EJB> <BEA-010081> <The message-driven bean RequestEJB-6379926953434238165--37f2a5df.12e4f78ff7c.-7fda was configured to use a JMS Topic, requires container-managed transactions, and uses a foreign JMS provider. Only one thread will be used to receive and process all messages.>
Thanks,
Prantor

Are you using an IP address for the AQ datasource host instead of a hostname ?
A search on ora-24047 revealed this thread http://kr.forums.oracle.com/forums/thread.jspa?threadID=431416 which states problem could be with using IP address.

ORABPEL-12165 error while publishing a 77KB message payload to a JMS topic

Our BPEL process reports the above exception when we tried to publish a 23 line PO to a JMS topic with the default partner link settings (on a dev workstation using the OC4J JMS provider). We do not see the above errror manifest itself on smaller size purchase orders (1-6 line orders). The stack trace from the domain long is shown below:
<2006-04-05 16:28:13,390> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> XMLHelper_setJmsMessageHeadersAndPropertiesFromXML: No headers/properties set because element is null
<2006-04-05 16:28:13,406> <ERROR> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JmsProducer_execute: A resource exception occured while producing message
<2006-04-05 16:28:13,406> <ERROR> <default.collaxa.cube.ws> <JMSAdapter::Outbound>
ORABPEL-12165
ERRJMS_PROVIDER_ERR.
Could not produce message due to JMS provider error.
Please examine the log file to determine the problem.
     at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:209)
     at oracle.tip.adapter.jms.outbound.JmsProducer.execute(JmsProducer.java:114)
     at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:195)
     at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:154)
     at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:458)
     at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:647)
     at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:448)
     at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327)
     at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
     at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317)
     at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:188)
     at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408)
     at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836)
     at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:166)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:252)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5438)
     at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1217)
     at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:511)
     at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:335)
     at ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1796)
     at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
     at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
     at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
     at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
     at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
     at java.lang.Thread.run(Thread.java:534)
Caused by: javax.jms.JMSException: storeMessage(ID:Oc4jJMS.Message.OCS1PC.737371:10a6c2453eb:-8000.352,c0:a7:7:1f:24:2c:0:0:29:0:0:0:0:0:0:0:0:2a:1:a:6c:2b:84:11)
     at com.evermind.server.jms.JMSUtils.makeJMSException(JMSUtils.java:1844)
     at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1860)
     at com.evermind.server.jms.ServerStore.storeMessage(ServerStore.java:757)
     at com.evermind.server.jms.ServerStore.enq(ServerStore.java:157)
     at com.evermind.server.jms.ServerTopic.enq(ServerTopic.java:464)
     at com.evermind.server.jms.ServerTopic.enq(ServerTopic.java:97)
     at com.evermind.server.jms.JMSProvider.enqMessage(JMSProvider.java:574)
     at com.evermind.server.jms.EvermindSession.send(EvermindSession.java:1099)
     at com.evermind.server.jms.EvermindMessageProducer.send(EvermindMessageProducer.java:409)
     at com.evermind.server.jms.EvermindMessageProducer.send(EvermindMessageProducer.java:201)
     at com.evermind.server.jms.EvermindTopicPublisher.publish(EvermindTopicPublisher.java:77)
     at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:195)
     ... 30 more

look into the jms.log - can be found @ $BPEL_HOME/integration\orabpel\system\appserver\oc4j\j2ee\home\log
maybe this gives some more information..
hth clemens

Problem with calling AQ JMS Adapter with Asynchronous BPEL Process

I have a AQ JMS Adapter and i'm invoking the adapter in my BPEL process.
I'm passing an xml as payload to AQ JMS adapter. When i post the xml in the BPEL Control, i'm getting the follwoing message:
"Cannot find the specified instance". I have tried 3-4 times but getting same message all the time.
However, i'm able to publish xml to JMS Topic with synchronous BPEL process.
I want to use asynchronous BPLE process.
Please let me know if there is a way to overcome this issue.
Thanks in advance.
Thanx in Advance.

I am experiencing the exact same issue while configuring for Tibco EMS!!!
I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries!

JMS Topic Load Balancing on Cluster

Folks
How do we load balance JMS Topic on a cluster.
We have a 2 App Server configuration to a single cluster.
If we have Topic A on both OC4J instances 1,2 - and we send a message to 1 - only clients connected to 1 get the message.
What do we need to do to setup JMS clustering so that the messages sent to Topic A can be handled by both OC4J instances.

Hi Ravi,
Check this forum:
/thread/24959 [original link is broken]
Load Balancing for J2EE Web Applications
http://help.sap.com/saphelp_nw04/helpdata/en/ce/4522d557b26942b202e05ff9ee1f3a/frameset.htm
SAP Web Dispatcher - Load balancing EP6.0 SP2
/thread/19304 [original link is broken]
Reward points if this helps
Regards
Pragathi.

JMS Topic - Deliver to only one Durable Subscriber

Hi,
Is it possible to put a message onto a topic but only have it delivered to a single durable subscriber?
I realise this breaks the rules of what a topic is but this is for a scenario where a single subscriber has errored when processing the original message from the topic. I am putting a user interaction process to recover it and if the user selects ‘resubmit’ I want to put the message back on the topic but only deliver it to the one subscriber that failed to process the message.
My ways to achieve this (in order of preference) would be.
1.     JMS Adapter
2.     Writing Java to use JMS API
If neither of these are possible than:
3.     Create a System Resubmit queue and have every composite look for message on the resubmit queue (with their client ID) as well as the normal topic they use
Of course I would like to avoid 3 as it introduces a complication into every process we create that takes messages from a JMS Topic.
Thanks for your help.
Robert

I could suggest a (dirty) trick:
all subscribers subscribe to the topic using a filter (message selector, http://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bncer)
SUBSCRIBER1 uses:
destination = ALL OR SUBSCRIBER1
SUBSCRIBER2 uses:
destination = ALL OR SUBSCRIBER2
etc
The first message has the property destination set to ALL, so all subscribers will process it.
The resubmitted message will have destination = SUBSCRIBER<N>, where N is the failed subscriber

How to retreive all unconsumed messages from a topic with a MDB?

Hello!
I have a webapp that stores TextMessages in a Topic in WebLogic.
I have an ejbapp (Message driven bean) that reads messages from the topic.
If both are up and running the ejbapp reads all messages sent from the webapp to the topic.
But if I stop the ejbapp for a while and sends a couple of messages to the topic and then deploy the ejbapp again, then the ejbapp does not read the unconsumed messages. If I send a new message to the topic the ejbapp reads that new messages but it does not get the previous messages that are on the topic.
Is this the way it should work? Or could I get the message driven bean to consume all the messages that it has not consumed from the topic when it starts?
My weblogic-ejb-jar.xml looks like:
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN' 'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>OrderManagerMDB</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>200</max-beans-in-free-pool>
<initial-beans-in-free-pool>20</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>jms/OrdersTopic</destination-jndi-name>
<connection-factory-jndi-name>jms/OrdersConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>And my ejb-jar.xml looks like:
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>OrderManagerMDB</ejb-name>
<ejb-class>brownbagwarehouse.OrderManagerMDB</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>My MDB onMessage looks like:
public void onMessage(Message message)
try
TextMessage textMessage = (TextMessage)message;
System.out.println(textMessage.getText());
catch(Exception e)
e.printStackTrace();
}Best regards
Fredrik

I am not much familiar with Weblogic, but i would suggest, you do a search for how to setup "Durable Subscriptions" in Weblogic. This will ensure the the messages that were sent when the consumer was not available, will be delivered once the consumer is available

Flex with JMS Topic/Queue for Asynchronous messaging

I have been working on Flex and JMS integration using Data
Services for Asynchronous messaging. I am able to do this
successfuly. Now I am in need to do the same without using the Data
Services piece.
For doing this I have done the following ......
I have created a JMS Webservice in the Oracle JDeveloper 10G
along with Webservice Client.I am able to Listen to JMS Topic/Queue
( this has been created in the Oracle AS ) using this Webservice
and receive the messages from this JMS Topic/Queue
Asynchronously.....
But If I need to use the Flex Client , I am not able to
Communicate with this Webservice to listen to the JMS Topic/Queue.
Did any one in this forum tried to communicate with JMS
Topic/Queue without using Flex Data Service.If so please share your
inputs.

Here is my confusion (I'm using J2EESDK1.3).
On a local server I did the following
j2eeadmin -addJmsFactory jms/RemoteTCF topic -props url=corbaname:iiop:mars#mars
In the app client running on the local server I had the code
ic = new InitialContext();
// JNDI lookup. The resource factory ref points to the
// Remote Connection Factory I registered
tcf = (TopicConnectionFactory)ic.lookup("java:comp/env/jms/TopicConnectionFactory");
// The env ref points to jms/Topic of the local server
pTopic = (Topic)ic.lookup("java:comp/env/jms/PTopic");
So I'm assuming that I'm using a connection factory that connect to mars and a Topic on the local box.
On remote server mars, I deployed a MDB which use
jms/TopicConnectionFactory and jms/Topic. But I'm thinking this jms/Topic and the one I used on the local box are not the same one. Right? Then how could the app client and the MDB share messages?
Some of my explanation I don't if it makes sense or not.
ConnectionFactory is a way to tell what kind of connection it could generate (Queue, Topic, Durable etc) and Where the connection would go to (local or remote).'
As for as destination, I'm not sure. How could two server share one Topic?

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

How to subscribe to a JMS topic with a selector

Similar Messages

Maybe you are looking for