9 Replies Latest reply: May 15, 2012 1:09 AM by 679490 RSS

    Tuxedo JCA and Conversation mode

    927205
      There are services of tuxedo workings in the conversation mode.
      Is it possible to work with them through JCA?
      There is interface weblogic.wtc.jatmi.Conversation - which does contain necessary methods, but does not see what class of JCA will realize them?
        • 1. Re: Tuxedo JCA and Conversation mode
          wilson.t
          Tuxedo has a resource adapter: http://docs.oracle.com/cd/E26665_01/jca/docs11gr1/users/jca_usersguide.html
          • 2. Re: Tuxedo JCA and Conversation mode
            927205
            Excuse me, but on the indicated reference does not see the conversation mode. Or does it mean that through JCA with services workings conversation mode, working is impossible?
            • 3. Re: Tuxedo JCA and Conversation mode
              927205
              Understood. But reference did not quite help herein!

              Example:

              Context ctx;
              TuxedoConnectionFactory cf
              TuxedoJCAConnection c;
              TDomainContext domain;
              Conversation myConv;
              TypedString send_buf = new TypedString( "" );

              try
              {
              ctx = new InitialContext();
              cf = (TuxedoConnectionFactory)ctx.lookup("eis/TuxedoConnectionFactory");
              c = (TuxedoJCAConnection)cf.getConnection();
              domain = c.getTDomainContext();
              myConv = domain.tpconnect( "NAMESERVICE", send_buf, ApplicationToMonitorInterface.TPSENDONLY );
              myConv.tpsend( send_buf, ApplicationToMonitorInterface.TPSENDONLY );
              • 4. Re: Tuxedo JCA and Conversation mode
                927205
                Close
                • 5. Re: Tuxedo JCA and Conversation mode
                  927205
                  Early closed a theme.
                  Error in tpsend!

                  TuxedoJCAConnection c;
                  TDomainContext domain;
                  Conversation Conv;
                  ...
                  domain = c.getTDomainContext();
                  Conv = domain.tpconnect( "SERVICENAME", null, ApplicationToMonitorInterface.TPSENDONLY );
                  Conv.tpsend( send_CArray_One, ApplicationToMonitorInterface.TPSENDONLY );
                  ...

                  [09.04.12 11:12:41:218 EEST] 00000017 servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet /conTux3.jsp in application TuxedoService__war. Exception created : com.ibm.websphere.servlet.error.ServletErrorReport: java.lang.IncompatibleClassChangeError: weblogic/wtc/gwt/TuxedoConnection.isTerminated()Z
                       at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:695)
                       at com.ibm._jsp._conTux3._jspService(_conTux3.java:96)
                       at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:99)
                       at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
                       at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
                       at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:939)
                       at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
                       at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)
                       at com.ibm.wsspi.webcontainer.servlet.GenericServletWrapper.handleRequest(GenericServletWrapper.java:121)
                       at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionServletWrapper.handleRequest(AbstractJSPExtensionServletWrapper.java:259)
                       at com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.handleRequest(AbstractJSPExtensionProcessor.java:353)
                       at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935)
                       at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
                       at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
                       at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
                       at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
                       at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
                       at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
                       at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
                       at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
                       at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
                       at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
                       at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
                       at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
                       at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
                       at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
                       at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
                       at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
                       at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
                       at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
                  Caused by: java.lang.IncompatibleClassChangeError: weblogic/wtc/gwt/TuxedoConnection.isTerminated()Z
                       at weblogic.wtc.gwt.TuxedoConversation.tpsend(TuxedoConversation.java:94)
                       at example.HelloWorld.connectTuxedo3(HelloWorld.java:460)
                       at com.ibm._jsp._conTux3._jspService(_conTux3.java:88)
                       ... 28 more

                  Edited by: ZAVRus on 9/4/2012 11:39
                  • 6. Re: Tuxedo JCA and Conversation mode
                    Deepak Goel-Oracle
                    Conversational APIs are not supported with current version of Tuxedo JCA Adapter. We are actively developing this support for next release of Tuxedo JCA Adapter. If you are interested in a beta version, please contact Oracle support or your Oracle account exec and request to participate in the same.
                    Deepak Goel
                    • 7. Re: Tuxedo JCA and Conversation mode
                      927205
                      Thank you. We are interested in it so much!
                      • 8. Re: Tuxedo JCA and Conversation mode
                        User9546281-Oracle
                        Hi,
                        Would you please let me know what function of conversation you want to have a try? such as whether XA involved, how will you use JCA conversation, etc.

                        Regards,
                        Dong
                        • 9. Re: Tuxedo JCA and Conversation mode
                          679490
                          Hi, Gilles

                          Would you please let me know which application server will be used by customer, i.e, weblogic 11g /12c, WAS6/7/8.0, GlassFish3.0, etc?

                          We are testing against weblogic12c. Is it enough?

                          Regards,
                          Xu he