June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4817) Sessions lost on server shutdown using DIST ASYNC

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4817: ----------------------------------- Summary: Sessions lost on server shutdown using DIST ASYNC Key: AS7-4817 URL: https://issues.jboss.org/browse/AS7-4817 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.3.Final (EAP) Looking at the client, after it gets 500 waits and continues with the same session it, the session is lost. {noformat} ./perf17.log:2012/05/13 17:26:24:788 EDT [DEBUG][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Session assigned: ER8NvbhQixAZmhQIHUDt-Zip ./perf17.log:2012/05/13 17:26:24:788 EDT [DEBUG][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JvmRoute assigned: perf20 ./perf17.log:2012/05/13 17:33:28:943 EDT [WARN ][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: > ./perf17.log:2012/05/13 17:33:28:944 EDT [WARN ][Runner - 106] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Invalid response code: 500 Content: > ./perf17.log:2012/05/13 17:33:32:947 EDT [INFO ][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf20 -> perf21 ./perf17.log:2012/05/13 17:35:41:023 EDT [WARN ][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 138, received 0, Runner: 106> ./perf17.log:2012/05/13 17:35:41:024 EDT [WARN ][Runner - 106] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 138, received 0, Runner: 106> {noformat} No exceptions in the server logs including this session {noformat} ./perf20.log:[JBossINF] 17:26:24,786 INFO [org.jboss.test.clusterbench.common.session.CommonHttpSessionServlet] (ajp-perf20/10.16.90.58:8009-10) New session created: ER8NvbhQixAZmhQIHUDt-Zip.perf20 ./perf17.log:2012/05/13 17:26:24:788 EDT [DEBUG][Runner - 106] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Session assigned: ER8NvbhQixAZmhQIHUDt-Zip {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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] (AS7-4844) Extremely slow response times in Remote EJB invocation on cluster membership change

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4844: ----------------------------------- Summary: Extremely slow response times in Remote EJB invocation on cluster membership change Key: AS7-4844 URL: https://issues.jboss.org/browse/AS7-4844 Project: Application Server 7 Issue Type: Bug Components: Clustering, EJB Affects Versions: 7.1.2.Final (EAP) Reporter: Radoslav Husar Assignee: jaikiran pai Fix For: 7.1.3.Final (EAP) In failover scenarios [1], the response times of remote EJB client are sometimes extremely large. On *graceful* shutdown, response times reach up to one minute [2]. Graceful failover is a positive test, no such exceptions are anticipated. On server crash in a cluster, RTs reach up to nearly 2 minutes [3]. [1] https://docspace.corp.redhat.com/docs/DOC-92019#Failover_Tests [2] http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x... [3] http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x... -- 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-4819) Read timed out on server shutdown and DIST SYNC

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4819: ----------------------------------- Summary: Read timed out on server shutdown and DIST SYNC Key: AS7-4819 URL: https://issues.jboss.org/browse/AS7-4819 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.3.Final (EAP) Some of the clients are getting read timeout when using dist sync and the node is gracefully shut down. This is even more suspicions since the TOs in clustering are probably all set to max 15 seconds but the client timeout is set to 30 seconds. This looks fishy. {noformat} 2012/05/13 17:22:54:388 EDT [WARN ][Runner - 1749] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: IO error: java.net.SocketTimeoutException: Read timed out> {noformat} The exceptions seem to correlate with {noformat} ./perf20.log:[JBossINF] 17:23:11,344 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20/10.16.90.58:8009-109) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.RuntimeException: JBAS018060: Exception acquiring ownership of K5VcZ4gGFzRaLKYMesOQk0zD {noformat} being thrown on the server. -- 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-4923) Fix logging of "Standard expiration of session X failed; switching to a brute force cleanup. Problem is null"

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4923: ----------------------------------- Summary: Fix logging of "Standard expiration of session X failed; switching to a brute force cleanup. Problem is null" Key: AS7-4923 URL: https://issues.jboss.org/browse/AS7-4923 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Radoslav Husar Assignee: Paul Ferraro Fix For: 7.1.3.Final (EAP) I am seeing exception with missing reason {noformat} 19:54:12,862 WARN [org.apache.catalina.session.ManagerBase] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) JBAS018080: Standard expiration of session 7TYWbrkMf6UGi4WUu2Z3VUam failed; switching to a brute force cleanup. Problem is null {noformat} Looks like the actual exception is not well propagated to the message. -- 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-4266) Replication of attribute changed in @PrePassivate method does not work for nested beans

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-4266: ------------------------------------- Summary: Replication of attribute changed in @PrePassivate method does not work for nested beans Key: AS7-4266 URL: https://issues.jboss.org/browse/AS7-4266 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Reporter: Ondřej Chaloupka Assignee: jaikiran pai In case that a sfsb nested bean (a stateful bean which is injected into other bean in this case into a clustered bean) changes its attribute (member variable) in @PrePassivate method then the new state is not replicated to other nodes. You can check my testcase: https://github.com/ochaloup/jboss-as/blob/67f992608bacc2bce95b0d7655083a8... The steps done in tests are following: 1) Search for stateful bean (a "parent" bean for the nested one, bean where the nested one is injected to) 2) Let the stateful bean be passivated (in this time the nested bean is passivated as well, the @PrePassivate method is called) 3) A variable of the nested bean is changed in the @PrePassivate method 4) Do a call on second node - changed state isn't on the other node You can check it in the linked test. When no method on nested been is called (the call is commented now): https://github.com/ochaloup/jboss-as/blob/67f992608bacc2bce95b0d7655083a8... Then the test on the changed attribute fails on the other server: https://github.com/ochaloup/jboss-as/blob/67f992608bacc2bce95b0d7655083a8... -- 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

5
7
0 / 0

[JBoss JIRA] (AS7-4818) Stale session data received when using DIST SYNC on node shutdown

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4818: ----------------------------------- Summary: Stale session data received when using DIST SYNC on node shutdown Key: AS7-4818 URL: https://issues.jboss.org/browse/AS7-4818 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Radoslav Husar Assignee: Paul Ferraro Priority: Critical Fix For: 7.1.3.Final (EAP) There are few occurrences when client received older data even when using DIST SYNC. http://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Failover/job/eap-6x... {noformat} ./perf17.log:2012/05/13 17:11:47:416 EDT [DEBUG][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Session assigned: hAzyrOe0KxA51coCNbSMUsrZ ./perf17.log:2012/05/13 17:11:47:416 EDT [DEBUG][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - JvmRoute assigned: perf18 ./perf17.log:2012/05/13 17:14:11:542 EDT [INFO ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf18 -> perf21 ./perf17.log:2012/05/13 17:14:15:546 EDT [WARN ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 37, received 36, Runner: 968> ./perf17.log:2012/05/13 17:14:15:546 EDT [WARN ][Runner - 968] SFCORE_LOG - Error sampling data: <org.jboss.smartfrog.loaddriver.RequestProcessingException: Stale session data received. Expected 37, received 36, Runner: 968> ./perf17.log:2012/05/13 17:21:20:224 EDT [INFO ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf21 -> perf19 ./perf17.log:2012/05/13 17:23:01:507 EDT [INFO ][Runner - 968] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Failover detected, JvmRoute changed. perf19 -> perf21 {noformat} No logging about the session (hAzyrOe0KxA51coCNbSMUsrZ) in the logs. -- 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] Created: (AS7-1805) Empty directories under "tmp/vfs" keeps on growing between server restarts

by Ramesh Reddy (JIRA)

Empty directories under "tmp/vfs" keeps on growing between server restarts -------------------------------------------------------------------------- Key: AS7-1805 URL: https://issues.jboss.org/browse/AS7-1805 Project: Application Server 7 Issue Type: Bug Components: VFS Affects Versions: 7.0.1.Final Reporter: Ramesh Reddy Assignee: John Bailey When you have active deployment deployed to the server and you are restarting server for various reasons, the tmp/vfs keeps on growing with empty directories. It deletes the contents under the directory but not the directory itself. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
3
0 / 0

[JBoss JIRA] (AS7-4566) Make web connector connectionTimeout configurable

by Takayoshi Kimura (JIRA)

Takayoshi Kimura created AS7-4566: ------------------------------------- Summary: Make web connector connectionTimeout configurable Key: AS7-4566 URL: https://issues.jboss.org/browse/AS7-4566 Project: Application Server 7 Issue Type: Feature Request Components: Web Affects Versions: 7.1.1.Final Reporter: Takayoshi Kimura Assignee: Remy Maucherat The default connectionTimeout (http=60000 and ajp=-1) is not always efficient and some users want to modify them to decrease number of idle connections. -- 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-2217) Console creates (/looks up) instances of bound object

by Carlo de Wolf (Created) (JIRA)

Console creates (/looks up) instances of bound object ----------------------------------------------------- Key: AS7-2217 URL: https://issues.jboss.org/browse/AS7-2217 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.Alpha1 Reporter: Carlo de Wolf Assignee: Heiko Braun When looking at JNDI bindings in Profile -> Container -> Naming instances of the bound object are created. The Console should not perform actual lookups, but just stick to the bindings. -- 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

15
23
0 / 0

[JBoss JIRA] (AS7-4837) JMXPropertyEditorsTestCase fails JDK7

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4837: -------------------------------- Summary: JMXPropertyEditorsTestCase fails JDK7 Key: AS7-4837 URL: https://issues.jboss.org/browse/AS7-4837 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.2.Final (EAP) Environment: Oracle JDK7 Reporter: Tomaz Cerar Assignee: Bartosz Baranowski Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 There are many tests that fail on JDK7 maven report: {noformat} Failed tests: testAtomicBoolean(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'AtomicBoolean' testAtomicInteger(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'AtomicInteger' testAtomicLong(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'AtomicLong' testBigDecimal(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'BigDecimal' testBigInteger(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'BigInteger' testClazz(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'Clazz' testFile(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'File' testLocale(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'Locale' testURI(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'URI' testURL(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'URL' testCharacterArray(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'CharacterArray' testClassArray(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'ClassArray' testInetAddress(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'InetAddress' testInetAddressArray(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'InetAddressArray' testObjectCharacter(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'ObjectChar' testProperties(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Found null attribute value for 'Properties' Tests in error: testChar(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Could not deploy to container: {(..) {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

13 years, 8 months

4
11
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