11/14/12 14:17:27:325 GMT+05:30 00000016
com.ibm.ws.kernel.feature.internal.FeatureManager A CWWKF0011I: The server defaultServer is ready to run a smarter planet.
11/14/12 14:17:40:536 GMT+05:30 00000011 com.ibm.ws.logging.internal.impl.Incident I FFDC1015I: An FFDC Incident has been
created: "java.lang.ArrayIndexOutOfBoundsException: 40157 com.ibm.ws.anno.targets.internal.AnnotationTargetsImpl_Targets 325" at
11/14/12 14:17:40:536 GMT+05:30 00000011 m.ibm.ws.anno.targets.internal.AnnotationTargetsImpl_Targets W CWWKC0044W:
An exception occurred while scanning class and annotation data.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
5 replies Latest Post - 2012-11-29T09:02:49Z by SystemAdmin
Pinned topic ArrayIndexOutOfBoundsException when starting the defaultServer
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Re: ArrayIndexOutOfBoundsException when starting the defaultServer2012-11-20T06:53:21Z in response to SystemAdminSpring version - 3.0.5
Liberty version - 188.8.131.52
Thanks in advance.
Jacek_Laskowski 060001359D133 PostsACCEPTED ANSWER
Re: ArrayIndexOutOfBoundsException when starting the defaultServer2012-11-21T12:15:09Z in response to SystemAdminHi,
Not that it may solve the problem, but could you give it a try with 184.108.40.206?
Could you also reproduce it with a very simple app and share it on github or other public repo to download and give it a try?
Japila :: verba docent, exempla trahunt
Re: ArrayIndexOutOfBoundsException when starting the defaultServer2012-11-29T09:02:49Z in response to SystemAdminHi,
The message you are seeing (which isn't hugely useful I'll admit) is reporting that one of the classes in your application has a problem with it and as a result it couldn't be loaded and scanned by our annotation scanner. This usually goes back to a corrupt or invalid class (although I can't say this is the case 100% of the time). If your application is functioning correctly then this message can be safely ignored.