I am experiencing unusual behavior with a Websphere 5 installation. We have a few components deployed in both EJB and Web containers.
We also have a few components that are standalone Java applications that are run from a command-line via Perl script. These standalone programs are executed with the Websphere JRE. In other words, the command-line contains the full path to the JRE within the Websphere directory structure.
This seems like an awkward design, in my opinion. Are there any issues with this design? Does the IBM Websphere JRE have any specific code that will cause potential problems or issues when running standalone applications, e.g. security, classloading, etc.? Or, will executing the standalone programs this way have any effect on the operation of the Web and EJB modules deployed in the application server?
Thanks. Any feedback is greatly appreciated. [ May 16, 2008: Message edited by: James Clark ]
I don't think this is a huge problem in itself. I mean, you do need a JRE to run client applications, and the IBM jre is as good as any, right?
A hard coded path does bother me a bit. You could always configure a variable and refer to that. That would obfuscate the path, but if it's all running on a trusted server, it may be a bit of work without much value.
I think you're good, until you move that application off the server on which it is running.
PERL and Java? You're nuts!
Joined: Apr 16, 2008
I am just investigating the IBM JRE and trying to see it there are any differences in behavior when running Java programs that are not deployed in the containers and not managed by the application server. In particular, the classloading process of bootstrap, extensions, application and web classloaders. Also, any security constraints related to code not deployed in the application server.
There are no issues with the hard-coded path in the Perl. I mentioned it to detail what I meant by standalone applications executing the application server's JRE.
Maybe I'm barking up the wrong tree. Doesn't hurt to investigate though. The issues we have encountered are related to queue listener's shutting down unexpectedly and the web application shutting down.