October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8952) Fix the testsuite/integration testcase failures

by jaikiran pai (JIRA)

Fix the testsuite/integration testcase failures ----------------------------------------------- Key: JBAS-8952 URL: https://issues.jboss.org/browse/JBAS-8952 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Environment: JBoss AS7 master Reporter: jaikiran pai Assignee: Shelly McGowan Fix For: 7.0.0.CR1 As reported in the mailing list http://lists.jboss.org/pipermail/jboss-as7-dev/2011-March/000759.html thread, the "testsuite/integration" tests are failing with a CCE in JSFUnitApplicationArchiveProcessor: {code} Caused by: java.lang.ClassCastException: org.jboss.shrinkwrap.impl.base.spec.ResourceAdapterArchiveImpl cannot be cast to org.jboss.shrinkwrap.api.spec.WebArchive at org.jboss.jsfunit.arquillian.JSFUnitApplicationArchiveProcessor.process(JSFUnitApplicationArchiveProcessor.java:41) at org.jboss.arquillian.impl.ClientDeploymentGenerator.applyApplicationProcessors(ClientDeploymentGenerator.java:91) at org.jboss.arquillian.impl.ClientDeploymentGenerator.generate(ClientDeploymentGenerator.java:64) at org.jboss.arquillian.impl.handler.ArchiveGenerator.callback(ArchiveGenerator.java:52) at org.jboss.arquillian.impl.handler.ArchiveGenerator.callback(ArchiveGenerator.java:42) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) {code} The tests are currently disabled and need to be fixed and enabled in some upcoming release. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

6
10
0 / 0

[JBoss JIRA] Created: (JBAS-8744) Failure to start the JVM should trigger a management update plan to rollback

by Andrig Miller (JIRA)

Failure to start the JVM should trigger a management update plan to rollback ---------------------------------------------------------------------------- Key: JBAS-8744 URL: https://issues.jboss.org/browse/JBAS-8744 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Alpha1 Reporter: Andrig Miller Assignee: Brian Stansberry Fix For: 7.0.0.Beta1 I have come across situations where certain JVM options, typically related to NUMA options, can cause the JVM to segfault. With our domain model, we expose the ability to set the JVM options, so I think this certainly would be a possibility. So, as we discussed on the Andiamo call today, this type of situation should cause a rollback of the management update plan, if the JVM fails to start. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-9204) On component stop, destroy all instances

by David Lloyd (JIRA)

On component stop, destroy all instances ---------------------------------------- Key: JBAS-9204 URL: https://issues.jboss.org/browse/JBAS-9204 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EE Reporter: David Lloyd Fix For: 7.0.0.Beta3 This will cause all outstanding component destroy lifecycle methods to be invoked when the component is stopped. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
9
0 / 0

[JBoss JIRA] (AS7-2131) Eliminate JNP usage in HornetQ

by David Lloyd (Created) (JIRA)

Eliminate JNP usage in HornetQ ------------------------------ Key: AS7-2131 URL: https://issues.jboss.org/browse/AS7-2131 Project: Application Server 7 Issue Type: Task Components: JMS Reporter: David Lloyd Assignee: Clebert Suconic Priority: Blocker Fix For: 7.1.0.Beta1 Currently HQ is using JNP to get the JNDI mapping for queues and stuff. This will be changed to use a client-side JNDI URL scheme, such as "hq:xxxx" to generate the client-side interfaces much like EJB uses the "ejb:" scheme. There is no server-round trip for this and it will enable us to remove the JNP sockets from the server configuration, which should never have been introduced. -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] (AS7-2313) read-operation-name and read-operation-description should be combined

by Kevin Barfield (Created) (JIRA)

read-operation-name and read-operation-description should be combined --------------------------------------------------------------------- Key: AS7-2313 URL: https://issues.jboss.org/browse/AS7-2313 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Kevin Barfield Assignee: Alexey Loubyansky For usability, there should be a way to get a list of operation names with the descriptions attached Example: read-resource - This shows you the resources at the this node etc etc etc -- 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, 11 months

5
6
0 / 0

[JBoss JIRA] Created: (JBAS-9224) Automatic JNDI implementation

by David Lloyd (JIRA)

Automatic JNDI implementation ----------------------------- Key: JBAS-9224 URL: https://issues.jboss.org/browse/JBAS-9224 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EE, Naming Reporter: David Lloyd Assignee: John Bailey Priority: Critical The JNDI subsystem should become fully service-oriented, meaning: 1) Contexts are always read-only 2) The NamingStore is populated solely by services 3) When the last binding in a context is removed, the context is automatically removed For pesky legacy subsystems which still expect to be able to bind into Context, we could possibly make up a "fake" Context from which the bound ObjectFactory (or whatever) is extracted to create the "real" service. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
10
0 / 0

[JBoss JIRA] Created: (JBAS-9011) Deployment phases need cleaning up

by David Lloyd (JIRA)

Deployment phases need cleaning up ---------------------------------- Key: JBAS-9011 URL: https://issues.jboss.org/browse/JBAS-9011 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 Every deployment phase adds a level of latency to deployment; thus we need to minimize them. There are some phases which are redundant, and some which are wholly unused which need to be consolidated and cleaned up. The deployment phase numbering should be finalized at this time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8979) Rename "ejb3" subsystem to "ejb"

by David Lloyd (JIRA)

Rename "ejb3" subsystem to "ejb" -------------------------------- Key: JBAS-8979 URL: https://issues.jboss.org/browse/JBAS-8979 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Minor Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
3
0 / 0

[JBoss JIRA] (AS7-2279) SocketBindingGroup not defined for server

by Heiko Braun (Created) (JIRA)

SocketBindingGroup not defined for server ----------------------------------------- Key: AS7-2279 URL: https://issues.jboss.org/browse/AS7-2279 Project: Application Server 7 Issue Type: Clarification Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 How can it be that a server has no explicit socket binding association? See server-one for instance: {noformat} <servers> <server name="server-one" group="main-server-group" auto-start="true"/> <server name="server-two" group="main-server-group" auto-start="false"> <system-properties> <property name="server" value="two" boot-time="false"/> </system-properties> <socket-binding-group ref="standard-sockets" port-offset="150"/> </server> <server name="server-three" group="other-server-group" auto-start="false"> <system-properties> <property name="a" value="a" boot-time="false"/> <property name="b" value="b"/> </system-properties> <socket-binding-group ref="ha-sockets" port-offset="250"/> </server> </servers> {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, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-8578) JMXConnector should support "jmxconnector" alias used by jmx-remoting.sar

by Scott Marlow (JIRA)

JMXConnector should support "jmxconnector" alias used by jmx-remoting.sar ------------------------------------------------------------------------- Key: JBAS-8578 URL: https://jira.jboss.org/browse/JBAS-8578 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMX Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 6.0.0.Final, 7.0.0.M2 For users that might of previously used jmx-remoting.sar. Add /jmxrmi alias for AS6+AS7. They could also later change their application for AS6/AS7 to use the "service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi" URL. This should be a one line change (I hope :-): registry.rebind("jmxrmi", rmiServer.toStub()); registry.rebind("jmxconnector", rmiServer.toStub()); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011