| Author |
Message
|
| dipankar |
 Posted: Mon Dec 17, 2007 5:34 am Post subject: java.lang.StackOverflowError - Insufficient Java stack size |
 |
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
Hi All,
AIX, WBI MB, mySAP 6.0.3
Sometime I am getting the following error in connector_manager_SAP.log.old file -
| Quote: |
java.lang.StackOverflowError: JVMXE018: Insufficient Java stack size
at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeExecute(Native Method)
at com.sap.mw.jco.rfc.MiddlewareRFC$Client.execute(MiddlewareRFC.java(Inlined Compiled Code))
at com.sap.mw.jco.JCO$Client.execute(JCO.java(Compiled Code))
at com.sap.mw.jco.JCO$Client.execute(JCO.java(Compiled Code))
at com.crossworlds.connectors.sap.rfcservermodule.SapRfcServerConnectorAgent$Server.updateIdocStatus(SapRfcServerConnectorAgent.java(Compiled Code))
at com.crossworlds.connectors.sap.rfcservermodule.SapRfcServerConnectorAgent$Server.onConfirmTID(SapRfcServerConnectorAgent.java(Compiled Code))
at com.sap.mw.jco.rfc.MiddlewareRFC$Server.nativeListen(Native Method)
at com.sap.mw.jco.rfc.MiddlewareRFC$Server.listen(MiddlewareRFC.java:1368)
at com.sap.mw.jco.JCO$Server.listen(JCO.java:6805)
at com.sap.mw.jco.JCO$Server.run(JCO.java:6734)
at java.lang.Thread.run(Thread.java:570) |
However it seems adapter is running, polling is also working. I have seen all these through connector trace file. I did not get any error message in connector log or trace file. But SAP system is unable to register through SM59 transaction
I have set Xss value to 1024k (previously it was not there) in adapterEnv.sh file and decreased the MaxNumberOfConnector value to 7 from 10.
Still getting the same issue once in a week.
Can anyone please advise me how to solve this?
_________________
Regards |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Dec 18, 2007 1:41 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
This happens when ever an infinite recursion occurs...
are you using any CHILD BO hierarchy here...
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| dipankar |
| Posted: Tue Dec 18, 2007 10:57 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
Hi,
Yes, we have child BO hierarchy. FYI, every sunday we recycle the adapter. We got this error generally on Friday or Saturday. After recycling, first 4/5 days adapter is running well. After that we got this error.
I noticed after increasing MaxNumberOfConnctor from 5 to 10, we got this error.
So I have again changed that to 5 now and set Xss value to 2m. What do you say here?
_________________
Regards |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Dec 18, 2007 11:21 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
Any reasons why you maximised the number of connections here..
then i will state my point here...
MaxNumberOfConnctor from 5 to 10: if you make like this, the resource shortage may happen here (infinite recursion occurs as you said there are child BO's).
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| k_usa |
| Posted: Tue Dec 25, 2007 6:18 pm Post subject: |
|
|
Apprentice
Joined: 14 Aug 2006
Posts: 42
Location: NewJersey
|
Hi, we were using mySAP 6.0.4 , SAPJCO2.1.6 with Adapter framework 2.6.0.11 with WMB 6 as broker.
We got the similar error in production. And it is coming once in every 3 days.
I have raised a PMR with IBM and they have recomended us to upgrade the mySAP adapter to 6.0.8 and sapJCO to 2.1.8.
I have also increased the JvmMaxHeapSize to 1024MB.
we will be implementing this in production soon. I will let u know if this is going to solve this problem.
we are using the MaxNumberOfConnections as default vaule 1. |
|
| Back to top |
|
|
| dipankar |
| Posted: Sun Jan 27, 2008 9:46 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
Hi Gayathri,
| Quote: |
| MaxNumberOfConnctor from 5 to 10: if you make like this, the resource shortage may happen here (infinite recursion occurs as you said there are child BO's). |
I got the following error
JCO_ERROR_RESOURCE; Message: Connection pool SAPConnector_ConnectionPool_<date> is exhausted. The current pool size limit is <n> connections.
That's why I increased the MaxNumberOfConnector. Anyway I have reverted back to 5.
However I am still getting the same error
Hi k_usa,
| Quote: |
| we will be implementing this in production soon. I will let u know if this is going to solve this problem. |
Please let me know your result.
_________________
Regards |
|
| Back to top |
|
|
|
|
