auto deploy do not work in weblogic 6.1 ?

[deepa karkala]

Hi everyone, I am facing a problem in my weblogic 6.1 that whatever ejb componet I am deploying (after modification) to the weblogic server, the changes are not getting reflected if the server is running. Each time, I have stop the server and start it and then only the changes done in ejb is getting reflected.
I am not setting startmode while starting the server. So by default it is false means ie., the server is running in devlopment mode.

Does this problem exist if we do not have proper Service Pack ? Does this problem exist in hight version of weblogic ?
thank you in advance.

[Ashish Pagare]

If you have added the ejb jar in your admin/managed server classpath then hot deployment will not work.
If order to utilize hot deployment you have to just target the ejb application to your managed server.
Regards.

[deepa karkala]

Hi Ashish,
I have only one server in the domain for the development and I have targeted the ejb component to this server. This server will also work as admin server. The OS is HP-UNIX. The service pack is 5.
I do not know why the server will not realize the changes I do in the ejb when it is running.
After copying the ejb component to the respective directory under domain, I will have to stop and start the server and then only the niw changes will appear. BTW, I have not added any EJB jar files in the classpath.
thanks.

[Ashish Pagare]

You mentioned that you are copying the ejb jar to the respective directory under domain. Can you be more specific on which directory you are lacing your directory.
To utilize hot deployment you need to place your ejb jar in "DOMAIN"/applications folder.
Other way to refresh your ejb's is to delete them in the admin console and redepoly then witout restarting the server.

[deepa karkala]

You are exactly right. I am placing the EJB jars under domain/applications/myproject. Since it is under applications, the auto deploy should work as per what is given in the BEA manual.
But it is not happening.
When we use ant utility to deploy the jar files to the weblogic domain/applications directory as we compile, it is not adviced to go to console each time and do the deploy right ?
thanks.

[Ashish Pagare]

I checked BEA doc for ejb hot deployment and it mentions hot deployment works only for files in applications folder. Nothing is mentioned about the recursive nature of hot deployment from the sub directories inside applications folders (I presume you are using jar file and not exploded directory structure).
Can you please try to put your jar right in the applications folder and try it out once. Make sure that to avoid any confusion/conflict first delete the existing ejb app from the console and then try.
Yeah I know using console is not suggested with hot deployment but when things doesn't work the way you want you need to try all voodoo things
In our app we are putting simple uncompiled ejb jar in the applications folder. Are you compiling the jar first with ejbc compiler and then putting the compiled jar in applications folder? Never mind this is not going to make any difference.

[deepa karkala]

Hi Ashish, as you suggested, I placed the ejb jar file directly under the domain/applicaions directory. Still, if I make some changes in the EJB, it will not be refleced if the server is running. But if I stop the server and start, immediately the change will be reflected which indicates that the autodeploy is not working at all.
BTW, I am placing compiled jar which contains stubs and skeleton for the EJB.
thanks.

[L Duperval]

Doesn't hot deployment require you to be in Development mode (instead of production mode)?
L