admin@glassfish.java.net

Re: debug message now missing

From: Tom Mueller <tom.mueller_at_oracle.com>
Date: Mon, 14 Mar 2011 14:23:32 -0500

AFAIK, there isn't a bug filed on this.
Tom


On 3/14/2011 11:56 AM, Bobby Bissett wrote:
> Anyone know if this was filed/documented anywhere?
>
> Am still seeing this in the trunk. I can file an issue if there's not one already.
>
> Thanks,
> Bobby
>
> On Feb 1, 2011, at 11:02 AM, Bobby Bissett wrote:
>
>> Hi all,
>>
>> When starting up in debug mode with suspend=y in my config, I used to get this helpful, friendly message from asadmin telling me that the server was waiting for me to connect.
>>
>> Now that's gone. Here's my startup output:
>>
>> --- begin ---
>> hostname% ./glassfish3/glassfish/bin/asadmin start-domain --debug
>> Waiting for domain1 to start ...............
>> --- end ---
>>
>> It's waiting for me to connect, but not telling me so. Once I connect with the debugger, I see that message output *after* I've already connected:
>>
>> --- begin ---
>> hostname% ./glassfish3/glassfish/bin/asadmin start-domain --debug
>> Waiting for domain1 to start .....................................
>> Successfully started the domain : domain1
>> domain Location: /Users/bobby/work/ws/v3/distributions/glassfish/target/glassfish3/glassfish/domains/domain1
>> Log File: /Users/bobby/work/ws/v3/distributions/glassfish/target/glassfish3/glassfish/domains/domain1/logs/server.log
>> Admin Port: 4848
>> Debugging is enabled. The debugging port is: 9009
>> Command start-domain executed successfully.
>> --- end ---
>>
>> If I start with --verbose on, then I see the message *before* connecting, but I didn't need to specify --verbose before.
>>
>> --- begin ---
>> hostname% ./glassfish3/glassfish/bin/asadmin start-domain --debug --verbose
>> Feb 1, 2011 10:56:23 AM com.sun.enterprise.admin.launcher.GFLauncherLogger info
>> INFO: JVM invocation command line:
>> [...]Feb 1, 2011 10:56:23 AM com.sun.enterprise.admin.launcher.GFLauncherLogger info
>> INFO: Successfully launched in 31 msec.
>> Listening for transport dt_socket at address: 9009
>> --- end ---
>>
>> This isn't a show-stopper issue, but the behavior is different than what I'm used to so maybe it needs to be documented. Or maybe I was just used to the wrong thing, though it doesn't seem very friendly to work the way it's working now.
>>
>> Thanks,
>> Bobby
>>