|
Bug No.
|
Description
|
|
COS-69
|
Notification Service: Fix for delayed event delivery: the last event sent by the event channel to a proxy supplier would occasionally not be sent on to the consumer until another event was passed on by the event channel.
|
|
COS-46
|
Timer Event Service: Changed log level for eventInterface restoring error and added possible NullPointerException handling.
|
|
COS-45
|
Notification Service: Dropped logging level for filtered event messages from INFO to DEBUG.
|
|
COS-42
|
Timer Event Service: Added timer event handler cleanup option when the Timer
Event Service starts up to prevent a possible Service crash on startup.
To switch this cleanup option on, add the
DOF.TimerEventService.CleanFailedEvents=true JVM flag to the
Time Service JVM.Flags configuration parameter via the GUI manager or by editing
the TimeService.xml file.
|
|
COS-33
|
Notification Service: Filters created using an event channel's default filter factory function correctly post-restart when the Notification Service is not using a fixed port and the IMR is not running.
|
|
COS660 and COS663
|
Notification Service: Fix threads issue in disconnect callback routines of proxy consumers / suppliers in Notification Service.
|
|
COS658
|
Notification Service: On a service restart without the IMR and without using a fixed port, the default_filter_factory(), MyFactory(), MyChannel() and MyAdmin() methods now function correctly.
|
|
COS657
|
Notification Service: Fix issue where FilterFactory used incorrect port on a service restart.
|
|
COS637
|
Notification Service: Fix synchronisation issue to prevent double object loading.
|
|
COS620
|
Tools: Fix for nsMgrTool (Name Service Manager Tool) initialisation.
|
|
COS611
|
Notification Service: Fix for ConcurrentModificationException in JtoRegistryImpl.
|
|
Bug No.
|
Description
|
|
COS579
|
Notification Service: Fix issue where MaxQueueLength did not take into account the size of the SequenceProxyPushSupplier's buffer, which meant that MaxQueueLength could be exceeded.
|
|
COS573
|
General: Add the Tomcat java object.
|
|
COS565
|
Log Service: Fix issue where an object being destroyed does not save the change in its parent's persistent state.
|
|
COS564
|
Log Service: Improve Service restart by cleaning up a Proxy Supplier when a narrow to its consumer fails with an OBJECT_NOT_EXIST exception.
|
|
COS559
|
Notification Service: Additional information added to log messages within filtering mechanism to make identification of channel, proxy and filter possible.
|
|
COS558
|
Notification Service: Improve synchronisation within the Service to prevent a ConcurrentModificationException.
|
|
COS546
|
Tools: Add quotes to arguments for adminMgrTool, configGen, node and server utilities so that arguments that contain spaces can be used.
|
|
COS539
|
Notification Service: Fix so that a zombie Notification Service process is no longer created when the Notification Service fails to start.
|
|
COS533
|
Notification Service: Fix issue where MaxEventsPerConsumer did not take into account the size of the SequenceProxyPushSupplier's buffer, which meant that MaxEventsPerConsumer could be exceeded.
|
|
COS533
|
Notification Service: Fix issue so that a SequenceProxyPushSupplier that has not been connected to a consumer now ignores events, rather than stores events.
|
|
COS531
|
Notification Service: Reduce the number of non-purgable CORBA Objects the TimeService and TimerEventService use to reduce the load on the object cache.
|
|
COS512
|
Time Service: The TimerEventService restart process has been altered to deal with the exception that is produced when corrupt data is encountered. An error message is logged and the corrupted file is cleaned from the data directory. The corrupt data is ignored and the event is not processed.
|
|
COS499
|
Log Service: When the Log Service is stopped and restarted, the log is off duty. This happens with VisiBroker but not JacORB. The log should not be off duty.
|
|
COS497
|
Name Service: When bind_new_context () is called on a context which already exists, an AlreadyBound exception is correctly thrown. However, extra files are incorrectly created in the jndi directory.
|
|
COS495, 486 and 446
|
Name Service: Fix issue where a reference to a Naming Context was stored in a cache of limited size and could be incorrectly removed from the cache, resulting in a "Could not find ctx to remove" error.
|
|
COS491
|
General: Add a time delay to fix an issue where a Windows machine is rebooted, the OpenFusion Notification Service is started as a Windows Service and fails to start due to a timing issue with the JacORB imr Windows Service.
|
|
COS431
|
Notification Service: Fix an issue where data becomes corrupted, the service does not restart and a zombie process remains. This is resolved by doing the following: establish if the data is corrupt and if it is, do not allow the service to restart, add a message to the Notification Service log file to state that the data is corrupt and the service should be restored before restarting the service.
|
|
COS392
|
Name Service: Fix for "Attempt to register object with duplicate id" message, which occurs occasionally when the Name Service starts, after being stopped and started several times under heavy load.
|
|
Bug No.
|
Description
|
|
COS426
|
Time Service: When a job is scheduled in the Time Service and the Time Service is restarted, the job does not start at the scheduled time.
|
|
COS421
|
Time Service: An IllegalStateException occurs when using a persisted TimerEventHandler after a service restart.
|
|
COS413
|
Notification Service: CPU usage of the Notification Service is unexpectedly high.
|
|
COS412
|
Log Service: A consumer stops receiving events after the Log Service and supplier are restarted.
|
|
COS403
|
Notification Service: A sequence proxy push supplier can perform two push calls
concurrently to the same consumer.
|
|
COS391
|
Administration: The Log manager does not display the numbers of suppliers and consumers correctly.
|
|
COS383
|
Administration: On Windows, the OpenFusion installation process does not create shortcuts in the Start Menu.
|
|
COS340
|
Administration: adminMgrTool does not accept arguments beginning with a minus sign, for example, -Xmx100M
|
|
COS300
|
Notification Service: Logging level has been changed from WARN to INFO for an exception that occurs from the Filter code when processing a constraint string that is specified in short-hand notation to match the behaviour for fully-qualified constraint expressions.
|
COS249
|
Tools: From VisiBroker 5.2 upwards, if the server-side security portable interceptor is enabled then the consumer browser does not receive events and errors occur in the log file.
|
|
Bug No.
|
Description
|
|
COS365
|
General: The services won't run on Windows 2000 because the node.bat program returns an "input too long" exception if the path to the OpenFusion distribution is too long and contains spaces.
|
|
COS363
|
Notification Service: If events arrive in intervals just short of the pacing interval, the pacing interval is constantly rescheduled and does not trigger as expected.
|
|
COS362
|
Notification Service: Reconnect count for a sequence proxy consumer shows incorrect numbering.
|
|
COS355
|
Notification Service: A deadlock occurs when creating one channel and destroying another at the same time.
|
|
COS353
|
Notification Service: com.prismt.cos.CosNotification.FilterImpl is obfuscated, unlike in previous versions, so this class cannot be extended.
|
|
COS351
|
Notification Service: On a restart, the service now reactivates all channels, admins and proxies, which makes the service behave similarly to v3 and v2.5.
|
|
COS350
|
Notification Service: When 400 consumers connect to the Service, occasionally a consumer stops receiving events.
|
|
COS333
|
Notification Service: Messages are not filtered correctly when the Notification Service and a persistent consumer restarts.
|
|
Bug No.
|
Description
|
|
COS334
|
Notification Service: Additional logging information is required on a per channel / proxy basis for event discards, event count and proxy disconnect.
|
|
COS332
|
Notification Service: When the Service is stopped and restarted before a channel, with the MaxMemoryUsage QoS set, is destroyed, this channel does not get destroyed correctly and a NullPointerException occurs.
|
|
COS319
|
Notification Service: Intermittent CORBA timeout occurs with a client of the Notification Service.
|
|
COS312
|
Notification Service: The oracle database can report a resource deadlock when an event is deleted.
|
|
COS309
|
Notification Service: NullPointer exception when using the AdminMgrTool -aSing option.
|
|
COS260
|
Notification Service: Problem restarting Notification Service with events in the database that are to be delivered on restart.
|
|
Bug No.
|
Description
|
|
010N
|
Licensing: If a service cannot start due to licensing an appropriate message is now written to the log file.
|
|
015D
|
Notification Service: Slow push to a sequence consumer due to PacingInterval.
|
|
0169
|
Notification Service: Events may not be delivered when using a low pacing interval value and the consumer is slow to respond.
|
|
018X
|
Installer: Command line installation required java.awt classes.
|
|
019W
|
Notification Service: Event delivery in a channel that has been idle may be delayed.
|
|
01AA
|
Administration: Enhanced method of setting VISIBROKER-52 timeout properties. See Known Issues for further information.
|
|
01AM
|
Administration: Unable to create another service in another domain using the Administration Manager.
|
|
01AQ
|
Notification Service: Limitations on number of event channels when using Oracle persistence.
|
|
01B6
|
Notification Service: A channel deadlock occurs when a consumer is slow to respond to a push call.
|
|
01BR
|
Notification Service: Resolve deadlock when using badly behaved sequence consumers.
|
|
01CH
|
Notification Service: The event channel id does not appear in the log file.
|
|
01CJ
|
Notification Service: A deadlock occurs due to slow push_structured_events calls.
|
|
01CU
|
Notification Service: An unresponsive push call causes the Service to deadlock.
|
|
01CY
|
Notification Service: A proxy causes a blocking problem in the Service.
|
|
COS284
|
Notification Service: MaxQueueLength admin property does not work correctly. The event channel does not display the correct number of undelivered events in the proxy suppliers.
|
|
01DK
|
Notification Service: Sequence proxy push supplier deliveries via the pacing interval fail and the Service blocks.
|
|
01DO
|
Notification Service: A push_structured_event call causes the Service to block.
|
|
01DY
|
Notification Service: Channel locks when the hosts file on a server has an entry for the consumer's machine, but the IP address in that entry is incorrect.
|
|
Bug No.
|
Description
|
|
00U5
|
NotificationService: When calling the Event Channel Factory's
get_event_channel method after you restart the service
an org.omg.CORBA.OBJECT_NOT_EXIST exception is thrown.
|
|
00XM
|
Notification Service: On restart of the service, the IOR is not
updated.
|
|
00ZF
|
NotificationService: Updated known issues to highlight issue of
'batched' events (when using auto-sequencing) can still be amended on the client
side before they are sent. Auto-sequencing functionality is now switched off by
default.
|
|
011P
|
NotificationService: New known issue added to explain potential difference
between v4 CORBA Services and previous versions when
receiving an org.omg.CORBA.OBJECT_NOT_EXIST.
|
|
013Y
|
NotificationService: Invalid JDBC properties cause the service to
continually try and start. New properties have been added to allow configuration
of the service startup to avoid this problem;
"JDBC Connection Attempts" and "JDBC Connection Retry Interval".
These properties are fully documented in the System Guide.
|
|
0145
|
Notification Service: java.lang.NullPointerException
when using local filters.
|
|
0156
|
Time Service: Object purging not correctly removing objects, thus
causing the service to exhaust memory.
|
|
017I
|
Name Service: On start-up, if a corrupt IOR is written due to lack of
file space the service will not re-start after new disk space made available.
|
|
017Y
|
Notification Service: When a PC goes into standy-by mode, it can cause
the Notification Service to hang.
|
|
Bug No.
|
Description
|
|
00X5
|
Notification Service: Event delivery stops completely for a persistent
sequence consumer when an event delivery failure is detected.
|
|
00XB
|
Configuration: Added display property value to the AdminMgrTool
script.
|
|
00XO
|
Notification Service: Proxies display their channel in log messages.
|
|
00Y5
|
Notification Service: SequenceProxyPushSupplier corrected to
prevent deadlock when PacingInterval QoS in use.
|
|
00Y9
|
Trading Service: withdraw_using_constraint does not appear to remove offers correctly.
|
|
00YD
|
Notification Service: Rolling log re-enabled by removing detailed loggers.
|
|
00YT
|
Naming Service: Improved usage of Naming Service Manager Command Line Tool.
|
|
00YX
|
Notification Service: SequenceProxyPushConsumer corrected to
prevent deadlocks.
|
|
00ZH/010Y
|
Notification Service: Memory leaks corrected in creation and
deletion of Admins and Proxies.
|
|
00ZV
|
Notification Service: Supplier xx threw an exception
while freeing memory: java.lang.NullPointerException error fixed.
|
|
010X/014H/016A
|
Notification Service: Notification Service hangs when receiving
timeout exceptions.
|
|
010Z
|
Notification Service: Notification Service uses a lot of CPU
in debug mode.
|
|
011Q
|
Notification Service: Notification Service can hang during Event
Channel destruction.
|
|
011O
|
Notification Service: Memory leak fix for events that arrive at the
proxy supplier in the interval between its consumer being killed and
the proxy then destroying itself.
|
|
029C
|
Installation: On installation the install directory is added
to the Windows registry:
HKEY_LOCAL_MACHINE->Software->PrismTech->OpenFusionV(X)->InstallDir
|
|
013Y
|
NotificationService: Invalid JDBC properties cause the service to
continually try and start. New properties have been added to allow configuration
of the service startup to avoid this problem;
"JDBC Connection Attempts" and "JDBC Connection Retry Interval".
These properties are fully documented in the System Guide.
|
|
Bug No.
|
Description
|
|
00XU
|
Notification Service: Timeout and transient exceptions occur after service restart.
|
|
00JU
|
Using AdminMgrTool -d results in error message
"localhost was unexpected at this time".
|
|
00TA
|
Naming Service:
nsMgrTool updated to handle '.' and '/' characters in output.
|
|
00UW
|
Trading Service: RegisterImpl::withdraw_using_constraint ()
now withdraws offers of the supplied type and also its subtypes, which match the supplied
constraint, to copy the default behaviour of Lookup::query ().
|
|
00U3
|
When installed with JacORB, the JacORB properties file contains default
corbaloc entries for the installed CORBA Services.
|
|
00V1
|
Notification Service: Incorrect XML parser being invoked.
See known issues.
|
|
00V5
|
Notification Service: IMP_LIMIT CORBA System exception
is not thrown when the AutoSequence Qos are turned off.
|
|
00W4
|
Notification Service: Removal of references to Dead Letter Drop
functionality in the Notification Service User Guide.
|
|
00WW
|
Name Service: NotFound exception not fully reporting
rest_of_name member.
|
|
00X6
|
Name Service: UNKNOWN exception being reported
incorrectly when NotFound exception should be thrown.
|
|
00X7
|
Installation: Installation problems when installing just Naming
and JacORB14 packages.
|
|
01X8
|
Installation: OF_ADMIN_URL now defaults to OF_DOMAINS_URL. This
does not affect default behaviour, but when the <install_dir>/domains
directory is moved, the Administration Manager will automatically pick
up it's properties from the new domains directory.
|
|
00XK
|
Trading Service: Trading Service would not start with HSQLDB.
|
|
Bug No.
|
Description
|
|
0003
|
Notification Service: Client application hangs on a call of the
operation "disconnect_structured_push_consumer.
|
|
00PY
|
Installation problems when trying to install JacORB14 from the command line.
|
|
00Q4
|
The -x option does not work with the server script does not work.
|
|
00Q5
|
The -halt option is missing from the server script.
|
|
00Q6
|
Notification Service: Add button missing from GUI for adding
information to the remaining body of an event.
|
|
00QN
|
Known issues in release notes enhanced to point out Notification Service
resolve name for installations on VisiBroker-52.
|
|
00R7
|
CORBA Services would not run as Windows Services.
|
|
00RB
|
Documentation - Incomplete list of Notification Service QoS Properties.
|
|
00RD
|
Documentation - The section on instrumentation mentions DeliveryQueueThreshold
but this is not in v4.
|
|
00RI
|
Notification Service: The MaxInactivityInterval QoS is missing
from the list of QoS Properties on the channel of the GUI.
|
|
00RJ
|
Unable to install in C:\Program Files\PrismTech\OpenFusion on Win 2000.
|
|
00RK
|
Documentation error - Product Guide refers to version 2.5.
|
|
00RL
|
Notification Service: Problems with discard when priority discard
order policy used.
|
|
00RO
|
Notification Service: Problems with discard when FIFO discard
order policy used.
|
|
00RQ
|
Notification Service: AutoSequence QoS not declared in IDL.
|
|
00RR
|
Notification Service: System Exception when a proxy is
disconnected using the Notification Service Manager GUI and the
NotificationService is running on a fixed port.
|
|
00RZ
|
Notification Service: Clarification on QoS settings for proxies.
|
|
00S0
|
Notification Service: Events with a timeout of zero in the variable header incorrectly
expire immediately.
|
|
00S1
|
Notification Service: Memory leak when sending events with timeouts.
|
|
00S4
|
Notification Service: Events with timeouts are not discarded when received only
when they timeout.
|
|
00SG
|
Notification Service: Performance issues when sending events with timeouts.
|
|
00U5
|
Notification Service: On VisiBroker-52, a call to the
get_event_channel method on the
event channel factory after a service was restarted threw an
org.omg.CORBA.OBJECT_NOT_EXIST exception.
|
|
00UE
|
Notification Service: Creating many consumers causes the service to
hang.
|
|
00UO
|
Naming Service: componentToIns added to Name Service API for
convenience.
|
