[
http://issues.apache.org/jira/browse/GERONIMO-540?page=comments#action_57827 ]
Jason Zou commented on GERONIMO-540:
------------------------------------
When debug using a simple client, the exception trace is as following.
It seems JDK 1.5's JMX impl getClassLoaderRepository before auth.
I have created a emptyClassLoaderRepository to fix this issue. Now the server
can use JDK 1.5's JMX impl instead of Mx4J.
Maybe further decision should be made to decide if using JDK 1.5's JMX impl is
reasonable.
--------------------------------------------
java.lang.SecurityException: Operation not allowed
at
org.apache.geronimo.kernel.jmx.MBeanServerDelegate.getClassLoaderRepository(MBeanServerDelegate.java:329)
at
javax.management.remote.rmi.RMIConnectionImpl$2.run(RMIConnectionImpl.java:1281)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.management.remote.rmi.RMIConnectionImpl.getClassLoaderRepository(RMIConnectionImpl.java:1278)
at
javax.management.remote.rmi.RMIConnectionImpl.access$000(RMIConnectionImpl.java:81)
at
javax.management.remote.rmi.RMIConnectionImpl$1.run(RMIConnectionImpl.java:132)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.management.remote.rmi.RMIConnectionImpl.<init>(RMIConnectionImpl.java:129)
at
javax.management.remote.rmi.RMIJRMPServerImpl.makeClient(RMIJRMPServerImpl.java:137)
at
javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:230)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:595)
> Unable to login to server when using jdk 1.5
> --------------------------------------------
>
> Key: GERONIMO-540
> URL: http://issues.apache.org/jira/browse/GERONIMO-540
> Project: Apache Geronimo
> Type: Bug
> Components: deployment, security
> Versions: 1.0-M4
> Environment: Windows XP / JDK 1.5
> Reporter: Mark DeLaFranier
> Attachments: my-changes-to-MBeanServerDelegate.patch
>
> 1. Get the latest codeline (Jan 7/2005)
> 2. Do a build
> 3. Open a command prompt with JDK 1.5
> > java -version
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64)
> Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing)
> 4. Start the server
> java -jar bin\server.jar org/apache/geronimo/RuntimeDeployer
> org/apache/geronimo/DebugConsole
> 5. Open a second command prompt and setup the same jdk 1.5 environment
> 6. Deploy a sample EJB (dead simple hello world ejb)
> > java -jar bin\deployer.jar deploy myejb.jar
> Username: system
> Password: manager
> Error: Unable to connect to server: Invalid login.
> I didn't notice any exceptions on the server side and nothing new is sent to
> the console or the server log file.
> If I used jdk 1.4 to start the server and run the client deployment tool then
> it works.
> > java -jar bin\deployer.jar deploy myejb.jar
> Username: system
> Password: manager
> Deployed myejb
> java version "1.4.2_04"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
> Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
--
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
