|Kohsuke Kawaguchi||Jul 27, 2006 2:08 pm|
|Scott Oaks||Jul 27, 2006 2:14 pm|
|Cheng Fang||Jul 27, 2006 2:17 pm|
|Jan Luehe||Jul 27, 2006 2:21 pm|
|Sreenivas Munnangi||Jul 27, 2006 3:11 pm|
|Mark Basler||Jul 27, 2006 3:24 pm|
|Jan Luehe||Jul 27, 2006 3:30 pm|
|Mark Basler||Jul 27, 2006 3:30 pm|
|Kohsuke Kawaguchi||Jul 27, 2006 3:36 pm|
|Mark Basler||Jul 27, 2006 3:38 pm|
|Kohsuke Kawaguchi||Jul 27, 2006 4:31 pm|
|Mark Basler||Jul 27, 2006 4:36 pm|
|Kedar Mhaswade||Jul 27, 2006 4:38 pm|
|Byron Nevins||Jul 27, 2006 4:54 pm|
|Jim Driscoll||Jul 28, 2006 8:35 am|
|Sameer Tyagi||Jul 28, 2006 11:59 am|
|Kedar Mhaswade||Jul 28, 2006 12:22 pm|
|Jan Luehe||Feb 13, 2009 1:48 pm|
|Jeanfrancois Arcand||Feb 13, 2009 1:54 pm|
|Hong Zhang||Feb 14, 2009 10:22 am|
|Wolfram Rittmeyer||Feb 15, 2009 5:36 am|
|Rajiv Mordani||Feb 17, 2009 10:42 am|
|Subject:||Re: Running glassfish in foreground?|
|From:||Mark Basler (Mark...@Sun.COM)|
|Date:||Jul 27, 2006 3:30:53 pm|
Did you also use the other JVM options to direct the log??? For example:
Here is a snippet from a previous email on getting dumps to a log when using the proprietary jvm options for J2SE 1.4. I am not sure if they will work in JavaSE 5, but it may be worth a try..
The easier way to do it is alter the jvm args in domain.xml or processLauncher.xml for the server/type to contain "-XX:+UnlockDiagnosticVMOptions -XX:+LogVMOutput -XX:LogFile=<file>". When a kill -3 is sent to the process the thread dump goes to the "<file>" location.
Hope this helps - Mark
Sreenivas Munnangi wrote:
Jan Luehe wrote On 07/27/06 02:21 PM,:
Scott Oaks wrote On 07/27/06 14:14,:
asadmin start-domain --verbose
This is particularly useful if you want to send a kill -3 signal (CTRL-BREAK on windows) to see a stack trace, as that output is otherwise lost (depending on the state of the build...it used to be lost, then it was fixed, then it was lost, and I'm not sure of it's state right now
It's not working with the latest 9.1 build, which is why I had filed https://glassfish.dev.java.net/issues/show_bug.cgi?id=838 ("-XX:+PrintClassHistogram" and SIGQUIT have no effect in default start mode) last week when I ran into this.
Jan, based on the following email exchange I thought the use of --verbose option worked for you. Can you pl. confirm.
This seems like a bug. Please file it. I just tried it. Workaround: asadmin start-domain --verbose. This should work, I tested it.
Thanks a lot, Kedar!
I've confirmed that your suggested workaroud does the trick.
On Thu, 2006-07-27 at 17:08, Kohsuke Kawaguchi wrote:
Would it be possible to run Glassfish in the foreground (as opposed to work like a daemon, which is what happens when I do "asadmin start-domain")?
In other words, I'd like to do the equivalent of "catalina.sh run" with Glassfish. I can see the console that way (presumably where I can configure logs to be sent) and I can kill it simply with Ctrl+C.