6171458
|
The package-appclient script does not work if domain1 is not present.
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.
|
6196993
|
Cannot restore backed-up domain with another name.
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.1 work only for backing up and restoring the same
domain on the same machine.
|
6200011
|
Starting Application Server with additional JMX Agent is not supported.
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 Virtual Machine.
An undesirable side-effect of this is that the administration functions are
affected adversely, and the Application Server administration Console and
command—line interface 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 JMXService URL
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 Administration Guide.
|
6206176
|
On UNIX, overly restrictive execute permissions on Application Server
start and stop scripts.
If you run the asadmin restore-domain command while
logged in as user "A", the scripts will end up with permissions as 744 (rwxr--r-- ). If you subsequently attempt to start or stop a domain
as user "B" (even if "B" is root), it will fail because the scripts are only
executable for "A".
Solution
Change the permissions on the scripts:
chmod 755 appserv/domains/domain-name/bin/*
|
|
6236544, 6275436
|
Load balancer configuration file does not get created with the endpoint
URL of any web service.
When setting up the load balancer configuration with an application
that has an EJB module that exports a web service URL, the context root for
the web service isn't in the resulting loadbalancer.xml file.
Solution
-
Edit the loadbalancer.xml file to add
the missing web module as follows:
<web-module context-root="context-root-name"
disable-timeout-in-minutes="30" enabled="true"/>
|
-
Replace context-root-name value
with the context root name of the web service that was exposed as an EJB.
|
6288893
|
Application Server restart using sun-appserv-admin causes LoginException error.
Solution
-
Rename the existing <as_install>/bin/asant script to asant.bak.
-
Copy the asant.template file in <as_install>/lib/install/templates/ee (for SE/EE version)
to the <as_install>/bin/
directory and rename the file asant.
-
Edit the newly copied <as_install>/bin/asant script, replacing the %CONFIG_HOME% token
with <as_install>/config.
-
If there were any manual changes made to the original asant.bak file, merge them into the new asant script.
|
6315957
|
The .asadmintruststore file is not described in the Application Server documentation.
If this file does not exist in the server administrator's home directory,
you may experience serious bugs when upgrading certain applications hosted
on the server.
Solution
-
If possible, the asadmin start-domain domain1 command
should be run by user who installed the server.
-
If it is not run by that user, the .asadmintruststore should
be moved or copied from the home directory of installing
user to the home directory of the running user.
-
Note that if the file is moved (not copied) from the installing
user's home directory to the running user's home directory,
you might experience application upgrade problems, as described in bugs 6309079,
6310428 and 6312869, because the upgrade/install user (normally root in
Java ES) will no longer have the .asadminstruststore file
in his or her home directory.
|
6462903
|
Error occurs in Application Server 8.1 Admin GUI when Save button
clicked more than once.
When changing the HTTP port value on a server instance, either start
the server instance before making the port change, or click the Save button
only once if the server instance is down.
|
6506605
|
asadmin multimode appears to cache the master password.
The following series of operations fail with asadmin when
running in multimode:
create-domain
start-domain
stop-domain
delete-domain
create-domain
|
The final create-domain fails with the error:
Invalid database password. CLI130 Could not create domain, domain2
|
This problem is caused by a JDK limitation.
Solution
Please do not create multiple domains in a single Java VM with asadmin
multimode. You cannot use asadmin multimode to
create or start two domains with different master passwords.
|