September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5208) StatefulFailoverTestCase intermittently fails

by Jason Greene (JIRA)

Jason Greene created AS7-5208: --------------------------------- Summary: StatefulFailoverTestCase intermittently fails Key: AS7-5208 URL: https://issues.jboss.org/browse/AS7-5208 Project: Application Server 7 Issue Type: Bug Reporter: Jason Greene Assignee: Paul Ferraro Fix For: 7.1.3.Final (EAP), 7.2.0.CR1 -- 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, 8 months

4
4
0 / 0

[JBoss JIRA] (AS7-5557) Connection pool config unable to run check-valid-connection-sql only in background thread

by Paul Sideleau (JIRA)

Paul Sideleau created AS7-5557: ---------------------------------- Summary: Connection pool config unable to run check-valid-connection-sql only in background thread Key: AS7-5557 URL: https://issues.jboss.org/browse/AS7-5557 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Environment: SQL Server 2012 JTDS 1.2.5 JBOSS 7 Cluster using domain controller Centos OS virtual Reporter: Paul Sideleau There may be a bug trying to get check-valid-connection-sql to only run in the background thread instead of every-time a connection is checked out from the pool. We have our connection pools configured to do background validation. The validate-on-match is explicitly set to false. Our SQL is simply "SELECT 1". We are using JTDS driver 1.2.5 against SQL Server 2012. We use new relic for performance monitoring and it is showing that the "SELECT 1" is executed every time a connection is checked out from the pool. When we had this configured under JBOSS 6, new relic correctly did not show the "SELECT 1" statement occurring. Here is an example datasource that we place in our domain.xml file: <datasource jta="true" jndi-name="java:jboss/MSSQLDS-DKR" pool-name="jboss/DKR41" enabled="true" use-java-context="true" use-ccm="true"> <connection-url>jdbc:jtds:sqlserver://OUR_DATABASE;sendStringParametersAsUnicode=true;</connection-url> <driver>jtds-1.2.5.jar</driver> <transaction-isolation>TRANSACTION_READ_UNCOMMITTED</transaction-isolation> <pool> <min-pool-size>45</min-pool-size> <max-pool-size>150</max-pool-size> <prefill>false</prefill> <use-strict-min>false</use-strict-min> <flush-strategy>FailingConnectionOnly</flush-strategy> </pool> <security> <user-name>username</user-name> <password>password</password> </security> <validation> <check-valid-connection-sql>SELECT 1</check-valid-connection-sql> <validate-on-match>false</validate-on-match> <background-validation>true</background-validation> <background-validation-millis>60000</background-validation-millis> <use-fast-fail>true</use-fast-fail> </validation> <timeout> <blocking-timeout-millis>5000</blocking-timeout-millis> <idle-timeout-minutes>2</idle-timeout-minutes> <query-timeout>30</query-timeout> </timeout> </datasource> Thank you -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] (AS7-5028) ability to removethe response-header Server:Apache-Coyote/1.1

by nimo stephan (JIRA)

nimo stephan created AS7-5028: --------------------------------- Summary: ability to removethe response-header Server:Apache-Coyote/1.1 Key: AS7-5028 URL: https://issues.jboss.org/browse/AS7-5028 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.1.Final Reporter: nimo stephan Jboss AS 7 includes the following HTTP-Header for every response: Server:Apache-Coyote/1.1 For security issues, it is good to hide this header so attackers cannot easily derivate its underlying technology (which, in this case, indicates that Java-Technology/Tomcat is used). Possible solutions is: Invent a new system-property "org.jboss.as.sendServerHeader" which can be set, for example, in standalone.xml: <system-properties> <property name="org.apache.coyote.http11.Http11Protocol.SERVER" value=""/> <property name="org.jboss.as.sendServerHeader" value="false"/> </system-properties> Note: - leaving the value of "org.apache.coyote.http11.Http11Protocol.SERVER" results in printing the Server-Header also, instead of to go away. However, with that value I can rename the Server-Header, but not deleting it. - At first, I have thought this is a JSF-Rendering-Issue, so I created that issue here http://java.net/jira/browse/JAVASERVERFACES-2445, but it stated out that printing the Server-Header is a "application server level concern". -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] (AS7-4673) Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property

by Roger S (JIRA)

Roger S created AS7-4673: ---------------------------- Summary: Failure to set "SetBigStringTryClob=true" ConnectionProperties in xa-datasource-property Key: AS7-4673 URL: https://issues.jboss.org/browse/AS7-4673 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Environment: Red Hat Enterprise Linux Server release 5.7, JDK 7 Reporter: Roger S I found that when the following is set in the standalone.xml of JBoss-7.1.1.Final, it will have a fatal error: <xa-datasource....> .... <xa-datasource-property name="ConnectionProperties">SetBigStringTryClob=true</xa-datasource-property> .... </xa-datasource> The error is: Caused by: javax.resource.ResourceException: No property editor found for type: class java.util.Properties at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXADataSource(XAManagedConnectionFactory.java:601) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:430) When I don't define the SetBigStringTryClob setting, all is fine. However, the SetBigStringTryClob is really important for the application to work correctly. Hope there's at least a workaround. This worked without problems in JBoss 4.2.3. -- 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, 8 months

2
2
0 / 0

[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, 8 months

2
2
0 / 0

[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, 8 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, 8 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, 8 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, 8 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, 8 months

2
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 September 2012