|
Problem |
Port duplication error occurs at startup of
AppServer after an xml import |
|
|
|
Solution |
If using clones, port duplication error occurs at
starting up of an AppServer after importing xml file.
Error Message
[02/06/27 0:32:10:965 JST] 35c9a871 ServletEngine X SRVE0146E:
Failed
to Start Transport. The most likely cause is that the port is already
in
use. Please ensure that no other applications are using this port and
restart the server.
com.ibm.servlet.engine.TransportException: The
socket name is already in use.
Resolution
- Restart AdminServers and AppServers
- If a restart is not a suitable option, increase the
DB2 Application heap size from the default 256 to 512 <db2
update db config for < WAS40> using applheapsz 256> and recycle DB2. This will resolve subsequent logging of this
error because WebSphere now has a larger application heap size to load
objects to at a reduced time. Note:
WAS40 in the illustration shows the name of the WAS database.
Substitute the correct name of your WAS repository.
Explanation
There is a casual relationship between increasing
application heap size and the resolution of this
problem.
It is normal to increase your application heap
especially as the objects in the WAS
repository increase (adding clones or application servers).
Increasing the heap actually allowed AppServer objects
to be loaded or unloaded much faster
from the heap. Therefore, the
duplication port exception got fixed by the reduced time it takes to
release the lock on the port (communication time between when the OS says
the port is free and when WAS knows it's free is shorter).
|
|
|
|
|
|
Historical Number |
PMR 12414 b698 c760 |
|
Product
Alias/Synonym |
WebSphere AppServer 4.0.3 |
|
|
|
|