SAP Basis Tech Supports

Symptom

List of Corrections for SP04 of the NW701 (EhP1) Application Server Java

Other terms

J2EE Engine, WebAs Java, NW701 SPS04

Reason and Prerequisites

List of Corrections for NetWeaver AS Java between NW7.01 SPS03 and the NW701 SPS04.

Solution

J2EE Core
Kernel
-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.
-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 failing during installation, upgrade or deployment caused by java.lang.NoClassDefFoundError which doesn’t fail after a restart of the cluster element
J2EE Services
AdminAdapter
-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. See also Note 1286323.
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 were missing. In other words no traces were written from the specified logging locations despite the fact the E2E tracing had been enabled. After this fix is applied the EndToEnd scenario will work properly. See also Note 1277477.
Connector
-Fix the association of JDBC, JMS or JCA connections with correct JTA transaction. See also Note 1303595.
CCMs
-Fix 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.
Deploy
-Improved logging in J2EE Engine – reducing logs in Deploy.
-Prevent NullPointerExceptions and file descriptor leak. See also Note 1265978.
DBPool / JDBC Connector
-Fixed deployment of datasources as library SDA. See also Note 1292762.
-Clearing unnecessary log statements from system logs.
-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.
DSR
-This fix changes the way the DSR service constructs the name of the DSR components. If the component name is longer than the 32 characters limit, the hostname of the machine the system is running on gets truncated. First the service tries to remove the domain part of the hostname. If such does not exist (does not take part in the hostname), the last characters of the hostname itself are removed so the whole DSR component name fits into the 32 characters limit. Before this change the customers that have very long hostnames on their systems see just a single DSR output directory despite the fact they have multiple server nodes. This causes the DSR data to get corrupted and the E2E trace not to work. After this change is applied a separate output directory will be created for each server node which allows the DSR data to be stored properly and the E2E trace to work. See also Note 1276299.
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 does 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.
-Performance improvement in http response compression. See also Note 746666.
IIOP
-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.
-Fix iiop request ids leak and possible hang in SAP iiop Delegate.getNewRequestId() method. See also Note 1291446.
-Fix IIOP performance/CPU problem in connection lost event during high connections load. See also Note 1287486.
-Fix 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.
JDO
- Reduced memory consumption. Before the fix a user performing memory profiling or analyzing a heap dump could see a set called _quries in a JDBCStoreManager object containing a large amount of entries. In some cases many of these entries can point to Queries not contaning any queryResults, these should be eligeble for garbage collection. After the patch a user can now see a set called _openQueryResults now containing only queryResults that are still open and in use. If the user code closes queryResults on time this set will be sufficently small.
JMS Provider
-Enabled E2E trace analysis integration of the SAP JMS Provider. See also Note 1292779.
-Clearing unnecessary log statements from system logs
-JMS service can now start even if there are invalid users in the Administrators role. See also Note 1272372.
J2EEDocs
-Change the product name to SAP NetWeaver Application Server Java on the start page.See also Note 1295447.
JMX
-The “CacheFillRate” monitor’s value was not updated in VA. See also Note 1285780.
Keystore
-Improved logging in j2ee runtime. Fixed incorrect logs, replaced with traces.
-Fixes SSO problem when the keystore authorization check does not correctly evaluate the protection domain stack. See also Note 1280840.
Log Viewer
-issue with 7.00 SAPControl usage for AGS scenario “LV in SMD”
-Log Viewer client was unable to connect to a remote Log Viewer Stand Alone server via a SAP Router.
Monitor
-Make possible to configure separate thresholds for the System thread pool monitors of the Dispatcher and Server nodes. See also Note 1298554
-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 the change the customer sees a NPE (with no meaning) in the defaultTrace.trc file, after applying this fix a proper error message would be displayed in the trace file. See also Note 1267874.
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.
Security
-Improved logging in J2EE Engine. The severities of the traces produced by security session management have been lowered from INFO to PATH and DEBUG.
-Fix in permissions deleting from Protection Domain tab in Visual Administrator. See also note 1303551.
-Fixed a deadlock in the Security service. See also note 1301056.
-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.
-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.
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 import of a user with user mapping will fail. See also Note 1292510.
UME Api
-During every logon the user has to change his password. See also Note 1291409.
-All services depending on the Guest user fail. See also Note 1287884.
-A security information is not shown in the default traces after this fix. See also Note 1273212.
-Users can not download the UME configuration zip archive, when they execute command:
java -jar /usr/sap//JC /j2ee/cluster/server/bin/services/com.sap.security.core.ume.service/com.sap.security.core.ume.service.jar /usr/sap//JC. See also Note 1276071.
Web Container / Servlet_JSP
-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.
-When parsing JSP pages, which contain custom tags in html comments/javascript jsp parser produced 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.
Webservices
-Logging cleanup – too much logs on startup

Tools
ConfigTool
-Enabled E2E trace analysis integration of the SAP JMS Provider. See also Note 1292779.
SDM
-System copy or the execution of createsdmkitjar SDM command fails with invalid entry size. The problem is caused by the limitation in the JAVA API for zip entries of size larger than 0xFFFFFFFF bytes. This limitation is avoided by packing the repository in several jar files based on the provider name of the components. See also Note 1169806.
-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
-The task status bar in Visual Administrator is reset to 0% if a connect to the Engine fails. See also Note 1309524.