- This topic has 4 replies, 2 voices, and was last updated 20 years, 10 months ago by
.
-
Posts
-
I’ve used Orion for several years, but have only recently been using it with MyEclipse.
Previously I used ant to build and hot-deploy by simply dropping the ear into an orion directory.
Occasionally, orion would stop hot-deploying . I’d do various things to wake it up again, i.e.
1. Start and stop it 3 or 4 times.
2. Stop it & yank out everything from my ear file that I could see, then start and stop it a few times.These tactics do not work consistently, and I have been unable to find a reliable test that reproduces the problem.
Now I use orion with myEclipse, instead of an ant build, and I’m getting more frequent unresponsive deployment behavior, to the point that I’m considering changing to another free appserver, in order to get less stressful deployment times.
My Questions
————–
1. Have other people had this problem of hot/auto deployment stopping??
2. Is there a workaround that works consistently ?
2. Is there a more reliable deployment combo, using another free appserver ?Bill.
Bill,
On your questions:
1) Yes, I’ve personally noticed the same issues with Orion 1.5.2 but don’t recall seeing them (yet) in 2.0. Which version of Orion are you using?2) I haven’t found a really good one. It is a bit irritating, but I don’t like Orion simply because it still can’t understand an exploded deployment.
3) For a free appserver, JBoss works quite well with both packaged and exploded deployments, IMO.
Scott, thanks for your reply.
I’m using Orion 2.0.1.
For what its worth, I’m not sure its all Orion’s fault. I also have to reboot MyEclipse on every debug cycle while I’m working on my current servlet. ME insists that there are no available and configured servers in the deploy dialog once a 500 Internal Server error comes out of Orion, even when Orion has been rebooted and is running other apps. Perhaps the orion module in ME has some state variables that go stale? Just a thought.
Nevertheless, the combo is not working, and I have to have a smoother cycle, so I’ll try JBoss.
Bill.
Bill,
I’ve opened a problem report referencing this URL so that our developers can investigate the problem you experienced with the deployment dialog. Thanks for taking the time to report it.
Bill,
I deployed an application that forced Orion 2.0.1 to generate a 500 error, but this had no adverse affect on my ability to deploy other applications on it. One thing to note is that the server won’t be listed if you already have an existing deployment on it for a particular application. That is, you can have only one active deployment at a time for a particular application on a particular server.
