Debatching is possible when we are reading messages from JMS queue

Hi all,
If i place a message in a queue can i read the message from JMS using BPEL ( JMS Adapter ) or OSB( JMS Transport ) like batcth rather than reading the whole message in to the OSB or BPEL at the same time .
is this option is available in OSB/BPEL ??
Thanks
Phani

Similar Messages

Recieve/Read Messages from JMS Queue through ALSB

Hi,
I have configured JMS Queue in weblogic server.
I have created Messaging Service in ALSB which sends messages in MESSAGE QUEUE.
Now Is it possinle to receive messages from JMS Queue by creating business service in Aqualogic Service bus???

Hi dear,
<br>
I am sending Message through Serializable Object.
<br>
I have JMS Proxy which gets invoked when i send message to JMs Queue. JMS Proxy then calls business service.
<br>
<br>
Business Service has two functions. One is taking String as input and one is taking Serializable Object as Input.
<br>
<br>
public void recieveString(String str)<br>
public void recieveObject(Trade obj)<br>
--------------------------------------------------<br>
Now I have configured Proxy Services' Request and Response
Message Type as a "TEXT". and I am sending ObjectMessage here so what kind of change I require.
<BR>
I also want to configure my proxy so that if JMS queue recieves TextMessage then it should invoke reciveString() function and if Object Message then vice versa.....
<BR><BR>
But i am not able to handle object even...
When I am sending Object Message it takes as a TextMessage.
I am getting following exception when I am sending Object Message to JMS QUEUE. Request and Response Message types are XML Schema of that object.
<BR>
<BR>
<Nov 30, 2006 4:57:19 PM IST> <Warning> <EJB> <BEA-010065>
<BR>
<MessageDrivenBean threw an Exception in onMessage(). The exception was: java.lang.AssertionError.<BR>
java.lang.AssertionError at com.bea.wli.sb.transports.jms.JmsInboundMDB.onMessage(JmsInboundMDB.j
ava:112)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:42
9)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDL
istener.java:335)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:
291)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4060)
Truncated. see log file for complete stacktrace
>
Message was edited by:
alwaysvaghu

How to read message from JMS queue as a ByteMessage

Hi,
i want to browse a xml message from a JMS queue(in Weblogic 8.1) as a ByteMessage instance and then need to put it into byte array .
Then i want to read each byte by byte from that array.
Can any one please help me to solve it.
(i am using java language in the program to browse message from a queue).
Thanks in advance.
Regards,
Deba

You can refer to the following link for the detailed steps :-
Link :[http://www.informit.com/articles/article.aspx?p=170722&seqNum=3]

How to Read Message from JMS Queue using Business Service(ALSB3.0)

Hi,
My Project Set up is as follows(using ALSB3.0).
1>One Proxy Service with transport as HTTP.
2>The Proxy service is calling another Business Service.
3>The Business Service has transport layer as JMS.
So here the business service is posting Request Message into the JMS queue.
I want at the same time it(The Business Service) should listen to another queue and from there it should read Response Message and forward back to the caller proxy service.
Can any one help me regarding this...
Thanks in advance...
Deba

Hi ,
Problem in : Reading / writing messages to the JMS Queue -
I am stuck with the same problem and I am not able to proceed futher, Can you please help me out in sending an example of how to do right configurations in ALSB and on the server. I read the documentation but still I dont see messages in the queues.
please help me out. can you post a small sample example
thanks
adi

I want to use ODI to read XML messages from JMS queue and then process it..

I want to use oracle ODI (Oracle Data Integrator) to read XML messages from JMS queue and then process it.. i also want to process and validate the data in it....
Could anyone please tell me the steps to achieve the same. I tried some ways which i got on OTN, but not able to implement it exactly...
As i m very new to ODI, it will be great if you provide detailed steps..
Thanks in advance for your help....

Hi,
Were you able to do it? We are facing this same issue now and, despite the fact the docs say otherwise, it does not seem to be a trivial task.
TIA,
Tedi

How to read Java Object message from JMS Queue using JMS Adapter .

Dear All,
In my scenario i have to read a java object message from JMS Queue . I tried by using the JMS Adaper ,but i am not getting any Payload . Can any one tell me is there any special settings for JMS Adapter to read the Java Object message .
I am able to read the Message successfully thru JMS Adapter but in SXMB_MONI it is not showing any payload .
I also went in Message monitoring but i am getting this type of message in Sender JMS Adapter in Audit Log.
JMS Message ID XXXXX Message Type Null unknown.Payload can not be read and will be empty.
JMS Message ID XXXXX Payload Empty can not read.
Please Help.
Lateef

Hi,
As far as i know, JMS Object Messages is not supported by XI JMS adapter.
you need to have the JMS provider to transform the message to bytes messages.
(Refer to SAP note 856346)

How to get the XML messages from JMS Queue in BPM

I have one requirement in my application.we are sending XML messages to the JMS Queue.How to get the XML messages from JMS Queue and how to Extract the details from XMl.
can you please send me the code to get the XML messages from the JMS Queue.
Thank you,

Hi,
Sure others will have some other ideas, but here's what I typically do to get the XML from a JMS queue. Inside the Global Automatic that pops the messages off the queue you'd have logic similar to this:
artifactInfoNodes as Any[]
xmlObject as Fuego.Xml.XMLObject = XMLObject()
load xmlObject using xmlText = message.textValue
. . . Once you have this, it's a matter of deciding what you want to do with the message. Most times you'll parse the XML (using XPATH statemens), set argument variables and create a work item instance.
Hope this helps,
Dan

Reading message from two queues and sort according the time stamp

Hi
I have a requirement where i have to read the message from two queue .. and sort according the Time stamp ( Field in payload ) and send it ot the Webservice ..
How i acheive using the BPM..
in the BPM i have to collect the message for every 20 sec ... and then sort it tout ...
S V

Do you mean from two sender? What do you exactly mean by "reading from two queues"?
Regards,
Prateek

Weblogic 10.3 Not Removing Expired Messages from JMS Queues

Dear All,
We have an application that is running on Weblogic 10.3.
This application (let us call this application Y) receives messages on a JMS queue. These messages are placed on the queue by another application (let us call this application X). We would like to have these messages expire within a certain amount of time (i.e. 90000 ms) if they are not consumed.
Now when application X places the messages onto the queue for application Y to consume, the JMS producer sets the time to live to 90000 ms. We can see that expiration time has been set appropriately in the weblogic console. If a message sits on the queue for longer than 90000 ms the state string of the message is changed to "receive expired". What we don't understand is why the expired messages still end up being consumed from the queue.
We understand that Weblogic is supposed to have an 'Active Message Expiration' thread that will remove expired messages from the queue. The Expiration Scan Interval for the JMS Server is set to 30 (seconds).
Can anyone tell us why our expired messages don't seem to be deleted from the queues?
Tim

Thank you for the response Rene.
We have set up both the active expiration scan and the message expiration policy. The active expiration scan is set for every 30 seconds. The message expiration policy is set to "discard". However, the expired messages are still being consumed. Is it possible we are doing something wrong? See a portion of our configuration files below.
We have set up the expiration scan time interval. See a portion of our config.xml below:
<jms-server>
<name>brokerJMSServer</name>
<target>AdminServer</target>
<persistent-store xsi:nil="true"></persistent-store>
<store-enabled>true</store-enabled>
<allows-persistent-downgrade>false</allows-persistent-downgrade>
<hosting-temporary-destinations>true</hosting-temporary-destinations>
<temporary-template-resource xsi:nil="true"></temporary-template-resource>
<temporary-template-name xsi:nil="true"></temporary-template-name>
<message-buffer-size>-1</message-buffer-size>
*<expiration-scan-interval>30</expiration-scan-interval>*
<production-paused-at-startup>false</production-paused-at-startup>
<insertion-paused-at-startup>false</insertion-paused-at-startup>
<consumption-paused-at-startup>false</consumption-paused-at-startup>
</jms-server>
<jms-system-resource>
<name>broker-jms</name>
<target>AdminServer</target>
<sub-deployment>
<name>EhrBrokerRequestQueue</name>
<target>brokerJMSServer</target>
</sub-deployment>
<descriptor-file-name>jms/broker-jms.xml</descriptor-file-name>
</jms-system-resource>
<admin-server-name>AdminServer</admin-server-name>
We have set up the message expiration policy in our jms descriptor. See a portion below:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-jms http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
<queue name="EhrBrokerRequestQueue">
<delivery-params-overrides>
<redelivery-delay>-1</redelivery-delay>
</delivery-params-overrides>
<delivery-failure-params>
<redelivery-limit>-1</redelivery-limit>
*<expiration-policy>Discard</expiration-policy>*
</delivery-failure-params>
<jndi-name>EhrBrokerRequestQueue</jndi-name>
</queue>
</weblogic-jms>
What could we be doing wrong?
Kind Regards,
Tim

Pulling message from JMS queue

Hi,
I'm looking to pull messages from a JMS queue and have tried setting up a Business Service that doesn't send a request but only expects a response. Doesn't seem to work, I'm unable to pull messages from a queue (I don't want to set up a Proxy Service that listens) - is there a standard way of doing this in ALSB?
Thanks.

This is not a supported feature. The best solution is to write a java callout to pull the message from the queue.
Gregory Haardt
ALSB Prg. Manager
[email protected]
Edited by ghaardt at 09/11/2007 4:00 PM

Facing error when trying to read message from MQ through B2B

Hi,
I'm trying to read the messages from MQ through B2B.
I have created a listening channel in B2B console.
Also place the required jar files in the Domain_Dir/lib folder.For your reference the jar files are given below,
a. com.ibm.mqjms.jar
b. dhbcore.jar
c. com.ibm.mq.jar
d. com.ibm.mq.jmqi.jar
e. mqcontext.jar
g. com.ibm.mq.commonservices.jar
h. com.ibm.mq.headers.jar
i. com.ibm.mq.pcf.jar
But i'm encounter the below error while reading the MQ. Pls let me know if i'm missing something.
####<Oct 9, 2014 4:00:03 PM IST> <Error> <oracle.soa.b2b.engine> <ULCAKESBTD1P> <b2b-server> <Workmanager: , Version: 0, Scheduled=false, Started=false, Wait time: 0 ms
> <<anonymous>> <> <0000KZoSn1y5YbWzLwyGOA1KDaCI000002> <1412850603388> <BEA-000000> <oracle.tip.b2b.transport.TransportException: [JMS_CONN_INVALID] JMS connection error.
at oracle.tip.b2b.transport.TransportException.create(TransportException.java:93)
at oracle.tip.b2b.transport.basic.jms.JMSMonitor.init(JMSMonitor.java:199)
at oracle.tip.b2b.transport.basic.jms.JMSMonitor.<init>(JMSMonitor.java:181)
at oracle.tip.b2b.transport.basic.JMSReceiver.init(JMSReceiver.java:266)
at oracle.tip.b2b.transport.b2b.B2BTransport.init(B2BTransport.java:577)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:240)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: oracle.tip.b2b.transport.TransportException: [JMS_CONN_FAC_NOT_FOUND] JMS_CONN_FAC_NOT_FOUND
at oracle.tip.b2b.transport.TransportException.create(TransportException.java:78)
at oracle.tip.b2b.transport.basic.jms.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:208)
at oracle.tip.b2b.transport.basic.jms.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConnectionFactoryFactory.java:85)
at oracle.tip.b2b.transport.basic.jms.JMSConnection.<init>(JMSConnection.java:136)
at oracle.tip.b2b.transport.basic.jms.JMSMonitor.init(JMSMonitor.java:195)
... 7 more
Caused by: java.lang.ClassNotFoundException: QMUL.PDT
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at oracle.tip.b2b.transport.basic.jms.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:162)
... 10 more
oracle.tip.b2b.transport.TransportException: [JMS_CONN_INVALID] JMS connection error.
at oracle.tip.b2b.transport.TransportException.create(TransportException.java:93)
at oracle.tip.b2b.transport.basic.jms.JMSMonitor.init(JMSMonitor.java:199)
at oracle.tip.b2b.transport.basic.jms.JMSMonitor.<init>(JMSMonitor.java:181)
at oracle.tip.b2b.transport.basic.JMSReceiver.init(JMSReceiver.java:266)
at oracle.tip.b2b.transport.b2b.B2BTransport.init(B2BTransport.java:577)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:240)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused By: oracle.tip.b2b.transport.TransportException: [JMS_CONN_FAC_NOT_FOUND] JMS_CONN_FAC_NOT_FOUND
at oracle.tip.b2b.transport.TransportException.create(TransportException.java:78)
at oracle.tip.b2b.transport.basic.jms.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:208)
at oracle.tip.b2b.transport.basic.jms.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConnectionFactoryFactory.java:85)
at oracle.tip.b2b.transport.basic.jms.JMSConnection.<init>(JMSConnection.java:136)
at oracle.tip.b2b.transport.basic.jms.JMSMonitor.init(JMSMonitor.java:195)
at oracle.tip.b2b.transport.basic.jms.JMSMonitor.<init>(JMSMonitor.java:181)
at oracle.tip.b2b.transport.basic.JMSReceiver.init(JMSReceiver.java:266)
at oracle.tip.b2b.transport.b2b.B2BTransport.init(B2BTransport.java:577)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:240)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused By: java.lang.ClassNotFoundException: QMUL.PDT
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:190)
at oracle.tip.b2b.transport.basic.jms.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:162)
at oracle.tip.b2b.transport.basic.jms.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConnectionFactoryFactory.java:85)
at oracle.tip.b2b.transport.basic.jms.JMSConnection.<init>(JMSConnection.java:136)
at oracle.tip.b2b.transport.basic.jms.JMSMonitor.init(JMSMonitor.java:195)
at oracle.tip.b2b.transport.basic.jms.JMSMonitor.<init>(JMSMonitor.java:181)
at oracle.tip.b2b.transport.basic.JMSReceiver.init(JMSReceiver.java:266)
at oracle.tip.b2b.transport.b2b.B2BTransport.init(B2BTransport.java:577)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:240)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
>
####<Oct 9, 2014 4:00:20 PM IST> <Warning> <oracle.adfinternal.view.faces.partition.FeatureUtils> <ULCAKESBTD1P> <b2b-server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KZoSn1y5YbWzLwyGOA1KDaCI000002> <1412850620868> <ADF_FACES-30130> <Ignoring feature-dependency on feature "AdfDvtCommon". No such feature exists.>
####<Oct 9, 2014 4:00:21 PM IST> <Warning> <org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl> <ULCAKESBTD1P> <b2b-server> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <0000KZoSn1y5YbWzLwyGOA1KDaCI000002> <1412850621197> <BEA-000000> <Configurator services already initialized.>
####<Oct 9, 2014 4:00:30 PM IST> <Notice> <Log Management> <ULCAKESBTD1P> <b2b-server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1412850630361> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
####<Oct 9, 2014 4:00:30 PM IST> <Notice> <WebLogicServer> <ULCAKESBTD1P> <b2b-server> <main> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac6> <1412850630614> <BEA-000365> <Server state changed to ADMIN>
####<Oct 9, 2014 4:00:30 PM IST> <Notice> <WebLogicServer> <ULCAKESBTD1P> <b2b-server> <main> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac6> <1412850630698> <BEA-000365> <Server state changed to RESUMING>
####<Oct 9, 2014 4:00:31 PM IST> <Notice> <Server> <ULCAKESBTD1P> <b2b-server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac8> <1412850631051> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:214:4fff:feeb:478d:7003 for protocols iiop, t3, ldap, snmp, http.>
####<Oct 9, 2014 4:00:31 PM IST> <Notice> <Server> <ULCAKESBTD1P> <b2b-server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac8> <1412850631051> <BEA-002613> <Channel "Default[1]" is now listening on 10.236.77.12:7003 for protocols iiop, t3, ldap, snmp, http.>
####<Oct 9, 2014 4:00:31 PM IST> <Notice> <Server> <ULCAKESBTD1P> <b2b-server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac8> <1412850631052> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:214:4fff:feeb:478c:7003 for protocols iiop, t3, ldap, snmp, http.>
####<Oct 9, 2014 4:00:31 PM IST> <Notice> <Server> <ULCAKESBTD1P> <b2b-server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac8> <1412850631053> <BEA-002613> <Channel "Default[4]" is now listening on 127.0.0.1:7003 for protocols iiop, t3, ldap, snmp, http.>
####<Oct 9, 2014 4:00:31 PM IST> <Notice> <Server> <ULCAKESBTD1P> <b2b-server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac8> <1412850631053> <BEA-002613> <Channel "Default" is now listening on 192.168.107.97:7003 for protocols iiop, t3, ldap, snmp, http.>
####<Oct 9, 2014 4:00:31 PM IST> <Notice> <Server> <ULCAKESBTD1P> <b2b-server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac8> <1412850631054> <BEA-002613> <Channel "Default[5]" is now listening on 0:0:0:0:0:0:0:1:7003 for protocols iiop, t3, ldap, snmp, http.>
####<Oct 9, 2014 4:00:31 PM IST> <Notice> <WebLogicServer> <ULCAKESBTD1P> <b2b-server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac8> <1412850631055> <BEA-000332> <Started WebLogic Managed Server "b2b-server" for domain "b2b-domain" running in Development Mode>
####<Oct 9, 2014 4:00:32 PM IST> <Notice> <WebLogicServer> <ULCAKESBTD1P> <b2b-server> <main> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac6> <1412850632557> <BEA-000365> <Server state changed to RUNNING>
####<Oct 9, 2014 4:00:32 PM IST> <Notice> <WebLogicServer> <ULCAKESBTD1P> <b2b-server> <main> <<WLS Kernel>> <> <308025e28c55d051:50252314:148f4730231:-8000-0000000000007ac6> <1412850632559> <BEA-000360> <Server started in RUNNING mode>
####<Oct 9, 2014 4:00:38 PM IST> <Warning> <oracle.soa.services.notification> <ULCAKESBTD1P> <b2b-server> <TimerFactory> <<anonymous>> <> <0000KZoSn1y5YbWzLwyGOA1KDaCI000002> <1412850638612> <BEA-000000> <<.> Notification via email, voice, SMS or IM will not be sent. If you would like to enable them, please configure corresponding sdpmessaging driver. Then modify the accounts and set NotificationMode attribute to either NONE, EMAIL or ALL in workflow-notification-config.xml>
####<Oct 9, 2014 4:02:41 PM IST> <Warning> <Socket> <ULCAKESBTD1P> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <a2e657fa9e6b5d11:789eb8cc:148f4403946:-8000-00000000000029c4> <1412850761335> <BEA-000449> <Closing socket as no data read from it on 192.168.96.66:29,963 during the configured idle timeout of 5 secs>
####<Oct 9, 2014 4:02:51 PM IST> <Warning> <Socket> <ULCAKESBTD1P> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <a2e657fa9e6b5d11:789eb8cc:148f4403946:-8000-00000000000029d2> <1412850771337> <BEA-000449> <Closing socket as no data read from it on 192.168.96.66:29,970 during the configured idle timeout of 5 secs>
####<Oct 9, 2014 4:03:16 PM IST> <Warning> <Socket> <ULCAKESBTD1P> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <a2e657fa9e6b5d11:789eb8cc:148f4403946:-8000-00000000000029f4> <1412850796335> <BEA-000449> <Closing socket as no data read from it on 192.168.96.66:29,984 during the configured idle timeout of 5 secs>
Thanks,
Ravindra.

Hi Ravindra,
Which mode of connectivity are you trying (credential based / .bindings based)
MQ connectivity support is provided via JMS offering of Oracle B2B. This blog post will provide you the steps for the same - https://blogs.oracle.com/oracleb2bgurus/entry/b2b_communication_using_ibm_mq
Please ensure to provide the proper values for connection factory and other details in JMS configuration in B2B
HTH

Exception in OSM 7.0 when XSLT Automator received message from JMS

Hi
I have been prototyping on OSM 7.0 on Linux. I have a simple project, with two "Automated tasks" and some manual tasks.
The first Automated task is using a XSLT Sender, and sends a message to a JSM queue "A".
The second Automated task is using a XSLT Automator to listen for a JMS message received from an external system in JMS queue "B".
I have setup a JMS bridge on the WebLogic server where OMS is running, so that messages in queue "A" are forwared to queue "B".
So I am seeing messages being sent to queue A and then forwarded to queue B.
However, I keep getting exceptions when OSM is trying to process the messages received at queue B.
It complains about "ORA-20503: no current hist_seq_id found for given automation context.".
Does anybody know what this means ?
At first I thought it might be the "JMSCorrelationId" for the message which arrived at queue B which was wrong, but that does not seem to be the case, because if I sent a dummy message with a dummy JMS correlation id, then I get another exception : "ORA-20502: Automation context not found.". This exception is ok, and I understand the reason for it.
Here are som excerpts from the log file for the "no current hist_seq_id found" case :
com.mslv.oms.dataaccesslayer.ProxyException: ORA-20503: no current hist_seq_id found for given automation context.
ORA-06512: at "ORDERMGMT.OM_AUTOMATION_PKG", line 27
ORA-06512: at "ORDERMGMT.OM_AUTOMATION_PKG", line 88
ORA-06512: at line 1
Nested Exception: ORA-20503: no current hist_seq_id found for given automation context.
ORA-06512: at "ORDERMGMT.OM_AUTOMATION_PKG", line 27
ORA-06512: at "ORDERMGMT.OM_AUTOMATION_PKG", line 88
ORA-06512: at line 1
Nested Exception: java.sql.SQLException: ORA-20503: no current hist_seq_id found for given automation context.
ORA-06512: at "ORDERMGMT.OM_AUTOMATION_PKG", line 27
ORA-06512: at "ORDERMGMT.OM_AUTOMATION_PKG", line 88
ORA-06512: at line 1
     at com.mslv.oms.dataaccesslayer.a.execute(Unknown Source)
     at com.mslv.oms.dataaccesslayer.CallableProxy.execute(Unknown Source)
     at com.mslv.oms.automation.plugin.AutomationDispatcherImpl.getClusterRequestContext(Unknown Source)
     at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.onMessage(Unknown Source)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
     Truncated. see log file for complete stacktrace
java.sql.SQLException: ORA-20503: no current hist_seq_id found for given automation context.
ORA-06512: at "ORDERMGMT.OM_AUTOMATION_PKG", line 27
ORA-06512: at "ORDERMGMT.OM_AUTOMATION_PKG", line 88
ORA-06512: at line 1
     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
     Truncated. see log file for complete stacktrace
<11-Feb-2010 12:32:05,954 CET PM> <ERROR> <message.ClusterMessageHandlerBean> <ExecuteThread: '12' for queue: 'oms.automation'> <Failed to process cluster request due to ClusterRequestContext = NULL>
<Feb 11, 2010 12:32:05 PM CET> <Error> <oms> <BEA-000000> <message.ClusterMessageHandlerBean: Failed to process cluster request due to ClusterRequestContext = NULL>
<Feb 11, 2010 12:32:06 PM CET> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
java.lang.RuntimeException: No transaction associated with request.
java.lang.RuntimeException: No transaction associated with request
     at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.onMessage(Unknown Source)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
     at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
     Truncated. see log file for complete stacktrace
Regards
Alf Hogemark
Edited by: user494649 on 11.feb.2010 04:26
Edited by: user494649 on 11.feb.2010 04:27

Hi,
I am trying to send message using XSLT sender for an automated task from osm 6.3.1 to ASAP 7.0, and also raised a request "Unable to deploy ATM/FrameRelay plugins for OSM 6.3.1" as i am stuck with an error- Null pointer Exception. could you share how did u deploy and register the plugins for sending message on automated tasks?
i am using ant for deploying the catridge and plugins,
Also could you point me the reason for the error
Thanks in advance.

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

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

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

OC4J 9.0.4: Problem receiving message from JMS queue

I've created an application which puts XML files in a JMS queue and try to get it out again. The enqueing (sending) is no problem, but when I dequeue from the same queue I receive nothing and if I don't specify a wait time the programs hangs.
If I create a QueueBrowser I can see there are messages in the queue.
Can someone tell me what I do wrong?
Here is the code of my dequeue action:
public String dequeue(int qName) throws RbsSysException
        final String method = "dequeue(int qName)";
        _log.debug(method);
        QueueConnection queueConnection = null;
        try
            queueConnection = _queueConnectionFactory.createQueueConnection();
            QueueSession queueSession = queueConnection.createQueueSession(false,
                    Session.AUTO_ACKNOWLEDGE);
            QueueReceiver queueRcv = queueSession.createReceiver(getQueue(qName));
            _log.debug("queue = "+ queueRcv.getQueue().getQueueName());
            // Due to bug 3376983 in OC4J We cannot use TextMessage if it exceeds
            // 64 kb. Therefore use ObjectMessage.
            Message msg = queueRcv.receiveNoWait();
            _log.debug("msg = " + msg);
            ObjectMessage objMsg = (ObjectMessage)msg;
            //ObjectMessage objMsg = (ObjectMessage) queueRcv.receiveNoWait();
            _log.debug("objMsg = " + objMsg);
            if (objMsg != null)
                return (String) objMsg.getObject();
            else
                return null;
        catch (JMSException je)
            throw new RbsSysException(je);
        finally
            if (queueConnection != null)
                try
                    queueConnection.close();
                catch (Exception any)
                    _log.error("Error while closing QueueConnection: ", any);
    }

Did you implement javax.jms.MessageListener and the method onMessage(Message)?
If you use onMessage() as wel as receive (or receiveNoWait() or receive(long)), the onMessage() can be called, while the main thread is blocking on a synchronous receive, so make sure you use only one of the two methods: onMessage() or receive.
Receive() blocks your thread until a message is published. So your program 'hangs' by design. Usually this is used when your program is waiting for a particular message. Otherwise use onMessage().
ReceiveNoWait() checks if something is in the queue at that very moment, so if nothing is there (yet), the main thread continues.
Hope this helps,
Lonneke

BAM EMS to read payload from JMS queue in remote weblogic domain

Hi ,
I am trying to connect to JMS queue located in different web logic domain using oracle BAM EMS configuration. But my EMS configuration is not able to start .
Please find below details,
Name:
OSBBAM_EMSProcessor
Owner:
XXXXX
Created:
9/23/2014 12:05:21 AM
Last modified:
9/24/2014 10:58:58 PM
Status:
Test failed - BAM-00553: Resources start operation for destination jms/OSBBAM_EMSQ failed.
Initial Context Factory:
weblogic.jndi.WLInitialContextFactory.
JNDI Service Provider URL:
t3://xx.xxx.xx.xx.:xxxx.
Topic/Queue Connection Factory Name:
jms/osbConnectionFactory.
Topic/Queue Name:
jms/OSBBAM_EMSQ.
JNDI Username:
XXXX
JNDI Password:
XXXXXXX
JMS Message Type:
TextMessage.
Durable Subscriber Name (Optional):
Message Selector (Optional):
Data Object Name:
/BAMPOC/BAM_AuditTable.
Operation:
Insert.
Batching:
No.
Transaction:
No.
Start when BAM Server starts:
Yes.
JMS Username (Optional):
JMS Password (Optional):
Can any one guide me how to proceed with that?I have already tried with trusted setup in WLS and foreign server but It did not work.

You can refer to the following link for the detailed steps :-
Link :[http://www.informit.com/articles/article.aspx?p=170722&seqNum=3]

Debatching is possible when we are reading messages from JMS queue

Similar Messages

Maybe you are looking for