Consortium Solutions Middleware Forge MyObjectWeb

JORAM

Project Links
· Home
· Specification
· Download
· Documentation
· Licenses
· History

Developers' Corner
· Welcome
· Road map
· Code updates
· CVS repository
· ObjectWeb Forge site

Support
· Free mailing lists
· Professional Support
· Wiki

Community
· Team
· Partners
· Contacts

JORAM maintenance release 5.0.9 (April 22, 2008)

Joram 5.0.9 is available in the CVS repository with tag JORAM_5_0_9. This release provides many features and changes:

New features and improvments

Adds a new UDP based network component.
Adds JMX based administration for JNDI implementation.
Enhancement in JMX use in an OSGI environment.
RA behavior in an HA colocated mode.
Javadoc and logging enhancements.

Bug fixes

NTransaction: No longer call System.exit in case of fatal errors.
JNDI: don't freeze the server in case of context loosing..

JORAM maintenance release 5.0.8 (February 12, 2008)

Joram 5.0.8 is available in the CVS repository with tag JORAM_5_0_8. This release provides many features and changes:

New features and improvments

Allows to choose the network component when adding a domain.
New HADistributedJndiServer component.
Allows administration through HA connection in XML Script.
Handling of expired messages in internal queue of MOM.
Use of RA with WebLogic server.

Bug fixes

Adding and removing a server in a PoolNetwork domain.
Starting and stopping a network component.
Right handling for ClusterDestination.
Allows server's synchronization during engine inactivity.
Cluster topic building is now an idempotent operation.

JORAM maintenance release 4.3.32 (February 12, 2008)

Joram 4.3.32 is available in the CVS repository with tag JORAM_4_3_32. This version is bundled in Jonas 4.9. This release provides many features and changes:

New features and improvments

New HADistributedJndiServer component.
Allows administration through HA connection in XML Script.
Use of RA with WebLogic server.

Bug fixes

Right handling for ClusterDestination.
Allows server's synchronization during engine inactivity.
Cluster topic building is now an idempotent operation.
Use of <XA><Tcp>ConnectionFactory objects with JNDI.

JORAM maintenance release 5.0.7 (December 19, 2007)

Joram 5.0.7 is available in the CVS repository with tag JORAM_5_0_7. This release provides many features and changes:

New features and improvments

Add MySQLDBTransaction and DerbyDBTransaction.
Best handling of TTL and priority of the JMS messages.
JMX enhancement: ClientSubscriptionMBean added.
Asynchronous subscription request.
Handling of socket binding either for Joram TCP connections and network components.
Handling of serialVersionUID.

Bug fixes

Removes NPE during getThreshold if threshold is not set.
Synchronization issue in Connection with id generation.
Handling of HA connection factories through JNDI.
Handling of [NOT] IN in selector.
DMQ behavior.

JORAM release 5.0.6 (September 25, 2007)

Joram 5.0 is available in the CVS repository with tag JORAM_5_0_6. This release provides many features and changes:

New features and improvments

New serialisation mechanism between client and server to allow the C/C++ client API: Xoram.
New architecture for destinations.
New architecture for ConnectionFactory.
Enhancements for the bridge destinations: XA, etc.
Enhancements for clustered destinations.
Implements loose coupling for distributed JNDI.
Improve AdministeredObject handling.

Bug fixes

Message retrieval in DMQ after a restart.
Persistance fault with administration messages on Windows.
Problems with Soap encoding.

JORAM maintenance release 4.3.30 (September 25, 2007)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_30. This release provides the following fixes and changes:

New features and improvments

Implements loose coupling for distributed JNDI.

Bug fixes

Message retrieval in DMQ after a restart.
Persistance fault with administration messages on Windows.
Problems with Soap encoding.

JORAM maintenance release 4.3.28 (April 26, 2007)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_28. This release provides the following fixes and changes:

Bug fixes

Sub-context creation through XML scripts.
JNDI binding of clustered objects through SOAP.

JORAM maintenance release 4.3.26 (March 27, 2007)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_26. This release provides the following fixes and changes:

New features and improvments

Adds clustering facilities in administered objects: connection factories and destinations.
Use of inheritance and reflection for generic handling of JNDI references.
Use an AbstractConnectionFactory factorizing code between connections factories.

JORAM maintenance release 4.3.25 (March 08, 2007)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_25. This version is bundled in Jonas 4.8.5. This maintenance release provides the following fixes and changes:

Bug fixes

Avoid useless socket creation on connection error (HttpNetwork component).
Bug fix in handling of byte array as object in BytesMessage.
Allow to fix SO_TIMEOUT on StreamNetwork.
Fixes in JMS message handling: avoid NPE if message's body is null, and catch NPE in Session.run to avoid MDB blocking.
Bug fixes in acknowledge handling of HttpNetwork.
toString and hashcode opttimization in Connection object.
Allows to asynchronously garbage the Transaction log file.
Fixes compatibilty issues with other JMS provider: allow to set JMSDestination with non Joram destination, and to convert messages with 'JMS_' properties.
Bug fixes: really remove messages on disk in clear and deleteMessage methods. Previously the messages come back after server retart.
Enhancements in mail destinations.
Bug fixes in SimpleNetwork. A synchronization issue may result in a message lost in case of network failures.
Adds periodic cleaning task for subscriptions.

JORAM maintenance release 4.3.22 (February 26, 2007)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_22. This version is bundled in Jonas 4.8.4. This maintenance release provides the following fixes and changes:

Bug fixes

Take in account topicAckBufferMax parameter in MessageConsumerListener.
Fix Jonas Bug#306288: Avoid NPE if the LogWriter of JCA connector is null.
Adds DeadMQueue.create methods allowing to internally name the queue. It fixes an issue with Jonas.
Apply a patch from Mark Anderson to add a timeout in Requestor.request.

JORAM maintenance release 4.3.21 (September 20, 2006)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_21. This version is bundled in Jonas 4.8 and Petals 1.0. This maintenance release provides the following fixes and changes:

Bug fixes

No longer removes durable subscription on consumer close (MDB undeploy).
Avoid NPE on Session.unsubscribe with null subscription name.
Work-around for JDK1.6 in ObjectMessage.
Fix NPE in RequestMultiplexer.cleanup (bug JOnAS #306110).

JORAM maintenance release 4.3.20 (August 03, 2006)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_20. This version is bundled in Jonas 4.8. This maintenance release provides the following fixes and changes:

New features and improvments

Allows activation of HA mode with Joram RA.
Dynamic loading of configuration file through the MBean.

Bug fixes

handling of exception in MDB onMessage method (bug JOnAS #305389).

JORAM maintenance release 4.3.19 (July 11, 2006)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_19. This version is bundled in Jonas 4.7.5. This maintenance release provides the following fixes and changes:

New features and improvments

XML export facilities for Joram's configuration.
Periodic cleaning task for queues.
Many improvments about JCA connector.

Bug fixes

Fix for SSL connection.
Fix for JDK1.5 XML generation.

JORAM maintenance release 4.3.18 (May 31, 2006)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_18. This maintenance release provides the following fixes and changes:

New features and improvments

Changes NTransaction to expose a repository interface; provides a File and DB implementation.
Adds a DBTransaction implementation of Transaction interface.
Adds multi-threading support in HttpNetwork.
Adds configuration for SO_TIMEOUT TCP parameter in JNDI.

Bug fixes

Fix for redeployment of JCA connector.
Run onException in a separate thread to avoid deadlock in connector onException method.
Many fixes to improve connection closure.

JORAM maintenance release 4.3.14 (March 19, 2006)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_14. This maintenance release provides the following fixes and changes.

New features and improvments

Adds SchedulerQueue.
Adds handling of expiration time in MOM.
Improvments in Network architecture.

Bug fixes

Many bug fixes in handling of messages error and DMQ.
Bug fix about connection close, improve cleaning and stop of Joram's connection.

JORAM maintenance release 4.3.12 (January 19, 2006)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_12. This maintenance release provides the following fixes and changes.

New features and improvments

Allows to bind Joram to a single IP address in multi-homed host. An optional IP address can be passed in argument of the Joram TCP or SSL service. Thank's to Alex Porras (MediaOcean) for its contribution.
Allows multiples 'client' in an Http(s)Network, the unique 'listen' server routes messages between 'client' servers.
Adds the HttpsNetwork component.
Adds a timeout property for jndi2 connection: its default value is 0, and its name fr.dyade.aaa.jndi2.client.SimpleNamingConnection.timeout.

Bug fixes

Report unknown destination to message producer, either throw an exception if the destination is local, or call the exception listener if any.
Avoid OutOfRange exception (DestinationPanel.setDestination) in administration GUI.
Adds the handling of queueMsgCount property in J2EE environment.
Correct the Ant target for SSL sample.
Avoid to load then store all messages contained in a queue at startup.
Soap serialization problem with Message, NPE if mapBody is null.

JORAM maintenance release 4.3.10 (November 3, 2005)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_10. This maintenance release provides the following fixes and changes.

New features and improvments

Basic XML scripting capabilities: it allows creation, deployment and JNDI binding of Destinations, Users and ConnectionFactories.
Adds PoolNetwork component in default packaging.

Bug fixes

Avoid endless retry during connection.
No longer throw a NPE in getMessageListener if none is set.

JORAM maintenance release 4.3.9 (October 25, 2005)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_9. This maintenance release essentially provides a bug fix, it is embedded in the last JOnAS build (4.6.1).

Bug fixes

Subscription behavior with nolocal attribute set.

JORAM maintenance release 4.3.8 (October 20, 2005)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_8. This maintenance release provides the following fixes and changes.

New features and improvments

Automatically process provider major and minor Version.
Use default version number from build.properties.
Removes '#' character in Message unique identifier.
Removes readMessage in QueueMBean in order to cut out dependancy to the JMS API. Replaces it by getMessageDigest, getMessageHeader and getMessageProperties.
Adds resetPropertiesRO method to Message class.
Use the ExceptionListener if any in cas of connection problem.

Bug fixes

Usage of connection's pool in Resource adapter.
Memory leak in Joram adpater. With maxWorks parameter set to 0 (no limit) the pool is not used, InboundSessions are alwaye created, inserted in the pool and never garbaged.
Fix Soap serialization problem with MapMessage.
Avoid NullPointerException in case of acknowledgment of an inexistent message.
Avoid sharing of message structure between different messages in MOM; clone the MessagePersistent and correctly set the message field.
Fix reliableClass property in getReference.

JORAM maintenance release 4.3.4 (August 3, 2005)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_4. This maintenance release provides the following fixes and changes.

New features and improvments

Performance improvements: management of transient message, saving of messages and agents.
Updates JGroups version.
Many JMX improvments.

Bug fixes

Colocated mode: clones message in sending, fix RO in receiving.
HA mode: Adds bag management for ClientSubscription.

JORAM maintenance release 4.3.1 (June 3, 2005)

This is a maintenance release. It is available in the CVS repository with tag JORAM_4_3_1. This maintenance release provides the following fixes and changes.

Bug fixes

Internal transactions: NTransaction behavior with big messages. Comments added to NTransaction javadoc. Statistics added. Use of lockfile is now configurable. Optimizations in the Engine, related to stamp savings for non-persistent messages.
JMS API : fixes in sendToDMQ method in DestinationImpl

JORAM 4.3 (May 17, 2005)

The Joram 4.3 final release is available in the CVS repository with the tag JORAM_4_3_0. It provides a lot of fixes and improvements.

New features

extended JMX management,
Performance improvments,
Handling of large message transmission (called swap out mode),
Complete SSL support with handling of encrypted client to server communications.

JORAM maintenance release 4.2.3 (May 13, 2005)

This is a maintenance release, the last one before version 4.3. It is available in the CVS repository with tag JORAM_4_2_3. This maintenance release provides the following fixes and changes compare to the 4.2.0 version (bug and fixes of maintenance release 4.2.1 and 4.2.2 are hereafter included)

Bug fixes

JMS Client API: Fix bug in ClientSubscription by avoiding multiple denies, fix bug in MessageConsumerListener by avoiding messages buffering in queue mode.
JMS Messages : Fix bug in Message.convertJMSMessage : no JMSException thrown if optional header (JMSX) are set in a non Joram message, just ignore.
Transactions and XA: Fix bug in Session setTransacted (deadlock) come from TX SUSPEND, add Joram version in start of JoramAdapter, fix bug in XAResourceMngr (deadlock).
Packaging: change traces in connector and add project name "joram" in build.xml, add JGroups library in shipping.
SOAP : Bug fix: Soap encode/decode.

JORAM 4.2 (March 31, 2005)

The Joram 4.2 final release is available in the CVS repository with the tag JORAM_4_2_0. It provides a lot of fixes and improvements.

The documentation has been updated and is available for download.

New Features and Improvments

Upgraded JMX management features : Servers list and status in SCServer, Right management in Joram's destinations.
Upgraded JDK 1.5 support
JAMT : support for dynamic configuration of the JORAM platform
Administration module: new operations to read/delete messages from subscriptions and queues.
Network communications: Many improvments and bug-fixes in NGNetwork.
Joram RA: Add util to configure the joram adapter resource. create new jar joram-config.jar and joram-raconfig.jar. modify ship.adapter, ship.remoteadapter and ship.jonasadapter. update jonas-ra.xml.

Bug fixes

JAMT : Closing the "abort dialog" aborts the running operation. Null pointer in popup listener
Joram client : Deadlock between message listener and concurrent close.Methods getMetaData from Connection and receiveNoWait from MessageConsumer throw an IllegalStateException if a connection failure occured (e.g. TCP failure).
Packaging : Adds jmxri.jar in classpath for samples/bin scripts.
Network Communication: Fix in HttpNetwork allowing the usage of a (non HTTP 1.1) proxy.
TCK Compatibility for Jonas : regression in TCK, null testing.

JORAM 4.2 RC2 (March 11, 2005)

The Joram 4.2 release candidate 2 is available in the CVS repository with the tag JORAM_4_2_RC2. It provides a lot of fixes and improvements.

New Features and Improvments

Upgraded JMX management features : Servers list and status in SCServer, Right management in Joram's destinations.
Upgraded JDK 1.5 support
JAMT : support for dynamic configuration of the JORAM platform
Administration module: new operations to read/delete messages from subscriptions and queues.
Network communications: Many improvments and bug-fixes in NGNetwork.
Joram RA: Add util to configure the joram adapter resource. create new jar joram-config.jar and joram-raconfig.jar. modify ship.adapter, ship.remoteadapter and ship.jonasadapter. update jonas-ra.xml.

Bug fixes

JNDI connection closure.
Joram client: fix automatic reconnection policy.
Selectors : Encoded string literals as UNICODE. Add joramSelector directory in org/objectweb/joram/shared/selector read joramselector.doc (HowTo generate the joram selector)
Network Communication: call server.moveToFirst(SocketAddress) until find the good socket (just for cluster use).
High Availability : Test cluster.properties.size() in the cluster configuration phase, in AgentServer.java. Replace serverCluster by server in a3config.dtd and update sample a3config.dtd no longer initialize 'Bag' agent in setState (HATransactionEngine).

JORAM 4.2 RC1 (January 10, 2005)

The Joram 4.2 release candidate 1 is available in the CVS repository with the tag JORAM_4_2_RC1. It provides new features as high-avaibility, dynamic configuration, and a lot of fixes and improvements.

The updated documentation, packaged version for download and more detailed announcement will be available soon on Joram web site.

New Features

High Availability Joram V4.2 provides the active replication of Joram servers and underlying agent servers, as well as replicated JORAM clients. It transparently handles network handover and server failover. This version currently relies on the use of JGroups.
Dynamic Configuration Joram V4.2 provide facilities to remotely add and remove Joram servers dynamically, using the Joram Administration API. This key feature, combined with upgraded JMX implementation, initiates a new set of management facilities for Joram.
Architecture and Performance improvements. Joram V4.2 provides a packaged version of a wide set of deep changes within the Joram and underlying bus architectures that lead to performance improvements compared to prior version V4.1. Communication protocols are concerned by this evolution, thus preventing backward compatibility with prior Joram versions.

Bug fixes

JMS message improvement, numerous bug fixes.

JORAM_4_1_5 (January 7, 2005)

This maintenance release is available in the CVS repository with the tag JORAM_4_1_5. It provides minors new features as dynamic configuration of logging and support for Java 1.5 or JMX. Except an important failure it should be the last 4.1.x version, the next release will be the 4.2 RC1 with high-avaibility and numerous improvements.

Feature improvements

JDK1.5 compatibility.
Add JMX management: server, engine, network, agent...
Transaction: Factorize definition in interface, allows to release a non-commited transaction
Configuration of logging might be changed dynamically at runtime.
Adds configuration of connection in ra-remote.xml

JORAM_4_1_4 (December 22, 2004)

This maintenance release is available in the CVS repository with the tag JORAM_4_1_4. This release contains some minor features and bug fixes (see below the history file).

It is also available for download and the documentation has been slightly updated.

Configuration improvements

Add configuration of connectingTimer, cnxPendingTimer and txPendingTimer in the connector.
Defines provider metadata in a unique class.
Set default transaction manager NTransaction in the connector.
JoramAdapter : remove scn:com/ prefix when we register a destination.

Bug fixes

invalid mesage removal in ClientSubscription.
Bug fixes in UserAgent.

JORAM_4_1_2 (November 9, 2004)

This maintenance release is available in the CVS repository with the tag JORAM_4_1_2. This release contains some minor features and bug fixes (see below the history file).

It is also available for download and the documentation has been slightly updated.

Performance enhancements

Changes in TCP connection to improve performances.

Bug fixes

Corrects mistakes in ra.xml and ra-remote.xml files.

Removes empty (and useless) <icon> </icon> tags.
Remove spaces and eof lines in the <xxx-class> tags and <xxx-interface> tags.

Fix bug (NullPointerException) in OutboundConnectionFactory.java, cxManager can be null.
Throws a StateException in setCtx(int key) if key <0 (ProxyImpl.java).

JORAM_4_1_1 (October 13, 2004)

This maintenance release is available in the CVS repository with the tag JORAM_4_1_1. This release contains some minor features and bug fixes (see below the history file).

It is also available for download and the documentation has been slightly updated.

New features and updates

Allows to fix inFlow value through ConnectionManager.inFlow property.
Allows change of default identity through JoramDfltLogin and JoramDfltPassword properties.
Major changes in the network architecture:
- Reconnection after persistancy failure,
- Deletion of old unused components: clock, update, etc.
- Adds PoolNetwork component (beta).
- Allows connection of reset(or non persistent) servers.
Allows swap out of messages in message consumer (MessageVector impl.)

Bug fixes

Bug fixes in RA descriptors.
Uses of JAXP classes and interfaces (xerces no more needed).
Bug fixes in TCP client/server connection.
Minor fixes in the ship and release processes.

JORAM 4.1 (September 14, 2004)

This version, integrated in JOnAS, succesfully passed the JMS test Suite of J2EE 1.4 TCK.

Modifications

Full featured JCA 1.5 RA
Clustered Queues for load-balancing purposes, in addition to existing clustered Topics

JORAM_4_0_5 (August 2, 2004)

This maintenance version is integrated in the latest JOnAS release available on CVS (JOnAS 4.1.3). This maintenance version succesfully passed the JMS test Suite of the J2EE 1.4 TCK

CVS base, no tag

Getting Joram through CVS without specifying a tag allows to get the latest tagged version with the latest corrections and updates.

Modifications (latest: May 17, 2004)

Config file extension changed to .cfg; slight change in the tracing module; better handling of a stopping adapter, by unregistering all mbeans. Updated package is org.objectweb.joram.client.connector.
Many improvements in the org.objectweb.joram.client.connector package for better handling the state management of the wrapping Outbound objects.
NbMaxAgents variable set when launching a non persistent server through the adapter, so that no agents swapping is performed (updated class: org.objectweb.joram.client.connector.JoramAdapter).
Admin file searched in the class loader if path not set, in org.objectweb.joram.client.connector.JoramAdapter.

Corrected bugs (latest: May 11, 2004)

Dependency of a client class to a server class (org.objectweb.joram.shared.client.QBrowseReply). Updated classes are org.objectweb.joram.shared.client.QBrowseReply and org.objectweb.joram.mom.proxies.ProxyImpl.
org.objectweb.joram.client.jms.admin.AdminModule.connect() not working with XA factories, found by Bradely Mazurek. The class has been updated.

JORAM_4_0_2 (May 4, 2004)

This maintenance version should be integrated into JOnAS 4.1

Modifications (latest: April 28, 2004)

Submission of the fr.dyade.aaa.jndi2.scn package allowing to use serveral JNDIs as documented here (section 3.2).
Destinations' administrative names are now returned when calling the AdminModule.getDestinations monitoring methods, and wrapped into the corresponding Destination instances.
Large update of the XA classes implementation for a better XA support (for example, recovery is now provided). Submissions occured in the org.objectweb.joram.client.connector, org.objectweb.joram.client.jms, org.objectweb.joram.mom.proxies, and org.objectweb.joram.shared.client packages.
Following the renaming of kjoram.jar to joram-kclient.jar, the samples/src/kjoram directory should be updated.

Corrected bugs (latest: April 28, 2004)

Broken SOAP connections not detected, found by Christian Neudorfer. The corrected classes are org.objectweb.joram.client.jms.soap.QueueSoapConnectionFactory, org.objectweb.joram.client.jms.soap.SoapConnectionFactory, org.objectweb.joram.client.jms.soap.TopicSoapConnectionFactory, and org.objectweb.joram.client.jms.admin.ObjectFactory.
Transacted sending not working from kJoram client, found by André Bottaro. The bug is corrected, the packages to update are com.scalagent.kjoram.ksoap and com.scalagent.ksoap.

joram4_0_1 (March 23, 2004)

This maintenance version is integrated within JOnAS 4.0

Modifications

New logging configuration, based on JavaLog rather than on log4j. Updated file is samples/config/a3debug.cfg.
New JORAM shipping; generated jars now are:

joram-client.jar: client library
joram-mom.jar: server library
joram-shared.jar: client/server shared library

Corrected bugs

Blocking admin disconnection, found by Martin Thompson. When disconnecting an administrator from a stopped server, the disconnect() call would block and never return. The bug is corrected, the updated class is org.objectweb.joram.client.jms.admin.AdminModule.
Improper construction of the mom.jar library, found by Nigel Rantor. The fr.dyade.aaa.jndi2.distributed package was not included in the jar construction, preventing any distributed JNDI conf to work. An updated joram.xml build file has been submitted under src/.
kJoram compiling issues, found by Stanley. Due to improper build setup and JORAM 4.0 new connection management, kJoram client classes could not be compiled and used anymore. Many corrections have been made in the CVS tree, to get them please update com/scalagent.
Blocking connection request, found by Piero de Salvia. In case a user does not exist, trying to open a connection for this user would block instead of throwing a security exception. The bug is corrected, the updated class is org.objectweb.joram.mom.proxies.OpenConnectionNot.
Improper connection close, found by Christian Neudorfer. Due to a static timer, it was not possible to open a new connection after having closed one in a same process. Bug is corrected, the impacted classe is org.objectweb.joram.client.jms.Connection.
SOAP connections failures never detected, found by Christian Neudorfer. Despite the setting of the connection pending timer, a failing SOAP connection was never detected due to an improper reconstruction of SOAP connection factories retrieved from JNDI. The bug is corrected, the impacted classes are org.objectweb.joram.client.jms.soap.SoapConnectionFactory, org.objectweb.joram.client.jms.soap.QueueSoapConnectionFactory, and org.objectweb.joram.client.jms.soap.TopicSoapConnectionFactory.
Incorrect target for launching JORAM as a SOAP service in the samples build.xml file, found by Christian Neudorfer. The target still refers to the old fr.dyade.aaa.joram package instead of refering to org.objectweb.joram.client.jms. An updated version has been submitted in CVS.

joram4_0_0 (February 13, 2004)

This version provides new functionnalities (collocated client-server communication protocol, universal JMS bridge feature, distributed JNDI server) and introduces a new sources architecture.

Modifications

Packages under fr/dyade/aaa/joram and fr/dyade/aaa/mom have moved under org/objectweb/joram/client, org/objectweb/joram/mom and org/objectweb/joram/shared. The main evolutions occured in these latest packages, as well as in fr.dyade.aaa.agent and fr.dyade.aaa.jndi2.

joram3_7_1 (February 3, 2004)

This version has been tagged for integration within JOnAS 3.3.6.

Modifications

ObjectMessage optimization [2]. When a getObject() call fails, an other trial is performed using the context class loader. This again, for improving JORAM's behaviour within an application server. Impacted class is fr.dyade.aaa.joram.ObjectMessage.
ObjectMessage optimization [1]. The wrapped object in an ObjectMessage instance is not automatically deserialized when reaching the consumer's connection, but only when calling the getObject method. This for improving the behaviour of JORAM within application servers. The updated classes are fr.dyade.aaa.mom.messages.Message and fr.dyade.aaa.joram.ObjectMessage.
New flow control mechanism. In order not to overload a JORAM server with incoming messages, it is possible to set a maximum authorized flow (in messages / second). This setting is done in the configuration file, at the ConnectionFactory service level. For example, for limitating the flow to 50 messages per second: <service class="fr.dyade.aaa.mom.proxies.tcp.ConnectionFactory" args="16010 root root 50"/>. The updated classes are fr.dyade.aaa.mom.proxies.tcp.ConnectionFactory and fr.dyade.aaa.mom.proxies.ProxyImpl.

Corrected bugs

Expired message monitored as pending messages. When monitoring a queue's messages, the expired messages are now removed (and sent to the DMQ, if needed), and thus not listed as pending messages anymore. The updated class is fr.dyade.aaa.mom.dest.QueueImpl.
Expired "receive" requests monitored as pending requests, as described here. When monitoring a queue's requests, the expired requests are removed and thus not listed as pending requests anymore. The updated class is fr.dyade.aaa.mom.dest.QueueImpl.
Automatic deny request sent to already deleted temporary queue, found by Gerald Schröder. This bug had no influence on a server's operations, however it generated the logging of ERROR messages. It is corrected, the class to update is fr.dyade.aaa.mom.proxies.ClientContext.
NullPointerException thrown by a single user's proxy which subscribed to various leafs of a same topic hierarchy, found by Mark Anderson. This bug is due to messages not being cloned in the topic leafs and to an improper processing of duplicated incoming messages. It has been corrected, the impacted classes are fr.dyade.aaa.mom.dest.TopicImpl and fr.dyade.aaa.mom.proxies.ClientSubscription.
Improper message delivery in a topic hierarchy when set on a single server, and when consumers subscribe to various leafs of the tree. Messages were not appropriately cloned and this resulted in subscribers never getting any message. The bug is corrected and the impacted class is fr.dyade.aaa.mom.dest.TopicImpl.
Messages delivered in an incorrect order after a rollback or disconnection, found by Franck Delporte. In some cases messages were delivered in an order different from the original delivery order after a client rollback or disconnection. The bug is corrected, the updated classes are fr.dyade.aaa.mom.dest.QueueImpl, fr.dyade.aaa.mom.messages.Message, fr.dyade.aaa.mom.proxies.ClientSubscription, fr.dyade.aaa.mom.proxies.ProxyImpl.
Message delivered twice, found by Dirk Muthorst. In a very specific case, persistent messages might be duplicated by the server. It occured when a message which arrived for example on a queue, was persisted alone, then consumed and denied but with other messages. Then it would be persisted again with the group of denied messages, its original individual persistence file being kept. Thus, the message would finaly be consumed twice after a server recovery (tricky!). The bug is corrected and the updated class is fr.dyade.aaa.mom.messages.PersistenceModule.

joram3_7_0 (November 3, 2003)

This release introduces a graphical administration and monitoring tool.

Modifications

Creation of a new sources branch: org.objectweb.joram, destinated to contain the JORAM client and MOM sources.
Submission of a new graphical administration tool engineered by Alexander Fedorowicz, in org.objectweb.joram.client.tools.admin.

Corrected bugs

Recovery issue, found by Dirk Muthorst. When stopping a JORAM server during a PTP exchange, and re-starting it, a NullPointerException was happening from time to time. This was due to the fact that the consumer's proxy would deny twice a same message (the message currently exchanged when the server stops), and that the queue could not handle this double deny. This bug is corrected, the corrected class is fr.dyade.aaa.mom.dest.QueueImpl.
NullPointerException occuring when requesting the defaut DMQ settings of a server in a distributed configuration; corrected class is fr.dyade.aaa.mom.dest.AdminTopicImpl.

joram3_6_3 (October 14, 2003)

This release is integrated into JOnAS 3.3.1.

Modifications

New possibility to create JORAM destinations with a name, so that such destinations may be permanently retrieved independently of JNDI. The modified classes are fr.dyade.aaa.joram.admin.AdminItf, fr.dyade.aaa.joram.admin.AdminImpl, fr.dyade.aaa.mom.admin.CreateDestinationRequest and fr.dyade.aaa.mom.dest.AdminTopicImpl.
New build.xml file for simplier building and cleaning targets.

Shipping JORAM: ant ship.joram
Shipping kJORAM: ant ship.kjoram
Cleaning the distribution: ant clean

Corrected bugs

Impossible to bind TopicSoapConnectionFactory objects when using JORAM JNDI through the SOAP protocol, found by Sabrina Tardelli. The bug is corrected, the impacted classes are fr.dyade.aaa.joram.soap.TopicSoapConnectionFactory and fr.dyade.aaa.joram.soap.QueueSoapConnectionFactory.

joram3_6_2 (September 22, 2003)

This release is integrated into JOnAS 3.3.

Modifications

Modification of AgentServer and NameService initialization allowing to stop a server (AgentServer.stop()), intialize it (AgentServer.init(...)) and start it again. In NullTransaction mode should allow to re-initialize completely the server. Impacted packages are fr.dyade.aaa.agent, fr.dyade.aaa.ns and fr.dyade.aaa.util.

Corrected bugs

Invalid creation of a s$i persistence root when running JORAM in transient mode; impacted classes are fr.dyade.aaa.agent.AgentServer, fr.dyade.aaa.util.ATransaction and fr.dyade.aaa.util.NullTransaction.

joram3_6_1 (September 11, 2003)

This release introduces MBean classes for standard JMX management.

Modifications

JMX MBeans introduced for the management of the JORAM destinations and users. The "MBeanified" destinations are still hosted by the fr.dyade.aaa.mom.dest package (more packages have been impacted by the support of JMX). This new feature is not documented yet.

Corrected bugs

Destinations were not removed from internal lists when being deleted. Bug corrected in fr.dyade.aaa.mom.dest.AdminTopicImpl.
Bug related to the MessageConsumer noLocal attribute, found by Tony Thompson. The bug has been corrected, the impacted class is fr.dyade.aaa.mom.proxies.ClientSubscription.
Invalid precedence on naming properties (as noticed here). The correct order is now taken into account. Modifications occured in the fr.dyade.aaa.jndi2 package.
Blocking AdminItf.stopServer method (as noticed here). The processing of this method disapeared from the administration topic server side since release 3.5, probably due to an invalid CVS merge. The code is back now in class fr.dyade.aaa.mom.dest.AdminTopicImpl.

joram3_6_0 (August 7, 2003)

This version provides the kJORAM libraries allowing J2ME applications to connect to the JORAM platform.

Modifications

Major modifications occured to the CVS tree. kJORAM sources are located in the src/com/scalagent directory. JORAM samples have been moved to the samples/src/joram directory, and the configuration files directory is now samples/config. The kJORAM samples are located in the samples/src/kjoram directory.
Improvement of the closing of a dead connection; particularly, calling Connection.close() within the onException method of an ExceptionListener would generate an infinite closing loop. The impacted class is fr.dyade.aaa.joram.Driver.
setConfig(...) method in fr.dyade.aaa.agent.AgentServer has now a public access for configuration purposes; calling it after the server has been started throws an exception.

Corrected Bugs

ClassCastException occuring in fr.dyade.aaa.mom.proxies.ProxyImpl when subscribing to a non-readable topic, found by Prashanth Kasturi. The bug is corrected, the impacted class is fr.dyade.aaa.mom.proxies.ProxyImpl.