WTC in 7.0

We finally got WTC in 7.0 to work my hand editing the config.xml file to
move part of the WTC config. Apparently the console doesn't setup
remote services properly.
My question is there any tracing available in the WTC?
Is there any monitoring that can be done on the health of WTC?
If WTC dies (and it does!!!) is there a way to restart things without
having to bounce our server??
Thanks
Tom

I don't know the version info off the top of my head but it was the GA
Release download off the Web site last week or so.
Tom
Bob Finan wrote:
Tom,
The tracing for WTC in 7.0 is done by defining the weblogic.wtc.TraceLevel
property when the server is started. The values for this property are the
same
as when TraceLevel was used as a startup class argument.
(ie >=15000 for tbridge,>=25000 for gwt, >=55000 for jatmi, >= 65000 for
corba)
Note: This TraceLevel is in addition to settings for the server to send the
debug output
to the log file and what type of logging needs to be done(I usually just put
it at Info to
get everything).
There are no WTC specific monitors that were added for 7.0.
If the WTCServerMBean is untargeted and retargeted from/to a server
then the service should reinitialize/restart without havinf to bring down
the server.
I'll check on why the console created the config.xml in the way your
previous email shows. I guess you figured out that the tBridgeRedirect MBean
should not be defined within the tBridgeGlobal MBean's scope. There were
some fixes applied in March that may be applicable to this. Do you know
the version information for the WLS product you have?
Bob Finan
Tom Gerber wrote:
We finally got WTC in 7.0 to work my hand editing the config.xml file to
move part of the WTC config. Apparently the console doesn't setup
remote services properly.
My question is there any tracing available in the WTC?
Is there any monitoring that can be done on the health of WTC?
If WTC dies (and it does!!!) is there a way to restart things without
having to bounce our server??
Thanks
Tom

Similar Messages

  • Start order between WTC server and EJBs provides exported services

    Using WLS 10.3.0 and Tuxedo 11.1.1.2.0 (32-bit) with WTC as the communication bus between the 2 platforms....
    Running load balancing/failover inside Tuxedo using the cluster setup as described by:
    http://docs.oracle.com/cd/E13222_01/wls/docs81/wtc_admin/Cluster.html#1110847
    and got WLS rigged in a cluster with 2 nodes (managed servers) on separate machines. When I take down and up one of the nodes soft (with start/stop scripts) everything works fine during shutdown but not upon starting. What I think happens is that the WTC server starts first before the EJBs that provide exported services. In the Tuxedo log a connection is first established then a ton of TPENOENT until the EJBs get going. Any way to reorder these resources during start up? So that the EJBs are ready first prior to the WTC server?
    mvh / Matthew Young

    Q8. What versions of Tuxedo are supported?
    A8. WTC 1.0 will support Tuxedo 6.5 and Tuxedo 8.0. WTC 1.1 (which adds
    CORBA support) will support Tuxedo 6.5 and Tuxedo 8.0. Soon after the
    release of both of these products we will certify WTC with Tuxedo 7.1.
    However, the version of Tuxedo 7.1 you will need to have will be Tuxedo 7.1
    after a certain patch level, which I don't know the number of yet. I will
    attempt to keep the public informed about which patch level will be required
    in Tuxedo 7.1
    Q9. What WLS Releases will be supported?
    A9. WTC 1.0 will be certified on WLS 6.0 SP2, WTC 1.1 will be bundled with
    WLS SilverSword release (6.1?)
    Q10. How will WTC be packaged?
    A10. WTC 1.0 will be a separately downloaded binary (one for unix, one for
    NT) that the user will have to install and configure in his/her WLS
    environment. (Configuration will consist of putting the jatmi.jar file into
    the classpath (as well as the normal BDMCONFIG configuration, of course)).
    WTC 1.1 will be bundled right in there with the WLS SilverSword release.
    Q11. When will WTC go live (no more beta)?
    A11. This is a question for Jeff Cutler, but my impression is that WTC 1.0
    will be shipped in the same time-frame as the Tuxedo 8.0 release and
    obviously (see A10) WTC 1.1 will be shipped with WLS SilverSword.
    John Wells (Aziz)
    [email protected]

  • JNDI conflict for WTC in cluster env

    I found this error when starting more than one managed server in clustered environment.
    <Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
    an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The
    object you have bound from 161.215.254.40 is non clusterable and you have tried
    to bind more than once from two or more servers. Such objects can only deployed
    from one server.>
    <Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
    an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The
    object you have bound from 161.215.254.41 is non clusterable and you have tried
    to bind more than once from two or more servers. Such objects can only deployed
    from one server.>
    <Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
    an object under the name tuxedo.services.TuxedoCorbaConnection in the JNDI tree.
    The object you have bound from 161.215.254.40 is non clusterable and you have
    tried to bind more than once from two or more servers. Such objects can only deployed
    from one server.>
    <Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start: You tried to bind
    an object under the name tuxedo.services.TuxedoCorbaConnection in the JNDI tree.
    The object you have bound from 161.215.254.41 is non clusterable and you have
    tried to bind more than once from two or more servers. Such objects can only deployed
    from one server.>
    Please help.

    Hi Salim,
    Salim Djaffar wrote:
    "A. Honghsi Lo" <[email protected]> wrote:
    Hi Salim,
    Salim Djaffar wrote:
    I have a stateless ejb using this context to get the same JNDI namefrom tuxedo
    connection factory. This ejb is deployed as clustered. I deployed thisejb into
    many managed servers in the cluster. In other word every managed serverdeploys
    this ejb.
    I also have the web server configured with clustered plugin, but Iguess it has
    nothing to do with it.
    Isn't the wtc_config.xml stanza "WlsClusterName" a little misleadingsince it
    does not support cluster at all ?Yes, it is kind of misleading. It is not used in WTC and will be removed
    from dtd
    (and document) in the future.
    Besides in the admin console, I configured the WTC startup target to"cluster".
    Is there any advise to overcome this problem ?I can't think of a good way to overcome this problem. One thing you
    can do is to
    target WTC to a WLS in the cluster. One drawback is that you have only
    one WTC in
    the cluster.
    Honghsi
    Does it mean I have to use RMI/IIOP to do the lookup to one particular server
    for WTC ?No. The RMI/IIOP lookup is specific for CORBA NS lookup. It won't help you at
    all.
    >
    Will WTC be available for clustered in the future ?There will be some changes to WTC that will make it possible for you to deploy WTC
    instance on every WL server in the cluster. There are some administration (and
    configuration) restrictions associate with it if you want to be able to do load
    balancing and fail over.
    Hong-Hsi :-)
    >
    >
    Thanks.
    Please help.
    "A. Honghsi Lo" <[email protected]> wrote:
    Hi Salim,
    The current version of WTC will have this problem. Because the connection
    factory is bound
    to the same name in JNDI tre. However, the first WTC booted in the
    WLS
    cluster should
    still be available to use.
    BTW, I am interested in knowing how you use WTC currently, and howyou
    plan to use in the
    future.
    Honghsi
    Salim Djaffar wrote:
    I found this error when starting more than one managed server in
    clustered
    environment.
    <Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
    You
    tried to bind
    an object under the name tuxedo.services.TuxedoConnection in the
    JNDI
    tree. The
    object you have bound from 161.215.254.40 is non clusterable and
    you
    have tried
    to bind more than once from two or more servers. Such objects can
    only
    deployed
    from one server.>
    <Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
    You
    tried to bind
    an object under the name tuxedo.services.TuxedoConnection in the
    JNDI
    tree. The
    object you have bound from 161.215.254.41 is non clusterable and
    you
    have tried
    to bind more than once from two or more servers. Such objects can
    only
    deployed
    from one server.>
    <Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
    You
    tried to bind
    an object under the name tuxedo.services.TuxedoCorbaConnection in
    the
    JNDI tree.
    The object you have bound from 161.215.254.40 is non clusterable
    and
    you have
    tried to bind more than once from two or more servers. Such objectscan only deployed
    from one server.>
    <Oct 5, 2001 9:14:07 AM CDT> <Error> <Cluster> <Conflict start:
    You
    tried to bind
    an object under the name tuxedo.services.TuxedoCorbaConnection in
    the
    JNDI tree.
    The object you have bound from 161.215.254.41 is non clusterable
    and
    you have
    tried to bind more than once from two or more servers. Such objectscan only deployed
    from one server.>
    Please help.

  • I have a problem when running my own EJB as a TUXEDO service using WTC.

    Hello,
    I have a problem when running my own EJB as a TUXEDO service using WTC. I am using TUXEDO 8.1 and WL 9.1.
    When I am trying to run my own EJB as a TUXEDO service error appears.
    TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could not find service TOUPPER
    at weblogic.wtc.gwt.WTCService.getImport(WTCService.java:4988)
    at weblogic.wtc.gwt.TuxedoConnection.getImport(TuxedoConnection.java:303)
    at weblogic.wtc.gwt.TuxedoConnection.tpcall(TuxedoConnection.java:1302)
    at examples.MyTestSessionBean.Toupper(MyTestSessionBean.java:102)
    at examples.TestSessionBean_knby6k_EOImpl.Toupper(TestSessionBean_knby6k_EOImpl.java:61)
    at net.roseindia.web.servlets.SessionTestServlet.doGet(SessionTestServlet.java:69)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    e8
    10
    java.rmi.RemoteException: EJB Exception: ; nested exception is:
    java.lang.NullPointerException
    at weblogic.ejb.container.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:95)
    at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:713)
    at weblogic.ejb.container.internal.BaseEJBObject.handleSystemException(BaseEJBObject.java:681)
    at weblogic.ejb.container.internal.BaseEJBObject.postInvoke1(BaseEJBObject.java:447)
    at weblogic.ejb.container.internal.StatelessEJBObject.postInvoke1(StatelessEJBObject.java:72)
    at weblogic.ejb.container.internal.BaseEJBObject.postInvokeTxRetry(BaseEJBObject.java:374)
    at examples.TestSessionBean_knby6k_EOImpl.Toupper(TestSessionBean_knby6k_EOImpl.java:75)
    at net.roseindia.web.servlets.SessionTestServlet.doGet(SessionTestServlet.java:69)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:272)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:165)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3153)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1973)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1880)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1310)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: java.lang.NullPointerException
    at examples.MyTestSessionBean.Toupper(MyTestSessionBean.java:130)
    at examples.TestSessionBean_knby6k_EOImpl.Toupper(TestSessionBean_knby6k_EOImpl.java:61)
    ... 15 more
    Any clue on this.
    With Regards,
    MVS

    If you are trying to create a Tuxedo service in Java using WTC you need to develop an EJB that implements the TuxedoService interface and register its home in JNDI so WTC can look it up. Once that is done you can then export the service to a remote domain in the WTC configuration.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • WTC performance issue

    Here's a few mesure I've completed.
    I'm working with WLS6.1sp2/solaris5.8 - Tuxedo 6.5 - Jolt 1.2
    (service TOUPPER just return uppercased incoming buffer)
    C client calling java service published in WTC : 190 ms
    C client calling C service published in Tuxedo : 30 ms (60 ms in WS mode)
    Java Client(servlet) using WTC to call Tuxedo service : 280 ms
    Java Client(servlet) using JOLT to call Tuxedo service : 30 ms
    Is there any hope/way to improve it ?
    Has anybody better perfs ?
    Thanks.

    Sorry, the first message is with WTC TraceLevel=100000
    With tracing disabled, it's better.
    (but still far form jolt !!)
    C client calling java service published in WTC : 100 ms (130 in WS mode)
    C client calling C service published in Tuxedo : 30 ms (60 ms in WS mode)
    Java Client(servlet) using WTC to call Tuxedo service : 110 ms
    Java Client(servlet) using JOLT to call Tuxedo service : 30 ms

  • Every 2nd request from WTC fails

    Hi there,
    We are using WLS 10.0.1 integrated with Tuxedo 6.5 and have this strange situation where every second request sent from WLS to Tuxedo fails with "TPESYSTEM(12):0:0:TPED_MINVAL(0):QMNONE(0):0". There is no other associated message.
    Our call sequence consists of:
    ApplicationToMonitorInterface connection = tuxedoConnectionFactory.getTuxedoConnection();
    Reply reply = connection.tpcall(requestMapper.getServiceName(), requestMapper.getTypedFmlBuffer(),
    ApplicationToMonitorInterface.TPNOAUTH | ApplicationToMonitorInterface.TPNOTIME);
    process reply
    connection.tpterm();
    The tpcall is throwing a TPException on every second invocation. The amount of time (seconds or minutes) that passes between invocations seems to be irrelevent. I've tried various combinations of flags passed to the tpcall, including zero, with no apparent difference.
    I turned up WTC logging to try and troubleshoot the issue. Log fragments are pasted below.
    Note that the same reader thread "ExecuteThread: '4'" appears to be used for both calls, suggesting that they are both making use of the same TCP connection.
    A tcpdump of both calls reveals (apparently complete) outgoing request and incoming reply data in both cases. However, it looks as though WTC gets its input stream out of sync and (possibly) reads left over data from the 1st call. WTC ditches the connection when the 2nd call fails, so the 3rd call starts off with a brand new connection again.
    Any ideas?
    Please excuse the bulk, but here is the trace from the successful call:
    ExecuteThread: '1'<BEA-180046> <[/TuxedoConnection/TuxedoConnection/>
    ExecuteThread: '1'<BEA-180046> <no transaction>
    ExecuteThread: '1'<BEA-180046> <]/TuxedoConnection/TuxedoConnection/30>
    ExecuteThread: '1'<BEA-180046> <[/TuxedoConnection/tpcall/GSM_GetAcct/32>
    ExecuteThread: '1'<BEA-180046> <[/TuxedoConnection/getProviderRoute/GSM_GetAcct>
    ExecuteThread: '1'<BEA-180046> <[/WTCRouteManager/selectTargetRotes/GSM_GetAcct>
    ExecuteThread: '1'<BEA-180046> <[/WTCService/getImport/(svc = GSM_GetAcct, xid = null)>
    ExecuteThread: '1'<BEA-180046> <[/TDMImport/getStatus/>
    ExecuteThread: '1'<BEA-180046> <[/TDMRemoteTDomain/getTsession/MTS-Remote, create = false>
    ExecuteThread: '1'<BEA-180046> <]/TDMRemoteTDomain/getTsession/20/null>
    ExecuteThread: '1'<BEA-180046> </TDMRemoteTDomain/getTsession/100/null>
    ExecuteThread: '1'<BEA-180046> <]/TDMImport/getStatus/30/AVAILABLE>
    ExecuteThread: '1'<BEA-180046> <]/WTCService/getImport/40/(0)>
    ExecuteThread: '1'<BEA-180046> <[/TDMRemoteTDomain/getTsession/MTS-Remote, create = true>
    ExecuteThread: '1'<BEA-180046> <[/WLSInvoke/weblogic.wtc.gwt.TDMLocalTDomain@264a55ca/weblogic.wtc.gwt.TDMRemoteTDomain@acb54dc7>
    ExecuteThread: '1'<BEA-180046> <]/WLSInvoke/10>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/set_compression_threshold/2147483647>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/set_compression_threshold/20/>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/set_sess_sec/NONE>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/set_sess_sec/30/>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/setDesiredName/WTC_OBF>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/setDesiredName/10/>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/set_dom_target_name/OBF_WTC>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/set_dom_target_name/10/>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/set_local_domain_name/MTS-Local>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/set_local_domain_name/10>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/setRemoteDomainId/OBF_WTC>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/setRemoteDomainId/10>
    ExecuteThread: '1'<BEA-180046> <[/TDMRemoteTDomain/getKeepAlive>
    ExecuteThread: '1'<BEA-180046> <]/TDMRemoteTDomain/getKeepAlive/10>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/setKeepAlive/0>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/setKeepAlive/10/>
    ExecuteThread: '1'<BEA-180046> <[/TDMRemoteTDomain/getKeepAliveWait>
    ExecuteThread: '1'<BEA-180046> <]/TDMRemoteTDomain/getKeepAliveWait/10>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/setKeepAliveWait/0>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/setKeepAliveWait/10/>
    ExecuteThread: '1'<BEA-180046> <[/dsession/setAppKey/TpUsrFile>
    ExecuteThread: '1'<BEA-180046> <]/dsession/setAppKey/10/>
    ExecuteThread: '1'<BEA-180046> <[/dsession/setAllowAnonymous/false>
    ExecuteThread: '1'<BEA-180046> <]/dsession/setAllowAnonymous/10/>
    ExecuteThread: '1'<BEA-180046> <[/dsession/setDfltAppKey/-1>
    ExecuteThread: '1'<BEA-180046> <]/dsession/setDfltAppKey/10/>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/setEncryptionFlags/39>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/setEncryptionFlags/10>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/tpinit/weblogic.wtc.jatmi.TPINIT@355e82>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/do_connect/WTC_OBF>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/alloc_TDOM/14/null>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/alloc_TDOM/10/TDOM:GWNW_XATMI_PRE_NW_ACALL1:1:-1:0:0:0:0:0:0:0:50:null>
    ExecuteThread: '1'<BEA-180046> <[/write_dom_65_tfmh/WTC_OBF/10/134217727>
    ExecuteThread: '1'<BEA-180046> </write_dom_65_tfmh/header calculated_size=524>
    ExecuteThread: '1'<BEA-180046> </write_dom_65_tfmh/opcode calculated_size=540>
    ExecuteThread: '1'<BEA-180046> </write_dom_65_tfmh/total calculated_size=540>
    ExecuteThread: '1'<BEA-180046> <[/TpeOut/writeTuxedoMessage/>
    ExecuteThread: '1'<BEA-180046> </TpeOut/writeTuxedoMessage/myNeedToWrite=32/myMark=32/myProtocol=10/parsedMetahdr=false>
    ExecuteThread: '1'<BEA-180046> <]/TpeOut/writeTuxedoMessage/70/>
    ExecuteThread: '1'<BEA-180046> </tfmh/write_dom_65_tfmh/TdomTcb=TDOM:GWNW_XATMI_PRE_NW_ACALL1:1:-1:0:0:0:0:0:0:0:50:null>
    ExecuteThread: '1'<BEA-180046> <[/TpeOut/writeTuxedoMessage/>
    ExecuteThread: '1'<BEA-180046> </TpeOut/writeTuxedoMessage/myNeedToWrite=540/myMark=540/myProtocol=10/parsedMetahdr=true>
    ExecuteThread: '1'<BEA-180046> <*]/TpeOut/writeTuxedoMessage/40/>
    ExecuteThread: '1'<BEA-180046> <]/write_dom_65_tfmh/110/0/>
    ExecuteThread: '1'<BEA-180046> <[/read_dom_65_tfmh/10>
    ExecuteThread: '1'<BEA-180046> <[/TpeIn/readTuxedoMessage/true>
    ExecuteThread: '1'<BEA-180046> </TpeIn/readTuxedoMessage/myNeedToRead=32/myOffset=0/myMark=0/myProtocol=10/parsedMetahdr=false>
    ExecuteThread: '1'<BEA-180046> </TpeIn/readTuxedoMessage/toRead=32>
    ExecuteThread: '1'<BEA-180046> </TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=32/myMark=0>
    ExecuteThread: '1'<BEA-180046> </TpeIn/readTuxedoMessage/size=544>
    ExecuteThread: '1'<BEA-180046> <[/TpeIn/readTuxedoMessage/false>
    ExecuteThread: '1'<BEA-180046> </TpeIn/readTuxedoMessage/myNeedToRead=512/myOffset=32/myMark=0/myProtocol=10/parsedMetahdr=true>
    ExecuteThread: '1'<BEA-180046> </TpeIn/readTuxedoMessage/toRead=512>
    ExecuteThread: '1'<BEA-180046> </TpeIn/readTuxedoMessage/myNeedToRead=0/myOffset=544/myMark=0>
    ExecuteThread: '1'<BEA-180046> <]/TpeIn/readTuxedoMessage/120/true>
    ExecuteThread: '1'<BEA-180046> <]/TpeIn/readTuxedoMessage/150/true>
    ExecuteThread: '1'<BEA-180046> </tfmh/read_dom_65_tfmh/opcode=GWNW_XATMI_PRE_NW_ACALL1_RPLY>
    ExecuteThread: '1'<BEA-180046> <[/TpeIn/available/>
    ExecuteThread: '1'<BEA-180046> <]/TpeIn/available/20/512>
    ExecuteThread: '1'<BEA-180046> </read_dom_65_tfmh/bufsize=544 available=512>
    ExecuteThread: '1'<BEA-180046> <[/TdomTcb/set_security_type 0>
    ExecuteThread: '1'<BEA-180046> <]/TdomTcb/set_security_type>
    ExecuteThread: '1'<BEA-180046> <[/TdomTcb/set_tm_release 64>
    ExecuteThread: '1'<BEA-180046> <]/TdomTcb/set_tm_release>
    ExecuteThread: '1'<BEA-180046> <[/TdomTcb/set_dom_protocol 13>
    ExecuteThread: '1'<BEA-180046> <]/TdomTcb/set_dom_protocol>
    ExecuteThread: '1'<BEA-180046> <]/read_dom_65_tfmh/70/0/0>
    ExecuteThread: '1'<BEA-180046> <Remote gateway support features = 0>
    ExecuteThread: '1'<BEA-180046> < /dsession(1)/do_connect/dom_protocol 13>
    ExecuteThread: '1'<BEA-180046> </dsession(1)/do_connect/no LLE protocol>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/setUpTuxedoAAA/>
    ExecuteThread: '1'<BEA-180046> <]/dsession/setUpTuxedoAAA/10/return 0>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/dmqDecision/>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/dmqDecision/10>
    xecuteThread: '1' BEA-180087> <Established a connection to a remote domain OBF_WTC.>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/do_connect/170/>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/tpinit/30/>
    ExecuteThread: '1'<BEA-180046> <]/TDMRemoteTDomain/getTsession/90/weblogic.wtc.gwt.gwdsession@1>
    ExecuteThread: '1'<BEA-180046> </TDMRemoteTDomain/getTsession/100/weblogic.wtc.gwt.gwdsession@1>
    ExecuteThread: '1'<BEA-180046> <]/WTCRouteManager/selectTargetRotes/30/weblogic.wtc.gwt.gwdsession@1>
    ExecuteThread: '1'<BEA-180046> <]/TuxedoConnection/getProviderRoute/20>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/tpcall/GSM_GetAcct/weblogic.wtc.jatmi.TypedFML32@247c48/32/null>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/tpacall/GSM_GetAcct/weblogic.wtc.jatmi.TypedFML32@247c48/32/null/0>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/_tpacall_internal/GSM_GetAcct/weblogic.wtc.jatmi.tfmh@5b63c2/32/null/0>
    ExecuteThread: '1'<BEA-180046> <myAppKey = null>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/alloc_TDOM/1/GSM_GetAcct>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/alloc_TDOM/10/TDOM:GWNW_XATMI_CALL:2:-1:0:0:32:0:0:0:0:50:GSM_GetAcct>
    ExecuteThread: '1'<BEA-180046> <[/rdsession(1)/add_rplyObj/SessionAcallDescriptor:2:false/weblogic.wtc.jatmi.TuxRply@f29035/-1>
    ExecuteThread: '1'<BEA-180046> <]/rdsession(1)/add_rplyObj/40/>
    ExecuteThread: '1'<BEA-180046> <[/write_dom_65_tfmh/WTC_OBF/13/2147483647>
    ExecuteThread: '1'<BEA-180046> </write_dom_65_tfmh/header calculated_size=76>
    ExecuteThread: '1'<BEA-180046> </write_dom_65_tfmh/opcode calculated_size=96>
    ExecuteThread: '1'<BEA-180046> <[/FML32/_tmpresend/java.io.DataOutputStream@d9af8d>
    ExecuteThread: '1'<BEA-180046> <numPointerFields=0 numView32Fields=0 numFml32Fields=0>
    ExecuteThread: '1'<BEA-180046> <]/TypedFML32/_tmpresend/60/>
    ExecuteThread: '1'<BEA-180046> <Outbound UDATA: buffer type(FML32, null)>
    ExecuteThread: '1'<BEA-180072> <+++++ 65 User Data(184) +++++>
    ExecuteThread: '1'<BEA-180113> <FF FF D8 F0 00 00 00 B8 7F FF FF FF 00 00 00 08 00 00 00 00 .......?............>
    ExecuteThread: '1'<BEA-180113> <00 00 00 10 00 10 DF 9D 00 00 00 01 02 10 DF 93 00 00 00 01 .......?.......?....>
    ExecuteThread: '1'<BEA-180113> <0A 10 DF 2F 00 00 00 13 00 00 00 0B 46 4F 58 5F 53 59 53 54 ............FOX.SYST>
    ExecuteThread: '1'<BEA-180113> <45 4D 00 00 0A 10 DF 39 00 00 00 1A 00 00 00 12 38 39 63 61 EM.....9........89ca>
    ExecuteThread: '1'<BEA-180113> <2D 61 31 34 66 65 65 31 32 34 34 36 65 00 00 00 0A 10 DF 43 .a14fee12446e......C>
    ExecuteThread: '1'<BEA-180113> <00 00 00 13 00 00 00 0B 46 4F 58 5F 53 59 53 54 45 4D 00 00 ........FOX.SYSTEM..>
    ExecuteThread: '1'<BEA-180113> <0A 10 DF 4D 00 00 00 14 00 00 00 0C 47 53 4D 5F 47 65 74 41 ...M........GSM.GetA>
    ExecuteThread: '1'<BEA-180113> <63 63 74 00 0A 10 DF F7 00 00 00 0C 00 00 00 04 46 4F 58 00 cct.............FOX.>
    ExecuteThread: '1'<BEA-180113> <0A 11 3E 7B 00 00 00 11 00 00 00 09 32 32 32 32 32 32 32 32 ............22222222>
    ExecuteThread: '1'<BEA-180113> <00 00 00 00 .... >
    ExecuteThread: '1'<BEA-180073> <+++++ END +++++>
    ExecuteThread: '1'<BEA-180046> </write_dom_65_tfmh/total calculated_size=280>
    ExecuteThread: '1'<BEA-180046> <[/TpeOut/writeTuxedoMessage/>
    ExecuteThread: '1'<BEA-180046> </TpeOut/writeTuxedoMessage/myNeedToWrite=32/myMark=32/myProtocol=13/parsedMetahdr=false>
    ExecuteThread: '1'<BEA-180046> <]/TpeOut/writeTuxedoMessage/70/>
    ExecuteThread: '1'<BEA-180046> <[/TpeOut/write(b)/>
    ExecuteThread: '1'<BEA-180046> <]/TpeOut/write/10/>
    ExecuteThread: '1'<BEA-180046> <[/TpeOut/write(b)/>
    ExecuteThread: '1'<BEA-180046> <]/TpeOut/write/10/>
    ExecuteThread: '1'<BEA-180046> </tfmh/write_dom_65_tfmh/TdomTcb=TDOM:GWNW_XATMI_CALL:2:-1:0:0:32:0:0:0:0:50:GSM_GetAcct>
    ExecuteThread: '1'<BEA-180046> <[/TpeOut/write(b)/>
    ExecuteThread: '1'<BEA-180046> <]/TpeOut/write/10/>
    ExecuteThread: '1'<BEA-180046> <[/TpeOut/write(b)/>
    ExecuteThread: '1'<BEA-180046> <[/TpeOut/writeTuxedoMessage/>
    ExecuteThread: '1'<BEA-180046> </TpeOut/writeTuxedoMessage/myNeedToWrite=280/myMark=280/myProtocol=13/parsedMetahdr=true>
    ExecuteThread: '1'<BEA-180046> <*]/TpeOut/writeTuxedoMessage/40/>
    ExecuteThread: '1'<BEA-180046> <]/TpeOut/write/30/>
    ExecuteThread: '1'<BEA-180046> <]/write_dom_65_tfmh/110/0/>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/_tpacall_internal/40/SessionAcallDescriptor:2:false>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/tpacall/100/SessionAcallDescriptor:2:false>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/tpgetrply/SessionAcallDescriptor:2:false/32>
    ExecuteThread: '1'<BEA-180046> <[/dsession(1)/_tpgetrply_internal/SessionAcallDescriptor:2:false/32>
    ExecuteThread: '1'<BEA-180046> <[/TuxRply/get_specific_reply/SessionAcallDescriptor:2:false/weblogic.wtc.gwt.gwdsession@1/true>
    ExecuteThread: '1'<BEA-180046> <TuxRply/get_specific_reply: Thr Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] waiting for message oid SessionAcallDescriptor:2:false/weblogic.wtc.gwt.gwdsession@1 on lockReq = weblogic.wtc.jatmi.TuxRply$LockReq@948b59>
    ExecuteThread: '4' <BEA-180046> <[/TuxedoMuxableSocket/dispatch/>
    ExecuteThread: '4' <BEA-180046> </TuxedoMuxableSocket/dispatch/myOffset=444/myDecryptOffset=0/myProtocol=13>
    ExecuteThread: '4' <BEA-180046> </TuxedoMuxableSocket/dispatch/size=444>
    ExecuteThread: '4' <BEA-180046> <[/rdsession(1)/allocTfmh/>
    ExecuteThread: '4' <BEA-180046> </rdsession(1)/allocTfmh/null>
    ExecuteThread: '4' <BEA-180046> <]/rdsession(1)/allocTfmh/weblogic.wtc.jatmi.tfmh@489f21>
    ExecuteThread: '4' <BEA-180046> <[/read_dom_65_tfmh/13>
    ExecuteThread: '4' <BEA-180046> </tfmh/read_dom_65_tfmh/opcode=GWNW_XATMI_REPLY>
    ExecuteThread: '4' <BEA-180046> </read_dom_65_tfmh/bufsize=444 available=968>
    ExecuteThread: '4' <BEA-180046> </read_dom_65_tfmh/prior compos bufsize=364 available=920>
    ExecuteThread: '4' <BEA-180046> </read_dom_65_tfmh/post compos bufsize=364 available=920>
    ExecuteThread: '4' <BEA-180046> <Inbound 65 UDATA: buffer type(FML32, null)>
    ExecuteThread: '4' <BEA-180072> <+++++ User Data(364) +++++>
    ExecuteThread: '4' <BEA-180113> <FF FF D8 F0 00 00 01 2C 00 00 10 00 00 00 00 10 00 00 00 00 ....................>
    ExecuteThread: '4' <BEA-180113> <00 00 00 10 0A 10 DF 2F 00 00 00 13 00 00 00 0B 46 4F 58 5F ................FOX.>
    ExecuteThread: '4' <BEA-180113> <53 59 53 54 45 4D 00 00 0A 10 DF 39 00 00 00 0E 00 00 00 06 SYSTEM.....9........>
    ExecuteThread: '4' <BEA-180113> <44 75 6D 6D 79 00 00 00 0A 10 DF 43 00 00 00 0C 00 00 00 04 Dummy......C........>
    ExecuteThread: '4' <BEA-180113> <46 4F 58 00 0A 10 DF 4D 00 00 00 14 00 00 00 0C 47 53 4D 5F FOX....M........GSM.>
    ExecuteThread: '4' <BEA-180113> <47 65 74 41 63 63 74 00 0A 10 DF F7 00 00 00 0D 00 00 00 05 GetAcct.............>
    ExecuteThread: '4' <BEA-180113> <53 74 75 62 00 00 00 00 0A 11 3E 77 00 00 00 10 00 00 00 08 Stub.......w........>
    ExecuteThread: '4' <BEA-180113> <31 32 33 34 2E 35 36 00 0A 11 3E 8A 00 00 00 0F 00 00 00 07 1234.56....?........>
    ExecuteThread: '4' <BEA-180113> <33 34 35 2E 36 37 00 00 0A 11 3E 8B 00 00 00 0F 00 00 00 07 345.67.....?........>
    ExecuteThread: '4' <BEA-180113> <34 35 36 2E 37 38 00 00 0A 11 3E 8C 00 00 00 0F 00 00 00 07 456.78.....?........>
    ExecuteThread: '4' <BEA-180113> <35 36 37 2E 38 39 00 00 0A 11 3E 8D 00 00 00 0F 00 00 00 07 567.89.....?........>
    ExecuteThread: '4' <BEA-180113> <32 33 34 2E 35 36 00 00 0A 11 3E 9B 00 00 00 0F 00 00 00 07 234.56.....?........>
    ExecuteThread: '4' <BEA-180113> <53 79 64 6E 65 79 00 00 0A 11 3E 9D 00 00 00 16 00 00 00 0E Sydney.....?........>
    ExecuteThread: '4' <BEA-180113> <4D 69 6C 6C 65 72 20 53 74 72 65 65 74 00 00 00 0A 11 3E 9E Miller.Street......?>
    ExecuteThread: '4' <BEA-180113> <00 00 00 15 00 00 00 0D 4E 6F 72 74 68 20 53 79 64 6E 65 79 ........North.Sydney>
    ExecuteThread: '4' <BEA-180113> <00 00 00 00 0A 11 3E 9F 00 00 00 0C 00 00 00 04 4E 53 57 00 .......?........NSW.>
    ExecuteThread: '4' <BEA-180113> <0A 11 3E A1 00 00 00 0D 00 00 00 05 32 30 36 30 00 00 00 00 ...?........2060....>
    ExecuteThread: '4' <BEA-180113> <0A 11 3E A8 00 00 00 13 00 00 00 0B 4A 6F 68 6E 20 44 75 6D ...?........John.Dum>
    ExecuteThread: '4' <BEA-180113> <6D 79 00 00 my.. >
    ExecuteThread: '4' <BEA-180073> <+++++ END +++++>
    ExecuteThread: '4' <BEA-180046> <[/TypedFML32/_tmpostrecv/364>
    ExecuteThread: '4' <BEA-180046> <]/TypedFML32/_tmpostrecv/100/>
    ExecuteThread: '4' <BEA-180046> <]/read_dom_65_tfmh/150/0>
    ExecuteThread: '4' <BEA-180046> <[/rdsession(1)/dispatch/>
    ExecuteThread: '4' <BEA-180046> </rdsession(1)/dispatch/TdomTcb=TDOM:GWNW_XATMI_REPLY:2:-1:0:32:32:0:0:0:0:50:null>
    ExecuteThread: '4' <BEA-180046> </rdsession/dispatch/25/reqId = 2>
    ExecuteThread: '4' <BEA-180046> <[/rdsession(1)/addlist/weblogic.wtc.jatmi.tfmh@489f21/2>
    ExecuteThread: '4' <BEA-180046> </rdsession(1)/addlist/SessionAcallDescriptor:2:false>
    ExecuteThread: '4' <BEA-180046> <[/TuxRply/add_reply/weblogic.wtc.gwt.gwdsession@1/SessionAcallDescriptor:2:false>
    ExecuteThread: '4' <BEA-180046> <TuxRply/add_reply: found eligible waiter= weblogic.wtc.jatmi.TuxRply$LockReq@948b59 for oid SessionAcallDescriptor:2:false/weblogic.wtc.gwt.gwdsession@1>
    ExecuteThread: '4' <BEA-180046> <]/rdsession(1)/addlist/10/>
    ExecuteThread: '1'<BEA-180046> <TuxRply/get_specific_reply: Thr Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] got message oid SessionAcallDescriptor:2:false/weblogic.wtc.gwt.gwdsession@1 on lockReq = weblogic.wtc.jatmi.TuxRply$LockReq@948b59>
    ExecuteThread: '4' <BEA-180046> <]/rdsession(1)/dispatch/60/>
    ExecuteThread: '1'<BEA-180046> <]/TuxRply/get_specific_reply/40/weblogic.wtc.jatmi.tfmh@489f21>
    ExecuteThread: '4' <BEA-180046> <]/TuxedoMuxableSocket/dispatch/30/>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/_tpgetrply_internal/20/weblogic.wtc.jatmi.tfmh@489f21>
    ExecuteThread: '1'<BEA-180046> <*]/dsession(1)/tpgetrply/85/opcode=2/diagnostic=0>
    ExecuteThread: '1'<BEA-180046> <[/rdsession(1)/restoreTfmhToCache/>
    ExecuteThread: '1'<BEA-180046> </rdsession(1)/addedtocache=weblogic.wtc.jatmi.tfmh@489f21>
    ExecuteThread: '1'<BEA-180046> <]/rdsession(1)/restoreTfmhToCache/30/>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/tpgetrply/100/weblogic.wtc.jatmi.TypedFML32@9d078d:0:SessionAcallDescriptor:2:false>
    ExecuteThread: '1'<BEA-180046> <]/dsession(1)/tpcall/20/weblogic.wtc.jatmi.TypedFML32@9d078d:0:SessionAcallDescriptor:2:false>
    ExecuteThread: '1'<BEA-180046> <]/TuxedoConnection/tpcall/40/weblogic.wtc.jatmi.TypedFML32@9d078d:0:SessionAcallDescriptor:2:false>
    ExecuteThread: '1'<BEA-180046> <[/TuxedoConnection/tpterm/>
    ExecuteThread: '1'<BEA-180046> <]/TuxedoConnection/tpterm/10>
    and the unsuccessful call:
    ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1250643290962> <BEA-180046> <[/TuxedoConnection/TuxedoConnection/>
    ExecuteThread: '0' <BEA-180046> <no transaction>
    ExecuteThread: '0' <BEA-180046> <]/TuxedoConnection/TuxedoConnection/30>
    ExecuteThread: '0' <BEA-180046> <[/TuxedoConnection/tpcall/GSM_GetAcct/32>
    ExecuteThread: '0' <BEA-180046> <[/TuxedoConnection/getProviderRoute/GSM_GetAcct>
    ExecuteThread: '0' <BEA-180046> <[/WTCRouteManager/selectTargetRotes/GSM_GetAcct>
    ExecuteThread: '0' <BEA-180046> <[/WTCService/getImport/(svc = GSM_GetAcct, xid = null)>
    ExecuteThread: '0' <BEA-180046> <[/TDMImport/getStatus/>
    ExecuteThread: '0' <BEA-180046> <[/TDMRemoteTDomain/getTsession/MTS-Remote, create = false>
    ExecuteThread: '0' <BEA-180046> <[/dsession(1)/getIsTerminated/ldom=WTC_OBF rdom=OBF_WTC>
    ExecuteThread: '0' <BEA-180046> <]/dsession(1)/getIsTerminated/false>
    ExecuteThread: '0' <BEA-180046> <]/TDMRemoteTDomain/getTsession/10/weblogic.wtc.gwt.gwdsession@1>
    ExecuteThread: '0' <BEA-180046> </TDMRemoteTDomain/getTsession/100/weblogic.wtc.gwt.gwdsession@1>
    ExecuteThread: '0' <BEA-180046> <]/TDMImport/getStatus/30/AVAILABLE>
    ExecuteThread: '0' <BEA-180046> <]/WTCService/getImport/40/(0)>
    ExecuteThread: '0' <BEA-180046> <[/TDMRemoteTDomain/getTsession/MTS-Remote, create = true>
    ExecuteThread: '0' <BEA-180046> <[/dsession(1)/getIsTerminated/ldom=WTC_OBF rdom=OBF_WTC>
    ExecuteThread: '0' <BEA-180046> <]/dsession(1)/getIsTerminated/false>
    ExecuteThread: '0' <BEA-180046> <]/TDMRemoteTDomain/getTsession/10/weblogic.wtc.gwt.gwdsession@1>
    ExecuteThread: '0' <BEA-180046> </TDMRemoteTDomain/getTsession/100/weblogic.wtc.gwt.gwdsession@1>
    ExecuteThread: '0' <BEA-180046> <]/WTCRouteManager/selectTargetRotes/30/weblogic.wtc.gwt.gwdsession@1>
    ExecuteThread: '0' <BEA-180046> <]/TuxedoConnection/getProviderRoute/20>
    ExecuteThread: '0' <BEA-180046> <[/dsession(1)/tpcall/GSM_GetAcct/weblogic.wtc.jatmi.TypedFML32@73a146/32/null>
    ExecuteThread: '0' <BEA-180046> <[/dsession(1)/tpacall/GSM_GetAcct/weblogic.wtc.jatmi.TypedFML32@73a146/32/null/0>
    ExecuteThread: '0' <BEA-180046> <[/dsession(1)/_tpacall_internal/GSM_GetAcct/weblogic.wtc.jatmi.tfmh@610734/32/null/0>
    ExecuteThread: '0' <BEA-180046> <myAppKey = null>
    ExecuteThread: '0' <BEA-180046> <[/dsession(1)/alloc_TDOM/1/GSM_GetAcct>
    ExecuteThread: '0' <BEA-180046> <]/dsession(1)/alloc_TDOM/10/TDOM:GWNW_XATMI_CALL:3:-1:0:0:32:0:0:0:0:50:GSM_GetAcct>
    ExecuteThread: '0' <BEA-180046> <[/rdsession(1)/add_rplyObj/SessionAcallDescriptor:3:false/weblogic.wtc.jatmi.TuxRply@f29035/-1>
    ExecuteThread: '0' <BEA-180046> <]/rdsession(1)/add_rplyObj/40/>
    ExecuteThread: '0' <BEA-180046> <[/write_dom_65_tfmh/WTC_OBF/13/2147483647>
    ExecuteThread: '0' <BEA-180046> </write_dom_65_tfmh/header calculated_size=76>
    ExecuteThread: '0' <BEA-180046> </write_dom_65_tfmh/opcode calculated_size=96>
    ExecuteThread: '0' <BEA-180046> <[/FML32/_tmpresend/java.io.DataOutputStream@200fa2>
    ExecuteThread: '0' <BEA-180046> <numPointerFields=0 numView32Fields=0 numFml32Fields=0>
    ExecuteThread: '0' <BEA-180046> <]/TypedFML32/_tmpresend/60/>
    ExecuteThread: '0' <BEA-180046> <Outbound UDATA: buffer type(FML32, null)>
    ExecuteThread: '0' <BEA-180072> <+++++ 65 User Data(184) +++++>
    ExecuteThread: '0' <BEA-180113> <FF FF D8 F0 00 00 00 B8 7F FF FF FF 00 00 00 08 00 00 00 00 .......?............>
    ExecuteThread: '0' <BEA-180113> <00 00 00 10 00 10 DF 9D 00 00 00 01 02 10 DF 93 00 00 00 01 .......?.......?....>
    ExecuteThread: '0' <BEA-180113> <0A 10 DF 2F 00 00 00 13 00 00 00 0B 46 4F 58 5F 53 59 53 54 ............FOX.SYST>
    ExecuteThread: '0' <BEA-180113> <45 4D 00 00 0A 10 DF 39 00 00 00 1A 00 00 00 12 38 66 33 64 EM.....9........8f3d>
    ExecuteThread: '0' <BEA-180113> <2D 39 34 63 39 34 61 30 30 61 35 62 66 00 00 00 0A 10 DF 43 .94c94a00a5bf......C>
    ExecuteThread: '0' <BEA-180113> <00 00 00 13 00 00 00 0B 46 4F 58 5F 53 59 53 54 45 4D 00 00 ........FOX.SYSTEM..>
    ExecuteThread: '0' <BEA-180113> <0A 10 DF 4D 00 00 00 14 00 00 00 0C 47 53 4D 5F 47 65 74 41 ...M........GSM.GetA>
    ExecuteThread: '0' <BEA-180113> <63 63 74 00 0A 10 DF F7 00 00 00 0C 00 00 00 04 46 4F 58 00 cct.............FOX.>
    ExecuteThread: '0' <BEA-180113> <0A 11 3E 7B 00 00 00 11 00 00 00 09 32 32 32 32 32 32 32 32 ............22222222>
    ExecuteThread: '0' <BEA-180113> <00 00 00 00 .... >
    ExecuteThread: '0' <BEA-180073> <+++++ END +++++>
    ExecuteThread: '0' <BEA-180046> </write_dom_65_tfmh/total calculated_size=280>
    ExecuteThread: '0' <BEA-180046> <[/TpeOut/writeTuxedoMessage/>
    ExecuteThread: '0' <BEA-180046> </TpeOut/writeTuxedoMessage/myNeedToWrite=32/myMark=32/myProtocol=13/parsedMetahdr=false>
    ExecuteThread: '0' <BEA-180046> <]/TpeOut/writeTuxedoMessage/70/>
    ExecuteThread: '0' <BEA-180046> <[/TpeOut/write(b)/>
    ExecuteThread: '0' <BEA-180046> <]/TpeOut/write/10/>
    ExecuteThread: '0' <BEA-180046> <[/TpeOut/write(b)/>
    ExecuteThread: '0' <BEA-180046> <]/TpeOut/write/10/>
    ExecuteThread: '0' <BEA-180046> </tfmh/write_dom_65_tfmh/TdomTcb=TDOM:GWNW_XATMI_CALL:3:-1:0:0:32:0:0:0:0:50:GSM_GetAcct>
    ExecuteThread: '0' <BEA-180046> <[/TpeOut/write(b)/>
    ExecuteThread: '0' <BEA-180046> <]/TpeOut/write/10/>
    ExecuteThread: '0' <BEA-180046> <[/TpeOut/write(b)/>
    ExecuteThread: '0' <BEA-180046> <[/TpeOut/writeTuxedoMessage/>
    ExecuteThread: '0' <BEA-180046> </TpeOut/writeTuxedoMessage/myNeedToWrite=280/myMark=280/myProtocol=13/parsedMetahdr=true>
    ExecuteThread: '0' <BEA-180046> <*]/TpeOut/writeTuxedoMessage/40/>
    ExecuteThread: '0' <BEA-180046> <]/TpeOut/write/30/>
    ExecuteThread: '0' <BEA-180046> <]/write_dom_65_tfmh/110/0/>
    ExecuteThread: '0' <BEA-180046> <]/dsession(1)/_tpacall_internal/40/SessionAcallDescriptor:3:false>
    ExecuteThread: '0' <BEA-180046> <]/dsession(1)/tpacall/100/SessionAcallDescriptor:3:false>
    ExecuteThread: '0' <BEA-180046> <[/dsession(1)/tpgetrply/SessionAcallDescriptor:3:false/32>
    ExecuteThread: '0' <BEA-180046> <[/dsession(1)/_tpgetrply_internal/SessionAcallDescriptor:3:false/32>
    ExecuteThread: '0' <BEA-180046> <[/TuxRply/get_specific_reply/SessionAcallDescriptor:3:false/weblogic.wtc.gwt.gwdsession@1/true>
    ExecuteThread: '0' <BEA-180046> <TuxRply/get_specific_reply: Thr Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] waiting for message oid SessionAcallDescriptor:3:false/weblogic.wtc.gwt.gwdsession@1 on lockReq = weblogic.wtc.jatmi.TuxRply$LockReq@e28ba0>
    ExecuteThread: '4' <BEA-180046> <[/TuxedoMuxableSocket/dispatch/>
    ExecuteThread: '4' <BEA-180046> </TuxedoMuxableSocket/dispatch/myOffset=444/myDecryptOffset=0/myProtocol=13>
    ExecuteThread: '4' <BEA-180046> </TuxedoMuxableSocket/dispatch/size=444>
    ExecuteThread: '4' <BEA-180046> <[/rdsession(1)/allocTfmh/>
    ExecuteThread: '4' <BEA-180046> </rdsession(1)/allocTfmh/weblogic.wtc.jatmi.tfmh@489f21>
    ExecuteThread: '4' <BEA-180046> <]/rdsession(1)/allocTfmh/weblogic.wtc.jatmi.tfmh@489f21>
    ExecuteThread: '4' <BEA-180046> <[/read_dom_65_tfmh/13>
    ExecuteThread: '4' <BEA-180046> <]/read_dom_65_tfmh/20/-1/-10000/1938831426>
    ExecuteThread: '4' <BEA-180046> <[/TuxedoMuxableSocket/endOfStream/>
    ExecuteThread: '4' <BEA-180046> <[/dsession(WTC_OBF, OBF_WTC)/setIsTerminated>
    ExecuteThread: '4' <BEA-180046> <[/dsession(WTC_OBF, OBF_WTC)/termimateTDomainSession/false>
    ExecuteThread: '4' <BEA-180046> <[/TDMRemoteTDomain/onTerm/1>
    ExecuteThread: '4' <BEA-180046> <]/TDMRemoteTDomain/onTerm/20>
    ExecuteThread: '4' <BEA-180046> <]/dsession/terminateTDomainSession(30)>
    ExecuteThread: '4' <BEA-180046> <]/dsession/setIsTerminated(10)/done>
    ExecuteThread: '4' <BEA-180046> <[/rdsession(1)/remove_rplyObj/SessionAcallDescriptor:3:false>
    ExecuteThread: '4' <BEA-180046> <]/rdsession(1)/remove_rplyObj/20/true>
    ExecuteThread: '4' <BEA-180046> <[/TuxRply/add_reply/weblogic.wtc.gwt.gwdsession@1/SessionAcallDescriptor:3:false>
    ExecuteThread: '4' <BEA-180046> <TuxRply/add_reply: found eligible waiter= weblogic.wtc.jatmi.TuxRply$LockReq@e28ba0 for oid SessionAcallDescriptor:3:false/weblogic.wtc.gwt.gwdsession@1>
    ExecuteThread: '4' <BEA-180046> </rdsession/connectionHasTerminated/10: TPESYSTEM sent>
    ExecuteThread: '4' <BEA-180046> <]/TuxedoMuxableSocket/endOfStream/10>
    ExecuteThread: '4' <BEA-180046> <[/dsession(WTC_OBF, OBF_WTC)/setIsTerminated>
    ExecuteThread: '4' <BEA-180046> <]/dsession/setIsTerminated(10)/done>
    ExecuteThread: '4' <BEA-180046> <]/TuxedoMuxableSocket/dispatch/90/failure=-1>
    ExecuteThread: '0' <BEA-180046> <TuxRply/get_specific_reply: Thr Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads] got message oid SessionAcallDescriptor:3:false/weblogic.wtc.gwt.gwdsession@1 on lockReq = weblogic.wtc.jatmi.TuxRply$LockReq@e28ba0>
    ExecuteThread: '0' <BEA-180046> <]/TuxRply/get_specific_reply/40/weblogic.wtc.jatmi.tfmh@aa352e>
    ExecuteThread: '0' <BEA-180046> <]/dsession(1)/_tpgetrply_internal/20/weblogic.wtc.jatmi.tfmh@aa352e>
    ExecuteThread: '0' <BEA-180046> <*]/dsession(1)/tpgetrply/85/opcode=3/diagnostic=12>
    ExecuteThread: '0' <BEA-180046> <*]/dsession(1)/tpgetrply/95/>
    ExecuteThread: '0' <BEA-180046> <*]/dsession(1)/tpcall/30/TPESYSTEM(12):0:0:TPED_MINVAL(0):QMNONE(0):0>
    ExecuteThread: '0' <BEA-180046> <*]/TuxedoConnection/tpcall/30/TPESYSTEM(12):0:0:TPED_MINVAL(0):QMNONE(0):0>
    ExecuteThread: '0' <BEA-180046> <[/TuxedoConnection/tpterm/>
    ExecuteThread: '0' <BEA-180046> <]/TuxedoConnection/tpterm/10>

    Hi Todd,
    Thanks for responding.
    The Tuxedo developer here has provided me with the following information:
    The Tuxedo version is 6.5 and the patch level as seen in the last line of $TUXDIR/udataobj/patchlev file is "389. CR093934 TUX 6.5 > HP-UX 11 64-bit /Domain is unable to connect to 32-bit domains"
    The OS, Tuxedo is running on is: "HP-UX B.11.11 U 9000/800 485721183 unlimited-user license"
    In the Tuxedo ULOG file, I can see that the MTS service has received the request from WTC and the response being logged as well, without any error. However immediately after the request is completed, error messages is logged. The extract of this message is shown below:
    130843.focdevapph001!GWTDOMAIN.4780: LIBGWT_CAT:1130: INFO: Disconnected from domain (domainid=<WTC_OBF>)
    130843.focdevapph001!GWTDOMAIN.4780: LIBGWT_CAT:1354: INFO: Retrying domain (domainid=<WTC_OBF>) every 60 seconds
    130843.focdevapph001!GWTDOMAIN.4780: LIBGWT_CAT:2005: INFO: Receive connecting request from remote domain (domainid<WTC_OBF>)
    130843.focdevapph001!GWTDOMAIN.4780: LIBGWT_CAT:1128: INFO: Connection accepted from domain (domainid=<WTC_OBF>)
    Here is the WTC config fragment:
    <wtc-server>
    <name>MTS</name>
    <target>AdminServer</target>
    <wtc-local-tux-dom>
    <name>MTS-Local</name>
    <access-point>MTS-Local</access-point>
    <access-point-id>WTC_OBF</access-point-id>
    <security>NONE</security>
    <connection-policy>ON_STARTUP</connection-policy>
    <nw-addr>//localhost:7050</nw-addr>
    <interoperate>Yes</interoperate>
    </wtc-local-tux-dom>
    <wtc-remote-tux-dom>
    <name>MTS-Remote</name>
    <access-point>MTS-Remote</access-point>
    <access-point-id>OBF_WTC</access-point-id>
    <connection-policy>ON_STARTUP</connection-policy>
    <credential-policy>LOCAL</credential-policy>
    <local-access-point>MTS-Local</local-access-point>
    <retry-interval>10</retry-interval>
    <max-retries>10</max-retries>
    <nw-addr>//focdevapph001:25395</nw-addr>
    <federation-url></federation-url>
    <federation-name></federation-name>
    </wtc-remote-tux-dom>
    <wtc-import>
    <name>WTCImportedService-0</name>
    <resource-name>GSM_GetAcct</resource-name>
    <local-access-point>MTS-Local</local-access-point>
    <remote-access-point-list>MTS-Remote</remote-access-point-list>
    <remote-name>GSM_GetAcct</remote-name>
    </wtc-import>
    <wtc-import>
    <name>WTCImportedService-1</name>
    <resource-name>GSM_GetBillPay</resource-name>
    <local-access-point>MTS-Local</local-access-point>
    <remote-access-point-list>MTS-Remote</remote-access-point-list>
    <remote-name>GSM_GetBillPay</remote-name>
    </wtc-import>
    <wtc-import>
    <name>WTCImportedService-2</name>
    <resource-name>SvcGetBilling</resource-name>
    <local-access-point>MTS-Local</local-access-point>
    <remote-access-point-list>MTS-Remote</remote-access-point-list>
    <remote-name>SvcGetBilling</remote-name>
    </wtc-import>
    </wtc-server>
    Finally, some tcpdump data:
    Successful call:
    11:41:44.715758 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: S 521001588:521001588(0) win 65535 <mss 1460,nop,wscale 3,nop,nop,timestamp 858559006 0,sackOK,eol>
    0x0000: 4500 0040 7a3d 4000 4006 e571 0a10 2945 E..@z=@[email protected]..)E
    0x0010: a12b 0689 cacc 6333 1f0d da74 0000 0000 .+....c3...t....
    0x0020: b002 ffff 6f29 0000 0204 05b4 0103 0303 ....o)..........
    0x0030: 0101 080a 332c 921e 0000 0000 0402 0000 ....3,..........
    11:41:44.716690 IP focdevapph001.optus.com.au.25395 > wsp165668wss.optus.com.au.51916: S 1330679351:1330679351(0) ack 521001589 win 32768 <mss 1460,nop,nop,sackOK,wscale 0,nop,nop,nop,timestamp 42832250 858559006>
    0x0000: 4500 0040 5e44 4000 3e06 036b a12b 0689 E..@^D@.>..k.+..
    0x0010: 0a10 2945 6333 cacc 4f50 8e37 1f0d da75 ..)Ec3..OP.7...u
    0x0020: b012 8000 7d89 0000 0204 05b4 0101 0402 ....}...........
    0x0030: 0303 0001 0101 080a 028d 917a 332c 921e ...........z3,..
    11:41:44.716786 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: . ack 1 win 65535 <nop,nop,timestamp 858559006 42832250>
    0x0000: 4500 0034 1575 4000 4006 4a46 0a10 2945 E..4.u@[email protected]..)E
    0x0010: a12b 0689 cacc 6333 1f0d da75 4f50 8e38 .+....c3...uOP.8
    0x0020: 8010 ffff 3d56 0000 0101 080a 332c 921e ....=V......3,..
    0x0030: 028d 917a ...z
    11:41:44.718457 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: P 1:541(540) ack 1 win 65535 <nop,nop,timestamp 858559006 42832250>
    0x0000: 4500 0250 7254 4000 4006 eb4a 0a10 2945 E..PrT@[email protected]..)E
    0x0010: a12b 0689 cacc 6333 1f0d da75 4f50 8e38 .+....c3...uOP.8
    0x0020: 8018 ffff 8a75 0000 0101 080a 332c 921e .....u......3,..
    0x0030: 028d 917a 7390 3842 0000 000e 0000 0001 ...zs.8B........
    0x0040: ffff ffff 0000 0000 0000 0000 0000 0001 ................
    0x0050: 0000 021c 0000 0057 0000 0054 0000 0043 .......W...T...C
    0x0060: 0000 005f 0000 004f 0000 0042 0000 0046 ..._...O...B...F
    0x0070: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0080: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0090: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0100: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0110: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0120: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0130: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0140: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0150: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0160: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0170: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0180: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0190: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01f0: 0000 ..
    11:41:44.719850 IP focdevapph001.optus.com.au.25395 > wsp165668wss.optus.com.au.51916: P 1:545(544) ack 541 win 32768 <nop,nop,timestamp 42832251 858559006>
    0x0000: 4500 0254 5e45 4000 3e06 0156 a12b 0689 E..T^E@.>..V.+..
    0x0010: 0a10 2945 6333 cacc 4f50 8e38 1f0d dc91 ..)Ec3..OP.8....
    0x0020: 8018 8000 087b 0000 0101 080a 028d 917b .....{.........{
    0x0030: 332c 921e 7390 3842 0000 000f 0000 0001 3,..s.8B........
    0x0040: ffff ffff 0000 0000 0000 0020 0000 0001 ................
    0x0050: 0000 0220 0000 004f 0000 0042 0000 0046 .......O...B...F
    0x0060: 0000 005f 0000 0057 0000 0054 0000 0043 ..._...W...T...C
    0x0070: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0080: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0090: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x00f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0100: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0110: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0120: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0130: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0140: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0150: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0160: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0170: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0180: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0190: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x01f0: 0000 ..
    11:41:44.719932 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: . ack 545 win 65535 <nop,nop,timestamp 858559006 42832251>
    0x0000: 4500 0034 9811 4000 4006 c7a9 0a10 2945 E..4..@.@.....)E
    0x0010: a12b 0689 cacc 6333 1f0d dc91 4f50 9058 .+....c3....OP.X
    0x0020: 8010 ffff 3919 0000 0101 080a 332c 921e ....9.......3,..
    0x0030: 028d 917b ...{
    11:41:44.729113 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: P 541:805(264) ack 545 win 65535 <nop,nop,timestamp 858559006 42832251>
    0x0000: 4500 013c fb6b 4000 4006 6347 0a10 2945 E..<.k@[email protected]..)E
    0x0010: a12b 0689 cacc 6333 1f0d dc91 4f50 9058 .+....c3....OP.X
    0x0020: 8018 ffff efcc 0000 0101 080a 332c 921e ............3,..
    0x0030: 028d 917b 7390 3842 0000 0001 0000 0002 ...{s.8B........
    0x0040: ffff ffff 0000 0000 0000 0000 0000 0001 ................
    0x0050: 0000 0108 0000 0007 5754 435f 4f42 4600 ........WTC_OBF.
    0x0060: 0000 0020 0000 0000 0000 0000 0000 0000 ................
    0x0070: 0000 0005 464d 4c33 3200 0000 0000 0000 ....FML32.......
    0x0080: 0000 000c 0000 000b 4753 4d5f 4765 7441 ........GSM_GetA
    0x0090: 6363 7400 ffff d8f0 0000 00a8 7fff ffff cct.............
    0x00a0: 0000 0008 0000 0000 0000 0010 0010 df9d ................
    0x00b0: 0000 0001 0210 df93 0000 0001 0a10 df2f .............../
    0x00c0: 0000 0009 0000 0001 0000 0000 0a10 df39 ...............9
    0x00d0: 0000 001a 0000 0012 6236 3764 2d34 6666 ........b67d-4ff
    0x00e0: 3631 6632 3139 3535 3700 0000 0a10 df43 61f219557......C
    0x00f0: 0000 0009 0000 0001 0000 0000 0a10 df4d ...............M
    0x0100: 0000 0014 0000 000c 4753 4d5f 4765 7441 ........GSM_GetA
    0x0110: 6363 7400 0a10 dff7 0000 0009 0000 0001 cct.............
    0x0120: 0000 0000 0a11 3e7b 0000 0012 0000 000a ......>{........
    0x0130: 3132 3331 3133 3331 3400 0000 123113314...
    11:41:44.768190 IP focdevapph001.optus.com.au.25395 > wsp165668wss.optus.com.au.51916: P 545:989(444) ack 805 win 32768 <nop,nop,timestamp 42832256 858559006>
    0x0000: 4500 01f0 5e46 4000 3e06 01b9 a12b 0689 E...^F@.>....+..
    0x0010: 0a10 2945 6333 cacc 4f50 9058 1f0d dd99 ..)Ec3..OP.X....
    0x0020: 8018 8000 3762 0000 0101 080a 028d 9180 ....7b..........
    0x0030: 332c 921e 7390 3842 0000 0002 0000 0002 3,..s.8B........
    0x0040: ffff ffff 0000 0000 0000 0020 0000 0001 ................
    0x0050: 0000 01bc 0000 0007 4f42 465f 5754 4300 ........OBF_WTC.
    0x0060: 0000 0020 0000 0000 0000 0000 0000 0000 ................
    0x0070: 0000 0005 464d 4c33 3200 0000 0000 0000 ....FML32.......
    0x0080: 0000 0000 ffff d8f0 0000 012c 0000 1000 ...........,....
    0x0090: 0000 0010 0000 0000 0000 0010 0a10 df2f .............../
    0x00a0: 0000 0013 0000 000b 464f 585f 5359 5354 ........FOX_SYST
    0x00b0: 454d 0000 0a10 df39 0000 000e 0000 0006 EM.....9........
    0x00c0: 4475 6d6d 7900 0000 0a10 df43 0000 000c Dummy......C....
    0x00d0: 0000 0004 464f 5800 0a10 df4d 0000 0014 ....FOX....M....
    0x00e0: 0000 000c 4753 4d5f 4765 7441 6363 7400 ....GSM_GetAcct.
    0x00f0: 0a10 dff7 0000 000d 0000 0005 5374 7562 ............Stub
    0x0100: 0000 0000 0a11 3e77 0000 0010 0000 0008 ......>w........
    0x0110: 3132 3334 2e35 3600 0a11 3e8a 0000 000f 1234.56...>.....
    0x0120: 0000 0007 3334 352e 3637 0000 0a11 3e8b ....345.67....>.
    0x0130: 0000 000f 0000 0007 3435 362e 3738 0000 ........456.78..
    0x0140: 0a11 3e8c 0000 000f 0000 0007 3536 372e ..>.........567.
    0x0150: 3839 0000 0a11 3e8d 0000 000f 0000 0007 89....>.........
    0x0160: 3233 342e 3536 0000 0a11 3e9b 0000 000f 234.56....>.....
    0x0170: 0000 0007 5379 646e 6579 0000 0a11 3e9d ....Sydney....>.
    0x0180: 0000 0016 0000 000e 4d69 6c6c 6572 2053 ........Miller.S
    0x0190: 7472 6565 7400 0000 0a11 3e9e 0000 0015 treet.....>.....
    0x01a0: 0000 000d 4e6f 7274 6820 5379 646e 6579 ....North.Sydney
    0x01b0: 0000 0000 0a11 3e9f 0000 000c 0000 0004 ......>.........
    0x01c0: 4e53 5700 0a11 3ea1 0000 000d 0000 0005 NSW...>.........
    0x01d0: 3230 3630 0000 0000 0a11 3ea8 0000 0013 2060......>.....
    0x01e0: 0000 000b 4a6f 686e 2044 756d 6d79 0000 ....John.Dummy..
    11:41:44.768327 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: . ack 989 win 65535 <nop,nop,timestamp 858559006 42832256>
    0x0000: 4500 0034 b478 4000 4006 ab42 0a10 2945 E..4.x@[email protected]..)E
    0x0010: a12b 0689 cacc 6333 1f0d dd99 4f50 9214 .+....c3....OP..
    0x0020: 8010 ffff 3650 0000 0101 080a 332c 921e ....6P......3,..
    0x0030: 028d 9180 ....
    Unsuccessful call:
    11:43:19.024968 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: P 805:1069(264) ack 989 win 65535 <nop,nop,timestamp 858559948 42832256>
    0x0000: 4500 013c 081f 4000 4006 5694 0a10 2945 E..<..@[email protected]...)E
    0x0010: a12b 0689 cacc 6333 1f0d dd99 4f50 9214 .+....c3....OP..
    0x0020: 8018 ffff bd55 0000 0101 080a 332c 95cc .....U......3,..
    0x0030: 028d 9180 7390 3842 0000 0001 0000 0003 ....s.8B........
    0x0040: ffff ffff 0000 0000 0000 0000 0000 0001 ................
    0x0050: 0000 0108 0000 0007 5754 435f 4f42 4600 ........WTC_OBF.
    0x0060: 0000 0020 0000 0000 0000 0000 0000 0000 ................
    0x0070: 0000 0005 464d 4c33 3200 0000 0000 0000 ....FML32.......
    0x0080: 0000 000c 0000 000b 4753 4d5f 4765 7441 ........GSM_GetA
    0x0090: 6363 7400 ffff d8f0 0000 00a8 7fff ffff cct.............
    0x00a0: 0000 0008 0000 0000 0000 0010 0010 df9d ................
    0x00b0: 0000 0001 0210 df93 0000 0001 0a10 df2f .............../
    0x00c0: 0000 0009 0000 0001 0000 0000 0a10 df39 ...............9
    0x00d0: 0000 001a 0000 0012 3862 3730 2d38 6337 ........8b70-8c7
    0x00e0: 3234 6539 6432 3364 6400 0000 0a10 df43 24e9d23dd......C
    0x00f0: 0000 0009 0000 0001 0000 0000 0a10 df4d ...............M
    0x0100: 0000 0014 0000 000c 4753 4d5f 4765 7441 ........GSM_GetA
    0x0110: 6363 7400 0a10 dff7 0000 0009 0000 0001 cct.............
    0x0120: 0000 0000 0a11 3e7b 0000 0012 0000 000a ......>{........
    0x0130: 3132 3331 3133 3331 3400 0000 123113314...
    11:43:19.027592 IP focdevapph001.optus.com.au.25395 > wsp165668wss.optus.com.au.51916: P 989:1433(444) ack 1069 win 32768 <nop,nop,timestamp 42841681 858559948>
    0x0000: 4500 01f0 5e47 4000 3e06 01b8 a12b 0689 E...^G@.>....+..
    0x0010: 0a10 2945 6333 cacc 4f50 9214 1f0d dea1 ..)Ec3..OP......
    0x0020: 8018 8000 0c1e 0000 0101 080a 028d b651 ...............Q
    0x0030: 332c 95cc 7390 3842 0000 0002 0000 0003 3,..s.8B........
    0x0040: ffff ffff 0000 0000 0000 0020 0000 0001 ................
    0x0050: 0000 01bc 0000 0007 4f42 465f 5754 4300 ........OBF_WTC.
    0x0060: 0000 0020 0000 0000 0000 0000 0000 0000 ................
    0x0070: 0000 0005 464d 4c33 3200 0000 0000 0000 ....FML32.......
    0x0080: 0000 0000 ffff d8f0 0000 012c 0000 1000 ...........,....
    0x0090: 0000 0010 0000 0000 0000 0010 0a10 df2f .............../
    0x00a0: 0000 0013 0000 000b 464f 585f 5359 5354 ........FOX_SYST
    0x00b0: 454d 0000 0a10 df39 0000 000e 0000 0006 EM.....9........
    0x00c0: 4475 6d6d 7900 0000 0a10 df43 0000 000c Dummy......C....
    0x00d0: 0000 0004 464f 5800 0a10 df4d 0000 0014 ....FOX....M....
    0x00e0: 0000 000c 4753 4d5f 4765 7441 6363 7400 ....GSM_GetAcct.
    0x00f0: 0a10 dff7 0000 000d 0000 0005 5374 7562 ............Stub
    0x0100: 0000 0000 0a11 3e77 0000 0010 0000 0008 ......>w........
    0x0110: 3132 3334 2e35 3600 0a11 3e8a 0000 000f 1234.56...>.....
    0x0120: 0000 0007 3334 352e 3637 0000 0a11 3e8b ....345.67....>.
    0x0130: 0000 000f 0000 0007 3435 362e 3738 0000 ........456.78..
    0x0140: 0a11 3e8c 0000 000f 0000 0007 3536 372e ..>.........567.
    0x0150: 3839 0000 0a11 3e8d 0000 000f 0000 0007 89....>.........
    0x0160: 3233 342e 3536 0000 0a11 3e9b 0000 000f 234.56....>.....
    0x0170: 0000 0007 5379 646e 6579 0000 0a11 3e9d ....Sydney....>.
    0x0180: 0000 0016 0000 000e 4d69 6c6c 6572 2053 ........Miller.S
    0x0190: 7472 6565 7400 0000 0a11 3e9e 0000 0015 treet.....>.....
    0x01a0: 0000 000d 4e6f 7274 6820 5379 646e 6579 ....North.Sydney
    0x01b0: 0000 0000 0a11 3e9f 0000 000c 0000 0004 ......>.........
    0x01c0: 4e53 5700 0a11 3ea1 0000 000d 0000 0005 NSW...>.........
    0x01d0: 3230 3630 0000 0000 0a11 3ea8 0000 0013 2060......>.....
    0x01e0: 0000 000b 4a6f 686e 2044 756d 6d79 0000 ....John.Dummy..
    11:43:19.027720 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: . ack 1433 win 65535 <nop,nop,timestamp 858559948 42841681>
    0x0000: 4500 0034 9c5b 4000 4006 c35f 0a10 2945 E..4.[@.@.._..)E
    0x0010: a12b 0689 cacc 6333 1f0d dea1 4f50 93d0 .+....c3....OP..
    0x0020: 8010 ffff 0b0d 0000 0101 080a 332c 95cc ............3,..
    0x0030: 028d b651 ...Q
    11:43:19.029667 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: F 1069:1069(0) ack 1433 win 65535 <nop,nop,timestamp 858559948 42841681>
    0x0000: 4500 0034 9748 4000 4006 c872 0a10 2945 E..4.H@[email protected]..)E
    0x0010: a12b 0689 cacc 6333 1f0d dea1 4f50 93d0 .+....c3....OP..
    0x0020: 8011 ffff 0b0c 0000 0101 080a 332c 95cc ............3,..
    0x0030: 028d b651 ...Q
    11:43:19.030434 IP focdevapph001.optus.com.au.25395 > wsp165668wss.optus.com.au.51916: . ack 1070 win 32768 <nop,nop,timestamp 42841682 858559948>
    0x0000: 4500 0034 5e48 4000 3e06 0373 a12b 0689 E..4^H@.>..s.+..
    0x0010: 0a10 2945 6333 cacc 4f50 93d0 1f0d dea2 ..)Ec3..OP......
    0x0020: 8010 8000 8b0a 0000 0101 080a 028d b652 ...............R
    0x0030: 332c 95cc 3,..
    11:43:19.030467 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: . ack 1433 win 65535 <nop,nop,timestamp 858559948 42841682>
    0x0000: 4500 0034 8f72 4000 4006 d048 0a10 2945 E..4.r@[email protected]..)E
    0x0010: a12b 0689 cacc 6333 1f0d dea2 4f50 93d0 .+....c3....OP..
    0x0020: 8010 ffff 0b0b 0000 0101 080a 332c 95cc ............3,..
    0x0030: 028d b652 ...R
    11:43:19.030747 IP focdevapph001.optus.com.au.25395 > wsp165668wss.optus.com.au.51916: F 1433:1433(0) ack 1070 win 0 <nop,nop,timestamp 42841682 858559948>
    0x0000: 4500 0034 5e49 4000 3e06 0372 a12b 0689 E..4^I@.>..r.+..
    0x0010: 0a10 2945 6333 cacc 4f50 93d0 1f0d dea2 ..)Ec3..OP......
    0x0020: 8011 0000 0b0a 0000 0101 080a 028d b652 ...............R
    0x0030: 332c 95cc 3,..
    11:43:19.030772 IP wsp165668wss.optus.com.au.51916 > focdevapph001.optus.com.au.25395: . ack 1434 win 65535 <nop,nop,timestamp 858559948 42841682>
    0x0000: 4500 0034 403c 4000 4006 1f7f 0a10 2945 E..4@<@.@.....)E
    0x0010: a12b 0689 cacc 6333 1f0d dea2 4f50 93d1 .+....c3....OP..
    0x0020: 8010 ffff 0b0a 0000 0101 080a 332c 95cc ............3,..
    0x0030: 028d b652 ...R

  • WTC FAQ

    Here are some common WTC questions and answers:
    Q1: What is the transaction story for WTC between WLS and Tuxedo and how
    does it differ from Jolt?
    A1: In version 1.0 of WTC transactions may be started in WLS and will
    "infect" Tuxedo with the same transaction. That implies that there is one
    and only one commit coordinator, and that is in WLS. In version 1.0 of WTC
    transactions originating
    in Tuxedo via WTC is not supported. In version 1.1 of WTC transactions from
    Tuxedo into WLS via WTC can be used, but only in Beta mode, as we will not
    have done the required QA of "inbound" transactions. In order to use
    inbound transactions in WTC 1.1 you will need to turn on the use of beta
    features with an attribute called "UseBetaInboundTransactions" on the WTC
    Startup class
    in WLS.
    This differs from Jolt in that while Jolt can start transactions in Tuxedo,
    these transactions are not coordinated with anything in WLS. Hence it is
    impossible to do a 2 phase commit which involves WLS resources and Tuxedo
    resources with Jolt. Since Jolt does not have any means of invoking WLS
    services transactions in that direction do not make sense.
    Q2. How does the security mapping work?
    A2: WLS and Tuxedo can share the same set of users (though they may be
    administered differently in the two systems) and the users can propagate
    their credentials from one system to the other. For example, if John Wells
    logs into WLS then the services which he invokes in Tuxedo will have all of
    the ACL permissions of John Wells as defined on the Tuxedo side.
    Furthermore, if Jolene User logs into Tuxedo then any resources she attempts
    to access in WLS via WTC will be checked against Jolene User's rights in WLS
    land.
    In order to accomplish this, a few things need to be set up:
    1. You must be using Tuxedo 7.1 or Tuxedo 8.0 for this to work. Tuxedo 6.5
    did not have the security infrastructure necessary to make this happen.
    2. In your BDMCONFIG on the Tuxedo side you will need to set ACL_POLICY and
    CREDENTIAL_POLICY to "GLOBAL" for the WLS remote domain. ACL_POLICY
    controls whether or not a domain accepts credentials coming from a remote
    domain and CREDENTIAL_POLICY controls whether or not we send credentials to
    a remote domain. (In Tuxedo 7.1 there was no CREDENTIAL_POLICY - we always
    sent the credentials to the remote domain).
    3. In your BDMCONFIG on the WLS side you must likewise specify <ACL_POLICY>
    and <CREDENTIAL_POLICY> to be "GLOBAL."
    4. On the WLS side you must also configure a <TpUsrFile> which will point
    to a file of the exact same format as the tpusr file generated by the
    various Tuxedo commands to add and delete users. (Which also happens to be
    of the same format as the unix /etc/passwd file). WTC needs this file
    because in WLS users do not have user identification numbers or group
    identification numbers. Hence we need a way to map WLS users into the
    standard Tuxedo UID/GID appkey.
    Voila! You have now set up your system such that users logged into either
    system can be given access privelidges in the other system. This is known
    as single sign-on. We are currently working on a way to better integrate
    the two user databases between WLS and Tuxedo, and one day we will have
    single administration and single-sign on!
    Q3: How is the performance of WTC?
    A3: Obviously, results will vary based on your machine, CPU, application
    (i.e., transactions/no transactions) etc...
    However, in the performance lab here we have seen WTC perform at levels that
    nearly equal Tuxedo in a similar configuration.
    Q4: What fail-over/fail-back mechanisms are there in WTC?
    A4: WTC has many of the same fail-over fail-back mechanisms which /T
    domains had. Any service can be offered by multiple remote domains, and if
    a domain link is down we will attempt all of the backup domains. In /T
    domains there was a limit of three backup remote domains, but in WTC there
    is no limit to the number of backup domains you can configure for a service.
    Furthermore, we support the connection policies of ON_STARTUP, ON_DEMAND and
    INCOMING_ONLY. If the policy is ON_STARTUP then you can also configure a
    retry interval and max-retries. We will attempt to connect to ON_STARTUP
    remote domains every retry interval for a maximum number of retries before
    giving up. If a domain is configured as ON_STARTUP or INCOMING_ONLY and the
    connection is not currently established then no services will be routed to
    that remote domain.
    Q5: What support features are available in WTC?
    A5: WTC has a tracing feature which can be enabled dynamically. If a
    customer reports a problem, support will likely ask the customer to turn
    tracing on and send a log file. This tracing facility has several levels of
    severity and can also help debug WTC applications. It is turned on by
    setting TraceLevel in the WTC startup class. The following are the defined
    levels:
    10000 - TBRIDGE Input/Output
    15000 - TBRIDGE extra information
    20000 - Gateway Input/Output (this will trace the ATMI verbs)
    25000 - Gateway extra information
    50000 - JATMI Input/Output (this will trace the low-level jatmi calls)
    55000 - JATMI extra information
    60000 - CORBA Input/Output (this will trace CORBA calls)
    65000 - CORBA extra information
    Q6: Will Jolt be deprecated?
    A6: No. There are some features of Jolt that are not covered by WTC. For
    example, the Jolt registry API are not supported by WTC. Furthermore WTC
    must run in conjunction with WLS, while Jolt can be run from Applets or from
    free-standing Java applications.
    Q7: What about JCA? Is WTC a JCA adapter?
    A7: WTC is not a JCA adapter. JCA does not define semantics for inbound
    invokations into the JCA container, but WTC allows for Tuxedo clients to
    invoke WLS EJBs. However, the jATMI object interactions are based on the
    JCA client model. BEA is currently evaluating several JCA strategies for
    connections into Tuxedo.
    Q8. What versions of Tuxedo are supported?
    A8. WTC 1.0 will support Tuxedo 6.5 and Tuxedo 8.0. WTC 1.1 (which adds
    CORBA support) will support Tuxedo 6.5 and Tuxedo 8.0. Soon after the
    release of both of these products we will certify WTC with Tuxedo 7.1.
    However, the version of Tuxedo 7.1 you will need to have will be Tuxedo 7.1
    after RP 89.
    Q9. What WLS Releases will be supported?
    A9. WTC 1.0 will be certified on WLS 6.0 SP2, WTC 1.1 will be bundled with
    WLS 6.1
    Q10. How will WTC be packaged?
    A10. WTC 1.0 will be a separately downloaded binary (one for unix, one for
    NT) that the user will have to install and configure in his/her WLS
    environment. (Configuration will consist of putting the jatmi.jar file into
    the classpath (as well as the normal BDMCONFIG configuration, of course)).
    WTC 1.1 will be bundled right in there with the WLS 6.1.
    John Wells (Aziz)
    [email protected]
    [email protected]

    References:
    http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/28f02631-2291-4f8c-875a-4fa5397536ee/
    Amalaraja Fernando,
    SharePoint Architect
    This post is provided "AS IS" with no warrenties and confers no rights.

  • WTC Questions and Answers

    Here are some common WTC questions and answers:
    Q1: What is the transaction story for WTC between WLS and Tuxedo and how
    does it differ from Jolt?
    A1: In version 1.0 of WTC transactions may be started in WLS and will
    "infect" Tuxedo with the same transaction. That implies that there is one
    and only one commit coordinator, and that is in WLS. In version 1.0 of WTC
    transactions originating
    in Tuxedo via WTC is not supported. In version 1.1 of WTC transactions from
    Tuxedo into WLS via WTC can be used, but only in Beta mode, as we will not
    have done the required QA of "inbound" transactions. In order to use
    inbound transactions in WTC 1.1 you will need to turn on the use of beta
    features with an attribute called "UseBetaFeatures" on the WTC Startup class
    in WLS.
    This differs from Jolt in that while Jolt can start transactions in Tuxedo,
    these transactions are not coordinated with anything in WLS. Hence it is
    impossible to do a 2 phase commit which involves WLS resources and Tuxedo
    resources with Jolt. Since Jolt does not have any means of invoking WLS
    services transactions in that direction do not make sense.
    Q2. How does the security mapping work?
    A2: WLS and Tuxedo can share the same set of users (though they may be
    administered differently in the two systems) and the users can propagate
    their credentials from one system to the other. For example, if John Wells
    logs into WLS then the services which he invokes in Tuxedo will have all of
    the ACL permissions of John Wells as defined on the Tuxedo side.
    Furthermore, if Jolene User logs into Tuxedo then any resources she attempts
    to access in WLS via WTC will be checked against Jolene User's rights in WLS
    land.
    In order to accomplish this, a few things need to be set up:
    1. You must be using Tuxedo 7.1 or Tuxedo 8.0 for this to work. Tuxedo 6.5
    did not have the security infrastructure necessary to make this happen.
    2. In your BDMCONFIG on the Tuxedo side you will need to set ACL_POLICY and
    CREDENTIAL_POLICY to "GLOBAL" for the WLS remote domain. ACL_POLICY
    controls whether or not a domain accepts credentials coming from a remote
    domain and CREDENTIAL_POLICY controls whether or not we send credentials to
    a remote domain. (In Tuxedo 7.1 there was no CREDENTIAL_POLICY - we always
    sent the credentials to the remote domain).
    3. In your BDMCONFIG on the WLS side you must likewise specify <ACL_POLICY>
    and <CREDENTIAL_POLICY> to be "GLOBAL."
    4. On the WLS side you must also configure a <TpUsrFile> which will point
    to a file of the exact same format as the tpusr file generated by the
    various Tuxedo commands to add and delete users. (Which also happens to be
    of the same format as the unix /etc/passwd file). WTC needs this file
    because in WLS users do not have user identification numbers or group
    identification numbers. Hence we need a way to map WLS users into the
    standard Tuxedo UID/GID appkey.
    Voila! You have now set up your system such that users logged into either
    system can be given access privelidges in the other system. This is known
    as single sign-on. We are currently working on a way to better integrate
    the two user databases between WLS and Tuxedo, and one day we will have
    single administration and single-sign on!
    Q3: How is the performance of WTC?
    A3: Obviously, results will vary based on your machine, CPU, application
    (i.e., transactions/no transactions) etc...
    However, in the performance lab here we have seen WTC perform at levels that
    nearly equal Tuxedo in a similar configuration. The performance is equal to
    or better than Jolt, and will scale much better than Jolt because of the
    concentration of network bandwidth.
    Q4: What fail-over/fail-back mechanisms are there in WTC?
    A4: WTC has many of the same fail-over fail-back mechanisms which /T
    domains had. Any service can be offered by multiple remote domains, and if
    a domain link is down we will attempt all of the backup domains. In /T
    domains there was a limit of three backup remote domains, but in WTC there
    is no limit to the number of backup domains you can configure for a service.
    Furthermore, we support the connection policies of ON_STARTUP, ON_DEMAND and
    INCOMING_ONLY. If the policy is ON_STARTUP then you can also configure a
    retry interval and max-retries. We will attempt to connect to ON_STARTUP
    remote domains every retry interval for a maximum number of retries before
    giving up. If a domain is configured as ON_STARTUP or INCOMING_ONLY and the
    connection is not currently established then no services will be routed to
    that remote domain.
    Q5: What support features are available in WTC?
    A5: WTC has a tracing feature which can be enabled dynamically. If a
    customer reports a problem, support will likely ask the customer to turn
    tracing on and send a log file. This tracing facility has several levels of
    severity and can also help debug WTC applications. It is turned on by
    setting TraceLevel in the WTC startup class. The following are the defined
    levels:
    10000 - TBRIDGE Input/Output
    15000 - TBRIDGE extra information
    20000 - Gateway Input/Output (this will trace the ATMI verbs)
    25000 - Gateway extra information
    50000 - JATMI Input/Output (this will trace the low-level jatmi calls)
    55000 - JATMI extra information
    60000 - CORBA Input/Output (this will trace CORBA calls)
    65000 - CORBA extra information
    Q6: Will Jolt be deprecated?
    A6: No. There are some features of Jolt that are not covered by WTC. For
    example, the Jolt registry API are not supported by WTC. Furthermore WTC
    must run in conjunction with WLS, while Jolt can be run from Applets or from
    free-standing Java applications.
    Q7: What about JCA? Is WTC a JCA adapter?
    A7: WTC is not a JCA adapter. JCA does not define semantics for inbound
    invokations into the JCA container, but WTC allows for Tuxedo clients to
    invoke WLS EJBs. However, the jATMI object interactions are based on the
    JCA client model. BEA is currently evaluating several JCA strategies for
    connections into Tuxedo.
    John Wells (Aziz)
    [email protected]
    [email protected]

    Q8. What versions of Tuxedo are supported?
    A8. WTC 1.0 will support Tuxedo 6.5 and Tuxedo 8.0. WTC 1.1 (which adds
    CORBA support) will support Tuxedo 6.5 and Tuxedo 8.0. Soon after the
    release of both of these products we will certify WTC with Tuxedo 7.1.
    However, the version of Tuxedo 7.1 you will need to have will be Tuxedo 7.1
    after a certain patch level, which I don't know the number of yet. I will
    attempt to keep the public informed about which patch level will be required
    in Tuxedo 7.1
    Q9. What WLS Releases will be supported?
    A9. WTC 1.0 will be certified on WLS 6.0 SP2, WTC 1.1 will be bundled with
    WLS SilverSword release (6.1?)
    Q10. How will WTC be packaged?
    A10. WTC 1.0 will be a separately downloaded binary (one for unix, one for
    NT) that the user will have to install and configure in his/her WLS
    environment. (Configuration will consist of putting the jatmi.jar file into
    the classpath (as well as the normal BDMCONFIG configuration, of course)).
    WTC 1.1 will be bundled right in there with the WLS SilverSword release.
    Q11. When will WTC go live (no more beta)?
    A11. This is a question for Jeff Cutler, but my impression is that WTC 1.0
    will be shipped in the same time-frame as the Tuxedo 8.0 release and
    obviously (see A10) WTC 1.1 will be shipped with WLS SilverSword.
    John Wells (Aziz)
    [email protected]

  • Calling one WTC service from another WTC service

    Hi,
    We have a service called COLLECT defined in our WTC server.
    Recently we've added a second service called SUM in the same WTC server.
    We were wondering if it's possible to call SUM from COLLECT, and if it is, what configuration changes should be made in order to do it?
    Currently both services are exported by the WTC server (and imported by our Tuxedo).
    Thanks,
    Shy

    Hi Shy,
    Although I haven't tried it, I'm fairly certain you cannot call a Tuxedo EJB using tpcall() within a WTC based application. What I normally advise customers to do when writing a Tuxedo EJB is to implement two separate interfaces. One is obviously the TuxedoService interface that all Tuxedo EJBs must implement. In particular you must implement the service() method that accepts a TPServiceInformation instance that provides access to the typed buffer passed to the EJB. Normally one then extracts the necessary fields or information from the typed buffer, performs whatever necessary business logic needs to be performed, and then constructs a reply typed buffer.
    What I recommend is that you separate out the business logic into a separate interface and have your class implement both interfaces. The service() method would only deal with the marshalling/unmarshalling of the information contained in the typed buffers, and leave all business processing to methods on the second interface. Then if you need to access another "service", you would use the second interface, thus saving you from all the typed buffer manipulation.
    So in your case, the business logic in the second interface of the COLLECT implementation would simply call the SUM implementations second interface (the EJB's business logic) instead of trying to call a Tuxedo service. While this helps in reuse of the business logic, it doesn't address the issue of trying to transparently move a service implementation from say Tuxedo to WLS. If that's what you are trying to do, you might try exporting the SUM service from WTC to the Tuxedo domain gateway, and then importing the SUM service from that gateway. This would likely cause a network round trip if it works, but it's something to consider.
    Another alternative is to use something like the Apache Tuscany/Java project and build your Java applications using SCA. Tuxedo SALT includes a Tuscany/Java binding extension that allows Tuscany/Java applications to transparently call Tuxedo services. The choice of whether to actually call a Tuxedo service or call a Tuscany/Java based SCA service is determine by the binding selection and not changes in your code. Just a thought...
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • WTC Error

    Hi, I am evaluating the weblogic 6.1 server. I have posted my question to
    support.bea.com and weblogic.developer.interest.wtc but no reply. Thank you.
    Problem description
    I used Server - Sparc 20(32bit kernel) with 512 MB RAM and 1GB swap space to
    install Weblogic server 6.1 sp1.
    What I need to do is to connect Weblogic with our existing Tuxedo 6.5 or
    vice versa. In order to test the connection between the two products, I will
    call TOUPPER at TUXEDO 6.5.
    I followed the document from
    /wls/samples/examples/wtc/atmi/simpapp/package-summary.html to configure
    WTC. When I run "run.sh aaa", below error message displayed:
    setSessionContext called
    ejbCreate called
    toupper called, converting aaa
    About to call tpcall
    tpcall threw TPException TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could
    not get a Tuxedo session
    below are the configuration files for your reference:
    ubbconfig
    #Skeleton UBBCONFIG file for the TUXEDO Simple Application.
    #Replace the <bracketed> items with the appropriate values.
    *RESOURCES
    IPCKEY 41828
    #Example:
    #IPCKEY 123456
    #DOMAINID simpapp
    MASTER REL4_DC
    MAXACCESSERS 50
    MAXSERVERS 25
    MAXSERVICES 50
    MODEL SHM
    LDBAL N
    *MACHINES
    DEFAULT:
    APPDIR="/software/tuxedo6.5/sunos53.sc30/apps/simpapp"
    TUXCONFIG="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/tuxconf
    ig"
    TUXDIR="/software/tuxedo6.5/sunos53.sc30"
    #Example:
    # APPDIR="/home/me/simpapp"
    # TUXCONFIG="/home/me/simpapp/tuxconfig"
    # TUXDIR="/usr/tuxedo"
    "itdrnd01" LMID="REL4_DC"
    #Example:
    #beatux LMID=simple
    *GROUPS
    GROUP1
    LMID="REL4_DC" GRPNO=1 OPENINFO=NONE
    GROUP2
    LMID="REL4_DC" GRPNO=2 OPENINFO=NONE
    *SERVERS
    DEFAULT:
    CLOPT="-A"
    simpserv SRVGRP=GROUP1 SRVID=1
    DMADM SRVGRP=GROUP2 SRVID=1
    GWADM SRVGRP=GROUP2 SRVID=2
    GWTDOMAIN SRVGRP=GROUP2 SRVID=3
    *SERVICES
    TOUPPER
    dmconfig
    *DM_RESOURCES
    VERSION=U22
    *DM_LOCAL_DOMAINS
    txndom01 GWGRP=GROUP2
    TYPE=TDOMAIN
    DOMAINID="REL4_DC"
    BLOCKTIME=20
    MAXDATALEN=56
    MAXRDOM=89
    DMTLOGDEV="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/DMTLOG"
    AUDITLOG="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/AUDITLOG"
    DMTLOGNAME="DMTLOG"
    *DM_REMOTE_DOMAINS
    TDOM2 TYPE=TDOMAIN
    DOMAINID="TDOM2"
    *DM_TDOMAIN
    #txndom01 NWADDR="0x0002a3660a610232"
    txndom01 NWADDR="//10.97.2.50:41830"
    NWDEVICE="/dev/tcp"
    #TDOM2 NWADDR="0x00021b590a610236"
    TDOM2 NWADDR="//10.97.2.54:7007"
    NWDEVICE="/dev/tcp"
    *DM_REMOTE_SERVICES
    TOLOWER RDOM="TDOM2"
    bdmconfig.xml
    <?xml version="1.0"?>
    <!DOCTYPE WTC_CONFIG SYSTEM
    "file:/software/bea/wlserver6.1/config/wlsdomain/wtc
    _config.dtd">
    <!--Java and XML-->
    <WTC_CONFIG>
    <BDMCONFIG>
    <T_DM_LOCAL_TDOMAIN AccessPoint="TDOM2">
    <WlsClusterName>Coolio</WlsClusterName>
    <AccessPointId>TDOM2</AccessPointId>
    <Type>TDOMAIN</Type>
    <Security>NONE</Security>
    <ConnectionPolicy>ON_DEMAND</ConnectionPolicy>
    <BlockTime>30</BlockTime>
    <NWAddr>//10.97.2.54:7007</NWAddr>
    <!-- Example address: //wlsdomain.com:20304 -->
    </T_DM_LOCAL_TDOMAIN>
    <T_DM_REMOTE_TDOMAIN AccessPoint="txndom01">
    <LocalAccessPoint>TDOM2</LocalAccessPoint>
    <AccessPointId>REL4_DC</AccessPointId>
    <Type>TDOMAIN</Type>
    <NWAddr>//10.97.2.50:41830</NWAddr>
    <Interoperate>Yes</Interoperate>
    <!-- Example address: //wlsdomain.com:20305 -->
    </T_DM_REMOTE_TDOMAIN>
    <T_DM_EXPORT ResourceName="TOLOWER"
    LocalAccessPoint="TDOM2">
    <EJBName>tuxedo.services.TOLOWERHome</EJBName>
    </T_DM_EXPORT>
    <T_DM_IMPORT
    ResourceName="TOUPPER"
    LocalAccessPoint="TDOM2"
    RemoteAccessPointList="txndom01">
    <TranTime>600</TranTime>
    </T_DM_IMPORT>
    </BDMCONFIG>
    </WTC_CONFIG>

    Hi.
    First, I'll say that I know very little about WTC. However, from the following
    link I don't know that WTC is supported with WLS 6.1:
    http://e-docs.bea.com/wtc/wtc10/notes/WTC_ReleaseNotes_New.html#1109022
    This link says it's only supported with WLS 6.0 sp2. I suggest you download
    this version and try again. If you are still having problems then you should
    open a case with support.
    Regards,
    Michael
    Neo Gigs wrote:
    Hi, I am evaluating the weblogic 6.1 server. I have posted my question to
    support.bea.com and weblogic.developer.interest.wtc but no reply. Thank you.
    Problem description
    I used Server - Sparc 20(32bit kernel) with 512 MB RAM and 1GB swap space to
    install Weblogic server 6.1 sp1.
    What I need to do is to connect Weblogic with our existing Tuxedo 6.5 or
    vice versa. In order to test the connection between the two products, I will
    call TOUPPER at TUXEDO 6.5.
    I followed the document from
    /wls/samples/examples/wtc/atmi/simpapp/package-summary.html to configure
    WTC. When I run "run.sh aaa", below error message displayed:
    setSessionContext called
    ejbCreate called
    toupper called, converting aaa
    About to call tpcall
    tpcall threw TPException TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could
    not get a Tuxedo session
    below are the configuration files for your reference:
    ubbconfig
    #Skeleton UBBCONFIG file for the TUXEDO Simple Application.
    #Replace the <bracketed> items with the appropriate values.
    *RESOURCES
    IPCKEY 41828
    #Example:
    #IPCKEY 123456
    #DOMAINID simpapp
    MASTER REL4_DC
    MAXACCESSERS 50
    MAXSERVERS 25
    MAXSERVICES 50
    MODEL SHM
    LDBAL N
    *MACHINES
    DEFAULT:
    APPDIR="/software/tuxedo6.5/sunos53.sc30/apps/simpapp"
    TUXCONFIG="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/tuxconf
    ig"
    TUXDIR="/software/tuxedo6.5/sunos53.sc30"
    #Example:
    # APPDIR="/home/me/simpapp"
    # TUXCONFIG="/home/me/simpapp/tuxconfig"
    # TUXDIR="/usr/tuxedo"
    "itdrnd01" LMID="REL4_DC"
    #Example:
    #beatux LMID=simple
    *GROUPS
    GROUP1
    LMID="REL4_DC" GRPNO=1 OPENINFO=NONE
    GROUP2
    LMID="REL4_DC" GRPNO=2 OPENINFO=NONE
    *SERVERS
    DEFAULT:
    CLOPT="-A"
    simpserv SRVGRP=GROUP1 SRVID=1
    DMADM SRVGRP=GROUP2 SRVID=1
    GWADM SRVGRP=GROUP2 SRVID=2
    GWTDOMAIN SRVGRP=GROUP2 SRVID=3
    *SERVICES
    TOUPPER
    dmconfig
    *DM_RESOURCES
    VERSION=U22
    *DM_LOCAL_DOMAINS
    txndom01 GWGRP=GROUP2
    TYPE=TDOMAIN
    DOMAINID="REL4_DC"
    BLOCKTIME=20
    MAXDATALEN=56
    MAXRDOM=89
    DMTLOGDEV="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/DMTLOG"
    AUDITLOG="/software/tuxedo6.5/sunos53.sc30/apps/simpapp/AUDITLOG"
    DMTLOGNAME="DMTLOG"
    *DM_REMOTE_DOMAINS
    TDOM2 TYPE=TDOMAIN
    DOMAINID="TDOM2"
    *DM_TDOMAIN
    #txndom01 NWADDR="0x0002a3660a610232"
    txndom01 NWADDR="//10.97.2.50:41830"
    NWDEVICE="/dev/tcp"
    #TDOM2 NWADDR="0x00021b590a610236"
    TDOM2 NWADDR="//10.97.2.54:7007"
    NWDEVICE="/dev/tcp"
    *DM_REMOTE_SERVICES
    TOLOWER RDOM="TDOM2"
    bdmconfig.xml
    <?xml version="1.0"?>
    <!DOCTYPE WTC_CONFIG SYSTEM
    "file:/software/bea/wlserver6.1/config/wlsdomain/wtc
    _config.dtd">
    <!--Java and XML-->
    <WTC_CONFIG>
    <BDMCONFIG>
    <T_DM_LOCAL_TDOMAIN AccessPoint="TDOM2">
    <WlsClusterName>Coolio</WlsClusterName>
    <AccessPointId>TDOM2</AccessPointId>
    <Type>TDOMAIN</Type>
    <Security>NONE</Security>
    <ConnectionPolicy>ON_DEMAND</ConnectionPolicy>
    <BlockTime>30</BlockTime>
    <NWAddr>//10.97.2.54:7007</NWAddr>
    <!-- Example address: //wlsdomain.com:20304 -->
    </T_DM_LOCAL_TDOMAIN>
    <T_DM_REMOTE_TDOMAIN AccessPoint="txndom01">
    <LocalAccessPoint>TDOM2</LocalAccessPoint>
    <AccessPointId>REL4_DC</AccessPointId>
    <Type>TDOMAIN</Type>
    <NWAddr>//10.97.2.50:41830</NWAddr>
    <Interoperate>Yes</Interoperate>
    <!-- Example address: //wlsdomain.com:20305 -->
    </T_DM_REMOTE_TDOMAIN>
    <T_DM_EXPORT ResourceName="TOLOWER"
    LocalAccessPoint="TDOM2">
    <EJBName>tuxedo.services.TOLOWERHome</EJBName>
    </T_DM_EXPORT>
    <T_DM_IMPORT
    ResourceName="TOUPPER"
    LocalAccessPoint="TDOM2"
    RemoteAccessPointList="txndom01">
    <TranTime>600</TranTime>
    </T_DM_IMPORT>
    </BDMCONFIG>
    </WTC_CONFIG>--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • WTC problem

    Hi,
    I'a new with tuxedo and I have to test the integration between weblogic integration(weblogic8.1) and the bea tuxedo product.
    I've installed the bea tuxedo(9) and run the qsample example.
    This one is ok. What I want to test now is the functionality with wtc to post message from jms to tuxedo queue and receive messages from tuxedo queue to jms.
    I've configured the wtc connector with the Bridge and 2 redirections. I've also changed the ubbconfig file in order to add the dmadm, gwadm and gwtdomain. I've also created the dmconfig file. All seems to be ok.
    But when I try to post a message on the jms queue, I received a message error and the message is enqueued to the jms error queue. The message is :
    <cgServer> <Thread-11> <<WLS Kernel>> <> <BEA-180046> </tBexec/jmsQ2tuxQ/t#1 TPException explanation: TPENOENT(6):0:0:TPED_MINVAL(0):QMNONE(0):0:Could not find service QSPACE>
    After reading and rereading the documentation on the gateway and wtc, I still don't understand what's wrong with the config.
    Has anyone an idea?
    Thanks,
    Rodrigue
    here is the ubbconfig :
    *RESOURCES
    IPCKEY          52617
    DOMAINID     qsample
    MASTER          SITE1
    MAXACCESSERS     100
    MAXSERVERS     50
    MODEL          SHM
    *MACHINES
    BOROMIR
         LMID = SITE1
         TUXDIR ="c:\beatuxedo\tuxedo9.0"
         TUXCONFIG = "C:\beatuxedo\test\qssampdir\tuxconfig"
         TLOGDEVICE ="C:\beatuxedo\test\qssampdir\TLOG"
         TLOGSIZE=10
         APPDIR = "C:\beatuxedo\test\qssampdir"
         ULOGPFX = "C:\beatuxedo\test\qssampdir\ULOG"
    # On Windows NT replace '/' character with '\' in paths.
    # So use instead:
    #     TUXCONFIG = "<full path of APPDIR>\tuxconfig"
    #     TLOGDEVICE ="<full path of APPDIR>\TLOG"
    #     ULOGPFX = "<full path of APPDIR>\ULOG"
    *GROUPS
    DMADMGRP
         LMID = SITE1
         GRPNO=3
    GWGROUP
         LMID = SITE1
         GRPNO=4
    GROUP1
         LMID = SITE1 GRPNO = 1
         TMSNAME=TMS TMSCOUNT=2
    QUE1
         LMID = SITE1 GRPNO = 2
         TMSNAME = TMS_QM TMSCOUNT = 2
         OPENINFO = "TUXEDO/QM:C:\beatuxedo\test\qssampdir\QUE;QSPACE"
    # For Windows NT delete previous line, uncomment next line
    #     OPENINFO = "TUXEDO/QM:<full path of APPDIR>\QUE;QSPACE"
    *SERVERS
    DEFAULT:     CLOPT="-A"
    server          SRVGRP=GROUP1 SRVID=2
    DMADM
         SRVGRP=DMADMGRP
         SRVID=4
         REPLYQ=N
         RESTART=Y
         GRACE=0
    GWADM
         SRVGRP=GWGROUP
         SRVID=5
         REPLYQ=N
    GWTDOMAIN
         SRVGRP=GWGROUP
         SRVID=6
         CLOPT = "-A -- -s"
    TMQUEUE
         SRVGRP = QUE1 SRVID = 2
         GRACE = 0 RESTART = Y CONV = N MAXGEN=10
         CLOPT = "-s QSPACE:TMQUEUE -- "
    TMQFORWARD
         SRVGRP=QUE1     SRVID= 7 GRACE=0 RESTART=Y CONV=N MAXGEN=10
         CLOPT="-- -i 2 -q STRING"
    *SERVICES
    The dmconfig :
    *DM_LOCAL
    LOCAL1 GWGRP=GWGROUP
         TYPE=TDOMAIN
         ACCESSPOINTID="qsample"
    *DM_REMOTE
    REMOT1 TYPE=TDOMAIN
         ACCESSPOINTID="PLDAAccessPoint"
    *DM_EXPORT
    QSPACE LACCESSPOINT=LOCAL1
    CONV=N
    RNAME=QSPACE
    STRING LACCESSPOINT=LOCAL1
    CONV=N
    RNAME=STRING
    *DM_TDOMAIN
    LOCAL1     NWADDR="//192.168.1.105:3051"
    REMOT1     NWADDR="//192.168.1.102:7003"
    part of the config.xml :
    <WTCServer DeploymentOrder="3000" Name="PldaWTC Service" Targets="cgServer">
    <WTCLocalTuxDom AccessPoint="PLDAAccessPoint"
    AccessPointId="PLDAAccessPoint" ConnectionPolicy="ON_DEMAND"
    NWAddr="//192.168.1.102:7003" Name="WTCLocalTuxDom-1128428553157"/>
    <WTCtBridgeGlobal DeliveryModeOverride="PERSIST"
    JmsFactory="weblogic.jws.jms.QueueConnectionFactory"
    JndiFactory="weblogic.jndi.WLInitialContextFactory"
    Name="WTCtBridgeGlobal-1128428647252"
    TuxFactory="tuxedo.services.TuxedoConnection" WlsErrorDestination="javax.jms.TuxedoErrorQueue"/>
    <WTCtBridgeRedirect Direction="JmsQ2TuxQ"
    Name="JmsQ2TuxQRedirection" SourceAccessPoint=""
    SourceName="javax.jms.TuxedoSenderQueue"
    TargetAccessPoint="qsample" TargetName="STRING" TargetQspace="QSPACE"/>
    <WTCRemoteTuxDom AccessPoint="qsample" AccessPointId="qsample"
    AllowAnonymous="true" ConnectionPolicy="ON_DEMAND"
    LocalAccessPoint="PLDAAccessPoint"
    NWAddr="//192.168.1.105:3051" Name="WTCRemoteTuxDom-1128462130197"/>
    <WTCtBridgeRedirect Direction="TuxQ2JmsQ"
    Name="TuxQ2JmsQRedirection" SourceAccessPoint="qsample"
    SourceName="RPLYQ" SourceQspace="QSPACE"
    TargetAccessPoint="" TargetName="javax.jms.TuxedoReceiverQueue"/>
    </WTCServer>

    Yes, I use TMQFORWARD. In the jmsQ2TuxQ(a part of the WTC configuration for bridge), I've put as:
    reply queue : RPLYQ(a queue that I've created on QSPACE), target Qspace : QSPACE(the name of the qspace on the remote domain)
    and as Queue name : STRING(which is also with TMQFORWARD the name of the service).
    Then I don't understand why the wtc says it doesn't find the
    QSPACE service. Why it doesn't search the STRING service?
    In which config file is the error(in the ubbconfig?)?
    Thanks

  • Missing WTC classes???

    I think I must be going mad.
    I'm upgrading an application from WLS8.1 to WLS10 and I can't find classes like weblogic.wtc.jatmi.Ferror and weblogic.wtc.jatmi.TypedFML32 in the weblogic.jar file.
    Any idea where they are hiding?

    There are a huge number missing - here's a comparison of the weblogic.wtc.jatmi package with a WLS9.2 jar file
    ***** \TEMP\wls92.txt
    weblogic/wtc/jatmi/
    weblogic/wtc/jatmi/AaaTcb.class
    weblogic/wtc/jatmi/AppKey.class
    weblogic/wtc/jatmi/ApplicationToMonitorInterface.class
    weblogic/wtc/jatmi/BEAObjectKey.class
    weblogic/wtc/jatmi/BetaFeatures.class
    weblogic/wtc/jatmi/BindInfo.class
    weblogic/wtc/jatmi/CallDescriptor.class
    weblogic/wtc/jatmi/CalloutTcb.class
    weblogic/wtc/jatmi/ClientId.class
    weblogic/wtc/jatmi/ClientInfo.class
    weblogic/wtc/jatmi/CodesetTcb.class
    weblogic/wtc/jatmi/ComposFmlTcb.class
    weblogic/wtc/jatmi/ComposHdrTcb.class
    weblogic/wtc/jatmi/Conversation.class
    weblogic/wtc/jatmi/ConversationReply$1.class
    weblogic/wtc/jatmi/ConversationReply$LockReq.class
    weblogic/wtc/jatmi/ConversationReply.class
    weblogic/wtc/jatmi/Decimal.class
    weblogic/wtc/jatmi/DefaultUserRec.class
    weblogic/wtc/jatmi/DequeueReply.class
    weblogic/wtc/jatmi/DomainOutboundConversation.class
    weblogic/wtc/jatmi/DomainRegistry.class
    weblogic/wtc/jatmi/DynamicFldTbl.class
    weblogic/wtc/jatmi/EngineSecError.class
    weblogic/wtc/jatmi/EnqueueRequest.class
    weblogic/wtc/jatmi/FML.class
    weblogic/wtc/jatmi/FViewFld.class
    weblogic/wtc/jatmi/Ferror.class
    weblogic/wtc/jatmi/FldTbl.class
    weblogic/wtc/jatmi/FmlKey.class
    weblogic/wtc/jatmi/GatewayTpacallAsyncReply.class
    weblogic/wtc/jatmi/HTableParser.class
    ***** \TEMP\WLS10.TXT
    weblogic/wtc/jatmi/
    weblogic/wtc/jatmi/AppKey.class
    weblogic/wtc/jatmi/BEAObjectKey.class
    weblogic/wtc/jatmi/CorbaAtmi.class
    weblogic/wtc/jatmi/DomainOutboundConversation.class
    weblogic/wtc/jatmi/HTableParser.class
    ***** \TEMP\wls92.txt
    weblogic/wtc/jatmi/KeepAliveTask.class
    weblogic/wtc/jatmi/LruCache.class
    weblogic/wtc/jatmi/MBEncoding$MapEntry.class
    weblogic/wtc/jatmi/MBEncoding.class
    weblogic/wtc/jatmi/MBStringTypes.class
    weblogic/wtc/jatmi/MuxableExecute.class
    weblogic/wtc/jatmi/ObjectId.class
    weblogic/wtc/jatmi/Objinfo.class
    weblogic/wtc/jatmi/Objrecv.class
    weblogic/wtc/jatmi/OnTerm.class
    weblogic/wtc/jatmi/QueueTimeField.class
    weblogic/wtc/jatmi/RMIReplyRequest.class
    weblogic/wtc/jatmi/Reply.class
    weblogic/wtc/jatmi/ReplyQueue.class
    weblogic/wtc/jatmi/ReqMsg.class
    weblogic/wtc/jatmi/ReqOid.class
    weblogic/wtc/jatmi/ReqXidMsg.class
    weblogic/wtc/jatmi/ReqXidOid.class
    weblogic/wtc/jatmi/RouteTcb.class
    weblogic/wtc/jatmi/SessionAcallDescriptor.class
    weblogic/wtc/jatmi/StandardTypes.class
    weblogic/wtc/jatmi/TDumpByte.class
    weblogic/wtc/jatmi/TGIOPUtil.class
    weblogic/wtc/jatmi/TPCrypt.class
    weblogic/wtc/jatmi/TPException.class
    weblogic/wtc/jatmi/TPINIT.class
    weblogic/wtc/jatmi/TPReplyException.class
    weblogic/wtc/jatmi/TPRequestAsyncReply.class
    weblogic/wtc/jatmi/TPServiceInformation.class
    ***** \TEMP\WLS10.TXT
    weblogic/wtc/jatmi/KeepAliveTask.class
    weblogic/wtc/jatmi/MuxableExecute.class
    weblogic/wtc/jatmi/ObjinfoImpl.class
    weblogic/wtc/jatmi/PasswordUtils.class
    weblogic/wtc/jatmi/RMIReplyRequest.class
    weblogic/wtc/jatmi/TGIOPUtil.class
    weblogic/wtc/jatmi/TPServiceInformation.class
    ***** \TEMP\wls92.txt
    weblogic/wtc/jatmi/TPServiceRequest.class
    weblogic/wtc/jatmi/TXidERFactory.class
    weblogic/wtc/jatmi/TdomTcb.class
    weblogic/wtc/jatmi/TdomTranTcb.class
    weblogic/wtc/jatmi/TdomValsTcb.class
    weblogic/wtc/jatmi/TpacallAsyncExecute.class
    weblogic/wtc/jatmi/TpacallAsyncReply.class
    weblogic/wtc/jatmi/Tpconvert.class
    weblogic/wtc/jatmi/TpeIn.class
    weblogic/wtc/jatmi/TpeOut.class
    weblogic/wtc/jatmi/TranTcb.class
    weblogic/wtc/jatmi/TuxRply$LockReq.class
    weblogic/wtc/jatmi/TuxRply.class
    weblogic/wtc/jatmi/TuxXidRply$LockReqXid.class
    weblogic/wtc/jatmi/TuxXidRply.class
    weblogic/wtc/jatmi/TuxedoArrayOutputStream.class
    weblogic/wtc/jatmi/TuxedoMuxableSocket.class
    weblogic/wtc/jatmi/TuxedoReply.class
    weblogic/wtc/jatmi/TuxedoService.class
    ***** \TEMP\WLS10.TXT
    weblogic/wtc/jatmi/TPServiceRequest.class
    weblogic/wtc/jatmi/TpacallAsyncExecute.class
    weblogic/wtc/jatmi/TuxedoMuxableSocket.class
    weblogic/wtc/jatmi/TuxedoService.class
    ***** \TEMP\wls92.txt
    weblogic/wtc/jatmi/TuxedoServiceHome.class
    weblogic/wtc/jatmi/Txid.class
    weblogic/wtc/jatmi/TypedBuffer.class
    weblogic/wtc/jatmi/TypedBufferFactory.class
    weblogic/wtc/jatmi/TypedCArray.class
    weblogic/wtc/jatmi/TypedFML.class
    weblogic/wtc/jatmi/TypedFML32$1.class
    weblogic/wtc/jatmi/TypedFML32$FmlComparator.class
    weblogic/wtc/jatmi/TypedFML32$FmlIterator.class
    weblogic/wtc/jatmi/TypedFML32.class
    weblogic/wtc/jatmi/TypedMBString.class
    weblogic/wtc/jatmi/TypedString.class
    weblogic/wtc/jatmi/TypedTGIOP.class
    weblogic/wtc/jatmi/TypedView.class
    weblogic/wtc/jatmi/TypedView32.class
    weblogic/wtc/jatmi/TypedXCType.class
    weblogic/wtc/jatmi/TypedXCommon.class
    weblogic/wtc/jatmi/TypedXML.class
    weblogic/wtc/jatmi/TypedXOctet.class
    weblogic/wtc/jatmi/UnsolTcb.class
    weblogic/wtc/jatmi/UserRec.class
    weblogic/wtc/jatmi/UserTcb.class
    weblogic/wtc/jatmi/Usysfl32.class
    ***** \TEMP\WLS10.TXT
    weblogic/wtc/jatmi/TuxedoServiceHome.class
    weblogic/wtc/jatmi/Usysfl32.class
    ***** \TEMP\wls92.txt
    weblogic/wtc/jatmi/Utilities.class
    weblogic/wtc/jatmi/ViewHelper.class
    weblogic/wtc/jatmi/ViewMember.class
    weblogic/wtc/jatmi/ViewParseException.class
    weblogic/wtc/jatmi/WSRPCRQ.class
    weblogic/wtc/jatmi/WsKey.class
    weblogic/wtc/jatmi/WsTcb.class
    weblogic/wtc/jatmi/atn.class
    weblogic/wtc/jatmi/atncontext.class
    weblogic/wtc/jatmi/atncred.class
    weblogic/wtc/jatmi/atncredtd.class
    weblogic/wtc/jatmi/atncredtdom.class
    weblogic/wtc/jatmi/atnctxtd.class
    weblogic/wtc/jatmi/atnctxtdom.class
    weblogic/wtc/jatmi/atntd.class
    weblogic/wtc/jatmi/atntdom65.class
    weblogic/wtc/jatmi/dreqid.class
    weblogic/wtc/jatmi/dsession.class
    ***** \TEMP\WLS10.TXT
    weblogic/wtc/jatmi/Utilities.class
    weblogic/wtc/jatmi/dsession.class
    ***** \TEMP\wls92.txt
    weblogic/wtc/jatmi/evt_mib.class
    weblogic/wtc/jatmi/gwatmi.class
    weblogic/wtc/jatmi/islflds.class
    weblogic/wtc/jatmi/ldapAppKey.class
    weblogic/wtc/jatmi/metahdr.class
    weblogic/wtc/jatmi/mkfldclass.class
    ***** \TEMP\WLS10.TXT
    weblogic/wtc/jatmi/evt_mib.class
    weblogic/wtc/jatmi/islflds.class
    weblogic/wtc/jatmi/mkfldclass.class
    ***** \TEMP\wls92.txt
    weblogic/wtc/jatmi/mkfldclass32.class
    weblogic/wtc/jatmi/ntrace.class
    weblogic/wtc/jatmi/rdCtimer.class
    ***** \TEMP\WLS10.TXT
    weblogic/wtc/jatmi/mkfldclass32.class
    weblogic/wtc/jatmi/rdCtimer.class
    ***** \TEMP\wls92.txt
    weblogic/wtc/jatmi/rdtimer.class
    weblogic/wtc/jatmi/rsession.class
    weblogic/wtc/jatmi/secflds.class
    weblogic/wtc/jatmi/tcb.class
    weblogic/wtc/jatmi/tch.class
    weblogic/wtc/jatmi/tcm.class
    weblogic/wtc/jatmi/tfmh.class
    weblogic/wtc/jatmi/tmibflds.class
    ***** \TEMP\WLS10.TXT
    weblogic/wtc/jatmi/rdtimer.class
    weblogic/wtc/jatmi/secflds.class
    weblogic/wtc/jatmi/tmibflds.class
    ***** \TEMP\wls92.txt
    weblogic/wtc/jatmi/tplle.class
    weblogic/wtc/jatmi/tpusrAppKey.class
    weblogic/wtc/jatmi/tsession.class
    weblogic/wtc/jatmi/ttrace.class
    weblogic/wtc/jatmi/tuxtrace.class
    weblogic/wtc/jatmi/unsol.class
    weblogic/wtc/jatmi/unsolthr.class
    weblogic/wtc/jatmi/viewj.class
    weblogic/wtc/jatmi/viewj32.class
    weblogic/wtc/jatmi/viewjCompiler.class
    ***** \TEMP\WLS10.TXT
    *****

  • What the best way to call twenty tuxedo domains from one weblogic server use WTC

    I need to call twenty tuxedo domains from one weblogic server use
    WTC. the Service be called in the twenty tuxdo domains are same, do I need to
    write twenty EJB in the weblogic server to call the same service? who have good
    adea to deal with this problem?

    Hi,
    I have a question on the second case. When the client doesn't care of which
    Tuxedo domain it is hitting. What happens if one of the Tux domain is down ? What
    happens to the client request to that domain ?
    Another question is lets say i have a Tuxedo configuration as MP mode( Multi
    machine mode) how does WTC load balance between the Tuxedo domains.
    Thanks,
    Srinivas
    "A. Honghsi Lo" <[email protected]> wrote:
    Hi xcjing,
    One way to handle your needs is to use local service name to remote
    reservice name translation. For instance,
    (in 6.1,6.0 WLS)
    <T_DM_IMPORT ResourceName="TOUPPER1" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM1">
         <RemoteName>TOUPPER</RemoteName>
    </T_DM_IMPORT>
    <T_DM_IMPORT ResourceName="TOUPPER2" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM2">
         <RemoteName>TOUPPER</RemoteName>
    </T_DM_IMPORT>
    <T_DM_IMPORT ResourceName="TOUPPER3" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM3">
         <RemoteName>TOUPPER</RemoteName>
    </T_DM_IMPORT>
    etc
    With this configuration if your client have to call "TOUPPER" service
    in
    TUX-DOM1 then you code your client to call "TOUPPER1" and the request
    will be routed to TUX-DOM1. The same way for request has to go to
    TUX-DOM3, your client calls "TOUPPER3" service and WTC will route it
    to
    TUX-DOM3. In this remote name translation you may have to write 20 EJB
    although they are almost the same. However, if your EJB can analyze
    your client input to decide which Remote Tuxedo Domain to send the
    service request to then you probably only need one EJB.
    In the case that your client does not care which remote Tuxedo Domain
    provides the service then adding
    <T_DM_IMPORT ResourceName="TOLOWER" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM1">
         <RemoteName>TOLOWER</RemoteName>
    </T_DM_IMPORT>
    <T_DM_IMPORT ResourceName="TOLOWER" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM2">
         <RemoteName>TOLOWER</RemoteName>
    </T_DM_IMPORT>
    <T_DM_IMPORT ResourceName="TOLOWER" LocalAccessPoint="WTC"
    RemoteAccessPointList="TUX-DOM3">
         <RemoteName>TOLOWEr</RemoteName>
    </T_DM_IMPORT>
    etc
    Will load balance your client "TOLOWER" service request among your 20
    remote Tuxedo Domain.
    However, there is a bug in WTC that causes the Remote Service Name
    translation functionality not working properly. It is fixed in the
    upcoming release of WLS.
    Honghsi :-)
    xcjing wrote:
    Thank you very much! But I still have question, give an example,
    twenty Tuxedo domain is named domain1,domain2,....domain20. The
    same Tuxedo Service: TOUPPER is deploy on those twenty Tuxedo domains,some time
    I need call the TOUPPER Service on domain1,saome time I need call theTOUPPER
    Service on domain3 or
    other domain depend on the input from client. you mean I need to importThe TOUPPER
    Service from twenty Tuxedo domains in the console,then write one EJBto call the
    TOUPPER Service,but how can the EJB know which Tuxedo domain's TOUPPERto call
    from?
    Thank you!
    "A. Honghsi Lo" <[email protected]> wrote:
    hi xcjing,
    You don't have to write 20 beans or deploy 20 beans because there
    are
    20
    remote Tuxedo TDomain you need get the service from. Of course, WLSand
    WTC does not prohibit you from doing it though. Whether you need20
    beans or not depend more on you architecture.
    To access 20 remote Tuxedo Domain from one single WLS with singleWTC
    you can configure 20 remote Tuxedo Domain in the BDMCONFIG (6.1,6.0)
    or
    from the console (7.0). You import 20 services one from each remote
    Tuxedo domain. You write one bean, and deploy one bean. Your WLS
    clients will be able to access THE ejb, the EJB will access the WTC
    service, and WTC will load balanced the service requests among the20
    remote Tuxedo Domain.
    Regards,
    honghsi :-)
    xcjing wrote:
    I need to call twenty tuxedo domains from one weblogic server use
    WTC. the Service be called in the twenty tuxdo domains are same,
    do
    I need to
    write twenty EJB in the weblogic server to call the same service?
    who
    have good
    adea to deal with this problem?

  • Timing out a WTC call

    Hi
    I am making an outbound WTC call to a webservice from my tuxedo service.
    Is there a way I can set a timeout to this specific call so that if this WTC call is responding after specific time, I can continue with my flow in the tuxedo service.
    I am assuming that BLOCK TIME is used to the tuxedo service as a whole. But this could impact my other flows where I am OK to wait for more time.
    Basically below should be the flow of tuxedo service
    tuxservice01
    status = tpcall("wtcWebService01", (char *)pInpRec,0, (char **)&pOutBuf, &olen, FLAG ); /* Not sure about the flag to be used in this case */
    if(status != 0)
    if(tperrno == TIMEOUT)
    handle timeout
    goto nextstep
    nextstep
    Thanks
    Raj

    Hi Raj,
    Depending upon the version of Tuxedo you are using, you may be able to set BLOCKTIME on a per call, per context, or per service basis. Starting with Tuxedo 9.0, the time to wait on a blocking call can be set either in the *SERVICES section of the UBBCONFIG file, or using the tpsblktime() function to set it on a per call or per context basis.  Please note that timing out a request with BLOCKTIME doesn't abort the request, i.e., the request will still likely be processed, although that depends upon a number of factors.  BLOCKTIME simply limits the amount of time a blocking call will wait to be unblocked.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • Enqueued messages with Tuxedo /Q and WTC

    Hi everyone,
    I have a Tuxedo /Q that through a WTC puts messages in a JMS queue in
    a Weblogic. During a period with heavy load ( +- 200 messages per
    second), the total messages in the destination queue starts to
    increase, deprecating the application response time.
    Some configurations
    • The queues are in non persistent mode
    • The connection policy in WTC and Tuxedo Domain is ON_STARTUP
    • WTC with Retry Interval and Block Time 60, keep alive and
    keep alive wait 0
    • Tuxedo 8, Weblogic 10g in RedHat 5
    Some analysis information
    • There is available threads in the Weblogic to process the
    messages, so it isn’t the problem.
    • There isn’t any enqueued packets in the network between
    tuxedo and Weblogic server
    • There is low use of CPU and memory in all machines
    I think that WTC connector hasn’t sufficient throughput to process
    the messages in the destination queue.
    Any suggestions????
    Thanks!

    Hi,
    If you are saying you are using a tBridge (JMS bridge component of WTC) redirection to take messages from Tuxedo /Q and place them on a JMS queue, then the problem is that only a single thread will process the redirection. In other words, a single thread is started to perform tpdequeue() operations on the Tuxedo /Q queue, and then put the message on a JMS queue. If you need more throughput than a single thread offers, you will need to add another redirection in the WTC configuration.
    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • How do i setup WTC in cluster environment using WLS6.1 sp3?

    Hello:
    the situation is:
    (1)Two solaris machines.
    (2)one WLS domain.
    (3)one admin server and four managed servers in this domain.
    (4)we cluster these 4 managed servers.
    (5)each machine contains 2 managed server.
    Here is the problem,
    when we start managed servers in the same machine, the wtc is ok, but when we start managed servers in diffent machine, the wtc fail.
    here is the error message:
    [Error][Cluster][Conflict start: You tried to bind an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The object you have bound  from 10.64.32.188 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.]
    [Error][Cluster][Conflict start: You tried to bind an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The object you have bound  from 10.64.32.187 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.]
    So, how can i setup wtc in cluster environment using WLS 61. sp3?
    Regards,
    cjyang

    cjyang <[email protected]> writes:
    [Error][Cluster][Conflict start: You tried to bind an object under the name tuxedo.services.TuxedoConnection in the JNDI tree. The object you have bound  from 10.64.32.188 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.] I believe that this is a known problem and that WTC clustering is not
    supported in WLS 6.1.
    andy

Maybe you are looking for

  • How to populate data in the same table based on different links/buttons

    Hi I'm using jdeveloper 11.1.4. I have a use case in which i need to populate data in the same table based on click of different links. Can anyone please suggest how can this be achieved. Thanks

  • User objects didn't display in SQL developer connecting to MS SQL server

    I follow the document steps and successfully connected to MS SQL server. I can connect and see all the objects in MS SQL if I use the SQL account with sysadmin role. Everything works fine for using the MS SQL account with sysadmin role. However, if I

  • Print Text Message Thread

    Is there a way to print out (or capture, etc.) a text message thread with all the time stamps and everything?????

  • Scan to e-mail Error

    I have had this printer for almost a year and the scan to e-mail function has always worked properly.  Yet today as I attempt to scan a document a message appears saying "unable to connect to web services.  Confirm internet access and try again." I u

  • Updating my Intel HD graphics driver...

    Hello, I'm attempting to update my graphics driver to hopefully achieve a slightly better gaming experiance. However I can't just get my drivers from the Intel Driver Update Utility because of it being a "Custom" driver, so I need assistance making s