-
1. Re: xts standalone
jhalliday Aug 20, 2007 5:49 AM (in response to gbiemolt)Calls in XTS are build from pairs of one-way web service invocations. Hence every client is also a server i.e. you need a web service listener at both ends. You can run using a separate coordinator (see the readme in the coordinator dir of XTS for config). You can't however run using a client that is not also listening for response messages.
-
2. Re: xts standalone
gbiemolt Aug 20, 2007 2:24 PM (in response to gbiemolt)i see, this raises two things,
what is a web service listener and how is it implemented, configured
further more i'm trying to get the xts-demo working as a standalone, according to the 'install' instructions. But somehow the usertransaction on the client side is not initialized. Also the web-interface shows this exception.
Transaction failed! Cause: com.arjuna.wst.SystemException: Receiver[java.net.ConnectException: Connection refused: connect]
Probably i need to specify somewhere, where the client can find the standalone configuration. I did this according to pre-mentioned install instructions, adding two properties to wstx.xml. But what other thing need to be changed?
kind regards -
3. Re: xts standalone
jhalliday Aug 21, 2007 4:38 AM (in response to gbiemolt)XTS currently uses its own web services stack, which has a servlet based listener. In short, you need a servlet container on both ends. Have a poke around in the .war files if you want to know the details on how it works.
There is a race condition in the setup code for the remote coordinator configuration that can cause problems - you may need to pull the latest source from svn to get the fix. See http://jira.jboss.com/jira/browse/JBTM-276 -
4. Re: xts standalone
dracopql Oct 21, 2007 4:10 PM (in response to gbiemolt)I'm on the same thing.-
I want to install a standalone coordinator and I follow the "install" instructions and the "administration guide", I read this post and also install the JBossTS 4.2.3 SP 6 (according to "http://jira.jboss.com/jira/browse/JBTM-27").
My steps:
1) I could create a separate installation on the same machine of another JBossAS ... it was very difficult, because the instructions on "http://www.yorku.ca/dkha/jboss/docs/MultipleInstances.htm" are out of date.-
2) I have edited the "...\JBossTS_4.2.3_SP6\xts\coordinator\build.xml" and I was able to run ant and deploy (automatically) the "xts-coordinator.ear" in the AS created in the previous step.-
3) I have setted the jboss.properties files in the "...\xts\demo\" to use my original AS and I have edited wstx.xml fila in "...\xts\conf" to point to the new AS created.-
4) Once I've deployed and started all the necesary artifacts, when I test the demo I've got this error:
Transaction failed! Cause: java.rmi.RemoteException: Call invocation failed with code [MustUnderstand] because of: Unprocessed 'mustUnderstand' header element: {http://schemas.xmlsoap.org/ws/2004/10/wscoor}CoordinationContext; nested exception is: javax.xml.rpc.soap.SOAPFaultException: Unprocessed 'mustUnderstand' header element: {http://schemas.xmlsoap.org/ws/2004/10/wscoor}CoordinationContext
Thanks in advence
LR -
5. Re: xts standalone
jhalliday Oct 21, 2007 5:57 PM (in response to gbiemolt)Which version of JBossAS are you using?
-
6. Re: xts standalone
dracopql Oct 21, 2007 6:22 PM (in response to gbiemolt)In both cases (AS & standalone coordinator) is JBossAS 4.2.1
-
7. Re: xts standalone
jhalliday Oct 22, 2007 5:35 AM (in response to gbiemolt)With AS 4.2.1 the simplest method is to use the service binding manager. You'll also need to grab TS 4.2.3.SP7, as SP6 is broken.
For the web services and client on the standard ports and a separate coordinator on different port:
Copy server/default to server/coordinator and edit server/coordinator/conf/jboss-service.xml, uncommenting the ServiceBindingManager section in accordance with http://labs.jboss.com/file-access/default/members/jbossas/freezone/docs/Server_Configuration_Guide/beta422/html/Additional_Services-Services_Binding_Management.html
In the xts install, edit coordinator/build.xml to point at the new AS coordinator server and use port 8180. run 'ant deploy-jboss'
Edit demo/jboss.properties.xml to point at the default jboss AS (port 8080) and edit xts conf/wstx.xml to include the URLs as described in coordinator/README.txt. run './build.sh jboss clean deploy' -
8. Re: xts standalone
dracopql Oct 24, 2007 8:48 PM (in response to gbiemolt)Thank you for your reply, it works perfect! Even in my "completely separate" installation that already had (http://www.yorku.ca/dkha/jboss/docs/MultipleInstances.htm and personal effort) ... next step is the integration with WCF, but that will be another story.-
Thank you again for the support
LR
P.D.: Thank you for stop offering the SP6 also.-