APAR status |
Closed as program error.
| Error description
This problem belongs with the plugin team component.
.
Customer is receiving the following error when trying to start
default server:
SMSQTransport X Transport Exception
com.ibm.servlet.engine.oselistener.serverqueue.SQException:default server:SMSQTransport X Transport Exception
Error,
failed to generate new ServerQeueue Object.
at
com.ibm.servlet.engine.oselistener.serverqueue.SQFactoryImp.crea
teINETqu
eue(SQFactoryImp.java:239)
.
The above error occurs only after they upgraded to ptf 6 of WAS
V35. They can switch back to WAS V355 and there are no problems.
.
Customer turned off "INFORM" log mask for the transport setting
and the problem goes away at V356. So the problem has to do with
INET sockets and selecting "INFORM" as the log mask.
.
Looks like the problem was introduced in WAS V356. com.ibm.servlet.engine.oselistener.serverqueue.SQException:Error,failed to generate new ServerQeueue Object.atcom.ibm.servlet.engine.oselistener.serverqueue.SQFactoryImp.createINETqueue(SQFactoryImp.java:239).The above error occurs only after they upgraded to ptf 6 of WASV35. They can switch back to WAS V355 and there are no problems..Customer turned off "INFORM" log mask for the transport settingand the problem goes away at V356. So the problem has to do withINET sockets and selecting "INFORM" as the log mask..Looks like the problem was introduced in WAS V356. Local fix
Turn off "INFORM" log mask fro the transport setting. Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users with *
* INFORM appserver side native tracing *
* enabled while running OSE remote. *
****************************************************************
* PROBLEM DESCRIPTION: Appserver won't start, or won't serve *
* any content with INFORM enabled on OSE *
* remote install. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A mistake in a log statement introduced in PTF6 could cause
memory corruption. The statement was only logged for
OSE remote, and at an INFORM level. Problem conclusion
Fixed the log statement in an earlier defect - this APAR
was opened so we could distribute an efix. Temporary fix
As a workaround, customers can turn off the appserver side
INFORM tracing. ( the checkboxes for this are in dialog that
allows you to change the transport between OSE remote and
local pipes ) Comments
APAR information | APAR number | PQ63148 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-07-15 | Closed date | 2002-07-16 | Last modified date | 2002-08-02 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSY | UP |
|