application crashed when using JCo library 3.1.x to to establish the SNC connection
Article ID: KB0073926
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | 7.2.x, 8.x |
Description
If debugging the core file and backtrace the error, following message could occur: Core was generated by `<tibo_home>/adapter/adr3/7.2/bin/adr3 --run --propFile /usr/tibco/devset'. Program terminated with signal 11, Segmentation fault. #0 0x00007f15bac8147d in ?? () (gdb) backtrace #0 0x00007f15bac8147d in replace_dollarparam(name_value_tupel*, int, int) () from /usr/tibco/devsetb/tibco_cfg/JCOLib/libsapjco3.so According to SAP Note 558250. This could be due to the stack size for the Java application that using the JCo library is too small. The initial JCo version works with the Java default stack size, but over time the native code could change significantly. In JCo version 3.1.x, the native code change could lead to use larger stacks, which eventually could be too large for the default stack size.
Issue/Introduction
application crashed when using JCo library 3.1.x to establish the SNC connection
Environment
Linux System
Resolution
To resolve this issue, try to double the application's stack size until the issue is resolved.
To set the stack size in TIBCO ActiveMatrix® Adapter for SAP, add the following TRA property in the application's tra file and set: java.thread.stack.size
The default value for the stack size varies on different platforms. Try starting with 512k which should be big enough on most platforms.
To set the stack size in TIBCO ActiveMatrix® Adapter for SAP, add the following TRA property in the application's tra file and set: java.thread.stack.size
The default value for the stack size varies on different platforms. Try starting with 512k which should be big enough on most platforms.
Additional Information
https://launchpad.support.sap.com/#/notes/558250
Feedback
Yes
No
Powered by
