January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3509) TCCL is not set for RA start

by Jason Greene (JIRA)

Jason Greene created AS7-3509: --------------------------------- Summary: TCCL is not set for RA start Key: AS7-3509 URL: https://issues.jboss.org/browse/AS7-3509 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Jason Greene Assignee: Jesper Pedersen Fix For: 7.1.1.Final Weston reported that the AMQP rar was getting the wrong TCCL during startup. We should make sure all EE code execution points get a deployment CL as the TCCL. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3508) JDR i18n broken in jython

by Jesse Jaggars (JIRA)

Jesse Jaggars created AS7-3508: ---------------------------------- Summary: JDR i18n broken in jython Key: AS7-3508 URL: https://issues.jboss.org/browse/AS7-3508 Project: Application Server 7 Issue Type: Bug Reporter: Jesse Jaggars Assignee: Jesse Jaggars The python/jython section of JDR does not work. The 'sos.po.sos' resource bundle is not found. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2016) Clustering switches in AS 4/5 and EAP 4/5 of -G -u -m

by Jim Tyrrell (Created) (JIRA)

Clustering switches in AS 4/5 and EAP 4/5 of -G -u -m ----------------------------------------------------- Key: AS7-2016 URL: https://issues.jboss.org/browse/AS7-2016 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell In the past these switches were used to setup clustering, to easily clone and instance does it make sense for these to continue to exist, or does something new take their place? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
10
0 / 0

[JBoss JIRA] (AS7-3234) Convert security subsystem to i18n logging and exceptions messages as per ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Convert security subsystem to i18n logging and exceptions messages as per ANDIAMO-2 ----------------------------------------------------------------------------------- Key: AS7-3234 URL: https://issues.jboss.org/browse/AS7-3234 Project: Application Server 7 Issue Type: Task Components: Security Reporter: Brian Stansberry Assignee: Anil Saldhana Priority: Critical Fix For: 7.1.0.Final The SecurityLogger and SecurityMessages classes are currently empty shells. The INFO and above logging and any exception messages in the subsystem needs to be converted to use these classes. See EJB subsystem for an example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] (AS7-3235) Convert web subsystem to i18n logging and exceptions messages as per ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Convert web subsystem to i18n logging and exceptions messages as per ANDIAMO-2 ------------------------------------------------------------------------------ Key: AS7-3235 URL: https://issues.jboss.org/browse/AS7-3235 Project: Application Server 7 Issue Type: Task Components: Web Reporter: Brian Stansberry Assignee: Remy Maucherat Fix For: 7.1.0.Final The WebLogger and WebMessages classes are currently empty shells. The INFO and above logging and any exception messages in the subsystem needs to be converted to use these classes. See EJB subsystem for an example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
3
0 / 0

[JBoss JIRA] (AS7-2578) Domain does not boot with custom welcome root

by Heiko Braun (Created) (JIRA)

Domain does not boot with custom welcome root --------------------------------------------- Key: AS7-2578 URL: https://issues.jboss.org/browse/AS7-2578 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Web Reporter: Heiko Braun Assignee: Brian Stansberry Priority: Critical Fix For: 7.1.0.CR1 Declaring a custom welcome root other then root.war, leads to an error that prevents the domain from booting: {noformat} <subsystem xmlns="urn:jboss:domain:web:1.1"> <connector name="http" protocol="HTTP/1.1" socket-binding="http" scheme="http" enabled="true"/> <connector name="https" protocol="HTTP/1.1" socket-binding="https" scheme="https" enabled="true"/> <virtual-server name="default-host" default-web-module="test.war" enable-welcome-root="true"> <alias name="localhost"/> <alias name="example.com"/> </virtual-server> </subsystem> {noformat} {noformat} [Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[353,17] [Host Controller] Message: The welcome root can not be enabled on a host that has a default web module [Host Controller] at org.jboss.as.web.WebSubsystemParser.parseHost(WebSubsystemParser.java:596) [Host Controller] at org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:446) [Host Controller] at org.jboss.as.web.WebSubsystemParser.readElement(WebSubsystemParser.java:117) [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) [staxmapper-1.0.0.Final.jar:1.0.0.Final] [Host Controller] at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.0.0.Final.jar:1.0.0.Final] [Host Controller] at org.jboss.as.controller.parsing.DomainXml.parseProfiles(DomainXml.java:536) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] [Host Controller] at org.jboss.as.controller.parsing.DomainXml.readDomainElement(DomainXml.java:208) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] [Host Controller] at org.jboss.as.controller.parsing.DomainXml.readElement(DomainXml.java:101) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] [Host Controller] at org.jboss.as.controller.parsing.DomainXml.readElement(DomainXml.java:86) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) [staxmapper-1.0.0.Final.jar:1.0.0.Final] [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) [staxmapper-1.0.0.Final.jar:1.0.0.Final] [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:117) [j {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

8
10
0 / 0

[JBoss JIRA] (AS7-3486) Arq: Delete temp mgmt-users.properties_arq-temp after shutting down AS 7.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3486: --------------------------------- Summary: Arq: Delete temp mgmt-users.properties_arq-temp after shutting down AS 7. Key: AS7-3486 URL: https://issues.jboss.org/browse/AS7-3486 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.0.Beta1b Reporter: Ondrej Zizka Assignee: Aslak Knutsen Priority: Blocker Fix For: 7.1.0.Final Arq renames the mgmt-users.properties_arq-temp, and it doesn't delete the file afterwards. When the second surefire run re-uses the same server, it fails because the file exists. Could you please check & fix it? {code} Caused by: java.lang.IllegalStateException: Could not rename W:\workspace\JBoss-AS-7.0.x-Windows\testsuite\integration\smoke\target\jbossas-smoke\standalone\configuration\mgmt-users.properties to W:\workspace\JBoss-AS-7.0.x-Windows\testsuite\integration\smoke\target\jbossas-smoke\standalone\configuration\mgmt-users.properties_arq-temp. Unable to start server with custom security. Please setup a management user manually and provide username/password in the Arquillian configuration. at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.createTempAuthConfigurationIfAuthNotDefined(ManagedDeployableContainer.java:284) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:104) ... 68 more {code} https://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x-Windows/1170/testRe... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1500) Additional packages in the sun.jdk module

by Shelley Baker (JIRA)

Additional packages in the sun.jdk module ----------------------------------------- Key: AS7-1500 URL: https://issues.jboss.org/browse/AS7-1500 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.0.0.Final Environment: JBoss AS 7.0.0.Final, Sun JRE 1.6.0_26 Reporter: Shelley Baker There are several packages that in the Sun JDK that should be made available to applications in JBoss, including: * com.sun.jndi.dns * com.sun.jndi.ldap * com.sun.security.auth One potential solution that would prevent applications from explicitly creating these modules or declaring them as dependencies would be to include them in the "sun.jdk" module (AS7-962). The inclusion of the DNS JNDI package was originally discussed in the following thread: http://community.jboss.org/message/619522#619522. The LDAP JNDI package is already included as a separate module (AS7-956), but it would be preferable to include it in the "sun.jdk" module so that applications do not need to declare this module dependency. The security package prevents performing privileged actions, so it would also be beneficial to include in the sun.jdk module. Attached is a test case that can be used to demonstrate the requested packages currently missing from the classloader. The exceptions will be thrown by invoking the following: * http://localhost:8080/jboss-test/dns * http://localhost:8080/jboss-test/ldap * http://localhost:8080/jboss-test/security After adding the following paths to the sun.jdk module descriptor ($JBOSS_HOME/modules/sun/jdk/main/module.xml), the classes are found and the application behaves as expected: <path name="com/sun/jndi/dns"/> <path name="com/sun/jndi/ldap"/> <path name="com/sun/security/auth"/> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
7
0 / 0

[JBoss JIRA] (JGRP-1417) UNICAST2: switch from NakReceiverWindow to Table

by Bela Ban (JIRA)

Bela Ban created JGRP-1417: ------------------------------ Summary: UNICAST2: switch from NakReceiverWindow to Table Key: JGRP-1417 URL: https://issues.jboss.org/browse/JGRP-1417 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.1 Similar to https://issues.jboss.org/browse/JGRP-1396: use Table rather than NakReceiverWindow. Should be simple as Table offers almost the same interface as NRW. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBRULES-3122) Classloading error with AspectJ and Drools 5.2.0.Final

by stevearoonie (JIRA)

Classloading error with AspectJ and Drools 5.2.0.Final ------------------------------------------------------ Key: JBRULES-3122 URL: https://issues.jboss.org/browse/JBRULES-3122 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.2.0.Final Reporter: stevearoonie Assignee: Mark Proctor NPE running Drools with AspectJ java.lang.NullPointerException at org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.parseDefinitions(ClassLoaderWeavingAdaptor.java:251) at org.aspectj.weaver.loadtime.DefaultWeavingContext.getDefinitions(DefaultWeavingContext.java:130) at org.aspectj.weaver.loadtime.ClassLoaderWeavingAdaptor.initialize(ClassLoaderWeavingAdaptor.java:161) at org.aspectj.weaver.loadtime.Aj$ExplicitlyInitializedClassLoaderWeavingAdaptor.initialize(Aj.java:271) at org.aspectj.weaver.loadtime.Aj$ExplicitlyInitializedClassLoaderWeavingAdaptor.getWeavingAdaptor(Aj.java:276) at org.aspectj.weaver.loadtime.Aj$WeaverContainer.getWeaver(Aj.java:254) at org.aspectj.weaver.loadtime.Aj.preProcess(Aj.java:90) at org.aspectj.weaver.loadtime.ClassPreProcessorAgentAdapter.transform(ClassPreProcessorAgentAdapter.java:54) at sun.instrument.TransformerManager.transform(TransformerManager.java:169) at sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:365) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) at java.lang.ClassLoader.defineClass(ClassLoader.java:616) at org.drools.rule.JavaDialectRuntimeData$PackageClassLoader.fastFindClass(JavaDialectRuntimeData.java:570) at org.drools.util.CompositeClassLoader$CachingLoader.load(CompositeClassLoader.java:258) at org.drools.util.CompositeClassLoader$CachingLoader.load(CompositeClassLoader.java:241) at org.drools.util.CompositeClassLoader.loadClass(CompositeClassLoader.java:88) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at org.drools.rule.JavaDialectRuntimeData.wire(JavaDialectRuntimeData.java:405) at org.drools.rule.JavaDialectRuntimeData.wire(JavaDialectRuntimeData.java:396) at org.drools.rule.JavaDialectRuntimeData.onBeforeExecute(JavaDialectRuntimeData.java:237) at org.drools.rule.DialectRuntimeRegistry.onBeforeExecute(DialectRuntimeRegistry.java:132) at org.drools.compiler.PackageBuilder.reloadAll(PackageBuilder.java:796) at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:751) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:360) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:538) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) at au.com.promedicus.rules.KnowledgeBaseBuilder.addPackagesFromList(KnowledgeBaseBuilder.java:108) at au.com.promedicus.rules.KnowledgeBaseBuilder.build(KnowledgeBaseBuilder.java:69) at au.com.promedicus.rules.KnowledgeBaseBuilder.build(KnowledgeBaseBuilder.java:54) I have traced the problem to org.drools.rule.JavaDialectRuntimeData$PackageClassLoader.getResources. This returns null whereas AspectJ expects it to at least return an empty enumeration - hence the NPE. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
9
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 2012