Re: [Opaltoolkit-users] Problem reloading opal

[Luca C. <lcl...@uc...>]

Sriram Krishnan wrote:
> Hi Anthony,
> 
> I looks like you may have some old Opal classes from a previous
> version lying around - basically because it can't find the
> JobManagerType, which should be in the latest Opal jar.
> 
> There are two solutions to this problem. If you run "ant uninstall-
> all", it will go ahead and clean up all the old Opal jars from inside
> Tomcat. However, if you do this, all your deployed Opal services will
> be gone. You will have to install Opal again, and manually deploy them
> one by one.
> 
> The second option is you shut down tomcat, and run "ant upgrade". This
> should replace the old Opal jar with the new one, along with other
> prerequisite jars. I would try this option first, restart Tomcat and
> see if everything works. If it doesn't, you may have to try the brute
> force approach, which is option one.
> 
> Thanks, and let us know if that works.
> 
> Sriram

Hey,
my previous email wasn't very clear.... but I did some testing on 
stopping and restarting Opal webapp using tomcat manager interface.

For some reason it doesn't work (problem with log4j, and axis for some 
reason doesn't find mapping in the classpath), so at the moment it is 
not possible to stop and restart a Opal webapp.
At the moment you need to restart tomcat.

As soon as I get a chance I will take a look at this problem.


Sincerely,
Luca