WebLogic 9.2MP2.Messages Pending topic count JMS display negative value

on admin console. Services -> Messaging -> JMS Modules in JMS System Modules -> JMS queue name -> Monitoring role tab .
I use WebLogic 9.2MP2 version . I found that JMS destination summaize page, Messages Pending topic count display negative value.
What is mean negative value ? or that bug of WebLogic9.2 MP2.
Thank you.
BR,

A negative value indicates a bug -- quite likely in internal statistics gathering code itself. I don't know if the problem has been addressed in later MPs or later versions.
Tom

Similar Messages

Counting and displaying Uniqe Values(Countries)

I have a Large table, Country, Project, Month(Jan, Feb, March.....)
I Count Projects each Month based on simple Formula.
Yes/No = Removed
No/Yes = Added
Yes/Yes= No Changes
No/No = None
Projects are all fine. i got all in and outs. (COUNTIF[Range]"Value") and (SUMIF"Value"[Range])
I count Unique Countries
=SUM(IF(A3:A10031<>"",1/COUNTIF(A3:A10031,A3:A10031)))-(CTR-SHIFT-ENTER)
How can i get the In(Added) and Outs(Removed) of the Unique Values of Countries based on Projects Answers?
Country
Project Num
Jan-14
Feb-14
Mar-14
Apr-14
May-14
Jun-14
Jul-14
Aug-14
Sep-14
Oct-14
Nov-14
Dec-14
Angola
AGO 1
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
Ghana
GHA 8
No/No
No/No
No/No
No/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Ghana
GHA 1
No/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
Ghana
GHA 3
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
Ghana
GHA 5
No/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
Ghana
GHA 7
No/No
No/No
No/No
No/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Ghana
GHA 2
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Ghana
GHA 6
No/No
No/No
No/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Kenya
KEN 5
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
Kenya
KEN 3
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
Kenya
KEN 4
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
Kenya
KEN 6
Yes/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
Kenya
KEN 6
No/No
No/No
No/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
Kenya
KEN 7
No/No
No/No
No/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
Mauritius
MRU 1
No/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
Morocco
MAR 2
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
Mozambique
MOZ 1
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
Mozambique
MOZ 2
Yes/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
Mozambique
MOZ 3
No/No
No/No
No/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
Mozambique
MOZ 4
No/No
No/No
No/Yes
Yes/Yes
Yes/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
Namibia
NAM 1
Yes/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
Nigeria
NGA 2
Yes/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No
No/No

Which Excel version do you use?
If you have Office 2013 Professional Plus, Office 365 Pro Plus, or Excel Standalone editions, you should consider using
Power Query Add-In to get your report.
With Power Query you can transform the data above, unpivot it and load it to the worksheet. Then with PivotTable you can get anything you need.
With Power Query, I took your data above and unpivot it into this table:
Then I created a PivotTable to count how many projects you got by month (With PivotTable you can achieve many other reports on top of this kind of data).
If needed, I can provide step-by-step instructions, once you install Power Query.

Messages Current and Messages pending in JMS

Hello All,
I would like to know the difference between Messages Current and Messages Pending in the JMS monitoring tab.
I did read the official documentation but to be honest I am not sure I am undestanding it right !
Could someone explain to me (in simple terms :-) the difference between the two ?
Many thanks.

Hi,
Can you please tell me what fields in the Message Header indicate about the source and/ or target systems? For example the Directory header parameter, of Sender FILE channel, tells me from where the file was picked up.
Likewise what does the field JMSDestination stands for?
The screenshot which I have shows the JMS Message Header Details (the ASMA characters).
Tried searching for fields like JMSDestination, but there is no information on SDN abou it.
Thank you,
Pankaj.

MDB leaving messages pending in a topic

I have a case in production where the MDB
          Pools Beans in use count is -2
          The topic which it subscribes to is having alot of message pending back
          up on our topic.
          Also the bean does not seem to undeploy so I can get rid of it as a
          consumer.
          I am also posting in EJB news group
          Weblogic 7.0 sp1


Well Raskol, you said that you have a (may be more) DurableSubscriber created for a Topic and consuming the messages asynchronously through the onMessage method. Now the question is how to know whether all the messages posted to that Topic are delivered to you so as to enable you to stop the DurableSubscriber from further listening.
My question to you is when do you decide (and convince your self) that no more messages are available on that Topic.
The answer may be to timeout after a predetermined value. But then, what is the guarantee that no more messages will be posted subsequently to this Topic.
Any way, this can not be accomplished as per the suggestion from 'turbobutton', since JMS does not allow for synchronous reception, once you declare an asynchronous listener.
So, try restarting a global timer with each message reception. On crossing a predetermined value, call subscriber.close method. If this is not supported by your provider, try calling connection.stop (but, mind you, this call stops reception by all consumers created on this connection).
-kris teja

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….

Messages stuck in "Messages Pending" column of a JMS queue.

Hi
Is there any way to retrive the messages which are stuck in "Messages Pending" column of a JMS queue.
weblogic 8.1 SP5 version.
Thanks

there is some possibility to prevent the Pending Message or to automatically purge them on WL 9.x or WL 10.x?WebLogic JMS provides "message management" console, scripting, and mbean features to view and manipulate messages in a destination. You can search for "message management" in this newsgroups for more information - here's a good post: Re: WLST Script Help It also provides features for automatically moving problem messages to an error destination, expiring old messages, and/or deleting messages thave have exceeded a configured redelivery limit. I suggest reading through our feature list in the documentation, see "Value-Added WebLogic Server JMS Features" in the [ Information Roadmap | http://download.oracle.com/docs/cd/E15523_01/web.1111/e14529/messaging.htm#sthref23 ].
Note that it's usually best to try and understand why messages are marked pending and fix the underlying reason instead of purging such messages. Messages are normally pending for a valid reason, and most use cases can't tolerate arbitrarily losing a message.
Tom

Weird things when persisting the jms messages of topic in the wls9?

I am testing the store of the jms messages in wls9.
          But when i sent a topic message to the topic, it seems that the message cannot be stored to the persistent stores.
          The things were that:
          when i send a message of queue and refreshed the page of console of wls9.I saw the number changed in :"Home > Summary of Persistent Stores > exampleJDBCStore "-Monitoring-Statistics,the "Create Count" had increased.
          But when i use the topic message, the "Create Count" never changed.
          Anybody can tell me why?
          Is the topic message cannot be stored in persistent stores, or others ?
          thx and rgds.

Topic messages are not persisted unless both the publisher qos is persistent and there are existing durable subscribers. Otherwise, there is no need to persist them. Do you have any durable subscribers?
          Tom

JMS has messages pending in the queue

Hi, I created a JMS queue to hold some messages, then two message driven bean each take a message from the queue and use JavaMail API 1.2 to send an email out. But somehow, after a while, say, a couple of weeks, there will be about 20 messages pending the queue causing the queue hanging forever. Does anybody know what cause this JMS queue pending? Or is there anything wrong with this design? Thank you very much.

No, Acknowledgement is sending successfully, no excpeption is raising, in finally it is got acknowledged.
here is code block,
public void sendObject(Serializable message) throws JMSException
try {
HelperMethods.logDebugMessage("begin sendObject " + System.currentTimeMillis(),
this.getClass().getName(), "sendObject");
ObjectMessage objectMessage = getQueueSession().createObjectMessage();
objectMessage.clearBody();
objectMessage.setObject(message);
getQueueSender().send(objectMessage);
HelperMethods.logDebugMessage("sent sendObject " +System.currentTimeMillis(),
this.getClass().getName(), "sendObject");
getQueueSession().commit();
catch (Exception e) {
HelperMethods.logDebugMessage("Exception" + e.getMessage(),
this.getClass().getName(), "sendObject");
throw new JMSException(e.getMessage());
public void onMessage(Message message) {
ObjectMessage objectMessage = (ObjectMessage) message;
AttachmentFileUtil attachUtil = new AttachmentFileUtil();
try {
HelperMethods.logDebugMessage("received write sendObject msg " +
System.currentTimeMillis(),
this.getClass().getName(), "onMessage");
if (message instanceof ObjectMessage) {
HelperMethods.logDebugMessage("about to process write sendObject msg " +
System.currentTimeMillis(),
this.getClass().getName(), "onMessage");
AttachmentInfoBean attachment = (AttachmentInfoBean)
objectMessage.getObject();
HelperMethods.logDebugMessage("processed the write sendObject msg " +
System.currentTimeMillis(),
this.getClass().getName(), "onMessage");
HelperMethods.logDebugMessage("writing the sendObject msg to disk " +
System.currentTimeMillis(),
this.getClass().getName(), "onMessage");
// Here we are calling attachment bean, which uploads the file into file server
     attachUtil.writeContents(attachment);
     HelperMethods.logDebugMessage("After writing the sendObject msg to disk ",
                                                       this.getClass().getName(), "onMessage");
          HelperMethods.logDebugMessage("After Commiting Session " +
                    System.currentTimeMillis(),
                    this.getClass().getName(), "onMessage");
HelperMethods.logDebugMessage(
"finished writing the sendObject msg to disk " +
System.currentTimeMillis(), this.getClass().getName(), "onMessage");
else {
HelperMethods.logDebugMessage(
"oops! no ObjectMessage was received" +
message.getClass(), this.getClass().getName(), "onMessage");
throw new NowException("not an ObjectMessage was received" +
message.getClass());
catch (Exception ex) {
ex.printStackTrace();
HelperMethods.logDebugMessage("Exception" + ex.getMessage(),
this.getClass().getName(), "onMessage");
finally {
try {
HelperMethods.logDebugMessage("acknowledging the message",
this.getClass().getName(), "onMessage");
objectMessage.acknowledge();
catch (JMSException ex) {
ex.printStackTrace();
HelperMethods.logDebugMessage("JMSException" + ex.getMessage(),
this.getClass().getName(), "onMessage");
This is my production problem, please suggest me ASAP.
Regards,
Murthy Patnaik

When i restart the weblogic server 9.2,all messages in Topic get cleared

Hi,
          When i restart the weblogic server 9.2,all messages in Topic get cleared for inactive dudrable subscribers.
          Please advise what the issue here.
          Thanks.

Hi Tom, Thanks you so much for spending your time on this issue.
          A)I didn't specify any persistent mode.so i believe default mode is "Persistent"
          B) when i click on durable subscribers link on the corrersponding Topic it is showing 2 users.
          actually these durable subscribers are created by executing below code after look up the Topic.
          TopicSubscriber tsub = ts.createDurableSubscriber(topic,"mysub");
          C) Delivery Mode Override is set to "No-Delivery".
          but Time-to-Live Override is set to 21600000 .
          i assume Time-to-Live is causing problem.
          Please advise.
          Thanks.
          Edited by rodex at 03/25/2008 3:55 PM

Example of Weblogic Appserver using XA Controlled Transaction to send messages to third party JMS

          I am looking for Example of Weblogic Appserver using XA Controlled Transaction
          to send messages to third party JMS Server.
          I want to send messages to JMS and use Weblogic MDB to consume that message and
          send it to some third party JMS in a XA Controlled transaction.


Sure. Right now, it involves a bit of JTA programming -- in our next
          release, it should be easier, however.
          Before sending a message, you have to:
          -- Use the TxHelper class to get the current Transaction object.
          -- Use the "getXAResource" method on the JMS provider's Session object to
          get the XAResource object for the JMS Session you're using to send.
          -- Call "enlistResource" on the Transaction object.
          You MUST do this in every transaction where you use the JMS provider to send
          a message.
          You can find the documentation for the TxHelper class and other
          WebLogic-specific classes here:
          http://e-docs.bea.com/wls/docs70/javadocs/index.html
          Look for the "weblogic.transaction" package.
          You can find documentation for the Transaction class (which defines
          enlistResource) and other classes here:
          http://java.sun.com/products/jta/javadocs-1.0.1/index.html
          You should also use the weblogic.transaction.TransactionManager class and
          call "registerDynamicResource" once (and only once) in your application to
          register the JMS providers XAResource with JTA. This makes JTA more
          efficient, and it makes transaction recovery work properly.
          If the JMS provider is MQ, then look at the whitepaper "Using JTA
          transactions to envelope WLS JMS and IBM MQSeries" here:
          http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          And finally, if you have more questions, the transaction people will be able
          to help more. Post to "weblogic.developer.interest.transaction".
          greg
          "Neeru Munjal" <[email protected]> wrote in message
          news:[email protected]...
          >
          > I am looking for Example of Weblogic Appserver using XA Controlled
          Transaction
          > to send messages to third party JMS Server.
          > I want to send messages to JMS and use Weblogic MDB to consume that
          message and
          > send it to some third party JMS in a XA Controlled transaction.
          >

JMS Adapter is not picking messages from Topic ( AIA Error Notification)

Hi All,
One of my service is not picking messages from topic. This service was working in one environment but not working in this environment.
I am using AIA 2.5 and using AIAErrorNotification.
Service AIAAsyncErrorHandlingBPELProcess is enquing the message but consumer service AIAReadJMSNotificationProcess is not being invoked automatically.
Whenever we are manually invoking this service, then this service is dequing messages from topic.
Is any have any clue for this?
Thanks in Advance.
Edited by: vikky123 on Dec 22, 2010 1:46 PM

Increase Log level for cube.activation to debug and check the logs by stopping & starting the activation agent(I mean Retire and activate the process) .. It should give a clue on what's happening..

What is Message Pending?

          What does the Message Pending statistic in weblogic console mean? Does that mean
          the message is not delivered to the topic or does it mean that the message was
          not consumed?


On a topic, all messages are counted as pending.
          A message is deleted on a topic once all subscribers
          that are due to receive the message have acknowledged/committed.
          Siri Nivasam wrote:
          > What does the Message Pending statistic in weblogic console mean? Does that mean
          > the message is not delivered to the topic or does it mean that the message was
          > not consumed?
          >
          >

JMS distrubuted topic and jms inbound adapter

Hi,
We are building a HA application using precise recovery using JMS. FOr that we want to create a distributed JMS Topic (ckustered JMS Topic). As we understand things, when a JMS subscriber subscribes to a distributed Topic it is actually wired to a sopecific server (a specific fisical JMS Topic). When this JMS server fails the connection is dropped and the JMS subscriber needs to reconnect.
1. Is our understanging correct?
2. If yes and we need to reconnect to the surviving JMS Topic, is there a way to "tell" the JMS Inbound adapter to do so? Is it done automatically by the adapter?
Thanks,

There are a few different things you should be considering when configuring JMS for precise recovery, so I'm afraid this is going to be a long response.
* The precise recovery feature may not work correctly in the case where JMS output messages are lost. Avoiding message loss in the case of a JMS failure involving topics requires the use of persistent messages and durable subscribers. This is true regardless of whether you're using Distributed Topics or a Topic hosted by a single server. So use of durable subscribers is highly recommended when using CEP precise recovery.
* The CEP JMS input adapter won't actually support durable subscriptions until the upcoming 11.1.1.6 (PS5) release. So if you want to use durable subscriptions to avoid problems with precise recovery in the case of JMS server failure you would need to be on this release of CEP (at least for production).
* If you're using the CEP JMS inbound adapter with a distributed topic and a non-durable subscription, you can configure the adapter destination-jndi-name with the logical name of the topic and if the topic member servicing a given consumer fails, the consumer will reconnect to a surviving topic member. This works because you're using a logical destination name (not a physical host name or IP address), so the adapter is able to determine the surviving servers associated with the logical topic and reconnect to one of them. However since you'd be using non-durable subscriptions in this case to achieve failover/reconnect, you can have the problem described above with message loss and precise recovery (non-durable subscribers/non-persistent messaging can lose messages during the actual failover/reconnect).
* Unfortunately, WLS doesn't support durable subscriptions to distributed topics using the logical destination name. When using distributed topics you can only create durable subscriptions on specific topic members, and since these are subscriptions to a specific physical member these subscribers won't failover to another topic member if the server hosting their subscription fails.
So given all of the above you can see that the use of distributed topics with CEP precise recovery may not provide the ideal level of HA (the ability to handle combinations of JMS and CEP failures). You might want to consider using a non-distributed (single server) topic with persistent messaging and durable subscriptions as an alternate approach for precise recovery. In this configuration JMS server failure would require restarting the failed server, but once the JMS server is restarted there should be no message loss and CEP precise recovery should work correctly.
If you're determined to use distributed topics you might want to try posting to the JMS forum to see if anyone there has ideas for other solutions. Just let them know that CEP in this case is essentially acting as a vanilla JMS client (not MDB based) that can't tolerate message loss:
WebLogic Server - JMS

Enforce to send the messages pending, after the Time To Deliver is changed

JMS Queue is being used to send data from our database to the headquartersâ€™ database.
          Our organization considers using "Time To Deliver Override" during the scheduled downtime of the headquartersâ€™ database. For example, when our admin is informed by the headquarters' admin that downtime is scheduled, our admin can change "Time To Deliver Override" from -1 to 1200000 (20 hrs) in WebLogic Consol. Then, when the database is back, our admin will reset the value to -1.
          It is simple and quick. However, I realized that the messages pending will not processed for the â€œTime To Deliverâ€ which was configured when the message was added.
          Can WebLogic enforce to send the messages pending, after the "Time To Deliver Override" is changed back to -1?

A few related points:
          - I think 9.x may provide mbean/JMX/administrative options to change time-to-deliver in existing messages - but, even if it does, this seems unwieldy.
          - 9.x also provides options for adminstratrively pausing delivery of a destinations messages, and/or pausing MDBs.
          - I think the "time-to-deliver override" also supports setting absolute times via cron like schedules (eg - you can configure it so messages are born at a specific time.)
          - Another option is to introduce an intermediate destination and configure a "messaging bridge" to forward messages between them. When messaging needs to be pause, administratively stop the bridge.
          Tom

WLST assign WTCServer (weblogic 9.2MP2)

using weblogic 9.2MP2 on both unix/windows....
configuring offline with WLST script and using the assign command to associate resources. works fine except for with the WTCServer bean. the python script first creates the WTCServer bean and directly afterward runs an assign:
assign('WTCServer','TestWTCServer','Target','appserver1)
however get the following error (via WLSTException):
WLSTException: ScriptException: Unable to find the specified application or service
have placed the following statement in another test script:
readDomain(<path to configuraiton>)
assign('WTCServer','TestWTCServer','Target','appserver1)
print 'assign completed'
exit()
which works fine. have even run the assign command later on in the main python script just to make sure the assign statement didn't come to fast after the mbean create for the WTCServer. same error.
anybody else had a similar problem?

Does the failure occur if appserver1 is defined before the WLST script is
run?
<Matthew Young> wrote in message news:[email protected]..
had to test the following script just to see if i made a dumb post:
readTemplate('C:/bea/weblogic92/common/templates/domains/wls.jar')
create('appserver1','Server')
print 'created appserver1'
create('myWTCServer', 'WTCServer')
print 'created myWTCServer'
#assign('WTCServer','myWTCServer','Target','AdminServer')
#print 'assigned myWTCServer to AdminServer'
assign('WTCServer','myWTCServer','Target','appserver1')
print 'assigned myWTCServer to appserver1'
exit()
same error. if i comment the assignment to appserver1 and replace it with
AdminServer everything works fine. smells like a bug or a complete
misunderstanding of the assign statement.

WebLogic 9.2MP2.Messages Pending topic count JMS display negative value

Similar Messages

Maybe you are looking for