Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Paul Clapham
  • Jeanne Boyarsky
  • Ron McLeod
  • Frank Carver
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
  • Piet Souris
  • Frits Walraven
  • fred rosenberger

Websphere 5, ISeries administering JMS problem

Ranch Hand
Posts: 225
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm using WebSphere 5.0.0 on the ISeries, and I'm having a problem administering JMS objects onto WebSphere, either via JACL scripts or via the Admin Console. I have no problems administering legacy resources or JDBC resources by either method, and my scripts work on WebSphere ( admittedly 5.0.2) on Unix and Windows.
The script appears to work ( ie. no error on screen or in the trace.log with all tracing enabled ), but the JMS items ( queue connection factories, queues ) do not appear in the JNDI context - my program cannot find them and neither can the dumpnamespace utility. Everything else appears in the JNDI context.
I have WebSphere MQ v5.3 and Java libraries installed ( before WAS ), and I have requested an upgrade of WebSphere to 5.0.2.
Does anyone know of a possible cause for this problem? Is there some configuration/installation issue that would cause this?
The fastest and most reliable components of any system are those that are not there. Tiny ad:
the value of filler advertising in 2021
    Bookmark Topic Watch Topic
  • New Topic