Messaging Bridge & Managed Server
Hi,
I am trying to use the messaging bridge in a cluster
(WLS61SP3 with CR081404_61sp3.jar + CR081511_61sp3.jar),
but I am getting the following error on startup of one
of my managed servers (error attached).
What am I doing wrong here?
Regards,
-Per
[error.txt]
Hi,
Came up with the idea of putting the jmsadapter.jar archive (included in the jms-xa-adp.rar
archive) in the system classpath,
of my managed servers.
This was mentioned in a previous posting I found, and now it seems to be working...
-Per
####<12.sep.02 09:34:18 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! creating bridge
bridgeOne>
####<12.sep.02 09:34:21 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge bridgeOne's
source properties are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = t3://localhost:7011
DestinationType = Queue
DestinationJNDIName = XmlQueue2
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = connFac>
####<12.sep.02 09:34:21 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge bridgeOne's
target properties are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = t3://localhost:8011
DestinationType = Queue
DestinationJNDIName = queue
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = connFac>
####<12.sep.02 09:34:21 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge bridgeOne
is successfully initialized>
####<12.sep.02 09:34:21 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<main> <system> <> <200004> <Messaging Bridge "bridgeOne" has been successfully
deployed.>
####<12.sep.02 09:34:25 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200012> <Bridge
"bridgeOne" suceesfully found the two adapters configured for it.>
####<12.sep.02 09:34:25 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging STARTUP! BridgeBridge bridgeOne forwarding policy is AUTO>
####<12.sep.02 09:34:25 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200033> <Bridge
"bridgeOne" is getting the connections to the two adapters.>
####<12.sep.02 09:34:25 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Getting source connection>
####<12.sep.02 09:34:26 CEST> <Notice> <WebLogicServer> <6S19FHGZN2CM> <serverone>
<ListenThread> <system> <> <000202> <ListenThread listening on port 7011>
####<12.sep.02 09:34:26 CEST> <Notice> <WebLogicServer> <6S19FHGZN2CM> <serverone>
<SSLListenThread> <system> <> <000202> <SSLListenThread listening on port 7012>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:26 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:28 CEST> <Info> <Management> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'1' for queue: '__weblogic_admin_rmi_queue'> <system> <> <141060> <Reconnected
to Admin Server running at http://6S19FHGZN2CM:7001 from Managed Server - serverone.>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190035> <There was/were 1 physical
connection(s) created with the following Meta Data: Product name of EIS instance:
Java Messaging Service Product version of EIS instance: 1.0.2 Maximum number of
connections supported from different processes: 0 User name for connection: system>
####<12.sep.02 09:34:29 CEST> <Notice> <Cluster> <6S19FHGZN2CM> <serverone> <main>
<system> <> <000102> <Listening for multicast messages (cluster MyCluster) on
port 7011 at address 224.0.0.1>
####<12.sep.02 09:34:29 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Successfully got connection to the
source destination>
####<12.sep.02 09:34:29 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Getting target connection>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:29 CEST> <Notice> <WebLogicServer> <6S19FHGZN2CM> <serverone>
<main> <system> <> <000330> <Started WebLogic Managed Server "serverone" for domain
"dmsdomain" running in Production Mode>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190011> <Unable to locate context:
java:/comp/env/wls-connector-resref>
####<12.sep.02 09:34:29 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190010> <Unable to determine Resource
Principal for Container Managed Security Context.>
####<12.sep.02 09:34:30 CEST> <Info> <Connector> <6S19FHGZN2CM> <serverone> <ExecuteThread:
'0' for queue: 'MessagingBridge'> <system> <> <190035> <There was/were 1 physical
connection(s) created with the following Meta Data: Product name of EIS instance:
Java Messaging Service Product version of EIS instance: 1.0.2 Maximum number of
connections supported from different processes: 0 User name for connection: system>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne Successfully got connection to the
target destination>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne: both source and target adapters support
XA = true>
####<12.sep.02 09:34:30 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200032> <Bridge
"bridgeOne" is configured not to allow degradation of its quality of service in
cases where the configured quality of service is not reachable.>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne supportsMDBTX = true supportsXA = true
async = true>
####<12.sep.02 09:34:30 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006> <Messaging
Bridge Debugging RUNTIME! Bridge bridgeOne WorkMode = Exactly-once>
####<12.sep.02 09:34:30 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200030> <Bridge
"bridgeOne" is configured to work in "Exactly-once" mode and it is actually working
in "Exactly-once" mode.>
####<12.sep.02 09:34:30 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200028> <Bridge
"bridgeOne" starts transferring messages.>
####<12.sep.02 09:35:29 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <> <> <200027> <Bridge "bridgeOne"
works in asynchronous mode and has not received messages for the predefined maximum
idle time. The connections to the adapters will be interrupted and re-established.>
####<12.sep.02 09:35:29 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <> <> <200020> <Bridge "bridgeOne"
is stopped.>
####<12.sep.02 09:35:29 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM> <serverone>
<ExecuteThread: '0' for queue: 'MessagingBridge'> <> <> <200033> <Bridge "bridgeOne"
is getting the connections to the two adapters.>
"Per Mengshoel" <[email protected]> wrote:
>
>Hi,
>
>I got the patch, but didn't quite succeed in configuring
>it... I am getting exceptions in the managed server's log.
>
>Ideas?
>-Per
>
>####<12.sep.02 08:44:58 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! creating
>bridge
>bridgeOne>
>####<12.sep.02 08:44:59 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge
>bridgeOne's
>source properties are:
> AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
> Classpath=null
> ConnectionURL = t3://localhost:7011
> DestinationType = Queue
> DestinationJNDIName = XmlQueue2
> InitialContextFactory = weblogic.jndi.WLInitialContextFactory
> ConnectionFactoryJNDIName = connFac>
>####<12.sep.02 08:44:59 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge
>bridgeOne's
>target properties are:
> AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
> Classpath=null
> ConnectionURL = t3://localhost:8011
> DestinationType = Queue
> DestinationJNDIName = queue
> InitialContextFactory = weblogic.jndi.WLInitialContextFactory
> ConnectionFactoryJNDIName = connFac>
>####<12.sep.02 08:44:59 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200006> <Messaging Bridge Debugging STARTUP! Bridge
>bridgeOne
>is successfully initialized>
>####<12.sep.02 08:44:59 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><main> <system> <> <200004> <Messaging Bridge "bridgeOne" has been successfully
>deployed.>
>####<12.sep.02 08:44:59 CEST> <Info> <HTTP> <6S19FHGZN2CM> <serverone>
><main>
><system> <> <101133> <Initializing WEB server serverone>
>####<12.sep.02 08:45:01 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200012>
><Bridge
>"bridgeOne" suceesfully found the two adapters configured for it.>
>####<12.sep.02 08:45:02 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006>
><Messaging
>Bridge Debugging STARTUP! BridgeBridge bridgeOne forwarding policy is
>AUTO>
>####<12.sep.02 08:45:02 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200033>
><Bridge
>"bridgeOne" is getting the connections to the two adapters.>
>####<12.sep.02 08:45:02 CEST> <Debug> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200006>
><Messaging
>Bridge Debugging RUNTIME! Bridge bridgeOne Getting source connection>
>
>####<12.sep.02 08:45:02 CEST> <Info> <MessagingBridge> <6S19FHGZN2CM>
><serverone>
><ExecuteThread: '0' for queue: 'MessagingBridge'> <system> <> <200042>
><Bridge
>"bridgeOne" failed to connect to the source destination and will try
>again in
>20 seconds. (java.lang.Exception: javax.resource.ResourceException: Problem
>granting
>connection request to a ManagedConnectionFactory which does not exist
>in connection
>pool. Check your MCF's hashcode()
> at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:149)
> at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:20)
> at weblogic.jms.adapter.JMSBaseConnectionFactory.getSourceConnection(JMSBaseConnectionFactory.java:97)
> at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:696)
> at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:901)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>)>
>
>
>"Dongbo Xiao" <[email protected]> wrote:
>>This is a known problem in the adapter deployment area.
>>Contact BEA customer support and ask about CR083563.
>>
>>Dongbo
>>
>>"Per Mengshoel" <[email protected]> wrote in message
>>news:[email protected]...
>>>
>>> Hi,
>>>
>>> I am trying to use the messaging bridge in a cluster
>>> (WLS61SP3 with CR081404_61sp3.jar + CR081511_61sp3.jar),
>>> but I am getting the following error on startup of one
>>> of my managed servers (error attached).
>>>
>>> What am I doing wrong here?
>>>
>>> Regards,
>>> -Per
>>>
>>>
>>
>>
>
Similar Messages
-
Warning message for Managed server
Hi,
I am using weblogic 11g and OS is LINUX.
I am getting warning message for my managed server as "ThreadPool has stuck threads".
And values of "Self-Tuning Thread Pool" are
Active Execute Threads : 17
Execute Thread Total Count : 17
Execute Thread Idle Count : 8
Queue Length : 0
Pending User Request Count : 0
Completed Request Count : 18529
Hogging Thread Count: 6
Standby Thread Count: 0
Throughput : 13.486513486513486
and thread dump is
"main" waiting for lock weblogic.t3.srvr.T3Srvr@4c704c70 WAITING native
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:849)
weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:465)
weblogic.Server.main(Server.java:67)
"JIT Compilation Thread" RUNNABLE
null
"Signal Dispatcher" RUNNABLE native
com.ibm.misc.SignalDispatcher.waitForSignal(Native Method)
com.ibm.misc.SignalDispatcher.run(SignalDispatcher.java:54)
"Gc Slave Thread" RUNNABLE
null
"Gc Slave Thread" RUNNABLE
null
"Gc Slave Thread" RUNNABLE
null
"Thread-4" waiting for lock java.util.Timer$TimerImpl@13ee13ee WAITING native
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
java.util.Timer$TimerImpl.run(Timer.java:210)
"Thread-5" waiting for lock java.util.Timer$TimerImpl@344a344a TIMED_WAITING native
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:196)
java.util.Timer$TimerImpl.run(Timer.java:230)
"[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE native
"[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@4a2f4a2f WAITING native
"[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE native
"[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE native
"[STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE native
"[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock [email protected]238d2 TIMED_WAITING native
"[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@63776377 WAITING native
"[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE native
"[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@b230b23 WAITING native
"[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@6d096d09 WAITING native
"[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE native
"[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@8ee08ee WAITING native
"[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@64426442 WAITING native
"[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" RUNNABLE native
"[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@7a087a08 WAITING native
"[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@35d035d WAITING native
"[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.work.ExecuteThread@6300630 WAITING native
Please suggest me how to resolve this issue.Hi,
The problem is that the <b>directory /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/</b> does not exist at the node, because we have move it to <b>/appl/webdbus/</b> instead of <b>/appl/webbus/</b>. The question is why applications need to create adminServerDevel/upload directory and how can override it.
Thanks in advanced -
Warning message at managed server start up for an EAR application
Hi all, I have an wli <b>cluster 8.1 sp3 running on AIX</b> machines. When i deploy an <u>webservice application</u> (ear) i get an exception in the node which does not host admin server. The strange thing is that the application seems to be deployed correctly. My suspicion, about the exception, is the it's caused by the different directory structure of the two nodes. As you can see at bold words, weblogic tries to create ear at a directory that does not exist at this node. It finds the latter webbus from the path of admin server at the other machine. My question is straightforwad, Can we have different paths at cluster nodes ? In this case, Should we deploy ear (webservice application) in a different way ? <Feb 22, 2005 12:33:26 PM EET> <Info> <Deployer> <BEA-149060> <Module faxManWeb of application faxManAppl successfully transitioned from prepared to active on server wliBusServerPatmosDevel.> <b>javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/adminServerDevel/upload/faxManAppl/faxManAppl.ear</b> at weblogic.management.internal.BootStrap.apply(BootStrap.java:580) at weblogic.management.internal.BootStrap.apply(BootStrap.java:474) at weblogic.management.mbeans.custom.Application.getFullPath2(Application.java:3476) at weblogic.management.mbeans.custom.Application.getFullPath(Application.java:3055) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java(Compiled Code)) at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Inlined Compiled Code)) at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java(Compiled Code)) at weblogic.management.configuration.ApplicationMBean_Stub.getFullPath(ApplicationMBean_Stub.java:543) at com.bea.wli.broker.manifest.ApplicationManager.load(ApplicationManager.java:71) at com.bea.wli.broker.MessageBroker.registerApplication(MessageBroker.java:999) at com.bea.wli.management.WLIAppListener$1.run(WLIAppListener.java:294) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at com.bea.wli.management.WLIAppListener.applicationInitialized(WLIAppListener.java:290) at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:46) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721) at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2201) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2094) at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:2976) at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751) at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359) at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361) at weblogic.Server.main(Server.java:32) --------------- nested within: ------------------ weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception: [javax.management.InvalidAttributeValueException: Unable to create path to /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/adminServerDevel/upload/faxManAppl/faxManAppl.ear] at weblogic.management.mbeans.custom.Application.getFullPath2(Application.java:3479) at weblogic.management.mbeans.custom.Application.getFullPath(Application.java:3055) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at weblogic.management.internal.DynamicMBeanImpl.getAttribute(DynamicMBeanImpl.java(Compiled Code)) at weblogic.management.internal.ConfigurationMBeanImpl.getAttribute(ConfigurationMBeanImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Compiled Code)) at com.sun.management.jmx.MBeanServerImpl.getAttribute(MBeanServerImpl.java(Inlined Compiled Code)) at weblogic.management.internal.RemoteMBeanServerImpl.getAttribute(RemoteMBeanServerImpl.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java(Compiled Code)) at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java(Compiled Code)) at weblogic.management.configuration.ApplicationMBean_Stub.getFullPath(ApplicationMBean_Stub.java:543) at com.bea.wli.broker.manifest.ApplicationManager.load(ApplicationManager.java:71) at com.bea.wli.broker.MessageBroker.registerApplication(MessageBroker.java:999) at com.bea.wli.management.WLIAppListener$1.run(WLIAppListener.java:294) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at com.bea.wli.management.WLIAppListener.applicationInitialized(WLIAppListener.java:290) at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:46) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721) at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2201) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2146) at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2094) at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:2976) at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751) at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359) at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229) at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131) at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361) at weblogic.Server.main(Server.java:32)
Hi,
The problem is that the <b>directory /appl/webbus/bea/user_projects/domains/ITIC-DEVEL-WLI/</b> does not exist at the node, because we have move it to <b>/appl/webdbus/</b> instead of <b>/appl/webbus/</b>. The question is why applications need to create adminServerDevel/upload directory and how can override it.
Thanks in advanced -
Messaging Bridge Migration to other Managed Server
Hi
I had encountered a difficulty when I deployed the Messaging Bridge using the
Migratable Target. The Messaging Bridge stop function with no exception. I had
double check that in my Managed Server (serverA) I had set the Migratable Target
ServerA (Migratable) preferable to serverA itself. However if I deployed the
Messaging Bridge to serverA directly it works perfectly. Can anyone share some
ideas that I can setup the Bridge in order I can failover the Bridge from one
Managed Server to another Managed Server manually without restart any Managed
Servers?
Thanks
Stephen
hi,
this is file from - .../new-admin-server/config-store/server-farm.xml
in the .../old-admin-server/config-store/server-farm.xml it was not glass it was "rama1" of course.
i've edit this manually
i can deploy, stop-start instance from new-admin-server
<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright 2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
-->
<server-farm>
<admin-server>glass</admin-server>
<node>
<host>glass</host>
<port>8989</port>
<description>This is the Administration Server node</description>
</node>
<node>
<host>kuku</host>
<port>8989</port>
</node>
</server-farm> -
When restarting server after a crash, Messaging bridges are not starting
Hi,
We have Messaging bridge configured with Exactly-Once QOS to read messages from IBM Websphere MQ to Weblogic distributed Queue. We are using Weblogic 10gR3.
1. We killed the weblogic server which was reading message from source destination(IBM MQ). We did this to check whether any message is lost when a server crashes.
2. Then we restarted the weblogic application server and checked the weblogic messaging bridge status.
3. The messaging bridge was not started properly and the following Exception was thrown.
####<Apr 22, 2010 4:09:11 PM BST> <Error> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-056A9014D88E2BE368B7> <> <12312323333> <BEA-200015> <An error occurred in bridge "BRIDGE" during the transfer of messages (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:941)
at weblogic.transaction.internal.XAResourceDescriptor.startResourceUse(XAResourceDescriptor.java:630)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1116)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:275)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:511)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:438)
at weblogic.connector.transaction.outbound.XATxConnectionHandler.enListResource(XATxConnectionHandler.java:118)
at weblogic.connector.outbound.ConnectionWrapper.invoke(ConnectionWrapper.java:218)
at $Proxy87.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1427)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
.).>
####<Apr 22, 2010 4:09:11 PM BST> <Warning> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1271948951881> <BEA-200026> <Bridge "BRIDGE" 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 weblogic.jms.bridge.internal.MessagingBridgeException.)>
####<Apr 22, 2010 4:09:12 PM BST> <Info> <MessagingBridge> <machineA> <desb03-ms11> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1271948952726> <BEA-200020> <Bridge "BRIDGE" is stopped.>
Please give your suggestions to fix this issue.
Thanks!
Edited by: user11340353 on 28-Apr-2010 06:34Hi,
*The server was started in warning mode and the JTA was declared unhealthy. I saw 2 transaction alive for more than 2000 seconds which is uncommon.
*The resource adaptor was started properly.
*We are using file store. But will it make a difference?
Thanks! -
Getting error message while strating managed server in weblogic console.
Hi,
Here are my config steps I followed:
1. Created Domain with the Admin server port 8001.
2. Able to log into the Admin console successfully.
3. Created Machine in the console
4. Created Managed server ms01.
5. Created Network Channels under ms01 for http and https with different ports.
6. Started node manager
7. Started ms01 and status shows RUNNING.
8. Deployed one sample war file on this ms01. Deployment was successful.
9. Tried to access the application which is deployed, white page is displayed. But same app I was able to access before, so its clear nothing wrong in war file.
10. I rebooted wls after this and tried restarting managed server, but stuck at this point because of below error.
At this point I could see error message in the wls log.
like:
<Error> <NodeManager> <BEA-300033> <Could not execute command "getVersion" on the node manager. Reason: "Connection refused: connect. Could not connect to NodeManager. Check that it is running at localhost:5,556.".>
<Error> <NodeManager> <BEA-300033> <Could not execute command "getNMLog" on the node manager. Reason: "Connection refused: connect. Could not connect to NodeManager. Check that it is running at sdc78197svod.corp.siebel.com:5,556.".>
I tried rebooting wls, did not work out.
Any help on this appreciated.
ThanksIs the node manager running at sdc78197svod.corp.siebel.com:5,556 ? YOu can do a telnet to this IP, port to confirm.
-
Error when starting managed server Message Too Long
Hi,
I'm trying to setup clustering with WLS6.1sp2.
I use the jdk include with wls
2 servers in the cluster OS=AIX
1 Adminserver running on Solaris 8
When I start a managed server on one of the clustered machines
I see the following error.
Starting Cluster Service ....
<Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread listening
on port 7001, ip address 10.160.3.74>
<Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast message:
java.io.IOException: Message too long
java.io.IOException: Message too long
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
at java.net.DatagramSocket.send(DatagramSocket.java:341)
at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
Code))
at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
>
<Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast messages
(cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
<Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic Managed
Server "s01ap007" for domain "axa" running in Production Mode>
Also deploying doesn't seem to succeed could this be coused by this error
I hope someone can help me.
Best regards,
Peter Van der Goten
Because I found the answer via Mr. yunyee who also had this problem on an AIX machine
I will post this also here.
The problem was that the upd_sendspace variable was set on
a mutch to low value (9126) or something in this range
It had to be set on 32769.
this was done with no -o udp_sendspace=32769
Best regards,
Peter
"Peter Van der Goten" <[email protected]> wrote:
>
>Hi,
>I'm trying to setup clustering with WLS6.1sp2.
>I use the jdk include with wls
>2 servers in the cluster OS=AIX
>1 Adminserver running on Solaris 8
>
>When I start a managed server on one of the clustered machines
>I see the following error.
>Starting Cluster Service ....
><Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread
>listening
>on port 7001, ip address 10.160.3.74>
><Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast
>message:
>java.io.IOException: Message too long
>java.io.IOException: Message too long
> at java.net.PlainDatagramSocketImpl.send(Native Method)
> at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
> at java.net.DatagramSocket.send(DatagramSocket.java:341)
> at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
> at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
> at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
>Code))
> at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
> at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
> at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
> at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
> at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
> at weblogic.Server.main(Server.java:35)
>>
><Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast
>messages
>(cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
><Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic
>Managed
>Server "s01ap007" for domain "axa" running in Production Mode>
>
>Also deploying doesn't seem to succeed could this be coused by this error
>
>I hope someone can help me.
>Best regards,
>Peter Van der Goten
>
-
Error occured in Message Bridging in Weblogic to MQ Server
Hi,
I am trying to send the message from weblogic JMS to MQ Server Queue using Message Bridging. All the configuration has been done in both Weblogic and MQ Server. Once creating the bridge, i am getting the following error.
<Feb 22, 2006 9:37:18 PM GMT+05:30> <Warning> <Connector> <BEA-190032> << Weblog
ic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAl
locationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
--Please give me the suggestion to fix this.
Thanks in Advance,
Sureshkannan NagarajanHello Priya
If u r loading thru flat file
1. Check the correct path in infopackage
2. Check if it is opened,if it is then close it and run package again
If loading thru R/3
1. Check DS is not opened in change mode
2. Check if RSA3 is able to extract data...if it is then check in RSA7 and chk IDOC status...
3. Are you running init..then make sure no document is posted in R/3 side...
Thanks
Tripple k -
Foreign JMS Server vs Messaging bridge
Could any body tell me which one is the best Whether Foreign JMS Server or Messaging bridge for connecting Weblogic to IBM MQ Series.I am trying to use foreign jms server but i dont know how to post the message to that queue i created in foreign jms server..
Hi,
For sending messages non-transactionally, foreign JMS server is sufficient. For sending messages transactionally using standard JTA transactions, the simplest way is to send them on the server and reference the foreign JMS through an EJB resource reference. See the the following FAQ for a walk-through of the various options, including guidance on when to use a bridge:
http://e-docs.bea.com/wls/docs81/faq/interop.html
Tom -
Messaging Bridge/Foreign JMS Server
Can someone clarify what is the difference in using messaging bridge or Foreign JMS Server in listening to a topic from other weblogic server of same version.
Edited by: user11359157 on 6 Jul, 2009 3:17 PMI always thought one has to use remote classes from the foreign JMS server in local the classpath to send or receive messages stored at
the foreign JMS server / the remote side.
<Jayesh> that is true of the remote side of the JMS is non-weblogic. </Jayesh>
Also in the WLS bridge this can be specified. IMHO the bridge has the advantage that I can use the wls classe and the bridge knows
the classpath and bridges to the foreign jms server, so the application developer doesn't have to use foreign classes, eg. tibco or mq.
<Jayesh> When you have remote JMS is WebLogic it is obvious considering that both remote and local jms uses same weblogic classes. </Jayesh>
Now, where does this happen for the foreign jms server (which is kind of alternative to wls bridge, without store and forward)?
All I can see is a local JNDI lookup being translated to a remote one.
Is really the local JMS implementation used to talk to the remote JMS server?
When a JNDI lookup for a queue happens will then be WLS queue implementation returned?
<Jayesh> No there is not local JMS store is used. Foreign JMS server just provides administrative convenience by moving remote JMS destination JNDI definitions in local JNDI definition. It allows to use this local definition by all EJBs, servlets and messaging bridges. If the remote definitions changes you can change those definition in admin console and does not need change in deployment descriptors of the EJBs and servlets to prevent redeployment. Again this is no administrative convenience and during run time it will behave exactly same as you are sending or receiving message directly from remote JMS destination.
</Jayesh>
Hope this clears confusion.
jayesh@yagna -
Unable to recieve multi cast messages managed server failure
Environment: WL Server 10.3. OS - Suse 11.1. X86 standalone box.
I am trying to start a managed server via startManagedWebLogic ms1 http://localhost:7001" and getting the exception shown below. I have set my cluster as multicast. Any tips are appreciated.
<Jan 8, 2009 7:14:39 PM MST> <Critical> <Health> <BEA-310006> <Critical Subsystem Cluster has failed. Setting server state to FAILED.
Reason: Unable to receive self generated multicast messages>
<Jan 8, 2009 7:14:39 PM MST> <Error> <> <BEA-000000> <
===== FULL THREAD DUMP ===============
Thu Jan 8 19:14:39 2009
BEA JRockit(R) R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32
"Main Thread" id=1 idx=0x4 tid=24837 prio=5 alive, in native, waiting
-- Waiting for notification on: weblogic/t3/srvr/SubsystemRequest@0x11814988[fat lock]
at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
at java/lang/Object.wait(J)V(Native Method)
at weblogic/t3/srvr/SubsystemRequest.rendezvouz(SubsystemRequest.java:100)
^-- Lock released while waiting: weblogic/t3/srvr/SubsystemRequest@0x11814988[fat lock]
at weblogic/t3/srvr/SubsystemRequest.action(SubsystemRequest.java:81)
at weblogic/t3/srvr/SubsystemRequest.start(SubsystemRequest.java:51)
at weblogic/t3/srvr/ServerServicesManager.startService(ServerServicesManager.java:457)
at weblogic/t3/srvr/ServerServicesManager.resume(ServerServicesManager.java:275)
^-- Holding lock: java/lang/Class@0x114ae0c0[biased lock]
at weblogic/t3/srvr/T3Srvr.resume(T3Srvr.java:776)
at weblogic/t3/srvr/T3Srvr.startup(T3Srvr.java:513)
at weblogic/t3/srvr/T3Srvr.run(T3Srvr.java:440)
at weblogic/Server.main(Server.java:67)
at jrockit/vm/RNI.c2java(IIIII)V(Native Method)
-- end of trace
Edited by: svachary on Jan 8, 2009 6:33 PMHi,
Please go through the following link once :-
Link :[http://support.bea.com/application_content/product_portlets/support_patterns/wls/Multicast_Pattern.html]
Also check if you have multiple NIC's on your box. In that case you need to specify a particular interface address to use for multicast traffic.
Regards. -
Messaging Bridge Between 2 Weblogic Server
Hi,
I would like to create a messaging bridge between two Weblogic Server on two different
server. One on Windows NT and one on Solaris.
I have created one queue on NT and one other queue on Solaris, and the corresponding
JMS Bridge destination for each queue on one server (and the other to test).
And on one server (and the other to test), I have created a messaging bridge to
transfert messages from one queue to the other, but I have a message on the Weblogic
Server.
javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
url = http://usv9007.rtc.ch:7001, user name = null, password = null
at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:978)
at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1708)
at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:163)
at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:126)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:733)
at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:899)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
<09.01.2003 13:48:51 CET> <Error> <Connector> <190006> <Error granting connection
request.>
Parameter for the distant queue
Adapter JNDI Name : eis.jms.WLSConnectionFactoryJNDIXA (I have activated the XA
ressources for the ConnectionFactory and the corresponding adapter)
Connection URL : http://SolarisIP:7001
InitialContextFactory : weblogic.jndi.WLInitialContextFactory
ConnectionFactory JNDI Name : myConnectionFactory
Destination JNDI Name : myQueueSolaris
Destination Type : Queue
I don't understand why I have this error, because all the parameters are correct,
and the http tunneling is activated.
Could you help me to configure correctly this messaging bridge ???
Thanks a lot.
Looks like the error occurred on the target destination
of the bridge. One way to find out if your configuration
is correct is to use the same parameters (initial context factory,
url, username and password) to get a connection to the
target server from a standalone client.
Dongbo
Seb wrote:
>
> Hi,
>
> I would like to create a messaging bridge between two Weblogic Server on two different
> server. One on Windows NT and one on Solaris.
>
> I have created one queue on NT and one other queue on Solaris, and the corresponding
> JMS Bridge destination for each queue on one server (and the other to test).
>
> And on one server (and the other to test), I have created a messaging bridge to
> transfert messages from one queue to the other, but I have a message on the Weblogic
> Server.
>
> -----------------------------------------------------------------
> javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
> ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
> url = http://usv9007.rtc.ch:7001, user name = null, password = null
> at weblogic.connector.common.internal.ConnectionPool.makeResources(ConnectionPool.java:978)
> at weblogic.connector.common.internal.ConnectionPool.getConnection(ConnectionPool.java:1708)
> at weblogic.connector.common.internal.ConnectionPoolManager.getConnection(ConnectionPoolManager.java:163)
> at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:25)
> at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:126)
> at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:733)
> at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.java:899)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
> <09.01.2003 13:48:51 CET> <Error> <Connector> <190006> <Error granting connection
> request.>
> -----------------------------------------------------------------
>
> Parameter for the distant queue
>
> Adapter JNDI Name : eis.jms.WLSConnectionFactoryJNDIXA (I have activated the XA
> ressources for the ConnectionFactory and the corresponding adapter)
> Connection URL : http://SolarisIP:7001
> InitialContextFactory : weblogic.jndi.WLInitialContextFactory
> ConnectionFactory JNDI Name : myConnectionFactory
> Destination JNDI Name : myQueueSolaris
> Destination Type : Queue
>
> I don't understand why I have this error, because all the parameters are correct,
> and the http tunneling is activated.
>
> Could you help me to configure correctly this messaging bridge ???
>
> Thanks a lot.
-
I am a Creative Cloud subscriber [limited to photoshop/ lightroom/ bridge] . I keep getting messages to manage my account on pain of being cut off. Why? There doesn't seem anything to manage -payments are being made through visa on monthly basis.
Online Chat Now button near the bottom for Activation and Deactivation problems may help
http://helpx.adobe.com/x-productkb/policy-pricing/activation-deactivation-products.html -
Error message seen when starting a managed server (dsp_config.ear)
Hi ,
I am having issues when i start the managed server under the admin server.
Seems like when i undeploy dsp_config.ear the managed server seems to start without any issues.
But since the dsp_config.ear is removed the dspconsole is messed up.
The admin server runs fine without any issues with or without dsp_config.ear deployment.
The error trace
####<Jul 27, 2009 9:36:01 AM EDT> <Warning> <DeploymentService> <wdcsn383a> <cashflow1MS1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (
self-tuning)'> <<WLS Kernel>> <> <> <1248701761543> <BEA-290064> <Deployment service servlet encountered an Exception while handling the deployment service m
essage for request id "-1" from server "BEAAdminServer". Exception is: "java.lang.ClassNotFoundException: com.bea.wli.config.deployment.server.ServerVersion:
This error could indicate that a component was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed o
n a server that is part of a cluster is also deployed on all other members of that cluster
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:218)
at weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:85)
at weblogic.common.internal.WLObjectInputStream.resolveClass(WLObjectInputStream.java:61)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at java.util.HashMap.readObject(HashMap.java:1030)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.deploy.service.internal.DomainVersion.readExternal(DomainVersion.java:180)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.deploy.service.internal.transport.DeploymentServiceMessage.readMessage(DeploymentServiceMessage.java:325)
at weblogic.deploy.service.internal.transport.DeploymentServiceMessage.readExternal(DeploymentServiceMessage.java:301)
at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.handleDeploymentServiceMessage(DeploymentServiceServlet.java:618)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.internalDoPost(DeploymentServiceServlet.java:235)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.access$000(DeploymentServiceServlet.java:77)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet$1.run(DeploymentServiceServlet.java:210)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.deploy.service.internal.transport.http.DeploymentServiceServlet.doPost(DeploymentServiceServlet.java:207)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
Can anybody help me on this one?
it seems more of ODSI issue than weblogic server issue.it sounds like you are deploying dsp_config.ear to a domain/server that is not ODSI-enabled.
com.bea.wli.config.deployment.server.ServerVersion is in <modules>/com.bea.common.configfwk.wlinterop_10.3.0.0.jar which is referenced by <modules>/features/odsi.server.modules_10.3.0.0.xml and used by com.bea.dsp.management.impl.DomainServiceImpl -
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….
Maybe you are looking for
-
Report ALV printing in background -display only 1 line for header
Hi, We are running a ALV report (transaction code ME2N) in background and when we get the Graphical display of the spool request, the number of columns of the header are limited and divided in 3 lines. It means that when exporting the report to exce
-
Using IO to create a Combo Box
Hello, I have failed to find any examples on how to do the following, and have not yet figured out how to do it msyelf. I want to add the entire contents of a file containg a list of people's personal numbers and their names to a combo box that is th
-
I cannot get access to my web server on my new Mac. I have finally gotten back to working on a Mac, after having to use Windows for work for a long time, but I cannot get ANY ftp client to access a server that I have been accessing for two years. I a
-
I show full wifi signal but pages won't load
I recently upgraded to Lion and I'm having internet connectivity problems. On my new macbook it shows I have full signal to my secured personal wifi network but nothing loads up on safari. This problem wasn't present when I was using Snow Leopard. My
-
Skype wont work on Leopard Snow MAC OSX 10.6
can anyone help please? Attachments: skype.jpg 126 KB