Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Release Notes

- Previous: About Application Server Platform Edition 8.2 2006Q1
- Next: Application Client

## Administration

### The `package-appclient` script does not work if `domain1` is not present. (ID 6171458)

By default, there is a hard-coded value in `$INSTALL/lib/package-appclient.xml` for the `AS_ACC_CONFIG` variable for `domain1` that is pointed to by `asenv.conf`. If `domain1` is deleted and a new domain created, the `AS_ACC_CONFIG` variable is not updated with the new domain name, which causes the `package-appclient` script to fail.

#### Solution

Do one of the following:

- Leave `domain1` intact, and create your other domains around it.

- Remove `domain1` and replace the hard-coded value for `domain1` in `$INSTALL/lib/package-appclient.xml` with the new domain name. This will have to be done every time a new domain is created if `domain1` is not present.

### Cannot restore backed-up domain with another name. (ID 6196993)

Mirroring of a domain on the same Application Server installation cannot be performed using the `backup-domain` and `restore-domain` commands because the domain cannot be restored using a different name than the original, even though the `asadmin restore-domain` command provides an option to rename the domain. Renaming the backed-up domain appears to succeed, but attempts to start the renamed domain fail because the entries in the domain configuration are not changed, and `startserv` and `stopserv` use the original domain name to set paths.

#### Solution

The domain name used for `restore-domain` must be the same as that used for the original `backup-domain` command. The `backup-domain` and `restore-domain` commands in Application Server 8.2 work only for backing up and restoring the same domain on the same machine.

### Starting Application Server with additional JMX Agent is not supported. (ID 6200011)

J2SE 1.4.x, 5.0, or later can be configured on the Application Server. An integral feature of J2SE 5.0 platform is the ability to start a JMX agent. This is activated when you explicitly set system properties at the server startup.

Example values include:

    name="com.sun.management.jmxremote" value="true"
    name="com.sun.management.jmxremote.port" value="9999"
    name="com.sun.management.jmxremote.authenticate" value="false"
    name="com.sun.management.jmxremote.ssl" value="false"

After configuring JMX properties and starting the server, a new `jmx-connector` server is started within the Application Server VM. An undesirable side-effect of this is that the administration functions are affected adversely, and the Application Server administration GUI and CLI may produce unexpected results. The problem is that there are some conflicts between the built in `jmx-connector` server and the new `jmx-connector` server.

#### Solution

If using `jconsole` (or any other JMX-compliant client), consider reusing the standard JMX Connector Server that is started with Application Server startup.

When the server starts up, a line similar to the one shown below appears in the server.log. You can connect to the `JMXServiceURL` specified there and perform the same management/configuration operations after successfully providing the credentials; for example:

    [#|2004-11-24T17:49:08.203-0800|INFO|sun-appserver-ee8.1|javax.enterprise.
    system.tools.admin|_ThreadID=10;|ADM1501: Here is the JMXServiceURL for the
    JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://hostname:8686/management/
    rmi-jmx-connector]. This is where the remote administrative clients should
    connect using the JSR 160 JMX Connectors.|#]

For more information, refer to the Sun Java System Application Server 8.2 Administration Guide.

### Cannot redeploy or undeploy the web module that is the default web module of any virtual server. (ID 6204799)

If the web module is specified as the default web module of a virtual server, and you try to redeploy or undeploy it, you will get the following error:

    Trying to undeploy application from domain failed; Virtual Servers [server]
    have <WEB-MODULE-NAME\> as default web module. Please remove the default web
    module references first. ; requested operation cannot be completed Virtual
    Servers [server] have <WEB-MODULE-NAME\> as default web module. Please
    remove the default web module references first.

At this point, `domain.xml` is in an error state, and the Admin Console may not be able to display the table that shows the deployed web applications. The condition will persist even if the domain is stopped and started again.

#### Solution

Change the default web module.

#### To change the default web module

1. Using the Admin Console, go to the virtual server page, and change the default web module to empty or specify another web module.

2. Using the CLI, undeploy the web module by specifying `domain` as the target.

       # asadmin undeploy --target domain <WEB-MODULE-NAME\>

   The Admin Console should be fine now, and the web module can be deployed again, if desired.

### `FrameworkError` exception after deploying a WAR and JAR to PE server via the AMX API in the Application Server GUI. (ID 6201462)

When an application is deployed on PE using the AMX API and not referenced, the Application Server GUI throws errors while displaying that application. AMX requires that you explicitly handle references for your applications. For example, when an application is deployed, the `DeployedItemRefConfig` needs to be explicitly created. To simplify the deployment process, references are assumed to be present in PE, which in turn causes the issue with Application Server GUI.

#### Solution

Always create the reference to a resource or application after creating it.

### The Administration Console functionality for selecting cipher suites is not working correctly. (ID 6654726)

When selecting Http-Listeners "Support All Cipher Suites,? the check boxes are disabled, but become enabled again when the page is refreshed, even though the "Support All..." box is checked. Although this might seem to be a problem, after a certificate nickname has been entered and Save has been clicked, the changes are written to the configuration.

Solution

No action required. The changes have been saved.

- Previous: About Application Server Platform Edition 8.2 2006Q1
- Next: Application Client

- © 2010, Oracle Corporation and/or its affiliates