Category: Connector
Status: Closed

Severity: HIGH
Reported against release: 0.8
Fixed in release: 0.9

PROBLEM:

If the OpenJMS Server is not up and a service is either published
or subscribed that uses the OpenJMS connector,
a NullPointerException is thrown.

The desired behavior is to keep trying until the JMS service
becomes available.

Consider a scenario where a service publisher or subscriber comes up 
before the OpenJMS server, users would like to see a retry of the 
connection until the server comes up. 

The idea is to eliminate a specific sequence of bringing up
services. We don't want to tell an operator that the OpenJMS server 
must be installed and running first BEFORE other services are made 
available.

------- added 01/07/02 ---------

After doing some further analysis it would seem that the service is 
still being published even though there is no OpenJMS server running.  
The following stack trace shows the failure.

java.rmi.RemoteException: Connect exception
	at 
com.mot.openwings.connector.asynchronous.openjms.broadcast.BroadcastConn
ectorPublisherProxyImpl.connect
(BroadcastConnectorPublisherProxyImpl.java:221)
	at 
com.mot.openwings.component.jini.EventServiceManager.publishService
(EventServiceManager.java:72)
	at com.mot.openwings.component.jini.JiniComponent.publishService
(JiniComponent.java:418)
	at com.gd.dcgs.uav.ParserWrapper.(Unknown Source)


------- added 01/08/02 ---------
This defect should also be worked in conjunction with 3915 "Improve 
integration of asynchronous connectors"

ANALYSIS:

Add a check for null before starting the thread.

back to top

home | vision | search | in the news | faq | registration | open forum | tutorial | bug database
 API | download | expert teams | process management office | projects | links | terms of use

© Copyright 2001-2006 General Dynamics C4 Systems. All rights reserved.