You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jason Dillon (JIRA)" <ji...@apache.org> on 2007/06/14 18:41:26 UTC
[jira] Updated: (GERONIMO-593) Make error handling in deployment
plugin more user friendly
[ https://issues.apache.org/jira/browse/GERONIMO-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Dillon updated GERONIMO-593:
----------------------------------
Component/s: (was: Maven Plugins for G)
geronimo-maven-plugin
Assignee: Jason Dillon
> Make error handling in deployment plugin more user friendly
> -----------------------------------------------------------
>
> Key: GERONIMO-593
> URL: https://issues.apache.org/jira/browse/GERONIMO-593
> Project: Geronimo
> Issue Type: Improvement
> Components: geronimo-maven-plugin
> Affects Versions: 1.0-M3
> Reporter: John Sisson
> Assignee: Jason Dillon
> Priority: Minor
> Fix For: Wish List
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.