Bug 30351

GemBuilder for Java

2.3, 2.2, 2.1.2, 2.1.1, 2.1, 2.0, 1.2.1, 1.2

All

3.0

Stale gslist info prevents current info from being registered

When a GBJ broker dies or is killed, it is listed under gslist as "killed". When a new broker is started, the old gslist entry remains, and the new broker is not listed.

The expected behavior is for the new broker to fail to start until the "killed" broker's info is cleared by issuing 'gslist -c'.

Workaround

Before starting the GBJ broker, execute 'gslist -c' to clear any stale gslist information.


Last updated: 8/23/04