April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6711) Unable to restart server group in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6711?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6711: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 913236|https://bugzilla.redhat.com/show_bug.cgi?id=913236] from MODIFIED to ON_QA > Unable to restart server group in domain mode > --------------------------------------------- > > Key: AS7-6711 > URL: https://issues.jboss.org/browse/AS7-6711 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: 8.0.0.Alpha1 > > Attachments: AS7-6711-threads.txt > > > Restarting the servers in the standard domain.xml main-server-group will result in a hang in the CLI and in the master HC. > To reproduce start the standard domain.sh and in another window launch the CLI and: > [domain@localhost:9999 /] /server-group=main-server-group:restart-servers > Resulting console log output: > [Host Controller] 18:17:30,511 INFO [org.jboss.as.host.controller] (management-handler-thread - 3) JBAS010923: Stopping server server-one > 18:17:30,515 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 5) JBAS012018: Stopping process 'Server:server-one' > [Server:server-one] 18:17:30,599 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA] > [Server:server-one] 18:17:30,600 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] > [Server:server-one] 18:17:30,611 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003075: Coyote HTTP/1.1 pausing on: http-localhost/127.0.0.1:8080 > [Server:server-one] 18:17:30,612 INFO [org.apache.coyote.http11] (MSC service thread 1-1) JBWEB003077: Coyote HTTP/1.1 stopping on : http-localhost/127.0.0.1:8080 > [Server:server-one] 18:17:30,616 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 79) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory > [Server:server-one] 18:17:30,615 INFO [org.apache.catalina.core] (MSC service thread 1-2) JBWEB001079: Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started > [Server:server-one] 18:17:30,640 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010418: Stopped Driver service with driver-name = h2 > [Server:server-one] 18:17:30,664 INFO [org.hornetq.ra] (MSC service thread 1-4) HQ151005: HornetQ resource adaptor stopped > [Server:server-one] 18:17:30,704 INFO [org.hornetq.core.server] (MSC service thread 1-3) HQ221004: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [93f152f7-8aa1-11e2-8c0e-99b598ec3b97] stopped > [Host Controller] 18:17:30,722 INFO [org.jboss.as.host.controller] (Remoting "pingguo.local:MANAGEMENT" read-1) JBAS010926: Unregistering server server-one > [Server:server-one] 18:17:30,754 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015950: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" stopped in 189ms > [Server:server-one] > 18:17:30,815 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) JBAS012010: Process 'Server:server-one' finished with an exit status of 0 > [Host Controller] 18:17:30,818 INFO [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) JBAS010926: Unregistering server server-one > [Host Controller] 18:17:30,836 INFO [org.jboss.as.host.controller] (management-handler-thread - 3) JBAS010922: Starting server server-one > 18:17:30,845 INFO [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 5) JBAS012017: Starting process 'Server:server-one' > [Server:server-one] 18:17:31,676 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR2 > [Server:server-one] 18:17:32,178 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.1.Final > [Server:server-one] 18:17:32,332 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss AS 8.0.0.Alpha1-SNAPSHOT "TBD" starting > [Server:server-one] 18:17:32,530 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.1.0.Beta9 > [Server:server-one] 18:17:32,538 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.1.0.Beta9 > [Server:server-one] 18:17:32,559 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.15.GA > [Host Controller] 18:17:33,607 INFO [org.jboss.as.domain.controller.mgmt] (Remoting "pingguo.local:MANAGEMENT" task-16) JBAS010920: Server [Server:server-one] registered using connection [Channel ID 2bacdeb7 (inbound) of Remoting connection 49660c5f to /127.0.0.1:60647] > After that everything hangs. -- 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-6760) Enabling data source fails if its not persistent

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6760?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6760: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 920974|https://bugzilla.redhat.com/show_bug.cgi?id=920974] from MODIFIED to ON_QA > Enabling data source fails if its not persistent > ------------------------------------------------ > > Key: AS7-6760 > URL: https://issues.jboss.org/browse/AS7-6760 > Project: Application Server 7 > Issue Type: Bug > Components: JCA > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final), 8.0.0.Alpha1 > Reporter: Bartosz Baranowski > Assignee: Stefano Maestri > > Steps to Reproduce: > 1. data-source add --name=NoTxTradeDataSource --jndi-name=java:jboss/datasources/NoTxTradeDataSource --driver-name=h2 --connection-url=jdbc:h2:notxtrade.db:trade > 2. cd subsystem=datasources/data-source=NoTxTradeDataSource > 3. :enable(persistent=false) > This will fail, as default behavior with persistent=false is to not enable DS. > Error: > Unable to start the ds because it generated more than one cf > This should not happen. -- 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] (JBJCA-1005) SemaphoreArrayListManagedConnectionPool should FIFO

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1005?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1005: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 922793|https://bugzilla.redhat.com/show_bug.cgi?id=922793] from MODIFIED to ON_QA > SemaphoreArrayListManagedConnectionPool should FIFO > --------------------------------------------------- > > Key: JBJCA-1005 > URL: https://issues.jboss.org/browse/JBJCA-1005 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.15.Final, 1.1.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > > Currently behaving in FILO manner -- 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] (JBJCA-1004) Subject / security domain overrides null values from CRI for a datasource with allow-multiple-users

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1004?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1004: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 922793|https://bugzilla.redhat.com/show_bug.cgi?id=922793] from MODIFIED to ON_QA > Subject / security domain overrides null values from CRI for a datasource with allow-multiple-users > --------------------------------------------------------------------------------------------------- > > Key: JBJCA-1004 > URL: https://issues.jboss.org/browse/JBJCA-1004 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.15.Final, 1.1.0.Beta4 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > Attachments: JBJCA-1004-tests.patch, JBJCA-1004.patch > > > An issue cloned from JBPAPP6-1323 for the upstream. > DataSource configured with security-domain using org.picketbox.datasource.security.CallerIdentityLoginModule is able to create correct connection > when one of ds.getConection(username, password) is set to null. > Null parameter is substituted using value of corresponding field from the security-domain. > The datasource is defined using <allow-multiple-users/>. > See test org.jboss.as.test.integration.jca.security.DsWithCallerIdentityLoginModuleTestCase at https://github.com/pskopek/jboss-as/tree/JBPAPP-9583. -- 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] (JBJCA-1006) isSameRmOverride doesn't take effect

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1006?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1006: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 922793|https://bugzilla.redhat.com/show_bug.cgi?id=922793] from MODIFIED to ON_QA > isSameRmOverride doesn't take effect > ------------------------------------ > > Key: JBJCA-1006 > URL: https://issues.jboss.org/browse/JBJCA-1006 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.15.Final, 1.1.0.Beta4 > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 1.0.16.Final, 1.1.0.Beta5 > > -- 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-6722) Quoted script parameters are not properly parsed in the bash script

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6722?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6722: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 918030|https://bugzilla.redhat.com/show_bug.cgi?id=918030] from MODIFIED to ON_QA > Quoted script parameters are not properly parsed in the bash script > ------------------------------------------------------------------- > > Key: AS7-6722 > URL: https://issues.jboss.org/browse/AS7-6722 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.Alpha1 > > > Quotes are added to parameters passed via the command line. When checking the parameters for the {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} properties quoted parameters are not found. -- 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-6699) AS7 messaging resources throws NPE when hornetq-server is a backup

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6699?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6699: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 918131|https://bugzilla.redhat.com/show_bug.cgi?id=918131] from MODIFIED to ON_QA > AS7 messaging resources throws NPE when hornetq-server is a backup > ------------------------------------------------------------------ > > Key: AS7-6699 > URL: https://issues.jboss.org/browse/AS7-6699 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Affects Versions: 7.1.3.Final (EAP) > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > steps to reproduce: > Configure AS7's hornetq-server to be a backup ready for failover. > Run AS7 standalone-full configuration with hornetq-server configured to be a backup: > {noformat} > <hornetq-server> > <backup>true</backup> > ... > {noformat} > The AS7 will start, its hornetq-server too *but* it will not be active: > {noformat} > 18:24:56,527 INFO [org.hornetq.core.server] (HQ119001: Activation for server HornetQServerImpl::serverUUID=349065dd-87f2-11e2-911d-f19bf97ea7a7) HQ002211: HornetQ Backup Server version 2.3.0.CR1 (buzzzzz!, 122) [349065dd-87f2-11e2-911d-f19bf97ea7a7] started, waiting live to fail before it gets active > {noformat} > The hornetq server will not become active until a live node fails. When this occurs, the server will become active, accept connection, create core and JMS resources etc. > The issue is that any runtime operation on a hornetq-server's children will fail. > The runtime operations rely on HornetQ's management resource (eg TopicControl, QueueControl) and these objects are not available until HornetQ server is active. > For AS7 integration that means that we must somehow prevent any runtime changes to any hornetq-server's children resources for a passive server. There are no corresponding runtime resources in HornetQ for them. > Additionnaly, hornetq-server does not expose the "active" runtime attribute to know whether the server is active. -- 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-6550) Confusing behavior of form under the "Unmanaged" tab in deployment's Replace dialog

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6550?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6550: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 912690|https://bugzilla.redhat.com/show_bug.cgi?id=912690] from MODIFIED to ON_QA > Confusing behavior of form under the "Unmanaged" tab in deployment's Replace dialog > ----------------------------------------------------------------------------------- > > Key: AS7-6550 > URL: https://issues.jboss.org/browse/AS7-6550 > 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=912690 -- 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-6744) Upgrade Hibernate to 4.2.0 Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6744?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6744: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 922886|https://bugzilla.redhat.com/show_bug.cgi?id=922886] from NEW to MODIFIED > Upgrade Hibernate to 4.2.0 Final > -------------------------------- > > Key: AS7-6744 > URL: https://issues.jboss.org/browse/AS7-6744 > Project: Application Server 7 > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Dave Stahl > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha1 > > > Upgrade Hibernate from 4.2.0.CR2 to 4.2.0.Final -- 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 ASSIGNED to MODIFIED > 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