JMS Queue Issue

Hi
I have a scenarion where i read the messsges from two different queues for every 20 sec ...
once i read all the message then i have to sort the message based on timestamp in PI .. and send to the R/3 system ..
for reading the messages from two different queue i created the Two different Communication Channels...
but once i read the messages from queue how to sort by time stamp...
how to solve this issue

Hi,
sorting of messages cannot be easily (and efficiently) implemented
for that you could try with queues (EOIO) and send them to R/3 as they arrive in XI but for that you need to enable EOIO at sender and receiver
Regards,
Michal Krawczyk

Similar Messages

HowTo:Publish Msg to JMS queue deployed in a Weblogic Cluster from a client

Hello All-
I am new to Weblogic and need help from this forum. Forgive me for my ignorance. I am learning.
Below is a brief about the context and the issues that we are facing:
Background
=======
1. We have Oracle Service Bus (OSB) installed on top of Oracle Weblogic Server (ver 10.3). In OSB we have developed a proxy service that listens to a JMS queue for an incoming message
2. The Weblogic environment is a cluster having 2 managed servers listening to different ports and it is front-ended by a Apache Load Balancer.
3. Our requirement is to post an XML message from a Java client to the JMS queue which will then initiate the proxy service deployed. We are using t3 protocol to post the message from the client to the JMS queue
Issue
====
1. To post an XML message from the client, how do we give the address of the JMS queue in the clustered environment to enable failover/loadbalancing if one managed server goes down. I understand from your earlier posts in this forum that directly hitting the JMS queue on a particular managed server will not enable failover/loadbalancing in case one of them goes down
2. Do we need to modify any config file in the Apache Proxy Plugin?
3. Do we need to provide the address of the Apache proxy in the client to send the message?
Kindly clarify and let me know me know if you need any additional information.
Greatly appreciate your help!!!
Regards,
Dibya

Hi Dibya,
Please refer to : http://weblogic-wonders.com/weblogic/2010/05/13/apache-proxy-as-static-content-repository/#comment-1379
Thanks
Jay SenSharma

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.

Issue with internal JMS queue

Hi,
We discovered following issue with Netweaver version:
SAP EP 6.0 ON WEB AS 6.20
J2EE version:
Cluster-Version: 6.40 PatchLevel 106831.313
Build-On:Thursday, October 26, 2006 18:56 GMT
Perforce-Server:
Project-Dir:JKernel/630_VAL_REL
JKernel Change-List:106831
Build machine:SAPInternal
Build java version:1.3.1_18-b01 Sun Microsystems Inc.
SP-Number: 19
Source-Dir: D:\make\engine\630_VAL_REL\builds\JKernel\630_VAL_REL\archive\dbg
During sending messages into internal JMS queue we sent messages bigger than 1MB. After that, JMS queue was not able to process any other messages even if it was smaller than 1MB. Same issue occured if there was more smaller messages sent in short time (e.g. in 2 seconds). We don't have any significant error message in any log.
See information thath we have found in dump stack trace file (ix.log):
"SAPEngine_Application_Thread[impl:3]_25" prio=5 tid=0x0000000101f5ebf0 nid=0x37 in Object.wait() [fffffffe0bdfd000..fffffffe0bdff8b0]
at java.lang.Object.wait(Native Method)
- waiting on <0xfffffffe2ebfa1b8> (a java.lang.Object)
at java.lang.Object.wait(Object.java:429)
at com.sap.jms.client.memory.MemoryManager.allocate(MemoryManager.java:132)
- locked <0xfffffffe2ebfa1b8> (a java.lang.Object)
at com.sap.jms.client.memory.MemoryManager.allocateMemoryForBigMessage(MemoryManager.java:92)
- locked <0xfffffffe2ebfa1b8> (a java.lang.Object)
at com.sap.jms.client.session.Session.processFinalMessage(Session.java:1732)
at com.sap.jms.client.session.Session.run(Session.java:675)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
which indicates to us that initializing of memory is locked.
Please let us know:
-if there is any log which indicates this behaviour without making thread dump
-which limits must be fulfilled to process messages without this error
-how to unblock this lock for processing correct messages without restarting NW - or if there is any predefined timout which kill this locked session and disable uncorrect message
-how to manage records in bc_jmsqueue table for removing big messages from queue if there were loaded already
-how to stop application which caused this problem. If we try to stop it through standard stop_App, application stays in Stopping mode forever.
This problem occured in test environment and also in productive environment using the same SAP NW. Now - we do not have any work around solution..... therefore periodically we need to restart SAP NW....
Thx for any suggestions.....

Hi,
We are also facing the same problem of restarting the SAP NW each time, if you have found the solution, please let me know.
Thx in advance.
Ramanath

Issue with MDB (jms Queue) in weblogic 8.1

 Hi all...
 I'm facing a strange kind of problem with MDB using weblogic 8.1.
 The code worked perfectly in weblogic 7.0.
 This is wht i'm trying to achieve..
 i'm having a MDB which implements a onMessage().
 I'm publishing message thru a standalone client. Publishing works fine..
 The problem is onMessage(javax.jms.Message msg) is never been called :-(.
 when i monitor it shows that messages are recieved..
 Am is missing something that is really important..
 here is my code
 package com.csxwt.zodiac.service.domain;
 import javax.ejb.*;
 import javax.jms.*;
 import javax.naming.*;
 import java.io.Serializable;
 //import com.csxwt.zodiac.service.domain.TestObject;
 public class MDBTestBean implements MessageDrivenBean, MessageListener {
 MessageDrivenContext messageDrivenContext;
 public void ejbCreate() throws CreateException {
 System.out.println("into the ejb create");
 /**@todo Complete this method*/
 public void ejbRemove() {
 /**@todo Complete this method*/
 public void onMessage(javax.jms.Message msg) {
 System.out.println("into the onMessage method 1 ");
 ObjectMessage objectMsg = null;
 String strObject = "Test";
 try
 System.out.println("into the onMessage method 2 ");
 if (msg instanceof ObjectMessage)
 System.out.println("into the onMessage method 3");
 objectMsg = (ObjectMessage) msg;
 Serializable serializableObj = objectMsg.getObject();
 String test = serializableObj.toString();
 System.out.println("value of the message sent " + test);
 TestObject test1 = null;
 if(serializableObj instanceof TestObject )
 test1 = (TestObject) serializableObj;
 System.out.println("after getting the test value ");
 System.out.println("getting the test object valuye " + test1.getName());
 else
 return;
 catch (Exception e)
 System.out.println("Message Bean:unexpected Exception thrown ");
 e.printStackTrace();
 public void setMessageDrivenContext(MessageDrivenContext messageDrivenContext)
 System.out.println("into MDB context");
 this.messageDrivenContext = messageDrivenContext;
 here are the 2 xml files....
 <ejb-jar>
 <enterprise-beans>
 <message-driven>
 <display-name>MDBTest</display-name>
 <ejb-name>MDBTest</ejb-name>
 <ejb-class>com.csxwt.zodiac.service.domain.MDBTestBean</ejb-class>
 <transaction-type>Container</transaction-type>
 <message-selector>GATE_LANE</message-selector>
 <message-driven-destination>
 <destination-type>javax.jms.Queue</destination-type>
 </message-driven-destination>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <container-transaction>
 <method>
 <ejb-name>MDBTest</ejb-name>
 <method-name>*</method-name>
 </method>
 <trans-attribute>Required</trans-attribute>
 </container-transaction>
 </assembly-descriptor>
 </ejb-jar>
 <weblogic-ejb-jar>
 <weblogic-enterprise-bean>
 <ejb-name>MDBTest</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>zodiac.jms.queue.HardWareOutMessageQueue</destination-jndi-name>
 </message-driven-descriptor>
 </weblogic-enterprise-bean>
 </weblogic-ejb-jar>
 Am i missing something somewhere?????
 any help in this is highly appreciated..
 thanks in advance.
 r
 sasi


Check your log for error and warning messages. If there
 are some, they should help trace down the problem. If there
 aren't any, try confirm that your MDB is deploying in
 the first place.
 The MDB below is a Q MDB, but you write below that your client
 is a "publisher". "Publisher" implies a topic producer, not
 a queue producer, and topic producer can't publish to queues.
 Tom
 T. Sasii Dharma wrote:
 > Hi all...
 >
 > I'm facing a strange kind of problem with MDB using weblogic 8.1.
 > The code worked perfectly in weblogic 7.0.
 > This is wht i'm trying to achieve..
 > i'm having a MDB which implements a onMessage().
 > I'm publishing message thru a standalone client. Publishing works fine..
 > The problem is onMessage(javax.jms.Message msg) is never been called :-(.
 > when i monitor it shows that messages are recieved..
 > Am is missing something that is really important..
 >
 > here is my code
 >
 > package com.csxwt.zodiac.service.domain;
 >
 > import javax.ejb.*;
 > import javax.jms.*;
 > import javax.naming.*;
 > import java.io.Serializable;
 > //import com.csxwt.zodiac.service.domain.TestObject;
 >
 > public class MDBTestBean implements MessageDrivenBean, MessageListener {
 > MessageDrivenContext messageDrivenContext;
 > public void ejbCreate() throws CreateException {
 > System.out.println("into the ejb create");
 > /**@todo Complete this method*/
 > }
 > public void ejbRemove() {
 > /**@todo Complete this method*/
 > }
 > public void onMessage(javax.jms.Message msg) {
 > System.out.println("into the onMessage method 1 ");
 > ObjectMessage objectMsg = null;
 > String strObject = "Test";
 > try
 > {
 > System.out.println("into the onMessage method 2 ");
 > if (msg instanceof ObjectMessage)
 > {
 > System.out.println("into the onMessage method 3");
 > objectMsg = (ObjectMessage) msg;
 > Serializable serializableObj = objectMsg.getObject();
 > String test = serializableObj.toString();
 > System.out.println("value of the message sent " + test);
 > TestObject test1 = null;
 > if(serializableObj instanceof TestObject )
 > {
 > test1 = (TestObject) serializableObj;
 > System.out.println("after getting the test value ");
 > System.out.println("getting the test object valuye " + test1.getName());
 > }
 >
 > }
 > else
 > {
 > return;
 > }
 >
 > }
 > catch (Exception e)
 > {
 > System.out.println("Message Bean:unexpected Exception thrown ");
 > e.printStackTrace();
 > }
 >
 > }
 > public void setMessageDrivenContext(MessageDrivenContext messageDrivenContext)
 > {
 > System.out.println("into MDB context");
 >
 > this.messageDrivenContext = messageDrivenContext;
 > }
 > }
 >
 >
 > here are the 2 xml files....
 >
 > <ejb-jar>
 > <enterprise-beans>
 > <message-driven>
 > <display-name>MDBTest</display-name>
 > <ejb-name>MDBTest</ejb-name>
 > <ejb-class>com.csxwt.zodiac.service.domain.MDBTestBean</ejb-class>
 > <transaction-type>Container</transaction-type>
 > <message-selector>GATE_LANE</message-selector>
 > <message-driven-destination>
 > <destination-type>javax.jms.Queue</destination-type>
 > </message-driven-destination>
 > </message-driven>
 > </enterprise-beans>
 > <assembly-descriptor>
 > <container-transaction>
 > <method>
 > <ejb-name>MDBTest</ejb-name>
 > <method-name>*</method-name>
 > </method>
 > <trans-attribute>Required</trans-attribute>
 > </container-transaction>
 > </assembly-descriptor>
 > </ejb-jar>
 >
 > <weblogic-ejb-jar>
 > <weblogic-enterprise-bean>
 > <ejb-name>MDBTest</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>zodiac.jms.queue.HardWareOutMessageQueue</destination-jndi-name>
 > </message-driven-descriptor>
 > </weblogic-enterprise-bean>
 > </weblogic-ejb-jar>
 >
 > Am i missing something somewhere?????
 > any help in this is highly appreciated..
 >
 > thanks in advance.
 >
 > r
 > sasi

Error while passing ODI variable in JNDI Url for JMS Queue XML

Hi,
Facing a weird problem while passing ODI variable in JNDI Url for JMS Queue XML.
Below is the JNDI Url configured under ODI Topology:
JNDI Url: t3://<host_location>?d=#TEST.SCHEMA_FILE&s=<schema_name>&JMS_DESTINATION=jms/<queue_name>
where,
#TEST.SCHEMA_FILE --> ODI variable storing xsd name and location
Issue Description:
If we restart ODI server then for the first run of any ODI interface using JMS Queue XML, it is unable to get the value for ODI variable present in JNDI Url (d=#TEST.SCHEMA_FILE).
It throws error message saying: No XSD found
Temporary Resolution:
As a temporary fix if we hard-code and pass the value in that ODI variable as shown below, it will successfully go through.
eg: JNDI Url: t3://<host_location>?d=C:\XSD\test.xsd&s=<schema_name>&JMS_DESTINATION=jms/<queue_name>
Reverting it back to variable later will have no issues and subsequent run will succeed.
But again anytime later if server is restarted then first run will have this issue.
Want to have permanent fix for it.
Any one having idea on it please share. Appreciate your help!

What ODI version are you using? It could be related to the bug in the older version as described in support note Doc ID 1290326.1

BPEL process failing in many instances due to JMS performance issue...

Hi All,
We are using a JMS adapter as partner link in a BPEL process to produce messages to JMS Queue.
We are getting an error while producing a message to a JMS Queue.
The error comes for 1 or 2 instances among 5 to10 intsances. (all these instances ran with in 1 or 2 seconds).
We are using Oracle 10G SOA suite.
This error is getting in the Production environment.
The error is as follows (took error from server log).
Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{summary=file:/sw/appaia/product/SOA/bpel/domains/default/tmp/.bpel_CurrencyExchangeListEbizJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrencyExchangeListEbizJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
file:/sw/appaia/product/SOA/bpel/domains/default/tmp/.bpel_CurrencyExchangeListEbizJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrencyExchangeListEbizJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: oracle.j2ee.connector.proxy.ProxyInterceptException: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: null [Caused by: RollbackException: Transaction has been marked for rollback: null]
; nested exception is:
ORABPEL-12511
Adapter Framework unable to create outbound JCA connection.
I tried the below JMS tunings with differnt combination, but no improvem
Please let me know if any other logs or any other information is required.
Thanks,
Pershad

One of the values in the oc4j-ra.xml has the below values:
<connector-factory location="OracleASjms/MyXAQCF" connector-name="OracleASjms">
 <config-property name="jndiLocation" value="jms/XAQueueConnectionFactory"/>
 <config-property name="autoCloseSession" value="false"/>
 <connection-pooling use="private">
 <property name="waitTimeout" value="300" />
 <property name="scheme" value="fixed_wait" />
 <property name="maxConnections" value="50" />
 <property name="minConnections" value="0" />
 </connection-pooling>
 <security-config use="principal-mapping-entries">
 <principal-mapping-entries>
 <principal-mapping-entry>
 <initiating-user>servletuser</initiating-user>
 <res-user>jmsuser</res-user>
 <res-password>->jmsuser</res-password>
 </principal-mapping-entry>
 </principal-mapping-entries>
 </security-config>
 <connectionfactory-interface>javax.jms.XAQueueConnectionFactory</connectionfactory-interface>
 </connector-factory>
Where do we need to change ?
Please suggest .
Thanks

Regarding JMS-Queue/Topic in Proxy and Business service in OSB

Hi
I have one query regarding to the JMS-Queue/Topic.
I am published the message to the JMS-Queue/Topic.
----My Business-service configuration is---
General----Any xml
Tranport--jms://localhost:7001/MyConnectionFactory/RequestQueue
Response--None
I call this Business-service in proxy-service of Routing message was published successfully to thee Queue.
I try to dequeue the message from that queue for this
--- I take another proxy with---
General----Any xml
Tranport--jms://localhost:7001/MyConnectionFactory/RequestQueue
In meassage flow
Routing--second busines-service)
--- Second business-service configuration is---
General----Any xml
Tranport-File (C://temp)
Issue is when I publish the message to Queue,the message is also found in the file i.e C:temp. I don't now why this come to the file.*
Any suggestions
Thanks
Mani

Either I did not get an idea, but in your JMS proxy you are routing to File :)
If you don't want file, why route to 2nd BS ?

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

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

Queue up messages in a JMS queue during DB outages.

I am currently using a MessageDriven EJB that pops messages of a JMS queue and
then grabs a connection from a weblogic dbpool and process it. However if the
database is down, the EJB still pops off messages and then throws exceptions when
trying to get the connection from the pool and the exception is logged and the
message lost.
How can i architect the application so that when the db is down the messages are
queued up in the JMS queue, so that when the DB comes back online they can be
processed.?

The $ is not a valid character for an element NAME per W3C standards. In short you can only use letters, numbers and the underscore ( _ )..
You need to correct this message / data and reprocess the message.
Setup an Error Queue so these messages get thrown some where that will not cause issues in your system. Then use error handling in something like AIA to report back to your support staff that a bad message was encountered, needs to be fixed and reprocessed.
You will see that if you do a google search for how to escape a dollar sign in xpath, there are no good results....
Hope that helps!
-Luke

JMS Dequeue issue -- OSB

Hi,
We have created a JMS Queue in WLS 10.3.0 and OSB (10.3.1) process is using proxy service - JMS transport to dequeue messages.
WLS JMS Queue -->OSB Proxy --> Business Service (JCA Db adapter) to insert data into a table
IF error in db --> Invoke OSB error handler and write to a file
Case - Success
Messages are deleted from the queue
Case - Failure
Messages are not deleted from the queue. Error handler is invoked in OSB and messages are written to a file.
This is creating an issue since OSB retries and number of files are created. We have tried setting retry settings in OSB, but in vain.
Please provide inputs, this is a bit of emergency.
Regards,
AP
Edited by: ARPL on Oct 15, 2009 3:41 AM

Am also dumb...
You need to create a new proxy service (and select the message type which suits your process, anysoap any xml, wsdl, etc), on the second tab you can select the transport.
In here select jms from the listbox and for the endpoint insert "jms://yourhost:yourpost/yourconnectionfactory/yourqueue"
thats all what is needed to let your proxy service pick up the messages from the queue.
eventually you want to route this message to something else, so for that you need to decide what sort of business service you use (webservice wsdl based, or just some other jms endpoint,or file...you name it)
@@JMS implementation in OSB
OSB concepts are really hard to digest if u r SOA developer from start. Proxy Service will act as a Inbound for JMS. It still shows the "Destination type" in JMS Transport Config tab
Really Confussing....
Sushil
Edited by: Sushil Deshpande on Jan 26, 2011 2:22 AM

JMS channel issue

Hi
My XI system is set-up with alerts frame-work and we are able to raise almost all the system generated alerts. But we are facing one issue with JMS channel alerts. Lets me explain the problem.
We have a JMS channel connected to JMS Server and we are publishing the messages on JMS queue. When JMS server is down, the channel status is not turning into red and it is staying in gree only. If we see the messages in adapter engine (through message monitoring) they are in delivering mode and they are not going into system error state. So either of the things are not triggering any system alerts. So are there any parameters that we can set-up in JMS channel or somewhere so that when JMS server is down, we can raise the system alerts ?? We are using the EMS server for hosting the JMS queues.
thanks
kumar

Hi Moorthy
yes! as you said, my main problem is..... channel is not turning into red, eventhough my JMS server is down and there by not able to raise the alert in either of the two cases. (Adapter Engine based standard alerts or CCMS Alerts). Is there any option to set through which when jms server is down, channel will become red ??
thanks
kumar

How can I put non-English characters onto JMS queues?

Hi
I am posting XML documents onto a JMS queue configured in a WLS domain. The XML doc is UTF-8 but WebLogic does not seem able to handle the advanced characters and shows them as 2 chars each (such as umlauts). How can I configure WebLogic to handle such special characters?
Any help greatly appreciated,
Craig

In order to send an XML message we need to use Interface XMLMessage and send the message by setDocument(Document document) .
In the document set the content of the message to the DOM document. If we follow this procedure I guess there should not be any issue.
Regards,
hy

Unable to insert messages in JMS QUEUE

Hi All,
I am facing an issue while inserting messages in JMS queue.
The JMS Queue is on another weblogic server and now i created a bpel process which has a jms adapter to insert messages inthe jms queue.I am deploying the Bpel in my server which does not have this particular JMS queue.
I am unable to insert the messages into the JMS queue present on another weblogic server. where as i am able to insert messages if the queue is present on my server.
Can you please let me know if its possible to put messages into a queue on remote server from local server.
Thanks in advance.

Most probably it seems like an issue of security. Please try to establish cross domain trust between these two Weblogic server domains. For more information refer to http://download.oracle.com/docs/cd/E1284001/wls/docs103/secmanage/domain.html#wp1175687_

JMS Queue Issue

Similar Messages

Maybe you are looking for