topic Re: Any bugs in java1.5.0.03 which crashes JVM at system bootup in Operating System - Linux

Any bugs in java1.5.0.03 which crashes JVM at system bootup

madhavabk — Mon, 21 Aug 2006 02:37:18 GMT

Hi All,

I am working with java1.5.0.03 version.
My application is registered to start at system boot up. As per application the application starts and produces PID information in logs.
But within few seconds it will be killed by JVM signal.

So are there any bugs in java1.5.0.03 version where we need to take care of some things.

The application starts with out any problem when i start it after reboot using same startup script.

Thanks,
Madhava

Re: Any bugs in java1.5.0.03 which crashes JVM at system bootup

Steven E. Protter — Mon, 21 Aug 2006 03:42:08 GMT

Shalom,

Yes there are bugs.

1) Make sure all patches recommended for the OS at http://www.hp.com/go/java are installed. Java will install without them, but it won't run well.
2) Make sure the box has been performance tuned in advance.
3) Make sure a recently bi-annual patch installation is installed.
4) Go with the latest JVM fromt he go/java site above that your application environment will tolerate.

SEP

Re: Any bugs in java1.5.0.03 which crashes JVM at system bootup

madhavabk — Mon, 21 Aug 2006 05:40:29 GMT

Hi Steven,

I hope my system is up with all required patches and also it has quality packs.

But what difference in environment required by JVM makes it different for application to run and fail during system boot up and run properly when it is already booted up?

Thanks,
Madhava

Re: Any bugs in java1.5.0.03 which crashes JVM at system bootup

V. Nyga — Mon, 28 Aug 2006 08:26:08 GMT

Hi Madhava,

some error messages from syslog or rc.log would be nice for us to be able to say more.
If you use a startup script as a user, you have defined search pathes, lib pathes and more. So it's hard to say without more informations, what's wrong with the application start.

Maybe you have to include pathes from your login to the start script (/etc/PATH, /etc/SHLIB_PATH).

Your startup script or error messages would help.

Volkmar