amitscjoshi

 Profile Answers by amitscjoshi 

• Mar 9th, 2006

 

Ya. Don't run that in Debug mode...

amitscjoshi

 Profile Answers by amitscjoshi 

• Mar 9th, 2006

 

I guess ,it's mostly the memory issue.

Raju

• Mar 17th, 2006

 

My application running very------Slow----- while Websphere is debug mode

if you problem?can you help ?

Raju

thulasi

• Mar 30th, 2006

 

Keep on removing logs from the following directory, then we can work on debug mode

..\.metadata\.plugins\com.ibm.etools.server.core\tmp0\tranlog\server1\transaction\tranlog\log1

and

 ..\.metadata\.plugins\com.ibm.etools.server.core\tmp0\tranlog\server1\transaction\tranlog\log2

rc

• Sep 10th, 2006

 

u need to increase the memmory allocated to java process in WAS. In WASD deployement description there is a setting for java process memmory allocation. Increase the -Xmx values in it and see if thst works for you.

It worked for me.

Good luck

James Samuel

• Oct 27th, 2006

 

You need to bump the heap size memory default is 0,0 Enable adminstative console in the wsad in the server settings I believe its configuration tab or environment . And logon to the adminconsole on port 9090 when u start the server in normal modehttp://localhost:9090/admin. Then go to server/ server1/process definition/JVMIncrease the initial heap and maximum heap size in there.. Give atleast (512MB,1.5Gb) And restart the server in debug modeIts should work. It worked for me