SAP Basis Tech Supports

Symptom

You want to know which changes have been done in SAP Netweaver04 Application Server – Java Stack 24.

Other terms

J2EE Engine, WebAs Java, Stack24, SPS24

Reason and Prerequisites

List of Corrections for the SAP NetWeaver AS Java 6.40 between stack 23 and Stack 24

Solution

J2EE CORE
Kernel:
- Improved logging in j2ee runtime cluster communication
- Fixed J2EE aplication hang during startup on SAP J2EE server running over IBM jdk and com.sap.engine.core.configuration location tracing switched on DEBUG. See also Note 1266076.
- Ensure reuse of J2EE threads with the original thread name. Fix of J2EE thread name infection by previous thread usage. See also Note 1265613.
- Fixed failing during installation, upgrade or deployment caused by java.lang.NoClassDefFoundError which doesn’t fail after a restart of the cluster element. See also Note 1271266.
- Performance improvement in http response compression. See also Note 746666.
- Before the command lsp did not have any parameters and showed only the PORT and PROTOCOL. Now the command has the parameter -force which causes the command to output the IP, PORT and PROTOCOL. See also Note 1286323.
- Fixed a program error in scenarios that try to add a non-String property in a property sheet in configurations. See also Note 1291166.
- Fixed deployment of datasources as library SDA. See also Note 1292762.

J2EE Services
Apptracing
- The SAP Passport (End-to-End) tracing did not work properly. After enabling the End-to-End (E2E) trace, setting the “trace” flag to “High” and specifying a set of logging locations that should write traces disregarding their severity, the expected log traces are missing. In other words no traces are written from the specified logging locations despite the fact the E2E tracing has been enabled. After this fix is applied the EndToEnd scenario will work properly. See also Note 1277477.
Connector
- Enhanced error message for wrong configuration of ManagedConnectionFactory during startup. See also Note 1265054.
Deploy
- Improved logging in deploy service
DBPool / JDBC Connector
- Empty sqljdbc.jar is deployed for Microsoft JDBC Driver version 1.2 for MSSQL Database. With the fix the sqljdbc.jar is deployed with its original length and content. See also Note 1282288. Temporary files in /temp/dbpool are now deleted after successful deployment.
- Clearing unnecessary log statements from system logs
- Fixed deployment of datasources as library SDA. See also Note 1292762.
File
- Fixed possible NullPointerException when createRemoteFile() method is used passing a relative path to the local file that does not start with “.”. For example “test.txt” instead of “./test.txt”. Prevented leakage of file descriptors.
Http
- In landscape: browser -> HTTPS -> webdispatcher -> HTTPS -> icm -> J2EE, where webdispatcher is SSL terminator (it extracts client certificate from browser and puts it in http header) , login with SSL client certificate did not work. The reason was incorrect handling of ICM certificate sent to J2EE server. ICM certificate was discarded, although J2EE option ProxyServersCertificates was configured with correct DN of ICM client certificate. After the fix this scenario works as expected. See also Note 1244255.
IIOP
- Fixed MARSHAL exception while processing iiop message from IBM java provider. Problem appears while SAP ORB implementation receive and unmarshal some CORBA objects in fragmented message. The initial problem was found when sender is IBM jdk 150 SR7. The result of problem is MARSHAL exception (sometimes caused by ArrayIndexOutOfBoundsException) on SAP side. See also Note 1282671.
- Fixed iiop request ids leak and possible hang in SAP iiop Delegate.getNewRequestId() method. See also Note 1291446.
- Introducing a new iiop ORB’s methods create_abstract_interface_tc and create_recursive_tc functionality required for IBM 142 SR13 JDK. See also Note 1306760.
- with IBM 142 SR13 IBM started to use create_abstract_interface_tc and create_recursive_tc ORB methods. This change is a part of the implementation of them in our ORB. See also Note 1306760.
JMS Provider
- Improved tracing when receive is called on a JMS queue session with negative timeout for identification of the faulty caller. See also Note 1255910.
- Fixed synchronization issue in the JMS client layer that lead to stopping of JMS message receipt. See also Note 1256636.
- JMS service can now start even if there are invalid users in the Administrators role. See also Note 1272372.
- Cleared unnecessary log statements from system logs
- Enabled E2E trace analysis integration of the SAP JMS Provider. See also Note 1292779.
Keystore
- Improved logging in j2ee runtime. Fixed incorrect logs, replaced with traces
- Fixed SSO problem when the keystore authorization check does not correctly evaluate the protection domain stack. See also Note 1280840.
Monitor
- Changed the way JARM history is aggregated and written in the DB. Before this fix is applied the aggregations performed by the Monitoring service were incorrect and thus the data in the DB was incorrect. See also Note 1236776.
- When the customer tries to install a custom monitor with wrong threshold values, a NPE is logged instead of the expected proper error message. Before this change the customer sees a NPE (with no meaning) in the defaultTrace.trc file, after applying this fix a proper error message will be displayed in the trace file. See also Note 1267874.
- Make possible to configure separate thresholds for the System thread pool monitors of the Dispatcher and Server nodes. See also Note 1298554.
HeartBeat
- Additional logging statements have been added. Before this change almost no traces were written by the Heartbeat application, after the change is applied the application will write extensive trace records when the severity of the “com.sap.engine.heartbeat” logging location is set to “Debug”. Extended the checks for JMS availability to check for correctness of the returned message. See also Note 1279661.
SAPJ2eeCcmsCustomizing
- Fixed management of the properties of the J2EE monitors through CCMS. Before this change the properties of the J2EE dispatcher monitors could not be changed, after the fix is applied it will be possible to maintain the properties of the J2EE dispatcher monitors. See also Note 1140146.
P4
- Improved logging in p4 service
- Fixed already opened rmi_p4 service connections to survive temporal system TCP performance problem on the dispatcher. See also Note 1265617.
SSL
- Prevented delays about 200 ms during the ssl handshake.
Security
- Sometimes after an installation some services such as the keystore and the jms service fail to start because of a deadlock. As a result they are unusable. After a restart of the server the defaultTrace.X.trc files are filled with entries such as “Role KeystoreAdministrator is missing”. If the role is created manually, another restart fixes everything.
- You have an authentication stack and you want to have the first login module authenticate the user while some (or all) of the rest of the login modules to confirm this user’s identity. A new feature has been added so that only the user admitted by the first login module will be able to complete the authentication process. See also Note 1269616.
- The security audit logs have been separated from the other security logs. They can no longer be found in the security.log file (in …/cluster/serverX/log/system) but in the security_audit.log file (in …/cluster/serverX). See also Note 1278155.
- Fixed a bug which caused the authentication stack of an application to be changed after redeployment even though it had previously been modified manually in the Visual Administrator. See also Note 1277341.
- Fixed a bug that caused a deadlock in the Security service. See also Note 1301056.
- Fixed deleting of permissions from Protection Domain tab in Visual Administrator. See also Note 1303551.
- Fixed security information not to be shown in the default traces.
WebContainer / Servlet JSP
- When parsing JSP pages, which contain custom tags in html comments/javascript jsp parser would produce unexpected result if tags were named with relative names like this: tagName and tagNameLonger. In such pages tag tagName would be used instead of tagNameLonger. After the fix the correct tag will be used. See also Note 1250666.
- Improved logging in Web Container Service. Events about init and destroy of servlets will be logged with severity PATH instead of INFO and will not be visible by default. Invokations of method javax.servlet.ServletContext.log(java.lang.String) will no longer produce enties in the applications.log by default. In order to log these invokations you need to set the severity of category /Applications/WebApplications to PATH. See also Note 1298829.
WebServices
- Downporting Reverse Proxies from 7.11 to 640 and 7.01
- 630_SP_COR use WSLogging.applyConfiguration and WSLogging.removeConfiguration instead of apployAndStoreConfiguration and removeAndStoreConfiguration
- 630_SP_COR remove several unused methods clone()
- Fixed webservice access problems
- Logging cleanup – too much logs on startup
Tools
SDM
- Improvement in the configuration of the login timeout (socket timeout) specified by the SDM Client API during connection. A new property defaultSDMTimeout is introduced, which changes the default timeout for the client. If there is no custom login timeout specified with ClientSessionFactory.setLoginTimeout() and the property is set in SDMClient.properties, it is used when a connection to the SDM is established. See also Note 1144877.
- When the deployment of an SCA fails and the deployment is canceled, the deployed SDAs were not shown in the undeployment tab. Fixed updating the component tree in the undeployment tab when the deployment is canceled.
Visual Admin
- Fixed session expiration on navigation between different managers and services in Visual Admin. See also Note 1266562.
- Previously the command lsp did not have any parameters and showed only the PORT and PROTOCOL. Now the command has the parameter -force which causes the command to output the IP, PORT and PROTOCOL.