Unable to resolve 'weblogic.messaging.dispatcher.S:null'
We have a WLS 10.3 cluster with 1 admin server and 2 managed servers. Each managed server hosts JMS queues so we have a distributed queue environment. Applications periodically report an issue that prevents messages from being dropped onto the queues. The frequency of the issue is weekly and sometimes multiple times during the week. We have found that un-targeting and re-targeting the JMS Servers seems to resolve the problem (at least in the short term). The message producer applications are using the weblogic.jar and an xa connection factory. I've included the stack trace below. I'm hoping that someone can help uncover the root cause of the issue.
Stack Trace:
Caused by: weblogic.jms.common.JMSException: No failover destination.
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1275)
at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:783)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:394)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:384)
at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:597)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:574)
at org.springframework.jms.core.JmsTemplate$4.doInJms(JmsTemplate.java:551)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:471)
... 8 more
Caused by: weblogic.jms.common.JMSException: No failover destination.
at weblogic.jms.frontend.FEProducer.pickNextDestination(FEProducer.java:750)
at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:1092)
at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1399)
at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1460)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
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: weblogic.messaging.dispatcher.DispatcherException: could not find Server null
at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:176)
at weblogic.messaging.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:58)
at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreate(JMSDispatcherManager.java:219)
at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreateChecked(JMSDispatcherManager.java:230)
at weblogic.jms.frontend.FEProducer.findDispatcher(FEProducer.java:825)
at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:995)
... 9 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:null'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:null'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:172)
... 14 more
Hi,
I would suggest you to go through these 2 links which you give all the details about UDD
Topic:Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
http://middlewaremagic.com/weblogic/?p=3747
Topic:JMS Demo using WebLogic Uniform Distributed Queue (UDQ)
http://middlewaremagic.com/weblogic/?page_id=1976
Tips to solve UDQ issues
- Make sure the Server Affinity Enabled parameter should be un-checked (disable) which under the [ Connection factory –> Configuration (tab) –> Load Balance (sub-tab)]
- Disable the Server Affinity Enabled parameter for the connection factory whish is been used by your UDQ.
- All the managed servers are in the same cluster.
- If the managed serves are in different boxes make sure the listing address is given correctly which is under [ Machine –> Configuration (tab) –> Node Manager (sub-tab) ]
- Test if you are able to PING the servers on different boxes and make sure that there is no network issues and you are able to communicate with the servers.
Hope this helps you.
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…
Similar Messages
-
Weblogic.messaging.dispatcher.DispatcherException!!??
Hi,
I have the following piece of code extract which creates a JMS Session. I am looking up a queue from a WLS1032 to a WLS1033 (SOA Suite 11g) and publish messages to it.
if (remoteCtx == null || remoteJmsConnection == null || remoteQueue == null) {
setupRemoteJMSResources();
session = remoteJmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
sender = session.createProducer(remoteQueue);
private void setupRemoteJMSResources() throws NamingException, JMSException {
Hashtable<String, String> env = new Hashtable<String, String>();
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, soaProviderUrl);
env.put(Context.SECURITY_PRINCIPAL, username);
env.put(Context.SECURITY_CREDENTIALS, password);
remoteCtx = new InitialContext(env);
QueueConnectionFactory connectionFactory = (QueueConnectionFactory) remoteCtx.lookup(jmsRemoteCFName);
remoteJmsConnection = connectionFactory.createQueueConnection();
remoteQueue = (Queue) remoteCtx.lookup(remoteQueueName);
It has been working fine the last month but yesterday started to throw the following exception at the createSession() line.
I cannot find the cause of this exception and I would like to prevent it in the future. It is running on a WLS1032 in a SLSB.
Could anybody provide a hint of what could have caused this? Start/Stop of the application resolved the problem but I would like to further investigate it.
weblogic.messaging.dispatcher.DispatcherException: weblogic.messaging.dispatcher.DispatcherException: java.lang.Exception: Connection not found at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:116) at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45) at weblogic.jms.client.JMSConnection.setupJMSSession(JMSConnection.java:520) at weblogic.jms.client.JMSConnection.createSessionInternal(JMSConnection.java:488) at weblogic.jms.client.JMSConnection.createSession(JMSConnection.java:474) at weblogic.jms.client.WLConnectionImpl.createSession(WLConnectionImpl.java:553) at
Thank you in advance,
PetrosCheck the soa_prod_a1:soa_a2 logs during the timestamp Oct 21, 2014 5:55:54 PM issue occured.
The below error message tells us the remote JVM is down and inaccessible.
java.rmi.ConnectException: This RJVM has already been shutdown
Check if the below port numbers are listening on the below ipaddresses
172.28.164.137: 21801,
172.28.164.139: 21811:
Thanks,
Vijaya -
At startup: "Unable to resolve weblogic.jdbc.connectionPool"
WLS 6.0 SP1 on Solaris 8
Oracle 8.1.7 using JDBC Thin driver from Oracle.
At startup of WebLogic, just after WLS creates the pool, I get a JNDI
NameNotFoundException, as shown below.
However, this does not seem to cause any problems for us.
####<Jun 20, 2001 10:16:17 AM GMT+10:00> <Info> <JDBC Pool ora817Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Pool: 'ora817Pool'
will be tested at: '10 minute intervals.>
####<Jun 20, 2001 10:16:20 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:21 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:22 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:23 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <Adapter> <pssydsun01>
<myserver> <main> <system> <> <000000> <Exception thrown by rmi
server(class weblogic.jndi.internal.RootNamingNode)
[-4918694186591914732S:192.168.0.52:[7001,7001,7002,7002,7001,7002,-1]/9]:
weblogic.jndi.internal.RootNamingNode@1fea8a>
javax.naming.NameNotFoundException: Unable to resolve
weblogic.jdbc.connectionPool Resolved: 'weblogic' Unresolved:'jdbc' ;
remaining name 'connectionPool'
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
at
weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(RootNamingNode_WLSkel.java:230)Just installed SP2 on top of WebLogic Server 6.0 SP1.
I still get the same message in weblogic.log while it was starting up:
####<Jun 28, 2001 12:53:00 PM GMT+10:00> <Info> <WebLogicServer>
<pssydsun01> <myserver> <main> <> <> <000000> <IIOP subsystem enabled.>
####<Jun 28, 2001 12:53:10 PM GMT+10:00> <Info> <WebLogicServer>
<pssydsun01> <myserver> <main> <system> <> <000214> <WebLogic Server (6.0
Service Pack 2 05/24/2001 11:55:28 #117037) "myserver"
(c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000 BEA Systems, Inc.>
####<Jun 28, 2001 12:53:23 PM GMT+10:00> <Info> <JDBC Pool ora817Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Pool: 'ora817Pool'
will be tested at: '10 minute intervals.>
####<Jun 28, 2001 12:53:26 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:27 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:28 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:29 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:30 PM GMT+10:00> <Info> <JDBC Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Connection for pool
"ora817Pool" created.>
####<Jun 28, 2001 12:53:30 PM GMT+10:00> <Info> <Adapter> <pssydsun01>
<myserver> <main> <system> <> <000000> <Exception thrown by rmi
server(class weblogic.jndi.internal.RootNamingNode)
[7126974831161186990S:192.168.0.52:[7001,7001,7002,7002,7001,7002,-1]/9]:
weblogic.jndi.internal.RootNamingNode@504ec1>
javax.naming.NameNotFoundException: Unable to resolve jdbc. Resolved: ''
Unresolved:'jdbc' ; remaining name ''
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:803)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
Daniel Hoppe wrote:
Hi,
it's a problem in SP1, doesn't seem to cause any harm. Afaik it's fixed
in RP1 and in SP2
Daniel
-----Urspr?ngliche Nachricht-----
Von: Jesus M. Salvo Jr. [mailto:[email protected]]
Bereitgestellt: Mittwoch, 20. Juni 2001 02:17
Bereitgestellt in: jndi
Unterhaltung: At startup: "Unable to resolve
weblogic.jdbc.connectionPool"
Betreff: At startup: "Unable to resolve weblogic.jdbc.connectionPool"
WLS 6.0 SP1 on Solaris 8
Oracle 8.1.7 using JDBC Thin driver from Oracle.
At startup of WebLogic, just after WLS creates the pool, I get a JNDI
NameNotFoundException, as shown below.
However, this does not seem to cause any problems for us.
####<Jun 20, 2001 10:16:17 AM GMT+10:00> <Info> <JDBC Pool
ora817Pool>
<pssydsun01> <myserver> <main> <system> <> <000000> <Pool:
'ora817Pool'
will be tested at: '10 minute intervals.>
####<Jun 20, 2001 10:16:20 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:21 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:22 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:23 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <JDBC
Connection Pool>
<pssydsun01> <myserver> <main> <system> <> <000000>
<Connection for pool
"ora817Pool" created.>
####<Jun 20, 2001 10:16:24 AM GMT+10:00> <Info> <Adapter>
<pssydsun01>
<myserver> <main> <system> <> <000000> <Exception thrown by rmi
server(class weblogic.jndi.internal.RootNamingNode)
[-4918694186591914732S:192.168.0.52:[7001,7001,7002,7002,7001,
7002,-1]/9]:
weblogic.jndi.internal.RootNamingNode@1fea8a>
javax.naming.NameNotFoundException: Unable to resolve
weblogic.jdbc.connectionPool Resolved: 'weblogic' Unresolved:'jdbc' ;
remaining name 'connectionPool'
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundExceptio
n(BasicNamingNode.java:803)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingN
ode.java:209)
at
weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamin
gNode.java:129)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:496)
at
weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:500)
at
weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(RootNaming
Node_WLSkel.java:230) -
JMS Unable to resolve 'weblogic.jms.TempDestinationFactory' error!
We are running an application within the Weblogic 7.x EJB Framework. While trying
to connect to the application from our GUI I get the following error. **... Unable
to resolve 'weblogic.jms.TempDestinationFactory' Resolved: 'weblogic.jms' Unresolved:'TempDestinationFactory'
; We have configured our JMS server with two topics - one of which is used for
persistent storage (i.e has the 'store' configuration attribute set to TRUE).
Also we have configured NO stores but a JDBC Tx DataSource.
I would appreciate any suggestions.
**see attached picture**
[confui2.jpg]
In order to use WLS JMS temporary destinations, you have to have a temporary destination template configured for
the JMS server.
Dongbo
Puneet Bhatia wrote:
> We are running an application within the Weblogic 7.x EJB Framework. While trying
> to connect to the application from our GUI I get the following error. **... Unable
> to resolve 'weblogic.jms.TempDestinationFactory' Resolved: 'weblogic.jms' Unresolved:'TempDestinationFactory'
> ; We have configured our JMS server with two topics - one of which is used for
> persistent storage (i.e has the 'store' configuration attribute set to TRUE).
> Also we have configured NO stores but a JDBC Tx DataSource.
> I would appreciate any suggestions.
>
> **see attached picture**
>
> ------------------------------------------------------------------------
> Name: confui2.jpg
> confui2.jpg Type: JPEG Image (image/pjpeg)
> Encoding: base64
-
JNDI naming exception...unable to resolve 'weblogic.management.adminhome'
I'm able to start admin server and access admin console (web). When I try to connect to admin server from managed server using WLST, I'm getting the error "compatibility mbean server is not initialized properly....". I tried to ping admin server from managed server using WLST ping command (java weblogic.Admin -url xxxxx -username xxxx-password xxxx PING), I'm getting error "JNDI naming exception....unable to resolve 'weblogic.management.adminhome'".
In order to run it remotely, I need to manually export the EAR file from Eclipse, ftp to the remote server and deploy it to the managed server.
It seems that I missed some jar files in the managed server classpath. But, I don't know which. -
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…. -
Suppressing unable to resolve reference to parameter... message
We have converted our applications to Oracle 9I (Internet) from Oracle 5 (Client Server).
We force a closing of an extra browser window by creating a .pll with a customized function called close_browser which runs close.htm and then does an exit_form to replace exit_form. We have forms call other forms, if the form is called, then it checks a forms parameter called parameter.pr_called. We want to just modify the library and not modify 100s of forms but :parameter.pr_called does not exist in a number of forms but we need to check parameter.pr_called with a NAME_IN in the library just in case it is called so we don't close the browser window if the form is a called form. It would then simply exit form and go back to the original form. When we check for name_in('parameter.pr_called) = 'Y' to check for this condition, we get unable to resolve reference to parameter pr_called.
We have tried changing message levels, but that only works for error messages and not messages. There seems to be no programming way to do a find_parameter for a form parameter. Any suggestions on how to prevent the message from appearing. We would not want to modify all the forms.
Thank you,
- BrianIf you want to add this parameter to all your forms in batch - this is simple to do with the Java API - here's some sample code.
package oracle.forms.jdapi.demos;
import oracle.forms.jdapi.*;
public class AddParam
public AddParam(String formName, String parameterName, String parameterValue)
try
// Open the module - this implicitly starts JDAPI
FormModule form = FormModule.open(formName);
System.out.println("Processing " + form.getName());
// see if the parameter already exists
ModuleParameter param = null;
try
param = ModuleParameter.find(form, parameterName);
catch (JdapiException cjdex)
System.out.println("Parameter not present needs creating...");
if (param == null)
// create the required Param
param = new ModuleParameter(form,parameterName);
param.setParameterDataType(JdapiTypes.PADA_CHARACTER_CTID);
param.setMaximumLength(3); //assuming Y/N, YES/NO??
param.setParameterInitializeValue(parameterValue);
System.out.println("Parameter created...");
//we've made a change so save...
form.save(formName);
System.out.println("Form Saved...");
else
System.out.println("Parameter already exists...");
form.destroy();
Jdapi.shutdown();
catch (JdapiException jdex)
System.out.println(jdex.toString());
* @param Pass the name of the Form as an agument to the class
public static void main(String[] args)
String paramName = "PR_CALLED";
String paramDefaultValue = "N";
AddParam addParam = new AddParam(args[0], paramName, paramDefaultValue);
System.exit(0);
} -
Unable to resolve JNDI DataSource in weblogic 12c When you upgrade web application
I create a datasource which jndi name is jdbc/allianzB2CDataSource and the target is AdminServer ,and i deploy a web application in AdminServer.In that web application,the code(base on spring framework) is:
public static DataSource getJndiDataSource(String name) {
JndiDataSourceLookup dsLookup = new JndiDataSourceLookup();
Properties jndiEnvironment = new Properties();
jndiEnvironment.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
dsLookup.setJndiEnvironment(jndiEnvironment);
try {
dsLookup.setResourceRef(false);
return dsLookup.getDataSource(name);
} catch (Exception e) {
dsLookup.setResourceRef(true);
return dsLookup.getDataSource(name);
And the parameter is jdbc/allianzB2CDataSource,everything work fine,but when i restart or upgrate the web application,i got the error like this:
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'
Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'I create a datasource which jndi name is jdbc/allianzB2CDataSource and the target is AdminServer ,and i deploy a web application in AdminServer.In that web application,the code(base on spring framework) is:
public static DataSource getJndiDataSource(String name) {
JndiDataSourceLookup dsLookup = new JndiDataSourceLookup();
Properties jndiEnvironment = new Properties();
jndiEnvironment.put("java.naming.factory.initial",
"weblogic.jndi.WLInitialContextFactory");
dsLookup.setJndiEnvironment(jndiEnvironment);
try {
dsLookup.setResourceRef(false);
return dsLookup.getDataSource(name);
} catch (Exception e) {
dsLookup.setResourceRef(true);
return dsLookup.getDataSource(name);
And the parameter is jdbc/allianzB2CDataSource,everything work fine,but when i restart or upgrate the web application,i got the error like this:
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource'
Unable to resolve 'jdbc.allianzB2CDataSource'. Resolved 'jdbc'; remaining name 'allianzB2CDataSource' -
Hi,
I am not able to resolve the JNDI name - ATGProductionDS
I have used CIM to create this and i am using ATG10.2 with MYSQL as my database and weblogic.
/atg/epub/file/ConfigFileSystem journaling file system started: vfs=file:/C:
/Stixs/ATG/ATG10.2/home/PublishingAgent/deploymentconfig/live/config/ journalDirectory=C:\Stixs\ATG\ATG10.2\home\PublishingAgent\deploymentc
onfig\data\config
**** Error Fri Dec 27 20:58:35 EST 2013 1388195915495 /atg/dynamo/service/jdbc/DirectJTDataSource Failed to resolve ATGProduct
ionDS javax.naming.NameNotFoundException: Unable to resolve 'ATGProductionDS'. Resolved ''; remaining name 'ATGProductionDS'
**** Error Fri Dec 27 20:58:35 EST 2013 1388195915495 /atg/dynamo/service/jdbc/DirectJTDataSource at weblogic.jndi.int
ernal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
**** Error Fri Dec 27 20:58:35 EST 2013 1388195915495 /atg/dynamo/service/jdbc/DirectJTDataSource at weblogic.jndi.int
Entries from Weblogic console -datasources
ATGBatchDS
Generic
ATGBatchDS
ATGProductionDS
Generic
ATGProductionDS
atg_production_lockserver, atg_publishing_lockserver
ATGPublishingDS
Generic
ATGPublishingDS
atg_publishing_lockserver
Please provide assistance.Hi,
if you click the "Control" tab for the ATGProductionDS datasource in the Weblogic console does it show the State as running?
Does the "Monitoring" tab for the datasource show the State as running? If you click on the "Testing" tab can you test the datasource successfully?
If you inspect the Server using the Weblogic console there is a link "View JNDI Tree" If you click the link do you see the datasource listed in the left pane?
Do you see any errors for the ATGProductionDS in the Weblogic server log and out log files? -
Javax.naming.NameNotFoundException: Unable to resolve 'jppsacntrQ' Resolved: ''
Hi,
I have written a simple client to receive messages from a 'jppsacntrQ'
queue,
The jms server which keeps this queue is already targetted at the
server I am running.
I have closed my command prompt and restarted WLS a few times but I am
still getting this error.
Has anyone else encountered the same problem?
Appreciate the help ...
Victor
c:\program files\intellij-idea-3.0.4\jre\bin\java.exe -Xmx128M
-Djava.home=C:\Program Files\IntelliJ-IDEA-3.0.4\jre -classpath
c:\program files\intellij-idea-3.0.4\jre\lib\tools.jar;C:\Program
Files\IntelliJ-IDEA-3.0.4\lib\idea_rt.jar;C:\Program
Files\IntelliJ-IDEA-3.0.4\lib\ant.jar;C:\Program
Files\IntelliJ-IDEA-3.0.4\lib\optional.jar;C:\Program
Files\IntelliJ-IDEA-3.0.4\lib\\rt\xerces1.jar
com.intellij.rt.ant.execution.AntMain -logger
com.intellij.rt.ant.execution.IdeaAntLogger -verbose
-Dbuild.compiler.emacs=true -buildfile
C:\java-projects\portnet-jp\build.xml test-polling-subscriber
build.xml
test-polling-subscriber
java
Running Start Polling Task ...
DEBUG [main]: subscriber.propertyFile.path=C:/java-projects/portnet-jp/resources/configuration/JPContainer.cfg
DEBUG [main]: java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
DEBUG [main]: java.naming.provider.url=t3://localhost:7001
DEBUG [main]: java.naming.referral=throw
DEBUG [main]: java.naming.security.authentication=simple
DEBUG [main]: java.naming.security.principal=null
DEBUG [main]: java.naming.security.credentials=null
DEBUG [main]: sleepTimePerCycle=15000
DEBUG [main]: queueConnectionFactoryName=pnsgQCF
DEBUG [main]: incomingQueueName=jppsacntrQ
DEBUG [main]: incomingFileStorePath=C:/java-projects/portnet-jp/resources/data/JP/Container/IN
DEBUG [main]: timestampFormat=yyyyMMddHHmm
INFO [main]: Setting Up Queue and QueueConnectionFactory ...
DEBUG [main]: Looking up QueueConnectionFactory: pnsgQCF
DEBUG [main]: Looking up Incoming Queue: jppsacntrQ
javax.naming.NameNotFoundException: Unable to resolve 'jppsacntrQ'
Resolved: '' Unresolved:'jppsacntrQ' ; remaining name 'jppsacntrQ'
at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown
Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:337)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:332)
at javax.naming.InitialContext.lookup(Unknown Source)
at pow.business.JP.Container.JPCntrSubscriber.init(JPCntrSubscriber.java:162)
at pow.business.JP.Container.JPCntrSubscriber.<init>(JPCntrSubscriber.java:58)
at pow.business.JP.Container.Main.start(Main.java:183)
at pow.business.JP.Container.Main.main(Main.java:289)
Please check whether 'jndi.properties' is available in the CLASSPATH
and whether it has been configured properly.
Java Result: -1
Build completed with 1 error and 13 warnings. Time: 13 s
Looks OK - did you check your log file for error messages?
Post the log file if you want me take a look.
[email protected] (Kok Liang) wrote:
>Here it is:
>
><?xml version="1.0" encoding="UTF-8"?>
><!--Last updated on: Sat May 24 01:50:49 SGT 2003, If your domain is
>active, please do not edit the config.xml file. Any changes made to
>that file while the domain is active will not have any effect on the
>domain's configuration and are likely to be lost. If your domain is
>inactive, you may edit this file with an XML editor. If you do so,
>please refer to the BEA Weblogic Server Configuration Reference
>documentation available from
>http://edocs.bea.com/wls/docs70/config_xml. In general, we recommend
>that changes to your configuration file be made through the
>Administration Console.-->
><Domain ConfigurationVersion="7.0.1.0" Name="portnet-domain">
> <Application Deployed="true" Name="DefaultWebApp"
>Path=".\applications" StagedTargets="" TwoPhase="false">
> <WebAppComponent Name="DefaultWebApp" Targets="portnet-server"
>URI="DefaultWebApp"/>
> </Application>
> <Application Deployed="true" Name="certificate" Path=".\applications"
>StagedTargets="" TwoPhase="false">
> <WebAppComponent Name="certificate" Targets="portnet-server"
>URI="certificate.war"/>
> </Application>
> <Application Deployed="true" Name="jive3"
>Path="C:\java-libraries\jive_forums_pro_3_0_9" TwoPhase="true">
> <WebAppComponent Name="jive3" Targets="portnet-server"
>URI="jive3.war"/>
> </Application>
> <ApplicationManager Name="portnet-domain"/>
> <EmbeddedLDAP Credential="{3DES}U0sIdpap3Jn35/agldr/nk4n9q5Vo449V4F0z3bLPsM="
>Name="portnet-domain"/>
> <FileRealm Name="wl_default_file_realm"/>
> <JMSConnectionFactory DefaultDeliveryMode="Persistent"
>JNDIName="pnsgQCF" Name="pnsgQCF" Targets="portnet-server"/>
> <JMSDestinationKey Name="portnet-jms-dest-key"/>
> <JMSFileStore Directory="c:\bea\user_projects\portnet-domain\logs\file-store"
>Name="portnet-jms-file-store"/>
> <JMSServer Name="portnet-jms-server" Store="portnet-jms-file-store"
>Targets="portnet-server">
> <JMSQueue BytesPagingEnabled="false"
>DeliveryModeOverride="Persistent"
>DestinationKeys="portnet-jms-dest-key" JNDIName="jppsacntrQ"
>MessagesPagingEnabled="false" Name="jppsacntrQ" StoreEnabled="true"/>
> <JMSQueue BytesPagingEnabled="false"
>DeliveryModeOverride="Persistent"
>DestinationKeys="portnet-jms-dest-key" JNDIName="psajpcntrQ"
>MessagesPagingEnabled="false" Name="psajpcntrQ" StoreEnabled="true"/>
> </JMSServer>
> <JTA Name="portnet-domain"/>
> <Log FileName=".\wl-domain.log" Name="portnet-domain"/>
> <PasswordPolicy Name="wl_default_password_policy"/>
> <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
> <SNMPAgent Name="portnet-domain"/>
> <Security GuestDisabled="false" Name="portnet-domain"
>PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"
>RealmSetup="true"/>
> <SecurityConfiguration
>Credential="{3DES}iE0EWRYurlOnPzbJk1HTM6ajARYfmNrCU4UL/1iAQRJOQGyzRoBdl9bhnBu6JzIucTmQclA22XOW7WwQpMguyQqbLDIGr1VA"
>Name="portnet-domain"/>
> <Server ListenPort="7001" Name="portnet-server"
>NativeIOEnabled="true" ServerVersion="7.0.1.0"
>StdoutDebugEnabled="true">
> <COM Name="portnet-server"/>
> <ExecuteQueue Name="default" ThreadCount="15"/>
> <IIOP Name="portnet-server"/>
> <JTAMigratableTarget Cluster="" Name="portnet-server"
>UserPreferredServer="portnet-server"/>
> <JTARecoveryService Name="portnet-server"/>
> <KernelDebug Name="portnet-server"/>
> <Log FileName="portnet-server\portnet-server.log"
>Name="portnet-server"/>
> <SSL Enabled="true" HostnameVerificationIgnored="true"
>ListenPort="7002" Name="portnet-server"
>ServerCertificateFileName="democert.pem"
>ServerPrivateKeyAlias="demokey"
>ServerPrivateKeyPassPhrase="{3DES}F9QhYhhBa4InPlBKebOlAw=="/>
> <ServerDebug Name="portnet-server"/>
> <ServerStart Name="portnet-server"/>
> <WebServer DefaultWebApp="DefaultWebApp"
>LogFileName="portnet-server\access.log" LoggingEnabled="true"
>Name="portnet-server"/>
> </Server>
></Domain>
>
>
>Tom Barnes <[email protected]> wrote in message news:<[email protected]>...
>> Please post your config.xml
>>
>> Kok Liang wrote:
>> > Hi,
>> >
>> > I have written a simple client to receive messages from a 'jppsacntrQ'
>> > queue,
>> >
>> > The jms server which keeps this queue is already targetted at the
>> > server I am running.
>> >
>> > I have closed my command prompt and restarted WLS a few times but
>I am
>> > still getting this error.
>> >
>> > Has anyone else encountered the same problem?
>> >
>> > Appreciate the help ...
>> >
>> > Victor
>> >
>> > c:\program files\intellij-idea-3.0.4\jre\bin\java.exe -Xmx128M
>> > -Djava.home=C:\Program Files\IntelliJ-IDEA-3.0.4\jre -classpath
>> > c:\program files\intellij-idea-3.0.4\jre\lib\tools.jar;C:\Program
>> > Files\IntelliJ-IDEA-3.0.4\lib\idea_rt.jar;C:\Program
>> > Files\IntelliJ-IDEA-3.0.4\lib\ant.jar;C:\Program
>> > Files\IntelliJ-IDEA-3.0.4\lib\optional.jar;C:\Program
>> > Files\IntelliJ-IDEA-3.0.4\lib\\rt\xerces1.jar
>> > com.intellij.rt.ant.execution.AntMain -logger
>> > com.intellij.rt.ant.execution.IdeaAntLogger -verbose
>> > -Dbuild.compiler.emacs=true -buildfile
>> > C:\java-projects\portnet-jp\build.xml test-polling-subscriber
>> > build.xml
>> > test-polling-subscriber
>> > java
>> > Running Start Polling Task ...
>> > DEBUG [main]: subscriber.propertyFile.path=C:/java-projects/portnet-jp/resources/configuration/JPContainer.cfg
>> > DEBUG [main]: java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
>> > DEBUG [main]: java.naming.provider.url=t3://localhost:7001
>> > DEBUG [main]: java.naming.referral=throw
>> > DEBUG [main]: java.naming.security.authentication=simple
>> > DEBUG [main]: java.naming.security.principal=null
>> > DEBUG [main]: java.naming.security.credentials=null
>> > DEBUG [main]: sleepTimePerCycle=15000
>> > DEBUG [main]: queueConnectionFactoryName=pnsgQCF
>> > DEBUG [main]: incomingQueueName=jppsacntrQ
>> > DEBUG [main]: incomingFileStorePath=C:/java-projects/portnet-jp/resources/data/JP/Container/IN
>> > DEBUG [main]: timestampFormat=yyyyMMddHHmm
>> > INFO [main]: Setting Up Queue and QueueConnectionFactory ...
>> > DEBUG [main]: Looking up QueueConnectionFactory: pnsgQCF
>> > DEBUG [main]: Looking up Incoming Queue: jppsacntrQ
>> > javax.naming.NameNotFoundException: Unable to resolve 'jppsacntrQ'
>> > Resolved: '' Unresolved:'jppsacntrQ' ; remaining name 'jppsacntrQ'
>> > at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
>> > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
>> > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
>> > at weblogic.jndi.internal.ServerNamingNode_WLStub.lookup(Unknown
>> > Source)
>> > at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:337)
>> > at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:332)
>> > at javax.naming.InitialContext.lookup(Unknown Source)
>> > at pow.business.JP.Container.JPCntrSubscriber.init(JPCntrSubscriber.java:162)
>> > at pow.business.JP.Container.JPCntrSubscriber.<init>(JPCntrSubscriber.java:58)
>> > at pow.business.JP.Container.Main.start(Main.java:183)
>> > at pow.business.JP.Container.Main.main(Main.java:289)
>> > Please check whether 'jndi.properties' is available in the CLASSPATH
>> > and whether it has been configured properly.
>> > Java Result: -1
>> >
>> > Build completed with 1 error and 13 warnings. Time: 13 s
-
Unable to resolve 'mslv.oms.oms1.internal.jms.ConnectionFactory'
Hello,
I hope I am posting this in the right place, if not please forgiv and point me to the right place.
Yesterday we did a live upgrade on a system that is running WebLogic 9.2, OSM 6.3.1 and Oracle DB 10.2.0.2, those applications are on a seperate system slice, we did a complete upgrade from Solaris 10/9 (update 6) to the latest Solaris 8/11 (update 10), on SPARC. After the upgrade everything was working and applications are able to start, but weblogic server is spewing the following error message:
<Aug 1, 2012 12:03:58 PM CEST> <Error> <oms.core> <600022> <EJB Create exception thrown while creating object=EventDispatcherEJB.>
<01-Aug-2012 12:03:58,982 CEST PM> <ERROR> <poller.a> <Timer-4> <Failed to process events>
java.rmi.RemoteException: Error in ejbCreate:; nested exception is:
javax.ejb.CreateException: Unable to resolve 'mslv.oms.oms1.internal.jms.ConnectionFactory'. Resolved 'mslv.oms.oms1.internal.jms'
at weblogic.ejb.container.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:95)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:724)
at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:681)
at weblogic.ejb.container.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:220)
at weblogic.ejb.container.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:64)
at com.mslv.oms.eventengine.EventDispatcher_86q3j1_EOImpl.processTimeout(EventDispatcher_86q3j1_EOImpl.java:485)
at com.mslv.oms.poller.a.handleNotification(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerInterceptor.java:1652)
at javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at javax.management.timer.Timer.sendNotification(Timer.java:1295)
at javax.management.timer.Timer.notifyAlarmClock(Timer.java:1264)
at javax.management.timer.TimerAlarmClock.run(Timer.java:1347)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
we went back and activated Solaris update 8, and we still got that problem. The requests that the clients that connect via OSM frontend application that communicates with WebLogic arent being processed.
The oracle db is working and listening to port 1521, I can connect to it and can connect with the user defined in the WebLogic connection pool.
This is the first time working on this system, the application and integration was done by someone else who are not available to help us out, I hope someone here on the forum will be able to help us out with this problem.
Regards,
OmarOften ConnectionFactory errors are caused by an inability to connect with the database hosting the OSM schema and user.
Check the database and make sure that both it and its listener are accepting connections. If that is ok you can also check the oms_pool configuration in WebLogic. Make sure the JNDI connection is valid. In my environments I see that DHCP often screws things up. If I install OSM on a host that has a DHCP assigned address (I'm guilty of being lazy when working in VMs and not statically assigning IP addresses) I often break the JNDI when I reboot the VM and get a new IP.
In WebLogic Admin Console:
Domain > Services > JDBC >Connection Pool > URL
and make sure the JDBC connection string is correct. -
Unable to start WebLogic 7.0 SP2 server
Hi,
Just created a new domain in WLS 7.0 SP2 and tried to start it. It gives the following
error:
<Apr 30, 2003 11:50:41 AM EDT> <Notice> <WebLogicServer> <000327> <Starting WebL
ogic Admin Server "stagingserver" for domain "staging">
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start(Native Method)
at weblogic.kernel.ExecuteThreadManager.startThreads(ExecuteThreadManage
r.java:177)
at weblogic.kernel.ExecuteThreadManager.setThreadCount(ExecuteThreadMana
ger.java:158)
at weblogic.kernel.ExecuteThreadManager.<init>(ExecuteThreadManager.java
:81)
at weblogic.kernel.Kernel.addExecuteQueue(Kernel.java:368)
at weblogic.kernel.Kernel.addExecuteQueue(Kernel.java:358)
at weblogic.jms.dispatcher.DispatcherImpl.<init>(DispatcherImpl.java:63)
at weblogic.jms.dispatcher.DispatcherManager.<init>(DispatcherManager.ja
va:57)
at weblogic.jms.dispatcher.DispatcherManager.create(DispatcherManager.ja
va:114)
at weblogic.jms.JMSService.initializeCommon(JMSService.java:377)
at weblogic.jms.JMSServiceServerLifeCycleImpl.initialize(JMSServiceServe
rLifeCycleImpl.java:54)
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.j
ava:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<Apr 30, 2003 11:50:47 AM EDT> <Error> <JMS> <040014> <Failed to start JMSServer
, JMS is shutting down...>
<Apr 30, 2003 11:50:47 AM EDT> <Critical> <WebLogicServer> <000361> <Server fail
ed during initialization of server subsystem ==> weblogic.jms.JMSServiceServerLi
feCycleImpl@f1327>
Any ideas ?
Thanks,
GaneshThere are memory settings you have to tweak on HP's VM, don't know what they
are, I suggest you contact BEA support or HP vendor.
Cheers
mbg
"Ganesh" <[email protected]> wrote in message
news:[email protected]...
>
We are running WLS 7.0 SP2 on HP-UX 11i.
Thanks,
Ganesh
"Ganesh" <[email protected]> wrote:
Hi,
Just created a new domain in WLS 7.0 SP2 and tried to start it. It gives
the following
error:
<Apr 30, 2003 11:50:41 AM EDT> <Notice> <WebLogicServer> <000327>
<Starting
WebL
ogic Admin Server "stagingserver" for domain "staging">
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start(Native Method)
atweblogic.kernel.ExecuteThreadManager.startThreads(ExecuteThreadManage
r.java:177)
atweblogic.kernel.ExecuteThreadManager.setThreadCount(ExecuteThreadMana
ger.java:158)
atweblogic.kernel.ExecuteThreadManager.<init>(ExecuteThreadManager.java
:81)
at weblogic.kernel.Kernel.addExecuteQueue(Kernel.java:368)
at weblogic.kernel.Kernel.addExecuteQueue(Kernel.java:358)
atweblogic.jms.dispatcher.DispatcherImpl.<init>(DispatcherImpl.java:63)
atweblogic.jms.dispatcher.DispatcherManager.<init>(DispatcherManager.ja
va:57)
atweblogic.jms.dispatcher.DispatcherManager.create(DispatcherManager.ja
va:114)
at weblogic.jms.JMSService.initializeCommon(JMSService.java:377)
atweblogic.jms.JMSServiceServerLifeCycleImpl.initialize(JMSServiceServe
rLifeCycleImpl.java:54)
atweblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.j
ava:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<Apr 30, 2003 11:50:47 AM EDT> <Error> <JMS> <040014> <Failed to start
JMSServer
, JMS is shutting down...>
<Apr 30, 2003 11:50:47 AM EDT> <Critical> <WebLogicServer> <000361><Server
fail
ed during initialization of server subsystem ==>weblogic.jms.JMSServiceServerLi
feCycleImpl@f1327>
Any ideas ?
Thanks,
Ganesh -
Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'
Hi
When executing import/export service through FSM we are getting below error on server console. Can someone please help us to resolve this.
<Nov 22, 2012 10:25:14 PM IST> <Error> <oracle.j2ee.ws.common.jaxws.JAXWSMessages> <BEA-000000> <[MessageID: uuid:3eac9f32-ad81-4d96-b5b2-18cf0fd887c0[migRequestId=300100015300332][migObjectId=300100015300326][]] Could not send async request message to the JMS queue.
java.security.PrivilegedActionException: javax.naming.NameNotFoundException: Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'. Resolved 'oracle.j2ee.ws.server.async'; remaining name 'DefaultRequestQueue'
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:51)
at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:56)
at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:365)
at oracle.j2ee.ws.server.jaxws.JMSChannel.getConnection(JMSChannel.java:468)
at oracle.j2ee.ws.server.jaxws.JMSChannel.sendMessage(JMSChannel.java:235)
at oracle.j2ee.ws.server.jaxws.JMSChannel.sendRequest(JMSChannel.java:199)
at oracle.j2ee.ws.server.jaxws.AsyncServiceRuntimeDelegate$JMSMessageQueue.send(AsyncServiceRuntimeDelegate.java:170)
at oracle.j2ee.ws.server.jaxws.AsyncServiceRuntimeDelegate.pro
Caused By: javax.naming.NameNotFoundException: Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'. Resolved 'oracle.j2ee.ws.server.async'; remaining name 'DefaultRequestQueue'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
FYI:
The "oracle.jrf.ws.async_template_11.1.1.jar" jar file required for JMS (oracle.j2ee.ws.server.async.) which is present in below directory path of weblogic standalone.
Edited by: user12820425 on Dec 2, 2012 11:56 PMAre you using Standalone (or) Integrated WLS. It works only on Standalone WLS.
Also for these issues, please put this in Cross Pillar Integration Forum. Contact Ning.Dong -
Weblogic Messaging Bridge - T3S Enabling Process
Dear All,
I need your help to resolve an issue in Weblogic Messaging Bridge - T3S enabling process.
I'm doing a POC to forward messages between 2 different domains (from wl 10.3.2 to wl 10.0) using Messaging Bridge with T3S Protocol.
I enabled SSL Port, Custom Identity and Custom Trust in those domains.
In my laptop (single JVM), WL Messaging Bridge in 10.3.2 is able to forward messages between domains using T3S.
My Testing Scenario:
A Sample web application use the https/t3s protocol to put message(s) in the source jms queue
Weblogic Messaging Bridge use the t3s protocol to get message(s) from source jms queue & forward the message(s) to the destination jms queue
But, When I tried the same POC in sepearate boxes (WL 10.3.2 in one box, WL 10.0 in another box). I got the below exceptiion.
Any one please throw some lights here to resolve the issue.
####<Oct 12, 2011 4:11:49 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1318416109085> <BEA-000000> <Exception:
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:367)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
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)
Caused By: java.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
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)
Caused By: java.rmi.ConnectException: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
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)
>
####<Oct 12, 2011 4:11:49 PM IST> <Warning> <Connector> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416109086> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3s://172.16.2.25:4936, user name = null) ">
####<Oct 12, 2011 4:11:49 PM IST> <Info> <MessagingBridge> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416109089> <BEA-200043> <Bridge "Bridge-0" failed to connect to the target destination and will try again in 45 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3s://172.16.2.25:4936, user name = null)
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1665)
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1645)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:460)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
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)
-------------- Linked Exception ------------
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:367)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
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)
Caused by: java.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
... 28 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
... 31 more
)>
####<Oct 12, 2011 4:11:49 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416109479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:50 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416110055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:50 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416110479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:51 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416111055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:51 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416111479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:52 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416112055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:52 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416112479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:53 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416113055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:53 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416113479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:54 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416114055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:54 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416114479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:55 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416115051> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:55 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416115479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:56 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416116055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:56 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416116479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:57 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416117055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:57 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416117479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:58 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416118055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:58 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416118479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
Thanks in advance.Think this can help you on the way - http://blog.eisele.net/2010/06/weblogic-server-ssl-httpst3s-and-java.html
-
I copy code from other thread and need to find a datasource named TestDS3. TestDS3 is created by me using weblogic 10.3.5 console. However, the following code has errors. If I change to
DataSource datasource = (DataSource)initialContext.lookup("CP-TestDS3");
I still get the same error.
================error=======================
"C:\Program Files\Java\jdk1.6.0_24\bin\javaw.exe" -client -classpath C:\JdevWorkspace\ANTdatasource\.adf;C:\JdevWorkspace\ANTdatasource\Project2\classes;E:\Jdeveloper_11115\wlserver_10.3\server\lib\weblogic.jar -Djavax.net.ssl.trustStore=E:\Jdeveloper_11115\wlserver_10.3\server\lib\DemoTrust.jks ant.DatasourceInfo
Exception in thread "main" javax.naming.NameNotFoundException: Unable to resolve 'TestDS3'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'TestDS3'. Resolved '']; remaining name 'TestDS3'
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at weblogic.jndi.internal.ServerNamingNode_1035_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:423)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at ant.DatasourceInfo.main(DatasourceInfo.java:31)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'TestDS3'. Resolved ''
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Process exited with exit code 1.
================code=======================
package ant;
import java.sql.Connection;
import java.sql.ResultSet;
import java.sql.Statement;
import java.util.Hashtable;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.sql.DataSource;
public class DatasourceInfo {
public DatasourceInfo() {
super();
public static void main(String[] args) throws Exception {
DatasourceInfo datasourceInfo = new DatasourceInfo();
Hashtable ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
Context initialContext = new InitialContext(ht);
DataSource datasource = (DataSource)initialContext.lookup("TestDS3");
if (datasource != null) {
Connection Conn = datasource.getConnection();
========config.xml====================================
<jdbc-system-resource>
<name>CP-TestDS3</name>
<target>AdminServer</target>
<deployment-order>1</deployment-order>
<descriptor-file-name>jdbc/CP-TestDS3-4702-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
</domain>Hi,
Try with JNDI name instead of data source name for lookup, JNDI name would be something like "jdbc/TestDS3"
Sireesha
Maybe you are looking for
-
BW 3.5 Update rule routine and start routine convert to BI 7.0 Endroutine.
I have bw 3.5 update routine and update rules start routine( r/3 to ODS). i need to replicate that routine into BI 7.0 endroutine with the same logic with some minor changes(DSO to DSO). IN BW 3.5 the data is getting from r/3 where as in BI7.0 the da
-
Microsoft Word and Xcel crashing on Yosemite!
Running MS Office 2011 for MAC - I upgraded to Yosemite soon after it's release and had problems with word and xcel both crashing. Researched the problem and found duplicate font files were suspect so I cleaned that up and things seemed to be workin
-
Is there any way to trigger the Ctrl+C command from a java application' as to copy a text selection made by the mouse on internet explorer to the system clip board. If not does any know the exe / service the command calls and ill figure out the rest
-
AVCHD Media for PowerPC based hardware
I have posted this earlier in an other thread but my posting has so far been ignored, so I am trying a new thread: We have just invested over 1500$ to upgrade to FCStudio 2 as well as stashing 3 more gigas of SDRAM into a G5, as I need to edit HD vid
-
Hi, Is it possible to make a make a component in Swing faded out and not selectable? I have a JTabbedPane and I want to specify at loading time how many tabs should be selectable and the other ones should be visible but not selectable.