You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by Steven McDowall <sj...@aptest.com> on 2000/07/26 17:47:09 UTC
RE: Deploy Nightmare
If you haven't gotten your first problem fixed, make sure you grab the
latest
from CVS and build it.. There were a lot of fixes (including that one) that
are
still not in the "distrib" version..
-Steve
P.S. When ARE we going to make a new distrib?? I think it is about time..
-----Original Message-----
From: mark@peabrain.ffsoft.com [mailto:mark@peabrain.ffsoft.com]On
Behalf Of Mark Boylan
Sent: Tuesday, July 25, 2000 6:39 PM
To: soap-user@xml.apache.org
Subject: Deploy Nightmare
Ugh. I'm having a problem deploying services.
Actually, I think there are two separate problems.
The first is when I try to deploy from the command line:
------------------------------------------
[mark@babydoll calculator]$ java
org.apache.soap.server.ServiceManagerClient
http://localhost:8080/xml-soap/rpcrouter.jsp deploy
./DeploymentDescriptor.xml
Exception in thread "main" [SOAPException: faultCode=SOAP-ENV:Client;
msg=error parsing HTTP status line: Connection reset by peer: Connection
reset by peer; targetException=java.lang.IllegalArgumentException: error
parsing HTTP status line: Connection reset by peer: Connection reset by
peer]
at
org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.ja
va,
Compiled Code)
at org.apache.soap.rpc.Call.invoke(Call.java, Compiled Code)
at
org.apache.soap.server.ServiceManagerClient.invokeMethod(ServiceManagerClien
t.java,
Compiled Code)
at
org.apache.soap.server.ServiceManagerClient.deploy(ServiceManagerClient.java
,
Compiled Code)
at
org.apache.soap.server.ServiceManagerClient.main(ServiceManagerClient.java,
Compiled Code)
[mark@babydoll calculator]$
------------------------------------------
The second problem is when I try to deploy from the browser,
I cant even load the deploy.jsp page:
------------------------------------------
Error: 500
Location: /xml-soap/deploy.jsp
Internal Servlet Error:
org.apache.jasper.JasperException: Unable to compile class for
JSP/opt/tomcat/work/localhost_8080%2Fxml-soap/_0002fdeploy_0002ejspdeploy_js
p_0.java:148:
No variable NS_URI_BML_ENC defined in class org.apache.soap.Constants.
org.apache.soap.Constants.NS_URI_BML_ENC};
^
1 error
at org.apache.jasper.compiler.Compiler.compile(Compiler.java,
Compiled Code)
at org.apache.jasper.runtime.JspServlet.loadJSP(JspServlet.java,
Compiled Code)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspSe
rvlet.java,
Compiled Code)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServlet.ja
va,
Compiled Code)
at
org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java,
Compiled Code)
at org.apache.jasper.runtime.JspServlet.service(JspServlet.java,
Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java,
Compiled Code)
at
org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java,
Compiled Code)
at
org.apache.tomcat.core.ContextManager.service(ContextManager.java,
Compiled Code)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java,
Compiled Code)
at
org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java,
Compiled Code)
at java.lang.Thread.run(Thread.java, Compiled Code)
---------------------------------------
I'm running RH6.2, tomcat 3.1, xerces 1.0.4, Blackdown JDK 1.2.2.
I tried switching to xerces 1.0.3, and got the same results.
If anyone has any insight, please post. This is driving me nuts.
Thanks,
Mark
Re: Deploy Nightmare
Posted by Kailash Aynor <ak...@hotmail.com>.
Also i think when u create a new distrib , please accompanny with it some install.txt file, which not only provides the expected supporting environment, but also the "exact" version of xerces,ant... required. This will probably help a lot, especially since there are now lots of versions floating around.
Kailash.
----- Original Message -----
From: Steven McDowall
To: soap-user@xml.apache.org
Cc: soap-dev@xml.apache.org
Sent: Wednesday, July 26, 2000 11:47 AM
Subject: RE: Deploy Nightmare
If you haven't gotten your first problem fixed, make sure you grab the
latest
from CVS and build it.. There were a lot of fixes (including that one) that
are
still not in the "distrib" version..
-Steve
P.S. When ARE we going to make a new distrib?? I think it is about time..
-----Original Message-----
From: mark@peabrain.ffsoft.com [mailto:mark@peabrain.ffsoft.com]On
Behalf Of Mark Boylan
Sent: Tuesday, July 25, 2000 6:39 PM
To: soap-user@xml.apache.org
Subject: Deploy Nightmare
Ugh. I'm having a problem deploying services.
Actually, I think there are two separate problems.
The first is when I try to deploy from the command line:
------------------------------------------
[mark@babydoll calculator]$ java
org.apache.soap.server.ServiceManagerClient
http://localhost:8080/xml-soap/rpcrouter.jsp deploy
./DeploymentDescriptor.xml
Exception in thread "main" [SOAPException: faultCode=SOAP-ENV:Client;
msg=error parsing HTTP status line: Connection reset by peer: Connection
reset by peer; targetException=java.lang.IllegalArgumentException: error
parsing HTTP status line: Connection reset by peer: Connection reset by
peer]
at
org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnectionja
va,
Compiled Code)
at org.apache.soap.rpc.Call.invoke(Call.java, Compiled Code)
at
org.apache.soap.server.ServiceManagerClient.invokeMethod(ServiceManagerClien
t.java,
Compiled Code)
at
org.apache.soap.server.ServiceManagerClient.deploy(ServiceManagerClient.java
,
Compiled Code)
at
org.apache.soap.server.ServiceManagerClient.main(ServiceManagerClient.java,
Compiled Code)
[mark@babydoll calculator]$
------------------------------------------
The second problem is when I try to deploy from the browser,
I cant even load the deploy.jsp page:
------------------------------------------
Error: 500
Location: /xml-soap/deploy.jsp
Internal Servlet Error:
org.apache.jasper.JasperException: Unable to compile class for
JSP/opt/tomcat/work/localhost_8080%2Fxml-soap/_0002fdeploy_0002ejspdeploy_js
p_0.java:148:
No variable NS_URI_BML_ENC defined in class org.apache.soap.Constants.
org.apache.soap.Constants.NS_URI_BML_ENC};
^
1 error
at org.apache.jasper.compiler.Compiler.compile(Compiler.java,
Compiled Code)
at org.apache.jasper.runtime.JspServlet.loadJSP(JspServlet.java,
Compiled Code)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspSe
rvlet.java,
Compiled Code)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServletja
va,
Compiled Code)
at
org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java,
Compiled Code)
at org.apache.jasper.runtime.JspServlet.service(JspServlet.java,
Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java,
Compiled Code)
at
org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java,
Compiled Code)
at
org.apache.tomcat.core.ContextManager.service(ContextManager.java,
Compiled Code)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java,
Compiled Code)
at
org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java,
Compiled Code)
at java.lang.Thread.run(Thread.java, Compiled Code)
---------------------------------------
I'm running RH6.2, tomcat 3.1, xerces 1.0.4, Blackdown JDK 1.2.2.
I tried switching to xerces 1.0.3, and got the same results.
If anyone has any insight, please post. This is driving me nuts.
Thanks,
Mark
Re: Deploy Nightmare
Posted by Kailash Aynor <ak...@hotmail.com>.
Also i think when u create a new distrib , please accompanny with it some install.txt file, which not only provides the expected supporting environment, but also the "exact" version of xerces,ant... required. This will probably help a lot, especially since there are now lots of versions floating around.
Kailash.
----- Original Message -----
From: Steven McDowall
To: soap-user@xml.apache.org
Cc: soap-dev@xml.apache.org
Sent: Wednesday, July 26, 2000 11:47 AM
Subject: RE: Deploy Nightmare
If you haven't gotten your first problem fixed, make sure you grab the
latest
from CVS and build it.. There were a lot of fixes (including that one) that
are
still not in the "distrib" version..
-Steve
P.S. When ARE we going to make a new distrib?? I think it is about time..
-----Original Message-----
From: mark@peabrain.ffsoft.com [mailto:mark@peabrain.ffsoft.com]On
Behalf Of Mark Boylan
Sent: Tuesday, July 25, 2000 6:39 PM
To: soap-user@xml.apache.org
Subject: Deploy Nightmare
Ugh. I'm having a problem deploying services.
Actually, I think there are two separate problems.
The first is when I try to deploy from the command line:
------------------------------------------
[mark@babydoll calculator]$ java
org.apache.soap.server.ServiceManagerClient
http://localhost:8080/xml-soap/rpcrouter.jsp deploy
./DeploymentDescriptor.xml
Exception in thread "main" [SOAPException: faultCode=SOAP-ENV:Client;
msg=error parsing HTTP status line: Connection reset by peer: Connection
reset by peer; targetException=java.lang.IllegalArgumentException: error
parsing HTTP status line: Connection reset by peer: Connection reset by
peer]
at
org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnectionja
va,
Compiled Code)
at org.apache.soap.rpc.Call.invoke(Call.java, Compiled Code)
at
org.apache.soap.server.ServiceManagerClient.invokeMethod(ServiceManagerClien
t.java,
Compiled Code)
at
org.apache.soap.server.ServiceManagerClient.deploy(ServiceManagerClient.java
,
Compiled Code)
at
org.apache.soap.server.ServiceManagerClient.main(ServiceManagerClient.java,
Compiled Code)
[mark@babydoll calculator]$
------------------------------------------
The second problem is when I try to deploy from the browser,
I cant even load the deploy.jsp page:
------------------------------------------
Error: 500
Location: /xml-soap/deploy.jsp
Internal Servlet Error:
org.apache.jasper.JasperException: Unable to compile class for
JSP/opt/tomcat/work/localhost_8080%2Fxml-soap/_0002fdeploy_0002ejspdeploy_js
p_0.java:148:
No variable NS_URI_BML_ENC defined in class org.apache.soap.Constants.
org.apache.soap.Constants.NS_URI_BML_ENC};
^
1 error
at org.apache.jasper.compiler.Compiler.compile(Compiler.java,
Compiled Code)
at org.apache.jasper.runtime.JspServlet.loadJSP(JspServlet.java,
Compiled Code)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.loadIfNecessary(JspSe
rvlet.java,
Compiled Code)
at
org.apache.jasper.runtime.JspServlet$JspServletWrapper.service(JspServletja
va,
Compiled Code)
at
org.apache.jasper.runtime.JspServlet.serviceJspFile(JspServlet.java,
Compiled Code)
at org.apache.jasper.runtime.JspServlet.service(JspServlet.java,
Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java,
Compiled Code)
at
org.apache.tomcat.core.ServletWrapper.handleRequest(ServletWrapper.java,
Compiled Code)
at
org.apache.tomcat.core.ContextManager.service(ContextManager.java,
Compiled Code)
at
org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
onnectionHandler.java,
Compiled Code)
at
org.apache.tomcat.service.TcpConnectionThread.run(SimpleTcpEndpoint.java,
Compiled Code)
at java.lang.Thread.run(Thread.java, Compiled Code)
---------------------------------------
I'm running RH6.2, tomcat 3.1, xerces 1.0.4, Blackdown JDK 1.2.2.
I tried switching to xerces 1.0.3, and got the same results.
If anyone has any insight, please post. This is driving me nuts.
Thanks,
Mark