April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6549) Remote JNDI is not working with a HornetQ-only JMS bridge

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6549?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6549: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 912653|https://bugzilla.redhat.com/show_bug.cgi?id=912653] from MODIFIED to ON_QA > Remote JNDI is not working with a HornetQ-only JMS bridge > --------------------------------------------------------- > > Key: AS7-6549 > URL: https://issues.jboss.org/browse/AS7-6549 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > The jms-bridge can be used to bridge a hornetq server to another and should work by specifying to use the org.hornetq.module to load the JMS implementation classes. > However, this fails because this module does not have access to the JBoss remote-naming module that is required to connect to remote JBoss JNDI server. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6751) JCA lookup UserTransaction in context java:comp instead of java:jboss

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6751?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6751: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 923230|https://bugzilla.redhat.com/show_bug.cgi?id=923230] from MODIFIED to ON_QA > JCA lookup UserTransaction in context java:comp instead of java:jboss > --------------------------------------------------------------------- > > Key: AS7-6751 > URL: https://issues.jboss.org/browse/AS7-6751 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 8.0.0.Alpha1 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6510) Unable to add Modules for security domains

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6510?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6510: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 909873|https://bugzilla.redhat.com/show_bug.cgi?id=909873] from MODIFIED to ON_QA > Unable to add Modules for security domains > ------------------------------------------ > > Key: AS7-6510 > URL: https://issues.jboss.org/browse/AS7-6510 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: console_1.5.2, merged > Fix For: 8.0.0.Alpha1 > > > See https://bugzilla.redhat.com/show_bug.cgi?id=909873 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6683) Fail to start the messaging subsystem when a connector is not defined

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6683?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6683: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 915369|https://bugzilla.redhat.com/show_bug.cgi?id=915369] from MODIFIED to ON_QA > Fail to start the messaging subsystem when a connector is not defined > --------------------------------------------------------------------- > > Key: AS7-6683 > URL: https://issues.jboss.org/browse/AS7-6683 > Project: Application Server 7 > Issue Type: Feature Request > Components: JMS > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jeff Mesnil > Assignee: Bartosz Baranowski > Fix For: 8.0.0.Alpha1 > > Attachments: AS7-6683.patch > > > <connectors> > <netty-connector name="netty" socket-binding="messaging"/> > <netty-connector name="netty-throughput" socket-binding="messaging-throughput"> > <param key="batch-delay" value="50"/> > </netty-connector> >  > <in-vm-connector name="in-vm" server-id="0"/> > </connectors> > <broadcast-groups> > <broadcast-group name="bg-group1"> > <socket-binding>messaging-group</socket-binding> > <broadcast-period>2000</broadcast-period> > <connector-ref> > connector-to-proxy-directing-to-this-server > </connector-ref> > </broadcast-group> > </broadcast-groups> > Additional info: > 15:56:47,200 WARN [org.hornetq.core.server] (MSC service thread 1-5) HQ222185: There is no connector deployed with name {0}. The broadcast group with name {1} will not be deployed. > 15:56:47,201 ERROR [org.hornetq.core.server] (MSC service thread 1-5) HQ224002: Failure in initialisation: java.lang.NullPointerException > at org.hornetq.core.server.management.impl.ManagementServiceImpl.registerBroadcastGroup(ManagementServiceImpl.java:346) [hornetq-server-2.3.0.CR1.jar:] > at org.hornetq.core.server.cluster.ClusterManager.deployBroadcastGroup(ClusterManager.java:815) [hornetq-server-2.3.0.CR1.jar:] > at org.hornetq.core.server.cluster.ClusterManager.deploy(ClusterManager.java:225) [hornetq-server-2.3.0.CR1.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.initialisePart1(HornetQServerImpl.java:1414) [hornetq-server-2.3.0.CR1.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.access$1000(HornetQServerImpl.java:164) [hornetq-server-2.3.0.CR1.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl$SharedNothingLiveActivation.run(HornetQServerImpl.java:2496) [hornetq-server-2.3.0.CR1.jar:] > at org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:416) [hornetq-server-2.3.0.CR1.jar:] > at org.hornetq.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:464) [hornetq-jms-server-2.3.0.CR1.jar:] > at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:74) [jboss-as-messaging-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_38] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_38] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38] > 15:56:47,205 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.messaging.default.jms.manager: org.jboss.msc.service.StartException in service jboss.messaging.default.jms.manager: java.lang.NullPointerException > at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:97) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_38] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_38] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_38] > Caused by: java.lang.NullPointerException > at org.jboss.as.messaging.jms.JMSService.start(JMSService.java:78) > ... 5 more > HornetQ logs a WARN when a referenced connector is not defined. AS7 should be more careful and reject the operation if that the case. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6516) Wrong value of "runtime-name" property for unmanaged deployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6516?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6516: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 910675|https://bugzilla.redhat.com/show_bug.cgi?id=910675] from MODIFIED to ON_QA > Wrong value of "runtime-name" property for unmanaged deployments > ----------------------------------------------------------------- > > Key: AS7-6516 > URL: https://issues.jboss.org/browse/AS7-6516 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: console_1.5.2, merged > Fix For: 8.0.0.Alpha1 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6714) Update to console 1.5.2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6714?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6714: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 920491|https://bugzilla.redhat.com/show_bug.cgi?id=920491] from MODIFIED to ON_QA > Update to console 1.5.2 > ----------------------- > > Key: AS7-6714 > URL: https://issues.jboss.org/browse/AS7-6714 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: console_1.5.2 > Fix For: 8.0.0.Alpha1 > > > Maintenance release -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6725) <security><application/></security> for a RA should give PoolByCRI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6725?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6725: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 921121|https://bugzilla.redhat.com/show_bug.cgi?id=921121] from MODIFIED to ON_QA > <security><application/></security> for a RA should give PoolByCRI > ------------------------------------------------------------------- > > Key: AS7-6725 > URL: https://issues.jboss.org/browse/AS7-6725 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Critical > Fix For: 8.0.0.Alpha1 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6518) Section "Runtime Operations" should not be visible when empty

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6518?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6518: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 910695|https://bugzilla.redhat.com/show_bug.cgi?id=910695] from MODIFIED to ON_QA > Section "Runtime Operations" should not be visible when empty > ------------------------------------------------------------- > > Key: AS7-6518 > URL: https://issues.jboss.org/browse/AS7-6518 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: console_1.5.2, merged > Fix For: 8.0.0.Alpha1 > > > See https://bugzilla.redhat.com/show_bug.cgi?id=910695 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-4377) Failed to create messaging connection factory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-4377?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-4377: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 908758|https://bugzilla.redhat.com/show_bug.cgi?id=908758] from MODIFIED to ON_QA > Failed to create messaging connection factory > --------------------------------------------- > > Key: AS7-4377 > URL: https://issues.jboss.org/browse/AS7-4377 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Reporter: Heiko Braun > Assignee: Jeff Mesnil > Fix For: 7.1.2.Final (EAP) > > > {noformat} > [INFO] { > [INFO] "compress-large-messages" => false, > [INFO] "failover-on-initial-connection" => false, > [INFO] "failover-on-server-shutdown" => false, > [INFO] "use-global-pools" => true, > [INFO] "address" => [ > [INFO] ("subsystem" => "messaging"), > [INFO] ("hornetq-server" => "default"), > [INFO] ("connection-factory" => "test") > [INFO] ], > [INFO] "operation" => "add", > [INFO] "entries" => ["java:/testCF"], > [INFO] "connector" => ["netty"] > [INFO] } > {noformat} > leads to > {noformat} > 15:28:47,269 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 5) JBAS014612: Operation ("add") failed - address: ([ > ("subsystem" => "messaging"), > ("hornetq-server" => "default"), > ("connection-factory" => "TestCF") > ]): java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] > at org.jboss.as.messaging.jms.ConnectionFactoryAdd.createConfiguration(ConnectionFactoryAdd.java:145) > at org.jboss.as.messaging.jms.ConnectionFactoryAdd.performRuntime(ConnectionFactoryAdd.java:109) > at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:466) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:309) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:299) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] > at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294) > at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201) > at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208) > at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) > at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:80) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81) > at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710) > at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78) > at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] > {noformat} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6664?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6664: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 915317|https://bugzilla.redhat.com/show_bug.cgi?id=915317] from MODIFIED to ON_QA > Unable to turn on/off logging handlers using enable()/disable() in CLI > ---------------------------------------------------------------------- > > Key: AS7-6664 > URL: https://issues.jboss.org/browse/AS7-6664 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Logging > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brian Stansberry > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Peter Kremens reports: > I am unable to use enable/disable operation in logging handlers. > > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Calling disable() won't affect enabled attribute > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable() > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => true, > ... > } > } > {code} > Must use write-attribute instead > {code} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource > { > "outcome" => "success", > "result" => { > "autoflush" => true, > "enabled" => false, > ... > } > } > {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, 3 months

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 April 2013