Re: [Soaplab-users] new and improved applab

[Mahmut U. <ul...@eb...>]

Hi Sirisha,

> Wonderful! I have just run a data-intensive workflow that always 'broke' 
> the applab server and it has completed successfully all the way through 
> for the first time! I am going to do a few more runs this afternoon to 
> make sure, but preliminary results look good :)

I carbon copy this message to the group in order to encourage people to
use the new version of applab jar file.

> One thing I would like to do is check the heap usage after running a 
> certain number of jobs

I use jconsole for this purpose. The last line of the run-Applab-server
script should normally be the following line.

java -Dcfg=Server.cfg -mx856m Server Applications.xml "$@"

If you add the "-Dcom.sun.management.jmxremote" option to this line
Applab should next time start with JMX support.

java -Dcfg=Server.cfg -Dcom.sun.management.jmxremote -mx856m Server
Applications.xml "$@"


After restarting Applab server with JMX support if you start jconsole it
will automatically detect the Applab process with JMX support and then
you can easily monitor heap usage and other characteristics of the
Applab process.

Regards,
Mahmut


> > Hi Sirisha,
> > 
> > Changes in the run-Applab-server script updates the CLASSPATH for the
> > Applab server but the deployment mechanism has its own definition of
> > CLASSPATH.For the other mechanisms use, such as the deployment
> > mechanism, you can keep the previous 4 jar files together with the
> > applab.jar file in the Soaplab lib directory.
> > 
> > Since you update the CLASSPATH in the run-Applab-server script it will
> > not use the previous 4 jar files but will use the new applab.jar file
> > but the other mechanism will continue to use the previous jar files.
> > 
> > Actually it is best to change CLASSPATH definition in all places. I will
> > look at this and will email to the group about this.
> > 
> > Please let me know if anything is not clear or not working.
> > 
> > Mahmut
> > 
> > 
> > 
> > On Fri, 2006-11-03 at 13:20 +0000, Sirisha Gollapudi wrote:
> >> I've just realised, the class not found error seems to be something to 
> >> do with AppLabShare which I had deleted both the jar file and reference 
> >> to the jar file in run-applab-server script...
> >>
> >> Mahmut Uludag wrote:
> >>> Hi Sirisha,
> >>>
> >>>> - with the improved Applab server - is it sufficient to simply 
> >>>> kill my current server, replace the 4 jar files you mentioned in the 
> >>>> previous post with the new "applab.jar" and then restart the 
> >>>> server/redeploy my services?
> >>> No need to redeploy the services, restarting should be enough.
> >>>
> >>> If you use the run-AppLab-server script please make sure you delete the
> >>> following 4 lines,
> >>>
> >>> CLASSPATH=SOAPLAB_HOME/lib/adaptors.jar:{CLASSPATH}
> >>> CLASSPATH=SOAPLAB_HOME/lib/AppLabClient.jar:${CLASSPATH}
> >>> CLASSPATH=SOAPLAB_HOME/lib/AppLabServer.jar:${CLASSPATH}
> >>> CLASSPATH=SOAPLAB_HOME/lib/AppLabShare.jar:${CLASSPATH}
> >>>
> >>> and add the following line instead.
> >>>
> >>> CLASSPATH=SOAPLAB_HOME/lib/applab.jar:${CLASSPATH}
> >>>
> >>> Developer version of the run-AppLab-server does have a generic mechanism
> >>> for building the CLASSPATH so it doesn't need to have the above change.
> >>> I think you are probably not using the developer version of the script.
> >>>
> >>> Regards,
> >>> Mahmut