• 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 ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Websphere trail version --> Default JMS server problemm

Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I am trying to migrate one of my Enterprise application running in websphere 5.0 to 6.1. So i have downloaded the trail version of Websphere 6.1.03 from the IBM site and installed, I have configured the JMS provider so as to use Version 5 default JMS provider and configured the QueueConnectionFactory and Queues on the server node and created Message Listeners for to listen to the configured queues.

But after i have created the queues, i need to add names of queues configured to the JMS Server, if i look at the
Websphere 5.1, i have the JMS Server defined (servers -> Application servers-> server1-> Service Components -> JMS Serer link) and i can change the properties to add the list of queue name to JMS server configuration.
But i don't find any JMS server defined for the server or i didn't see any JMS server in the servers Navigation pane from the admin console.

But i have configured Listeners and Queues without any error and my application deployed properly, but when i post the message on to the queue i am getting the following error.

com.sungard.edx.workflow.WorkflowException: Error sending message to Workflow Queue - Linked Exception = MQJE001: An MQException occurred: Completion Code 2, Reason 2059

MQJE011: Socket connection attempt refused
at com.sungard.edx.workflow.InitializerBean.sendToWorkflow(InitializerBean.java:45 9)

at com.sungard.edx.workflow.InitializerBean.placeInQueue(InitializerBean.java:612)

at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989)


javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:WAS_ses050Node02_server1'

at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:5 86)

at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2082)

at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:1449)

I have seen the documentation like the following.

* Version 5 JMS server collection

On a WebSphere Application Server Version 5 node, a JMS server provides the functions of the JMS provider. Use this panel to list JMS servers on WebSphere Application Server Version 5 nodes within the administration domain, or to select a JMS server to view or change its configuration properties.

There can be at most one JMS server on each Version 5 node in the administration domain, and any application server within the domain can access JMS resources served by any JMS server on any node in the domain.

To view this page, use the administrative console to complete the following step:
In the navigation pane, select Servers > Version 5 JMS Servers.
To browse or change the properties of a JMS server, select its name in the list displayed.*

BUT I don't see any Version5 JMS sever as mentioned in the help.

Can any one let me know the solution to this problem.
Do you think is there any problem with Installation ? or is there any way to navigate to the JMS Server properties to add the queue list or is there anything else need to be configured.

Prompt reply would be very grateful

Switching from electric heat to a rocket mass heater reduces your carbon footprint as much as parking 7 cars. Tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic