Re: Pipelines failing
Mohana Ramaratnam
As the pipeline runs, the workflow row along with status is updated.
This is done by connecting to XNAT. Has the URL to the XNAT host
changed?
Mohana
On Fri, Dec 10, 2010 at 7:43 AM, Alex <ski...@gmail.com> wrote:
> Starting today the pipelines stopped running on our production XNAT
> (1.4rc3). When I try to run a pipeline from command line, I get
> exceptions below. What is it cannot connect to? As far as I know
> nothing changed on the server.
>
> Thank you, Alex.
>
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}
> Server.userException
> faultSubcode:
> faultString: java.net.ConnectException: Connection refused
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}
> stackTrace:java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:
> 333)
> at
> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> at java.net.Socket.connect(Socket.java:519)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
> 25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:
> 153)
> at
> org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:
> 120)
> at
> org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:
> 191)
> at
> org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:
> 404)
> at
> org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:
> 32)
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:
> 118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:
> 165)
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at org.apache.axis.client.Call.invoke(Call.java:2767)
> at org.apache.axis.client.Call.invoke(Call.java:2443)
> at org.apache.axis.client.Call.invoke(Call.java:2366)
> at org.apache.axis.client.Call.invoke(Call.java:1812)
> at
> org.nrg.xnattools.xml.AbsService.createServiceSession(AbsService.java:
> 100)
> at org.nrg.xnattools.xml.XMLStore.store(XMLStore.java:33)
> at org.nrg.xnattools.xml.XMLStore.store(XMLStore.java:59)
> at
> org.nrg.pipeline.client.XNATPipelineLauncher.update(XNATPipelineLauncher.java:
> 179)
> at java.util.Observable.notifyObservers(Observable.java:142)
> at
> org.nrg.pipeline.manager.EventManager.notify(EventManager.java:35)
> at
> org.nrg.pipeline.utils.AdminUtils.fireNotification(AdminUtils.java:44)
> at
> org.nrg.pipeline.manager.ExecutionManager.execute(ExecutionManager.java:
> 80)
> at org.nrg.pipeline.task.StepManager.execute(StepManager.java:
> 166)
> at
> org.nrg.pipeline.manager.PipelineManager.launchPipeline(PipelineManager.java:
> 214)
> at
> org.nrg.pipeline.manager.PipelineManager.launchPipeline(PipelineManager.java:
> 194)
> at
> org.nrg.pipeline.client.XNATPipelineLauncher.launch(XNATPipelineLauncher.java:
> 46)
> at
> org.nrg.pipeline.client.XNATPipelineLauncher.main(XNATPipelineLauncher.java:
> 253)
>
> {http://xml.apache.org/axis/}hostname:karl
>
> java.net.ConnectException: Connection refused
> at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
> at
> org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:
> 32)
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:
> 118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:
> 165)
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at org.apache.axis.client.Call.invoke(Call.java:2767)
> at org.apache.axis.client.Call.invoke(Call.java:2443)
> at org.apache.axis.client.Call.invoke(Call.java:2366)
> at org.apache.axis.client.Call.invoke(Call.java:1812)
> at
> org.nrg.xnattools.xml.AbsService.createServiceSession(AbsService.java:
> 100)
> at org.nrg.xnattools.xml.XMLSearch.searchAll(XMLSearch.java:
> 97)
> at
> org.nrg.pipeline.client.XNATPipelineLauncher.isPipelineQueuedOrAwaitingOrOnHold(XNATPipelineLauncher.java:
> 119)
> at
> org.nrg.pipeline.client.XNATPipelineLauncher.launch(XNATPipelineLauncher.java:
> 44)
> at
> org.nrg.pipeline.client.XNATPipelineLauncher.main(XNATPipelineLauncher.java:
> 253)
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:
> 333)
> at
> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> at java.net.Socket.connect(Socket.java:519)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
> 25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:
> 153)
> at
> org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:
> 120)
> at
> org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:
> 191)
> at
> org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:
> 404)
> at
> org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
> ... 14 more
>
> --
> You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
> To post to this group, send email to xnat_di...@googlegroups.com.
> To unsubscribe from this group, send email to xnat_discussi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/xnat_discussion?hl=en.
>
>
Alex
I resolved this issue as I realized that the url was changed a few
days ago, but there's another issue connected to this. The reason url
was changed is that I noticed that in emails that users send out
through XNAT (such as invitations to join projects) the logo was not
displayed. Logo url was referring to port 8080, but our XNAT runs on
80 and gets redirected to 8080 internally. So, once I changed the port
number - pipelines stopped working. Bottom line is: the url has to
refer to 8080 in order for pipelines to communicate with XNAT
internally, but that breaks any auto-generated external links.
Alex.
Mohana Ramaratnam
What is the URL set at XNAT WEBAPP -> Administer -> Default Settings
and also are you using -aliasHost parameter in
PIPELINE_HOME/bin/XnatPipelineLauncher
Mohana