January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4491) Server startup failure with JDK 1.6

by Greg Zoller (JIRA)

Server startup failure with JDK 1.6 ----------------------------------- Key: JBAS-4491 URL: http://jira.jboss.com/jira/browse/JBAS-4491 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta2 Environment: Windows Reporter: Greg Zoller An out-of-the-box installation of JBoss 5.0.0 Beta2 running with JDK 1.6 produces the following exception upon startup. Not sure the whys or wherefores but am pretty sure its not a good thing. 13:24:13,467 INFO [ServerImpl] Starting JBoss (Microcontainer)... 13:24:13,467 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.0.Beta2 (build: SVNTag=JBoss_5_0_0_Beta2 date=200704060017) 13:24:13,467 INFO [ServerImpl] Home Dir: C:\Program Files\jboss-5.0.0.Beta2 13:24:13,467 INFO [ServerImpl] Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/ 13:24:13,467 INFO [ServerImpl] Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/lib/ 13:24:13,467 INFO [ServerImpl] Patch URL: null 13:24:13,467 INFO [ServerImpl] Server Name: default 13:24:13,467 INFO [ServerImpl] Server Home Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default 13:24:13,467 INFO [ServerImpl] Server Home URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/ 13:24:13,467 INFO [ServerImpl] Server Data Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\data 13:24:13,467 INFO [ServerImpl] Server Temp Dir: C:\Program Files\jboss-5.0.0.Beta2\server\default\tmp 13:24:13,467 INFO [ServerImpl] Server Config URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/ 13:24:13,467 INFO [ServerImpl] Server Library URL: file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/lib/ 13:24:13,467 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml 13:24:13,499 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Program Files/jboss-5.0.0.Beta2/server/default/conf/bootstrap-beans.xml 13:24:14,831 INFO [ProfileImpl] Using profile root:C:\Program Files\jboss-5.0.0.Beta2\server\default 13:24:15,913 ERROR [AbstractKernelController] Error installing to Instantiated: name=DeploymentFilter 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.getComponentMetaDataRetrieval(AnnotatedElementMetaDataLoader.java:138) at org.jboss.metadata.plugins.context.AbstractMetaDataContext.getComponentMetaDataRetrieval(AbstractMetaDataContext.java:280) at org.jboss.metadata.spi.retrieval.MetaDataRetrievalToMetaDataBridge.getComponentMetaData(MetaDataRetrievalToMetaDataBridge.java:159) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.methodHasAnnotations(AOPConstructorJoinpoint.java:202) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasMethodMetaData(AOPConstructorJoinpoint.java:172) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.hasInstanceOrJoinpointMetaData(AOPConstructorJoinpoint.java:152) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:99) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:103) at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:52) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.installAction(KernelControllerContextAction.java:197) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.install(KernelControllerContextAction.java:136) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.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:445) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:555) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489) 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(AbstractKernelDeployer.java:302) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:272) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:119) at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:64) 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(ProfileServiceBootstrap.java:295) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.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(Unknown Source) Caused by: java.lang.ClassNotFoundException: [Ljava.lang.String; at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at org.jboss.metadata.spi.signature.Signature.stringsToClasses(Signature.java:170) ... 35 more 13:24:16,258 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc. 13:24:16,258 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,Sun Microsystems Inc. 13:24:16,258 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 13:24:16,305 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(Unknown Source) 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(ProfileServiceBootstrap.java:389) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:236) at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) ... 5 more -- 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

18 years, 5 months

10
12
0 / 0

[JBoss JIRA] Created: (JBCACHE-1277) Remove sample configs from distro jar's META-INF

by Manik Surtani (JIRA)

Remove sample configs from distro jar's META-INF ------------------------------------------------ Key: JBCACHE-1277 URL: http://jira.jboss.com/jira/browse/JBCACHE-1277 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.0.CR3 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.CR4 -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1111) Integrate with JBoss SSO framework

by Alex Pinkin (JIRA)

Integrate with JBoss SSO framework ---------------------------------- Key: JBPORTAL-1111 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1111 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Security Reporter: Alex Pinkin Assigned To: Julien Viet Fix For: 3.0 Final Dev will need to look into this for 3.0 -- 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

18 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (SECURITY-117) JBossAuthorizationContext is not initializing the modules with the subject passed

by Anil Saldhana (JIRA)

JBossAuthorizationContext is not initializing the modules with the subject passed --------------------------------------------------------------------------------- Key: SECURITY-117 URL: http://jira.jboss.com/jira/browse/SECURITY-117 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 The initialize modules method is taking the instance variable (authenticatedSubject) and not the passed argument. -- 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

18 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-678) NPE in NAKACK under startup load

by Bela Ban (JIRA)

NPE in NAKACK under startup load -------------------------------- Key: JGRP-678 URL: http://jira.jboss.com/jira/browse/JGRP-678 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.2, 2.7 Attachments: NAKACK.patch.txt Here's another NPE that we found, this time in NAKACK in 2.6.1. Again, we are starting up ~30 systems at once which causes some thrashing for a couple of minutes until things settle down. You will notice that we also moved over to trace the dumping of the NAKACK table which at some points threatened to overwhelm our log systems. That has (I think) been mentioned here before. -- 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

18 years, 5 months

1
7
0 / 0

[JBoss JIRA] Created: (JGRP-676) Infinite NPE/error loop in ClientGmsImpl.java

by Bela Ban (JIRA)

Infinite NPE/error loop in ClientGmsImpl.java --------------------------------------------- Key: JGRP-676 URL: http://jira.jboss.com/jira/browse/JGRP-676 Project: JGroups Issue Type: Bug Affects Versions: 2.6.1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.2, 2.7 Attachments: ClientGmsImpl.stack.txt So we are starting up ~30 hosts at the same time running 2.6.1 and have seen a number of exception stacks and anomalies. There are a couple nasty bugs in the ClientGMSImpl.join() method which caused an infinite loop of NPE exceptions or other errors. I fixed 3 of them and left one more for someone who knows the code better. See the patch. -- 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

18 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (JGRP-677) Another NPE in ClientGmsImpl

by Bela Ban (JIRA)

Another NPE in ClientGmsImpl ---------------------------- Key: JGRP-677 URL: http://jira.jboss.com/jira/browse/JGRP-677 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.2, 2.7 Also saw this NPE inside of ClientGmsImpl.join() with 2.6.1. -- 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

18 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1227) Statement leak in HandleBeforeCommit1PCRunner

by Kevin Conner (JIRA)

Statement leak in HandleBeforeCommit1PCRunner --------------------------------------------- Key: JBMESSAGING-1227 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1227 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3 Reporter: Kevin Conner Assigned To: Tim Fox Priority: Blocker >From JBESB-1450 "This leak appears to be coming from JBoss Messaging, specifically JDBCPersistenceManager$1HandleBeforeCommit1PCRunner.doTransaction(JDBCPersistenceManager.java:1587) This line creates a prepared statement within a loop but only the last statement created will be released. Other examples of this construct, within this file, use a simple guard to prevent subsequent allocations. This appears to be the only occurrence which does not." "The following change fixes the leak. Index: src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java =================================================================== --- src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java (revision 3648) +++ src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java (working copy) @@ -1584,8 +1584,11 @@ ChannelRefPair pair = (ChannelRefPair) i.next(); MessageReference ref = pair.ref; - psReference = conn + if (psReference == null) + { + psReference = conn .prepareStatement(getSQLStatement("INSERT_MESSAGE_REF")); + } // Now store the reference addReference(pair.channelID, ref, psReference, false); " -- 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

18 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1218) ResultSet not explicitly closed in JDBCPersistenceManager

by Tim Fox (JIRA)

ResultSet not explicitly closed in JDBCPersistenceManager --------------------------------------------------------- Key: JBMESSAGING-1218 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1218 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3 Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: Stable branch A ResultSet is left open at line 924 JDBCPersistenceManager:loadFromStart. The JCA adapter will close this automatically so the only negative effect of this bug is a warning in the logs. Can safely ignore this until the next release when it will be fixed. -- 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

18 years, 5 months

2
17
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1801) CMS content shows incorrect 'Created' and 'Modified' timestamps

by Martin Putz (JIRA)

CMS content shows incorrect 'Created' and 'Modified' timestamps --------------------------------------------------------------- Key: JBPORTAL-1801 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1801 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.2 Final Reporter: Martin Putz Assigned To: Sohil Shah A given file (index.html) in CMS is displayed like: index.html Created=T1, Modified=T1 - index.html - Version 1.0, Created=T1, Modified=T1 If this file is updated, a new version (2.0) is created and after that the display looks like index.html Created=T1, Modified=T1 - index.html - Version 1.0, Created=T1, Modified=T1 - index.html - Version 2.0, Created=T2, Modified=T2 One would expect to see the Modified=T2 date of the latest Version 2.0 on the top level entry of this content: index.html Created=T1, Modified=*T2* - index.html - Version 1.0, Created=T1, Modified=T1 - index.html - Version 2.0, Created=T2, Modified=T2 -- 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

18 years, 5 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008