LIBGWT_CAT:1313: ERROR: Bad message

Question

I am trying to connect a clarifyCRM 11.5 based system from BEA WebLogic 7.0 Sp2
through WebLogic Tuxedo Connector.
I am getting a "Bad Message" error on the clarify side. PLease let me know what
might be the error.
Details are as follows:
================
1. BEA Weblogic is installed on Win2k and Clarify is installed on Solaris8.
2. On Solaris8 machine, the ULog shows the following error:
==============================================
150353.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1129: INFO: Connection established
with domain (domainid=<BEA001
)150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1313: ERROR: Bad message from BEA001.
Closing file descriptor
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1130: INFO: Disconnected from domain
(domainid=<BEA001>)
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1354: INFO: Retrying domain (domainid=<BEA001>)
every 60 seconds
==========================================================
3.The configuration for WTC in config.xml :
===========================================================
<WTCServer Name="MyWTCServer" Targets="myserver">
<WTCImport LocalAccessPoint="BEA001"
Name="WTCImport-1056499621875"
RemoteAccessPointList="CLAR115" RemoteName="CB_EXESUB" ResourceName="MyImportedService"/>
<WTCLocalTuxDom AccessPoint="BEA001" AccessPointId="BEA001"
ConnectionPolicy="ON_DEMAND" MaxRetries="5000000"
NWAddr="//172.24.3.208:7001" Name="WTCLocalTuxDom-1055806963906"/>
<WTCRemoteTuxDom AccessPoint="CLAR115" AccessPointId="CLAR115"
ConnectionPolicy="ON_DEMAND" LocalAccessPoint="BEA001"
NWAddr="//10.3.0.14:53401" Name="WTCRemoteTuxDom-1056499341890"/>
</WTCServer>
==================================================================
4. DMConfig on on clarify machine:
==================================================
# DMCONFIG FILE
*DM_RESOURCES
     VERSION="U22"
*DM_LOCAL
CLAR115     GWGRP=GWDOM
          TYPE="TDOMAIN"
          DOMAINID="CLAR115"
     AUDITLOG="/u02/program/tuxedo/clr_115/AUDITLOG"
     BLOCKTIME=10
     CONNECTION_POLICY="ON_DEMAND"
     DMTLOGDEV="/u02/program/tuxedo/clr_115/DMTLOG"
     DMTLOGNAME="DMTLOG_TDOM"
     MAXDATALEN=56
     MAXRACCESSPOINT=89
     MAXTRAN=100
     BLOB_SHM_SIZE=1000000
*DM_REMOTE
BEA001     TYPE=TDOMAIN
     DOMAINID="BEA001"
*DM_TDOMAIN
BEA001     NWADDR="//172.24.3.208:7001"
#     NWDEVICE="/dev/tcp"
CLAR115     NWADDR="//jupiter:53401"
#     NWDEVICE="/dev/tcp"
*DM_LOCAL_SERVICES
CB_EXESUB     LDOM="CLAR115"
*DM_REMOTE_SERVICES
===============================================================

Answer 1

Bhaskar,
The ULOG message about "Retrying" does not go with a configuration
of "ON_DEMAND". The best guess is that BEA001 is not really communicating
with whom you think. Two things to look at:
1)Check that "jupiter"=="10.3.0.14"
2) Do a dmunloadcf on the CLAR115 domain and see if the domain that is
booted
is what you expected from your configuration.
Bob Finan
Bhaskar wrote:
Bob,
No success by changing port numbers.
However after some more experimentation I am getting the following:
I installed tuxedo on another Windows 2000 m/c. (say TUX001). If I call the Clarify
domain as CLAR115 and BEA domain as BEA001 then
a) I am able to communicate between CLAR115 and TUX001
b) I am able to communicate between TUX001 and BEA001 by using WTC in BEA001
c) But, I am still not able to communicate between BEA001 and CLAR115. I still
obtain a BAD Message error on the CLAR115 side
Quite puzzled with this.
Regards
Bhaskar
"Bhaskar" <[email protected]> wrote:
Thanks Bob,
I would surely try with using another port.
Currently,I am using a different port for the WLS admin server. Secondly,
in case
I was using a port that was already being used by some other server,
one of the
two servers would not have come up.
Is there any method to read the ULogs for the Local tuxedo domain on
WLS end.
thanks and regards
Bhaskar
Bob Finan <[email protected]> wrote:
Bhaskar,
You are probably using the //172.24.3.208:7001 port for other purposes
and this is
causing the problem(e.g. 7001 is the default WLS admin port).Try
changing the
NWAddr port number for the WTCLocalTuxDom..
Bob Finan
Bhaskar wrote:
I am trying to connect a clarifyCRM 11.5 based system from BEA WebLogic
7.0 Sp2
through WebLogic Tuxedo Connector.
I am getting a "Bad Message" error on the clarify side. PLease let
me
know what
might be the error.
Details are as follows:
================
1. BEA Weblogic is installed on Win2k and Clarify is installed on Solaris8.
2. On Solaris8 machine, the ULog shows the following error:
==============================================
150353.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1129: INFO: Connection
established
with domain (domainid=<BEA001
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1313: ERROR: Bad message
from BEA001.
Closing file descriptor
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1130: INFO: Disconnected
from domain
(domainid=<BEA001>)
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1354: INFO: Retrying
domain
(domainid=<BEA001>)
every 60 seconds
==========================================================
3.The configuration for WTC in config.xml :
===========================================================
<WTCServer Name="MyWTCServer" Targets="myserver">
<WTCImport LocalAccessPoint="BEA001"
Name="WTCImport-1056499621875"
RemoteAccessPointList="CLAR115" RemoteName="CB_EXESUB"
ResourceName="MyImportedService"/>
<WTCLocalTuxDom AccessPoint="BEA001" AccessPointId="BEA001"
ConnectionPolicy="ON_DEMAND" MaxRetries="5000000"
NWAddr="//172.24.3.208:7001" Name="WTCLocalTuxDom-1055806963906"/>
<WTCRemoteTuxDom AccessPoint="CLAR115" AccessPointId="CLAR115"
ConnectionPolicy="ON_DEMAND" LocalAccessPoint="BEA001"
NWAddr="//10.3.0.14:53401" Name="WTCRemoteTuxDom-1056499341890"/>
</WTCServer>
==================================================================
4. DMConfig on on clarify machine:
==================================================
# DMCONFIG FILE
*DM_RESOURCES
     VERSION="U22"
*DM_LOCAL
CLAR115     GWGRP=GWDOM
          TYPE="TDOMAIN"
          DOMAINID="CLAR115"
     AUDITLOG="/u02/program/tuxedo/clr_115/AUDITLOG"
     BLOCKTIME=10
     CONNECTION_POLICY="ON_DEMAND"
     DMTLOGDEV="/u02/program/tuxedo/clr_115/DMTLOG"
     DMTLOGNAME="DMTLOG_TDOM"
     MAXDATALEN=56
     MAXRACCESSPOINT=89
     MAXTRAN=100
     BLOB_SHM_SIZE=1000000
*DM_REMOTE
BEA001     TYPE=TDOMAIN
     DOMAINID="BEA001"
*DM_TDOMAIN
BEA001     NWADDR="//172.24.3.208:7001"
#     NWDEVICE="/dev/tcp"
CLAR115     NWADDR="//jupiter:53401"
#     NWDEVICE="/dev/tcp"
*DM_LOCAL_SERVICES
CB_EXESUB     LDOM="CLAR115"
*DM_REMOTE_SERVICES
===============================================================
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
Bhaskar,<br>
You are probably using the //172.24.3.208:7001 port for other purposes
and
this is<br>
causing the problem(e.g. 7001 is the default WLS admin port).Try changing
the <br>
NWAddr port number for the WTCLocalTuxDom..<br>
Bob Finan<br>
<br>
Bhaskar wrote:<br>
<blockquote type="cite" cite="[email protected]">
<pre wrap="">I am trying to connect a clarifyCRM 11.5 based system
from BEA WebLogic 7.0 Sp2
through WebLogic Tuxedo Connector.
I am getting a "Bad Message" error on the clarify side. PLease let me
know what
might be the error.
Details are as follows:
================
1. BEA Weblogic is installed on Win2k and Clarify is installed on Solaris8.
2. On Solaris8 machine, the ULog shows the following error:
==============================================
150353.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1129: INFO: Connection
established
with domain (domainid=<BEA001
</pre>
<blockquote type="cite">
<pre wrap="">)
</pre>
</blockquote>
<pre wrap=""><!---->150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1313:
ERROR: Bad message from BEA001.
Closing file descriptor
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1130: INFO: Disconnected
from domain
(domainid=<BEA001>)
150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1354: INFO: Retrying domain
(domainid=<BEA001>)
every 60 seconds
==========================================================
3.The configuration for WTC in config.xml :
===========================================================
<WTCServer Name="MyWTCServer" Targets="myserver">
<WTCImport LocalAccessPoint="BEA001"
Name="WTCImport-1056499621875"
RemoteAccessPointList="CLAR115" RemoteName="CB_EXESUB" ResourceName="MyImportedService"/>
<WTCLocalTuxDom AccessPoint="BEA001" AccessPointId="BEA001"
ConnectionPolicy="ON_DEMAND" MaxRetries="5000000"
NWAddr="//172.24.3.208:7001" Name="WTCLocalTuxDom-1055806963906"/>
<WTCRemoteTuxDom AccessPoint="CLAR115" AccessPointId="CLAR115"
ConnectionPolicy="ON_DEMAND" LocalAccessPoint="BEA001"
NWAddr="//10.3.0.14:53401" Name="WTCRemoteTuxDom-1056499341890"/>
</WTCServer>
==================================================================
4. DMConfig on on clarify machine:
==================================================
# DMCONFIG FILE
*DM_RESOURCES
     VERSION="U22"
*DM_LOCAL
CLAR115     GWGRP=GWDOM
          TYPE="TDOMAIN"
          DOMAINID="CLAR115"
     AUDITLOG="/u02/program/tuxedo/clr_115/AUDITLOG"
     BLOCKTIME=10
     CONNECTION_POLICY="ON_DEMAND"
     DMTLOGDEV="/u02/program/tuxedo/clr_115/DMTLOG"
     DMTLOGNAME="DMTLOG_TDOM"
     MAXDATALEN=56
     MAXRACCESSPOINT=89
     MAXTRAN=100
     BLOB_SHM_SIZE=1000000
*DM_REMOTE
BEA001     TYPE=TDOMAIN
     DOMAINID="BEA001"
*DM_TDOMAIN
BEA001     NWADDR="//172.24.3.208:7001"
#     NWDEVICE="/dev/tcp"
CLAR115     NWADDR="//jupiter:53401"
#     NWDEVICE="/dev/tcp"
*DM_LOCAL_SERVICES
CB_EXESUB     LDOM="CLAR115"
*DM_REMOTE_SERVICES
===============================================================
</pre>
</blockquote>
<br>
</body>
</html>
[att1.html]