on 03-13-2014 3:31 PM
Hi All,
We have SAP xMII version 12.1 SP 10 installed on Windows 2003 server upon SAP Netweaver 7.1 EHP1.
MII Application gets connected to SQL database of version 2000.Application was running fine on this server for the past two years.
There are no recent changes to application functionality in the past few months.
Two weeks back, memory consumption under "Java System Reports" shoots up to almost 100%. Due to which application performance is very slow, we end up with restarting MII services to make application up and running. This issue happened thrice in the last two weeks.
We checked NWE logs and system logs, could not find any appropriate errors.
we are unable to find out why the memory comsumption went high? All the existing jobs are running fine.
Kindly help us to resolve the issue.
Thanks
S.Rajesh
Hi Rajesh
kindly check the follow thing before get in to the SAP application area.
1. In Windows 2003 server under the task manager you can find the which process taking more resource?
2. All the windows 2003 drivers, & Service pack updates are up to date?
3. In windows event viewer any error message?
4. Is this any page memory low ?
Regards
Sriram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
we have SAP xMII 12.1.9 installed onWindows 2003 SP2 x64, Intel xeon 2,40GHz and 16 GB RAM, .
MII gets connected to Microsoft SQL Server 2005.
The problem is the process jstart.exe. This process actually get 5,7 GB RAM when the xMII services start. We havent jobs running and we have not uers connected to MII.
5,7 GB of Memory this is normal for this process?
Thanks in advance,
Cristian C.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
To analyse more you can generate thread dump for culprit <PID> , jlaunch process.
Please, add below two parameters to server<X> node, then reboot the
system.
-XX:+UseCMSInitiatingOccupancyOnly
-XX:+GCHistory
-XX:+GCHistory will write detailed GC information to a file named
"sapjvm_gc.prf" in the server working directory. It allowes to
analyze GC behavior in case of problems. And this has no impact
to performance.
-XX:+UseCMSInitiatingOccupancyOnly instructs the CMS to start only
when the Java heap is filled up to 80%.
Hope it helps
BR Vaibhav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rajesh,
With regards to your query as Deepak has asked please provide details about the swap, ram & DB.
Was anything changed in MII before this issue came. Was any parameters got changed at OS, DB or application which resulted in the issue.
Check out the reason why the load increased, is the some reports causing issue, users causing issue.
Regards,
Deepanshu Sharma
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rajesh
Kindly refer the SAP links for Garbage collection
https://help.sap.com/saphelp_nwce10/helpdata/en/8f/7cfac9b978416cb2e3423c96817f75/content.htm
https://help.sap.com/saphelp_nwce10/helpdata/en/5f/d99052023d414aa1dc6aec5c806360/content.htm
Regards
Sriram
Hi Rajesh,
1) What is the database of MII system
2) How much swap is configured ?
3) How much RAM is configured on the Windows Server ?
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.