August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5339) JBoss 7.2-alpha.zip

by Rodney Kite (JIRA)

Rodney Kite created AS7-5339: -------------------------------- Summary: JBoss 7.2-alpha.zip Key: AS7-5339 URL: https://issues.jboss.org/browse/AS7-5339 Project: Application Server 7 Issue Type: Bug Components: Class Loading Affects Versions: 7.2.0.Alpha1 Environment: Windows 7 64 bit, Oracle Jdk 1.6.0 32 bit Reporter: Rodney Kite Assignee: David Lloyd During deployment there is an ERROR. Failed to start service jboss.module.service."deployment.Mef.ear".main JBAS018759: Failed to load module: deployment.Mef.ear:main ... Caused by: org.jboss.modules.ModuleNotFoundException: deployment.MefBusiness.ear.mefCommon.jar:main A deployment ear has a jar that references another deployment ears jar/module indicated in the referencing jars "Dependencies:" secion of its Manifest.MF. It seems that dynamic deployment modules are not visible to other ears referencing them. This works fine in JBoss 7.1.1 -- 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

11 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1370) Domain Management - Add support for database authentication.

by Darran Lofthouse (JIRA)

Domain Management - Add support for database authentication. ------------------------------------------------------------ Key: AS7-1370 URL: https://issues.jboss.org/browse/AS7-1370 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 It should be possible to define a database authentication element for authentication of incoming connections against a database. Ideally the password should be obtainable from the database to allow us to use DIGEST authentication but if not a fallback to verify the password should be supported. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

4
5
0 / 0

[JBoss JIRA] (AS7-3570) jboss-ejb3.xml is not valided

by Simon Walter (JIRA)

Simon Walter created AS7-3570: --------------------------------- Summary: jboss-ejb3.xml is not valided Key: AS7-3570 URL: https://issues.jboss.org/browse/AS7-3570 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.CR1b Reporter: Simon Walter Priority: Minor When deploying a module with invalid jboss-ejb3.xml (missing <ejb-name> in <assembly-descriptor><security:security>) there is no validation and an NPE is thrown at deployment time. {noformat} 11:02:45,347 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."xxx.ear"."xxx-impl.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."xxx.ear"."xxx-impl.jar".POST_MODULE: Failed to process phase POST_MODULE of subdeployment "xxx-impl.jar" of deployment "xxx.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014402: Could not merge data for XXXImpl at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.deploy(AbstractMergingProcessor.java:75) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b] ... 5 more Caused by: java.lang.NullPointerException at org.jboss.as.ejb3.deployment.processors.merging.SecurityDomainMergingProcessor.handleDeploymentDescriptor(SecurityDomainMergingProcessor.java:83) at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.processComponentConfig(AbstractMergingProcessor.java:93) at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.deploy(AbstractMergingProcessor.java:73) ... 6 more {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

11 years, 10 months

4
5
0 / 0

[JBoss JIRA] (JBMETA-360) EJB bound parsers should validate ejb name is set

by Eduardo Martins (JIRA)

Eduardo Martins created JBMETA-360: -------------------------------------- Summary: EJB bound parsers should validate ejb name is set Key: JBMETA-360 URL: https://issues.jboss.org/browse/JBMETA-360 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: ejb Reporter: Eduardo Martins Assignee: Eduardo Martins Fix For: 7.0.4 This issue is a consequence of https://issues.jboss.org/browse/AS7-3570 , please refer to it for full details. -- 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

11 years, 10 months

1
1
0 / 0

[JBoss JIRA] (AS7-5259) DataSourceOperationsUnitTestCase fails with db other then h2

by Honza Brázdil (JIRA)

Honza Brázdil created AS7-5259: ---------------------------------- Summary: DataSourceOperationsUnitTestCase fails with db other then h2 Key: AS7-5259 URL: https://issues.jboss.org/browse/AS7-5259 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.2.Final (EAP) Reporter: Honza Brázdil Assignee: Stefano Maestri Tests in DataSourceOperationsUnitTestCase fails if run with other database then h2 (-Dds=...). The test should be independent on the ExampleDS datasource. {code} $ mvn install -Dds=mysql51 -rf testsuite/integration/smoke ... Results : Tests in error: testSendWithTxCommit(org.jboss.as.test.smoke.stilts.SimpleStompletTestCase): Connection timed out. testAddDsAndTestConnection(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddDisabledDsEnableItAndTestConnection(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddDsWithConnectionProperties(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddAndRemoveSameName(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddAndRemoveNameAndJndiNameDifferent(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddAndRemoveXaDs(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testMarshallUnmarshallXaDs(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." disableAndReEnableXaDs(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddXaDsWithProperties(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddComplexDs(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testAddComplexXaDs(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testXaDsWithSystemProperties(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS010468: Driver named \"h2\" is not installed." testDsWithSystemProperties(org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase): Management operation failed: "JBAS014803: Duplicate resource [(\"system-property\" => \"sql.parameter\")]" {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

11 years, 10 months

4
6
0 / 0

[JBoss JIRA] (AS7-5312) Update to console 1.4.0.Final

by Heiko Braun (JIRA)

Heiko Braun created AS7-5312: -------------------------------- Summary: Update to console 1.4.0.Final Key: AS7-5312 URL: https://issues.jboss.org/browse/AS7-5312 Project: Application Server 7 Issue Type: Feature Request Components: Build System Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.3.Final (EAP) -- 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

11 years, 10 months

2
2
0 / 0

[JBoss JIRA] (AS7-5226) CLI: Allows adding a Datasource with both user-name+password and security-domain specified

by Thomas Hauser (JIRA)

Thomas Hauser created AS7-5226: ---------------------------------- Summary: CLI: Allows adding a Datasource with both user-name+password and security-domain specified Key: AS7-5226 URL: https://issues.jboss.org/browse/AS7-5226 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.2.Final (EAP) Reporter: Thomas Hauser Assignee: Stefano Maestri Running the command [standalone@localhost:9999 /] data-source add --name=TestDS1 --jndi-name=java:jboss/examples/TestDS1 --connection-url=localhost:8888/fake-url --driver-name=h2 --user-name=admin --password=something --security-domain=Management -- 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

11 years, 10 months

2
3
0 / 0

[JBoss JIRA] (AS7-5331) @Resource UserTransaction should not be allowed in CMT beans

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-5331: ------------------------------------- Summary: @Resource UserTransaction should not be allowed in CMT beans Key: AS7-5331 URL: https://issues.jboss.org/browse/AS7-5331 Project: Application Server 7 Issue Type: Bug Components: EJB, Transactions Affects Versions: 7.1.2.Final (EAP) Reporter: Dominik Pospisil Assignee: jaikiran pai Currently, it seems then @Resource UserTransaction injection is allowed in CMT beans and injects container managed transaction. In AS/EAP5 this would throw an exception which I think is correct as this violates EJB 3.0 & 3.1 specs. Section 16.12 of the EJB 3.1 specification says: The container must make the UserTransaction interface available to the enterprise beans that are allowed to use this interface (only session and message-driven beans with bean-managed transaction demarcation are allowed to use this interface) either through injection using the Resource annotation or in JNDI under the name java:comp/UserTransaction, in addition to through the EJBContext interface. The authenticationType and shareable elements of the Resource annotation must not be specified. In my interpretation the statement "only session and message-driven beans with bean-managed transaction demarcation are allowed to use this interface" would mean that other beans are prohibited to use this interface. Allowing such beans to use this interface is specification violation. -- 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

11 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-495) Memory leak in NAKACK

by Bela Ban (JIRA)

Memory leak in NAKACK --------------------- Key: JGRP-495 URL: http://jira.jboss.com/jira/browse/JGRP-495 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Priority: Blocker Fix For: 2.5 Probably due to the changes introduced in NAKACK/NakReceiverWindow (http://jira.jboss.com/jira/browse/JGRP-281). To reproduce, run perf.Test on 2 nodes with 1 million 1K messages each. JProfiler shows that we are leaking Map.Entry instances in NAKACK. They seem to accumulate in xmit_table. -- 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

11 years, 10 months

2
3
0 / 0

[JBoss JIRA] (AS7-5335) CLONE - JGroups protocol properties not always being applied to protocol configurations

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created AS7-5335: ---------------------------------------- Summary: CLONE - JGroups protocol properties not always being applied to protocol configurations Key: AS7-5335 URL: https://issues.jboss.org/browse/AS7-5335 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Richard Achmatowicz Assignee: Richard Achmatowicz Fix For: 7.1.3.Final (EAP) In JGroups subsystem processing, JGroups protocol properties are updated correctly in the model but not always correctly applied to the runtime configuration. For example, specifying an MPING.mcast_port as a property of the protocol MPING will be overridden by the value of the multicast port in the associated socket binding. -- 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

11 years, 10 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2012