Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

WAS 5.1.1 JMS Problem (tempQPrefix)

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello!
I have an application that is intended to run on WAS 5.1.1 (base) and it uses embedded JMS Messaging. The application did work fine under WAS 5.1, but after the update to 5.1.1 I get the following error when connecting to JMS:

ERROR de.launcher.client.MessageReceiver - com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is javax.jms.JMSException: MQJMS1006: invalid value for tempQPrefix: ]
java.security.PrivilegedActionException: java.lang.reflect.InvocationTargetException
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java:389)
at com.sun.interop.beans.RegularDispatcher.invoke(RegularDispatcher.java:142)
at com.sun.interop.dispatch.InstanceProxy.Invoke(InstanceProxy.java:69)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sun.interop.beans.PrivilegedMethodInvokeAction.run(PrivilegedMethodInvokeAction.java:51)
...

From what i understand from ptf docs that came with the 5.1.1. Fixpack the embedded JMS introduced a new parameter tempQPrefix which determines a prefix for dynamically created Queues. But I also understood that this parameter defaults to some value when it is not set. Anyway, neither am i using dynamically created queues nor do i know where to set the parameter. Unfortunately it seems that no one faced this problem yet, so our application probably does something wrong - however, once agian, it worked fine under WSA 5.1

Any help is highly appreciated.

Thanks in advance,

Ralf

[ September 17, 2004: Message edited by: Ralf Altmeyer ]Any help is highly appreciated.
[ September 20, 2004: Message edited by: Ralf Altmeyer ]
 
Ranch Hand
Posts: 86
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
you add mq.jar and mqjms.jar files in the classpath
 
Ralf Altmeyer
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you very much, that helped. I had elder versions of the jars you mentioned (by the way they are named com.ibm....jar) in my classpath. After i added the new versions to the classpath the applications worked again.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic