FMC00013E Communication error - Failing Action: Connect, Reason

CodeVerge.Net ^Beta
Item Entry Register Login

Novell Forums

Zone:

> NEWSGROUP > IBM Software > ibm.software.websphere.mqworkflow

Tags:

Item Type:

Date Entered:

7/5/2007 2:18:21 PM

Date Modified:

Subscribers:

Subscribe Alert

Rate It:

XPoints:

N/A

Replies:

Views:

751

Favorited:

Favorite

Can Reply: Yes

Members Can Edit: No

Online: Yes

root

4 Items, 1 Pages |< << Go >> >|

	<raman_532@yaho
	NewsGroup User

FMC00013E Communication error - Failing Action: Connect, Reason

7/5/2007 2:18:21 PM

Hi,
We are facing some problem while trying to connect to IBM Workflow 3.5 from IBM WAS 6.0 App.server installed in solaris machine.
We tried to launch the below sample client program from solaris machine to logon to the workflow(Workflow is installed in NT based machine).

import com.ibm.workflow.api.Agent;
import com.ibm.workflow.api.ExecutionService;
import com.ibm.workflow.api.FmcException;
import com.ibm.workflow.api.ProcessInstance;
import com.ibm.workflow.api.ProcessTemplate;
import com.ibm.workflow.api.ReadOnlyContainer;
import com.ibm.workflow.api.ReadWriteContainer;
import com.ibm.workflow.api.WorkItem;
import com.ibm.workflow.api.ItemPackage.ExecutionState;
import com.ibm.workflow.api.ServicePackage.AbsenceIndicator;
import com.ibm.workflow.api.ServicePackage.SessionMode;

public class WorkFlowLogon {

public static void main(String[] args) {

try {
ExecutionService service = null;
String userid = null;
String password = null;
String serverInstanceFlag = "";
long t1 = System.currentTimeMillis();
Agent agent = new Agent();
agent.setConfigurationID("FMC");

agent.setName("agentLocator");
service = agent.locate("FMCGRP","FMCSYS");
userid = "PROCESSSTART1";
password = "PROCESSSTART1";

System.out.println(" Before login ");
service.logon2(userid,password, SessionMode.PRESENT_HERE,AbsenceIndicator.LEAVE );

System.out.println(" After login ");
} catch (Exception e) {
e.printStackTrace();
}

}
}

FMCRC Configuration:
Configuration/FMC/System=FMCSYS
Configuration/FMC/MQConnectionType=MQClient
Configuration/FMC/MQCommunicationAddress=25.23.201.125
Configuration/FMC/SystemGroup=FMCGRP
Configuration/FMC/FMLConnectName=FMC.FMCGRP.FMCSYS,FMCQM
Configuration/DefaultConfigurationID=FMC
Configuration/FMC/MQQueueManager=FMCQM
Configuration/FMC/MQPrefix=FMC
Configuration/FMC/MQPort=5010
Configuration/FMC/ConfigurationID=FMC

Also, all required jars including FMCJAPI.jar is properly set in the classpath.

The above configuration is working fine when i am trying to launch from NT machine.
But from solaris box, the below error is displayed:

FMC00013E Communication error - Failing Action: Connect, Reason Code: 2009, Failing Object: FMCQM

	hos@de.ibm.com
	NewsGroup User

Re: FMC00013E Communication error - Failing Action: Connect, Reason Code: 2009, Failing

7/6/2007 6:13:15 AM

Hi,

have you tried to run the configuration checker tool on your client box?
Can you connect from a Solaris client outside of WAS?
What are your MQ library settings in WAS (MQ_INSTALL_ROOT or internal)?
Did you check the error log for any preceeding information?

Regards

Volker Hoss
IBM WebSphere Process Server Development

	<raman_532@yaho
	NewsGroup User

Re: FMC00013E Communication error - Failing Action: Connect, Reason

7/7/2007 4:18:00 PM

Hi,
Sorry for the late reply.

-> After running fmczchk in my client solaris box, displays the following info,with 4 errors...
FMC34010I: Configuration checker version 3.5.0.115 started.

FMC34012I: ===> General checks.
FMC34011I: Performing WebSphere MQ Workflow Version 3.5.0 checks.
FMC34156E: Required patch 108827-12 is not installed, installed version is: none
..
FMC34156E: Required patch 111177-04 is not installed, installed version is: none
..

FMC34013I: ===> Admin Server found, checks started.

FMC34013I: ===> Server message device found, checks started.
FMC34032E: Cannot load QM switch file library oraswit: No such file or directory
(rc = 2).
FMC34nnnE: Default queue manager <null> not found in /var/mqm/mqs.ini

FMC34013I: ===> Execution Server found, checks started.

FMC34013I: ===> Client message layer (server API) found, checks started.

FMC34013I: ===> Client message layer (client API) found, checks started.

FMC34013I: ===> WebSphere MQ Workflow C/C++ API found, checks started.

FMC34013I: ===> Java Agent found, checks started.

FMC34100I: Messages have been written to /var/mqm/log/fmczchk.log.
FMC34998I: See fmczchk.htm for more information on the messages.
FMC34999I: Configuration checker ended: 4 error(s), 0 warning(s), rc = 0.

-> I could logon to workflow(installed in NT machine) from another NT machine(WAS is not installed in this machine)
but, I couldnt do the same from solaris box.

What are your MQ library settings in WAS (MQ_INSTALL_ROOT or internal)?
MQ_INSTALL_ROOT

This is the error log in my solaris client machine.
inside qmgrs/FMCQM/errors

07/07/07 18:36:25
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'FMCQM' failed with reason code 2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 425 --------------------------------------------------------
07/07/07 18:36:25
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'FMCQM.CL.TCP' ended abnormally.
ACTION:
Look at previous error messages for channel program 'FMCQM.CL.TCP' in the error
files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------
07/07/07 18:36:25
AMQ9508: Program cannot connect to the queue manager.

EXPLANATION:
The connection attempt to queue manager 'FMCQM' failed with reason code 2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 425 --------------------------------------------------------
07/07/07 18:36:25
AMQ9999: Channel program ended abnormally.

EXPLANATION:
Channel program 'FMCQM.CL.TCP' ended abnormally.
ACTION:
Look at previous error messages for channel program 'FMCQM.CL.TCP' in the error
files to determine the cause of the failure.
----- amqrmrsa.c : 467 --------------------------------------------------------

In my workflow NT machine, eventvwr is showing the below error:

Connection to host '10.47.200.19' closed.

An error occurred receiving data from '10.47.200.19' over TCP/IP. The connection to the remote host has unexpectedly terminated.

Tell the systems administrator.

can you please help me in fixing this error.

	<raman_532@yaho
	NewsGroup User

Re: FMC00013E Communication error - Failing Action: Connect, Reason

7/7/2007 4:18:03 PM

4 Items, 1 Pages |< << Go >> >|

Free Download:

Invite

Members

SiteMap

Privacy | Contact Us
All Times Are GMT