geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "anita kulshreshtha (JIRA)" <...@geronimo.apache.org>
Subject [jira] Created: (GERONIMO-656) Invalid Login in deployer should not print the stack trace
Date Fri, 27 May 2005 12:13:03 GMT
Invalid Login in deployer should not print the stack trace
----------------------------------------------------------

         Key: GERONIMO-656
         URL: http://issues.apache.org/jira/browse/GERONIMO-656
     Project: Geronimo
        Type: Bug
    Versions: 1.0-M4    
 Environment: All environments
    Reporter: anita kulshreshtha
    Priority: Trivial


The deployer should not print out the following stack trace for invalid logins caused by null/bad
 Username/Password. Just an invalid login message should be enough.

Username:
Password:
    Error: Unable to connect to server

org.apache.geronimo.deployment.plugin.factories.AuthenticationFailedException: Invalid login.
        at org.apache.geronimo.deployment.plugin.factories.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryI
mpl.java:87)
        at javax.enterprise.deploy.shared.factories.DeploymentFactoryManager.getDeploymentManager(DeploymentFactoryManag
er.java:109)
        at org.apache.geronimo.deployment.cli.ServerConnection.tryToConnect(ServerConnection.java:182)
        at org.apache.geronimo.deployment.cli.ServerConnection.doAuthPromptAndRetry(ServerConnection.java:238)
        at org.apache.geronimo.deployment.cli.ServerConnection.tryToConnect(ServerConnection.java:185)
        at org.apache.geronimo.deployment.cli.ServerConnection.<init>(ServerConnection.java:147)
        at org.apache.geronimo.deployment.cli.DeployTool.execute(DeployTool.java:111)
        at org.apache.geronimo.deployment.cli.DeployTool.main(DeployTool.java:254)
Caused by: java.lang.SecurityException: Invalid login
        at org.apache.geronimo.jmxremoting.Authenticator.authenticate(Authenticator.java:61)
        at javax.management.remote.rmi.RMIServerImpl.newClient(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
        at sun.rmi.transport.Transport$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Unknown Source)
        at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
        at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
        at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
        at sun.rmi.server.UnicastRef.invoke(Unknown Source)
        at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
        at javax.management.remote.rmi.RMIConnector.getConnection(Unknown Source)
        at javax.management.remote.rmi.RMIConnector.connect(Unknown Source)
        at javax.management.remote.JMXConnectorFactory.connect(Unknown Source)
        at org.apache.geronimo.deployment.plugin.factories.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryI
mpl.java:81)
        ... 7 more

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


Mime
View raw message