CNTR0020E: 在 bean“BeanId(BizServer_jar#BizServer.jar#StatelessBizServer, null)”上处理方法“executeSQL”时发生非应用程序异常。异常数据:javax.ejb.EJBException: ORA-00933: SQL command not properly ended
参考 http://www-1.ibm.com/support/doc ... amp;uid=swg1PK35736
好像是WAS处理多线程的缺陷,在5.1.1.14得到了修改
==============================
APAR status
Closed as program error.
Error description
WSIFUtils.isJavaKeyword () produces an intermittent
ConcurrentModificationException as shown below when operating
with multiple threads
[27/09/06 12:58:35:378 BST] 6cc81c21 ExceptionUtil E CNTR0020E:
Non-application exception occurred while processing method
"createEvent"
on
bean
"BeanId(CesEvConnector#CesEvConnectorEJB.jar#EventManagercicseci
Service, null)".
Exception data: javax.ejb.EJBException: nested exception
is:
java.util.ConcurrentModificationException: concurrent access to
HashMap attempted by Thread[ORB.thread.pool : 1,5,main]
java.util.ConcurrentModificationException: concurrent access to
HashMap attempted by Thread[ORB.thread.pool : 1,5,main]
java.util.ConcurrentModificationException: concurrent access to
HashMap
at java.util.HashMap.onExit(HashMap.java(Compiled Code))
at java.util.HashMap.transfer(HashMap.java(Compiled Code))
at java.util.HashMap.resize(HashMap.java(Inlined Compiled
Code))
at java.util.HashMap.addEntry(HashMap.java(Compiled Code))
at java.util.HashMap.put(HashMap.java(Compiled Code))
at org.apache.wsif.util.WSIFUtils.isJavaKeyword
.
The underlying cause of the problem is that the
java.util.HashMap is not thread-safe, so the concurrent access
causes unpredictable results.
Local fix
Synchronize access to the method that call
WSIFUtils.isJavaKeyword() method
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of *
* WSIF *
****************************************************************
* PROBLEM DESCRIPTION: WSIFUtils.isJavaKeyword () produces *
* an intermittent *
* ConcurrentModificationException when *
* operating with multiple threads *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The underlying cause of the problem is that the
java.util.HashMap is not thread-safe, so the concurrent access
causes unpredictable results.
Problem conclusion
This issue has been fixed in WebSphere Application Server
cumulative fix 5.1.1.14.
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR information
APAR number PK35736
Reported component name WEBSPHERE BASE
Reported component ID 5630A3600
Reported release 10W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2006-12-06
Closed date 2007-01-29
Last modified date 2007-01-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
WSIF
Publications Referenced
Fix information
Fixed component name WEBSPHERE BASE
Fixed component ID 5630A3600
Applicable component levels
R103 PSY UP
R10A PSY UP
R10H PSY UP
R10I PSY UP
R10P PSY UP
R10S PSY UP
R10W PSY UP |