You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "John Sisson (JIRA)" <de...@geronimo.apache.org> on 2005/02/23 06:53:49 UTC

[jira] Created: (GERONIMO-593) Make error handling in deployment plugin more user friendly

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


[jira] Updated: (GERONIMO-593) Make error handling in deployment plugin more user friendly

Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Updated: (GERONIMO-593) Make error handling in deployment plugin more user friendly

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-593?page=all ]

Aaron Mulder updated GERONIMO-593:
----------------------------------

    Fix Version: 1.0
    Description: 
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>

  was:
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>

        Version: 1.0-M3
    Environment: 

Do you have a procedure to reproduce this problem?

> 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
>     Versions: 1.0-M3
>     Reporter: John Sisson
>     Priority: Minor
>      Fix For: 1.0

>
> 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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (GERONIMO-593) Make error handling in deployment plugin more user friendly

Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-593?page=all ]

Aaron Mulder updated GERONIMO-593:
----------------------------------

    Component: Maven Plugins for G
                   (was: deployment)

> 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: Maven Plugins for G
>     Versions: 1.0-M3
>     Reporter: John Sisson
>     Priority: Minor
>      Fix For: 1.1

>
> 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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (GERONIMO-593) Make error handling in deployment plugin more user friendly

Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-593?page=all ]

Matt Hogstrom updated GERONIMO-593:
-----------------------------------

    Fix Version/s: Wish List
                       (was: 1.2)

> Make error handling in deployment plugin more user friendly
> -----------------------------------------------------------
>
>                 Key: GERONIMO-593
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-593
>             Project: Geronimo
>          Issue Type: Improvement
>          Components: Maven Plugins for G
>    Affects Versions: 1.0-M3
>            Reporter: John Sisson
>            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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (GERONIMO-593) Make error handling in deployment plugin more user friendly

Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/GERONIMO-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon closed GERONIMO-593.
---------------------------------

       Resolution: Invalid
    Fix Version/s:     (was: Wish List)

Too old

> 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
>
> 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.


[jira] Updated: (GERONIMO-593) Make error handling in deployment plugin more user friendly

Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-593?page=all ]

Dain Sundstrom updated GERONIMO-593:
------------------------------------

    Fix Version: 1.1
                     (was: 1.0)

> 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
>     Versions: 1.0-M3
>     Reporter: John Sisson
>     Priority: Minor
>      Fix For: 1.1

>
> 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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira