This section describes known problems and associated workarounds for the Sun Java System Application Server Platform Edition 8.2 2006Q1 product. If a summary statement does not specify a particular platform, the problem applies to all platforms. This information is organized into the following sections:
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.
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.
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.
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.
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.
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.
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.
Change the default web module.
Using the Admin Console, go to the virtual server page, and change the default web module to empty or specify another web module.
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.
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.
Always create the reference to a resource or application after creating it.
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.
This section describes known application client issues and associated solutions.
If you have a top level JAR file inside your client JAR (in this case, reporter.jar), when you deploy the client JAR, the MANIFEST file for that JAR overwrites the MANIFEST file for the client JAR.
None at this time.
Dynamic content technologies, such as CGI-bin and SHTML, are no longer supported.
Use JSP and Web service technologies instead.
This section describes known container managed persistence issues and associated solutions.
If the where clause in an EJBQL query contains an OR operator and a single-valued cmr navigation, the query result will not contain the result for rows in which the navigation path is null even though the navigation path is in a different OR clause.
For example, consider a schema comprising Employee, Department, and Insurance. Employee has a 1:Many relationship with Department and a 1:1 relationship with Insurance:
select Distinct Object(e) from Employee e where e.name = ’John’ OR e.department.name = ’Engineering’
The above query will not return employees whose name is John and does not belong to any department.
select Distinct Object(e) from Employee e where e.department.name = ’Engineering’ OR e.insurance.name = ’xyz’
The above query will not return any employee whose insurance name is xyz and does not belong to any department. It will also not return any employee whose department name is Engineering and does not have any insurance.
Execute the query for each OR condition separately and merge the results.
This section describes known Deploytool issues and associated solutions.
sun-application-client.xml
sun-ejb-jar.xml
sun-web.xml
A JMS destination resource specified as the JNDI Name in the Message Destinations tab may not be saved to the Sun descriptor. After specifying the Destination Name (for example, PhysicalQueue, a physical destination created with create-jmsdest) and pressing Enter, the Destination Name appears under Display Name, and the client or bean name appears in the Producers list. After typing “jms/Queue” in the Sun-specific JNDI Name text field and pressing Enter, the application does not show as “(changed)” in the title bar, and an error is written to ~/.deploytool/logfile. When saving the application and going back to the tab, the JNDI Name field is blank again. When viewing the Sun descriptor using Tools\>Descriptor Viewer\>Application Server Descriptor, the <message-destination\> element within the <jndi-name\> element has not been created.
The problem is that during a deploytool session, the first time a value is entered for a Message Destination JNDI Name, the value appears correct in the Sun descriptor but an IllegalArgumentException is thrown by org.netbeans.modules.schema2beans.BeanProp.setElement(). Subsequent changes or additions of a Message Destination JNDI Name in the same application or other applications will not be saved to the Sun descriptor.
To edit an existing JNDI Name of a Message Destination:
Delete the existing JNDI Name by leaving the JNDI Name text field blank and pressing Enter.
Type the new JNDI Name and press Enter.
Review the Sun descriptor by clicking Tools\>Descriptor Viewer\>Application Server Descriptor.
Save the application by clicking File\>Save.
If the JNDI Name is not saved to the Sun descriptor:
Restart deploytool.
On the Message Destinations tab, select a Message Destination or add a new Message Destination.
Enter the JNDI Name for the Message Destination in the Sun-specific JNDI Name text field, and then press Enter.
Review the Sun descriptor by clicking Tools\>Descriptor Viewer\>Application Server Descriptor.
Save the application by clicking File\>Save.
Repeat the above steps each time a value needs to be entered in the Sun-specific JNDI Name on the Message Destinations tab, unless a value is being entered in the JNDI Name text field for the first time during a deploytool session.
This problem manifests with two sets of symptoms:
Clicking Next on the WSDL File panel does not go to the next panel, and an exception is thrown:
java.lang.NoClassDefFoundError: com/sun/org/apache/xpath/internal/XPathAPI
On Create Packaged Endpoint panel, select Create Web Service Endpoint and Package. Clicking Finish on the Next Steps panel does not create the Endpoint module in the output directory, and an exception is thrown:
java.lang.NoClassDefFoundError: com/sun/org/apache/xpath/internal/XPathAPI.
The problem is that xalan.jar, which contains the XPathAPI.class, is missing from the CLASSPATH. Note that this problem does not exist with JDK 5.0.
Add xalan.jar to the CLASSPATH includes for the s1as-deploytool process of install_dir/lib/processLauncher.xml; for example:
includes="appserv-assemblytool.jar,activation.jar,appserv-admin.jar, appserv-cmp.jar,appserv-rt.jar,j2ee.jar,jaxrpc-impl.jar,appserv-ext.jar, deployhelp.jar,admin-cli.jar,dom.jar,xercesImpl.jar, xalan.jar"
When you create an Enterprise Bean in deploytool, and then navigate to the Transaction or Security tab for the bean node, the “Local Home” and “Remote Home” labels are incorrectly translated as “Local Installation Directory” and “Remote Installation Directory.”
This section describes known documentation issues and associated solutions.
The documentation for AMX (Application Server Management eXtenstions) does not specify some monitoring features that are not available in Application Server Platform Edition 8.2. Specifically, the components that cannot be monitored in the Platform Edition are as follows:
Production Web Container (PWC):
PWC HTTP Service
PWC Connection Queue
PWC ThreadPool
PWC DNS
PWC KeepAlive
PWC File Cache
PWC Virtual Server
PWC Request
Webmodule
SessionSize
ContainerLatency
SessionPersistTime
CachedSessionsCurrent
PassivatedSessionsCurrent
StatefulSessionStore
CheckpointCount
CheckpointSuccessCount
CheckpointErrorCount
CheckpointedBeanSize
CheckpointTime
None needed. These statistics are not relevant for Platform Edition.
The help command for asadmin create-domain describes --admin.jmxport, which is not a valid option for this command.
The --admin.jmxport cannot be used with the asadmin create-domain command.
The “Realms” section in Chapter 2, “Securing Applications,” in the Sun Java System Application Server Platform Edition 8.2 2006Q1 Developer’s Guide incorrectly refers to extending com.sun.appserv.AbstractLoginModule, however this class is now named com.sun.appserv.AppservLoginModule.
Refer to com.sun.appserv.AppservLoginModule instead of com.sun.appserv.AbstractLoginModule.
Getter methods for NumConnAcquired and NumConnReleased statistics are missing from ConnectorConnectionPoolStats and AltJDBCConnectionPoolStats. These getter methods will be added in a future release as getNumConnAcquired() and getNumConnReleased().
Calling the following methods in EJBCacheStats will throw an exception: getPassivationSuccesses(), getExpiredSessionsRemoved(), getPassivationErrors(), getPassivations(). This will be fixed in a future release.
The AMX MBeans may require several seconds after server startup before they are all registered and available for use. A future release will make it possible to determine when the AMX MBeans are fully loaded.
The constant XTypes.CONNNECTOR_CONNECTION_POOL_MONITOR is misspelled (“NNN”). This will be corrected in a future release.
As a result of other defects (possibly 6295215) the code provided in the Obtaining a Physical Connection from a Wrapped Connection in Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Developer’s Guide section of Chapter 11, Using the JDBC API for Database Access, in Sun Java System Application Server Platform Edition 8.1 2005Q2 Update 2 Developer’s Guide is not correct. Specifically, the line:
Connection drivercon = ds.getConnection(con); |
should now read:
Connection drivercon = ((com.sun.gjc.spi.DataSource)ds).getConnection(con); |
This section describes known installation/uninstallation issues and associated solutions.
This problem has been reported intermittently on the Solaris x86 platform, but it is possible that it also affects Solaris SPARC and Linux platforms.
The problem is that the installer\qs or uninstaller\qs first screen correctly displays the full text and “Help” and “Cancel” buttons, but the “Next” button necessary to navigate to the next screen is not visible. Although button is not visible, its area is active and if you click on it, navigation to the next screen proceeds normally. The cause of the problem is intermittent J2SE GUI repaint issue.
One workaround is to click on the Next button area just to the left of the Help button. Another workaround is to force repainting of the screen by resizing it slightly or by minimizing and restoring the installer window. After repainting, the missing Next button will become visible.
This problem has been observed on several Linux systems. It is most common on Java Desktop System 2 but has also been observed on RedHat distributions.
After clicking the Finish button on the last installer screen, the installer fails to launch a browser window containing the product About page or product registration page, and hangs indefinitely, not returning the command prompt.
Exit the installer by pressing Ctrl+C in the terminal window in which the installer was started. After doing this, browser window containing product About page or registration page will sometimes be launched, but if it does not show up, start the browser and enter following URL in order to review About page:
file://install_dir/docs/about.html
If you also selected the installation option to register the product, follow the link to registration page available on product About page.
The setup executable that launches the Linux installer sometimes hangs. Instead of resolving the J2SE location and starting the install wizard, the wrapper hangs and returns the following messages:
Chcking available disk space.... Checking Java(TM) 2 Runtime Environment.... Extracting Java(TM) 2 Runtime Environment.... Deleting temporary files.....
This issue is seen only in some versions of Linux, and seems to depend on environment settings, especially the presence of the JAVA_HOME variable.
To work around this issue:
Unset the JAVA_HOME variable by running unset or unsetenv depending on your shell.
Run setup with the -javahome option to specify the JAVA_HOME used by the installer.
For this release, Application Server does not support Network File System (NFS).
None.
This section describes known lifecycle management issues and associated solutions.
[echo] Doing admin task set [exec] [Attribute(id=redelivery-interval-internal-in-millis) : Redelivery- Interval (7,000) should be greater than or equal to Minimum-delivery- interval-in-millis (9,000)] [exec] CLI137 Command set failed.
minimum-delivery-interval is the minimal interval duration between deliveries of the same periodic timer.
redelivery-interval-in-mills is the time the timer service will wait after a failed ejbTimeout before attempting redelivery.
The problem is that the logic that relates the redelivery interval property to the minimum delivery property is incorrect and prevents you from using the GUI or the CLI to set any value where the minimum delivery interval is greater than redelivery interval.
The minimum-delivery-interval-in-millis must always be set equal to or higher than ejb-timer-service property redelivery-interval-in-millis. The problem is that there is an erroneous validation check in the Application Server to verify that the value for redelivery-interval-in-millis is greater than the value for minimum-delivery-interval-in-millis.
Use the default values for these properties, as follows:
minimum-delivery-interval(default)=7000 redelivery-interval-in-millis(default)=5000
Values other than these defaults will generate an error.
This section describes known logging issues and solutions.
Setting the java.security.debug option for the JVM will cause the server instance startup to freeze with a deadlock; for example, setting the following in domain.xml causes the problem:
<jvm-options\>-Djava.security.debug=access,failure</jvm-options\>
None at this time. Please avoid setting this flag.
This section describes known security issues and solutions.
This problem occurs, for example, when a target message in a client-side message-security-binding element is specified by java-method within a port-info element within a service-ref element:
<!ELEMENT service-ref ( service-ref-name, port-info*, call-property*, wsdl- override?, service-impl-class?, service-qname? )\> <!ELEMENT port-info ( service-endpoint-interface?, wsdl-port?, stub- property*, call-property*, message-security-binding? )\> <!ELEMENT message-security-binding ( message-security* )\> <!ELEMENT message-security ( message+, request-protection?, response-protection? )\> <!ELEMENT message ( java-method? | operation-name? )\>
The message-security-binding element is used here to define message protection policies for specific methods of a web service endpoint.
Use an operation-name element within the message element to identify by WSDL operation name the message to which the protection policies defined in the containing message-security element apply.
This section describes known Upgrade utility issues and associated solutions.
When running the Upgrade Utility and identifying the install_dir as the source installation directory, the upgrade process upgrades only those domains that are created under install_dir/domains directory. Domains created in other locations are not upgraded.
Before starting the upgrade process, copy all the domain directories from their different locations to the install_dir/domains directory.
After upgrading an 8.0 Application Server with multiple domains, the domains may not be able to start simultaneously due to having the same port number configured for the JMX connector.
Change the port value.
Check the install dir /domains/domain1/config/domain.xml file, for the following entry:
<jmx-connector accept-all="false" address="0.0.0.0" auth-realm-name= "admin-realm" enabled="true" name="system" port="8686" protocol="rmi_jrmp" security-enabled="false"/\>" -- and in file <as 8.1 install dir\> /domains/domain1/samples/config/domain.xml, notice it used the same port "8686", so it failed to start domain due to port conflict. |
Change the port value 8686 to 8687, and then restart domain1.
This problem has been observed on several Linux systems, it is most common on Java Desktop System 2 but has also been observed on RedHat distributions.
After clicking the Start Upgrade Tool button on the final installer screen, the installer fails to launch the upgrade tool to complete the upgrade process, and hangs indefinitely, not returning the command prompt.
This issue is not encountered if command line installation mode is used to run upgrade in place.
If you ran upgrade in place in GUI mode and encountered this problem, exit the installer by pressing Ctrl+C in the terminal window in which the installer was started.
Start upgrade tool from the terminal window, using following command:
install_dir/bin/asupgrade --source install_dir/domains --target install_dir --adminuser adminuser--adminpassword adminpassword --masterpassword changeit |
adminuser and adminpassword should match the values used for the installation you are upgrading.
When the upgrade tool completes the upgrade process you can also start the browser and enter following URL in order to review About page:
file://install_dir/docs/about.html
If you also selected the installation option to register the product, follow the link to registration page available on product About page.
This section describes known web container issues and associated solutions.
If you request precompilation of JSPs when you deploy an application on Windows, later attempts to undeploy that application or to redeploy it (or any application with the same module ID) will not work as expected. The problem is that JSP precompilation opens JAR files in your application but does not close them, and Windows prevents the undeployment from deleting those files or the redeployment from overwriting them.
Note that undeployment succeeds to a point, in that the application is logically removed from the Application Server. Also note that no error message is returned by the asadmin utility, but the application\qs directory and the locked jar files remain on the server. The server\qs log file will contain messages describing the failure to delete the files and the application\qs directory.
Attempts to redeploy the application after undeploying fail because the server tries to remove the existing files and directory, and these attempts also fail. This can happen if you try to deploy any application that uses the same module ID as the originally deployed application, because the server uses the module ID in choosing a directory name to hold the application\qs files.
Attempts to redeploy the application without undeploying it first will fail for the same reasons.
If you attempt to redeploy the application or deploy it after undeploying it, the asadmin utility returns an error similar to the one below.
An exception occurred while running the command. The exception message is: CLI171 Command deploy failed : Deploying application in domain failed; Cannot deploy. Module directory is locked and can\qt be deleted
If you specify --precompilejsps=false (the default setting) when you deploy an app, then this problem will not occur. Be aware that the first use of the application will trigger the JSP compilation, so the response time to the first request will be longer than for later requests.
Note also that if you do precompile, you should stop and restart the server before undeploying or redeploying the application. The shutdown frees the locked JAR files so the undeployment or redeployment after the restart can succeed.
The optional load-on-startup servlet element in a web.xml indicates that the associated servlet is to be loaded and initialized as part of the startup of the web application that declares it.
The optional content of this element is an integer indicating the order in which the servlet is to be loaded and initialized with respect to the web application\qs other servlets. An empty <load-on-startup\> indicates that the order is irrelevant, as long as the servlet is loaded and initialized during the startup of its containing web application.
The Servlet 2.4 schema for web.xml no longer supports an empty <load-on-startup\>, meaning that an integer must be specified when using a Servlet 2.4 based web.xml. If specifying an empty <load-on-startup\>, as in <load-on-startup/\>, the web.xml will fail validation against the Servlet 2.4 schema for web.xml, causing deployment of the web application to fail.
Backwards compatibility issue. Specifying an empty <load-on-startup\> still works with Servlet 2.3 based web.xml.
Specify <load-on-startup\>0</load-on-startup\> when using a Servlet 2.4 based web.xml to indicate that servlet load order does not matter.
When using the AMX API, removing a reference to an application without first explicitly stopping the application results in that application still being accessible. This behavior is by design, and is a documentation omission.
To remove an application so it is no longer accessible:
The JSP page is accessed but fails to compile, and the server log contains the error message “Unable to execute command” with the following stack trace:
at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec (Execute.java:655) at org.apache.tools.ant.taskdefs.Execute.launch (Execute.java:416) at org.apache.tools.ant.taskdefs.Execute.execute (Execute.java:427) at org.apache.tools.ant.taskdefs.compilers. DefaultCompilerAdapter.executeExternalCompile(DefaultCompilerAdapter. java:448) at org.apache.tools.ant.taskdefs.compilers.JavacExternal. execute(JavacExternal.java:81) at org.apache.tools.ant.taskdefs.Javac. compile(Javac.java:842) at org.apache.tools.ant.taskdefs.Javac.execute (Javac.java:682) at org.apache.jasper.compiler.Compiler.generateClass (Compiler.java:396)
Set the JSP compilation switch fork to false.
This can be done either of two ways:
Globally, by setting the fork init parameter of the JspServlet in ${S1AS_HOME}/domains/domain1/config/default-web.xml to false:
<servlet\> <servlet-name\>jsp</servlet-name\> <servlet-class\>org.apache. jasper.servlet.JspServlet</servlet-class\> .... <init-param\> <param-name\> fork</param-name\> <param-value\>false</param-value\> </init-param\> .... </servlet\>
On a per-web application basis, by setting the fork JSP configuration property in sun-web.xml to false:
<sun-web-app\> <jsp-config\> <property name="fork" value="false" /\> </jsp-config\> </sun-web-app\>
Either setting will prevent ant from spawning a new process for javac compilation.
The default configuration of the Application Server PE does not perform optimally on multi-CPU machines. A trade-off is made so that startup is faster, but this can negatively impact the performance of web applications.
Configure the Application Server to use the following JVM option:
-Dcom.sun.enterprise.server.ss.ASQuickStartup=false