Issue Details (XML | Word | Printable)

Key: GLASSFISHPLUGINS-326
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: ludo
Reporter: mkrainer
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
glassfishplugins

Starting glassfish in debug mode fails with 'wrong user name or password.'

Created: 20/Jan/11 01:26 AM   Updated: 28/Oct/11 11:07 AM   Resolved: 24/Jan/11 04:00 PM
Component/s: eclipse
Affects Version/s: current
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: 1. Text File oracle.eclipse.tools.glassfish.patch (1 kB) 20/Jan/11 11:49 PM - ruaudl

Environment:

Linux, Eclipse 3.6.1, glassfish 3.0.1


Tags: eclipse plugin glassfish launch
Participants: ludo, mkrainer, narduk and ruaudl


 Description  « Hide

I cannot debug my webapp on glassfish from eclipse because every time I start the app in debug mode I get the message "Wrong user name or password.". Although glassfish runs fine, in eclipse it says [stopped] and debugging is not possible (and you have to manually kill glassfish).
In "normal" operation glassfish runs with no warnings/errors so I had no clue where that comes from.
Nevertheless I changed all passwords, reinstalled certificates, reinstalled eclipse and plugins, created a new server instance, created a new workspace a.s.o. Nothing helped, so I finally looked into the code, just to find out, that in SunAppServer.getV3ServerStatus() there is a hardcoded 30 seconds time limit after it returns a CREDENTIAL_ERROR! I checked it - and of course - after exact those 30 seconds the message pops up.

So please:

1.) Change the error message to sth that doesn't mislead the developer

2.) Increase the timeout - or better make it configurable.

thanks



ruaudl added a comment - 20/Jan/11 11:48 PM

Actually, I had the same issue and looking at the code and logs, it appears GlassFish is sending a "please wait" response to the plugin.
The plugin then consider the request as failed and throw an exception regarding credentials.

However, the "please wait" message is catched but not taken into account :

ServerCommand.readResponse():
if(message != null && message.contains("please wait")) { retry = true; } else { serverMessage = null != message ? message.replaceAll("%%%EOL%%%", "\n") : ""; }

CommandRunner.call(): does not take care of serverCmd.retry()

Small patch attached.


ruaudl added a comment - 20/Jan/11 11:49 PM

Patch to take care of "please wait" responses.


ludo added a comment - 21/Jan/11 09:11 AM

Thanks for the patch! will try it asap and integrate it... My dev machine might be too fast?
Anyway great to see your active participation!!!


ruaudl added a comment - 21/Jan/11 11:09 AM

I'm curently building a custom Eclipse distro for my team based on M2eclipse and GlassFish/OEPE.
I'll try to give as much info as I can on the issues I'll find

Happy to help on this one but my patch's just adding the test on serverCmd.retry() on the while loop.

In my case, this bug appeared this way:

  • Start GlassFish
  • Deploy an app (EAR) with numbers of libs (more than 50 MB, like GWT + Spring + Hibernate)
  • Stop the server
  • Restart the server
  • The server seems to be deploying all the apps at startup (which takes more than two minutes) before answering any _locations command, thus send a "please wait" response

ludo added a comment - 24/Jan/11 04:00 PM

Patch committed


narduk added a comment - 28/Oct/11 11:04 AM - edited

I'm still having this issue "Starting glassfish in debug mode fails with 'wrong user name or password"

However, I have no idea what is causing it. I'm using:
-Glassfish 3.1.1
-Oracle Glassfish Server Tools 4.0.2
-Eclipse Indigo
-Ubuntu 10.04 LTS