Hi Herr Helmut Arnold, Chris Pollach & All
Earlier I had similar kind of discussion on this forum with Herr Helmut Arnold & Chris Pollach on below thread and their suggestion worked to nail the issue perfectly, but the recent issue seems to be memory issue but different than earlier. I tried all the ways to tweak the HeapSize, Statck Size etc to fix it but there have been hardly any help as the tweaking of the JVM parameters just helped to update extra few more records but no solution yet.
EAServer 6.3.1 compatible with JDK 1.7[EBF 20852 6.3.1 ESD #6 Support jdk1.7]?
ISSUE:
Info About the Product & Build:
Sybase Enterprise Application Server 6.3.1.07 [nt386] Build
(63107.19926)Developer Edition.
PowerBuilder 12.5.2 Build 5006
Easerver installed on Windows Server 2008 6.1 (x86)(64-bit Operating System), 6GB RAM
We have a PB & Easerver component application migrated to PB 12.5.2 & EAServer 6.3.1 which runs on JDK 1.7.
Web request through SOAP UI inserts\updates the records calling PB methods through stub.
All goes well but the call request fails after updating near about to 600 records in db printing the log stated below which seems to be specific to memory leakage what I come to know through various post on forums and my earlier discussions gathered on this forum.
2014-10-08 11:20:16.017 INFO RMI TCP Accept-0 [ConsoleOutput] okt 08, 2014 11:20:16 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAcceptLoop
2014-10-08 11:20:16.017 INFO RMI TCP Accept-0 WARNING: RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=55271] throws
2014-10-08 11:20:16.017 INFO RMI TCP Accept-0 java.lang.OutOfMemoryError: unable to create new native thread
2014-10-08 11:20:16.017 INFO RMI TCP Accept-0 at java.lang.Thread.start0(Native Method)
2014-10-08 11:20:16.017 INFO RMI TCP Accept-0 at java.lang.Thread.start(Thread.java:691)
2014-10-08 11:20:16.017 INFO RMI TCP Accept-0 at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:943)
2014-10-08 11:20:16.017 INFO RMI TCP Accept-0 at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1336)
2014-10-08 11:20:16.017 INFO RMI TCP Accept-0 at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:402)
2014-10-08 11:20:16.017 INFO RMI TCP Accept-0 at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:359)
2014-10-08 11:20:16.017 INFO RMI TCP Accept-0 at java.lang.Thread.run(Thread.java:722)
2014-10-08 11:20:24.019 INFO RMI TCP Accept-0 [ConsoleOutput] okt 08, 2014 11:20:24 AM sun.rmi.transport.tcp.TCPTransport$AcceptLoop executeAcceptLoop
2014-10-08 11:20:24.019 INFO RMI TCP Accept-0 WARNING: RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=55271] throws
2014-10-08 11:20:24.019 INFO RMI TCP Accept-0 java.lang.OutOfMemoryError: unable to create new native thread
2014-10-08 11:20:24.019 INFO RMI TCP Accept-0 at java.lang.Thread.start0(Native Method)
2014-10-08 11:20:24.019 INFO RMI TCP Accept-0 at java.lang.Thread.start(Thread.java:691)
2014-10-08 11:20:24.019 INFO RMI TCP Accept-0 at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:943)
2014-10-08 11:20:24.019 INFO RMI TCP Accept-0 at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1336)
2014-10-08 11:20:24.019 INFO RMI TCP Accept-0 at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:402)
2014-10-08 11:20:24.019 INFO RMI TCP Accept-0 at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:359)
2014-10-08 11:20:24.019 INFO RMI TCP Accept-0 at java.lang.Thread.run(Thread.java:722)
The above logs get printed on call failure of web service. Log also prints the memory check to critical level after thread failure:
2014-10-08 14:20:00.018 INFO ScheduledTask:Dump60SecondMemoryUsage [CheckMemoryUsageTask] Java virtual memory usage: 23% (114/124/494 Mb)
2014-10-08 14:20:00.018 INFO ScheduledTask:Dump60SecondMemoryUsage [CheckMemoryUsageTask] Process virtual memory usage: 98% (2019/2047 Mb)
I googled to know some details on the error java.lang.OutOfMemoryError: unable to create new native thread and found several forums where this JVM issue seems to be general on all the platform and most of the people faced it, but they were all for Unix, linux etc but no were for EAServer6 as of now. So thought to post it here and find if someone might have come across the same issue.
For ref on the error below are some links that might be usefull w.r.t JVM\JDK. Below link has several suggestions on JVM\JDK
DevGrok: Resolving OutOfMemoryError: unable to create new native thread
Eagerly waiting for some suggestion and help on this running issue.
Regards,
Kunal