Hot deployment and JMX

Hi,
I need to know how classes are loaded in hot deployment. my problem is that I'm using a JMX server that has some MBeans registered into it, but when I redeploy an application, and the JMX server is recreated as are the MBeans, the JMX agent clearly points to the old instances of the MBeans instead of the redployed ones. It seems that only restarting the OC4J would fix the pointers.
Is there any way to fix this? or do I have to restart the server every time I deploy an application?

What option are you using for deployment ? Are you choosing re-deploy ? We recommend Oracle9iAS install in a test/production environment when
the application has stabilized.
Also if you are in a development mode and constantly changing your applications you should consider deploying your apps in standalone OC4J. You can choose to do open-expanded directory deployment.
If you are using OC4J standalone:
1) you can replace the EAR file in applications directory and it redeploys
2) you can replace a Servlet class and change the time stamp on web.xml and it redeploys the srvlets
3) It automatically redeploys the JSP files
4) If your EJBs are changed, replace your EJBs and change the timestamp on application.xml and it redeploys
Some of these options are disabled in OC4J embedded in Oracle9iAS to provide a stable environment for production applications.
If you still have problems in hot-deployment in OC4J please send me a test case at [email protected]
thanks
Debu

Similar Messages

Specifications of deployment and lifecycle of JMX beans in a JEE server

Hello,
one colleague of mine is developping a service that uses an MBean to mimick a singleton (the MBean is not used for instrumentation or administration, it just holds a pool of shared non-standard resources) within a Glassfish server.
I fought this idea (as I found a static utility would be both straightforward and easy to implement), but I took it, from this forum in particular, that it is a recommended way to use an MBean to serve as a shared resource holder. Point taken (I'm not concerned with clustering yet, I mean it's OK if the singleton is not cluster-wide)
The problem is, my colleague warns that he witnesses "strange deployment behavior" with regard to the MBEan: in particular, it seems that the MBean is not unregistered upon EAR undeployment, and not redeployed upon EAR re-deployment. In particular updates to the MBean code (currently packaged within the EAR) require a server restart to take effect.
From what I understand, the MBean is registered in a JVM-wide registry (the MBean server), and its classs and instances have a different lifecycle from the EAR, which has (some sort of, obviously more complex in the details) class-loader scope.
I admit I'm making that up, from various observation -> my main problem is that I can't find an appserver-agnostic specification of the MBean lifecycle in a JEE environement. The EJB3 specification do not mention JMX (but as I understand it EJB3 alters none of the way JMX works).
There seems however to be a J2EE-specific way of handling MBean - presumably because the hot-deployment-without-JVM-restart expands the MBean lifecycle beyond the EAR lifecycle.
Could you point me to authoritative references on JMX used in JEE servers. In particular specification of the lifecycle and deployment is extremely welcome.
I'm sorry for asking pointers: my own web searches turn up non-specifying docs.
And if I search on JMX and Glassfish together, I find articles on either:
- how Glassfish uses JMX to implement a lot of stuff, but not how Glassfish implements "JMX lifecycle" (if that expression even means something).
- how to extend Glassfish's adminsitration capabilites writing custom MBeans
Thanks in advance,
J.

The location of the registration code is thus the key to all this. e.g If you register manually in some startup class, you can unload/load the required versions of the MBean code.That's what we do (using a RegistryServlet and init()/destroy() callbacks).
Sketchy description from what I understand of the developer's code: the init() indeed looks up the MBean and unregisters it if it exists, then registers it anew. Sometimes, the unregistering will fail (I haven't witnessed that), which triggered this topic.
We have to investigate it further (with more rigorous archiving and analysis of the error logs). I'll post updates if any.
If the MBeans are configured to be registered by the server itself (common) then the server would need to be restarted for the changes to be picked.OK. I have no idea how to configure where the MBeans are registered, time now to confess I have used JMX only in trivial cases so far.
It is my sincere hope that you won't need to use the techniques of chapter 8 of [this specification|http://java.sun.com/javase/6/docs/technotes/guides/jmx/JMX_1_4_specification.pdf] .
Indeed!
Probably my lack of JMX knowledge, but I have no idea what the "Mlet service" is in my scenario, and I suspect I won't want to know :o)
Overall this suggests that using JMX introduces unforeseen complexities, that may be overkill in our scenario (but I'm biased as I defended a couple of other alternatives).
Thanks for your help so far; I'm still looking for some document that would clarify how the JEE server, or how Glassfish specifically, handles MBean lifecycle.

Procedure for hot deploying EJBs using Jdeveloper and OC4J comtainer

i am using JDeveloper , please any one help me out in hot deploying EJBs. what is the procedure if i want to hot deploy EJBS

1) You have to start OC4J with higher Java heap size e.g. java -Xms100m -Xmx150m -jar oc4j.jar
2) The RMI port by default used is 23791 and configurable by modifying config/rmi.xml.
regards
Debu

Creation of InitialContext fails when i hot-deploy scheduler-service.xml

Creation of InitialContext fails when i hot-deploy scheduler-service.xml
I configured scheduler-service as follows in Jboss 3.2:
scheduler-service.xml
<mbean code="org.jboss.varia.scheduler.Scheduler"
 name=":service=Scheduler">
<attribute name="StartAtStartup">true</attribute>
<attribute name="SchedulableClass">com.beta.my.utils.FMScheduler</attribute>
<attribute name="SchedulableArguments">Schedulabe Test,12345</attribute>
<attribute name="SchedulableArgumentTypes">java.lang.String,int</attribute>
<attribute name="InitialStartDate">0</attribute>
<attribute name="SchedulePeriod">10000</attribute>
<attribute name="InitialRepetitions">-1</attribute>
</mbean>
Schedulable Class
package com.beta.my.utils;
import java.util.Date;
import org.jboss.varia.scheduler.Schedulable;
public static class FMScheduler
implements Schedulable
private String mName;
private int mValue;
public FMScheduler(String pName,int pValue)
mName = pName;
mValue = pValue;
public void perform(Date pTimeOfCall,long pRemainingRepetitions)
try {
 Context context = new InitialContext();//properties taken from jndi.properties file
 } catch (Exception e){
 e.printStackTrace();
I started my jboss..,FMScheduler created successfully, perform method in FMScheduler called succesfully after SchedulePeriod(1000)
The problem occurs(NullPointerException) while i changed SchedulePeriod time and hot-deployed(just saved scheduler-service.xml).
The following Exception occures due to InitialContext creation fails*(Context context = new InitialContext();)* in FMScheduler.
17:46:27,361 ERROR [STDERR] java.lang.NullPointerException
17:46:27,361 ERROR [STDERR] at org.jboss.mx.loading.UnifiedClassLoader.findR
esources(UnifiedClassLoader.java:374)
17:46:27,361 ERROR [STDERR] at java.lang.ClassLoader.getResources(ClassLoade
r.java:825)
17:46:27,361 ERROR [STDERR] at com.sun.naming.internal.VersionHelper12$5.run
(VersionHelper12.java:145)
17:46:27,361 ERROR [STDERR] at java.security.AccessController.doPrivileged(N
ative Method)
17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.VersionHelper12.getRe
sources(VersionHelper12.java:142)
17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.ResourceManager.getAp
plicationResources(ResourceManager.java:468)
17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.ResourceManager.getIn
itialEnvironment(ResourceManager.java:159)
17:46:27,377 ERROR [STDERR] at javax.naming.InitialContext.init(InitialConte
xt.java:215)
17:46:27,377 ERROR [STDERR] at javax.naming.InitialContext.<init>(InitialCon
text.java:195)
17:46:27,377 ERROR [STDERR] at com.beta.my.utils.FMScheduler.perform
(FMScheduler.java:42)
17:46:27,392 ERROR [STDERR] at org.jboss.varia.scheduler.Scheduler$Listener.
handleNotification(Scheduler.java:1263)
17:46:27,392 ERROR [STDERR] at org.jboss.mx.server.NotificationListenerProxy
.handleNotification(NotificationListenerProxy.java:69)
17:46:27,392 ERROR [STDERR] at javax.management.NotificationBroadcasterSuppo
rt.sendNotification(NotificationBroadcasterSupport.java:95)
17:46:27,392 ERROR [STDERR] at javax.management.timer.Timer.sendNotification
s(Timer.java:441)
17:46:27,392 ERROR [STDERR] at javax.management.timer.Timer.access$000(Timer
.java:31)
17:46:27,408 ERROR [STDERR] at javax.management.timer.Timer$RegisteredNotifi
cation.doRun(Timer.java:612)
17:46:27,408 ERROR [STDERR] at org.jboss.mx.util.SchedulableRunnable.run(Sch
edulableRunnable.java:164)
17:46:27,408 ERROR [STDERR] at org.jboss.mx.util.ThreadPool$Worker.run(Threa
dPool.java:225)
please help me if u have any idea,thanks

Hi Hamsa,
Did you also create and configure an "Execution Destination"?
You can test the Metadata destination configuration on Web Service Navigator.
On the web service navigator (http://hostname:portnumber/wsnavigator) search in the metatda destination you have created for the service you imported in web dynpro as a model. If you can find it there test it on the ws navigator.
Best regards,
Yasar

Hot deployment of class files (non-EJB)

Also posting to the servlet newsgroup.
"Craig Ambrose" <[email protected]> wrote in message
news:[email protected]..
>
I am using WebLogic 6.1 and am interested in using auto-deployment indevelopment
mode of JSPs and class files that those JSPs rely on. I have a simpleWebLogic
application that gets deployed using the exploded directory format andwhen I
modify the JSPs or the class files that they use everything reloadsproperly and
a newly modified class file will be reloaded the next time the pageutilizing
the Java class is requested.
I have a much more complicated application (the one I am really doing workon)
and I can't get the hot deploy of the class files to take effect. The JSPswill
reload but I can't seem to cause the class loader to reload any changedclass
files. If I use the WebLogic Console and un-deploy and then re-deploy theapplication
then the class files will be reloaded, but I thought that wasn't necessaryfor
hot deployment. This complex application stores many things in the HTTPsession
context. I am wondering if that has an effect on the class loader fordependant
class files.
I'm pretty sure it is not a configuration issue as I have it working forthe simple
application. I have the application deployed under the.\config\<domainname>\applications
directory and am using the exploded directory format with the class filesalso
exploded in the WEB-INF\classes directory.
Any insights on dependancies of the hot depployment would be helpful.

Hot deployment of servlet

hi
i have compiled the servlet in jdeveloper and set the path to oc4j../../web-inf/classes path;after compiling the class Is it neccassary to shutdown the oc4j container;
after shutdown the container only i am seeing the effect;without shutdown the container can we see the effect;we can do it Tomcat ;Is there any facility in OC4J ;
bye
chaitanya

 Hi, suppose you have the servlet called JoeServlet and registered as joeservlet with an argument, say, a file joe.txt. If you want to 'hot' deploy the JoeServlet you should make sure that a) the servlet's name must be unique b) the servlet's class must be in your servlet classpath (see the properties sheet aside) c) the initial argument, say: joeargument=./joe.txt, must match the the name expected by your servlet (eg. getInitParameter("joeargument")). If you have done correctly WLS must work.
 Joe
 "Jayesh Patel" <[email protected]> wrote:
 >
 >I am trying to hot deploy a simple servlet using weblogic console.
 >
 >I am getting error saying that
 >
 >"Property change error for property "RegisterNewServlet".
 >Servlet could not be loaded or instantiated"
 >
 >I am sure that servlet class I am trying to load is in servlet
 >class path.
 >
 >Any idea what is going wrong here.
 >
 >Thanks.
 >
 >
 >

Hot deployment while running...

Hi there!
Does any body have experience HotDeployment while end user are using the application?
For my self I got a real problem with HttpSession. After hot deployment all
sessions are invalidate!! I mean "request.getSession(false)" return false. I
have already carefully read documentation and pointed out that object store in
session must be serializable. OK it's done. Now what else should I check?
Thanks!

redeploying will invalidate a servlet session. this is not a bug, but rather the intended
behavior.
if all you want to do is update content (jsp's, html, gif, jpeg, etc) you can use the
refresh tool.
it is a light-weight operation, instead of the heavyweight redeploy.
to use it, please run the command:
java weblogic.management.tools.WebAppComponentRefreshTool
(this tool is compatible with 6.0 and 6.1)
tracey
"Thierry Giguère" wrote:
Hi there!
Does any body have experience HotDeployment while end user are using the application?
For my self I got a real problem with HttpSession. After hot deployment all
sessions are invalidate!! I mean "request.getSession(false)" return false. I
have already carefully read documentation and pointed out that object store in
session must be serializable. OK it's done. Now what else should I check?
Thanks!

Hot deployment

Hi,
I have a gateway which instantiates and runs applications. Each application implements an interface so the gateways only sees the class at type (interface).
I have a huge problem in that we have a number of developers working on these applications. There are constantly bug fixes, new functionality etc. that must be added.
How can I hot deploy these classes? I cannot restart the entire gateway every time I upload a class. This affects all the other applications.
I have looked at dynamic class loading but this is going to take some serious time to create a custom class loader that will actually destroy old class loaders when creating new ones.
Is there a simpler way to enable my gateway for hot deployment?
thanks!

Creating a new classLoader does not take a lot, and you can tell it NOT to cache the class.
Also, you can simply destroy all current references to a class when running, replace the class file, and then allow code to call the class object again - thus reading the new class file.
It's not typically a good idea to deploy-in-production any code.

Hot swap and JSP debugging for Weblogic in exploded format?

Hi,
I'm trying to use JDeveloper for JSF development to be deployed to a weblogic server.
I must say JDeveloper is a great tool for JSF development as none of the free IDE in the market can do what JDeveloper does.
However, I have a question on hot swap and JSP debugging.
I have managed to setup JDeveloper to debug my JSF application deploy to my Weblogic server's applications folder in exploded format.
I can step through the java code.
However, I didn't manage to do a hot swap and the break point set in the JSF-JSP does not seems to take effect.
I would appreciate any advice on the problem.
Thanks.
Han Ming

How did you setup the server to handle exploded format? Appreciate the help. Sorry can't help with your question though.
Thnx.
Soni

Having issues hot deploying with ebcc in Solaris environment.

I keep getting an error message when hot deploying a new webapp portal using ebcc.
The error message reads" Unable to add module. appname to application descriptor for portal app. I check the portalapptools and i see the webapp in the portal management.. I also see that it added this to the database under the Portal table.. It never actually added the webapplication under in the console.. This is where it gets stuck... Basicly the steps that are missing are adding a deployment descriptor and then the webapp.. I manually did it and it works.. the problem after that is that i need to execute sync.sh after i bounce the manage server or else i dont see the webapps under portal management..
So basicly the 2 questions are:
1..Why doesnt hot deploying work in unix using X11?
2.. Why do i need to execute sync.sh everytime after every bounce?
Thanks,
Oscar

Oscar,
Are you running the EBCC on the same machine as your server? The hot
deploy mechanism of the EBCC forces you to have the server and the EBCC
on the same machine. While the files are sync'd to the database, the
web app files never get transfered. The deployer then is syncing to
nothing.
Try running it all on one machine, locally or with a remote display.
Depending on your window manager some Java Swing applications like the
EBCC do not always display fonts well remotely but it should still work.
oscar sumano wrote:
I keep getting an error message when hot deploying a new webapp portal using ebcc.
The error message reads" Unable to add module. appname to application descriptor for portal app. I check the portalapptools and i see the webapp in the portal management.. I also see that it added this to the database under the Portal table.. It never actually added the webapplication under in the console.. This is where it gets stuck... Basicly the steps that are missing are adding a deployment descriptor and then the webapp.. I manually did it and it works.. the problem after that is that i need to execute sync.sh after i bounce the manage server or else i dont see the webapps under portal management..
So basicly the 2 questions are:
1..Why doesnt hot deploying work in unix using X11?
2.. Why do i need to execute sync.sh everytime after every bounce?
Thanks,
Oscar--
scott dunbar
bea systems, inc.
boulder, co, usa

JSF (RI) app hot-deploy memory leak

I have a standard JSF (RI) based web app that appears to be working just fine in terms of functionality. However, I believe that there is a memory leak associated with the sort of frequent hot-deploy cycles that are typical during a normal development cycle. I have been monitoring the app via the jvmstat 3.0 tools and have witnessed NO memory growth in the young or old generation areas - regardless of useage pattern. All of the growth seems to happen in the perm area of memory and be directly coincidental with the occurence of a deploy. Eventually, continued hot-deply cycles will result in an OutOfMemory error on the container - please note that continued and extensive use of the app WITHOUT the aforementioned hot-deploys does NOT result in the OutOfMemory error.
From my research so far, I have discovered the following thread:
http://forum.hibernate.org/viewtopic.php?t=935948&postdays=0&postorder=asc&start=75
It refers to a similar problem with hiberate (which I am NOT using) as well as a commons-logging and several others. From the looks of it, I strongly suspect that there may be an issue with JSF when it's implementation is bundled inside the WEB-INF/lib dir - i.e. inside the specific web app's ClassLoader.
Based on the above, I have implemented a SessionContextListener that invokes the org.apache.commons.logging.LogFactory.release() inside the contextDestroyed( ServletContextEvent e ) method. This does appear to free up some perm memory but there is still large growth that appears to be directly related to the FacesServlet initialization (navigation handlers, etc). I looked into calling the FacesContext.release() method which seems to have purpose similar to that of the LogFactory.release() method. However, at the time of the contextDestroyed() invocation, FacesContext.getCurrentInstance() always returns null, so I do not ever have an opportunity to invoke the release method that I am aware of. If my suspicions are correct, than I would likely be able to avoid this problem entirely by simply placing the JSF implementation jars in the conatiner's shared lib dir - instead of bundling it inside WEB-INF/lib. However, this is not an option for this container as multiple web apps (which require the flexibility to use differing JSF implementations and versions - i.e. RI vs MyFaces, etc) will run on this container.
I don't believe it is at all related to the problem at hand, but my container is JBoss 4.0.2.
Any and all assistance and suggestion will be greatly appreciated! Has anyone else seen this sort of behavior? Are there any work arounds or corrective actions?
TIA

Has anyone else run into this? I'd greatly appreciate any assistance as I cannot seem to resolve this hot-deploy related leak.

Hot deployment in WL 8.1

Hi All,
I am deploying the application from my development dir "c:\development" as
exploded for WAR file and EJB modules as JAR files. What should I do to make
the hot deployment work?
My environment is: Win XP, IDE is JBuilder(also use Eclipse3.0), Weblogic
8.1
When I was googling, it brought me the CLASS-LOADER article in bea docs and
I applied that making different nested class-loaders for EJB, WAR in one and
the EJB module which is under development in a separate class-loader. It did
not work. But I think there should be an easy way for hot deployment. If
there is any link that talks about this please let me know. Your response is
appreciated.
Thanks,
senthil

Also adding to that, the server is started in development mode.
"Senthil" <[email protected]> wrote in message
news:[email protected]...
I am not sure this a way to go for hot deployment. But what I did was
changing the application and weblogic-application.xml files.
My application.xml is like
===========application.xml===========
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE
Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>AppName</display-name>
<module>
<web>
<web-uri>Web</web-uri> 
<context-root>/</context-root>
</web>
</module>
<module>
<ejb>EJB1</ejb>
</module>
<module>
<ejb>EJB2</ejb>
</module>
</application>
=============END==========
weblogic-application.xml is given below
==============weblogic-application.xml==========
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-application PUBLIC "-//BEA Systems, Inc.//DTD WebLogic
Application 8.1.0//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic-application_2_0.dtd">
<weblogic-application>
<classloader-structure>
<module-ref>
<module-uri>EJB1.jar</module-uri>
</module-ref>
<classloader-structure>
<module-ref>
<module-uri>EJB2.jar</module-uri>
</module-ref>
</classloader-structure>
</classloader-structure>
</weblogic-application>
=========End===========
Thanks,
senthil
"Senthil" <[email protected]> wrote in message
news:[email protected]...
Hi All,
I am deploying the application from my development dir
"c:\development"
as
exploded for WAR file and EJB modules as JAR files. What should I do tomake
the hot deployment work?
My environment is: Win XP, IDE is JBuilder(also use Eclipse3.0),
Weblogic
8.1
When I was googling, it brought me the CLASS-LOADER article in bea docsand
I applied that making different nested class-loaders for EJB, WAR in oneand
the EJB module which is under development in a separate class-loader. Itdid
not work. But I think there should be an easy way for hot deployment. If
there is any link that talks about this please let me know. Your
response
is
appreciated.
Thanks,
senthil

Obaccess.dll causes link error on hot deploy

I'm doing web services development with AccessServerSDK 10G, Glassfish v3, on windows XP using Eclipse. It works fine except whenever I change my code and eclipse attempts to hot deploy the application, the following error occurs and the deploy bombs:
"org.apache.catalina.LifecycleException: org.apache.catalina.LifecycleException: java.lang.UnsatisfiedLinkError: Native Library C:\NetPoint\AccessServerSDK\oblix\lib\obaccess.dll already loaded in another classloader"
It seems that the obaccess.dll reloads without checking whether if it is already loaded. The only way to redeploy the application is to shutdown Glassfish and restart it for every change I make. It's impeding my progress.
So far I've tried the following:
--removing jobaccess.jar from inside my application and putting it into Glassfish_HOME/domain/domain1/lib; it didn't help.
--put an ObConfig.shutdown before the ObConfig.initialize; it didn't help.
--catching the exception and ignoring it, but then the application gets a null pointer exception when it runs.
I can't find anyone else in cyberspace complaining about this problem. I hope it isn't an issue with Windows because we do all our development on our desktops, but I wouldn't be surprised.
Anyone else having this problem or found a fix for it?

Hi,
I already faced with this problem on WLS11gR3 (10.3.4) and I try with all your workaround.
The solution I found was to install on separate server chain in order to reboot the server instead of use Hot Deploy.
We have also think to migrate the application to J2SE.
It seam that it is not possible to remove Jni 'till jvm is up and running.
Wile summer have you found any solution?

Obaccess.dll causes link error on hot deploys

I'm doing web services development with AccessServerSDK, Glassfish v3, on windows XP using Eclipse. It works fine except whenever I change my code and eclipse attempts to hot deploy the application, the following error occurs and the deploy bombs:
"org.apache.catalina.LifecycleException: org.apache.catalina.LifecycleException: java.lang.UnsatisfiedLinkError: Native Library C:\NetPoint\AccessServerSDK\oblix\lib\obaccess.dll already loaded in another classloader"
It seems that the obaccess.dll reloads without checking whether if it is already loaded. The only way to redeploy the application is to shutdown Glassfish and restart it for every change I make. It's impeding my progress.
So far I've tried the following:
--removing jobaccess.jar from inside my application and putting it into Glassfish_HOME/domain/domain1/lib; it didn't help.
--put an ObConfig.shutdown before the ObConfig.initialize; it didn't help.
--catching the exception and ignoring it, but then the application gets a null pointer exception when it runs.
I can't find anyone else in cyberspace complaining about this problem. I hope it isn't an issue with Windows because we do all our development on our desktops, but I wouldn't be surprised.
Anyone else having this problem or found a fix for it?

Hi,
I already faced with this problem on WLS11gR3 (10.3.4) and I try with all your workaround.
The solution I found was to install on separate server chain in order to reboot the server instead of use Hot Deploy.
We have also think to migrate the application to J2SE.
It seam that it is not possible to remove Jni 'till jvm is up and running.
Wile summer have you found any solution?

Previous unanswered Hot deploy of non EJB, non JSP classes

 Subject to my last post I've since seen my questions has appeared twice on this
 newsgroup, March 2001, and Nov 2000 and no responses to it those times. Aren't
 there BEA engineers reading this newsgroup who would know the answer to that question?
 http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=3776&utag=
 http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=5171&utag=


 Firstly I already did call BEA support before coming here, this is my last resort.
 I can't get a definitive answer from support. They were the ones that actually
 suggested to me that I post here in the first place. I did search the BEA edocs
 and couldn't find anything on it.
 Secondly, I am using WL 6.1 SP1, and in the thread just beneath this one, which
 I referred to directly in my opening post on this thread, I do mention this in
 the opening paragraph, in fact I give considerable detail.
 Thirdly, I never implied there was an onus on any BEA engineer to answer anything
 here. What I did mean was that given that they do read these posts and they do
 answer posts, I was merely a bit concerned that as I'm third person to ask, it
 would be strange to still get no response given that they answer other questions.
 I mean if they don't know, then who does? It's a real simple yes/no answer, it
 would take 5 seconds.
 Paul
 Robert Patrick <[email protected]> wrote:
 >
 >
 >The answer is simple -- move to WLS 6.x and use enterprise applications
 >(or web applications or an EJB jar file)
 >to package everything up into a single deployment unit and hot deploy
 >the whole deployment unit. WLS 5.1 and
 >earlier do not support hot deployment of non-servlet/non-JSP/non-EJB
 >classes.
 >
 >Mike Reiche wrote:
 >
 >> You can always call BEA Support - 1.888.232.7878 to get the help you
 >need. This
 >> newsgroup is not official BEA Support. It is out of the goodness of
 >their hearts
 >> that BEA engineers help people out here.
 >>
 >> I don't really think you wanted everyone that read your email and didn't
 >know
 >> if such a feature was available, to send you an email saying 'No, I
 >don't know
 >> if such a feature is available'. That's why there were zero responses.
 >>
 >> None of the posts you listed mention what version of WL. That makes
 >a difference.
 >> Also read the online documentation at edocs.bea.com, search for 'hot
 >deploy'.
 >>
 >> Mike Reiche
 >>
 >> "Paul H" <[email protected]> wrote:
 >> >
 >> >Subject to my last post I've since seen my questions has appeared
 >twice
 >> >on this
 >> >newsgroup, March 2001, and Nov 2000 and no responses to it those times.
 >> >Aren't
 >> >there BEA engineers reading this newsgroup who would know the answer
 >> >to that question?
 >> >
 >> >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=3776&utag=
 >> >
 >> >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=5171&utag=
 >
 >
 ><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 ><html>
 >The answer is simple -- move to WLS 6.x and use enterprise applications
 >(or web applications or an EJB jar file) to package everything up into
 >a single deployment unit and hot deploy the whole deployment unit.
 >WLS 5.1 and earlier do not support hot deployment of non-servlet/non-JSP/non-EJB
 >classes.
 >Mike Reiche wrote:
 ><blockquote TYPE=CITE>You can always call BEA Support - 1.888.232.7878
 >to get the help you need. This
 > newsgroup is not official BEA Support. It is out of the goodness
 >of
 >their hearts
 > that BEA engineers help people out here.
 >I don't really think you wanted everyone that read your email and
 >didn't
 >know
 > if such a feature was available, to send you an email saying 'No,
 >I
 >don't know
 > if such a feature is available'. That's why there were zero responses.
 >None of the posts you listed mention what version of WL. That makes
 >a difference.
 > Also read the online documentation at edocs.bea.com, search
 >for
 >'hot deploy'.
 >Mike Reiche
 >"Paul H" <[email protected]> wrote:
 > >
 > >Subject to my last post I've since seen my questions has appeared
 >twice
 > >on this
 > >newsgroup, March 2001, and Nov 2000 and no responses to it those
 >times.
 > >Aren't
 > >there BEA engineers reading this newsgroup who would know the answer
 > >to that question?
 > >
 > >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=3776&utag=
 > >
 > >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jsp&item=5171&utag=</blockquote>
 ></html>
 >
 >

Hot deployment and JMX

Similar Messages

Maybe you are looking for