June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4463) Add VisualVm launch scripts to the AS7 distirubution

by John O'Hara (JIRA)

John O'Hara created AS7-4463: -------------------------------- Summary: Add VisualVm launch scripts to the AS7 distirubution Key: AS7-4463 URL: https://issues.jboss.org/browse/AS7-4463 Project: Application Server 7 Issue Type: Feature Request Components: Scripts Affects Versions: 7.1.1.Final Reporter: John O'Hara Assignee: Brian Stansberry Priority: Trivial -- 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, 6 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, 6 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, 6 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, 6 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, 6 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, 6 months

5
6
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, 6 months

2
2
0 / 0

[JBoss JIRA] (AS7-5011) Unable to save network interface configuration

by Stefan Negrea (JIRA)

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] (AS7-4974) Disabling of log handler reset at server boot

by Nicklas Karlsson (JIRA)

Nicklas Karlsson created AS7-4974: ------------------------------------- Summary: Disabling of log handler reset at server boot Key: AS7-4974 URL: https://issues.jboss.org/browse/AS7-4974 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.1.Final Reporter: Nicklas Karlsson Assignee: James Perkins Disabling a log handler is only in effect until the next boot (because there is no attribute for it?). Most other changes are persisted so a user normally would assume it for this operation. -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] (AS7-4942) modcluster configuration does not respect SSL configuration

by yuval konrad (JIRA)

yuval konrad created AS7-4942: --------------------------------- Summary: modcluster configuration does not respect SSL configuration Key: AS7-4942 URL: https://issues.jboss.org/browse/AS7-4942 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.1.Final Environment: jboss AS 7.1.1.Final. HA-Standalone configuration (clustered) with HTTPD modcluster advertise is on Reporter: yuval konrad Assignee: Jason Greene jboss AS 7.1.1.Final. HA-Standalone configuration (clustered) with HTTPD modcluster advertise is on; SSL configuration inside standalone xml are ignored (server is using default values). Setting the following inside httpd.conf file: <IfModule manager_module> Listen *:6666 # ManagerBalancerName myCluster <VirtualHost *:6666> <Location /> Order deny,allow Deny from all Allow from all </Location> SSLEngine ON SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL SSLCertificateKeyFile conf/cert.key SSLCertificateFile conf/cert.cert SSLProtocol all -SSLv2 .. Setting the following in jboss AS: <subsystem xmlns="urn:jboss:domain:modcluster:1.0"> <mod-cluster-config balancer="pnw-cluster" advertise-socket="modcluster" advertise-security-key="blabla"> <dynamic-load-provider history="10" decay="50"> <load-metric type="cpu" weight="2" capacity="2"/> <load-metric type="sessions" weight="1" capacity="1000"/> <load-metric type="heap" weight="3" capacity="1"/> </dynamic-load-provider> <ssl password="17227491" certificate-key-file="configuration/.keystore" ca-certificate-file="configuration/.keystore"/> </mod-cluster-config> </subsystem> Keep getting the following ERRORS on jboss output: 17:51:44,291 ERROR [stderr] (pool-27-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:113) 17:51:44,291 ERROR [stderr] (pool-27-thread-1) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler$Proxy.<init>(DefaultMCMPHandler.java:747) 17:51:44,292 ERROR [stderr] (pool-27-thread-1) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.add(DefaultMCMPHandler.java:183) 17:51:44,293 ERROR [stderr] (pool-27-thread-1) at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.addProxy(DefaultMCMPHandler.java:179) 17:51:44,293 ERROR [stderr] (pool-27-thread-1) at org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl$AdvertiseListenerWorker.run(AdvertiseListenerImpl.java:443) 17:51:44,294 ERROR [stderr] (pool-27-thread-1) at java.lang.Thread.run(Thread.java:662) 17:51:44,294 ERROR [stderr] (pool-27-thread-1) Caused by: java.io.FileNotFoundException: /export/home/ana50/.keystore (No such file or directory) 17:51:44,295 ERROR [stderr] (pool-27-thread-1) at java.io.FileInputStream.open(Native Method) 17:51:44,295 ERROR [stderr] (pool-27-thread-1) at java.io.FileInputStream.<init>(FileInputStream.java:120) 17:51:44,295 ERROR [stderr] (pool-27-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getStore(JSSESocketFactory.java:253) 17:51:44,296 ERROR [stderr] (pool-27-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeystore(JSSESocketFactory.java:208) 17:51:44,296 ERROR [stderr] (pool-27-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:280) 17:51:44,297 ERROR [stderr] (pool-27-thread-1) at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:98) 17:51:44,297 ERROR [stderr] (pool-27-thread-1) ... 5 more I went over all modcluster open and closed bugs without finding any relevant solution. I'm getting these error when using absolute paths as well. -- 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, 6 months

3
3
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 June 2012