perfsonar-dev - Re: [pS-dev] Help decoding an error.
Subject: perfsonar development work
List archive
- From: Jason Zurawski <>
- To: Joe Metzger <>
- Cc:
- Subject: Re: [pS-dev] Help decoding an error.
- Date: Mon, 28 Aug 2006 23:18:54 -0400
Joe;
Every time I install Axis (any version), it complains about
activation.jar, mail.jar and xmlsec.jar not being present.
However, these are in the perfSONAR distribution, so I run
install once (and it fails to deploy the service).
Perhaps the deploy scripts are being created wrong (since you noted problems with some other aspects from your last e-mail). Does the *AxisDeploy.sh have the appropriate fabricated classpath (and do the files in the classpath exist)?
At this point the Happy Axis page says it is happy.
Then I try to install.pl again hoping it will work.
The second pass generates the same error
when trying to undeploy the service:
Processing file /usr/local/esnet/perfsonar/perfSONAR-1.0/wsdd/ma-service-undeploy.wsdd
Exception: AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Invalid argument
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Invalid argument
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:364)
at java.net.Socket.connect(Socket.java:507)
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:585)
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:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:1784)
at org.apache.axis.client.AdminClient.process(AdminClient.java:439)
at org.apache.axis.client.AdminClient.process(AdminClient.java:404)
at org.apache.axis.client.AdminClient.process(AdminClient.java:410)
at org.apache.axis.client.AdminClient.process(AdminClient.java:320)
at org.apache.axis.client.AdminClient.main(AdminClient.java:463)
{http://xml.apache.org/axis/}hostname:mea1.es.net
It gives the same error when trying to Deploy the service.
Suggestions about what to look at?
I remember seeing the connect error when tomcat/axis were not running, were running on a different port then specified, or firewall issues blocked things. It is still probably related to a poorly created deploy/undeploy script. I will attach mine so you can compare.
-jason
Attachment:
scripts.tar.gz
Description: GNU Zip compressed data
- Help decoding an error., Joe Metzger, 08/28/2006
- Re: [pS-dev] Help decoding an error., Jason Zurawski, 08/28/2006
- Re: [pS-dev] Help decoding an error., Joe Metzger, 08/29/2006
- Re: [pS-dev] Help decoding an error., Jason Zurawski, 08/30/2006
- Re: [pS-dev] Help decoding an error., Joe Metzger, 08/29/2006
- Re: [pS-dev] Help decoding an error., Jason Zurawski, 08/28/2006
Archive powered by MHonArc 2.6.16.