Re: Consuming jms queue synchronously in SOA11g

Hi
I have the below requirement
In Queue total 5 messages are there, in those 3 are with same ID and 2 are with same ID.
My requirement is that for the above 5 messages only two BPEL processes should be created for each ID.
1st BPEL consumes 3 messages
2nd BPEL consumes 2 messages
Please give me idea to do this.
Thanks in Advance
Vamsi..

Hello friend,
So, according to your scenario...you are producing messages into the Queue using JMS Adapter Outbound Operation ( JMS adapter is on the references side)
And as we know, in order to read the message from JMS Queue we use JMS Adapter and that would be inbound operation (JMS adapter is on the services side)
So, when we define a JMS adapter in our composite as consume message operation...then the JMS adapter will be on the services side...then we declare our BPEL interface based on the WSDL of JMS Adapter (Consume operation). SO by default the interface of the BPEL would be one-way i.e., just fire and forget. So, lets say you wrote 10 messages to the Queue. So, the consuming BPEL would take all messages at a time...as you said there would be 10 instances....
So, if you make the interface of the BPEL to synchronous and also you just need to reply back ( any dummy message) to JMS adapter....just keep a reply activity at the end of the BPEL ...so by doing this...unless and until it gets the response from the synchronous BPEL (consuming BPEL), the JMS adapter doesn't give the next message in the Queue to the BPEL...that means at any point of time only one BPEL instance would be running for you which is what we want to achieve...And you can see this clearly in the Queue in the weblogic admin console...This is called throttling the JMS adapter....This works...
And one more important thing to be considered is...taking the synchronous process time out thing...as we know by default the client of the synchronous process cannot wait for more than 45 seconds...may be if you want more time to process ...you can change that in EM console...BPEL properties in SOA administration...
I think it is syncMaxWaitTime..change that may be to 300...
Try this...Hopefully this should work for you..and let us know ...
Hope this helps...
Thanks,
N

Similar Messages

MDBs in 9.1 continue to consume JMS queues even after being deleted

We have an MDB application that reads a batch message off of a JMS queue, archives it in a database, parses the batch message into individual messages and writes them onto other JMS queues to be consumed by another application. Everything was running fine in Weblogic 8.1.5. However, due to problems with XA drivers and the MSDTC(predictable SQL server crashes), we decided to upgrade to Weblogic 9.1 to take advantage of the LLR option.
 First, we had an issue where our MDBs were causing the following exception:
 ####<May 26, 2006 7:42:12 PM EDT> <Error> <JMX> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686932991> <BEA-149500> <An exception occurred while registering the MBean null.
 java.lang.IllegalArgumentException: Registered more than one instance with the same objectName : com.bea:ServerRuntime=wltest1,MessageDrivenEJBRuntime=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,Name=RhapsodyMDB_DMBModule!JMSServer4@DMB_BEAN_QUEUE,ApplicationRuntime=DataBrokerEAR1_2,Type=EJBPoolRuntime,EJBComponentRuntime=DataBrokerEJB new:[email protected] existing weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl@7db003
 at weblogic.management.jmx.ObjectNameManagerBase.registerObject(ObjectNameManagerBase.java:146)
 at weblogic.management.mbeanservers.internal.WLSObjectNameManager.lookupObjectName(WLSObjectNameManager.java:133)
 at weblogic.management.jmx.modelmbean.WLSModelMBeanFactory.registerWLSModelMBean(WLSModelMBeanFactory.java:86)
 at weblogic.management.mbeanservers.internal.RuntimeMBeanAgent$1.registered(RuntimeMBeanAgent.java:104)
 at weblogic.management.provider.internal.RegistrationManagerImpl.invokeRegistrationHandlers(RegistrationManagerImpl.java:205)
 at weblogic.management.provider.internal.RegistrationManagerImpl.register(RegistrationManagerImpl.java:85)
 at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:320)
 at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:257)
 at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:222)
 at weblogic.ejb.container.monitoring.EJBPoolRuntimeMBeanImpl.<init>(EJBPoolRuntimeMBeanImpl.java:32)
 at weblogic.ejb.container.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:49)
 at weblogic.ejb.container.manager.MessageDrivenManager.initialize(MessageDrivenManager.java:503)
 at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:120)
 at weblogic.ejb.container.manager.MessageDrivenManager.setup(MessageDrivenManager.java:146)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManager(MessageDrivenBeanInfoImpl.java:1481)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createDDMDManagers(MessageDrivenBeanInfoImpl.java:1378)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onDDMembershipChange(MessageDrivenBeanInfoImpl.java:1285)
 at weblogic.jms.common.CDS$DD2Listener.listChange(CDS.java:454)
 at weblogic.jms.common.CDSServer$DDHandlerChangeListener.statusChangeNotification(CDSServer.java:167)
 at weblogic.jms.dd.DDHandler.callListener(DDHandler.java:318)
 at weblogic.jms.dd.DDHandler.callListeners(DDHandler.java:344)
 at weblogic.jms.dd.DDHandler.run(DDHandler.java:282)
 at weblogic.jms.common.SerialScheduler.run(SerialScheduler.java:37)
 at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
 >
 ####<May 26, 2006 7:42:13 PM EDT> <Info> <EJB> <ist-clft2> <wltest1> <ExecuteThread: '1' for queue: 'default'> <<WLS Kernel>> <> <> <1148686933069> <BEA-010060> <The Message-Driven EJB: RhapsodyMDB has connected/reconnected to the JMS destination: weblogic.jms.DMB_BEAN_QUEUE.>
 
 Generally this happend after there were cluster communication issues. Multi-cast messages were lost and our MDB reconnects to the JMS queues as indicated by the below log:
 ####<May 30, 2006 5:19:06 PM EDT> <Info> <EJB> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '54' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1149023946040> <BEA-010060> <The Message-Driven EJB: DataBrokerMDB has connected/reconnected to the JMS destination: weblogic.jms.PHINMS_DMB_QUEUE.>
 ####<May 30, 2006 5:19:10 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023950228> <BEA-000112> <Removing RAPBEA3S jvmid:720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S from cluster view due to timeout.>
 ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951009> <BEA-000115> <Lost 2 multicast message(s).>
 ####<May 30, 2006 5:19:11 PM EDT> <Info> <Cluster> <AMTC-RAP-STG3> <RAPBEA1S> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1149023951040> <BEA-000111> <Adding RAPBEA3S with ID 720875810499147484S:cmts-rap-bea3:[7005,-1,-1,-1,-1,-1,-1]:DMBstg:RAPBEA3S to cluster: DMBstg_cluster view.>
 
 This would cause the queues to eventually have hundreds of consumers and cause the server to fail.
 Basically, it seems as though the MDBs that are supposed to stop continue and attempt to process, while new threads connect to the JMS queues.
 I tried undeploying our application and deleted it from the configuration. However there were consumers still on the respective queues and when I sent messages, I got an error indicating a "Class Not Found exception" due to the fact that the EJB was undeployed and deleted from the configuration, however the MDB component was not and continued to listen for messages. In 8.1.5, as soon as the application was undeployed, there were zero consumers on the JMS queues.
 I have read the posts about a soon to be released fix that would have the MDBs connect only to the queues locally and not go out the the cluster. Would this fix my issue?
 Is there something in the deployment descriptor to configure that will cause it to disconnect and now spawn so many consumers to the JMS queues?
 Why is it that the number of MDB consumers on the JMS queues stayed static in 8.1.5, but they are erratic in 9.1 even after I set our 9.1 server to use the 8.1.5 execute queue policy. Help would be much appreciated.

I recommend contacting customer support. There's a known problem with MDBs listening to distributed destinations that are local to the same cluster as the MDB, you're problem may be related (the clue is that the stack trace contains jms.dd.DDHandler.callListeners()). The problem is that the MDB connects to all physical queues in a distributed destination rather than just the local queue.
 Tom

Issue in Synchronous OSB using Jms Queues in OSB11g

Hi,
I am working on building a synchronous OSB using the following steps.
1) Creating the Synchronous OSB Proxy Service which routes the message to the business service which in turn places a message in the Queue(inqueue) by populating the JMSCorrelationId and waits for the response message to consume from another queue.
2) A Composite(SOA) will consume the message from this Queue
3) It will do necessary transformation and Places it in another Queue (Say Response Queue).
4) OSB Business service waiting in Step 1 will receive the response from this response Queue.
I used a sample Wsdl which has both request and response message types.
I observed that the correlation ID is maintained properly from inqueue to response queue. But the message is not getting picked up by OSB from the response Queue
Twist: It is working absolutely fine in OSB 10g but it is not working in OSB 11g.
I tried using Messaging service as well as using the sample WSDL i.e keepiing the soap message in the queue. Both the cases are working absolutely fine OSB 10g but not in OSB 11g.
Can anyone faced a similar issue or any pointers will be great help in this regard.
Regards,
Ashok

To debug this further can you check if the response Q has any active consumers. ? When you use response by correlation ID business service, OSB actually creates MDB's with message selectors under the hood.
This is a sample of the ejb-jar.xml of the MDB created for a business service with response by Correlation ID pattern.
<?xml version='1.0' encoding='UTF-8'?>
<jav:ejb-jar xmlns:jav="http://java.sun.com/xml/ns/javaee">
<jav:display-name>BEA ALSB JMS Outbound Sync-Async Endpoint</jav:display-name>
<jav:enterprise-beans>
<jav:message-driven>
<jav:ejb-name>ResponseEJB-6577847719916437493-3893eeb7.1287d30ba4f.-7fe1</jav:ejb-name>
<jav:ejb-class>com.bea.wli.sb.transports.jms.JmsAsyncResponseMDB</jav:ejb-class>
<jav:transaction-type>Container</jav:transaction-type>
<jav:message-destination-type>javax.jms.Queue</jav:message-destination-type>
<jav:activation-config>
*<jav:activation-config-property>*
*<jav:activation-config-property-name>messageSelector</jav:activation-config-property-name>*
*<jav:activation-config-property-value>JMSCorrelationID LIKE 'ID:424541534594cf52%'</jav:activation-config-property-value>*
*</jav:activation-config-property>*
</jav:activation-config>
<jav:env-entry>
<jav:env-entry-name>service-ref</jav:env-entry-name>
<jav:env-entry-type>java.lang.String</jav:env-entry-type>
<jav:env-entry-value>BusinessService$Test$RequestQ</jav:env-entry-value>
</jav:env-entry>
As you can see the message selector is based on JMSCorrelationID LIKE 'ID:424541534594cf52%'. This means the business service will pick only those messages which has its correlation ID starting with ID:424541534594cf52.
You can see the message selector for your MDB from admin console --> deployments.
Check and confirm if the correlation ID created in the request also starts with this value and the same is send back from the server. Also try deleting and recreating the business service or rename the business service which will create a new MDB under the hood and check the above.

JMS queue consumer challenge

Hi there,
 I have met a pretty challenging problem in JMS queue consumer and
 would like to know if any JMS lovers in the group know about it.
 We have queue receiver listening on queue which contains a number of
 mugs.
 Once a msg is received (onMessage returns), the msg is handed over to
 a worker thread from a thread pool.
 Essentially there are two parts of the problem:
 1. We want kind of flow control - only x number of msg can be
 processed at a given time. This can be resolved by using semaphore.
 However, there might be better solution out there. Anyhow, this is
 less an issue than the second part -
 2. As we know client_acknowledge happens at the session level:
 Acknowledging a consumed message automatically acknowledges the
 receipt of all messages that have been consumed by its session. For
 example, if a message consumer consumes ten messages and then
 acknowledges the fifth message delivered, all ten messages are
 acknowledged.
 -- this is the problem -- we want to acknowledge each msg
 individually so that only the processed msg is acknowledged although
 there are x number of msg being retrieved. By doing that we won't lost
 any msg in case the JMS client crashes.
 It is a challenge, isn't it? Might well not be one for you, if you
 know the trick. If you do, could you share with us? Thanks a lot.
 Mike


Just to be clear, I favor (2), where each worker thread has its own session and
 consumer.
 This naturally throttles, as there are only as many outstanding messages as
 worker-threads.
 BTW, be aware that it is against spec, and dangerous, to call acknowledge()
 outside of
 onMessage() - as this multi-threads the Session and Session's are not thread
 safe.
 Tom
 Tom Barnes wrote:
 > Actually you both are correct. The ack behavior is configurable on the
 > connection factory via the "AcknowledgePolicy", where the default is
 > what the spec requires (ack-all). Prior to 6.1
 > the behavior was what one would expect (ack-before).
 >
 > As for how to solve the problem at hand. I can think of three approaches:
 >
 > (1) use the current async consumer but set the ack-policy
 > to ack-before, and defer acknowledging a msg until all msgs before
 > it have finished their processing
 >
 > (2) use multiple synchronous consumers, one consumer per defered msg
 >
 > (3) use a single synchronous consumer, but dequeue transactionally,
 > one transaction per msg. suspend the transaction, then have
 > the worker thread resume the transaction once it finishes processing
 > the message and call commit. (Take care that the default
 > tran timeout is 30 seconds.)
 >
 > Shean-Guang Chang wrote:
 >
 > > Just to correct one assumption. Ack the fifth message will not ack message
 > > received after that (e.g. message 6, 7, 8, etc...). At least not WLS JMS.
 > > If this is not true for you please give details of your client code and
 > > version of WLS JMS you have. Thanks!
 > >
 > > "Mike" <[email protected]> wrote in message
 > > news:[email protected]...
 > > > Hi there,
 > > >
 > > > I have met a pretty challenging problem in JMS queue consumer and
 > > > would like to know if any JMS lovers in the group know about it.
 > > >
 > > > We have queue receiver listening on queue which contains a number of
 > > > mugs.
 > > > Once a msg is received (onMessage returns), the msg is handed over to
 > > > a worker thread from a thread pool.
 > > >
 > > > Essentially there are two parts of the problem:
 > > >
 > > > 1. We want kind of flow control - only x number of msg can be
 > > > processed at a given time. This can be resolved by using semaphore.
 > > > However, there might be better solution out there. Anyhow, this is
 > > > less an issue than the second part -
 > > >
 > > > 2. As we know client_acknowledge happens at the session level:
 > > > Acknowledging a consumed message automatically acknowledges the
 > > > receipt of all messages that have been consumed by its session. For
 > > > example, if a message consumer consumes ten messages and then
 > > > acknowledges the fifth message delivered, all ten messages are
 > > > acknowledged.
 > > > -- this is the problem -- we want to acknowledge each msg
 > > > individually so that only the processed msg is acknowledged although
 > > > there are x number of msg being retrieved. By doing that we won't lost
 > > > any msg in case the JMS client crashes.
 > > >
 > > > It is a challenge, isn't it? Might well not be one for you, if you
 > > > know the trick. If you do, could you share with us? Thanks a lot.
 > > >
 > > > Mike

Exception in the XML consuming from JMS Queue

In the CEP application we have a business flow like we want to consume an xml message from the JMS queue.
While CEP is consuming the message sometimes we are getting an exception.
But this issue occurs rarely and we have no idea about the root cause.
I am attaching the trace of this exception.
It seems this exception is from weblogic server itself.
Also this could be an interface problem, since its showing a casting error.
The Bug description:
When we send a meter event through SOAP UI in the CEP visualizer when the event is consumed CEP also shows this exception.
This may not halt the analysis process of the event, but this unwanted piece of code/lines have to be avoided.
<OutageEvent xmlns:ns1="http://www.accenture.com/INDE"; xmlns:wsa="http://www.w3.org/2005/08/addressing"; xmlns="http://www.accenture.com/INDE"><meterId xmlns="">203</meterId><outageType xmlns="">Permanent Outage</outageType><premiseId xmlns="">1111</premiseId><timeEvent xmlns="">2010-07-30T</timeEvent><heName xmlns="">SAMPLEHE</heName></OutageEvent>
<Jul 30, 2010 11:01:50 AM IST> <Error> <JMSAdapter> <BEA-2041118> <Setup for JMS task for destination JMS_OI_MeterState_MeterEvent_Queue at provider t3://10.212.182.30:8002 failed with exception: weblogic.jms.common.JMSException: [JMSClientExceptions:055039]A system error has occurred. The error is java.lang.ClassCastException: weblogic.workarea.StringWorkContext
weblogic.jms.common.JMSException: [JMSClientExceptions:055039]A system error has occurred. The error is java.lang.ClassCastException: weblogic.workarea.StringWorkContext
at weblogic.jms.client.JMSSession.handleException(JMSSession.java:3121)
at weblogic.jms.client.JMSConsumer.receiveInternal(JMSConsumer.java:650)
at weblogic.jms.client.JMSConsumer.receive(JMSConsumer.java:526)
at weblogic.jms.client.WLConsumerImpl.receive(WLConsumerImpl.java:184)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveMessage(AbstractPollingMessageListenerContainer.java:405)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:308)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:261)
at com.bea.core.asyncbeans.internal.DefaultMessageListenerContainer.receiveAndExecute(DefaultMessageListenerContainer.java:59)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:982)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:974)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:876)
at com.bea.core.asyncbeans.internal.WorkManagerTaskExecutor$1.run(WorkManagerTaskExecutor.java:38)
at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.ClassCastException: weblogic.workarea.StringWorkContext
at weblogic.rjvm.MsgAbbrevInputStream.readContext(MsgAbbrevInputStream.java:243)
at weblogic.workarea.spi.WorkContextEntryImpl.<init>(WorkContextEntryImpl.java:47)
at weblogic.workarea.spi.WorkContextEntryImpl.readEntry(WorkContextEntryImpl.java:97)
at weblogic.workarea.WorkContextLocalMap.receiveRequest(WorkContextLocalMap.java:151)
at weblogic.jms.common.JMSWorkContextHelper.readWorkContext(JMSWorkContextHelper.java:89)
at weblogic.jms.common.MessageImpl.readExternal(MessageImpl.java:2275)
at weblogic.jms.common.TextMessageImpl.readExternal(TextMessageImpl.java:354)
at weblogic.jms.common.JMSConsumerReceiveResponse.readExternal(JMSConsumerReceiveResponse.java:133)
at weblogic.messaging.dispatcher.DispatcherObjectHandler.readResponse(DispatcherObjectHandler.java:154)
at weblogic.messaging.dispatcher.DispatcherProxy.unmarshalResponse(DispatcherProxy.java:269)
at weblogic.messaging.dispatcher.DispatcherProxy.dispatchSyncTranFuture(DispatcherProxy.java:134)
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncTran(DispatcherWrapperState.java:338)
at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchSyncNoTran(DispatcherWrapperState.java:386)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:59)
at weblogic.jms.client.JMSSession.receiveMessage(JMSSession.java:886)
at weblogic.jms.client.JMSConsumer.receiveInternal(JMSConsumer.java:647)
at weblogic.jms.client.JMSConsumer.receive(JMSConsumer.java:526)
at weblogic.jms.client.WLConsumerImpl.receive(WLConsumerImpl.java:184)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveMessage(AbstractPollingMessageListenerContainer.java:405)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:308)
at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:261)
at com.bea.core.asyncbeans.internal.DefaultMessageListenerContainer.receiveAndExecute(DefaultMessageListenerContainer.java:59)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:982)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:974)
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:876)
at com.bea.core.asyncbeans.internal.WorkManagerTaskExecutor$1.run(WorkManagerTaskExecutor.java:38)
at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
11:01:50,548 INFO MeterInputConverter : 81 - Accepted the input xml :<?xml version="1.0" encoding="UTF-8" ?><MeterEvent xmlns:inde="http://www.accenture.com/INDE"; xmlns:wsa="http://www.w3.org/2005/08/addressing"; xmlns="http://www.accenture.com/INDE">;
<meterId xmlns="">103</meterId>
<outageType xmlns="">RESUME</outageType>
<premiseId xmlns="">1111</premiseId>
<timeEvent xmlns="">2010-07-30T</timeEvent>
<lastGasp xmlns="">false</lastGasp>
<heName xmlns="">CURRENT</heName>
</MeterEvent>

Hi,
I will forward this to the weblogic JMS team, to see if they have any insight for us.
Regards,
Seth

How to pick(or consume) messages from Woblogic JMS Queue only when DB is UP

Hi,
I have a requirement to pick(or consume) messages from Woblogic JMS Queue only when DB is UP.
When DB is down, messages should remain in queue. When DB is up, messaged should be picked on scheduler basis.
We are using SOA suite 11g(BPEL or mediator,JMS Adapter).
What is the best way to achive it in SOA 11g.
I tried, but when I setup a Consumer, there is no control over there. Messages are picked automatically.
Please advise.
Thanks
Ram

something wrong with the design.
why dont you set the retry options in the fault policies?
So if the external DB is down you could reprocess them after specified interval or make it go to human retry queue.
Then you could use SOA api to retry all of them.
--Prasanna

Consumer number for a JMS queue continues to grow

 I am using WLS 7.0 SP2. I have a JMS Queue and number of consumers continues to
 grow.
 Is there any way to stop it from growing? If not, should I be concerned about
 the memory usage by those consumers?
 Thanks.
 Rick


 Tom,
 You are right on JMS resources. We found that developer didn't close JMS session
 and conneciton which caused the memory leak. Now it has being running more than
 10 hours without crashing.
 Thanks.
 Rick
 Tom Barnes <[email protected]> wrote:
 >
 >Rick Chang wrote:
 >> I am using WLS 7.0 SP2. I have a JMS Queue and number of consumers
 >continues to
 >> grow.
 >>
 >> Is there any way to stop it from growing?
 >
 >No.
 >
 >> If not, should I be concerned about
 >> the memory usage by those consumers?
 >
 >Before jumping to conclusions though, make sure
 >that you are looking at the right statistic, there
 >are three for consumer count:
 > current -- active consumer count
 > high -- highest active consumer count
 > total -- total consumers ever created
 > (ever increasing by definition)
 >
 >If you are looking at "current"
 >the statistics point to a likely memory/resource leak.
 >Perhaps some part of your application is failing to close
 >its JMS resources when it is finished with them.
 >
 >>
 >> Thanks.
 >>
 >> Rick
 >

Reg: Consuming missing data by JMS queue.

Hi,
System1 is configured to send XML messages though JMS queue to my WL-server. But some times i have observed missing of message consumption at my server end.
what may be the reason? How can i consume the missing XML messages? is there any place where missing data will be stored?
Please advise...!
Regards,
Sk

When I meant there is an expiry time set with the message. It means the message is received by your WLS, but you are not able to see it because the message has expired.
You can only view the messages that are not expired.
If you think you are not even receiving the message, may be you can enable debugging on the WLS JMS and see if you are able to get more details in the server logs.
Please refer - http://download.oracle.com/docs/cd/E12840_01/wls/docs103/jms_admin/troubleshoot.html#wp1128871
Thanks,
Patrick

JMS stand-alone client consuming a queue in GlassFish cluster

I want to connect to a JMS queue running in clustered glassfish enterprise 2.1 and consume a message. I have a simple client app. that works with my one-machine cluster (pointing it either to first or second node, ports 3330 or 3331), but doesn't work with a company cluster (two machines, two nodes).
 Hashtable properties = new Hashtable();
 properties.put(Context.PROVIDER_URL, "iiop://" + hostname + ":" + port);
 properties.put("org.omg.CORBA.ORBInitialHost", hostname);
 properties.put("org.omg.CORBA.ORBInitialPort", "" + port);
 properties.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.appserv.naming.S1ASCtxFactory");
 try {
 ctx = new InitialContext(properties);
 } catch (NamingException ex) {
 ex.printStackTrace();
 }The program fails on line ctx = new InitialContext(properties);
The strange thing is, whatever I use as hostname or port, it always ends like this:
27.5.2009 18:03:17 com.sun.appserv.naming.RoundRobinPolicy setClusterInstanceInfo
WARNING: NAM1005 : No Endpoints selected. Please specify using system property com.sun.appserv.iiop.endpoints.
27.5.2009 18:03:17 com.sun.appserv.naming.RoundRobinPolicy getEndpointForProviderURL
WARNING: NAM1001: No Endpoints selected in com.sun.appserv.iiop.endpoints property. Using JNDI Provider URL iiop://10.0.0.30:33700 instead
27.5.2009 18:03:18 com.sun.appserv.naming.RoundRobinPolicy setClusterInstanceInfo
INFO: endpoint.weight after checking isWeight = 10
27.5.2009 18:03:18 com.sun.appserv.naming.RoundRobinPolicy setClusterInstanceInfo
INFO: sumOfAllWeights = 10
27.5.2009 18:03:19 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
 at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2690)
 at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2711)
 at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:261)
 at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:274)
 at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:130)
 at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:192)
 at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:181)
 at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:325)
 at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
 at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
 at com.sun.corba.ee.impl.folb.ClientGroupManager.getInitialClusterInstanceInfo(ClientGroupManager.java:596)
 at com.sun.corba.ee.impl.folb.ClientGroupManager$GIS.getClusterInstanceInfo(ClientGroupManager.java:620)
 at com.sun.corba.ee.impl.folb.ClientGroupManager.getClusterInstanceInfo(ClientGroupManager.java:666)
 at com.sun.appserv.naming.GroupInfoServiceObserverImpl.membershipChange(GroupInfoServiceObserverImpl.java:73)
 at com.sun.appserv.naming.S1ASCtxFactory.getInitialContext(S1ASCtxFactory.java:290)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
 at javax.naming.InitialContext.init(InitialContext.java:223)
 at javax.naming.InitialContext.<init>(InitialContext.java:197)
 at client.JmsQueueConsumer.<init>(JmsQueueConsumer.java:41)
 at client.JmsQueueConsumer.main(JmsQueueConsumer.java:57)
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect
 at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:347)
 at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:244)
 ... 18 more
Caused by: java.net.ConnectException: Connection refused: connect
 at sun.nio.ch.Net.connect(Native Method)
 at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:507)
 at com.sun.corba.ee.impl.orbutil.ORBUtility.openSocketChannel(ORBUtility.java:105)
 at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:332)
 ... 19 moreI've tried to turn off all firewalls between me and the cluster but it still doesn't work. ANy ideas what can be wrong? I guess clusters are always different...
(I will try to do more investigation, especially packet capturing, later)

Double check the ORB configuration in the servers...
+"The default naming service port in the app server is 3700. If the naming service is running on a different port, you'll need to set it via the -Dorg.omg.CORBA.ORBInitialPort property when starting the client JVM. You can double-check the actual naming service port for a given server instance by looking in the server instace's domain.xml for "orb-listener-1". Alternatively, check the Applications..Configuration..ORB..IIOP Listeners section of the admin GUI for orb-listener-1."+
[https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#StandaloneRemoteEJB|https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html#StandaloneRemoteEJB] (step-5)
Edited by: Conchas on Aug 3, 2009 12:12 PM

Program to consume the JMS queue

Hi, I' m new to WebLogic stuff. Got a question over here. There's a JMS queue that we want to have a program (not those built in stuff from weblogic) to see if they re consumed. Similar stuff would be displayed like
 ABCD Queue consumers: 1 / consumers high: 0 ...messages: 10 / messages received: 19........
 as if we get into the console page to check the JMS queues.
 I've got no clues yet. We don't wanna check the number of files from C:\Original and the destination folder C:\Destin......if so, it'd be an easy task but that s not what we wanted....

As with any WebLogic subsystem, you can get all statistics programmatically using standard JMX mbeans (see the JMX developer guide). The console uses these beans, as does the WLST scripting language. In addition, there are helper methods in the public weblogic.jms.extensions package that simplify access to these beans.
 I think there are various mbean and WLST samples on dev2dev, including one called "JMSStats.java". Note that JMSStats.java, and some other samples were written for versions 8.1 and earlier. They use deprecated methods that don't have access to all runtime statistics for 9.0 and later versions.
 Tom

Read message synchronously from JMS queue using OSB

Hi,
Is it possible to read message from the JMS queue using OSB based on the request invocation. I know messages can be read from the queue but it will be polling based.
The requirement is to have an OSB proxy service (HTTP service ) an an interface to the client application. Client application invokes the proxy service and the proxy service need to read message from the JMS queue and provide the message as response to the client.
Let me know if there are any pointers.
Thanks
Sandeep

Hi,
I spent some time trying to do this and apart from creating custom database tables etc. I was not able to achieve this.
We wanted to use in memory JMS queues in our situation.
In the end we developed a Java Web Service which preformed the on-demand read from the queue (using a particular message selector)
This is working for us without a problem
Robert

JMS-130 JMS queue cannot be multi-consumer enabled

error:
queue = ((AQjmsSession)t_sess).getQueue("tmp", "tmp_queue");
pl/sql code:
BEGIN
DBMS_STREAMS_ADM.SET_UP_QUEUE(
queue_table => 'tmp_queue_table',
queue_name => 'tmp_queue');
END;
BEGIN
SYS.DBMS_AQADM.CREATE_AQ_AGENT(
agent_name => 'explicit_dq');
END;
BEGIN
DBMS_AQADM.ENABLE_DB_ACCESS(
agent_name => 'explicit_dq',
db_username => 'tmp');
END;
DECLARE
subscriber SYS.AQ$_AGENT;
BEGIN
subscriber := SYS.AQ$_AGENT('explicit_dq', NULL, NULL);
SYS.DBMS_AQADM.ADD_SUBSCRIBER(
queue_name => tmp.tmp_queue',
subscriber => subscriber);
END;
I search in forums, google but i can not find solution. Any idea?
regards

Bill,
I could be mistaken, but as far as I know, you can only access JMS queues from java. In other words, "queue_payload_type" needs to be: SYS.AQ$_JMS_OBJECT_MESSAGE
Good Luck,
Avi.

Dequeue from JMS Queue 10 at a time and process it.

Hi,
I have created a JMS queue in weblogic.
Say i enqueue 1000 records in the queue at one go.
Now, i want a bpel process to dequue from it and process it.
However as per my requirement i want at a time 10 instances being active at a time i.e. 10 records from the queue are being processed at a time.
Once any one of them finishes, the other will pick up the message.
1 BPEL instance will process only 1 record from Q at a time
Please let me know how to achieve this.

You need to understand here that it is adapter which deques the message from queue and it will deliver it to BPEL for processing which is an async process. So adapter will keep dequeing messages and keep publishing it to BPEL irrespective of whether BPEL process has completed processing.
You may need to tweak the adapter configuration here. First of all create the synchronous BPEL composite so that both adapter and BPEL work in same transaction -
https://blogs.oracle.com/adapters/entry/creating_a_synchronous_bpel_composite_using_file_adapter
You may control the number of threads for inbound JMS adapter using binding property "adapter.jms.receive.threads" in composite.xml
Regards,
Anuj

Reading Message from Foreign JMS Queue in SOA Suite 11g.

Hi,
I am trying to read a JMS message that has been put into a JMS Queue on a remote weblogic Server.
The steps that I know is that I need to create a foreign JMS Server and then probably use JMS Adapter to subscribe to the message that is lying in the remote queue.
Has anybody been able to achieve this kind of scenario working for a remote JMS queue? Also, is this supported by JMS Adapter in SOA11g?
Any help will be appreciated.
Regards,
Varun Maheshwari

Hi Atheek1,
Thanks for your reply.
The confusion that is pondering me is that do I need to create a Foreign JMS Server or should I create a JMS adapter and override the properties.
I have tried the steps for creating a Foreign Server from the below link
Unable to access remote JMS Queue through JMS Adapter
But I am not able to find the Foreign Server created and any connection factories and Destinations related to foreign Server in my JMS Destination while configuring JMS Adapter.
I am not sure how to do step2 as entailed by you.
Could you please explain me in little detail on how to do this or redirect me to some blog or forum which will be really helpful.
Cheers,
Varun

How to keep a back up of messages from the JMS queues?

Hi,
I need to keep a back up of messages which are coming in the JMS queue before they get consumed. This is for recovery purpose.
I checked file store option but it doesnt have any time stamp on messages so dont know how to trace back messges if needed from file store.
Please let me know if you guys have any idea to handle this.
Thanks in advance
Bips

No. Not with Time Machine at least.
If you tell Time Machine to backup the external then you will have it.
Or you can manually copy it to another disk for storage outside of Time Capsule/TimeMachine.
Allan

Re: Consuming jms queue synchronously in SOA11g

Similar Messages

Maybe you are looking for