Sun ONE Application Server Bugs

Default Browser Is Incompatible With Sun ONE Application Server 7 (4741123)

When you attempt to use the Sun ONE Application Server Administrative UI with the Solaris 9 12/03 software default browser, the following error message is displayed:

Unsupported Browser: Netscape 4.78

It is recommended that you upgrade your browser to Netscape 4.79 or 
Netscape 6.2 (or later) to run the Sun One Application Server 
Administrative UI. Those who choose to continue and not upgrade may
notice degraded performance or unexpected behavior.

If you are running the version of Sun ONE Application Server Administrative UI that is included in the Solaris 9 12/03 release, use Netscape 4.79 or Netscape 7.0 software.

Workaround: Use /usr/dt/appconfig/SUNWns/netscape instead of /usr/dt/bin/netscape.

Access Control List Editing Not Supported on Some Versions of Netscape Navigator Software (4750616)

Sun ONE Application Server Access Control List (ACL) editing is not supported on some versions of Netscape Navigator^TM software. If you attempt to edit ACL entries while using either Netscape Navigator version 6.x or Netscape Navigator version 7.x software, you might encounter intermittent problems.

The following are the types of problems that might occur:

• The browser window disappears.

• The ACL edit screen does not display when launched.

Workaround: Choose one of the following workarounds:

• Use the supported 4.79 version of Netscape Navigator software or Microsoft Internet Explorer, version 6.0.

• Edit the ACL file manually. For details on ACL file formatting, see the Sun ONE Application Server 7 Administrator's Guide.

Accessing an Oracle 9.1 Database With an Oracle 9.2 Client Might Cause Data Corruption (4707531)

If you use an Oracle® 9.2 client to access an Oracle 9.1 database, data corruption might occur when a number column follows a timestamp column.

The problem might be caused by using the ojdbc14.jar file with an Oracle 9.1 database. Application of the patch might assist in addressing the situation on Solaris 32-bit machines that run an Oracle 9.1 database. This JDBC^TM driver is for Oracle working with JDK^TM 1.4.

Workaround: Obtain the patch that Oracle might make available from the Oracle Web site for Bug 2199718. Apply the patch to your server.

Administration Interface Reports Verifier Error When Viewing Persistence Manager Factory Resource Created From the Command Line (4733109)

A verifier error is reported for a Persistence Manager Factory resource that was created using the command-line interface. The following error is displayed when the resource is viewed in the Sun ONE Application Server Administration interface:

ArgChecker Failure: Validation failed for jndiName: object must be non-null

Workaround: Perform the following steps to create a new Persistence Management Factory resource:

1. Create a jdbc-connection pool with data source information to connect to a database.

2. Create a jdbc-resource to make the connection pool available through a Java Naming and Directory Interface^TM (J.N.D.I.) lookup.

3. Create a persistence-management resource with the jdbc-resource that was created in Step 2.

any Value in Address Attribute of iiop-listener Element in server.xml File Is Not Supported (4743366)

The any value in the address attribute of the iiop-listener element in the server.xml file allows for listening on all interfaces that are available on a system. This support includes both IPv4 and IPv6 interfaces. However, the Sun ONE Application Server default configuration uses an address value of 0.0.0.0 in the iiop-listener element. This default configuration does not listen on IPv6 interfaces. The configuration only listens on all IPv4 interfaces on a system.

Workaround: Use the :: value in the address attribute of the iiop-listener element in the server.xml file to listen on all IPv4 and IPv6 interfaces on a system.

Application Server Fails to Restart When Converting to an SSL-Enabled Environment (4723776)

If you attempt to restart the Sun ONE Application Server after installing a certificate, then enabling security, the restart fails. A message indicates that the server failed to receive a password.

When the Secure Socket Layer (SSL) is not enabled, passwords are not cached, which results in the failure of restart. The restart command does not support the transition from non-SSL to SSL enabled mode.

This problem only occurs the first time the server is restarted. Subsequent restarts work fine.

Workaround: Choose one of the following workarounds:

• If you have encountered this problem. Click the Start button.

• To avoid this problem, perform the following steps instead of clicking the Restart button:

  1. Click the Stop button.

  2. Click the Start button.

Application Server Might Crash During Dynamic Reloading (4750461)

If an application has many Enterprise JavaBeans^TM components, the server might crash during dynamic reloading of the application. The dynamic reloading feature is used in the development environment to quickly test minor changes to an application. The crash is caused by attempting to use more file descriptors than are available.

Workaround: Follow these steps:

1. Increase the file descriptors limit by adding lines, in this format, to the /etc/system file.

   • set rlim_fd_max=8192

   • set rlim_fd_cur=2048

   The values can be set higher or lower, depending upon the size of the application.

2. Reboot the system.

External Certificate Nickname Does Not Display in Administration Interface Nickname List (4725473)

If you install an external certificate through the Sun ONE Application Administration interface, a problem is encountered. This problem is encountered when you attempt to enable SSL for the http-listener by using the certificate that is installed on the external cryptographic module. Although the installation of the certificate is successful, the certificate nickname does not display in the Administration interface.

Workaround: Complete the following steps:

1. Log in to the system where the Sun ONE Application Server software is installed as an Administrative User.

2. Link the http-listener to the certificate that is installed on the external cryptographic module by using the asadmin command. For more information on the asadmin command, see the asadmin(1AS) man page.

   # asadmin create-ssl --user admin user--password password --host host name \ --port port --type http-listener --certname nobody@apprealm:Server-Cert \ --instance instance --ssl3enabled=true \ --ssl3tlsciphers +rsa_rc4_128_md5 http-listener-1

   The previous command establishes the link between the certificate and the server instance. The command does not install the certificate. The certificate was installed through the Administration interface.

   ---

   Note –

   Although the certificate is linked with http-listener, the http-listener listens in non SSL mode.

   ---

3. Enable the http-listener to listen in SSL mode. Use the following command:

   # asadmin set --user admin user --password password --host host name \ --port port server1.http-listener.http-listener-1.securityEnabled=true

   The previous command switches the server instance listening state from non-SSL to SSL. After you complete the previous steps, the certificate is displayed in the Administration interface.

You can now use the Administration interface to edit the http-listener as needed.

flexanlg Command Might Cause Open Failure Error (4742993)

If you are running the Sun ONE Application Server software in the Solaris 9 12/03 release, an open failure error might be displayed. The following error is displayed if you use the flexanlg command from /usr/appserver/bin:

ld.so.1: /usr/appserver/bin/flexanlg: fatal: libplc4.so:open failed:
No such file or directory
killed

Workaround: Complete these steps.

1. Add the following entry to the LD_LIBRARY_PATH file:

   /usr/lib/mps

2. Run the flexanlg command.

   % /usr/appserver/bin/flexanlg

IPv6-only Clients Cannot Connect to the Application Server (4742559)

If IPv6 is not used in your network, this problem does not apply to you.

By default, the Sun ONE Application Server 7 instances and Admin Server instances use IPv4. IPv4 is supported by all system software on which the Sun ONE Application Server is available. The Sun ONE Application Server configuration changes are required for conformance on those platforms where IPv6 is supported.

If these configuration changes are to be made, you must be absolutely sure of IPv6 support. If the IPv6 related configuration is applied to a system that has only IPv4 support, Application Server instances might not start.

Workaround: Perform the following configuration changes:

1. Start the Admin Server.

2. Start the Admin Console by connecting to the Admin Server HTTP host or port in a browser.

3. Select the server instance to configure for IPv6, for example, server1.

4. Expand the HTTP Listeners node in the tree view.

5. Select the HTTP Listener to configure for IPv6, for example, http-listener1.

6. Change the value of the IP Address field to ANY in the General section.

7. In the Advanced section, change the value of the Family field to INET6.

   If you set the Family field to INET6 IPv4, functionality is not disabled unless an IPv6 address is selected for IP address. Selection of an IP address of ANY matches any IPv4 or IPv6 address.

8. Click Save.

9. Select your server instance from the left pane.

10. Click Apply Changes.

11. Click Stop.

12. Click Start.

    The server restarts and implements your changes.

Modified Samples Are Not Updated Until Redeployed (4726161)

If users attempt to deploy a sample more than once after making small changes and repackaging the application, the following error message is displayed:

Already Deployed

This issue affects most of the samples because the samples use the Ant utility and the common.xml file, which have the deploy target. The combined use mixes deployment of applications with registration of resources.

Workaround: Choose one of the following workarounds:

• For the majority of the sample applications that use the Ant utility build.xml files, which include the common.xml file, type the following command:

  % asant deploy_common

• For all other sample applications, type the following commands:

  % asant undeploy % asant deploy

Nonzero Transaction Setting Causes Slow Local Transactions (4700241)

The Local Transaction Manager does not support transactions with definite timeouts. If you set the timeout-in-seconds attribute in the transaction-service element to a value that is greater than 0, all local transactions are processed as global transactions. A timeout value of 0 means that the transaction manager waits indefinitely if there is no response from a participating data source.

If the Data source driver does not support global transactions, a local transaction might fail.

Workaround: Reset the timeout-in-seconds value to the default of 0.

Oracle JDBC Driver Optimizations Not Being Initiated (4732684)

To utilize Oracle JDBC optimizations with Container-Managed Persistence (CMP) beans, the classes12.zip must be specified in the classpath-suffix attribute of the server.xml file. Do not place the classes12.zip file in the instance/lib/ directory, the default for third-party libraries.

Workaround: Add the classes12.zip file to the classpath-suffix attribute of the server.xml file.

RMI-IIOP Clients Do Not Work for IPv6 Addresses Where DNS Address Lookups Fail for the IPv6 Address (4743419)

If a DNS lookup for an IPv6 address fails, clients of Remote Method Invocation-Internet Inter-ORB Protocol (RMI-IIOP) do not work for IPv6 addresses.

Workaround: DNS should be set up at the deployment site, in order to look up an IPv6 address.