Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning

This article is a copy of the version for SPECjAppServer2004 v1.05 and Geronimo v1.2. It's now being updated for SPECjAppServer2004 v1.08 and Geronimo v2.0.12, but the updating process is not yet complete.

...

This article is written for SPECjAppServer2004 v1.08 and Geronimo v2.0.12. For other versions some stages may be different. Older versions of this article for SPECjAppServer2004 v1.05 and older versions of Geronimo can be found here: v1.0, v1.1, v1.2.

...

Product site: http://geronimo.apache.org

Latest version, 2.0.12: http://geronimo.apache.org/apache-geronimo-v201v202-release.html

Release notes: http://cwiki.apache.org/GMOxDOC20/release-notes-201txt202txt.html

Documentation page: http://geronimo.apache.org/documentation.html

...

The latest Geronimo version for now is 2.0.12.

General download page: http://geronimo.apache.org/downloads.html

...

Extract the downloaded archive to a local directory. The geronimo-jetty6-jee5-2.0.12 or geronimo-tomcat6-jee5-2.0.12 directory is created, that is your <GERONIMO> directory.

...

You may also use <GERONIMO>/bin/geronimo.sh or <GERONIMO>/bin/geronimo.bat scripts instead.

Note

Geronimo v2.0.12 needs access to Internet for SPECjAppServer2004 application to be deployed – it tries to fetch XML schemas from http://java.sun.com site.

So if you're behind a firewall, add the appropriate -Dhttp.proxyHost= and -Dhttp.proxyPort= options to the Geronimo startup line.

This problem is caused by OPENEJB-700 bug and should disappear after that bug is fixed.

...

No Format
bgColorblack
borderStylesolid
Booting Geronimo Kernel (in Java 1.5.0_11)...
Starting Geronimo Application Server v2.0.12
[********************************] 100%  38s Startup complete
  Listening on Ports:
    1050 127.0.0.1 CORBA Naming Service
    1099 0.0.0.0   RMI Naming
    1527 0.0.0.0   Derby Connector
    2001 127.0.0.1 OpenEJB ORB Adapter
    4201 0.0.0.0   OpenEJB Daemon
    6882 127.0.0.1 OpenEJB ORB Adapter
    8009 0.0.0.0   Jetty Connector AJP13
    8080 0.0.0.0   Jetty SelectChannel Connector HTTP
    8443 0.0.0.0   Jetty Select Channel Connector HTTPS
    9999 0.0.0.0   JMX Remoting Connector
   61613 0.0.0.0   ActiveMQ Transport Connector
   61616 0.0.0.0   ActiveMQ Transport Connector

  Started Application Modules:
    EAR: org.apache.geronimo.configs/webconsole-jetty6/2.0.12/car
    RAR: org.apache.geronimo.configs/activemq-ra/2.0.12/car
    RAR: org.apache.geronimo.configs/system-database/2.0.12/car
    WAR: org.apache.geronimo.configs/dojo-jetty6/2.0.12/car
    WAR: org.apache.geronimo.configs/remote-deploy-jetty/2.0.12/car
    WAR: org.apache.geronimo.configs/welcome-jetty/2.0.12/car

  Web Applications:
    /
    /console
    /console-standard
    /dojo
    /remote-deploy

Geronimo Application Server started

...

Note

Edit the deployment plans in <SPEC>/src/geronimo, remove all message-driven-destination tags from mfg.xml, orders.xml and supplier.xmlGeronimo v2.0.12 doesn't handle those tags correctly.

Instead of removing those tags, you also can replace them with <message-destination-type>javax.jms.Queue</message-destination-type>.

This problem is caused by OPENEJB-701 bug and should disappear after that bug is fixed.

...

Panel
borderStylesolid

java -jar bin/deployer.jar deploy repository/org/apache/geronimo/modules/geronimo-activemq-ra/2.0.12/geronimo-activemq-ra-2.0.12.rar <KIT>/sjas-jms.xml

You will get the SPECjAppServer2004/JMS/1.08/rar diagnostic.

...

To deploy SPECjAppServer2004 on Geronimo, this configuration uses the deployment plan that was originally found in Geronimo sources at http://svn.apache.org, modified and updated for Geronimo version 2.0.12.

Go to the <GERONIMO> directory and run:

...

Warning

These diagnostics are probably caused by the fact that TranQL version 1.3 is used in Geronimo v2.0.12 does not provide the necessary transaction isolation level. Hopefully, this problem will be fixed in TranQL version 1.3.1.

...