|
Problem |
Why must the JMS resources (configured in JMSAdmin) be
rebound to the namespace every time WebSphere® Application Server V4.0 AEs
is restarted? |
|
Cause |
WebSphere Application Server Single Server Edition does
not have a persistent namespace; the naming directory does not store the
JMS configuration between runs. This means that every time the single
server runs, the JMS objects must be added to the namespace. |
|
Solution |
Use a script to add the JMS objects to the namespace;
however, this must be done every time the server is started.
This is not the case with WebSphere Advanced Edition, which has a
persistent namespace. |
|
|
|
|
|
|