ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » AMQ9209-inetd.conf

Post new topic  Reply to topic
 AMQ9209-inetd.conf « View previous topic :: View next topic » 
Author Message
pshan81
PostPosted: Fri Mar 10, 2006 4:44 am    Post subject: AMQ9209-inetd.conf Reply with quote

Acolyte

Joined: 24 May 2005
Posts: 72

I am doing MQ two phase commit.I have my MQ client(TwoPhaseCommit.java),db and queue manager running on different machines.When i start my queue manager i am getting the following error in the log file

-------------------------------------------------------------------------------
03/10/06 17:44:09
AMQ9209: Connection to host '***.**.***.***' closed.

EXPLANATION:
An error occurred receiving data from '***.**.***.*** over TCP/IP. The
connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
----- amqccita.c : 2781 -------------------------------------------------------

Do i need to give an entry for the queue manager in inetd.conf(/etc) file?The same MQ client works fine when all(MQ client,qmgr and db) are running in the same machine
Back to top
View user's profile Send private message
EddieA
PostPosted: Fri Mar 10, 2006 9:00 am    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

Quote:
I am doing MQ two phase commit.I have my MQ client(TwoPhaseCommit.java),db and queue manager running on different machines

Do you have the Extended Client, because the "normal" Client will not do two phase commits.
Quote:
When i start my queue manager

Do you really mean the Queue Manager. If so, what has this to do with the Client.
Quote:
Do i need to give an entry for the queue manager in inetd.conf(/etc) file

Your QM needs a listener running. Either using runmqlsr, which is preferred, or you can configure it using inetd.
Quote:
he same MQ client works fine when all(MQ client,qmgr and db) are running in the same machine

Then, if that's really the case, it sounds like you haven't set up the "new" client machine/code correctly to connect to the QM.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
pshan81
PostPosted: Sat Mar 11, 2006 1:39 am    Post subject: Reply with quote

Acolyte

Joined: 24 May 2005
Posts: 72

Quote:


Do you have the Extended Client, because the "normal" Client will not do two phase commits



What do you mean by extended client?

Quote:


Do you really mean the Queue Manager. If so, what has this to do with the Client.


Its nothing but qMgr.begin() in my two phase commit code.


When i run the TwoPhaseCommit.java i am getting the following exception

MQJE001: Completion Code 2, Reason 2012
An MQ error occurred: 2 2012
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2012
at com.ibm.mq.MQQueueManager.begin(MQQueueManager.java:1004)
at TwoPhaseCommit.start(TwoPhaseCommit.java:42)
at TwoPhaseCommit.main(TwoPhaseCommit.java:17)

[/code]
Back to top
View user's profile Send private message
wschutz
PostPosted: Sat Mar 11, 2006 3:33 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

Quote:
I have my MQ client(TwoPhaseCommit.java),db and queue manager running on different machines.When i start my queue manager i am getting the following error in the log file

Quote:
The same MQ client works fine when all(MQ client,qmgr and db) are running in the same machine

Quote:

begin

public void begin() throws MQException;

Begins a new unit of work. This method is only supported by WebSphere MQ in a bindings connection. It signals to the queue manager that a new unit of work is to begin.

Exceptions

* MQException - if the call fails


Bindings mode means "not as an MQ client" but directly connected to the qmgr (ie, on the same machine)
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
kotha
PostPosted: Tue Jul 18, 2006 10:49 am    Post subject: Reply with quote

Partisan

Joined: 12 Mar 2005
Posts: 333

http://www-1.ibm.com/support/docview.wss?doc=aimwmq&rs=171&uid=swg21110505
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » AMQ9209-inetd.conf
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.