Polling or JMS Message in Global Automatic

Hi,
I am currently working on a process which uses a Global Automatic activity to invoke a process instance. The process instance is invoked when the process receives some ticket information ( ticket id, type of ticket, customer name etc.) from an external application. This information is passed to the process using a web-service.
Now, I am confused whether to use JMS message or Polling by Interval inside of the Global Automatic acitivity to receive the message with the ticket information. Could anyone please suggest..
Also does anybody have an example of invoking a process instance after receiving a JMS message...?

HI!!!
In this URL of the Glorius bea.edocs.com, there is an example about working with JMS
http://egeneration.beasys.com/albsi/docs55/index.html

Similar Messages

Exception when begin process via Global Automatic JMS task

I have a process that works when I invoke it via a global creation task. However, when I try to invoke it automatically via a global automatic task listening to a JMS queue, I get the following exceptions and the instance fails.
An exception occurred while executing a transaction. Details:
java.lang.ClassNotFoundException: xobject.CandidateManagement.CandidateList$CandidatesGroup
java.lang.ClassNotFoundException: java.lang.ClassNotFoundException: xobject.CandidateManagement.CandidateList$CandidatesGroup
     at fuego.lang.JavaClass.loadClass(JavaClass.java:945)
     at fuego.lang.JavaClass.loadByJavaType(JavaClass.java:902)
     at fuego.lang.JavaClass.loadByJavaType(JavaClass.java:874)
     at fuego.lang.JavaClass.loadByJavaType(JavaClass.java:868)
     at fuego.lang.JavaClass.forName(JavaClass.java:271)
     at xobject.CandidateManagement.CandidateList.<init>(CandidateList.xcdl)
     at JMSPrototype3.ChooseCandidateCustomer.Default_1_0.Instance.<init>(Instance.xcdl)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at java.lang.Class.newInstance0(Unknown Source)
     at java.lang.Class.newInstance(Unknown Source)
     at fuego.server.execution.GlobalAutomaticJMSListeningHelper.executeJmsListener(GlobalAutomaticJMSListeningHelper.java:86)
     at fuego.server.AbstractProcessBean$42.execute(AbstractProcessBean.java:2771)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:302)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
     at fuego.server.AbstractProcessBean.runGlobalJmsActivity(AbstractProcessBean.java:2777)
     at fuego.server.execution.GlobalJMSExecutor$1.run(GlobalJMSExecutor.java:113)
     at fuego.component.Message.process(Message.java:578)
     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:772)
     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:747)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:143)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:135)
     at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:248)
     at fuego.component.ExecutionThread.work(ExecutionThread.java:831)
     at fuego.component.ExecutionThread.run(ExecutionThread.java:409)
Process execution engine execution error.
Caused by: java.lang.ClassNotFoundException: xobject.CandidateManagement.CandidateList$CandidatesGroup
fuego.papi.impl.EngineExecutionException: Process execution engine execution error.
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:139)
     at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
     at fuego.server.AbstractProcessBean.runGlobalJmsActivity(AbstractProcessBean.java:2777)
     at fuego.server.execution.GlobalJMSExecutor$1.run(GlobalJMSExecutor.java:113)
     at fuego.component.Message.process(Message.java:578)
     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:772)
     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:747)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:143)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:135)
     at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:248)
     at fuego.component.ExecutionThread.work(ExecutionThread.java:831)
     at fuego.component.ExecutionThread.run(ExecutionThread.java:409)
Caused by: java.lang.ClassNotFoundException: java.lang.ClassNotFoundException: xobject.CandidateManagement.CandidateList$CandidatesGroup
     at fuego.lang.JavaClass.loadClass(JavaClass.java:945)
     at fuego.lang.JavaClass.loadByJavaType(JavaClass.java:902)
     at fuego.lang.JavaClass.loadByJavaType(JavaClass.java:874)
     at fuego.lang.JavaClass.loadByJavaType(JavaClass.java:868)
     at fuego.lang.JavaClass.forName(JavaClass.java:271)
     at xobject.CandidateManagement.CandidateList.<init>(CandidateList.xcdl)
     at JMSPrototype3.ChooseCandidateCustomer.Default_1_0.Instance.<init>(Instance.xcdl)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at java.lang.Class.newInstance0(Unknown Source)
     at java.lang.Class.newInstance(Unknown Source)
     at fuego.server.execution.GlobalAutomaticJMSListeningHelper.executeJmsListener(GlobalAutomaticJMSListeningHelper.java:86)
     at fuego.server.AbstractProcessBean$42.execute(AbstractProcessBean.java:2771)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:302)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     ... 11 more

Hi,
Sure this is just my confusion, but if I'm reading this correctly, you're trying to use an instance variable in a Global Automatic.
If this is the case, I know this sounds odd, but you don't have access to instance variables inside a Global Automatic. You can create an instance inside the logic of one of these activities if you call the Fuego.Lib.ProcessInstance method "createInstance". For this method you'll notice that one of the parameters it expects is a Any[String]. You'll need to populate this hash table to set instance variable in the instance you're creating.
Hth,
Dan

Webservice vs JMS in Global Automatic

Hi all,
My client wants to automatically initiate a process after receiving some information from a web service. I have to use a Global Automatic activity to do so. I understand that the Global Automatic activity has an option to listen to an automatic JMS message and trigger/start/initiate the process..
But the global automatic activity has no option to trigger/start/initiate the process after receiving some information from a web service. Can this be done irrespective of whether the Global Automatic activity has the option or not? Or do I have to only use JMS message to trigger the process?
Edited by: user647659 on Aug 7, 2009 7:29 AM

But the global automatic activity has no option to trigger/start/initiate the process after receiving some information from a web service. Can this be done irrespective of whether the Global Automatic activity has the option or not? Or do I have to only use JMS message to trigger the process?To see how to create an instance from a Global Automatic (or any activity) using logic go to How to create Instace of another process from running process.
Dan

Why are my JMS messages automatically dequeued without consumer?

I created a simple in-memory JMS queue.
Now I wrote a BPEL process which writes (successfully ?) JMS message to this JMS queue.
Another consuming BPEL process is deployed but not started.
However I cannot see them in MBean JMSDestinationResource on the OC4J Enterprise Manager Web page.
When I tell the AppServer to browse all currently existing (and waiting) JMS message then there are none.
However the statistics for this queue show 17 messagesEnqueued and 17 messagesDequeued Messages.
It seems to me that my JMS messages are automatically dequeued. But why?
Are in-memory JMS messages not persistent (as long as the AppServer is up and running) ?
Do I have to set a certain preference to let JMS live in the Queue as long as they are not retrieved by another BPEL process?
Furthermore I tried the following:
I started a consuming BPEL process. Yes, he is waiting at the JMS adapter until a new JMS message arrive.
Then I send from the first BPEL process a JMS message. But even when consumption is possible the JMS message is dequeued and not forwarded to the consumer.
Why?
Peter

It seems to me that my JMS messages are automatically dequeued. But why?
This is how BPEL PM is designed; The activation-agent is running that belongs to the BPEL process. When a message arrives in a Queue or Table or File it is read into the dehydration store. Then an instance of the appropriate BPEL process is started. This functionality makes the system more stabel and reliable when something is goingin wrong in quees/files/db or any adapter that is used for polling.Are in-memory JMS messages not persistent (as long as the AppServer is up and running) ?
As you desribed: in-memory messages are only persistent in memory, if you restart the server, the messages are gone.Do I have to set a certain preference to let JMS live in the Queue as long as they are not retrieved by another BPEL process?
No you can not.Marc
http://orasoa.blogspot.com

Byte JMS Message processing in BPM process

Hello, I have a Global Automatic activity in my process which is listening a JMS Queue with Acknowledge Mode is set to "Auto Acknowledge". I am sending a XML on this JMS Queue as Byte Message. Please let me know how can I convert Byte XML back into text XML in my Global Automatic activity. I am using Oracle BPM 10.3.1.
Thanks in advance.

not the receive activity, rather the delivery service - that is called by the adapter. Depending on the operation type (one way only (input only) or two way /req-reply) the thread ~ and hence the transaction is held until it returns.
This means, under normal circumstances, the operation generated by the adapter wizard is oneway, and hence the delivery service inserts the message into the invoke message store, the thread returns, and the adapter (owning the tx if configured that way) will commit.
The process instance is started from a new thread then (and hence with its own tx).

Trigger a Begin event running Global Automatic activity

Hi
I have a situation explained as follows:
The BPM Process flow would be triggered when a message comes into a JMS Queue.
I have configured the JMS Messaging Service as an external resource and used a Global Automatic Activity as an Automatic JMS Listener to listen on that queue.
Once the message is received on the queue, I want my actual process flow to be instantiated and activities following the begin activity to be executed.
In the Studio Reference document, it is mentioned that
You can trigger a Begin event running Global Automatic activity.
Can someone tell me the steps to trigger the Begin Event from Global Automatic Activity and create the process instance.
Thanks

You have to call this method
ProcessInstance.create(arguments : args, argumentsSetName : "BeginIn")
Args is Any[String] where you put you input arguments that you have in your begin activity and BeginIn is the set of arguments you have in the begin activity.
HTH

JMS Messages Refusing to participate in JTA transaction

I have been working on this issue for several days, and I cannot find a path out.
I have a situation where I need to write to the database and also send out a JMS message. I want either both to work, or nothing to work, so its a straightforward JTA application, so I would think.
The JMS connection factory in use is set to participate in XA transactions (I have checked this 10 times).
I originally had a UserTransaction started and committed around these statements, but since this did not seem to be working, I put all the code in an EJB with transaction Required.
Either way, it is not working the way I expect.
I have a break point in the MDB that receives the message, as well as a break point on the publisher code and the code immediately after it. I find every time that as soon as I step past the JMS publish, the breakpoint in the MDB stops next, indicating that the JMS message was sent out, even though the publishers transaction is definitely not completed -- eventually the debugger will return back to the next line after the publish.
I am pretty sure we have done this many times in the past, and it has worked like I expect transacted code to work.
Anyone have any ideas on obvious things to check to determine why the JMS message is going out outside of the transaction? Or not so obvious...
Thanks in advance,
ken clark

Hi Ken,
You're right -- the use case is common, but there are a couple pitfalls that new users sometimes run into.
The break-point tracing results that you have are expected. A sender's message goes to the JMS server while the message send call is made. If the message is participating in the transaction, it is still sent, but it won't become visible to consumers until the transaction is later committed.
To ensure that a sent message participates in a transaction:
1 - ensure the connection factory is "XA enabled"
2 - ensure there's a transaction on the thread. For example: System.out.println("MY TX" + weblogic.transaction.TransactionHelper.getTransactionHelper().getTransaction());
3 - ensure that your connection.createSession() invoke passes "false" for the first parameter -- not true! if true and you're not using a resource ref, then the session becomes a "transacted" session, and JMS messages will participate in an independent local transaction rather than the global XA transaction
4 - If not using a WebLogic JMS to send, then you need to ensure that WebLogic automatically enlists the foreign vendor send call in the WL TX. All that is required is to use a standared JEE "resource reference" to obtain the CF. rather than directly looking up the foreign CF in the foreign JNDI provider. This lets WebLogic detect and wrap the application's foreign vendor calls, which in turn enables automatic enlistment. See the WebLogic JMS Interop FAQ for more info.
4B - If you're using AQ-JMS to send, more work is required, as AQ-JMS is fairly unique among JMS implementations. WL 10.3.1 and later provides features to simplify this work.
For a related FAQ see [ Integrating Remote JMS Providers | http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/interop.htm#JMSPG553 ], and for resource ref info see [ Enhanced Support for Using WebLogic JMS with EJBs and Servlets|http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/j2ee.htm#g1329180 ] (especially example 9-5).
Hope this helps,
Tom

How to stop and start MDBs to listen for JMS messages

Hello! This might be more of an architecture question rather than a technical questing, but I post it here, in the lack of a better place...
For several years I have been using Webster and Webster MQ to send messages back and forth to clients. The architecture for the middleware platform has been designed around the functionality of ListenerPorts. Listenerports is a Webster functionality that let you "stop" and start to listen to JMS messages for a given MDB either by admin console, or by JMX.
The arhitecture we used was something like this :
1.Client sends a persistent message to a queue. (order)
2. An MDB pics up the order message, calls a SessionBean that "fronts" the IIOP back end system.
This is quite "out of the box" architecture, but we used the Listenerports to solve a stability problem for our back end system.
The backEnd system was quite unstable, so the EJB threw an exception (typically because of timeout or connection refused) back to the MDB.
The Listenerport was "defined" to handle 3 errors before stopping, so the MDB resent the message twice before the listenerport automatically stopped. The nice thing about this feature was that the client could continue to send orders, and was not bothered when the back end system was down.
When the backEnd system was up and running, we could start the listenerport and it was all back to normal state. We even had a start script that checked the state of the listenerport every 30 minute, and started it automatically if it was stopped, making the admin task of starting the MDB unnecessary..
Now.. Why am I telling this story..
I would like to know how this could be done using "clean" J2EE technologies..That is..Not using any technology that is not portable..
I`m playing with glassfish at home, and it struck me that there is nothing in the J2EE spec that defines the functionality described above ? Am i missing something ?
I Do not want to stop My application because the back end system is down? That is the only way (i know of) that i can "stop" to listen for messages..
I can put all the messages on an error queue when the backbend system is down, but that would lead to more code just to handle the error messages. Maybe the easiest way to solve this is to "move" (programmatically) all messages from the error queue over to the "standard" queue every XX minute, but somehow that sounds "wrong"
Can anyone give me some advice to how this problem situation should be solved ? I`m interested in the solution both from an architectural perspective and from a more technical perspective..
Best regards
Hans-Jacob Melby

Breakpoints, whether normal or conditional, are just meant for debugging of your code. I had the sense from your question that the pausing you want to do is a part of normal operation of your code. I would NOT recommend using a breakpoint for that situation. It would bring up the block diagram showing the breakpoint when it occurs. A user besides the programmer would not know what to do in that case.
Yes, both the inner and outer loops would have shift registers.
Putting a case structure with a small while loop inside the "Pausing Case" is doable. It just depends on what you are doing or waiting for while the program operation is "paused".

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

How to do service callout with the incoming JMS message in OSB 11g

Hello All,
I have a specific requirement for which I am creating a kind of POC where I need some help in OSB, however am new to OSB.
My Environment:
1> I have a request queue (deployed on a WLS domain) - WFReq_WS
2> I have a response queue (deployed on a WLS domain) - WFRes_WS
3> I have created a ProxyService (request/response type) in OSB 11g which is simply mapping the incoming message in WFReq_WS to WFRes_WS
4> I have a WebService (it is currently a simple hello WebService for testing) which takes a string and returns the same string with an added 'Hi' in front of it (e.g. If you send Jack, it will return 'Hi Jack')
My Requirement:
1> I have to do some mechanism in OSB, by which while mapping the message from WFReq_WS to WFRes_WS (through the proxy service I have), it will pick the JMS message (which will be a string/text) and will make a service callout to the Webservice I mentioned using the message as the input parameter of the WebService.
2>Now when the response of the WebService will come, OSB should send this response as the message in the response queue (WFRes_WS) I mentioned above.
To simplify the requirement using an example:
A> I will send a text/String message (say Jack) to the request queue (WFReq_WS)
B> OSB should pick the message (Jack) and make a service callout to the webservice
C> webservice will return 'Hi Jack'
D> OSB should send this to the response queue (WFRes_WS)
I know the above might look very basic question to the PROs, but please elaborate (step by step) what need to be done, since I do not know OSB.
Thanks a lot for your help !

Your example points A and D are easily done by having a "Proxy Service" which has the following details:
Service Type = Messaging Service
Request and Response type = Text
Protocol = jms
Endpoint URI = your request queue (format like 'jms://localhost:7013/weblogic.jms.XAConnectionFactory/QueueJNDIName')
Checkmark "response" so that the proxy service automatically delivers the response to another queue - your response queue
Response URI = jms://localhost:7013/weblogic.jms.XAConnectionFactory/QueueResponse
Now since your "Hello" webservice is (probably) a SOAP xml service you need to "convert" your text based JMS message to xml before sending it on to the "Hello" service.
Your JMS proxy can do that by just doing a "Assign <whom>{$body/text()}</whom>" to a variable (lets call it 'reqHello')
Now your JMS proxy should actually call the Hello service and since your JMS proxy is text and the Hello service is SOAP you cannot just "pass" on to the Hello service in a "Route to". Instead you can do a Service Callout where you can specify your "reqHello" variable as payload and a "respHello" as response variable.
Now you have the "<whom>Hi jack</whom>" in the response variable and since the JMS response needs to be text format you can "extract" the text value into the body variable of the JMS proxy (use "replace /* in body with $respHello/text()" - replace node contents)
The actual Hello service is a simple "SOAP" based Proxy Service. Add a pipeline and add a stage in the reponse pipeline. Do a ...
Assign fn:concat("Hi ",$body/whom/text()) to $whomVar
Replace whom in body with $whomVar (replace node contents)

Weblogic Message Bridge Producing Duplicate JMS Messages

We have a message bridge that we use to integrate with TIBCO. The message bridge is deployed on a WL cluster. We see duplicate JMS messages produced by the bridge when it is deployed on the cluster. We don't see this behavior when only one ManagedServer in the cluster is active,.
TIBCO version: 4.4.3 V5
WLS: 10.3.3 with patch for bug BUG8732539 (BQC6)
java -version
java version "1.6.0_17"
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2121-linux-x86_64, compiled mode)
We are also seeing a lot of exceptions related to
<May 27, 2011 4:11:57 PM PDT> <Warning> <Connector> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
However the bridge is active. We are monitoring the message-out count on TIBCO and we observed that we see duplicates whenever there a message is re-delivered. We opened a case with Oracle support and they suggested patch 10258751 which didn't help. The next suggestion was a patch for "Bug 11852771 - [WLS10.3.2]MISSING AND DUPLICATE IN JMS QUEUE MESSAGE MONITORING" but I don't think it will help since our JMS consumers are getting duplicate messages and this is not just a UI issue.
Here is the message behavior when we send a single message:
Timelines
11:34:17 --> Message sent to TIBCO EMS queue
11:34:17 --> WL MS3 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:17 --> WL MS1 says it got the message and committed the transaction
11:34:17 --> Message is visible in the JMS queue in the admin console
11:34:17 --> TIBCO EMS has still not received an ACK from WL for the message
11:34:31 --> TIBCO EMS resends the same JMS message to WL
11:34:31 --> WL MS2 says it got the message and committed the transaction
11:34:31 --> WL MS1 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are two messages in the JMS queue)
11:34:31 --> TIBCO EMS has still not received an ACK from WL for the message
11:34:54 --> TIBCO EMS resends the same JMS message to WL
11:34:31 --> WL MS4 says it got the message and committed the transaction
11:34:31 --> WL MS2 throws an javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable exception
11:34:31 --> Message is visible in the JMS queue in the admin console (At this point there are three messages in the JMS queue)
11:34:31 --> TIBCO EMS receives an ACK from WL for the message
MS04
####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: true
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-6A59E8FE76C4FC4CA149
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:54 AM PDT> <Debug> <MessagingBridgeRuntime> <MS04> <MS04> <[ACTIVE] ExecuteThread: '109' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-6A59E8FE76C4FC4CA149> <> <1306521294611> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<193654.1306521294611.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
MS03
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257342> <BEA-000000> <Bridge MessageBridge1 Successfully got connection to the target destination>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1: both source and target adapters support XA = true>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 supportsMDBTX = false supportsXA = true async = true>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 WorkMode = Exactly-once>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntimeVerbose> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257343> <BEA-000000> <Bridge MessageBridge1 Entering processMessages() ------ >
####<May 27, 2011 11:34:17 AM PDT> <Error> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-3AA29116A4CA622834EA> <> <1306521257343> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: javax.resource.ResourceException: Failed to setup the Resource Adapter Connection for enlistment in the transaction, Pool = 'eis/jms/WLSConnectionFactoryJNDIXA', javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:948)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:200)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMFAIL : Resource manager is unavailable
javax.transaction.xa.XAException: Internal error: XAResource 'eis/jms/WLSConnectionFactoryJNDIXA' is unavailable
at weblogic.transaction.internal.XAResourceDescriptor.checkResource(XAResourceDescriptor.java:948)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:634)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1227)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy62.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1431)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:507)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:434)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:117)
... 8 more
).>
####<May 27, 2011 11:34:17 AM PDT> <Warning> <MessagingBridge> <MS03> <MS03> <[ACTIVE] ExecuteThread: '30' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521257344> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
.)>
MS02
####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271386> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: true
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-679AF074F381152F047C
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:31 AM PDT> <Debug> <MessagingBridgeRuntime> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-679AF074F381152F047C> <> <1306521271392> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<196075.1306521271386.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:54 AM PDT> <Error> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:225)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
... 2 more
).>
####<May 27, 2011 11:34:54 AM PDT> <Warning> <MessagingBridge> <MS02> <MS02> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521294610> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
MS01
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257536> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) received message:
JMS Message Class: TextMessage
JMSMessageID: ID:MS01.4B044DDFEE1F1:25354AD
JMSCorrelationID: null
JMSDeliveryMode: PERSISTENT
JMSDestination: Queue[SourceQueue1]
JMSExpiration: 0
JMSPriority: 4
JMSRedelivered: false
JMSReplyTo: null
JMSTimestamp: 1306521256905 (Fri May 27 11:34:16 PDT 2011)
JMSType: null
Transaction Id: BEA1-72BC818FE2BB8C2655C6
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:17 AM PDT> <Debug> <MessagingBridgeRuntime> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-72BC818FE2BB8C2655C6> <> <1306521257542> <BEA-000000> <Bridge: MessageBridge1 (processMessages()) successfully sent message:
JMS Message Class: TextMessage
Old JMS MessageID: ID:MS01.4B044DDFEE1F1:25354AD
New JMS MessageID: ID:<195581.1306521257536.0>
<?xml version="1.0" encoding="UTF-8"?>
<commands ...
>
####<May 27, 2011 11:34:31 AM PDT> <Error> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200015> <An error occurred in bridge "MessageBridge1" during the transfer of messages (java.lang.Exception: weblogic.transaction.RollbackException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1871)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:330)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:224)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:293)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1534)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1006)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1083)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: start() failed on resource 'eis/jms/WLSConnectionFactoryJNDIXA': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:495)
at weblogic.connector.transaction.outbound.XAWrapper.setTransactionTimeout(XAWrapper.java:457)
at weblogic.connector.transaction.outbound.RecoveryOnlyXAWrapper.setTransactionTimeout(RecoveryOnlyXAWrapper.java:34)
at weblogic.transaction.internal.XAResourceDescriptor.setXAResourceTransactionTimeoutIfAppropriate(XAResourceDescriptor.java:1422)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1223)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1161)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at weblogic.connector.security.layer.AdapterLayer.setTransactionTimeout(AdapterLayer.java:485)
... 14 more
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1185)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:282)
at weblogic.transaction.internal.XAServerResourceInfo.enlistIfStatic(XAServerResourceInfo.java:181)
at weblogic.transaction.internal.ServerTransactionImpl.enlistStaticallyEnlistedResources(ServerTransactionImpl.java:1565)
at weblogic.transaction.internal.ServerTransactionManagerImpl.dispatchRequest(ServerTransactionManagerImpl.java:551)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:132)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
... 1 more
).>
####<May 27, 2011 11:34:31 AM PDT> <Warning> <MessagingBridge> <MS01> <MS01> <[ACTIVE] ExecuteThread: '36' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306521271384> <BEA-200026> <Bridge "MessageBridge1" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was java.lang.Exception: MessagingBridgeException: Messaging bridge operation failed
.)>

@Tom, thanks for your hints and sorry for my delayed response. Here are my answers to your queries…
-- Does messaging work, without any exceptions, when only one bridge is active?
It works fine when only one node of the cluster is active. -- I'm not familiar with Tibco monitoring, but I suspect that the "message-out count on TIBCO" stat doesn't always imply that there's a duplicate message. It could mean that an initial message delivery attempt failed, it's transaction rolled back, and the message was redelivered. Redelivery after a failure is normal - the original delivered message, if one actually made it onto a WebLogic queue, should be discarded by WebLogic when its failed transaction eventually rolls back (before its ever handed to a consumer application).
You are absolutely right. The mismatch in count was due to redelivery attempts. We could see that as soon as we turned on trace in TIBCO-- The posted stack traces look like they may be JVM stdout/stderr scrapes, which are often automatically truncated, for example, see the "... 8 more" listed at the bottom of one of the stack traces below. There might be more information in the full stack trace for the "Resource manager is unavailable" exception. Full traces are logged in each WebLogic Server's log files.
I tried redirecting the output and even set "stdout Stack Trace Depth:" to -1 but I am not albe to see the complete trace.-- The setTransactionTimeout NullPointerException error message looks like it is collateral damage from the original reported "Resource manager is unavailable" exception that's thrown earlier during the enlistResource() step. If you are truly getting duplicates, then I think this is a clue that the bridge is somehow (stupidly) trying to proceed with forwarding the message despite the fact that there's no current transaction on the thread... 
I have a case open with Oracle support and we have extensive debugging turned on. Here is what the engineer came back with. There is an issue with XA transactions in JCA adapter when it talks to third party providers like TIBCO. Since the resource names are not unique across the cluster, a XA transaction is started on multiple nodes in the cluster for the same message. All transactions abort but the message is persisted and TIBCO redelivers the message since the connection is severed when the transaction aborts. We were able to reproduce this scenario at will with our setup and Oracle was able to reproduce the issue too.  -- Can you check the state of the message on the WebLogic Q? The fact that a message is shown on the WL console doesn't necessarily mean that the state of the message is visible (it could be waiting for the transaction to commit - something that apparently never happens). On the console: Services -> Messaging -> JMS Modules -> [module name] -> [destination name]. 
Our consumer was getting duplicate messages. This confirms that the console was not giving us incorrect information. The console showed that 2/3/4 messages were in "current" state when we expected only one message. -- Make sure that the bridge's Tibco destination is a Tibco queue not a Tibco topic (it's happened). 
Yeah we made sure it was a Queue. -- Can you post your bridge and destination stanzas from your config.xml?  
Will try to do this shortly but have to strip out lot of information. -- I vaguely recall that there was a problem with untyped connection factories in Tibco at one point (not sure). You might want to try changing the Tibco configuration to spin-up "XA Queue Connection Factory" instead of just an "XA Connection Factory" (plus modify the bridge configuration accordingly). 
We tried this but it didn't eliminate this issue. One thing we did notice however was that the number of rollbacks were greatly reduced. 
Here is the workaround that Oracle is suggesting: Create pinned destinations and assign it to a distributed queue. This will keep the transactions local and hence eliminate the duplicate transactions and rollback. We tried it and it eliminated the dups issue. However I discovered another bug during my testing. Our cluster messaging mode is "Unicast" and message forwarding from zero consumer queues to queues with consumers fails. We have four/five nodes in the cluster and two consumer threads. I observed that the zero consumer queues always forward to one queue in the cluster that has consumers. The forwarding stalls when I bring down the node that has consumers. Again, we were able to reproduce this issue at will and Oracle has acknowledged that it is a bug. They've reported that Unicast fails without any warning whereas Multicast fails with a warning in the log. We have observed this message forwarding stalling even with UDQs.
I have another case open for an issue where our message bridges that transfer messages from TIBCO to WLS stalls after sometime. The status is shown as active but it is not doing anything. The server instance shows stuck threads trying to roll back a message. TIBCO logs indicate that it is receiving a request to rollback a transaction but it is not finding the transaction to rollback. The only way to recover from this condition is to restart the cluster. I am fairly confident that he root case for this issue is again the XA transaction issue. I changed our UDQ to pinned destination in one environment and we are no longer seeing dups or bridge stalling there. Hopefully Oracle can resolve the message forwarding issue.Thanks again….

Error in JMS message routing

Hi,
I am doing interface which send JMS messages to IDOC. JMS is sending three different messages (three XSD's) and I have created three separate interfaces as a below.
A) Negative.xsd ; to IDOC1
B) Positive.xsd ; to IDOC2
C)Multiple.xsd ; to IDOC3
When I get the Negative.xsd from JMS for the first time, Interface u2018Au2019 is executing and itu2019s creating IDOC1 successfully. When I get the Negative.xsd for the second time then the Interface u2018Bu2019 is executing (Instead of Interface u2018Au2019) and itu2019s trying to send Negative.xsd into IDOC2 and itu2019s getting fail.
When we are getting all the three XSDu2019s at the same time then first interface u2018Au2019 is getting picked up and failed for the second (u2018Bu2019) and third (u2018Cu2019) interfaces and for first one is successful.
Can you please guide me to pick the right interface?
Regards,
Kishore

Hi, Kishore:
In your situation, you need to configure Message Selector for your JMS sender adapter:
1. First you have to work with your JMS Queue system consultant, create a Property name, Saying "MsgType", its value is used to identify type of the message. e.g. the message of Positive Type put into the queue, its Property value "MsgType" can be set to "Positive"
2. In your JMS Communication Channel, Parameter Tab -> Advanced Tab, you need to Check " Adapter Specific Message Attribute"
3. Then Check "Specify Additional JMS Message Properties
Click "+" to add your property name, it should match the property name mentioned in step 1. e.g. "MsgType"
4. In "Process" tab, you specify message Selector:
e.g. MsgType = Positive"
After you have done above step, this JMS adapter only pick message of the Property value "MsgType" equals to "Postive"
You can create additonal JMS commnunication channels that polling from same queue, but only for different type of message: e.g. "Negative"
Regards !
Liang

View JMS messages wls 10.3

Hello
I m trying to view/delete jms messages in a queue in WLS 10.3. As Administrator user I m able to view/delete the messages but when logged as an user of Monitors group I m not even able to view the messages.
Is there any other user group apart from Administrator which can view messages in WLS 10.3. Please help
Thanks
Kranthi

Tom,
You are correct, I m able to view messages as Monitors group ID even from Hermes.
To check from console I had to update the weblogic.management.runtime.JMSDestinationRuntimeMBean security.
Here the steps I got from support to enable operations on JMSDestinationruntime mbean:
1.     In the left pane, select Security Realm.
2.     Select “myrealm”.
3.     In “Configuration” tab, check “Use Authorization Providers to Protect JMX Access”, click save and then activate changes.
4.     Restart the server.
5.     In the left pane, select Security Realm.
6.     Select “myrealm”.
7.     Go to “Users and Groups”.
8.     In users, create a new user say “queueuser”, add it to group “Monitors”
9.     Adding it to group “Monitors”:
a.     Select “myrealm”.
b.     Select “Users and Groups”.
c.     Click on user name, in right pane select “Groups”.
d.     From Parent Groups, select monitors, click arrow pointing right side.
10.     Go to “Roles and Policies” - > Realm Policies
11.     In Policy table, select “JMX Policy Editor”.
12.     Select “Global Scope”, click next.
13.     From MBean Types, select “weblogic.management.runtime”
14.     Select “JMSDestinationRuntimeMBean”, click next.
15.     In Attributes and Operations, select “Operations: Permission to Invoke”.
16.     Click on “Create Policy” button and save
17.     Click on “Add Condition”, Select “Group” in “Predicate List”, click next, type Monitors, say add. Click “Finish”.

JMS message transacted

I am trying to deploy a MDB PTP implementation within WebLogic 7 and I keep getting the following error. Could some please enlighten me to what configuration or code changes I need to make?
Thankyou in advance for any help :-)
####<4/10/2002 10:20:56> <Warning> <EJB> <WSJON> <T5MBankServer> <ExecuteThread: '9' for queue: 'default'> <kernel identity> <> <010061> <The Message-Driven EJB: mBankingJMSBean is unable to connect to the JMS destination: mBankingJMSQueue.
The EJB container will automatically attempt to re-establish the connection with the JMS server. This warning may occur during WebLogic Cluster start-up if the JMS destination is located on another WebLogic Server instance. When the JMS server connection is re-established, the Message-Driven EJB will again receive JMS messages.
The Error was:
Message Driven Bean 'mBankingJMSBean' is transacted but the provider defined in the ejb is not transacted. Provider should be transacted if onMessage method in MDB is transacted.>

The connection factories that you configure for your MDB must return XAConnection. From that the MDB container can create XASessions and ultimately get access to the XAResource for your JMS provider. If your factory is not returning XA connections.
My guess is you are using container managed transactions. That is you want everything in the same transaction. Without XA support from your JMS provider the container cannot provide the guarantees that you have requested, therefore it fails the connection (rather than lie to you and give you something that is not atomic).

JMS messages sometimes not received by Flex client

We have a problem that Flex client is sometimes not able to
receive JMS messages from a JBoss JMS Queue. Most of the time it
works, but if users logout/login using the same account frequently
or you restart JBoss 4.0.4 during their session then it might
happen. Then it doesn't work at all even if you wait. Client is
able to send messages when this problem occurs, which can then be
intercepted by other clients but cannot receive any messages from
himself or from the others. JBoss 4.0.4 is running in cluster mode.
Could it be that there is an old frozen session which is receiving
the messages meant for the new client?(consumer selector is unique
to each user, but if a user logs in twice, the same selector is
used) If I run 2 instances of my JMS test consumer using the same
selector then the consumer which registered later receives the
messages and if it quits, then the older consumer starts receving
them. This doesn't occur in Flex.
Flex is running on Tomcat 5.5.17.
Our messaging-config.xml is
<?xml version="1.0" encoding="UTF-8"?>
<service id="message-service"
class="flex.messaging.services.MessageService"
messageTypes="flex.messaging.messages.AsyncMessage">
<adapters>
<adapter-definition id="actionscript"
class="flex.messaging.services.messaging.adapters.ActionScriptAdapter"
default="true" />
<adapter-definition id="jms"
class="flex.messaging.services.messaging.adapters.JMSAdapter"/>
</adapters>
<destination id="JMSQueueB">
<properties>
<network>
<session-timeout>10</session-timeout>
</network>
<jms>
<initial-context-environment>
<property>
<name>java.naming.factory.url.pkgs</name>
<value>org.jboss.naming:org.jnp.interfaces</value>
</property>
<property>
<name>Context.PROVIDER_URL</name>
<value>jnp://x.x.x.x:1100,jnp://x.x.x.y:1100</value>
</property>
<property>
<name>Context.INITIAL_CONTEXT_FACTORY</name>
<value>org.jnp.interfaces.NamingContextFactory</value>
</property>
</initial-context-environment>
<destination-type>Queue</destination-type>
<message-type>javax.jms.TextMessage</message-type>
<connection-factory>ConnectionFactory</connection-factory>
<destination-jndi-name>queue/B</destination-jndi-name>
<destination-name>B</destination-name>
<delivery-mode>PERSISTENT</delivery-mode>
<message-priority>DEFAULT_PRIORITY</message-priority>
<acknowledge-mode>AUTO_ACKNOWLEDGE</acknowledge-mode>
<transacted-sessions>false</transacted-sessions>
</jms>
</properties>
<channels>
<channel ref="my-rtmp"/>
<channel ref="my-secure-amf"/>
</channels>
<adapter ref="jms"/>
</destination>
</service>
Part of our actionscript code:
pmConsumer = new Consumer();
pmConsumer.destination = "JMSQueueB";
pmConsumer.selector = "some jms selector ....";
pmConsumer.addEventListener(MessageEvent.MESSAGE,
presenceMessageHandler);
pmConsumer.addEventListener(MessageFaultEvent.FAULT,
faultHandler);
pmConsumer.addEventListener(ChannelFaultEvent.FAULT,
channelFaultHandler);
pmConsumer.subscribe();
Also Flex seems to be handing channel switching incorrectly,
if rtmp port is firewalled, it won't use amf properly even though
it was given 2 channels in configuration file and JMS messaging
doesn't work. We have to alter the channel set during runtime.
Flex also doesn't automatically switch to other JMS server if
one goes down. Is this a feature or a bug? We have to reset
producer and consumer in order for this to work.

Hi,
It was in earlier version of the OS that you could turn Bonjour On and Off.
If this can be done in Leopard and Snow Leopard I have not found it yet. (But I don't look that often and nor for very long)
This Forum may help with that
I would also try a PRAM reset. (on Both computers)
Shut down the computer.
Restart it holding down APPLE(or ⌘)ALT+PR Keys until you have heard three Start Up Bongs.
7:18 PM Tuesday; December 8, 2009
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

Polling or JMS Message in Global Automatic

Similar Messages

Maybe you are looking for