Listener won't configure second application

Question

Using
Glassfish 3.1
apex_listener.1.1.0.60.10.38
first listener context root: /dev name: apex_dev
http://10.45.100.10:8081/dev/listenerConfigure
Works.
deploy second app context root: /test name: apex_test
http://10.45.100.10:8081/test/listenerConfigure
The APEX Listener is already configured. Please login as Administrator to access APEX Listener Administration.
In /tmp there is a directory apex. When I set this up before there were separate directories /tmp/apex_dev and /tmp/apex_test.
Any help in why I can't configure a second listener would be appreciated.

Answer 1

Correct, it is essential to undeploy all previous listener instances, and restart the application server. It is also important to remove any existing apex-config.xml that might have been created in one of the default locations, for example ${java.io.tmpdir/apex/apex-config.xml. If you fail to do either of these then the old configuration will be picked up.
Below are the steps I follow to deploy more that one instance of the listener:
<pre>
unzip listener zip file to some temporary folder (/tmp/al)
cd /tmp/al
mkdir tmp
cd tmp
unzip ../apex.war
cd WEB-INF
# edit the web.xml, uncomment config.dir param, set it to wherever you wish to store the config data e.g.: /home/cdivilly/al
zip -r ../apex1.war .
cd ..
cp apex1.war apex2.war
</pre>
I then deploy apex1.war and apex2.war to the application server in the usual fashion, and finally navigate to http://server:port/apex1/listenerConfigure and then http://server:port/apex2/listenerConfigure