[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
12 years, 8 months
[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
12 years, 8 months
[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
12 years, 8 months
[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
12 years, 8 months
[JBoss JIRA] (AS7-3301) Attribute local-bind-address in broadcast-groups configuration is ignored and 0.0.0.0 is always used
by Miroslav Novak (JIRA)
Miroslav Novak created AS7-3301:
-----------------------------------
Summary: Attribute local-bind-address in broadcast-groups configuration is ignored and 0.0.0.0 is always used
Key: AS7-3301
URL: https://issues.jboss.org/browse/AS7-3301
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.0.CR1
Reporter: Miroslav Novak
Assignee: Clebert Suconic
Fix For: 7.1.0.Final
When local-bind-address in broadcast-groups is set in messaging subsystem in stantalone-ha.xml:
{code}
<broadcast-groups>
<broadcast-group name="bg-group-nodeA">
<local-bind-address>192.168.10.1</local-bind-address>
<group-address>231.8.8.8</group-address>
<group-port>9875</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref>netty</connector-ref>
</broadcast-group>
</broadcast-groups>
{code}
and server is started then "netstat -lnp | grep java" shows:
{code}
[jbossqa@station1 test-eap6]$ netstat -lnp | grep java
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:5455 0.0.0.0:* LISTEN 21181/java
tcp 0 0 127.0.0.1:9999 0.0.0.0:* LISTEN 21181/java
tcp 0 0 192.168.10.1:8080 0.0.0.0:* LISTEN 21181/java
tcp 0 0 192.168.10.1:4447 0.0.0.0:* LISTEN 21181/java
tcp 0 0 127.0.0.1:5445 0.0.0.0:* LISTEN 21181/java
tcp 0 0 127.0.0.1:9990 0.0.0.0:* LISTEN 21181/java
tcp 0 0 192.168.10.1:3528 0.0.0.0:* LISTEN 21181/java
udp 0 0 0.0.0.0:9875 0.0.0.0:* 21181/java
udp 0 0 0.0.0.0:40861 0.0.0.0:* 21181/java
udp 0 0 224.0.1.105:23364 0.0.0.0:* 21181/java
{code}
>From this output it looks that hornetq is broadcasting on all interfaces.
--
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
12 years, 8 months
[JBoss JIRA] (AS7-3502) <vault> not supported in standalone.xml - password maskind doesn't work
by Jan Lanik (JIRA)
Jan Lanik created AS7-3502:
------------------------------
Summary: <vault> not supported in standalone.xml - password maskind doesn't work
Key: AS7-3502
URL: https://issues.jboss.org/browse/AS7-3502
Project: Application Server 7
Issue Type: Bug
Components: Security
Environment: commit: fa19da5ffce7ce765af4700af9126c1a9acc5505
Reporter: Jan Lanik
Assignee: Anil Saldhana
Priority: Blocker
I tried to set up Vault as documented here: https://community.jboss.org/wiki/AS7UtilisingMaskedPasswordsViaTheVault
The server did non started because of a parsing error - it seems that it does not know <vault> tag at all (See the stacktrace bellow).
As a consequence Password Masking does not work.
This is a blocker for testsuite development.
14:30:06,876 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([("core-service" => "vault")]): java.lang.RuntimeException: JBAS015804: Error initializing vault -- org.jboss.as.server.services.security.VaultReaderException: org.jboss.security.vault.SecurityVaultException: org.jboss.security.vault.SecurityVaultException: PB00026: Wrong Format:/opt/AS7/PasswordMasking/jboss-as/testsuite/integration/basic/src/test/resources/securitydoes not end with / or \
at org.jboss.as.server.services.security.VaultAddHandler.performRuntime(VaultAddHandler.java:115)
at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:378) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:265) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:193) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.controller.ParallelBootOperationStepHandler.execute(ParallelBootOperationStepHandler.java:161) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:378) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:265) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:193) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:165) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:192) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.server.ServerService.boot(ServerService.java:272)
at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:187) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.as.server.ServerService.boot(ServerService.java:261)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: org.jboss.as.server.services.security.VaultReaderException: org.jboss.security.vault.SecurityVaultException: org.jboss.security.vault.SecurityVaultException: PB00026: Wrong Format:/opt/AS7/PasswordMasking/jboss-as/testsuite/integration/basic/src/test/resources/securitydoes not end with / or \
at org.jboss.as.security.vault.RuntimeVaultReader.createVault(RuntimeVaultReader.java:84)
at org.jboss.as.server.services.security.VaultAddHandler.performRuntime(VaultAddHandler.java:113)
... 15 more
Caused by: org.jboss.security.vault.SecurityVaultException: org.jboss.security.vault.SecurityVaultException: PB00026: Wrong Format:/opt/AS7/PasswordMasking/jboss-as/testsuite/integration/basic/src/test/resources/securitydoes not end with / or \
at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:194)
at org.jboss.as.security.vault.RuntimeVaultReader.createVault(RuntimeVaultReader.java:82)
... 16 more
Caused by: org.jboss.security.vault.SecurityVaultException: PB00026: Wrong Format:/opt/AS7/PasswordMasking/jboss-as/testsuite/integration/basic/src/test/resources/securitydoes not end with / or \
at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java:176)
... 17 more
--
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
12 years, 8 months
[JBoss JIRA] (AS7-3497) Exception when deploying EJB with duplicated Interceptors-annontation is not informative enough
by Simon Walter (JIRA)
Simon Walter created AS7-3497:
---------------------------------
Summary: Exception when deploying EJB with duplicated Interceptors-annontation is not informative enough
Key: AS7-3497
URL: https://issues.jboss.org/browse/AS7-3497
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.CR1b
Reporter: Simon Walter
Priority: Minor
{noformat}
13:11:12,017 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001:
Failed to start service jboss.deployment.unit."xxx.ear".WeldService:
org.jboss.msc.service.StartException in service jboss.deployment.unit."xxx.ear".WeldService:
org.jboss.interceptor.proxy.InterceptorException:
Duplicate interceptor class definition when bindingorg.jboss.interceptor.reader.SimpleInterceptorMetadata@1db7445 on AROUND_INVOKE
{noformat}
The exception should contains information regarding the interceptor or the annotated class:
org.jboss.interceptor.builder.InterceptionModelImpl Line 162: {code}throw new InterceptorException("Duplicate interceptor class definition when binding" + interceptor + " on " + interceptionType.name());{code} should at least be
{code}throw new InterceptorException("Duplicate interceptor class definition when binding" + interceptor.getInterceptorClass().getClassName() + " on " + interceptionType.name());{code}
--
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
12 years, 8 months
[JBoss JIRA] (AS7-3489) Arquillian should not be modifying mgmt-users.properties
by Stuart Douglas (JIRA)
Stuart Douglas created AS7-3489:
-----------------------------------
Summary: Arquillian should not be modifying mgmt-users.properties
Key: AS7-3489
URL: https://issues.jboss.org/browse/AS7-3489
Project: Application Server 7
Issue Type: Feature Request
Components: Test Suite
Affects Versions: 7.1.0.CR1b
Reporter: Stuart Douglas
Assignee: Ondrej Zizka
At the moment arquillian overwrites mgmt-users.properties.
This is a feature we need for our testsuite, it is not something that the average end user of arquillian would expect. Instead when we build our server config in the testsuite a mgmt-users.properties file should be created/copied in.
The only affected test appears to be org.jboss.as.test.smoke.surefire.servermodule.HttpDeploymentUploadUnitTestCase, which I am going to ignore for now.
--
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
12 years, 8 months
[JBoss JIRA] (AS7-3496) CLONE - Unexpected auth dir in standalone/tmp when -Djboss.server.temp.dir is used
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created AS7-3496:
--------------------------------------
Summary: CLONE - Unexpected auth dir in standalone/tmp when -Djboss.server.temp.dir is used
Key: AS7-3496
URL: https://issues.jboss.org/browse/AS7-3496
Project: Application Server 7
Issue Type: Feature Request
Components: Server
Affects Versions: 7.1.0.CR1b
Reporter: Rostislav Svoboda
Assignee: Brian Stansberry
Fix For: 7.1.0.Final
Unexpected 'auth' dir is created in standalone/tmp when -Djboss.server.temp.dir is used.
There shouldn't be tmp directory at all.
Steps to reproduce:
- remove everything from 'standalone' directory with exception for 'configuration' and 'deployments' sub-directories
- run standalone - 'bin/standalone.sh -Djboss.server.log.dir=xx-log -Djboss.server.data.dir=xx-data -Djboss.server.temp.dir=xx-temp -Djboss.server.deploy.dir=xx-deployments'
- list recursively 'standalone' directory -- 'tmp' directory with 'auth' subdirectory is created
'jboss.server.temp.dir' property is not 100% reflected.
--
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
12 years, 8 months