Re: HOT deployment ??
Helllu, noc noc... Can someone please help me with the problem I did send a few days ago ?? I like to hear how Linux users correctly deploy their J2EE applications, and the problems the are having with this ? Eddie - Original Message - From: "Eddie" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Tuesday, July 10, 2001 2:45 PM Subject: HOT deployment ?? > I still don't understand when my changes are NOT picked up ?? > During development I don't have a ear file, I just have a dir with all the > classes/xml files. > Untill now, when I change something in an EJB class, I have to stop orion, > delete the deployment dir en start again > Why like this ?? As if I do it the other ways, like: > + using the admin.jar tool, something like: java -jar /opt/Orion/admin.jar > ormi://localhost admin pass -deploy -file > /opt/Orion/applications/sgs.ear -deploymentName sgs > + touching the xml files in the META dir (the orion signals an update). > + Removing the deployment dir during operation... it gives "Java Exception: > Broken pipe errror..." > > If I do it like above it ofter occurs that it doesn't pick up my changes. > Also when I replace a class that is not part of the EJB's, which it loaded > during runtime, it still keeps on using the old class... what am I doing > wrong It can't believe that is can't be done more simple!!?? > > BTW: when I do a: > ++ java -jar /opt/Orion/admin.jar ormi://localhost admin pass -restart, I do > get: > -- > Recovery completed, 0 connections committed and 0 rolled back... > Orion/1.5.1 initialized > > Restarting... > Error starting JMS-Server: Unable to bind socket: Address already in use > Error starting RMI-Server: IO Error: Address already in use > - > > ++ The shutdown command does work however. > > So please some advices on what I am doing wrong, and how I should do it (do > I needs to change some JVM settings ??). > I am running RedHat 7.0. > > Eddie >
Re: Hot deployment
- Original Message - From: "Daniel Lopez" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Friday, March 30, 2001 8:20 AM Subject: Re: Hot deployment > Hi Marcel, > > You're right, I had already tried that and it didn't work. On the other > hand, I tried to pack my .war inside a .ear and everything worked. Of > course that adds another directory and another file to be created but > it's something I can cope with ;). Touching the application.xml file > works fine but I was hoping that auto-detection of new .war files would > be as easy as .ear files, that way a simple ftp with the new war file is > enough but that's not a problem. > > Another question, when I perform a hot deployment, all the sessions are > lost. Is there any way I can keep the sessions alive? I mean is there > any setting to persist the sessions across deployments? Yes and as far as I kow orion is by default configured to do this (it works for me). Look at the tags in orion-web.xml and orion-application.xml . > > Thank you for your help, > Dan > --- > Daniel Lopez Janariz ([EMAIL PROTECTED]) > Web Services > Computer Center > Balearic Islands University > ---
Re: Hot deployment not so hot
I'd suggest something a little less radical first... go into the orion-ejb-jar.xml file in your deployment directory and make sure that your updates were reflected there. In particular, make sure that Orion not only added what you did, but that it removed what you did. Orion seems to, thankfully, be pretty conservative about changing the deployed descriptors. If you don't have anything in there that you care about (custom mappings, finders, whatever...), then you could just nuke that file, touch the orion-application.xml to redeploy, and you should be golden. Rian - Original Message - From: [EMAIL PROTECTED] To: Orion-Interest Sent: Friday, March 30, 2001 6:46 AM Subject: Re: Hot deployment not so hot When we had similar problems we would remove the application from the application directory, the ear and the files from the applications-deployment directory. Make sure you stop the server before doing this. Jonathan BrickerLilly Research LabsJava ATG Dan North <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 03/30/2001 06:13 AM Please respond to Orion-Interest To: Orion-Interest <[EMAIL PROTECTED]> cc: Subject: Hot deployment not so hotHi all.I've been having a number of problems with hot deployment ever since I started using orion, and I wondered if anyone could shed any light?Typically it happens when I change an interface rather than just internal bean logic or code: orion says it is redeploying whatever-xyz.jar, but will complain that:- A cmp-field is missing (that I have removed from both the bean and the ejb-jar.xml)- A method doesn't exist (that I have just added to both the bean and the remote i/f)- etc.All the messages I get seem to come down to a conflict between some cached version of the bean and the new version. If I shut down and restart orion, all the problems go away and it deploys the new version fine.This hasn't been a problem during development, but I'm concerned that I might be doing something wrong, and obviously once the system goes live I can't just stop and restart the server when I deploy changes, so what's the Right Way to redeploy a session or entity bean into a running server and tell orion to forget everything it knew about the previous version?(I'm running 1.4.7 on Sun's jdk1.3 on Windows 2000 if it makes any difference.)Thanks,Dan/tastapod--Dan NorthVP Development - Cadrion Software Ltd - +44 (0)20 7440 9550CONFIDENTIALITYThis e-mail and any attachments are confidentialand may also be privileged. If you are not the named recipient,please notify the sender immediately and do not disclose thecontents to another person, use it for any purpose, or storeor copy the information in any medium
Re: Hot deployment not so hot
Unfortunately, this is exactly my problem - I will soon be in a situation where "stop the server" will not be an option :o) I'm looking for a way to force orion to completely discard any knowledge it has of a particular bean and redeploy from scratch. Thanks, Dan/tastapod At 09:46 30/03/2001 -0500, you wrote: >When we had similar problems we would remove the application from the >application directory, the ear and the files from the >applications-deployment directory. Make sure you stop the server before >doing this. > >Jonathan Bricker >Lilly Research Labs >Java ATG > > >Dan North <[EMAIL PROTECTED]> >Sent by: [EMAIL PROTECTED] > >03/30/2001 06:13 AM >Please respond to Orion-Interest > > To:Orion-Interest <[EMAIL PROTECTED]> > cc: > Subject:Hot deployment not so hot > >Hi all. > >I've been having a number of problems with hot deployment ever since I >started using orion, and I wondered if anyone could shed any light? > >Typically it happens when I change an interface rather than just internal >bean logic or code: orion says it is redeploying whatever-xyz.jar, but will >complain that: > >- A cmp-field is missing (that I have removed from both the bean and the >ejb-jar.xml) >- A method doesn't exist (that I have just added to both the bean and the >remote i/f) >- etc. > >All the messages I get seem to come down to a conflict between some cached >version of the bean and the new version. If I shut down and restart orion, >all the problems go away and it deploys the new version fine. > >This hasn't been a problem during development, but I'm concerned that I >might be doing something wrong, and obviously once the system goes live I >can't just stop and restart the server when I deploy changes, so what's the >Right Way to redeploy a session or entity bean into a running server and >tell orion to forget everything it knew about the previous version? > >(I'm running 1.4.7 on Sun's jdk1.3 on Windows 2000 if it makes any >difference.) > >Thanks, >Dan/tastapod > >-- >Dan North >VP Development - Cadrion Software Ltd - +44 (0)20 7440 9550 > >CONFIDENTIALITY >This e-mail and any attachments are confidential >and may also be privileged. If you are not the named recipient, >please notify the sender immediately and do not disclose the >contents to another person, use it for any purpose, or store >or copy the information in any medium > > > -- Dan North VP Development - Cadrion Software Ltd - +44 (0)20 7440 9550 CONFIDENTIALITY This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose, or store or copy the information in any medium
Re: Hot deployment not so hot
When we had similar problems we would remove the application from the application directory, the ear and the files from the applications-deployment directory. Make sure you stop the server before doing this. Jonathan Bricker Lilly Research Labs Java ATG Dan North <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 03/30/2001 06:13 AM Please respond to Orion-Interest To: Orion-Interest <[EMAIL PROTECTED]> cc: Subject: Hot deployment not so hot Hi all. I've been having a number of problems with hot deployment ever since I started using orion, and I wondered if anyone could shed any light? Typically it happens when I change an interface rather than just internal bean logic or code: orion says it is redeploying whatever-xyz.jar, but will complain that: - A cmp-field is missing (that I have removed from both the bean and the ejb-jar.xml) - A method doesn't exist (that I have just added to both the bean and the remote i/f) - etc. All the messages I get seem to come down to a conflict between some cached version of the bean and the new version. If I shut down and restart orion, all the problems go away and it deploys the new version fine. This hasn't been a problem during development, but I'm concerned that I might be doing something wrong, and obviously once the system goes live I can't just stop and restart the server when I deploy changes, so what's the Right Way to redeploy a session or entity bean into a running server and tell orion to forget everything it knew about the previous version? (I'm running 1.4.7 on Sun's jdk1.3 on Windows 2000 if it makes any difference.) Thanks, Dan/tastapod -- Dan North VP Development - Cadrion Software Ltd - +44 (0)20 7440 9550 CONFIDENTIALITY This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose, or store or copy the information in any medium
Re: Hot deployment
Hi Marcel, You're right, I had already tried that and it didn't work. On the other hand, I tried to pack my .war inside a .ear and everything worked. Of course that adds another directory and another file to be created but it's something I can cope with ;). Touching the application.xml file works fine but I was hoping that auto-detection of new .war files would be as easy as .ear files, that way a simple ftp with the new war file is enough but that's not a problem. Another question, when I perform a hot deployment, all the sessions are lost. Is there any way I can keep the sessions alive? I mean is there any setting to persist the sessions across deployments? Thank you for your help, Dan --- Daniel Lopez Janariz ([EMAIL PROTECTED]) Web Services Computer Center Balearic Islands University --- Marcel Schutte wrote: > > I'm having the same problem as Daniel. It's not a matter of touching or > recreating the .war. Daniel wrote that he tried that already. > > For me, the automatic redeployment of .ear files works fine. Whenever I > overwrite the .ear file, orion starts redeploying right away. However, when > I make my .war part of the global-application by editing the following line > in /config/application.xml: > > > > orion doesn't redeploy my web application when I overwrite the .war. > Instead, I have to restart the server for it to pick up the changes. > > > > Just occurred to me that perhaps touching the file > /config/application.xml would trigger redeployment. And indeed it > does, problem solved. > > Marcel > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Mike > > Cannon-Brookes > > Sent: Thursday, March 29, 2001 4:02 PM > > To: Orion-Interest > > Subject: RE: Hot deployment > > > > > > Touch the .war file or recreate it - Orion will detect that > > and redeploy it. > > If not, check your date settings etc. Sometimes one machine (if you're > > deploying across a network) may have a different clock to another. > > > > -mike > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]]On Behalf Of > > Daniel Lopez > > > Sent: Thursday, March 29, 2001 8:22 PM > > > To: Orion-Interest > > > Subject: Hot deployment > > > > > > > > > Hi, > > > > > > I've been using Orion for a while and so far, so good. Now > > I'm trying to > > > improve the way we develop/deply applications and I started > > to digg in > > > the .war file world. I've created the war file containing > > just the web > > > application and it's been auto-unpacked and auto-deployed > > succesfully, > > > great! Now I wanted to check what are the steps that I need > > to follow in > > > order to deploy a new version of an application. Re-creating the war > > > file and substituting it seems not to affect Orion and it's not > > > detecting a new version. I even tried to remove the > > deployed application > > > directory to see if it would re-unpack it from the new war > > file but it > > > didn't work either. So, what am I missing? Do I need to > > create the full > > > .ear file blah, blah so hot-deployment works? As I don't > > use EJB, I was > > > thinking about just using a plain .war file with just the web > > > application. Is that the problem? > > > Thank you very much in advance, > > > regards > > > Dan
RE: Hot deployment
I'm having the same problem as Daniel. It's not a matter of touching or recreating the .war. Daniel wrote that he tried that already. For me, the automatic redeployment of .ear files works fine. Whenever I overwrite the .ear file, orion starts redeploying right away. However, when I make my .war part of the global-application by editing the following line in /config/application.xml: orion doesn't redeploy my web application when I overwrite the .war. Instead, I have to restart the server for it to pick up the changes. Just occurred to me that perhaps touching the file /config/application.xml would trigger redeployment. And indeed it does, problem solved. Marcel > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Mike > Cannon-Brookes > Sent: Thursday, March 29, 2001 4:02 PM > To: Orion-Interest > Subject: RE: Hot deployment > > > Touch the .war file or recreate it - Orion will detect that > and redeploy it. > If not, check your date settings etc. Sometimes one machine (if you're > deploying across a network) may have a different clock to another. > > -mike > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of > Daniel Lopez > > Sent: Thursday, March 29, 2001 8:22 PM > > To: Orion-Interest > > Subject: Hot deployment > > > > > > Hi, > > > > I've been using Orion for a while and so far, so good. Now > I'm trying to > > improve the way we develop/deply applications and I started > to digg in > > the .war file world. I've created the war file containing > just the web > > application and it's been auto-unpacked and auto-deployed > succesfully, > > great! Now I wanted to check what are the steps that I need > to follow in > > order to deploy a new version of an application. Re-creating the war > > file and substituting it seems not to affect Orion and it's not > > detecting a new version. I even tried to remove the > deployed application > > directory to see if it would re-unpack it from the new war > file but it > > didn't work either. So, what am I missing? Do I need to > create the full > > .ear file blah, blah so hot-deployment works? As I don't > use EJB, I was > > thinking about just using a plain .war file with just the web > > application. Is that the problem? > > Thank you very much in advance, > > regards > > Dan > > --- > > Daniel Lopez Janariz ([EMAIL PROTECTED]) > > Web Services > > Computer Center > > Balearic Islands University > > --- > > > >
RE: Hot deployment
Touch the .war file or recreate it - Orion will detect that and redeploy it. If not, check your date settings etc. Sometimes one machine (if you're deploying across a network) may have a different clock to another. -mike > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Lopez > Sent: Thursday, March 29, 2001 8:22 PM > To: Orion-Interest > Subject: Hot deployment > > > Hi, > > I've been using Orion for a while and so far, so good. Now I'm trying to > improve the way we develop/deply applications and I started to digg in > the .war file world. I've created the war file containing just the web > application and it's been auto-unpacked and auto-deployed succesfully, > great! Now I wanted to check what are the steps that I need to follow in > order to deploy a new version of an application. Re-creating the war > file and substituting it seems not to affect Orion and it's not > detecting a new version. I even tried to remove the deployed application > directory to see if it would re-unpack it from the new war file but it > didn't work either. So, what am I missing? Do I need to create the full > .ear file blah, blah so hot-deployment works? As I don't use EJB, I was > thinking about just using a plain .war file with just the web > application. Is that the problem? > Thank you very much in advance, > regards > Dan > --- > Daniel Lopez Janariz ([EMAIL PROTECTED]) > Web Services > Computer Center > Balearic Islands University > --- >
