| Author |
Message
|
| sas_kannan |
 Posted: Sat Aug 27, 2005 3:42 am Post subject: Failed to obtain a connection with MQSeries |
 |
|
Newbie
Joined: 27 Aug 2005
Posts: 8
Location: Tirunelveli
|
Hi,
I am trying out implementing IBM WebSphere Business Integration Server Express v4.3.1. I am trying to work out with a JText Adapter, (JTextConnectorExample, The one I downloaded from Web) I've successfully deployed it into the ICS. While trying to start the JText and TestConnectors I recieve the following error.
----------------------
Failed to obtain a connection with MQSeries, queue manager name = WebSphereICS.queue.manager, channel=CHANNEL1, host=bissvr, port=1414. [info]::MQSeries:Completion code 2 Reason code 2059
---------------
While trying it using the TestConnector Utility the following error is raised.
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
What could be the problem? Any help is appreciated.
With regards,
S.A.Senthil Kannan |
|
| Back to top |
|
 |
| hopsala |
| Posted: Sat Aug 27, 2005 4:25 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Well, it's quite simple - if you had looked through the literature (as you should do after reading this reply) you would have known that 2059 means MQRC_Q_MGR_NOT_AVAILABLE.
That is to say, either the ip address is wrong (bissvr 1414), there is a communication error, the listener is down, the qmanager is down, or many a similar problem.
So, check all these out, check CHANNEL1 exists on your QM, and if everything seems ok - have a look at the error log AMQERR01.LOG.
For more info, read MQ literature and search this forum for "2059" or "Jtext". If you solved the problem - tell us how, if you did not solve the problem - post your standard adapter configuration properties. |
|
| Back to top |
|
|
| vennela |
| Posted: Sat Aug 27, 2005 6:53 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Apart from all the above checks:
Have you created a channel called CHANNEL1 which is a SVRCONN type of channel.
If there is no specific reason for you to use MQ as the transport property for your connector, then change it to IDL and that should help you to start the connector agent easily. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Sun Aug 28, 2005 6:09 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| sas_kannan |
| Posted: Sun Aug 28, 2005 8:05 pm Post subject: |
|
|
Newbie
Joined: 27 Aug 2005
Posts: 8
Location: Tirunelveli
|
Hi Hopsala,
Thanks for all your comments and help regarding to fix the problem with MQ Series. As you mentioned it was quite simple, there was no LISTENER for the CHANNEL. Once I started teh LISTENER, Hurrah! it worked fine.
Thank you Vennela for your suggestions, as my requirement is that to use MQ as I work in an environment where things are in asynchronous, I chose MQ as a best candidate...
Thank you one and all..
With Regards,
S.A. Senthil Kannan |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Aug 29, 2005 10:43 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Thank you Vennela for your suggestions, as my requirement is that to use MQ as I work in an environment where things are in asynchronous, I chose MQ as a best candidate... |
Also, if your collab is a long running transactional collab, then you must specify MQ or JMS as the transport type. |
|
| Back to top |
|
|
| sas_kannan |
| Posted: Tue Aug 30, 2005 8:32 pm Post subject: How to start the Lisener Automaically |
|
|
Newbie
Joined: 27 Aug 2005
Posts: 8
Location: Tirunelveli
|
Hi,
I have a problem with the listener again. Whenever the server machine needs a restart I have to customarily start the LISTENER.. Is there any way to make it start automatically when the Queue Manager starts..
The problem I 've identified is every time I have to set the Protocol Type as TCP in the Parameters Tab and then start it ...
Is there any way to work around this problem?...
Thanks in advance...
With regards,
Senthil Kannan |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Tue Aug 30, 2005 10:16 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
with version 6 this may work, but with version 5 it is up to you to start the listener.
depending on the plattform you may (unix) use httpd or a start command (script during startup or qmgr start script) to start a listener. windows should be started automatically if defined in the services. other plattforms differ.
check the quick beginnings manual.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Sep 02, 2005 9:45 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| Quote: |
| Whenever the server machine needs a restart |
So I assume you are using windows. Just create a listener in MQ Services for that Queue Manager.
_________________
-Ratan |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Sep 02, 2005 11:36 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And if you happen to be on Windows with MQ 5.3 CSD 06 don't forget to apply the relevant APAR...
Enjoy  |
|
| Back to top |
|
|
|
|
