January 2012 - jboss-jira - Jboss List Archives

[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

14 years, 3 months

3
4
0 / 0

[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

14 years, 3 months

1
3
0 / 0

[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

14 years, 3 months

1
0
0 / 0

[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

14 years, 3 months

2
9
0 / 0

[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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3494) Missing dependencies log4j module

by Maas van den Berg (JIRA)

Maas van den Berg created AS7-3494: -------------------------------------- Summary: Missing dependencies log4j module Key: AS7-3494 URL: https://issues.jboss.org/browse/AS7-3494 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.0.Final Reporter: Maas van den Berg Assignee: James Perkins Fix For: 7.1.0.Final Since AS7-1389 deployments fail due to missing dependencies for log4j on *org.dom4j* and *org.w3c.dom.Node* Modifying the module.xml for org\apache\log4j resolves the issue: {code} <module xmlns="urn:jboss:module:1.1" name="org.apache.log4j"> <resources> <resource-root path="log4j-1.2.16.jar"/>  </resources> <dependencies> <module name="org.dom4j"/> <module name="javax.api"/> </dependencies> </module> {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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3493) Remove cxf-xjc-bug671.jar

by Alessio Soldano (JIRA)

Alessio Soldano created AS7-3493: ------------------------------------ Summary: Remove cxf-xjc-bug671.jar Key: AS7-3493 URL: https://issues.jboss.org/browse/AS7-3493 Project: Application Server 7 Issue Type: Task Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 7.1.0.Final As per https://issues.jboss.org/browse/JBWS-3374, cxf-xjc-bug671.jar needs to be removed as it's not needed. -- 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-2981) Provide consistent behaviour to enable/disable datasources and resource adaptes

by Heiko Braun (Created) (JIRA)

Provide consistent behaviour to enable/disable datasources and resource adaptes ------------------------------------------------------------------------------- Key: AS7-2981 URL: https://issues.jboss.org/browse/AS7-2981 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 For datasources there is a disable operation, for resource adapters it's an attribute. consistency is required. -- 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
4
0 / 0

[JBoss JIRA] (AS7-3442) 'jms-destinations' section disappears from config file

by Dmitry Savenko (JIRA)

Dmitry Savenko created AS7-3442: ----------------------------------- Summary: 'jms-destinations' section disappears from config file Key: AS7-3442 URL: https://issues.jboss.org/browse/AS7-3442 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.CR1b Environment: Linux 2.6.32-37-generic-pae #81-Ubuntu SMP i686 GNU/Linux java version "1.6.0_30" Java(TM) SE Runtime Environment (build 1.6.0_30-b12) Java HotSpot(TM) Server VM (build 20.5-b03, mixed mode) Reporter: Dmitry Savenko Steps to reproduce: 1. Unpack fresh jboss 7.1.0CR1b from here: http://download.jboss.org/jbossas/7.1/jboss-as-7.1.0.CR1b/jboss-as-7.1.0.... 2. Open standalone-full.xml config file and remove this: <jms-topic name="testTopic"> <entry name="topic/test"/> </jms-topic> So, jms-destinations section should look like this: <jms-destinations> <jms-queue name="testQueue"> <entry name="queue/test"/> </jms-queue> </jms-destinations> 3. Start the server: bin/standalone.sh --server-config=standalone-full.xml 4. Deploy 'helloworld' quickstart: mvn clean package jboss-as:deploy Results: jms-destinations section (with 'testQueue') completely disappears from the config file. I did it on JBoss AS 7.0.2 (with standalone-preview.xml, since there is no standalone-full.xml there), and everything works fine, i.e. jms-destinations section is not removed. -- 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
3
0 / 0

[JBoss JIRA] (AS7-2006) Allow re-entrance into SFSB under specific conditions by default (non-spec compliant)

by Carlo de Wolf (Created) (JIRA)

Allow re-entrance into SFSB under specific conditions by default (non-spec compliant) ------------------------------------------------------------------------------------- Key: AS7-2006 URL: https://issues.jboss.org/browse/AS7-2006 Project: Application Server 7 Issue Type: Feature Request Components: EJB Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 7.1.0.CR1 Make it possible to re-enter a SFSB when a flag is set. Under specific conditions, which will be outlined in the documentation, re-entrance will then be allowed (similar to an Entity EJB re-entrance as outlined in EJB 3.1 FR 8.5.13). The re-entrance flag will be set by default (which is non-spec compliant). -- 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

5
7
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