October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5385) need an init.d script for domain mode

by Shay Matasaro (JIRA)

Shay Matasaro created AS7-5385: ---------------------------------- Summary: need an init.d script for domain mode Key: AS7-5385 URL: https://issues.jboss.org/browse/AS7-5385 Project: Application Server 7 Issue Type: Enhancement Affects Versions: 7.1.2.Final (EAP) Reporter: Shay Matasaro Assignee: Shay Matasaro Priority: Minor There is a script for launching the standalone server as a service but no script for domain mode -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] (JBAS-9498) Server restart with a wrong server group name should fail from CLI

by Adam Kovari (JIRA)

Adam Kovari created JBAS-9498: --------------------------------- Summary: Server restart with a wrong server group name should fail from CLI Key: JBAS-9498 URL: https://issues.jboss.org/browse/JBAS-9498 Project: Application Server 3 4 5 and 6 Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR1 Reporter: Adam Kovari Priority: Minor If I run this command with the wrong server group name: {code}[domain@localhost:9999 /] /server-group=camc-server-group:restart-servers { "outcome" => "success", "result" => undefined, "server-groups" => undefined }{code} I expect an error in this case, not a success. -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] (AS7-4913) Server sends "big interger <val>" for config entries when a reload is needed

by Heiko Rupp (JIRA)

Heiko Rupp created AS7-4913: ------------------------------- Summary: Server sends "big interger <val>" for config entries when a reload is needed Key: AS7-4913 URL: https://issues.jboss.org/browse/AS7-4913 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final (EAP) Reporter: Heiko Rupp Assignee: Brian Stansberry Priority: Critical RHQ sends JSON like this to change e.g. the max-pool-size setting of a data source: {"operation":"composite","steps":[{"operation":"write-attribute","address":[{"subsystem":"datasources"},{"data-source":"ExampleDS"}],"name":"max-pool-size","value":75},{"operation":"write-attribute","address":[{"subsystem":"datasources"},{"data-source":"ExampleDS"}],"name":"use-fast-fail","value":false}],"address":[]} Server returns success. When I directly go to the cli afterwards I see: [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-attribute(name=max-pool-size) { "outcome" => "success", "result" => big integer 75, "response-headers" => {"process-state" => "restart-required"} } Note the "big integer" [standalone@localhost:9999 /] /:reload {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=datasources/data-source=ExampleDS:read-attribute(name=max-pool-size) { "outcome" => "success", "result" => 75 } [standalone@localhost:9999 /] Now the server acts as always. -- 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

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] (AS7-4237) Possible errrors

by Yamamoto Mie (JIRA)

Yamamoto Mie created AS7-4237: --------------------------------- Summary: Possible errrors Key: AS7-4237 URL: https://issues.jboss.org/browse/AS7-4237 Project: Application Server 7 Issue Type: Enhancement Components: Documentation Reporter: Yamamoto Mie Priority: Minor I have a few questions about AS7 and also found possible errors in the doc. Questions: - Null owned session update can you explain when is this message shown? - to multiple create* methods with different return types on home %s when is this message shown? to create* multiple methods?? or multiple create() methods? - EJB component for address %s is in Is this EJB component for address %s is in (state %s)? ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Possible errors - Class %s has more *that* one constructor annotated with @Inject -> more than? - Boolean to determine whether to create create the tables - Boolean to determine whether to create drop the tables - Timeout, in seconds, a deployment is allows to execute before being canceled. The default is 60 seconds. - Filed to lookup: %s - Specifies whether the ejb3 container need only (to?) provide the "LITE" profile of the specification. This value should only be false when using the "everything" distro. - Removes a specific (a) bean instance pool which has a strict upper limit for bean instances -No timed object invoke(d) for %s -- 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

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1133) MSC service in war file is loaded from WEB-INF/classes/META-INF/services instead of META-INF/services

by David Bosschaert (JIRA)

MSC service in war file is loaded from WEB-INF/classes/META-INF/services instead of META-INF/services ----------------------------------------------------------------------------------------------------- Key: AS7-1133 URL: https://issues.jboss.org/browse/AS7-1133 Project: Application Server 7 Issue Type: Bug Components: MSC, Web Affects Versions: 7.0.0.CR1 Reporter: David Bosschaert Priority: Minor When deploying a .war file that contains a META-INF/service/org.jboss.msc.service.ServiceActivator this file is only processed when it's in the WEB-INF/classes/META-INF/services location, where I think it should really be picked up fro /META-INF/services -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] (AS7-5043) Filtering of logging messages works incorrectly

by Oleg Nitz (JIRA)

Oleg Nitz created AS7-5043: ------------------------------ Summary: Filtering of logging messages works incorrectly Key: AS7-5043 URL: https://issues.jboss.org/browse/AS7-5043 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.1.Final Reporter: Oleg Nitz Assignee: James Perkins In standalone.xml I'm trying to filter out wrong error messages: <subsystem xmlns="urn:jboss:domain:logging:1.1"> <console-handler name="CONSOLE"> <filter> <all> <not><match pattern="JBAS014101: Failed to find SFSB instance with session ID"/></not> <not><match pattern="JBAS011806: Channel end notification received, closing channel Channel ID"/></not> </all> </filter> </console-handler> But this doesn't work, and under debugger I see that the configuration got parsed as "filter" => {"all" => {"not" => {"match" => "JBAS011806: Channel end notification received, closing channel Channel ID"}}}, Looks like due to the use of maps for storing the parsing results the first "not" filter got overwritten by the second "not" filter. -- 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

13 years, 9 months

5
6
0 / 0

[JBoss JIRA] (AS7-5749) Reading deployment resource with missing dependencies leads to exception

by Heiko Braun (JIRA)

Heiko Braun created AS7-5749: -------------------------------- Summary: Reading deployment resource with missing dependencies leads to exception Key: AS7-5749 URL: https://issues.jboss.org/browse/AS7-5749 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Reading from a deployment with missing dependencies leads to an IllegalArg exception: {noformat} 10:05:04,971 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("read-attribute") failed - address: ([("deployment" => "jboss-as-login.war")]): java.lang.IllegalArgumentException at org.jboss.dmr.ModelValue.asBoolean(ModelValue.java:66) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] at org.jboss.dmr.ModelNode.asBoolean(ModelNode.java:248) [jboss-dmr-1.1.1.Final.jar:1.1.1.Final] at org.jboss.as.server.deployment.DeploymentStatusHandler.execute(DeploymentStatusHandler.java:50) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:414) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:296) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:216) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:482) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:414) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:296) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:216) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:135) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:111) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) [jboss-as-protocol-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_35] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_35] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_35] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] {noformat} The management layer response isn't helpful in this case: {noformat} [INFO] { [INFO] "outcome" => "failed", [INFO] "rolled-back" => true [INFO] } {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, 9 months

2
1
0 / 0

[JBoss JIRA] (AS7-5080) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]

by Steven xu (JIRA)

Steven xu created AS7-5080: ------------------------------ Summary: JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds] Key: AS7-5080 URL: https://issues.jboss.org/browse/AS7-5080 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Environment: OS: AIX 5.3 App Server: JBoss AS 7.1.1 Final Reporter: Steven xu 1. Write a simply web application test.ear. 2. Placed the test.ear folder under the <JBOSS_HOME>/standalone/deployment directory. 3. Added "auto-deploy-exploded="true"" to the "deployment-scanner" element of standalone.xml Deployement failed when JBoss staring. (Sometimes JBoss start success, sometimes the test.ear deploy failed) Error info: 12:24:21,153 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) Operation ("add") failed - address: ([("deployment" => "test.ear")]) - failure description: "Operation cancelled asynchronously" 12:24:21,161 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment. I have tried increase the timeout in the standalone.xml by setting "deployment-timeout", But the issue still exists. (This issue does not exist on others OS(Redhat, Debian...). -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-5663) CLONE - System properties are currently unusable for setting a connector's proxy-name

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5663?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5663: ---------------------------------- Fix Version/s: 7.2.0.CR1 > CLONE - System properties are currently unusable for setting a connector's proxy-name > ------------------------------------------------------------------------------------- > > Key: AS7-5663 > URL: https://issues.jboss.org/browse/AS7-5663 > Project: Application Server 7 > Issue Type: Enhancement > Components: Domain Management, Web > Affects Versions: 7.1.1.Final > Environment: -JBoss Enterprise Application Platform (EAP) 6.0.0 > Reporter: Aaron Ogburn > Assignee: Tomaz Cerar > Fix For: 7.2.0.CR1 > > > A connector's proxy-name cannot be set through system properties currently in the web subsystem: > ==domain.xml== > <subsystem xmlns="urn:jbossomain:web:1.1" default-virtual-server="default-host" instance-id="${jboss.node.name}" > native="false"> > <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" proxy-name="${jboss.proxy.name}"/> > The property is never parsed though and > request.getServerName() just returns ${jboss.node.name}. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5451) Eliminate lock contention in SecurityContextAssociationValve

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5451?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved AS7-5451. ----------------------------------- Assignee: Stuart Douglas (was: Remy Maucherat) Fix Version/s: 7.2.0.Alpha1 7.1.3.Final (EAP) Resolution: Done > Eliminate lock contention in SecurityContextAssociationValve > ------------------------------------------------------------ > > Key: AS7-5451 > URL: https://issues.jboss.org/browse/AS7-5451 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.1.2.Final (EAP) > Reporter: Scott Marlow > Assignee: Stuart Douglas > Fix For: 7.2.0.Alpha1, 7.1.3.Final (EAP) > > > Stuart already submitted a pull request against the 7.1 branch for this issue. I'm creating this tracking jira since Andy mentioned that it is important to fix for EAP 6.0.1. -- 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, 9 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 October 2012