Back to Main Page
PrismTech has added a number of valuable features to OpenFusion JacORB that are not available in the standard Open Source JacORB distribution. These features include:
The new OpenFusion Implementation Repository (IMR) is used by OpenFusion JacORB to locate and activate CORBA object implementations. The new OpenFusion IMR was designed so that it can also be used to locate object implementations based on OpenFusion TAO or OpenFusion e*ORB. The OpenFusion IMR was designed to provde a single unifying IMR that can be used across OpenFusion ORBs. However, in this initial release of the OpenFusion IMR, support will only be provided for CORBA servers written with OpenFusion JacORB. The OpenFusion IMR provides a number of advanced features including:
The jacorb.properties file now includes references to allow transparent corbaloc URLs for the OpenFusion CORBA Services.
The jacorb.properties file now includes new properties to limit the thread used for client and server side connections. See the programming guide for more information on jacorb.connection.client.max_receptor_threads, jacorb.connection.server.max_idle_receptor_threads and jacorb.connection.server.max_receptor_threads.
Initially jacorb provided a thread pool per POA. Using the new property "jacorb.poa.thread_pool_shared" allows one thread pool per JVM instance.
Option added to IDL compiler that will generate toString() and equals() methods on generated stubs for Structs. (Added JacORB 2.1.3+)
Under certain platforms (e.g. J2ME CDC platforms) when the JSSE initializes it's random number generator it may spawn a large number of threads and/or ORB initialisation is slow.
OpenFusion JacORB comes with a plugin system to resolve this issue.
An implementation of the
can initialise SecureRandom as required. Two examples are provided in
the org.jacorb.security.ssl.sun_jsse package in the JacORB source code.
(Added JacORB 2.1.3+)
The jacorb.properties file now includes new properties to allow servers and clients to be kept alive. See the programming guide for more information on jacorb.connection.server.keepalive and jacorb.connection.client.keepalive. (AddedJacORB 2.1.3+)
The jacorb.properties file now includes new properties to allow
a developer to create listeners to monitor TCP and SSL connections.
The developer has to implement an interface (that uses the Java
EventListener pattern) in order to receive notifications upon e.g.
TCP connections, SSL sessions.
See the programming guide for more information on
JacORB Network Event Logging. (Added JacORB 2.1.3+)
TCPConnectionEvent and SSLSessionEvent extended to include a method to return the local IP. (Added JacORB 126.96.36.199+)
To allow developers to plug-in their own java.security.SecureRandom initialisation when using SSL. See the programming guide for more information on jacorb.security.randomClassPlugin. (Added JacORB 2.1.3+)
A new property
jacorb.enhanced_thread_name has been added to configure
additional information for threads. Specifically, it adds connection endpoints and time
(in milliseconds) that the thread started to the Thread name.
See the programming guide for more information. (Added JacORB 2.1.3+)
Change to API for SSLSessionEvent to receive and provide cause of Exception. SSL logging also provides exception cause. (Added JacORB 2.1.3+)
openfusioninstalls the distribution to the
/opt/openfusiondirectory and an associated script called
/etc/init.ddirectory to ensure that the services are run as Unix services on machine boot.
serviceWrapper.shis installed with the RPM into the
/opt/openfusion/bindirectory. This script is responsible for starting the JacORB ImR and OpenFusion Services, detecting multiple start attempts, configuring a timeout and detect if a Service is already running. This script takes the following options:
/etc/init.d/openfusion -start(or reboot the machine) which calls onto the
serviceWrapper.shscript with the -start option.If you want to configure the timeout value, edit the
openfusionscript to put -t <timeout> before -start.
openfusion script supports
chkconfig and the services are active in levels 2,3,4,5. The script executes last in the boot sequence (or first when shutting down).