Solution : https://service.sap.com/sap/support/notes/1126202 (Connexion à SAP Service Marketplace requise)
Mots Clés :
sf patch collection pc-1 minimum kernel patch level, java instance stopped processing http requests, sf patch collection pc-4solves, sf patch collection pc-5solves, sf patch collection pc-6solves, sf patch collection pc-7solves, sf patch collection pc-8solves, sf patch collection pc-9solves, sf patch collection pc-10solves, sf patch collection pc-11solves
Notes associées :
| 1436491 | Startup Framework patch collection PC-14 |
| 1430975 | Startup Framework patch collection PC-13 |
| 1412139 | Setting the Java stack size for AS Java 7.10 and newer |
| 1387621 | Startup Framework patch collection PC-12 |
| 1374098 | Startup Framework patch collection PC-11 |
| 1374096 | AS Java (JEE Engine) may fail to restart during deployment |
| 1350481 | Startup Framework patch collection PC-10 |
| 1350357 | Web sessions may be closed unexpectedly |
| 1337857 | Java callstack not available after server crash |
| 1295212 | Startup Framework 7.1 patch collection PC-9 |
| 1288859 | Startup Framework 7.1 patch collection PC-8 |
| 1271342 | Startup Framework patch collection PC-7 |
| 1266733 | IPv6 support in Java Startup Framework |
| 1237612 | Java server process: deployment fails |
| 1160072 | Startup Framework patch collection PC-4 |
| 1125091 | CST patch collection 50 2007 |
| 1123337 | Java servers may hang in garbage collection |
| 1115331 | CST Patch Collection 47 2007 |
| 1114588 | Java servers may hang on JSOLWESE after a server restart |
| 1114284 | Java servers may show "no valid license" after JVM crash |
| 1084930 | Java servers may hang on SF-SeMnt aven after restart |
| 1081201 | SAP Start Service may crash when fetching a Java callstack |
| 1081072 | Java instance fails due to corruption in shared memory |