June 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-14) Remove deprecated attributes of messaging subsystem in console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-14?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration updated WFLY-14: ---------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=948900 (was: https://bugzilla.redhat.com/show_bug.cgi?id=908664) > Remove deprecated attributes of messaging subsystem in console > -------------------------------------------------------------- > > Key: WFLY-14 > URL: https://issues.jboss.org/browse/WFLY-14 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Minor > Labels: console_1.5.3, merged > Fix For: 8.0.0.CR1 > > > The attribute {{failover-on-server-shutdown}} in > * {{/subsystem=messaging/hornetq-server=default/connection-factory=*}} and > * {{/subsystem=messaging/hornetq-server=default/bridge=*}} > is deprecated and should be removed from the UI. The relevant classes in the UI are > * {{org.jboss.as.console.client.shared.subsys.messaging.model.ConnectionFactory}} > * {{org.jboss.as.console.client.shared.subsys.messaging.model.Bridge}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-14) Remove deprecated attributes of messaging subsystem in console

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-14?page=com.atlassian.jira.plugin.sy... ] Heiko Braun resolved WFLY-14. ----------------------------- Resolution: Done > Remove deprecated attributes of messaging subsystem in console > -------------------------------------------------------------- > > Key: WFLY-14 > URL: https://issues.jboss.org/browse/WFLY-14 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Minor > Labels: console_1.5.3, merged > Fix For: 8.0.0.CR1 > > > The attribute {{failover-on-server-shutdown}} in > * {{/subsystem=messaging/hornetq-server=default/connection-factory=*}} and > * {{/subsystem=messaging/hornetq-server=default/bridge=*}} > is deprecated and should be removed from the UI. The relevant classes in the UI are > * {{org.jboss.as.console.client.shared.subsys.messaging.model.ConnectionFactory}} > * {{org.jboss.as.console.client.shared.subsys.messaging.model.Bridge}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-14) Remove deprecated attributes of messaging subsystem in console

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-14?page=com.atlassian.jira.plugin.sy... ] RH Bugzilla Integration updated WFLY-14: ---------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=908664, https://bugzilla.redhat.com/show_bug.cgi?id=948900 (was: https://bugzilla.redhat.com/show_bug.cgi?id=908664) > Remove deprecated attributes of messaging subsystem in console > -------------------------------------------------------------- > > Key: WFLY-14 > URL: https://issues.jboss.org/browse/WFLY-14 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Priority: Minor > Labels: console_1.5.3, merged > Fix For: 8.0.0.CR1 > > > The attribute {{failover-on-server-shutdown}} in > * {{/subsystem=messaging/hornetq-server=default/connection-factory=*}} and > * {{/subsystem=messaging/hornetq-server=default/bridge=*}} > is deprecated and should be removed from the UI. The relevant classes in the UI are > * {{org.jboss.as.console.client.shared.subsys.messaging.model.ConnectionFactory}} > * {{org.jboss.as.console.client.shared.subsys.messaging.model.Bridge}} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1450) NPE when add ejb3/cache

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-1450?page=com.atlassian.jira.plugin.... ] jaikiran pai resolved WFLY-1450. -------------------------------- Resolution: Duplicate Issue Thank you for reporting this. I just created a JIRA for this a few minutes back and sent a pull request containing the fix. The JIRA is WFLY-1449. I'll mark this one as a duplicate of WFLY-1449. > NPE when add ejb3/cache > ----------------------- > > Key: WFLY-1450 > URL: https://issues.jboss.org/browse/WFLY-1450 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: 金沢栄治 > Assignee: jaikiran pai > Priority: Minor > > In EAP 6.1.0, NPE happens when I add ejb3/cache using the following cli: > ./subsystem=ejb3/cache=my-cache:add(passivation-store=infinispan) > with the next outputs. > > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("add") failed - address: ([ > ("subsystem" => "ejb3"), > ("cache" => "my-cache") > ]): java.lang.NullPointerException > at java.util.HashSet.<init>(HashSet.java:116) [rt.jar:1.6.0_24] > at org.jboss.as.ejb3.subsystem.CacheFactoryAdd.installRuntimeServices(CacheFactoryAdd.java:83) > at org.jboss.as.ejb3.subsystem.CacheFactoryAdd.performRuntime(CacheFactoryAdd.java:74) > at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > When I add the aliases attribute, it becomes OK, but aliases attribute is nillable, it should ok without the aliases attribute. > And it's OK in EAP 6.0.1 withoutthe aliases attribute. > So I did some research, and it turned out the StringListAttributeDefinition#unwrap will return null when the attribute is not defined. > I also believe there are more subsystems have the same problem other than the ejb3/cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1450) NPE when add ejb3/cache

by 金沢栄治 (JIRA)

金沢栄治 created WFLY-1450: --------------------------- Summary: NPE when add ejb3/cache Key: WFLY-1450 URL: https://issues.jboss.org/browse/WFLY-1450 Project: WildFly Issue Type: Bug Components: EJB Reporter: 金沢栄治 Assignee: jaikiran pai Priority: Minor In EAP 6.1.0, NPE happens when I add ejb3/cache using the following cli: ./subsystem=ejb3/cache=my-cache:add(passivation-store=infinispan) with the next outputs. ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("add") failed - address: ([ ("subsystem" => "ejb3"), ("cache" => "my-cache") ]): java.lang.NullPointerException at java.util.HashSet.<init>(HashSet.java:116) [rt.jar:1.6.0_24] at org.jboss.as.ejb3.subsystem.CacheFactoryAdd.installRuntimeServices(CacheFactoryAdd.java:83) at org.jboss.as.ejb3.subsystem.CacheFactoryAdd.performRuntime(CacheFactoryAdd.java:74) at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] When I add the aliases attribute, it becomes OK, but aliases attribute is nillable, it should ok without the aliases attribute. And it's OK in EAP 6.0.1 withoutthe aliases attribute. So I did some research, and it turned out the StringListAttributeDefinition#unwrap will return null when the attribute is not defined. I also believe there are more subsystems have the same problem other than the ejb3/cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1449) NullPointerException while adding CacheFactory through EJB3 subsystem

by jaikiran pai (JIRA)

jaikiran pai created WFLY-1449: ---------------------------------- Summary: NullPointerException while adding CacheFactory through EJB3 subsystem Key: WFLY-1449 URL: https://issues.jboss.org/browse/WFLY-1449 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 8.0.0.Alpha1 Reporter: jaikiran pai Assignee: jaikiran pai A user has reported a NPE while adding the cache through the management operation in EJB3 subsystem. Please see the referenced forum thread for details -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1388) Cannot load module alias defined for root deployment

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1388?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated WFLY-1388: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/4547, https://github.com/wildfly/wildfly/pull/4584 (was: https://github.com/wildfly/wildfly/pull/4547) > Cannot load module alias defined for root deployment > ---------------------------------------------------- > > Key: WFLY-1388 > URL: https://issues.jboss.org/browse/WFLY-1388 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 8.0.0.Alpha2 > > > A module defined like this cannot get loaded by its module-alias > {code} > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <deployment> > <resources> > <resource-root path="wrapped-resource.jar" use-physical-code-source="true"/> > </resources> > <dependencies> > <module name="javax.api"/> > <module name="javax.jms.api"/> > <module name="org.apache.camel.core"/> > <module name="org.springframework.beans"/> > <module name="org.springframework.context"/> > <module name="org.springframework.core"/> > <module name="org.springframework.jms"/> > <module name="org.springframework.transaction"/> > <module name="org.slf4j"/> > </dependencies> > <module-alias name="org.apache.camel.component.jms"/> > </deployment> > </jboss-deployment-structure> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-5761) EJB2 entity bean CMP collection toArray throws NPE

by Jay Kris (JIRA)

[ https://issues.jboss.org/browse/AS7-5761?page=com.atlassian.jira.plugin.s... ] Jay Kris commented on AS7-5761: ------------------------------- Seems this issue is still present in Jboss EAP 6.1 final. > EJB2 entity bean CMP collection toArray throws NPE > --------------------------------------------------- > > Key: AS7-5761 > URL: https://issues.jboss.org/browse/AS7-5761 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final, 7.1.3.Final (EAP) > Environment: MAC OSX, Java7 > Reporter: Lucas Galfaso > Assignee: Pieter Bos > Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP) > > > From an EJB2 entity bean that has a CMP collection of entities, calling toArray() on the CMP collection throws NullPointerException > Caused by: java.lang.NullPointerException > at org.jboss.as.cmp.jdbc.bridge.RelationSet.toArray(RelationSet.java:291) [jboss-as-cmp-7.1.1.Final.jar:7.1.1.Final] > Normal iteration thru the collection using the iterator works as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1448) MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase failed due to NamingException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1448?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1448: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=907542 > MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase failed due to NamingException > ---------------------------------------------------------------------------------------------- > > Key: WFLY-1448 > URL: https://issues.jboss.org/browse/WFLY-1448 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 8.0.0.Alpha2 > > > MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase from EAP 6.1.0 TS fail due to NamingException. > Both tests use hardcoded address like: env.put(Context.PROVIDER_URL, "remote://localhost:4447"); > When Jenkins configures to use other address, they will failed with NamingException. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1448) MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase failed due to NamingException

by Chao Wang (JIRA)

Chao Wang created WFLY-1448: ------------------------------- Summary: MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase failed due to NamingException Key: WFLY-1448 URL: https://issues.jboss.org/browse/WFLY-1448 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 8.0.0.Alpha1 Reporter: Chao Wang Assignee: Chao Wang Fix For: 8.0.0.Alpha2 MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase from EAP 6.1.0 TS fail due to NamingException. Both tests use hardcoded address like: env.put(Context.PROVIDER_URL, "remote://localhost:4447"); When Jenkins configures to use other address, they will failed with NamingException. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
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 June 2013