Help!! Configuring JMS in WebLogic (w/cluster & managed servers) to deploy a Workshop Portal app
Posted on 2006-07-03
I am trying to setup a test environment.
The target configuration consists of 2 physical machines, each with WebLogic 8.1 SP3.
I also have a 3rd machine with WebLogic that I use Workshop to create a portal app (portal.ear).
On the first target machine, "weblogic", I have configured an admin server. On second target machine, I have a cluster ("mycluster") with two managed servers ("myman1" and "myman2").
I've been successful at getting this configuration working, where I can start/stop the managed servers in the cluster using the WebLogic console on the 1st machine, and I am able to deploy my portal app to both the admin server and to the cluster.
BUT, I am having a problem where I am seeing warnings in the managed server logs like:
####<Jul 3, 2006 10:11:07 PM EDT> <Warning> <EJB> <weblogiccluster> <myman1> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-010096> <The Message-Driven EJB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.queue. Connection failed after 2 attempts. The MDB will attempt to reconnect every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
####<Jul 3, 2006 10:11:07 PM EDT> <Warning> <EJB> <weblogiccluster> <myman1> <ExecuteThread: '13' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-010061> <The Message-Driven EJB: KNEX.bean.QueueTransport is unable to connect to the JMS destination: jws.queue_auto_1. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jws.queue_auto_1 could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml is correct, and the JMS destination has been deployed.>
And then, the DefaultAuditRecorder.log file gets filled up VERY quickly, growing to over 1/2 GB for each managed server until eventually the entire hard drive is full, then everything comes to a grinding halt :(!!
When I look in WebLogic console, it LOOKS like I've created the jws.queue and jws.queue_auto_1 (and jws.queue_auto_2)), and I've targeted jsw.queue_auto_1 to "myman1", and jsw.queue_auto_2 to "myman2". The "jws.queue" is configured as a Distributed Destination which is auto deployed to myman1 and myman2.
So, I CANNOT understand why the KNEX.bean.QueueTransport on myman1 "can't connect" to jws.queue_auto_1?? Same situation on myman2, for jws.queue_auto_2.
Can anyone please help me?
I'm really new to WebLogic environment, and I know that I *MUST* be missing something, probably something really obvious, and I've read a lot of stuff on BEA's website and also a pile of WebLogic books, but can't figure out what :(!!
Since I'm fairly unfamiliar with WebLogic, if you know what I need to do, please describe it specifically, and I'd prefer not to be pointed back to something on BEA's website, as I've scoured that pretty thoroughly, and most of it is "over my head"...
Thanks in advance,