February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3526) Unable to initialize Vault in domain mode

by Diego Silveira (JIRA)

Diego Silveira created AS7-3526: ----------------------------------- Summary: Unable to initialize Vault in domain mode Key: AS7-3526 URL: https://issues.jboss.org/browse/AS7-3526 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.CR1b Environment: Linux CentOS, JBoss 7.1.0.CR1b Reporter: Diego Silveira Assignee: Brian Stansberry It is possible to encrypt datasource's password when running JBoss in standalone mode. But when trying to run JBoss in domain mode got an exception claiming that "Vault is not initialized". Situation is detailed at https://community.jboss.org/message/649556#649556. -- 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

14 years, 2 months

3
5
0 / 0

[JBoss JIRA] (AS7-2758) Changes host interface to any_address fails to bring up domain

by Heiko Braun (Created) (JIRA)

Changes host interface to any_address fails to bring up domain -------------------------------------------------------------- Key: AS7-2758 URL: https://issues.jboss.org/browse/AS7-2758 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.0.CR1 {noformat} [Server:server-one] 15:26:27,285 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.host.controller.channel: org.jboss.msc.service.StartException in service jboss.host.controller.channel: Failed to start service [Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780) [jboss-msc-1.0.1.GA.jar:] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] [Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] [Server:server-one] at java.lang.Thread.run(Thread.java:680) [:1.6.0_29] [Server:server-one] Caused by: java.lang.IllegalArgumentException: destination address may not be null [Server:server-one] at org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:92) [jboss-remoting-3.2.0.CR3.jar:] [Server:server-one] at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:264) [jboss-remoting-3.2.0.CR3.jar:] [Server:server-one] at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:246) [jboss-remoting-3.2.0.CR3.jar:] [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:353) [jboss-remoting-3.2.0.CR3.jar:] [Server:server-one] at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337) [jboss-remoting-3.2.0.CR3.jar:] [Server:server-one] at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:133) [jboss-as-protocol-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:108) [jboss-as-protocol-7.1.0.CR1-SNAPSHOT.jar:] [Server:server-one] at org.jboss.as.server.mgmt.domain.HostControllerConnectionService.start(HostControllerConnectionService.java:109) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] {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

14 years, 2 months

6
5
0 / 0

[JBoss JIRA] (AS7-3566) Inconsistent managemtn model of the JMX subsystem

by Heiko Braun (JIRA)

Heiko Braun created AS7-3566: -------------------------------- Summary: Inconsistent managemtn model of the JMX subsystem Key: AS7-3566 URL: https://issues.jboss.org/browse/AS7-3566 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.1.Final The description doesn't contain any "connector" children, however the actual model does: {noformat} [domain@192.168.2.126:9999 /] /profile=default/subsystem=jmx:read-resource-description { "outcome" => "success", "result" => { "description" => "The configuration of the JMX subsystem.", "attributes" => {"show-model" => { "type" => BOOLEAN, "description" => "Set to 'true' to include MBeans for the model controller resources", "expressions-allowed" => false, "nillable" => true, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "no-services" }}, "operations" => undefined, "children" => {"remoting-connector" => { "description" => "JBoss remoting connectors for the JMX subsystem.", "model-description" => undefined }} } } {noformat} {noformat} [domain@192.168.2.126:9999 /] /profile=default/subsystem=jmx:read-resource(recursive=true) { "outcome" => "success", "result" => { "connector" => {}, "remoting-connector" => undefined, "show-model" => true } } {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

14 years, 2 months

2
5
0 / 0

[JBoss JIRA] (AS7-3612) Arquillian launches AS 7 with different java than it's own process.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3612: --------------------------------- Summary: Arquillian launches AS 7 with different java than it's own process. Key: AS7-3612 URL: https://issues.jboss.org/browse/AS7-3612 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.0.CR1b Reporter: Ondrej Zizka Assignee: Aslak Knutsen Priority: Critical -- 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

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] (AS7-3597) Cannot remove security domain module

by Heiko Braun (JIRA)

Heiko Braun created AS7-3597: -------------------------------- Summary: Cannot remove security domain module Key: AS7-3597 URL: https://issues.jboss.org/browse/AS7-3597 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.1.Final Trying to clear the list of authentication modules fails: {noformat} {"domain-failure-description" => "JBAS014706: [0] is an invalid size for parameter value. A minimum length of [1] is required"} {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

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] (AS7-3384) Stopping domain.sh process leaving individual process still running

by Galder Zamarreño (JIRA)

Galder Zamarreño created AS7-3384: ------------------------------------- Summary: Stopping domain.sh process leaving individual process still running Key: AS7-3384 URL: https://issues.jboss.org/browse/AS7-3384 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.CR1b Reporter: Galder Zamarreño Fix For: 7.1.0.Final After starting domain.sh via command line (4 nodes), doing Ctrl+C on it leaves java processes hanging around. See thread dumps. -- 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

14 years, 2 months

3
4
0 / 0

[JBoss JIRA] (AS7-3109) Solidify ProcessController and HostController shutdown handling

by Brian Stansberry (Created) (JIRA)

Solidify ProcessController and HostController shutdown handling --------------------------------------------------------------- Key: AS7-3109 URL: https://issues.jboss.org/browse/AS7-3109 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Priority: Critical Fix For: 7.1.0.Final Improve upon the work done for AS7-3093. Properly handle all 5 of these cases 1) reload op on the HC 2) shutdown op on the HC 3) shutdown op on the HC with restart=true param (suggestion: handle this the same as 2) and pass the exit code via the ProcessControllerClient SHUTDOWN message) 4) soft kill of PC 5) Hard kill of PC -- 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

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (AS7-3565) Failed to get file from remote repository error

by Rich Raposa (JIRA)

Rich Raposa created AS7-3565: -------------------------------- Summary: Failed to get file from remote repository error Key: AS7-3565 URL: https://issues.jboss.org/browse/AS7-3565 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.CR1b Environment: Three RHEL5.4 machines: one configured as the DC and no servers; the second machine has one server; third machine has two servers. All servers are in the same Server Group. Reporter: Rich Raposa I am getting this error on a fairly regular basis - it only occurs when I reboot the host machines. The error message is below, and whenever it occurs that particular server does not start, nor can you start it later from the Admin Console. For some reason the host is not able to retrieve the deployed WAR file from the repository on the DC. [Server:prod-server-B] 18:40:41,446 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([("deployment" => "cluster_test.war")]): java.lang.RuntimeException: JBAS015835: Failed to get file from remote repository [Server:prod-server-B] at org.jboss.as.server.mgmt.domain.HostControllerServerClient$RemoteFileRepositoryExecutorImpl.getFile(HostControllerServerClient.java:248) [Server:prod-server-B] at org.jboss.as.server.mgmt.domain.RemoteFileRepository.getFile(RemoteFileRepository.java:102) [Server:prod-server-B] at org.jboss.as.server.mgmt.domain.RemoteFileRepository.getDeploymentFiles(RemoteFileRepository.java:73) [Server:prod-server-B] at org.jboss.as.server.deployment.DeploymentAddHandler$DomainServerDeploymentAddHandler.addFromHash(DeploymentAddHandler.java:222) [Server:prod-server-B] at org.jboss.as.server.deployment.DeploymentAddHandler.execute(DeploymentAddHandler.java:154) [Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:378) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:265) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:193) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.controller.ParallelBootOperationStepHandler.execute(ParallelBootOperationStepHandler.java:161) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:378) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:265) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:193) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:165) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:192) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.server.ServerService.boot(ServerService.java:272) [Server:prod-server-B] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:187) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.server.ServerService.boot(ServerService.java:261) [Server:prod-server-B] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at java.lang.Thread.run(Thread.java:619) [:1.6.0_15] [Server:prod-server-B] Caused by: java.util.concurrent.ExecutionException: Operation failed [Server:prod-server-B] at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] [Server:prod-server-B] at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] [Server:prod-server-B] at org.jboss.as.server.mgmt.domain.HostControllerServerClient$RemoteFileRepositoryExecutorImpl.getFile(HostControllerServerClient.java:246) [Server:prod-server-B] ... 18 more [Server:prod-server-B] Caused by: java.io.IOException: JBAS010985: unrecognized type 36 [Server:prod-server-B] at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:110) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.protocol.mgmt.ManagementChannelReceiver$1.handleMessage(ManagementChannelReceiver.java:57) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleMessage(ManagementChannelReceiver.java:79) [jboss-as-protocol-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] [Server:prod-server-B] at org.jboss.remoting3.remote.RemoteConnectionChannel$5.run(RemoteConnectionChannel.java:409) [jboss-remoting-3.2.0.CR9.jar:3.2.0.CR9] [Server:prod-server-B] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_15] [Server:prod-server-B] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_15] [Server:prod-server-B] ... 1 more [Server:prod-server-B] -- 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

14 years, 2 months

3
3
0 / 0

[JBoss JIRA] (AS7-3543) Remove EndpointRegistryDeploymentAspect

by Richard Opalka (JIRA)

Richard Opalka created AS7-3543: ----------------------------------- Summary: Remove EndpointRegistryDeploymentAspect Key: AS7-3543 URL: https://issues.jboss.org/browse/AS7-3543 Project: Application Server 7 Issue Type: Bug Reporter: Richard Opalka Assignee: Richard Opalka Our EndpointRegistryDeploymentAspect relies on AS7 runtime services that are not available on server shut down. The reason is runtime MSC services EndpointRegistryDeploymentAspect is depending on are stopped before aspect stop() method is being called. --- 10:16:29,835 ERROR [org.jboss.as.server.deployment] JBAS015892: Deployment unit processor org.jboss.as.webservices.deployers.AspectDeploymentProcessor@90acb9b unexpectedly threw an exception during undeploy phase INSTALL of deployment "jaxws-samples-oneway.war": java.lang.IllegalStateException: Endpoint not registered: jboss.ws:context=jaxws-samples-oneway,endpoint=TestService at org.jboss.ws.common.management.DefaultEndpointRegistry.unregister(DefaultEndpointRegistry.java:104) at org.jboss.ws.common.deployment.EndpointRegistryDeploymentAspect.stop(EndpointRegistryDeploymentAspect.java:63) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.undeploy(AspectDeploymentProcessor.java:102) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:167) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:161) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] 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:662) [:1.6.0_29] -- 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

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] (AS7-3551) Rewrite EndpointRecordProcessorDeploymentAspect to don't use MBeanServer

by Richard Opalka (JIRA)

Richard Opalka created AS7-3551: ----------------------------------- Summary: Rewrite EndpointRecordProcessorDeploymentAspect to don't use MBeanServer Key: AS7-3551 URL: https://issues.jboss.org/browse/AS7-3551 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.CR1b, 7.1.0.CR1 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.1.0.Final Our EndpointRecordProcessorDeploymentAspect relies on AS7 runtime services that are not available on server shut down. The reason is runtime MSC services EndpointRecordProcessorDeploymentAspect is depending on are stopped before aspect stop() method is being called. --- 11:49:53,571 ERROR [org.jboss.as.webservices.deployers.EndpointRecordProcessorDeploymentAspect] Cannot unregister record processor with JMX server: javax.management.InstanceNotFoundException: jboss.ws:context=jaxws-samples-oneway,endpoint=TestService,recordProcessor=MemoryBufferRecorder at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094) [:1.6.0_29] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:415) [:1.6.0_29] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:403) [:1.6.0_29] at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:506) [:1.6.0_29] at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.unregisterMBean(PluggableMBeanServerImpl.java:575) at org.jboss.as.jmx.PluggableMBeanServerImpl.unregisterMBean(PluggableMBeanServerImpl.java:328) at org.jboss.ws.common.deployment.EndpointRecordProcessorDeploymentAspect.unregisterRecordProcessor(EndpointRecordProcessorDeploymentAspect.java:119) [jbossws-common.jar:2.0.1-SNAPSHOT] at org.jboss.ws.common.deployment.EndpointRecordProcessorDeploymentAspect.stop(EndpointRecordProcessorDeploymentAspect.java:90) [jbossws-common.jar:2.0.1-SNAPSHOT] at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.undeploy(AspectDeploymentProcessor.java:102) [jboss-as-webservices-server-integration-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:167) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:161) at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1911) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1874) 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:662) [:1.6.0_29] -- 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

14 years, 2 months

1
1
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 February 2012