Is there any other way to get around you propose for this scenario ?Because we dont want to redeploy the Static.ear,as it runs in production environment on a 24*7 basis.
Hi Hari, Another way to round this problem would be to set up a kind of secondary server. You should assign the client to send the requests to this server always when the primary server is not available. If you want to deploy a new JAR into the primary server, you should deploy the old JAR into the secondary server. Now you can re-start the primary server and do the re-deployment. 24*7 service should be guaranteed because the requests are targeted to the secondary server while the primary server is re-starting. I have not tested this kind of solution, but I don't see any reason why it should not work out. Best, Erno Lindfors [EMAIL PROTECTED] View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946637#3946637 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3946637 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
