Issue in OSB publishing message to openJMS Queue

I am trying to post a message from OSB to openJMS Queue. I am able to post message to openJMSQueue using Java API.
I have created a Foreign Server and then a foreign connection factory.
I am able to see the connection factory in the JNDI Tree as below.
Binding Name:localConnectionFactory
Class:org.exolab.jms.client.JmsConnectionFactory
Hash Code:18168258
toString Results:org.exolab.jms.client.JmsConnectionFactory@11539c2I have used the below URL in business service..
jms://localhost:17000/localConnectionFactory/openJMSQueueBut i am getting error as :
<Aug 22, 2012 11:28:19 AM IST> <Warning> <WliSbTransports> <BEA-381508> <Failed to check whether connection factory localConnectionFactory supports XA. Will assume it does not: javax.naming.NoInitialC
ontextException: Cannot instantiate class: org.exolab.jms.jndi.InitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.exolab.jms.jndi.InitialContextFactory]
javax.naming.NoInitialContextException: Cannot instantiate class: org.exolab.jms.jndi.InitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.exolab.jms.jndi.InitialContextFacto
ry]
        at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
        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 weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:190)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: org.exolab.jms.jndi.InitialContextFactory
        at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
        at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
        at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
        Truncated. see log file for complete stacktrace
>
<Aug 22, 2012 11:28:19 AM IST> <Warning> <JMSPool> <BEA-169807> <There was an error while making the initial connection to the JMS resource named ALSB_JMS_SessionPool_1449855884 from within an EJB or
a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [JMSPool:169803]JNDI lookup of the JMS connection factory localConnectionFactory failed: javax.nami
ng.NoInitialContextException: Cannot instantiate class: org.exolab.jms.jndi.InitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.exolab.jms.jndi.InitialContextFactory]>I have placed all the JARS of openJMS in the lib directory. The Jars are :
castor-0.9.5.jar
concurrent-1.3.4.jar
openjms-0.7.7-beta-1.jar
openjms-common-0.7.7-beta-1.jar
openjms-net-0.7.7-beta-1.jar
openjms-tools-0.7.7-beta-1.jar
spice-jndikit-1.2.jarAny help on this would be much appreciated. My first try on foreign JMS provider connection.
Regards
Sesha

I think you have to add the jars on the CLASSPATH in setDomainEnv.sh(cmd) file...
It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts)
https://forums.oracle.com/forums/ann.jspa?annID=893

Similar Messages

Publishing message to JMS Queue on Weblogic from OSB proxy service

Hi,
1. I have created a JMS module: testModule and a JMS queue: testQueue in the weblogic admin console.
2. Created a business service with the above queue as endpoint.
3. Created a proxy service which publishes the message to the queue using the business service. I have used Publish activity to publish the message to the business service.
When i run the proxy service with the request message, then, no error is coming but, in the admin console when i click on JMS module->testModule->testQueue->Monitoring tab, i see nothing. There are no entries in the table so, how can i check if the message is properly published to the queue or not.
The queue is not listened by any service for consuming the messages.
Kindly help me in figuring out this issue.
Thanks in advance.

If the destination was a topic, the behavior would be expected. Messages only stays on a topic and are delivered to consumers if there are consumers or durable subscribers.
Did you check the server logs and see if there are any exceptions or warnings?
You can also turn on jms debugging by adding the following to your server startup script.
-Dweblogic.debug.DebugJMSFrontEnd=true
-Dweblogic.debug.DebugJMSBackEnd=true
The debugging messages wiill show up in the server log.

OSB publish action and error queue

Hello there,
where in case of poisened messages, the "publish" action, routes the messages.
I have one proxy which, along its pipeline, publish a message to another proxy and then carry on. Well, I guess this is done some how with internal OSB queues, where in case of error these messages are moved? Is there anyway to specify a specific destination?
Thanks in advance

If there is an error in your proxy service and you want push the messages to the queue you have to handle it manually through error handler. In case of publish if you want to handle the messages you have use routing options and change the quality of service and then in the error handler publish the message to the required queue.
Edited by: 988445 on Mar 18, 2013 6:20 PM

QoS issue with OSB publish to JMS business service

Hi,
1. I have a http OSB proxy service which is publishing an audit message to a JMS queue through OSB business service.
MainProxyService (http) --> Publish (best-effort) --> AuditBusinessService (JMS) --> Audit Queue
2. I want 'Publish to JMS business service' to be a non-blocking call so that proxy service message flow can continue. Transaction support is disabled in proxy service as well as in JMS connection factory.
3. As default value of QoS (quality of service) for publish action is best-effort, ideally proxy service should continue its message flow immediately after dispatching the message to publish action and it should not block the main proxy flow.
4. But in my case, proxy service is blocking the message flow until the message is delivered to JMS business service/JMS queue. This is degrading performance of my application.
5. I think default 'best-effort' QoS is not working with JMS business service as there is a significant time lag between publish action and its next subsequent action.
6. If I replace the JMS business service with HTTP business service, then it seems to be a non-blocking call and message flow immediately proceeds to next actions.
Correct me if I am going wrong anywhere or my understanding is wrong.
Many thanks.

HI,
u can use Conditional Branching
http://docs.oracle.com/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageflow.html#wp1061670
Split join would be used in case u need to split your request and call your Business Service in Serial/parallel & then gather resposnes from multiple callouts to have single response
http://docs.oracle.com/cd/E13159_01/osb/docs10gr3/userguide/splitjoin.html#wp1137258
Abhinav

OSB:Publish to business service with for each in osb proxy message flow

Hi,
I have an external application that will make a call to my web-service and post a message to my queue "A" and i need to model my osb component such that it picks the message from that queue " A"and posts it to another queue "B". All this is done without any BPEL involved.
for publishing the message i have created a business service that publishes a msg to the queue A and my proxy service is modelled such that it subscribes to this same queue A and publishes the msg to another business service (that posts it to a queue B).
Everything is working fine but i have an issue in modelling my proxy message flow. If an external application sends a bulk msg i need to post the message one by one to my queue B. I have used for-each and Publish to BS but the msg doesn't get posted one by one. i know i am missing something please help me out.
SOA Suite Version - 11.1.1.3

Are you sure that your for-each definition is correct? Does the flow within the for-each get executed multiple times?
You can check this by logging the variable to which you assign the message in the for-each. Don't forget to put the log level to Error, so you're sure that it's logged.
Let's say you get a list of persons like the following xml in a variable personList
<Persons>
<Person>Glenn</Person>
<Person>Prasanth</Person>
</Persons>
Your for-each definition should be the following.
For each variable: person
XPath: +./Person+
In Variable: personList
You don't mention the Persons element in the XPath expression since it is the root element of the XML. The root element is represented by . (dot).
In the for-each, the variable person can be used like any other variable.

Need to publish message from database to a JMS Queue using Java

I need to publish messages to a Websphere JMS Queue whenever any changes happen on a particular column of a table in oracle 11g. For that I have written a trigger on that particular table which in turn will invoke one java procedure. I have written the java procedure using a standalone java class and uploaded the java class as a schema object. While executing the procedure it is throwing error as it is not able to instantiate some of the java classes. I don't know how to provide the reference of different jar files while executing the java class. Can anyone help me on this.

Welcome to the forum!
>
I have written the java procedure using a standalone java class and uploaded the java class as a schema object. While executing the procedure it is throwing error as it is not able to instantiate some of the java classes. I don't know how to provide the reference of different jar files while executing the java class.
>
Clarify your statement. First you say 'standalone java class' but then you talk about instantiating java 'classes' and referencing 'different jar files'. If you are executing your Java class inside Oracle then any Java classes that your java class is referencing also have to be loaded into Oracle or it won't be able to reference or execute them.
How do you plan to ' publish messages to a Websphere JMS Queue '? Where is this queue you are talking about?
Why are you using a Java procedure and class instead of PL/SQL?
What is your 4 digit Oracle version (result of SELECT * FROM V$VERSION)?

A bug in message pattern's queue implementation?

Here is how to reproduce the problem.
Have 2 Java program ready.
A is to create a queue and publish 3 messages to the queue.
B is to subscribe to the same queue and try to get all messages from the queue (put the getMessage inside a while(true) loop) then wait for new message.
Step 1. Run A, which put 3 messages into queue.
Step 2. Run B, which get 3 messages out of the queue then waiting on the getMessage() blocking call.
Step 3. Kill program B without unsubscribe() call.
Step 4. Run A, which put 3 messages into the queue again.
Step 5. Run B, this time it only get 2 messages. The 1st message A put in on Step 4 got lost.
Actually, if you run Step 2 multiple times before step 3, you will lost more message. It seems each time when there is a subscription created without a unsubscribe(), it will get one message lost.
I know the propery way is to call unsubscribe(), but the JVM could be killed thus won't have time to do cleanup.

Using message pattern 2.3, command pattern 2.3 and common 1.3
Coherence version is 3.4.2.
BTW, if the unit test program you mentioned is the MessageTests.java included in the src zip file, you won't be able to test this issue.
All unit test inside the MessageTests.java are comsuming exactly number of messages been published then do unscribe() call.
In order to reproduce this issue, you'd need to put your consumer JVM in a blocking getMessage() state (i.e. call getMessage() while there is no message in queue)
then kill the JVM. The unit test codes in MessageTests.java never enter blocking wait state when call getMessage().
Example code -
For the one putting message
MessagingSession messagingSession = DefaultMessagingSession.getInstance();
Identifier topicIdentifier = messagingSession.createQueue("test-queue");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY1");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY2");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY3");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY5");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY1");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY2");
messagingSession.publishMessage(topicIdentifier, "Hello WorldY3");
For the one getting message
MessagingSession messagingSession = DefaultMessagingSession.getInstance();
Identifier topicIdentifier = messagingSession.createQueue("test-queue");
Subscriber subscriber = messagingSession.subscribe("test-queue");
while (true) {
String message = (String)subscriber.getMessage();
System.out.println(message);
}

Issues with BI publisher report in dashboard

Hello all,
I got some issues about BI publisher reports in a dashboard.
I use a dashboard prompt in combination with a BIP report.
1.) I don't want to see the publisher control bar in my dashboard. Now you can't view the report anymore after using the dashboard prompt. Because it says you have to press the view button which is on the publisher control bar.
So when I add the bar. Then I have first to press on go in the dashboard prompt and after that I have to press on view in the publisher control bar.
2.) When I open my dashboard I see a scroll bar in my BIP report. Now when I use the dashboard prompt, it disappears. So I can't view the entire report anymore
3.) I like to develop in english, but the test must be in dutch. Now I have a english dashboard with a dutch control bar. Also logging in to BIP in english and then navigating to analytics will not help.
4.) I can't use I-bots on BI publisher reports, or can I?
5.) This is not really an issue, but more like a problem but I want that users can view the BIP report on the dashboard only in HTML, but I want that they only can export to excel, is this possible?
Hoping for some answers ;)
Thanks in advance!
Message was edited by:
Remc0

Hi Venkat,
Thanks for your quick respond.
1.) Auto Run is enabled. And the report runs automatically as well. But then it ignores the dashboard prompt (as a regular report would do as well). But when I choose some values in the prompt and then press go. Then it says I have to press on view as well.
2.) no that is not the case. My report is so big that it always need a scroll bar ;) also adjusting the size settings in the dashboard doesn't help. The only occurs when viewing in HTML, when previewing in excel or RTF it all just work fine.
3.) true, but ow well this is the least importetant one ;) so if this doesn't work, than it doesn't work ;)
4.) Ok, I will have a look on that.
5.) I did enabled HTML and EXCEL outputs in my BIP report. But when the first point is working, then I don't want to see the control bar anymore and I want to have the output on the dashboard in HTML and then I want to build a button, or a link or something that exports the request to excel. Is that possible?

Error while trying to pick message from weblogic queue

Hi,
We are getting the following error while trying to connect to pick up a message from weblogic queue.
We are suing oracle soa suite 10.1.3.1 and weblogic 8.1
the bad part is that, this error is not documented anywhere and couldn't get much help on this.
Would appreciate any suggestions / pointers on this.
Let me know if any further information is required.
invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: file:/E:/product/10.1.3.1/OracleAS_4/bpel/domains/default/tmp/.bpel_OTOCBPELProcess_1.0_78fcf080ec2bd7495aebfb5373e76116.tmp/readmsg.wsdl [ Consume_Message_ptt::Consume_Message(opaque) ] - WSIF JCA Execute of operation 'Consume_Message' failed due to: ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
; nested exception is:
ORABPEL-12115
ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
---------------------------------------------------

Hi!
I am facing a similar issue, does someone have an idea ?
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
</part><part name="detail"><detail>null</detail>
</part><part name="summary"><summary>file:/opt/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_TestReceiveMessage_BPEL_1.0_e00fd88d454889b871183d0d92dc9f7d.tmp/plReceiveMessage.wsdl [ Consume_Message_ptt::Consume_Message(TestPushMessage_BPELProcessRequest) ] - WSIF JCA Execute of operation 'Consume_Message' failed due to: ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
; nested exception is:
ORABPEL-12115
ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
Please examine the log file to determine the problem.
</summary>
</part></remoteFault>
Thanks,
romain.

JMS messages stuck in queue in weblogic v923 cluster

Hi all,
Enviornment details:
In our pre-production weblogic v923 cluster enviornment with Oracle 10g database, there are 10 server boxes with 2 managed nodes running on each server box in linux enviornment.
There are 3 JMS queues and 1 error queue per managed node.
All the queues are durable and the persitence store is a database table. There is a single database table per single managed node.
High loads of JMS messages from client applications coming on each of the 3 JMS queue are processed by the cluster on daily basis.
The JMS messages that failed to be processed the very first time due to the application logic exceptions are put on error queue since the retry is set to zero on the non-error queue.
The application exceptions are logged to a database table for futher reference.
The falied messages from the error queue are read by spring based MDP and resent to the application for reprocessing.
If no application exceptions, the message will be persisted in a relational database; in the case of failures, MDP code puts the failed message back on to the error queue.
The auto_ack is true on the JMS message.
It is observed about less than 1% of the messages fail the original processing and are in error queue on daily basis.
99.9% of the time, the reprocessing of the messages from the error queue is a success.
Currently due to some obvious reasons, the system administrator stops a managed node when the disk is full and start a different managed node on the same server box. This approach will be stopped in the very near future so that all nodes on all servers are running at any point of time by making few enviornment changes.
Problem:
1a) Occasionally, it is observed that 1 - 4 JMS messages are stuck in the error queue. There are no signs of reprocessing as there are no application exceptions or the corresponing insert into the database. The JMS persistence store table still has the JMS message.
1b) It is observed that over time, the same JMS messages that were originally stuck on server 1's managed node A are no longer there but are found in a different node (say node B) on a different server box.
As far as I understand the JMS, a message could be in a Pending state if MDP (in my case) does not automatically send ACKNOWLEGMENT back due to an issue in the Spring Defaultlisternercontainer before calling MDP's onMessage(). I am not sure as what happens to that status over time).
It is also observed that the stuck messages content is not much different than the other messages that are processed fine.
Any pointers/input is highly appreciated.
Thanks in advance for your valuable input and time.

Off the top of my head, I can only think of two reasons why a message might move from node to node:
(A) An application is dequeueing them and enquening them elsewhere.
(B) The application is using distributed queues, and the distributed queue has been configured to enable "queue forwarding". The forwarding feature automatically moves messages from distributed queue members that have no consumers to members that do have consumers. Queue forwarding is sometimes enabled as a work-around to better enable MDP support of WL distributed destinations, unlike WebLogic MDBs, MDPs have no container logic to ensure that all members of a distributed destination are serviced by a consumer under all circumstances...
Regards,
Tom

Messages in Distributed Queue remain on one JMSServer in Cluster

Hi,
          the situation is as follows:
          We're having Distributed Queues on a two-Node server setup. A queue therefore exists two times, once on each JMSServer on each node.
          Forward-Delay has been set on the DistibutedQueue to value 1 second (we tested with values 0 and 10, too).
          External Java client (both cluster nodes in the provider_url for initialcontext) connects to the DistributedQueue and sends messages. In the weblogic console you can see these messages on the physical queue on the JMSServer, let's call it QueueA on NodeA.
          An external java process to consume messages (again both clusters nodes in the jndi-connection-string) is started to consume messages. Because of round-robin it sometimes get's connections to QueueB (part of same DistributedQueue as QueueA, but on the other node in the cluster).
          When connected to QueueB on NodeB no single message is received. You can even see in the weblogic console that QueueA on NodeA has zero consumers and 50 messages, QueueB on NodeB has zero messages but one consumer.
          When we restart the consumer java process and it randomly get's connected to QueueA on NodeA it consumes fine, as it should.
          Should'nt Forward-Delay do exactly this? Transport messages from QueueA on NodeA with zero consumers to QueueB on NodeB which actually has consumers?
          Any help would be appreciated.
          Axel van Lil

Hi,
          thanks for your answer. We opened a support case today for this issue... I don't know. Cluster seems to run fine, no warnings, no exceptions.
          The next step of this issue is the following (just to give an idea of our upcoming problems :-)
          External Java process listens on QueueA on NodeA (QueueA is part of a Distributed Queue). Currently receives all the messages located on that queue. We kill NodeA on that machine to simulate failover.
          The external process failovers immediately to NodeB (which is good! proven by netstat and debugger) but just doesn't receive messages even though there are messages in that queue! It seems that the new consumer is just being forgotten by the BEA server.
          I don't know... somehow our configuration is quirked... or the BEA implementation doesn't work at all...
          Rgds,
          Axel

Messages in inbound queue in status-RUNNING and it is too slow

Hi Experts,
We have a issue there are tons of messages in inbound queue in status-RUNNING and it is too slow!, hence there are more messages getting in the queue every minute.
This is Production enviorment.
We have priority queues
QIN is waiting status.
De-register will not work due to loss of messages fear
Please advice
thanks and regards,
krushi

Hi,
If the queues are hanging due to peak load at sometimes
you can schedule following reports to restart them automatically
(dont have to lock and unlock manually)
RSQIWKEX - Inbound Queues
RSQOWKEX- Outbound Queues
Also you can save the first entry of the queue if its causing problems to process later- smq3
thanks
francis

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

** Message being processed - Queue status green colour

Hi Friends,
Many messages in our SXMB_MONI shows green color in the queue id column. It shows 'Message being processed'. All messages are in queue, still they are not delivered. Processing takes more hours. These messages are not EOIO queue. While we check this thru SMQ1 and SMQ2 it shows 'Running'. So, what could be the problem ...?
Kindly help friends, to solve this issue. (Points rewarded for helpful answer)
Kind Regards,
Jeg P.

HI,
QUEUE STATUS RUNNING BASICALLY MEANS THT
The first LUW of this queue is currently being processed. If a queue in this status hangs for more than 30 minutes, this may mean that the work process responsible for processing this LUW has been terminated. In this case you can activate this queue again. Note that activating a queue in status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system at that time. We therefore recommend a waiting time of at least 30 minutes before you reactivate the queue.
HOPE THIS WILL SOLVE THE PROBLEM
PLZ REWARDS POINTS
VIKAS

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_

Issue in OSB publishing message to openJMS Queue

Similar Messages

Maybe you are looking for