December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1988) Please remove zipeinit.jar from tests

by Marek Goldmann (JIRA)

Please remove zipeinit.jar from tests ------------------------------------- Key: AS7-1988 URL: https://issues.jboss.org/browse/AS7-1988 Project: Application Server 7 Issue Type: Task Components: VFS Reporter: Marek Goldmann Assignee: John Bailey This file contains binary files and the license of it is unclear. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1568) MDB component doesn't setup the correct dependencies on the RA service

by jaikiran pai (JIRA)

MDB component doesn't setup the correct dependencies on the RA service ---------------------------------------------------------------------- Key: AS7-1568 URL: https://issues.jboss.org/browse/AS7-1568 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.1.Final Reporter: jaikiran pai Assignee: jaikiran pai A user has reported that he runs into {code} Caused by: java.lang.IllegalStateException: No resource-adapter has been specified for MessageDrivenComponent MqServiceMessageBean at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:171) {code} when he uses a custom RA which is deployed as an deployment (instead of via the subsystem configuration file). Looking at the code, we don't correctly setup the dependencies between the MDB component create service and the RA service, which can lead to issues like these. See referenced thread for more details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

4
3
0 / 0

[JBoss JIRA] (AS7-2783) servlet/http errors reports the server is 7.0.3

by Max Rydahl Andersen (Created) (JIRA)

servlet/http errors reports the server is 7.0.3 ----------------------------------------------- Key: AS7-2783 URL: https://issues.jboss.org/browse/AS7-2783 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.0.Beta1 Reporter: Max Rydahl Andersen Assignee: Remy Maucherat Start AS 7.1.0.Beta1 goto a page that does not exist, i.e. http://localhost:8080/tesla Title says "JBoss Web/7.0.3.Final" Should say "JBoss Web/7.1.0.Beta1" I assume ? -- 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, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-2904) Cannot execute composite operations on a slave HC

by Brian Stansberry (Created) (JIRA)

Cannot execute composite operations on a slave HC ------------------------------------------------- Key: AS7-2904 URL: https://issues.jboss.org/browse/AS7-2904 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Beta1 Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker Fix For: 7.1.0.CR1 Trying to execute a composite op on a slave HC results in: { "outcome" => "failed", "failure-description" => "Operation composite for address [] can only handled by the master Domain Controller; this host is not the master Domain Controller", "rolled-back" => true } -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] (AS7-2905) Reduce logging level on non-OFE management API user errors

by Brian Stansberry (Created) (JIRA)

Reduce logging level on non-OFE management API user errors ----------------------------------------------------------- Key: AS7-2905 URL: https://issues.jboss.org/browse/AS7-2905 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.CR1 A number of methods in OperationContext and similar places throw runtime exceptions when error conditions are detected that are really due to user mistakes (e.g. trying to add a resource that's already present.) These are caught and logged at ERROR. It would be better if OperationFailedException were thrown, since those are only logged at DEBUG -- logging client request errors at ERROR in the server log is noisy and will anger admins. Unfortunately, OFE is a checked exception, so we can't throw it without making an incompatible API change that may break subsystems. Solution is to create an OperationFailedRuntimeException and throw that. The logic that catches and handles OFE will do the same thing for OFRE. -- 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, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1457) Cleaner Security Provider Registration

by Darran Lofthouse (JIRA)

Cleaner Security Provider Registration -------------------------------------- Key: AS7-1457 URL: https://issues.jboss.org/browse/AS7-1457 Project: Application Server 7 Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 Currently the SASL security provider registration occurs each place that it is identified as required. Everything however is modules based so we should see if there is a cleaner way this can happen - even if it was as simple as having a class executed automatically as the module is loaded. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

7
10
0 / 0

[JBoss JIRA] (AS7-2902) Upgrade to JBoss SASL 1.0.0.Beta10

by Darran Lofthouse (Created) (JIRA)

Upgrade to JBoss SASL 1.0.0.Beta10 ---------------------------------- Key: AS7-2902 URL: https://issues.jboss.org/browse/AS7-2902 Project: Application Server 7 Issue Type: Task Components: Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.CR1 -- 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, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-2906) Datasource does not support long username

by hantsy bai (Created) (JIRA)

Datasource does not support long username ----------------------------------------- Key: AS7-2906 URL: https://issues.jboss.org/browse/AS7-2906 Project: Application Server 7 Issue Type: Bug Environment: JBoss 7.0.2.Final JBoss Maven Plugin 7.0.2.Final Reporter: hantsy bai I tried to create a datasource for my demo(seam3-sandbox on github) via jboss maven plugin. When I use "seam3sandboxuser" and "seam3sandboxpass" as user/password pair, the datasource was created, but I can not connect to the mysql database. Connection exception will be thrown at Jboss starts up. After I changed user/password to "seam3user"/"seam3pass", it was connected successfully. PS: I created the related user/pass in mysql before I execute mvn command. -- 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, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-2081) read-resource with recurse and include-runtime is broken

by David Bosschaert (Created) (JIRA)

read-resource with recurse and include-runtime is broken -------------------------------------------------------- Key: AS7-2081 URL: https://issues.jboss.org/browse/AS7-2081 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Beta1 Reporter: David Bosschaert When I add recursive=true to :read-resource the runtime attributes disappear. E.g. {code}subsystem=osgi] :read-resource(include-runtime=true) { "outcome" => "success", "result" => { "activation" => "eager", "startlevel" => 1, "bundle" => { "19" => undefined, "17" => undefined, "18" => undefined, {code} The above works, but adding recursive=true produces: {code}subsystem=osgi] :read-resource(include-runtime=true,rrecursive=true) { "outcome" => "success", "result" => { "activation" => "eager", "bundle" => { "20" => {}, "21" => {}, {code} The startlevel attribute is gone and the bundle resources are empty. Note that when I run :read-children-resources it does return the correct information {code}subsystem=osgi] :read-children-resources(child-type=bundle,include-runtime=true) { "outcome" => "success", "result" => { "0" => { "id" => 0L, "startlevel" => 0, "state" => "ACTIVE", "symbolic-name" => "system.bundle", "version" => "0.0.0" }, "1" => { "id" => 1L, "startlevel" => 1, "state" => "INSTALLED", "symbolic-name" => "javaee.api", "version" => "0.0.0" }, {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, 7 months

7
10
0 / 0

[JBoss JIRA] (AS7-2136) Can't wire up MDBs when multiple RARs are deployed

by Carlo de Wolf (Created) (JIRA)

Can't wire up MDBs when multiple RARs are deployed -------------------------------------------------- Key: AS7-2136 URL: https://issues.jboss.org/browse/AS7-2136 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Carlo de Wolf Assignee: Jesper Pedersen Fix For: 7.1.0.CR1 Whenever multiple RARs are deployed backed by the same implementation class an MDB is unable to wire up to the correct RAR. {code:java} @MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/test") }) @ResourceAdapter("external-hornetq-ra.rar") public class ReplyingMDB implements MessageListener {code} {noformat} 10:00:01,502 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC00001: Failed to start service jboss.deployment.unit."ejb3mdb.jar".component.ReplyingMDB.CREATE: org.jboss.msc.service.StartException in service jboss.deployment.unit."ejb3mdb.jar".component.ReplyingMDB.CREATE: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [:1.6.0_26] Caused by: java.lang.IllegalStateException: found more than one RA registered external-hornetq-ra at org.jboss.as.ejb3.component.EJBUtilities.createActivationSpecs(EJBUtilities.java:126) at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentCreateService.createComponent(MessageDrivenComponentCreateService.java:78) at org.jboss.as.ee.component.BasicComponentCreateService.start(BasicComponentCreateService.java:78) 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] ... 3 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

14 years, 7 months

8
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 December 2011