| Author |
Message
|
| vpkjadhav |
 Posted: Thu Oct 26, 2006 4:08 am Post subject: FMC00013E communication error with reason code 2103 |
 |
|
Newbie
Joined: 03 Aug 2006
Posts: 9
|
After WF migration from 3.5 to 3.6 Webclient is installed on websphere. When first application connects , it gets connection. When second application tries to connected above error is thrown.
The set up was working in 3.5.
A profile is created with ckw option and .ear file is installed on Appserver.
The set up consists of total 3 profiles (server ).
What options needs to change? |
|
| Back to top |
|
 |
| chintu |
| Posted: Thu Oct 26, 2006 6:39 am Post subject: |
|
|
Acolyte
Joined: 27 Dec 2004
Posts: 64
|
|
| Back to top |
|
|
| koko |
| Posted: Thu Oct 26, 2006 9:02 am Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
If you say it was working fine on 3.5 but broke with 3.6, I bet this would be documented in any of the readmes for 3.6.
_________________
Thanks
Koko |
|
| Back to top |
|
|
| vpkjadhav |
| Posted: Thu Oct 26, 2006 9:07 am Post subject: reason code 2103 |
|
|
Newbie
Joined: 03 Aug 2006
Posts: 9
|
The WAS version is 5.1.1.5 . When a weblient is installed on WAS server,
any other application installed on same WAS server can not get connectivity. Is this a limitation of WF 3.6?
I tried to make changes on jvm properties? does not work?
any fix |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Oct 31, 2006 7:43 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
|
| Back to top |
|
|
| vpkjadhav |
| Posted: Tue Oct 31, 2006 8:08 am Post subject: web applications and web client |
|
|
Newbie
Joined: 03 Aug 2006
Posts: 9
|
Thx for post. The post talks about Two web clients running on different WAS Servers which is alright. However let me sum up the issue
3.5
uses Java API which allows only one configuration to access the applications and thin client. The applications internally use fmcrc files for connection to WF Servers using same configuration ID as Web Client. This is possible because all of them set MQConnectionType = MQClient.
3.6
uses native JAVA API. So set up in 3.5 should work with 3.6 However there is difference. Now WebClient uses fmcrc file in classes directory which is different than 3.5. There was no fmcrc file in classes directory in 3.5. This file makes MQConnectionType=MQServer. I tried changing it to MQClient bt no success!!
also there is one more thought about WebClient.properties files
This file contens
AgentConfiguration = FMC
commenting this might force all of applications to choose default configuration. Bt still this migth not solve the problem. As the problem lies in strictly one connection to whosoever comes first!! How to Overcome this?
Any though on this !!! |
|
| Back to top |
|
|
| hos |
| Posted: Thu Nov 02, 2006 3:47 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
there are a couple of weired things in your append:
1. It is an MQ restriction on UNIX platforms that a single process cannot
concurrently connect to multiple queue managers. Obviously this is
what your MQWF clients are trying and what is causing the 2103 error.
This is independent from the MQWF version and from the usage of the
Java -JNI or the native Java API.
--> MQ experts correct me if I am wrong:
a single process (e.g. a WAS JVM) cannot have concurrent connections
to different queue managers - be it a MQClient or an MQServer
connection.
2. The fmcrc file (aka 'summary profile') located in the classes
ubdirectory is not used in your case, as the precedence is, to first look
into the profile file(s) located at the MQWF install directory. Rename it
and you will see no difference in your client behaviour.
3. The summary profile contains only configurationIDs that are MQClient
type. I doubt that the MQServer connections are created by the MQWF
profile migration step. Do you touch fmcrc files manually (i.e. via
editor)??? You should NEVER do this. Always use MQWF tools to modify
profile settings!! You can never know all the internal dependencies.
4. If your scenario really worked in MQWF 3.5 you must have had a
'concentrator setup'. One MQ queue manager for all clients /
configurations. This queue manager operates in a cluster with other
queue managers that run on the MQWF server boxes.
See the Installation Guide for more info about concentrator setups. |
|
| Back to top |
|
|
| vpkjadhav |
| Posted: Thu Nov 02, 2006 7:50 am Post subject: 2103 error |
|
|
Newbie
Joined: 03 Aug 2006
Posts: 9
|
You are right. We are having a Client Concentrator set up. We are having 3 profiles
ABCX
ABCGRP01 ABCSYSX ABCQMX ABC
ABCY
ABCGRP01 ABCSYSY ABCQMY ABC
ABCZ
ABCGRP01 ABCSYSZ ABCQMZ ABC
Client Concentrator
ABCW
ABCGRP01 ABCSYSZ ABCWQM ABC
ABCGRP01 ABCSYSX ABCQM ABC
3 applications access WF Server through a single WAS Server. Set up works in 3.5 but not in 3.6 |
|
| Back to top |
|
|
|
|
