Solved

Unable to connect to the JMS destination error in the weblogic console

Posted on 2008-10-17
5
5,474 Views
Last Modified: 2013-12-10
Hi,

We are getting the following error on the console. We have not changed anything on our side and the application server has been running fine.  But recently we are seeing this error on the console.


"<Oct 17, 2008 10:56:04 AM CDT> <Warning> <EJB> <BEA-010096> <The Message-Driven
EJB: WorkerMDB_FirehouseU_1185984552791 is unable to connect to the JMS destinat
ion: wli.internal.egrdbms.queue. Connection failed after 64 attempts. The MDB wi
ll attempt to reconnect every 20 seconds. This log message will repeat every 600
 seconds until the condition clears.>
<Oct 17, 2008 10:56:04 AM CDT> <Warning> <EJB> <BEA-010061> <The Message-Driven
EJB: WorkerMDB_FirehouseU_1185984552791 is unable to connect to the JMS destinat
ion: wli.internal.egrdbms.queue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: wli.internal.egrdbms.queue c
ould not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml
is correct, and the JMS destination has been deployed.>"
0
Comment
Question by:Anandhi1
  • 3
  • 2
5 Comments
 
LVL 10

Expert Comment

by:rajesh_bala
ID: 22764143
Which version of weblogic are you using. It would be helpful if you could post the config.xml or the jms.xml present in weblogic.

Can you also check if the queue has been active through weblogic console?

~Rajesh.B
0
 
LVL 1

Author Comment

by:Anandhi1
ID: 22815962
I am using weblogic 8.1 SP6.  I am attaching the config.xml file.
config.txt
0
 
LVL 10

Accepted Solution

by:
rajesh_bala earned 500 total points
ID: 22818098
Can you make the following change and check it out?

<JMSQueue CreationTime="1185982177572"
            JNDIName="MaxFireHouseInt3Web.queue.AsyncDispatcher" Name="MaxFireHouseInt3Web.queue.AsyncDispatcher"/>
        <JMSQueue CreationTime="1185982198431"
            JNDIName="MaxFireHouseInt3Web.queue.AsyncDispatcher_error" Name="MaxFireHouseInt3Web.queue.AsyncDispatcher_error"/>
        <JMSQueue CreationTime="1224258073362"
            JNDIName="wli.internal.egrdbms.queue" Name="wli.internal.egrdbms.queue"/>

To the following

<JMSQueue JNDIName="MaxFireHouseInt3Web.queue.AsyncDispatcher" Name="MaxFireHouseInt3Web.queue.AsyncDispatcher"/>
        <JMSQueue             JNDIName="MaxFireHouseInt3Web.queue.AsyncDispatcher_error" Name="MaxFireHouseInt3Web.queue.AsyncDispatcher_error"/>
        <JMSQueue             JNDIName="wli.internal.egrdbms.queue" Name="wli.internal.egrdbms.queue"/>


Try removing your cache by deleting contents in stage directory and in <appserverdomain>\servers\<yourservername>\_WL_User\

~Rajesh.B
0
 
LVL 1

Author Comment

by:Anandhi1
ID: 22818686
Thanks for your suggestion. I will try it out.
I did some research on the above mentioned problem and nailed it down to the following.

The pointbase database is rejecting the connections for the connection pool CGJms and the other two default connection pools created by the weblogic. This is resulting in the following error. The error I am getting in the Pointbase console says 'java.lang.OutofMemoryError'.

How do we eliminate the outofMemory error in the pointbase database?

thanks,
Anu
0
 
LVL 1

Author Comment

by:Anandhi1
ID: 22818755
Now when I am starting my application domain server, this is the error I am getting in the pointbase server console.

java.lang.StackOverflowError'
0

Featured Post

Portable, direct connect server access

The ATEN CV211 connects a laptop directly to any server allowing you instant access to perform data maintenance and local operations, for quick troubleshooting, updating, service and repair.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Verbose logging is used to diagnose garbage collector problems. By default, -verbose:gc output is written to either native_stderr.log or native_stdout.log.   It is also possible to redirect the logs to a user-specified file. This article will de…
This article is about some of the basic and important steps to be used to improve the performance in web-sphere commerce application development. 1) Always leverage the Dyna-caching facility provided by the product 2) Remove the unwanted code …
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question