August 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1288) NPE in thread "vfs-shutdown"

by Juergen Zimmermann (JIRA)

NPE in thread "vfs-shutdown" ----------------------------- Key: AS7-1288 URL: https://issues.jboss.org/browse/AS7-1288 Project: Application Server 7 Issue Type: Bug Components: VFS Affects Versions: 7.0.0.Final Environment: 7.1.0.Alpha1 Jenkins build 1402 Reporter: Juergen Zimmermann Assignee: John Bailey When I shutdown a standalone server I'm getting a NPE. The shutdown command is: jboss-admin.bat --connect command=:shutdown Console log: ... 18:24:55,990 INFO [org.jboss.as.logging] Restored bootstrap log handlers 18:24:55,990 INFO [org.jboss.as.jmx.JMXConnectorService] JMX remote connector stopped 18:24:56,075 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: jboss-as-osgi-configadmin:7.1.0.Alpha1-SNAPSHOT 18:24:56,125 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: org.apache.felix.log:1.0.0 18:24:56,230 INFO [org.apache.catalina.core.StandardContext] Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started 18:24:56,286 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: org.apache.felix.configadmin:1.2.8 18:24:56,323 INFO [org.jboss.osgi.framework.internal.HostBundleState] Bundle stopped: jboss-osgi-logging:1.0.0 18:24:56,330 INFO [com.arjuna.ats.jbossatx] ARJUNA32018: Destroying TransactionManagerService 18:24:56,331 INFO [com.arjuna.ats.jbossatx] ARJUNA32014: Stopping transaction recovery manager 18:24:56,368 ERROR [stderr] Exception in thread "vfs-shutdown" java.lang.NullPointerException 18:24:56,368 ERROR [stderr] at org.jboss.vfs.TempFileProvider$DeleteTask.run(TempFileProvider.java:151) 18:24:56,368 ERROR [stderr] at org.jboss.vfs.TempFileProvider.close(TempFileProvider.java:132) 18:24:56,368 ERROR [stderr] at org.jboss.osgi.vfs30.VirtualFileAdaptor30$2.run(VirtualFileAdaptor30.java:94) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 12 months

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3163) Drools does not work with Java7

by Andreas Pieber (JIRA)

Drools does not work with Java7 ------------------------------- Key: JBRULES-3163 URL: https://issues.jboss.org/browse/JBRULES-3163 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.2.0.Final, 5.1.1.FINAL Reporter: Andreas Pieber Assignee: Mark Proctor Fix For: 5.2.1.Final, 5.3.0.Beta1 While there are various places where 1.7 for java source version is already used it seams that there are some places where it simply had been forgotten. It would be very great if that pull request could make it into a very soon 5.2.1.FINAL release since java7 is released now. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

7
9
0 / 0

[JBoss JIRA] Created: (LOGMGR-24) Bad level "OFF" when using JDK7

by Jesper Pedersen (JIRA)

Bad level "OFF" when using JDK7 ------------------------------- Key: LOGMGR-24 URL: https://jira.jboss.org/browse/LOGMGR-24 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.2.0.CR6 Reporter: Jesper Pedersen Assignee: David Lloyd When using JDK7 I get Caused by: java.lang.ExceptionInInitializerError at sun.util.logging.PlatformLogger.<init>(PlatformLogger.java:164) at sun.util.logging.PlatformLogger.getLogger(PlatformLogger.java:128) at sun.net.www.protocol.http.HttpURLConnection.<clinit>(HttpURLConnection.java:298) at sun.net.www.protocol.http.Handler.openConnection(Handler.java:62) at sun.net.www.protocol.http.Handler.openConnection(Handler.java:57) at java.net.URL.openConnection(URL.java:969) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:628) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(XMLEntityManager.java:1292) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(XMLEntityManager.java:1259) at com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerImpl.java:260) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(XMLDocumentScannerImpl.java:1169) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(XMLDocumentScannerImpl.java:1065) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:978) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:551) at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1234) at org.jboss.jca.common.metadata.ra.RaParser.parse(RaParser.java:114) at org.jboss.jca.common.metadata.MetadataFactory.getStandardMetaData(MetadataFactory.java:105) at org.jboss.jca.deployers.fungal.RADeployer.deploy(RADeployer.java:166) ... 26 more Caused by: java.lang.IllegalArgumentException: Bad level "OFF" at java.util.logging.Level.parse(Level.java:355) at java.util.logging.LoggingProxyImpl.parseLevel(LoggingProxyImpl.java:95) at sun.util.logging.LoggingSupport.parseLevel(LoggingSupport.java:134) at sun.util.logging.PlatformLogger$JavaLogger.getLevelObjects(PlatformLogger.java:504) at sun.util.logging.PlatformLogger$JavaLogger.<clinit>(PlatformLogger.java:496) ... 46 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
13
0 / 0

[JBoss JIRA] Created: (AS7-1535) More management operations for timers

by Stuart Douglas (JIRA)

More management operations for timers ------------------------------------- Key: AS7-1535 URL: https://issues.jboss.org/browse/AS7-1535 Project: Application Server 7 Issue Type: Feature Request Reporter: Stuart Douglas Using the management api it should be possible to perform additional operations on timers such as: suspending cancelling invoking a timeout method -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
3
0 / 0

[JBoss JIRA] Created: (JBNAME-51) Delay in connecting when first of multiple providers is down can cause performance issue

by Dennis Reed (JIRA)

Delay in connecting when first of multiple providers is down can cause performance issue ---------------------------------------------------------------------------------------- Key: JBNAME-51 URL: https://issues.jboss.org/browse/JBNAME-51 Project: JBoss Naming Issue Type: Bug Components: jnpserver Affects Versions: 5.0.3.GA Reporter: Dennis Reed org.jnp.interfaces.NamingContext.checkRef always loops through the provider list in order, trying to connect to the first before checking for a cached connection to a later provider. This affects performance because it can cause a delay on every context created, waiting for a timeout on a node that is down. For instance, the following takes a very long time when node1 is down. ... env.put ( Context.PROVIDER_URL, "node1:1100,node2:1100" ); for ( int i = 0; i < 1000; ++ i ) { InitialContext ctx = new InitialContext ( env ); ... } If checkRef looked for a cached connection to any of the listed providers before trying to connect to an uncached one, there would only be a timeout delay on the very first connection attempt. Note: This would change the behavior of the client when node1 comes back up in the middle, so would not be eligible for an EAP patch release. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
7
0 / 0

[JBoss JIRA] Created: (JBAS-9177) Launch script does not work on Windows

by Max Rydahl Andersen (JIRA)

Launch script does not work on Windows --------------------------------------- Key: JBAS-9177 URL: https://issues.jboss.org/browse/JBAS-9177 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Max Rydahl Andersen Priority: Critical Launching AS 7 does not work on windows. Several issues: Quoting java_home causes error: set JAVA_HOME="C:\Program Files\Java\jdk1.6.0_24" Y:\products\jboss 7.0.0.Beta1\bin>standalone.bat Config file not found Y:\products\jboss 7.0.0.Beta1\bin\standalone.conf.bat Files\Java\jdk1.6.0_24"" was unexpected at this time. Non quoting and you get this: Y:\products\jboss 7.0.0.Beta1\bin>set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_2 4 Y:\products\jboss 7.0.0.Beta1\bin>standalone.bat Config file not found Y:\products\jboss 7.0.0.Beta1\bin\standalone.conf.bat =============================================================================== JBoss Bootstrap Environment JBOSS_HOME: Y:\products\jboss 7.0.0.Beta1 JAVA: C:\Program Files\Java\jdk1.6.0_24\bin\java JAVA_OPTS: -Dprogram.name=standalone.bat -server =============================================================================== Exception in thread "main" java.lang.NoClassDefFoundError: 7/0/0/Beta1\standalon e\log\boot/log Caused by: java.lang.ClassNotFoundException: 7.0.0.Beta1\standalone\log\boot.log at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) Could not find the main class: 7.0.0.Beta1\standalone\log\boot.log. Program wil l exit. Press any key to continue . . . And it seem to be looking for standalone.conf.bat which does not exist. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
13
0 / 0

[JBoss JIRA] Created: (JBAS-8390) Allow for configuration of respawn policy in host.xml/domain.xml

by Kabir Khan (JIRA)

Allow for configuration of respawn policy in host.xml/domain.xml ---------------------------------------------------------------- Key: JBAS-8390 URL: https://jira.jboss.org/browse/JBAS-8390 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 7.0.0.M1 The server manager currently uses the default respawn policy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-5900) jars are not loaded from the lib directory of a sar in JBoss AS 5

by Matt Wringe (JIRA)

jars are not loaded from the lib directory of a sar in JBoss AS 5 ----------------------------------------------------------------- Key: JBAS-5900 URL: https://jira.jboss.org/jira/browse/JBAS-5900 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Affects Versions: JBossAS-5.0.0.CR2 Reporter: Matt Wringe Assignee: Scott M Stark Attachments: testsar.tar.gz In JBoss AS 5, any jars placed in the lib directory of a sar are not loaded and results in a class not found exception. The classes are loaded if the jar is placed in the root directory of the sar. On previous versions of JBoss AS, the classes would be loaded from either location. This prevents sars that would have worked on JBoss AS 4 to fail on JBoss AS 5. Steps to reproduce: 1) take zip attached to this report. 2) deploy test-in-lib.sar to JBoss AS 5. The sar will not deploy and will fail with a classNotFoundException 3) deploy test-in-lib.sar to JBoss AS 4, the sar will deploy without issue. test-in-root.sar will work on both versions of JBoss. The only difference between these sars is the location of the jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
9
0 / 0

[JBoss JIRA] Created: (SECURITY-542) Add Full Kerberos Support for EJB3 Invocations

by Darran Lofthouse (JIRA)

Add Full Kerberos Support for EJB3 Invocations ---------------------------------------------- Key: SECURITY-542 URL: https://jira.jboss.org/browse/SECURITY-542 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA Add full Kerberos support for EJB3 invocations. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1488) Document how Extension-List works in the class loading guide

by Stuart Douglas (JIRA)

Document how Extension-List works in the class loading guide ------------------------------------------------------------ Key: AS7-1488 URL: https://issues.jboss.org/browse/AS7-1488 Project: Application Server 7 Issue Type: Task Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
1
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 August 2011