|
Replies:
6
-
Last Post:
Oct 5, 2009 9:33 AM
by: skeeny
|
|
|
|
|
|
|
Why do I have to restart GlassFish on every single little change? I
Posted:
Dec 23, 2008 4:20 PM
|
|
|
Maybe it's just my particular installation of glassfish but it seems for even the most trivial change I have to restart the entire application server for the changes to take effect. Particularly for entries such as JNDI or enabling certain log monitoring features. Does it really have to be like that? Does changing my password really mean I have to shut down the entire application server for it to take effect? Enabling precompile means that again the WHOLE server has to be shutdown and rebooted again? Maybe I'm the only one annoyed by this but it certainly seems, ridiculous. I'm certainly curious how others deploy GlassFish for production issues handle that. Shutting down a E-Commerce site because you don't want your admin console to time out in 60 minutes seems a little awkward to say the least.
|
|
|
|
|
|
|
Re: Why do I have to restart GlassFish on every single little change? I
Posted:
Dec 23, 2008 4:41 PM
in response to: xyonanexus
|
|
|
I noticed -- while I happened to be tailing my server.log file -- that some changes in the admin console in fact do (sort of) silently bounce just the domain. Unfortunately, the admin console doesn't do the best job of telling you when something "took effect" or whether you need to bounce the whole thing. But the server.log does show the "silent" restarts and they take far less time.
|
|
|
|
|
|
|
|
|
RE: Why do I have to restart GlassFish on every single little change? I
Posted:
Dec 23, 2008 6:38 PM
in response to: russpet
|
|
|
Arguably, you shouldn't be making changes like logging level changes or admin console timeout changes to a server running in production.
However, I would like to not have to restart my domain so much during dev/test.
Alex Sherwin
alex.sherwin@acadiasoft.com
-----Original Message-----
From: glassfish@javadesktop.org [mailto:glassfish@javadesktop.org]
Sent: Tuesday, December 23, 2008 7:41 PM
To: users@glassfish.dev.java.net
Subject: Re: Why do I have to restart GlassFish on every single little change? I
I noticed -- while I happened to be tailing my server.log file -- that some changes in the admin console in fact do (sort of) silently bounce just the domain. Unfortunately, the admin console doesn't do the best job of telling you when something "took effect" or whether you need to bounce the whole thing. But the server.log does show the "silent" restarts and they take far less time.
[Message sent by forum member 'russpet' (russpet)]
http://forums.java.net/jive/thread.jspa?messageID=323161
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net
|
|
|
|
|
|
|
|
|
Re: RE: Why do I have to restart GlassFish on every single little change? I
Posted:
Dec 25, 2008 7:43 AM
in response to: Alex Sherwin
|
|
|
> Arguably, you shouldn't be making changes like
> logging level changes or admin console timeout
> changes to a server running in production.
>
> However, I would like to not have to restart my
> domain so much during dev/test.
>
And you don´t.
The vast majority of changes during dev/test are redeploys of earfiles (and other deployment archives) and don´t require a restart (though in my experience it´s often better for stability to do one anyway, as it is with any appserver, there´s always the chance of something not being properly cleared from a ClassLoader somewhere and causing trouble down the line).
|
|
|
|
|
|
|
|
|
Re: Why do I have to restart GlassFish on every single little change? I
Posted:
Dec 25, 2008 1:53 AM
in response to: xyonanexus
|
|
|
i'm sure its not so much glassfish as it is requirements of the ee specification.
|
|
|
|
|
|
|
|
|
Re: Why do I have to restart GlassFish on every single little change? I
Posted:
Jan 6, 2009 6:51 PM
in response to: ilazarte
|
|
|
Hi,
Following is the reply from GlassFish Admin GUI testing. What GlassFish version are you using ? There was one bug filed in GlassFish v3, 6644(https://glassfish.dev.java.net/issues/show_bug.cgi?id=6644), but for GlassFish v2 we could not recreate your scenarios. When you had a change triggers the message show up in any case, you should restart domain, otherwise, this message will always show on the screen. Would you please try this and if you still see this issue, please help us log a bug. Thanks, Judy
-----
User mentioned couple scenarios:
1. enable log monitoring
for v2.1 9.1.1, the change doesn't require server restart, just tested
2. change password
no require restart show for both v2.1 and v3
3. enabling precompile
does it mean to enable jsp precompile during deployment, I tried on v2.1, and it doesn't trigger restart message
|
|
|
|
|
|
|
|
|
Re: Why do I have to restart GlassFish on every single little change? I
Posted:
Oct 5, 2009 9:33 AM
in response to: judytangs
|
|
|
I'd like to resurrect this topic....I'm using GF v2.1 and found that after turning Monitoring on (via choosing HIGH or LOW on the Monitoring Service page), a restart appears to be necessary or else the domain will not behave well after other configuration changes are made and attempts to restart. No notice on the admin console that the domain needs to be restarted, no "needs restart" in the asadmin list-domains output for the domain.
Anyone else experience this issue?
Thanks.
|
|
|
|
|
java.net RSS
