Make error handling in deployment plugin more user friendly
-----------------------------------------------------------
Key: GERONIMO-593
URL: http://issues.apache.org/jira/browse/GERONIMO-593
Project: Geronimo
Type: Improvement
Components: deployment
Reporter: John Sisson
Priority: Minor
E.G. for a "Connection reset" error, rather than dumping out approx 37 lines of
stack trace, just output a message identifying the operation that failed and
the cause (e.g. java.net.SocketException: Connection reset). Possibly provide
a verbose option to dump whole stack trace?
E.G. currently you get:
java.rmi.UnmarshalException: Error unmarshaling return header; nested exception
is:
java.net.SocketException: Connection reset
org.apache.geronimo.kernel.InternalKernelException:
java.rmi.UnmarshalException: Error unmarshaling return header; nested exception
is:
java.net.SocketException: Connection reset
at
org.apache.geronimo.kernel.jmx.KernelDelegate.invoke(KernelDelegate.java:232)
at
org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:92)
at
org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:71)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.rmi.UnmarshalException: Error unmarshaling return header;
nested exception is:
java.net.SocketException: Connection reset
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:203)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown
Source)
at mx4j.remote.rmi.ClientInvoker.invoke(ClientInvoker.java:207)
<snip>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
