[ http://jira.jboss.com/jira/browse/JBAS-4491?page=all ] Ning Zhao updated JBAS-4491: ---------------------------- Attachment: Signature.java I encountered this problem while using Seam 2.0 beta 1. The microcontainer needs to be started when I run my test classes extending SeamTest.java. Please see: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111930 This problem was due to regression between jdk 1.6 and jdk 1.5. My patch was based on the discussion which can be found here: https://glassfish.dev.java.net/issues/show_bug.cgi?id=714 http://forums.java.net/jive/thread.jspa?threadID=15823 I did not download the whole microcontainer project so that I have not rebuilt from the source code. Hopefully someone could test this patch. Thanks! Regards, Ellen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4491?page=comments#action_12374566 ] Aaman Lamba commented on JBAS-4491: ----------------------------------- Is there any update to this issue - it is pretty much a showstopper for us.The error message we receive on JBoss Startup is reproduced below, and quite similar to the original report. =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: D:\jboss-5.0.0.Beta2 JAVA: d:\sun\sdk\jdk\bin\java JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dsun.rmi.dgc.cl ient.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 CLASSPATH: d:\sun\sdk\jdk\lib\tools.jar;D:\jboss-5.0.0.Beta2\bin\run.jar =============================================================================== 14:55:46,344 INFO [ServerImpl] Starting JBoss (Microcontainer)... 14:55:46,376 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta2 (build: SVNTag=JBoss_5_0_0_ Beta2 date=200704060017) 14:55:46,376 INFO [ServerImpl] Home Dir: D:\jboss-5.0.0.Beta2 14:55:46,376 INFO [ServerImpl] Home URL: file:/D:/jboss-5.0.0.Beta2/ 14:55:46,376 INFO [ServerImpl] Library URL: file:/D:/jboss-5.0.0.Beta2/lib/ 14:55:46,391 INFO [ServerImpl] Patch URL: null 14:55:46,391 INFO [ServerImpl] Server Name: default 14:55:46,391 INFO [ServerImpl] Server Home Dir: D:\jboss-5.0.0.Beta2\server\default 14:55:46,391 INFO [ServerImpl] Server Home URL: file:/D:/jboss-5.0.0.Beta2/server/default/ 14:55:46,391 INFO [ServerImpl] Server Data Dir: D:\jboss-5.0.0.Beta2\server\default\data 14:55:46,391 INFO [ServerImpl] Server Temp Dir: D:\jboss-5.0.0.Beta2\server\default\tmp 14:55:46,391 INFO [ServerImpl] Server Config URL: file:/D:/jboss-5.0.0.Beta2/server/default/conf/ 14:55:46,391 INFO [ServerImpl] Server Library URL: file:/D:/jboss-5.0.0.Beta2/server/default/lib/ 14:55:46,391 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml 14:55:46,422 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/D:/jboss-5.0.0.Beta2/ser ver/default/conf/bootstrap-beans.xml 14:55:47,266 INFO [ProfileImpl] Using profile root:D:\jboss-5.0.0.Beta2\server\default 14:55:48,860 ERROR [AbstractKernelController] Error installing to Instantiated: name=DeploymentFilte r state=Described java.lang.IllegalStateException: Class not found: [Ljava.lang.String; at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:174) at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:125) at org.jboss.metadata.spi.signature.Signature.getParametersTypes(Signature.java:292) at org.jboss.metadata.plugins.loader.reflection.AnnotatedElementMetaDataLoader.getComponentM etaDataRetrieval(AnnotatedElementMetaDataLoader.java:138) at org.jboss.metadata.plugins.context.AbstractMetaDataContext.getComponentMetaDataRetrieval( AbstractMetaDataContext.java:280) at org.jboss.metadata.spi.retrieval.MetaDataRetrievalToMetaDataBridge.getComponentMetaData(M etaDataRetrievalToMetaDataBridge.java:159) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.methodHasAnnotations(AOP ConstructorJoinpoint.java:202) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasMethodMetaData(AOPCon structorJoinpoint.java:172) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasInstanceOrJoinpointMe taData(AOPConstructorJoinpoint.java:152) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJ oinpoint.java:99) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(Kerne lControllerContextAction.java:103) at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAc tion.java:52) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelCon trollerContextAction.java:197) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControlle rContextAction.java:136) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerC ontextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext. java:233) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:724) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:44 5) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:5 55) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:4 89) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeplo yer.java:302) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDepl oyer.java:272) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer. java:119) at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:6 4) at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:76) at org.jboss.kernel.plugins.deployment.xml.BasicXMLDeployer.deploy(BasicXMLDeployer.java:146 ) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.deploy(ProfileServiceBoots trap.java:295) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBo otstrap.java:222) at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403) at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342) at org.jboss.Main.boot(Main.java:210) at org.jboss.Main$1.run(Main.java:522) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: [Ljava.lang.String; at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:170) ... 35 more 14:55:49,328 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc. 14:55:49,328 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0-b105,Sun Microsystems Inc. 14:55:49,328 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 14:55:49,360 INFO [JMXKernel] Legacy JMX core initialized Failed to boot JBoss: java.lang.RuntimeException: Exception during Bootstrap at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:99) at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403) at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342) at org.jboss.Main.boot(Main.java:210) at org.jboss.Main$1.run(Main.java:522) at java.lang.Thread.run(Thread.java:619) Caused by: org.jboss.deployers.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State} VFSBootstrapScanner -> DeploymentFilter{Configured:**ERROR**} VFSDeployerScanner -> DeploymentFilter{Configured:**ERROR**} VFSDeploymentScanner -> DeploymentFilter{Configured:**ERROR**} *** CONTEXTS IN ERROR: Name -> Error DeploymentFilter -> java.lang.ClassNotFoundException: [Ljava.lang.String; at org.jboss.system.server.profileservice.ProfileServiceBootstrap.checkIncomplete(ProfileSer viceBootstrap.java:389) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBo otstrap.java:236) at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) ... 5 more 14:57:19,568 INFO [ServerImpl] JBoss SHUTDOWN 14:57:19,568 INFO [ServerImpl] Undeploying all packages Shutting down Microcontainer 14:57:19,615 INFO [ServerImpl] Shutdown complete Shutdown complete Halting VM Terminate batch job (Y/N)? y ============ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4491?page=all ] Adrian Brock updated JBAS-4491: ------------------------------- Comment: was deleted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4491?page=comments#action_12374628 ] Greg Zoller commented on JBAS-4491: ----------------------------------- Adrian, Actually I found some more info on this "bug". It appears to be a bug in the JDK but it is not. Sun says that there was some ambiguity/misinterpretation of certain functionality of class loading that permitted developers to get away with some common things that strictly speaking were not part of the Java spec. Java 6 simply closed the loophole. So while the behavior is not really a "bug" per se the change certainly does impact a lot of software out there and unfortunately the onus is on software providers like JBoss, not Sun, to rectify the problems this causes. Sun is not and will not likely be open to treat this as a regression issue since in their minds the "feature" in question probably never should have worked in the first place. Providers that don't rework the affected bits of their code may find themselves effectively stuck on JDK5. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4491?page=comments#action_12380878 ] Nicolas Doye commented on JBAS-4491: ------------------------------------ Another data point - this issue is also there with JDK 6 on Linux. (All other reporters mention versions of Windows). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBAS-4491?page=all ] Dimitris Andreadis updated JBAS-4491: ------------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira