This week's book giveaway is in the Spring forum.
We're giving away four copies of Spring Boot in Practice and have Somnath Musib on-line!
See this thread for details.
Win a copy of Spring Boot in Practice this week in the Spring 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 ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Websphere MQ Socket issue

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I'm currently installing a WAS 5.1 environement and testing MQ communications.
WAS 5.1 was installed with internal Websphere MQ
When I create a new server in WAS a new QueueManager is created as WAS_node_application_name and this Queue manager works fine.
(I've tested it with postCard test application)
But when I try to send a message it fail with following error :

javax.jms.JMSException: MQJMS2005: Impossible de créer MQQueueManager pour 't22.TMHE.COM:WAS_t22_TMHE_Parts_Portal'
com.ibm.mq.MQException: MQJE001 : MQException : Code achèvement 2, raison 2059 MQJE011 : Tentative de connexion au socket refusée

Does someone have some guidance for me ?
 
Marshal
Posts: 27292
87
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"Connection refused"... that means the code was trying to connect to server X at port Y, but there was no answer. Either server X is not running, or it's not listening at port Y, or there is a firewall preventing the connection.

So you'll have to check out the configuration which specifies X and Y for your environment. See if the server is really listening there. Check out your network if necessary.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic