Novell
exteNd Application Server

5.2.1 RELEASE NOTES

March 2005

Welcome to Novell^® exteNd^TM Application Server (Version 5.2.1). These release notes include the following sections:

Important note about 5.2.1 documentation	Where to find information about Version 5.2.1 of Novell exteNd
Installing exteNd Application Server	How to prepare for installing the Novell exteNd Application Server
J2EE compatibility	Information on the J2EE compatibility of the Novell exteNd Application Server
Novell product compatibility	Information on compatibility between the Novell exteNd Application Server and other Novell products
System requirements	Software and hardware needed to run the Novell exteNd Application Server features
Supported databases	Database types and versions supported by the Novell exteNd Application Server
What's new in 5.2	New features in Version 5.2 of the Novell exteNd Application Server
What's new in 5.2.1	New features in Version 5.2.1 of the Novell exteNd Application Server
Upgrade notes	Server changes that may affect you when upgrading to the latest version
Documentation updates	Updates to the documentation for the Novell exteNd Application Server
Known issues	Known problems with this version of the Novell exteNd Application Server
Problems fixed in Version 5.2	Problems that have been fixed in 5.2, including problem numbers
Problems fixed in Version 5.2.1	Problems that have been fixed in 5.2.1, including problem numbers

Release note updates   To check for updates to these release notes, click here.

Important note about 5.2.1 documentation

Documentation specific to the 5.2.1 maintenance release of exteNd is provided in the product release note files:

• exteNd Suite Release Notes
• exteNd Director Release Notes
• exteNd Composer Release Notes
• exteNd Application Server Release Notes (which you are reading now)

These files include:

• Directions for upgrading to 5.2.1
• Descriptions of new features
• Added information about some existing features

The other exteNd help and PDF files are still primarily at the 5.2 level; they have not been updated to reflect 5.2.1 product changes (except where noted).

Installing exteNd Application Server

For a complete guide to installing the exteNd Application Server and the exteNd 5 Suite, see Installing Novell exteNd in the exteNd 5 Suite help.

J2EE compatibility

This version of the Novell exteNd Application Server is compatible with Java 2 Platform, Enterprise Edition 1.3 (J2EE 1.3).

To learn the details about J2EE compatibility, see the J2EE Compatibility Web site hosted by Sun at java.sun.com/j2ee/compatibility.html. It lists products that are certified to be J2EE compatible, explains how they are tested, and describes the benefits of ensuring J2EE compatibility.

Novell product compatibility

To learn about compatibility between the Novell exteNd Application Server and other Novell products:

1. Go to the Novell support Web site: support.novell.com

2. See the following document:

   Document title	Solution ID
   exteNd Application Server on NetWare	NOVL87857

System requirements

This section describes the software and hardware needed to run these product features:

• Novell exteNd Application Server
• SilverJ2EEClient
• UDDI Services

Novell exteNd Application Server

System requirements for the server environment are listed in the exteNd Suite Release Notes, which also includes information on:

• Web Server Integration (WSI) modules
• Server Management Console (SMC)

SilverJ2EEClient

SilverJ2EEClient is the J2EE application client container for the Novell exteNd Application Server. The SilverJ2EEClient installers are available for download at developer.novell.com/ndk/j2eeclient.htm. After downloading, copy the installers to the Novell exteNd AppServer\Resources\SilverJ2EEClientInstall directory on your application server host machine.

This version of the application server does not support access by earlier versions of SilverJ2EEClient; you must use the current version of SilverJ2EEClient. The current version of SilverJ2EEClient cannot access earlier versions of the application server.

Novell has a two-tier approach to platform support for SilverJ2EEClient:

Tier	Description
1	The platforms for which Novell tests and supports SilverJ2EEClient, and provides installers: Windows Solaris Linux
2	The platforms for which SilverJ2EEClient should work but that Novell will not test. They include: NetWare If you encounter a problem trying to use SilverJ2EEClient on these platforms, Novell will attempt to fix it; but the problem is likely VM-related and beyond the control of Novell. SilverJ2EEClient installers for these platforms are not provided.

To run SilverJ2EEClient, you must have the following hardware and software installed:

Component	Description
Java 2 JRE	Installed with SilverJ2EEClient
Minimum RAM (memory)	40 MB and up for SilverJ2EEClient (in addition to memory required for OS and other applications)
Minimum disk space (if installed alone)	50 MB, including the JRE

UDDI Services

You can add UDDI (Universal Description, Discovery, and Integration) capabilities to the application server by using UDDI Services. This facility is a lightweight edition of the Novell Nsure UDDI Server that comes with its own lightweight LDAP server. It supports Web Service development by providing a UDDI 2.0 test registry where you can publish and find components (using Novell exteNd Director™ or Novell exteNd Composer™) before production (when you can publish to the Novell Nsure UDDI Server).

UDDI Services is implemented as a J2EE Web application that you deploy to the application server. Everything you need to deploy UDDI Services is provided in the application server's UDDI subdirectory, along with deployment instructions and other UDDI Services documentation. The UDDI subdirectory and its files are copied to your file system during the Novell exteNd Application Server install.

Note that the exteNd Suite also contains a separate copy of the same lightweight LDAP server for test and tutorial purposes. If you run both at the same time, you may have conflicts.

Supported databases

Database types and versions supported by the Novell exteNd Application Server are listed in the exteNd Suite Release Notes.

What's new in 5.2

For information about new 5.2 features, see What's New in the application server's help.

What's new in 5.2.1

This section describes the new features of the exteNd Application Server for 5.2.1:

client_throttle_size property for performance tuning

The following property has been added to the application server's httpd.props file to help you tune performance:

   http-server.com.sssw.srv.http.client_throttle_size=0

This property specifies the server's HTTP client-request throttle size (the maximum number of HTTP client requests that can be run concurrently). The default is 0, which disables the throttle (same as before this performance enhancement was added).

The client_throttle_size property can help reduce Java lock contention on objects that are read/written by multiple Java threads. You might start with a setting of 24, then increase or decrease to see the effect on performance.

The reason you may need to throttle concurrency in HTTP request handling is that, in high thread/load environments, the Java scheduler can be unfair; it randomly picks the next thread to get a lock, even though this may be the same thread that just had the object lock previously. Threads that have been waiting several seconds for access to the lock may wait while other threads get the lock repeatedly.

Java applications that do not share objects between Java threads will not be helped by this property. Most Java applications do share objects between Java threads. (PPR 48543)

nocheckcase parameter for tuning LDAP login performance

SilverServer now provides a new optional startup parameter to help you tune login performance for an LDAP security provider:

   +Dsssw.ldap.nocheckcase

By default, when a user logs in through the application server for the first time, a search of all users in the context is performed to check for the correct case of the username. This search can be very expensive in a large environment, resulting in slower login performance. By specifying the nocheckcase startup parameter, you can prevent the username case check and associated search. (PPR 48793)

poolsize parameter for Dispatcher performance tuning

The Dispatcher (SilverDispatcher) now provides a new optional startup parameter to help you tune performance:

   +Dnovell.dispatcher.poolsize=NNN

You can use this parameter to change the client pool size (default is 50). For example, to set the client pool size to 100:

   SilverDispatcher [other parameters] +Dnovell.dispatcher.poolsize=100

When traffic is very heavy and end users get errors hitting the Dispatcher, try using this parameter to increase the pool size. (PPR 48515)

Support for SMC help on Linux

In the SMC (Server Management Console), you can display help by selecting Help>Help Topics or pressing F1. If you use the SMC on Linux, SMC help requires one of the following browsers in order to display:

• Firefox
• Mozilla
• Netscape
• Opera

Make sure that the browser's executable is on your path. (PPR 45181)

Upgrade notes

This section lists server changes that may affect you when upgrading to the latest version.

• Rebranding
• J2EE
• Database
• Configuration
• General
• Legacy

Rebranding

As of Version 5.0, this product is branded Novell exteNd Application Server. Earlier versions were branded SilverStream^® eXtend Application Server. If you are upgrading from one of those earlier versions, note that the following changes have been made for the product's rebranding:

• Default install directory   When the application server is installed on Windows, the default install directory is C:\Program Files\Novell\exteNdn\AppServer. (It used to be C:\Program Files\SilverStream\eXtendAppServer.)

  When the application server is installed on UNIX or Linux, the default install directory is /opt/novell/exteNdn/AppServer. (It used to be /opt/silverstream.)

• Program group   When the application server is installed on Windows, the following program group is created: Novell exteNd n.n>AppServer. (It used to be SilverStream eXtend>AppServer n.n.)

• Environment variables   When the application server is installed on Windows, an environment variable is created (for use by sample applications) to point to the server product directory. This environment variable used to be named SILVERSTREAM_HOME. It is now NOVELL_EXTEND_APPSERVER_HOME. (SILVERSTREAM_HOME is still provided in this release, but it is deprecated.)

  When the application server is installed on UNIX or Linux, the environment file .agprofile is created to set environment variables that the server needs at runtime. The environment variable that points to the server's root location is named EXTENDAPPSERVERROOT. (It used to be SILVERSTREAMROOT.)

• Database drivers   The SilverStream JDBC-ODBC bridge driver is now the Novell exteNd JDBC-ODBC bridge driver. The SilverStream Oracle drivers are now the Novell exteNd Oracle drivers. (Note that these drivers are deprecated.)

• SMC   The SMC used to be the SilverStream Management Console but is now the Server Management Console.

• Command-line options   Some of the startup options you can specify on the command line for server executables (SMC, SilverCmd, SilverJ2EEClient) have been renamed. Specifically, all options that used to start with -ss_ now start with -as_. For example, -ss_password is now -as_password. (The -ss_ option names are still supported in this release, but they are deprecated.)

• Server startup options for EJB debugging   The SSSWEJBDebug server startup option is now EJBDebug. The SSSWEJBDebugName server startup option is now EJBDebugName.

• EJB deployment plan   In the DTD (XML document type definition) for the EJB deployment plan, the element nonSSSWPersistenceInfo has been renamed to externalPersistenceMgr.

• Deployment plan in archive   When you create a J2EE archive for deployment to the application server, you have the option of storing the deployment plan inside that archive. If you do, the deployment plan must be named appserver.xml. (It used to be silverstream.xml.)

• Directory for temporary files during deployment   If you have a HOME environment variable defined, the SilverCmd deployment commands (such as DeployEAR) store temporary files in the %HOME%\.appsrv directory. (This directory used to be named %HOME%\.silverstream.)

• Security realm string   The application server's security realm string now defaults to Silver Security. This string is displayed in the server login dialog. It is also passed on the WWW-Authenticate response header sent to the client.

  If you want to change the security realm string, you can now use the property com.sssw.srv.http.authHeaderRealm in the httpd.props file. (Previously, this string was set to SilverStream and you couldn't change it.)

• What's not changed   Several aspects of the application server are not affected by rebranding, even though they involve names containing Silver, Ag, or SSSW. This is primarily to ensure backward compatibility for J2EE applications developed under earlier versions of the server. Things that haven't changed include:
  • Names of executable files (such as SilverServer.exe) in the server's bin directory

  • Names of JAR files (such as SilverServerAll.jar) in the server's lib directory

  • Use of the name SilverMaster to refer to the server's system database

  • Use of the name Silver Security to refer to the server's native security (and the login realm name remains SSSW)

  • Package and class names (such as com.sssw.rts.adminapi.AgiAdmServer) in the server's API

  • Property names in the httpd.props file (such as http-server.com.sssw.srv.port_rt)

  • Use of the AGCLASSPATH environment variable to set the server's classpath

  • Server system table names (such as AgContents)

  • Server system URLs including the name SilverStream, such as:

       http://servername/SilverStream/Statistics/

J2EE

• Redeploy required when upgrading   If you have existing J2EE applications running on an earlier (pre-5.0) version of the server, you must redeploy them in order to run on the 5.x server. This requirement applies to both J2EE 1.2 and J2EE 1.3 applications.

• J2EE 1.3 deployment plans required   As of 5.0, the server no longer supports J2EE 1.2 deployment plans for any archives (EARs, WARs, EJBs, and so on). You must use J2EE 1.3 deployment plans, even if deploying J2EE 1.2 archives (which have J2EE 1.2 deployment descriptors). Novell exteNd Director includes facilities to help you upgrade deployment plans from 1.2 to 1.3 (see "How to Handle J2EE Versions" in the Utility Tools book of the exteNd Director help).

  For more information on the supported deployment plans, see the chapter on deployment plan DTDs in the Facilities Guide.

• Moving to the EJB 2.0 container   As of 5.0, the old EJB 1.1–only container has been removed from the server. As a result, you'll use the EJB 2.0 container for all EJB deployments, including 1.1 and 2.0 EJBs.

  Whether you're deploying 1.1 or 2.0 EJBs, you'll need to use an EJB 2.0 deployment plan. If you're starting with 1.1 EJBs and EJB 1.1 deployment plans, you must at least migrate those plans to 2.0. Migrating the beans themselves to 2.0 EJBs is recommended but not required.

  For more information on the EJB 2.0 container, see the server implementation notes chapter in the Facilities Guide.

• SilverJ2EEClient installation   As of 5.0, installation of SilverJ2EEClient is independent of SilverJRunner (which has been removed). As of 5.1, the SilverJ2EEClient installers:
  • SilverJ2EEClientInstall.exe
  • SilverJ2EEClientInstallSolaris.sh
  • SilverJ2EEClientInstallLinux.sh

  are no longer included on the product CD. You must download them from the Novell Web site and set them up on your server. Then users can access them from your server's SilverJ2EEClient install page:

     http://servername/SilverStream/Pages/SilverJ2EEClient.html

  or directly from this location:

     http://servername/SilverStream/SilverJ2EEClientInstall/

• Setting permissions for deployed archives   As of 5.0, the SMC's Security/Permissions panel lists deployed J2EE archives under the Deployed Objects directory. In earlier versions of the server, this directory was named EJB JARs & Media.

• ClassLoader hierarchy issues   See EJB java.lang.NoClassDefFoundErrors in the "Known issues" section of these release notes (below).

• JAR organization for deployed EJBs   As of 4.0, there are no more remote JARs for deployed EJBs. Instead, you need to add the client JAR (which contains the stubs, ties, and so on) into the client archive and deploy. This provides cross-vendor access of EJBs.

• Support removed for a JAR access technique   In 3.7.x you could add a JAR to the ObjectStore and reference it via a manifest classpath entry from a WAR, EJB, and so on. This is not supported as of 4.0.

• Path mapped URL patterns need leading slash   As of 4.0, you must have a leading slash in any path mapped URL patterns. In 3.7.x, this requirement was not enforced.

  This change may affect exteNd Director applications when you upgrade them to J2EE 1.3 to run on your post-3.7.x server. For example, you may discover that resources in a resource set cannot be found. The solution is to change $CONTEXT_URL$resource to $CONTEXT_URL$/resource and change the resource servlet mapping from:

     <url-pattern>resource/*</url-pattern>

  to:

     <url-pattern>/resource/*</url-pattern>

• JSP URLs need .jsp   As of 4.0, the .jsp extension is required when you reference a JSP page via an URL. In 3.7.x you could reference the JSP page as pagename instead of pagename.jsp:

     http://localhost/directory/mypage?parm=x

  Now you need to specify:

     http://localhost/directory/mypage.jsp?parm=x

• Tag library access for included JSP pages   In 3.7.x if you had a JSP page (aaa.jsp) that included other JSP pages (bbb.jsp and ccc.jsp), then ccc.jsp would get access to custom tag libraries declared in bbb.jsp. This was incorrect behavior. As of 4.0, you must do one of the following instead:
  • Reference the TLD in both bbb.jsp and ccc.jsp
  • Reference the TLD in aaa.jsp (which automatically gives bbb.jsp and ccc.jsp access to it)

Database

• ASA and Cloudscape DBMSs no longer installed   As of 5.1, the Sybase ASA (Adaptive Server Anywhere) and IBM Cloudscape DBMSs are no longer provided with the application server install. The DBMS provided with the application server is now MySQL.

Configuration

• Converting an RSA certificate to be FIPS-compliant   If you have an RSA certificate installed on your application server, but want to configure that server to be FIPS-compliant once you upgrade to the new server version, you must convert the RSA certificate to be FIPS-compliant. You can use the SMC to perform this conversion. Before you install the new server version, use the SMC to:
  1. Export the certificate
  2. Re-import the certificate

  For more information, see the chapter on setting up security in the Administrator's Guide.

• Consolidation of the server's port types   As of 5.0, you can configure two separate port types for handling the application server's operations: administration and runtime. The design port type (supported in earlier versions) has been consolidated into the administration port type.

• Support removed for enCommerce getAccess   As of 5.0, support for enCommerce getAccess is removed from the Web Server Integration (WSI) modules.

• New guidelines for client connections   The guidelines for determining your application server's client connection settings have been updated as of 5.0. For more information, see the chapter on tuning the server in the Administrator's Guide.

• JAR-related changes on the server   As of 5.0, the following JARs have been removed from the application server's \lib and \userlib directories (because JRE 1.4 provides all classes contained in these JARs):
  • Removed from \lib:

       crimson.jar
       jaas.jar
       jndi.jar
       ldap.jar

  • Removed from \userlib:

       crimson-java_xml_pack_fall_2001.jar
       xalan-java_xml_pack_fall_2001.jar
       xerces-1_4_4.jar
       xercesImpl-2_0_1.jar
       xmlParserAPIs-2_0_1.jar

    Because the XML classes are now included with the JRE, the excludeJ2EEXMLJars subelement of the EAR, EJB, and WAR deployment plans is ignored. Make sure you test applications that relied on the classes in the XML JARs (in the \userlib directory). The XML classes included with JRE 1.4 do not provide backward compatibility.

• How upgrading affects the name service port   As of 4.0, the property that specifies the server's name service port has been moved from the httpd.props file to the SilverMaster database. When you upgrade your server from an earlier version, the name service port will be reinitialized to 54890. If any of your servers use a value other than 54890 for the name service port, you will have to update the name service port to the value you want to use. After you upgrade your servers, you can change the name service port using the SMC or SilverMasterInit with the -C option (the latter is the required way if you are running multiple instances of the server on the same machine).

  In the SMC, the name service port setting is in the ORB settings section of the Configuration/General panel. Make sure to click Update after setting the value.

  To use the SilverMasterInit -C option, you'll need to create a property file. The property file can have any name and can reside in any location that is accessible to SilverMasterInit. The property file has the same syntax as the httpd.props file, except that you do not specify http-server in front of the property; instead, you specify hostname.portnumber (note that the host name and port number are separated by a dot and not a colon). The port number is the administration port and is required only when it is some value other than 80. To set the nameServicePort, specify:

     hostname.portnumber.com.sssw.srv.nameServicePort=nnnn

  For example:

     tundra.8080.com.sssw.srv.nameServicePort=55597

  When you run SilverMasterInit you should also use the -r option, because it will update an existing SilverMaster. This example shows how to use SilverMasterInit with the property file called port.props:

     SilverMasterInit -C port.props -U smbb -P password -A administrator -W admin -r

General

• Localization   The list of languages for which the server provides runtime support has changed. The supported languages as of 5.0 are:
  • Simplified Chinese
  • Traditional Chinese
  • English
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Portuguese
  • Russian
  • Spanish

  For more on localization, see the server implementation notes chapter in the Facilities Guide.

• Status of Server Administration API   As of Version 5.0 of the application server, reference documentation (including javadoc) for the Server Administration API is no longer included in the application server's help. Instead, this documentation is available on request from Novell.

• Remote UserTransaction support   Support for remote UserTransaction objects is deprecated as of Version 4.0 of the application server. If you use this feature, it should only be to maintain backward compatibility with existing applications. When looking up the remote UserTransaction object, make sure you use the old-style lookup string RMI/SilverStream-UserTransaction. For example:

     utx = (UserTransaction)PortableRemoteObject.narrow( initialContext.lookup(
           "RMI/SilverStream-UserTransaction" ), UserTransaction.class);

Legacy

• Classic features removed   In Version 4.x of the application server, the legacy SilverStream tools and technologies are supported but deprecated. As of Version 5.0, the application server no longer includes these classic features. The 5.x server is strictly for standard J2EE development and deployment.

Documentation updates

The following updates apply to the documentation and help for the exteNd Application Server:

Running the application server as a UNIX/Linux daemon

When you set up the Novell exteNd Application Server (or cluster) to run as a daemon in UNIX or Linux, note that the startup scripts you need are provided in the following directory (assuming that you install exteNd to the default path /opt/novell/exteNd5):

   /opt/novell/exteNd5/AppServer/etc/

Keep this in mind when reading the exteNd installation documentation, which is vague on the script location. (PPR 48626)

Known issues

Here are some noteworthy issues or problems that apply to this version of the Novell exteNd Application Server.

• Install issues
• Database issues
• Administration issues
• Deployment issues
• Runtime issues
• EJB issues
• Web Service issues

Install issues

• Path requirements for running new and old versions   Installing the application server on Windows will append the server's installation directory to your path. If you are keeping an earlier version of the application server on the same machine, you should change your path so that the version you are currently running comes first. Running both at the same time is not recommended and may result in some unexpected behavior—but if you try it, the more recent version should appear first on your path.

Database issues

• Troubleshooting for Microsoft JDBC driver   If you have trouble using the Microsoft JDBC driver, placing the required JAR files in a location without spaces in the path may help. (The default install location for this driver will contain a number of spaces.)

Administration issues

• When updating name service port   If your server uses a fully qualified domain name (such as myserver.mydomain.com), you will not be able to use SilverMasterInit -C to update your name service port. You will instead need to start the server and use the SMC to modify the port number. Be sure to use the fully qualified name when adding the server in the SMC in order for the port modification to take effect properly.

Deployment issues

• Deploying JARs with non-ASCII names   If you currently set the com.sssw.srv.international.UrlEncoding property (in the httpd.props file) to a value other than UTF-8, you may experience failures during deployment if any of your deployed JARs (including JARs packaged inside the archives) have names containing non-ASCII characters. To solve this problem, do one of the following:
  • Change the value of com.sssw.srv.international.UrlEncoding to UTF-8, or simply remove this property (UTF-8 is the default).
  • Rename your JARs to eliminate the non-ASCII characters.

  (PPR 46104)

• Deploying to the SSL administration port   If you deploy to the SSL administration port using SilverCmd, make sure you specify the HTTPS protocol with your server name (for example, https://localhost:8080). Otherwise, SilverCmd will block until the connection times out or until you initiate a break (via Ctrl+C or equivalent). (PPR 34573)

• Supported compilers   The SJ compiler listed in Compileroptions.xml is not supported.

• isEnabled setting for WARs   WARs with isEnabled set to false in the deployment plan are nonetheless enabled after deployment. (PPR 24720)

• Avoiding Sybase ASE deadlock during deployment   If you deploy a large and/or complex application to Sybase Adaptive Server Enterprise, in rare cases the database may deadlock. You can reduce the possibility of deadlock by reducing the number of threads used by the deployer to one. If that does not resolve the problem, there is a workaround involving dropping and adding indexes on a server system table; contact Technical Support.

Runtime issues

• OutOfMemoryError on Linux   If you get the failure message java.lang.OutOfMemoryError when running the application server on Linux, the problem may be insufficient threads. In this case, you need to increase the value of the tasks.h parameter NR_TASKS. (PPR 22849)

EJB issues

• EJB java.lang.NoClassDefFoundErrors   If you encounter java.lang.NoClassDefFoundErrors when running entity or session beans, it may be a JAR packaging problem. The server's ClassLoader hierarchy is:
  • EAR ClassLoader (highest level)
  • EJB ClassLoader
  • WAR ClassLoader (lowest level)

  A WAR delegates to an EJB, and an EJB delegates to an EAR.

  Classes loaded by a ClassLoader at a lower level can access any class loaded by a ClassLoader at a higher level (a component can call up the hierarchy, but not down it). For example, any class loaded by the WAR ClassLoader can access any class loaded by the EJB ClassLoader or the EAR ClassLoader. But the reverse is not true: a class loaded by the EAR ClassLoader cannot access a class loaded by the EJB ClassLoader or the WAR ClassLoader.

• Support limitation for CA certificates   The application server does not support the following CA certificates with EJBs using SSL over IIOP:
  • Autoridad Certificadora de la Asociacion Nacional del Notariado Mexicano,A.C..der
  • Autoridad Certificadora del Colegio Nacional de Correduria Publica Mexicana,A.C..der
  • C&W HKT SecureNet CA Class A.der
  • C&W HKT SecureNet CA Class B.der
  • C&W HKT SecureNet CA Root.der
  • C&W HKT SecureNet CA SGC Root.der
  • Equifax Secure Certificate Authority.der
  • Equifax Secure eBusiness CA-2.der
  • EUnet International Root CA.der
  • Saunalahden Serveri CA.der
  • Saunalahden Serveri CA_2.der

• Setting establishTrustInClient for EJB 2.0 IOR security   SUPPORTED mode for EJB 2.0 IOR security establishTrustInClient (subelement of the deployment plan's transportConfig and iorSecurityConfig elements) doesn't provide predictable SSL behaviors. Use NONE or REQUIRED mode for applications. (PPRs 34450 and 34441)

Web Service issues

• Web Service access problems with 100 continues   You may find that a Web Service works fine from a standalone Java program but hangs or generates SocketExceptions when called from the Novell exteNd Application Server. The problem is probably that the server hosting the Web Service claims to be HTTP1 1.1 compliant but doesn't support 100 continues properly. When HTTP client code running in the application server makes a request of a server with this bug, there will be some problems. The first request to the server will work (regardless of whether it's a GET or a POST), but the next POST request will hang or throw a SocketException.

  The best thing to do is see if there is a later version of the server software and proxy software. Most webmasters will be happy to get their sites working well. Novell knows that the following servers and proxies have this problem:

  • GLUE versions before 3.1

Problems fixed in Version 5.2

Number	Description
42251	HTTP - Calling setMaxInactiveInterval method on session doesn't timeout session
43858	HTTP - client debug HTTP headers get mixed up in server console
45603	HTTP - getServletContext() throws Exception
36626	JNDI - Unexpected behavior when looking up java:comp/env
42078	Security - Provide cache for NT System info
44189	Security - Unable to set a default NT domain if user is logged on as a local user
45108	Security - Allow non-default property values for Ldap jndi service provider
40816	Server General - Missing timestamps in error log when logging to file
44749	Server General - Ring buffer file processing does not increment file when max size reached
44750	Server General - Ring buffer feature file handling processing makes data hard to read
36579	Servlets - ServletContext temp directory creation can remove other temp dirs
39588	Servlets - web.xml session-timeout setting doesn't work if value greater than SMC timeout
43254	Servlets - response.setStatus(response.SC_NOT_FOUND) not handled properly
44065	Servlets - HttpServletRequest.getContextPath() returns null when executed in AgiExecutor
45284	Servlets - Mapping of error pages to Exception does not work.
40343	SilverCmd - SilverCmd errors are directed to wrong output in Linux platform
40786	SilverCmd - SilverCmd fails with unsecured silvermaster

Problems fixed in Version 5.2.1

Number	Description
46743	Administer Server/SMC - Add Users to Group Clear All button in Japanese is truncated.
46891	Administer Server/SMC - DEFECT000375350 SMC : Log Chart Data dialog contains truncated cancel button
47655	Administer Server/SMC - SMC - Log chart data to file: is truncated in Japanese. The value is missing
46890	Administer Server/SMC - DEFECT000372409 SMC - add security provider server dialog - truncated text
46766	Administer Server/SMC - DEFECT100367298 Pools can't be restarted after shutdown on Linux
46646	Administer Server/SMC - DEFECT100367279 - Can't Login after a Logout.
45181	Administer Server/SMC - On Linux, SMC context help doesn't launch browser
44018	Administer Server/SMC - Remote server console does not show output
39390	DB-MySQL -MySQL database server crashed during silvermasterinit
35400	Docs & Help (AppServ) - Need doc for new "dynamic connection pool limit" per-server property
37505	EJB - Entity Beans (AppServer) - Concurrency violation on update and delete to MySQL
41177	HTTP (AppServer) - "trace client 0" doesn't disable http session manager debug output
46918	Internationalization (AppServer) - Japanese Linux only: Truncations in SMC
46407	Internationalization (AppServer) - DEFECT100353819 truncated cancel button in SMC chart "reload statistics" dialog
46790	Internationalization (AppServer) - DEFECT100353785: Japanese/SMC chopped text on add database dialog
46791	Internationalization (AppServer) - DEFECT000373246: Japanese/SMC: Truncated Cancel button on Clipher suites Dialog
45816	Internationalization (AppServer) - error msg displayed on server console (or stored in log file) multi-lang problem
35079	JBroker Web - chinese characters displayed as ??? - jBrokerWeb doesn't support MBCS
46552	Localization (AppServer) - DEFECT000372410 SMC - group additional attribute - truncated text
47183	Localization (AppServer) - MBCS character string is corrupt in errlog file
47559	Security (AppServer) - NameNotFoundException exception when assigning Locksmith to LDAP user in SMC
47775	Security (AppServer) - Can not login LDAP from SMC
47151	Security (AppServer) - new SilverCmd to get/set properties on a running server or cluster
47617	Server General (AppServer) - fix appserver wrapper to pass flag to work around issue on 2.6 kernal
40927	Server General (AppServer) - sminit failure on upgrade
36152	Server General (AppServer) - NW: Unable to pass server startup parameters on Nakoma