| |
Results |
|
Intermittentt Deadlocks in SSM with Java caches
|
Intermittentt Deadlocks in SSM with Java caches
|
|
|
|
Cannot create java stubs using wsimport command
|
Cannot create java stubs using wsimport command
|
|
|
|
Now that Oracle will charge for Java, what is the impact on SBM (SSM and SRC and RLC) customers?
|
Now that Oracle will charge for Java , what is the impact on SBM (SSM and SRC and RLC) customers?
|
|
|
|
Error when starting the Application Engine: Unable to initialize ALF SSO library: 'Error while creating JVM: 'Not enough memory to load JVM''
|
Error when starting the Application Engine: Unable to initialize ALF SSO library: 'Error while creating JVM : 'Not enough memory to load JVM ''
|
|
|
|
A service step with Dynamic endpoints can use excessive JVM memory
|
A service step with Dynamic endpoints can use excessive JVM memory
|
|
|
|
Performance, Java Bridge Init exception on x64, with very large database ( large cache )
|
Performance, Java Bridge Init exception on x64, with very large database ( large cache )
|
|
|
|
Intermittent Deadlock in SSM with Java caches - [error] ajp_service::jk_ajp_common.c (2799): (worker2) connecting to tomcat failed (rc=0, errors=1597, client_errors=26)
|
Intermittent Deadlock in SSM with Java caches - [error] ajp_service::jk_ajp_common.c (2799): (worker2) connecting to tomcat failed (rc=0, errors=1597, client_errors=26)
|
|
|
Contents
|
Known Issues for Supported Web and Application Servers 1. The following minimum standards are required to use the SBM Web tier: Oracle Java Run Time Environment ( JRE ) 1.8+ Servlet API Version 2.3+ JSP API Version 1.2+ SOAP Version 1.1 or 1.2 HTML Version 4.0+ JavaScript Version 1.3+ 2. JRE versions 1.7.0 and earlier are not supported.
|
|
|
|
How to enable SBM to communicate via SSL with a SQL Server database
|
The current versions of SBM will fail to connect to to the SQL Server database even after updating the JDBC connection strings. The issue is related to changes made to Oracle's JRE 1.6 update 29+ which is the version used in SBM 10.1 and higher. The change was made to fix the SQL Server "Beast" security issue.
|
|
|
|
Failed to load JNIBridge
|
This can be caused by the msvcr71.dll not being found in the "C:\Program Files\Serena\SBM\Common\ jdk 1.6\ jre \bin\server" directory. To work around this issue, copy the "C:\Program Files\Serena\SBM\Common\jdk1.6\jre\bin\msvcr71.dll"
|
|
|
