January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3448) Slave host failure during take-snapshot operation

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3448: ------------------------------------- Summary: Slave host failure during take-snapshot operation Key: AS7-3448 URL: https://issues.jboss.org/browse/AS7-3448 Project: Application Server 7 Issue Type: Bug Components: Domain Management Environment: testsuite/domain/src/test/resources/domain-configs/domain-standard.xml testsuite/domain/src/test/resources/host-configs/host-master.xml testsuite/domain/src/test/resources/host-configs/host-slave.xml Reporter: Dominik Pospisil Assignee: Brian Stansberry Fix For: 7.1.0.Final Take-snapshop operation fails on domain configured with master and slave host. Slave host failure: [Host Controller] 13:29:22,226 ERROR [org.jboss.as.controller.management-operation] (domain-connection-threads - 2) JBAS014612: Operation ("take-snapshot") failed - address: ([]): java.lang.IllegalArgumentException: newValue is null [Host Controller] at org.jboss.dmr.ModelNode.set(ModelNode.java:458) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] [Host Controller] at org.jboss.as.controller.operations.common.SnapshotTakeHandler.execute(SnapshotTakeHandler.java:53) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationSlaveStepHandler.execute(OperationSlaveStepHandler.java:81) [jboss-as-host-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:77) [jboss-as-host-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:119) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.controller.remote.TransactionalModelControllerOperationHandler$ExecuteRequestHandler.doExecute(TransactionalModelControllerOperationHandler.java:141) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.controller.remote.TransactionalModelControllerOperationHandler$ExecuteRequestHandler$1.execute(TransactionalModelControllerOperationHandler.java:127) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$3$1.doExecute(AbstractMessageHandler.java:269) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:425) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0_b147-icedtea] [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0_b147-icedtea] [Host Controller] at java.lang.Thread.run(Thread.java:722) [:1.7.0_b147-icedtea] [Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] Steps to reproduce: dpospisi@simkin bin]$ ./jboss-admin.sh You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. [disconnected /] connect [domain@localhost:9999 /] :take-snapshot I am using domain configuration from testsuite/domain module. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] (AS7-2028) Make host controller's address/port available from a domain mode server's environment

by Kabir Khan (Created) (JIRA)

Make host controller's address/port available from a domain mode server's environment ------------------------------------------------------------------------------------- Key: AS7-2028 URL: https://issues.jboss.org/browse/AS7-2028 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan Fix For: 7.1.0.Beta1 -- 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, 8 months

6
7
0 / 0

[JBoss JIRA] (JGRP-1407) UUID isn't serializable

by Bela Ban (Created) (JIRA)

UUID isn't serializable ----------------------- Key: JGRP-1407 URL: https://issues.jboss.org/browse/JGRP-1407 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0.2, 3.1 UUID doesn't implement Serializable or Externalizable, therefore it cannot be used in MethodCall. The unit test that fails is MethodCallTest.testMarshalling2(). SOLUTION: implement Externalizable (again) -- 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, 8 months

4
7
0 / 0

[JBoss JIRA] (AS7-2219) Thread factory can be removed, even when it is assigned to a pool.

by Stan Silvert (Created) (JIRA)

Thread factory can be removed, even when it is assigned to a pool. ------------------------------------------------------------------ Key: AS7-2219 URL: https://issues.jboss.org/browse/AS7-2219 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.0.Alpha1 Reporter: Stan Silvert Assignee: Brian Stansberry You should not be able to remove a thread factory if it is currently assigned to a thread pool. {code} [standalone@localhost:9999 subsystem=threads] :read-resource(recursive=true) { "outcome" => "success", "result" => { "bounded-queue-thread-pool" => undefined, "scheduled-thread-pool" => undefined, "unbounded-queue-thread-pool" => undefined, "queueless-thread-pool" => {"queueless" => { "blocking" => false, "handoff-executor" => undefined, "keepalive-time" => undefined, "max-threads" => { "count" => 2, "per-cpu" => 1 }, "name" => "queueless", "properties" => undefined, "thread-factory" => "mine" }}, "thread-factory" => {"mine" => { "group-name" => undefined, "name" => "mine", "priority" => "1", "properties" => undefined, "thread-name-pattern" => undefined }} }, "response-headers" => {"process-state" => "reload-required"} } [standalone@localhost:9999 subsystem=threads] cd thread-factory=mine [standalone@localhost:9999 thread-factory=mine] :remove { "outcome" => "success", "response-headers" => {"process-state" => "reload-required"} } [standalone@localhost:9999 thread-factory=mine] cd .. [standalone@localhost:9999 subsystem=threads] :read-resource(recursive=true) { "outcome" => "success", "result" => { "bounded-queue-thread-pool" => undefined, "scheduled-thread-pool" => undefined, "thread-factory" => undefined, "unbounded-queue-thread-pool" => undefined, "queueless-thread-pool" => {"queueless" => { "blocking" => false, "handoff-executor" => undefined, "keepalive-time" => undefined, "max-threads" => { "count" => 2, "per-cpu" => 1 }, "name" => "queueless", "properties" => undefined, "thread-factory" => "mine" }} }, "response-headers" => {"process-state" => "reload-required"} } [standalone@localhost:9999 subsystem=threads] {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

12 years, 8 months

4
5
0 / 0

[JBoss JIRA] (AS7-2226) In console, I can't set a thread pool's thread factory back to undefined after it has been set to some value.

by Stan Silvert (Created) (JIRA)

In console, I can't set a thread pool's thread factory back to undefined after it has been set to some value. ------------------------------------------------------------------------------------------------------------- Key: AS7-2226 URL: https://issues.jboss.org/browse/AS7-2226 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Stan Silvert Assignee: Stan Silvert If a thread pool already has a factory assigned it can only be set to a different factory. It can not be set to undefined. -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] (AS7-3445) CLONE - Fix description for read-resource operation

by Rostislav Svoboda (JIRA)

Rostislav Svoboda created AS7-3445: -------------------------------------- Summary: CLONE - Fix description for read-resource operation Key: AS7-3445 URL: https://issues.jboss.org/browse/AS7-3445 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Rostislav Svoboda Assignee: Emanuel Muckenhuber Fix For: 7.1.0.Final {code} bin/jboss-admin.sh -c command=":read-operation-description(name="read-resource")" ... "include-runtime" => { "type" => BOOLEAN, "description" => "Whether to include runtime attributes (i.e. those whose value does not come from the persistent configuration) in the response. If absent, false is the default. Ignored if the 'recursive' parameter is set to true; i.e. runtime attributes can only be read in non-recursive queries.", ... {code} Remove 'Ignored if the 'recursive' parameter is set to true; i.e. runtime attributes can only be read in non-recursive queries.' Support for recursive queries with runtime details was added in AS7-2033 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1420) DefaultSocketFactory: failed socket creations lead to sockets lingering in hashmap

by Bela Ban (JIRA)

Bela Ban created JGRP-1420: ------------------------------ Summary: DefaultSocketFactory: failed socket creations lead to sockets lingering in hashmap Key: JGRP-1420 URL: https://issues.jboss.org/browse/JGRP-1420 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0.4, 3.1 In TCPConnectionMap.TCPConnection(), the following code is executed: sock=socketFactory.createSocket(); // (1) sock.bind(); // (2) sock.connect(); // (3) In the first step, an unconnected socket is created and added to the 'sockets' hashmap in DefaultSocketFactory. This is used to dump the open sockets in a JGroups program (e.g. via probe.sh socks). However, if step (3) fails, e.g. because the destination is not reachable, the socket should be removed from the 'sockets' hashmap, but isn't ! SOLUTIUON: #1 Check all occurrences of this or similar code and make sure exceptions don't lead to lingering sockets #2 Make the 'sockets' hashmap a weak hashmap, so refs can be GC'ed when memory is low #3 Store string reps of the sockets rather than the sockets themselves -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] (JBADMCON-166) JBoss Admin console allows to add JMS destination with the same name twice without an error

by Tom Ross (JIRA)

Tom Ross created JBADMCON-166: --------------------------------- Summary: JBoss Admin console allows to add JMS destination with the same name twice without an error Key: JBADMCON-166 URL: https://issues.jboss.org/browse/JBADMCON-166 Project: JBoss Admin Console Issue Type: Bug Components: Hibernate Environment: EAP 5.1.2, HornetQ 2.2.10 Reporter: Tom Ross When creating a JMS destination in JBoss Admin console it is possible to create a destination with the same name twice. In each case the console reports "Successfully added new JMS Queue." -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2933) Regression: WebMetaDataParser gives error on war with no version info in web.xml

by Kabir Khan (Created) (JIRA)

Regression: WebMetaDataParser gives error on war with no version info in web.xml -------------------------------------------------------------------------------- Key: AS7-2933 URL: https://issues.jboss.org/browse/AS7-2933 Project: Application Server 7 Issue Type: Bug Reporter: Kabir Khan Assignee: Jean-Frederic Clere Fix For: 7.1.0.CR1 To play with the deployment subsystem I normally deploy http://gwt-examples.googlecode.com/files/Calendar.war, which has no version info in its web.xml: {code} $unzip -p ~/temp/Calendar.war WEB-INF/web.xml <?xml version="1.0" encoding="ISO-8859-1"?> <web-app> <display-name>gwt-Calendar Compiled: Sun Jan 27 06:17:26 GMT 2008</display-name> <description>Google Web Toolkit Project</description> </web-app> {code} After https://github.com/jbossas/jboss-as/commit/977c1dd3c1717f53d96ae7dce32154... I see this error when deploying that war 16:35:07,788 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "Calendar.war" 16:35:08,023 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."Calendar.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."Calendar.war".PARSE: Failed to process phase PARSE of deployment "Calendar.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:680) [:1.6.0_29] Caused by: java.lang.IllegalStateException: Cannot obtain servlet version at org.jboss.metadata.parser.servlet.WebMetaDataParser.parse(WebMetaDataParser.java:103) at org.jboss.metadata.parser.servlet.WebMetaDataParser.parse(WebMetaDataParser.java:54) at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:87) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] ... 5 more A test should be added with a similar web.xml to guard against this in future -- 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, 8 months

6
5
0 / 0

[JBoss JIRA] (AS7-3331) JacORB SSL config parameters should use enumeration instead of values encoded in integers

by David Bosschaert (JIRA)

David Bosschaert created AS7-3331: ------------------------------------- Summary: JacORB SSL config parameters should use enumeration instead of values encoded in integers Key: AS7-3331 URL: https://issues.jboss.org/browse/AS7-3331 Project: Application Server 7 Issue Type: Task Components: IIOP, Server Affects Versions: 7.1.0.CR1b Reporter: David Bosschaert Assignee: Stefan Guilhen The JacORB SSL settings use a fairly cryptic way to express something that would be better represented as a string with 4 allowed values. >From the description: {noformat}client-supports: Value that indicates the client SSL supported parameters (EstablishTrustInTarget=20,EstablishTrustInClient=40,MutualAuth=60). client-requires: Value that indicates the client SSL required parameters (EstablishTrustInTarget=20,EstablishTrustInClient=40,MutualAuth=60). server-supports: Value that indicates the server SSL supported parameters (EstablishTrustInTarget=20,EstablishTrustInClient=40,MutualAuth=60). server-requires: Value that indicates the server SSL required parameters (EstablishTrustInTarget=20,EstablishTrustInClient=40,MutualAuth=60).{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, 8 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012