Bug 46200

Bug: 46200

Impact:

Product:

GemBuilder for Java

Versions:

2.3, 2.2, 2.1.2.1, 2.1.2, 2.1.1, 2.1, 2.0

Platform:

All Platforms

Fixed In:

3.0

GbjBroker gslist status "killed" if prior broker dies and is restarted

If the GbjBroker process is killed or dies suddenly, gslist with options -l -v or -x will still continue to report it with a status of "killed" unless a gslist -c is performed to clear it.

If a new GbjBroker is started without doing a gslist -c, gslist will still continue to show a status of "killed" even though the new GbjBroker is working correctly.

Workaround

Remember to "gslist -c" before starting a new GbjBroker.

Alternatively, file-in as SystemUser and commit the following code:

! Bugfix for 46200
!
! Add code to unpublish earlier published data in case prior session died
!
category: 'Private'
method: GsbServerSocket
publishOnGsList

    self shouldPublishOnGsList ifTrue:
        [
         (System _publish: self name 
                     port: self port 
                      log: self gslistLogName asString 
                  options: self gslistOptionsString asString)
          ifFalse: [
              "Problem publishing new data -- unpublish old info"     
              self unpublishOnGsList.
              System _publish: self name 
                         port: self port 
                          log: self gslistLogName asString 
                      options: self gslistOptionsString asString ]]
%