Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
APAR status
Closed as program error.
Error description
A 3 minute delay in application startup was seen followed by the message: BBOO0221W: CWNBV0005W: A validation.xml file was found for the /xxxx/xxx.ear/xxx.war module. However, that validation.xml file is not configured for validation; therefore this XML file is ignored. Additionally, this issue can occur as an application server startup hang condition with a message similar to the the following hung thread indication in the Application Server's SystemOut.log file when the AppServer does not start or fails to start up : ---------------------------------------------------------------- [9/29/14 9:53:23:066 EDT] 00000064 ThreadMonitor W WSVR0605W: Thread "server.startup : 0" (00000051) has been active for 711354 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:140) at java.io.BufferedInputStream.fill(BufferedInputStream.java:229) at java.io.BufferedInputStream.read1(BufferedInputStream.java:269) at java.io.BufferedInputStream.read(BufferedInputStream.java:328) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:708) (http://www.http.HttpClient.parseHTTPHeader%28HttpClient.java:70 8%29) (http://www.http.HttpClient.parseHTTPHeader%28HttpClient.java:70 8%29) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:653) (http://www.http.HttpClient.parseHTTP%28HttpClient.java:653%29) (http://www.http.HttpClient.parseHTTP%28HttpClient.java:653%29) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpU RLConnec (http://www.protocol.http.HttpURLConnection.getInputStream%28Htt pURLConnec) tion.java:1207) (http://www.protocol.http.HttpURLConnection.getInputStream%28Htt pURLConn ection.java:1207%29) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unkno wn Source) at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown ---------------------------------------------------------------- Can also see a hang during app server startup. WSVR0605W: Thread "server.startup : 0" (00000092) has been active for 692282 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung. at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:140) at java.io.BufferedInputStream.fill (BufferedInputStream.java:229) at java.io.BufferedInputStream.read1 (BufferedInputStream.java:269) ...
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0.0 and V8.5.0 whose application * * contains a validation.xml file not * * intended for Bean Validation. * **************************************************************** * PROBLEM DESCRIPTION: Delay in application start when Bean * * Validation attempts to validate a * * validation.xml not intended for Bean * * Validation. * **************************************************************** * RECOMMENDATION: * **************************************************************** A 3 minute delay in application startup was seen followed by the message: BBOO0221W: CWNBV0005W: A validation.xml file was found for the /xxxx/xxx.ear/xxx.war module. However, that validation.xml file is not configured for validation; therefore this XML file is ignored. The new Bean Validation APIs in WebSphere v8 attempt to process any file named validation.xml, even if it's not intended to be used for Bean Validation. The validation.xml in this case was intended for the struts framework of the customer's application. The following Connection timeout was seen in traces: Trace: 2013/01/31 15:02:09.294 02 t=7BE470 c=UNK key=P8 tag= (13007004) SourceId: com.ibm.ws.beanvalidation.JaxbBvalUnmarshaller ExtendedMessage: Error occured for the validation.xml file in /xxxx/xxx.ear/xxx.war; java.net.ConnectException: EDC8127I Connection timed out. (errno2=0x76630291) .at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:381) .at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:2 43) .at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:230) .at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377) .at java.net.Socket.connect(Socket.java:539) .at java.net.Socket.connect(Socket.java:488) .at sun.net.NetworkClient.doConnect(NetworkClient.java:175) .at sun.net.www.http.HttpClient.openServer(HttpClient.java:408) .at sun.net.www.http.HttpClient.openServer(HttpClient.java:543) .at sun.net.www.http.HttpClient.<init>(HttpClient.java:247) .at sun.net.www.http.HttpClient.New(HttpClient.java:320) .at sun.net.www.http.HttpClient.New(HttpClient.java:337) .at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient (HttpURLConnection.java:982) .at sun.net.www.protocol.http.HttpURLConnection.plainConnect (HttpURLConnection.java:923) .at sun.net.www.protocol.http.HttpURLConnection.connect (HttpURLConnection.java:848) .at sun.net.www.protocol.http.HttpURLConnection.getInputStream (HttpURLConnection.java:1184) .at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unkno wn Source) .at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source) .at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source) .at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source) .at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.disp atch (Unknown Source) .at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume nt (Unknown Source) .at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) .at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) .at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) .at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) .at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) .at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source) .at javax.xml.parsers.SAXParser.parse(Unknown Source) .at com.ibm.ws.beanvalidation.JaxbBvalUnmarshaller.doUnmarshal (JaxbBvalUnmarshaller.java:232) .at com.ibm.ws.beanvalidation.JaxbBvalUnmarshaller.unmarshal (JaxbBvalUnmarshaller.java:190) .at com.ibm.ws.beanvalidation.BeanValidationServiceImpl. getValidatorFactory(BeanValidationServiceImpl.java:211) .at com.ibm.ws.beanvalidation.BeanValidationMetaDataListener. metaDataCreated(BeanValidationMetaDataListener.java:222) .at com.ibm.ws.beanvalidation.BeanValidationMetaDataListener. metaDataCreated(BeanValidationMetaDataListener.java:136) ...
Problem conclusion
With this fix, code has been added to Bean Validation to allow for only the processing of a validation.xml file which is defined by the Bean Validation specification, all other validation.xml files will be ignored. The fix for this APAR is currently targeted for inclusion in Fix Packs 8.0.0.8 and 8.5.5.1 of WebSphere Application Server 8.0 and V8.5. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PM85921
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-03-29
Closed date
2013-07-22
Last modified date
2014-10-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
11 January 2022