Sun Java System Application Server 7 Update 11 Release Notes

Sample Applications

This section describes known Sun Java System Application Server 7 sample application issues, and the associated solutions.

ID  

Summary  

4714439

In PetStore, cannot add a user that already exists.

In the PetStore sample application, trying to add a user that already exists displays a stack trace on the screen. 

Solution

None. 

4726161

Modified samples are not updated until redeployment.

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 since they use the Ant utility and the common.xml file, which have the "deploy" target, thus mixing deployment of applications with registration of resources.

Solution

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

4733412

Sample application converter has redundant JAR file in web module.

The converter application has a redundant stateless-converter EJB JAR file under the WEB-INF/lib directory. The EAR file is located under the sample application directory. From the bundled Solaris build, it is here:

/usr/appserver/samples/ejb/stateless/converter/stateless-converter.ear

Extract this file and go to the WEB-INF/lib directory of the web module named stateless-converter and you will see the file. This redundant JAR file applies to all the web modules which call the EJB module. The root cause of the problem is the common.xml file used to build the application.

Solution

None. Doesn’t affect functionality when running sample application. 

4739854

Instructions needed for deploying resources using asadmin.

In the documentation for some samples, your are instructed to deploy the application using the asadmin command, but no explanation is provided on how to create the needed resources.

Solution

You can deploy the application/resource by using the asadmin command and can get more information by referring to the sample’s build.xml file. More information can also be found in the printout from running asant deploy.

For JDBC/BLOB example, the following steps create the resources using asadmin (assuming the hostname is jackiel2 and the username/password/port for the Admin Server is admin/adminadmin/4848):

asadmin create-jdbc-connection-pool --port 4848 --host jackiel2 --password adminadmin --user admin jdbc-simple-pool

--datasourceclassname com.pointbase.jdbc.jdbcDataSource --instance server1

asadmin set --port 4848 --host jackiel2 --password adminadmin --user admin

server1.jdbc-connection-pool.jdbc-simple-pool.property.DatabaseName=jdbc:pointbase:server://localhost/sun-appserv-samples

4747534

The lifecycle-multithreaded sample application asks for the admin user password 8 times.

While deploying the sample application lifecycle-multithreaded.jar file using the asant deploy command, you are prompted to enter the admin user password eight times.

Solution

None. 

4748535

Miscellaneous sample file issues.

  1. Logging sample generates multiple log files, for the fourth logging option.

  2. Logging sample has a redundant log.properties file.

  3. Instructions for the security grant in sample documentation are not fully correct.

Solution

  1. Close the handler before removing it. See initLog() method in GreeterServlet.java.

    private void initLog(String log_type) { //Remove all handlers Handler[] h = logger.getHandlers(); for (int i = 0; i < h.length; i++) { h[i].close(); //must do this logger.removeHandler(h[i]); } ...}

    Also, open file handler with an append option. See addHandler() in GreeterServlet.java. Write:

    Handler fh = new FileHandler(log_file, true);

    instead of

    Handler fh = new FileHandler(log_file);

  2. Edit the build.xml file as follows:

    < <fileset dir="${src.docroot}" excludes="cvs,annontation"/>

    > <fileset dir="${src.docroot}" excludes="cvs,annontation,log.properties"/>

  3. In "Running the Sample Application" section, remove domains/domain1/ from instructions to adding security grant entries to the server.policy file.

4752731

PointBase 4.3 replaced with PointBase 4.4.

When downloading and installing PointBase with the samples, (http://hostname:port/samples/docs/pointbase.html) the instructions refer to PointBase 4.3. However, PointBase 4.3 as been replaced by PointBase 4.4.

Solution

In the "Update Samples Ant Files" section, use the pbtools44.jar and pbclient44.jar files instead of the pbtools43.jar and pbclient43.jar files.

In the "Starting PointBase" section, for PointBase downloaded and installed separately on UNIX platforms, use pointbase_install_dir/tools/server/start_server to start PointBase.

5012233

Deployment failed on the connector sample cci.ear file.

Displays an error saying external entity not found “http://www.sun.com/software/sunone/appserver/dtds/sun-application-client_1_3-0.dtd”. 

Solution

Modify sun-application-client.xml to have single quotes instead of double quotes.

Sample: 

<!DOCTYPE sun-application-client PUBLIC ’-//Sun Microsystems, Inc.//DTD Sun ONEApplication Server 7.0 Application Client 1.3//EN’ ’http://www.sun.com/software/sunone/appserver/dtds/sun-application-client_1_3-0.dtd’>