The HTTP and HTTPS connectors now communicate with the OpenJMS server via the openjms-tunnel servlet.

This replaces the servlets deployed in openjms.war in previous releases. The openjms-tunnel servlet supports bidirectional communication. This means that the server no longer needs to establish socket connections back to clients (which was problematic for hosts with firewalls).

See Configuring the HTTP Connector   and Configuring the HTTPS Connector   for more details.

The server now listens on a single port for client connections, when the TCP, TCPS, HTTP, or HTTPS connector is configured.

Previously, two ports were required. However, the server, embedded JNDI service and administration service can be configured to use separate ports.

The TCPS connector no longer defaults to requiring clients to authenticate themselves. See Client authentication   for more details.

Changed the configuration of the HttpConfiguration   and HttpsConfiguration   elements in openjms.xml .

The meanings of the port   and host   attributes have changed. Previously, these used to represent the web-server host and port. Now, they represent the host and port that the server is handling requests from the openjms-tunnel servlet on.

Two new attributes, webServerHost   and webServerPort , now represent the web-server host and port.

The following attributes, previously part of HttpConfiguration   and HttpsConfiguration , are no longer supported:

• proxyHost
• proxyPort
• clientPingInterval
• serverServlet
• jndiServlet
• adminServlet

The following attributes, previously part of the DatabaseConfiguration   element in openjms.xml   are no longer supported:

• garbageCollectionInterval
• garbageCollectionBlockSize
• garbageCollectionThreadPriority

Fixed bug 1192265 - Message lost in multi-processor environment.

Fixed bug 1108562 - NullPointerException when calling DatabaseService.getAdapter

Fixed bug 1058427 - QueueDestinationCache throws IndexOutOfBoundsException

Fixed bug 1107742 - Clock Daemon Thread never exits in Applet

Fixed bug 756237 telnet-ing directly to tcp connector/jndi yields OutOfMemory.

Added support for RFE 750870 - Cannot bind to a specific interface

Fixed bug 667580 - setClientID not throwing IllegalStateException

Fixed bug 1109259 - Applet client connection to firewalled server

Fixed bug 1023188 - Network cable disconnect does not deregister client.

Fixed bug 1105874 - Can't use https connector with other JSSEs

Fixed bug 1123902 - Heirarchical names results in NameNotFoundException

Dropped support for the JDBM database.

The JdbmDatabaseConfiguration   element of openjms.xml   is no longer valid.

OpenJMS now ships with a version of Derby as the default database. See Configuring the database   for more details.

Removed pre-0.7.5 release InitialContextFactory implementations:

• RmiJndiInitialContextFactory
• IpcJndiInitialContextFactory
• IntravmJndiInitialContextFactory
• HttpJndiInitialContextFactory
• SslHttpJndiInitialContextFactory

The database schema has changed, in order to support the fix for bug 782209 - "JMSMessageID generation inadequate".

To migrate an existing JDBC database to the new schema, run:

Windows

        
     
> cd %OPENJMS_HOME%\bin
   
     
> dbtool.bat -migrate -config ../config/openjms.xml
   
     
          
   
      

Unix

        
     
> cd $OPENJMS_HOME/bin
   
     
> dbtool.sh -migrate -config ../config/openjms.xml
   
     
          
   
      

Back up your database prior to doing this!

Limitations

• no provision for migrating databases which are unsupported by dbtool
• no provision for migrating a JDBM database

Fixed bug 744331 - messages.messageBlob using wrong field type in PostgreSQL

Fixed bug 832157 - Remove LeaseManagerConfiguration.

As a consequence, the < LeaseManagerConfigu ration/ >   element is no longer required in openjms.xml (specifying it will cause a FailedToCreateServerException).

Unified InitialContextFactory implementations into a single class.

To construct an InitialContext:

        
     
Hashtable properties = new Hashtable();
   
     
properties.put(Context.INITIAL_CONTEXT_FACTORY,
   
     
               "org.exolab.jms.jndi.InitialContextFactory");
   
     
properties.put(Context.PROVIDER_URL, "rmi://myhost:1099/");
   
     
Context initial = new InitialContext(properties);
   
     
          
   
      

To specify to connect to the JNDI provider using TCP:

        
     
properties.put(Context.PROVIDER_URL, "tcp://myhost:3035/");
   
     
          
   
      

Using HTTP:

        
     
properties.put(Context.PROVIDER_URL, "http://myhost:8080/");
   
     
          
   
      

The old InitialContextFactory implementations ( RmiJndiInitialContextFactory, IpcJndiInitialContextFactory, IntravmJndiInitialContextFactory, HttpJndiInitialContextFactory, SslHttpJndiInitialContextFactory ) may still be used, but will be removed in a future release.

Simplified URLs for the RMI connector. The server path no longer needs to be specified in the URL.

E.g, when specifying the Context.PROVIDER_URL, rmi://myhost:1099/   is equivalent to rmi://myhost:1099/JndiServer

When specifying the administration URL, rmi://myhost:1099/ is equivalent to rmi://myhost:1099/JmsAdminServer

Changed the behaviour of the http connector. Previously, if the JndiConstants.HTTP_CLIENT_URL_PROPERTY property wasn't set, the value would default to http://localhost:8080/openjms/OpenJMSClient , which isn't very useful for most applications. It now defaults to the host and port of the server's web server.