Jeffery, yes that does help. I don't think we are using JRun properly, and that if we were then we would not have this problem. We should not have to modify java.class.path in the jvm.config file when deploying new apps. If we put the jars in the proper JRun directory then the hot-deploy would work for us.
-----Original Message----- From: Jeffrey Anderson [mailto:[EMAIL PROTECTED] Sent: Thursday, November 06, 2003 10:09 AM To: JRun-Talk Subject: Re: Dynamic JRun Reconfiguration and Restart Wel...That is what hot-deploy is for... If you are developing your J2EE apps properly the class loader picks up the new libraries on deployment. Read the Jrun docs on how to package your application (ear file, or war file) and you won't have to restart. If you are dropping them in {jrun-root}/servers/{SERVER}/SERVER-INF/lib or {jrun-root}/lib or {jrun-root}/servers/lib Then yes you will need a restart, but since you haven't been specific in your question as to why you would need to do this, I will give you the benefit of the doubt you have your reasons. If this is the case you could try to reverse-engineer the method used by the JMC to start and restart servers since it is just another method call. Hope that helps. On 11/6/03 7:56 AM, "Baker, Ed" <[EMAIL PROTECTED]> wrote: > We modify java.class.path to point to the new .jar files. > > -----Original Message----- > From: Jeffrey Anderson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 05, 2003 5:35 PM > To: JRun-Talk > Subject: Re: Dynamic JRun Reconfiguration and Restart > > > What is it that you are modifying on the jvm.config that it needs a restart > in the first place? > > On 11/5/03 2:00 PM, "Baker, Ed" <[EMAIL PROTECTED]> wrote: > >> Hi Eric, >> >> That's great, but can I make it reread the Jrun/bin/jvm.config file on the >> fly after I've modified it with an application running under JRun4? >> >> Thanks, >> >> -Ed >> >> -----Original Message----- >> From: Eric Anderson [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, November 05, 2003 2:42 PM >> To: JRun-Talk >> Subject: RE: Dynamic JRun Reconfiguration and Restart >> >> >> Hot deployment and auto deployment are both features of JRun 4. >> >> Eric >> >> -----Original Message----- >> From: Baker, Ed [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, November 05, 2003 2:28 PM >> To: JRun-Talk >> Subject: Dynamic JRun Reconfiguration and Restart >> >> We have a product that is dynamically extensible and allows the addition > of >> applications. When we detect a new application we programmatically modify >> the JRun configuration file(s). Is there a way to restart JRun or have it >> reread its configuration files on the fly? >> >> Thank you, >> >> -Ed >> >> >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Get the mailserver that powers this list at http://www.coolfusion.com Message: http://www.houseoffusion.com/lists.cfm?link=i:8:5296 Archives: http://www.houseoffusion.com/lists.cfm?link=t:8 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:8 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=<:emailid:>.<:userid:>.<:listid:>
