Jeremy,
After updating my code with your fix, the login failed message is now gone. I am getting another exception, but I think its a deployment problem. Let me dig a little, but I believe that this issue can be closed.
Mark
Jeremy Boynes (JIRA) wrote:
[ http://issues.apache.org/jira/browse/GERONIMO-540?page=history ]
Jeremy Boynes resolved GERONIMO-540:
------------------------------------
Resolution: Fixed Fix Version: 1.0-M4
Fix applied in revision 125807 Seems to work on my machine but I'm leaving this open until others can verify.
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 Assignee: Jeremy Boynes Fix For: 1.0-M4 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)
