Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JMS Error

 
Madhu Juneja
Ranch Hand
Posts: 176
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
When executing JMS Application I am getting the following exception :
SEVERE unable to locate resource bundle: com.sun.jms.LocalStrings
This exception is thrown at the point where the createQueueConnection() method is invoked to create a QueueConnection.
How do I solve this problem ?
Thanks
 
Madhu Juneja
Ranch Hand
Posts: 176
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The same exception is thrown in both the createQueueConnection() methods.
Can anybody help ...
 
Majid Khan
Ranch Hand
Posts: 92
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Madhu
Can u specify what provider are u using?
Mac
 
Madhu Juneja
Ranch Hand
Posts: 176
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using the sun's very own jsdkee1.3 version. Can you provide any clues to the problem I am facing. Thanks in advance.
 
Majid Khan
Ranch Hand
Posts: 92
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Add this to your classpath %J2EE_HOME%\lib\locale.
Your code should work fine.
Rgds
Mac
 
Madhu Juneja
Ranch Hand
Posts: 176
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks. Will do that on Monday.
Thanks Again.
 
Amit Goyal
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Majid Khan:
Add this to your classpath %J2EE_HOME%\lib\locale.
Your code should work fine.
Rgds
Mac

Hi, I also ran into the same problem. I tried the suggested fix, only to come across another error. I am trying to send messages over a network to another computer via JMS.
Here is the error:
SEVERE ConnectionFactoryImpl: Failed to lookup or connect to JMS service because
: javax.naming.CommunicationException: Cannot connect to ORB [Root exception is
org.omg.CORBA.COMM_FAILURE: minor code: 1398079689 completed: No]
Any help would be greatly appreciated.
 
Ragu Sivaraman
Ranch Hand
Posts: 464
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Amit Goyal:

Hi, I also ran into the same problem. I tried the suggested fix, only to come across another error. I am trying to send messages over a network to another computer via JMS.
Here is the error:
SEVERE ConnectionFactoryImpl: Failed to lookup or connect to JMS service because
: javax.naming.CommunicationException: Cannot connect to ORB [Root exception is
org.omg.CORBA.COMM_FAILURE: minor code: 1398079689 completed: No]
Any help would be greatly appreciated.

Please check your client's run time jars
They have to in correct order
If its another computer, make sure the lookup jndi or any propreitary mechanism is functional

Ragu
 
kite
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
add the following into your %j2ee_home%\config\jms_service.properties , jms_client.properties
com.sun.jms.internal.java.naming.factory.initial=com.sun.enterprise.naming.SerialInitContextFactory
all of the problems will be solved
[ August 12, 2002: Message edited by: kite ]
 
Frank Truong
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Kite,
I added what you recommended to those 2 files but it still keeps saying ... can't not find SerialContextProvider ... Do you still have any ideas?
I don't know why it does work on some machines I try remotely but not all of them .
Thanks,
Frank
 
Jeroen de Vries
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This error message occurs when your piece of code is generating an exception. For some reason it will not be caught unless you catch a Throwable.
I implemented the onMessage method of the jms MessageListener and had the same problem. What i did was put a try-catch around all code in the onMessage method and had a Throwable caught which i stacktraced.
try {
<all your code inside the onMessage method>
} catch(Throwable e) {
e.printStackTrace();
}
Voila an exception originating from my own code appeared although i had a correct try-catch around the faulty code.
It does not solve the problem with the resource bundle message but it does reveal a problem causing it.
Hope this tip will help you.
grtz, j
 
Dwayne Perkins
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I had the same Exception when attempting to publish a message. It ended up being caused by using a property name with a dash in it when setting a property in the jms message. Apparently dashes aren't allowed. I lost a lot of time on this stupid problem, so I can only hope this helps someone else out there getting the same exception.

I find the wording of the exception to be completely innacurate. Even the stack trace wasn't all that helpful.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic