[peterjb]

I’ve followed the guide to install my application in WAS 6 ( I’m running WAS 6.0.2.9 Base ). I’ve run into a problem where the JVM settings that I’ve set for the server definition in the MyEclipse profile don’t appear to being applied when I start the server from MyEclipse. In particular, I’m setting the JVM Min/Max Heap Size and some environment variables that influence the behaviour of my app when I’m in development mode.

When I start the server from the MyEclipse profile outside of MyEclipse, the JVM settings for my server have been applied.

[20/06/06 16:47:40:106 EST] 00000021 WebApp A SRVE0180I: [ICS] [/icsprnt] [Servlet.LOG]: ICSActionServlet: ObjectPoolThread: Initialising…
[20/06/06 16:47:40:121 EST] 00000021 WebApp A SRVE0180I: [ICS] [/icsprnt] [Servlet.LOG]: ICSActionServlet: ObjectPoolThread: Lightweight Mode Set…Starting in Lightweight mode.
[20/06/06 16:47:40:137 EST] 00000021 WebApp A SRVE0180I: [ICS] [/icsprnt] [Servlet.LOG]: ICSActionServlet: ObjectPoolThread: Configuration options: Minimum Reset Count: 10 Minimum Free Instances: 1

But When I start WAS6 from within MyEclipse, the console output and application/performance behaviour indicate that these settings have not been applied.

[20/06/06 16:58:06:610 EST] 0000000a WebApp A SRVE0180I: [ICS] [/icsprnt] [Servlet.LOG]: ICSActionServlet: ObjectPoolThread: Initialising…
[20/06/06 16:58:06:641 EST] 0000000a WebApp A SRVE0180I: [ICS] [/icsprnt] [Servlet.LOG]: ICSActionServlet: ObjectPoolThread: Configuration options: Minimum Reset Count: 10 Minimum Free Instances: 2
[20/06/06 16:58:06:688 EST] 0000000a WebApp A SRVE0180I: [ICS] [/icsprnt] [Servlet.LOG]: ICSActionServlet: ObjectPool: Initialising…

If I add -Xms256m -Xmx768m -DCMIDEBUG=ON -Dlightweight=True to the JDK parameters, then the application appears to at least startup identically both from within MyEclipse and native WAS6. My question is, what other WAS6 settings ( JVM or otherwise ) within the server definition are ignored by MyEclipse? And are they documented anywhere?

Cheers

Peter

[Riyad Kalla]

Peter,
Could you give me an example of the settings that you are trying to turn on that you aren’t having luck turning on from within MyEclipse? Also how you have tried to get them to work?

[peterjb]

No worries – From within the WAS6 Console I navigate to WAS Servers > Application Servers > server_name > Server Infrastructure > Process Definition > Java Virtual Machine.

I then set the following value And apply and save the Master configuration

Initial Heap Size : 256

Maximum Heap Size : 768

Generic JVM Arguments : -Dlightweight=true -DCMIDEBUG=ON

After stopping WAS6, when I look at the server.xml, the above values are set within it. When I start WAS6 from within MyEclipse, the log output shows that the server has not been started in lightweight mode nor is my debug working correctly. The speed ( or lack thereof ) of the application startup and the process memory allocation/usage are indicative that the Heap Size values have also not been applied.

However, when I specify the values as JDK parameters in the target configuration of MyEclipse – It works correctly.

Cheers

Peter

[Riyad Kalla]

Hrrm, I know our connectors circumvent startup scripts because they launch the process directly, but I’ll double check if the server.xml file is being ignored as well or if that’s an oversight. In the mean time you *are* doing the right thing by setting them manually in the JDK options.

[Author]

Posts