• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • paul wheaton
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
  • Himai Minh
Bartenders:

OC4J Question

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All!
I have a J2EE Application (App.ear), that often change. For every deploy I stop and start the app server (OC4J).
There is any risk if I adopt the "HOT DEPLOYMENT"?
(The application contain EJB, Servlet ecc.).

Thanks in advance, Veri.
 
Sheriff
Posts: 9109
12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hot deploy works just fine most of the time, but it is safer to restart oc4j.
 
author
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi. Based on my experience most deployments go fine, but sometimes wierd things do happen. If you have the time I'd do a stop/start. I'll also say I've had fewer problems on 10gAS (9.0.4) than 9iAS V2 (9.0.2). I'd recommend creating separate OC4J instances for each application. Sometimes things do get hosed up and I have to delete and OC4J instance and redeploy. That's not common but it has happened.

Thanks,
Mike
reply
    Bookmark Topic Watch Topic
  • New Topic