August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4260) Exception acquiring ownership of X

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4260: ----------------------------------- Summary: Exception acquiring ownership of X Key: AS7-4260 URL: https://issues.jboss.org/browse/AS7-4260 Project: Application Server 7 Issue Type: Bug Reporter: Radoslav Husar {noformat} 13:09:28,290 WARN [org.apache.catalina.session.ManagerBase] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) JBAS018080: Standard expiration of session qLQps+CQJxEi6pJTBSzis0g3 failed; switching to a brute force cleanup. Problem is JBAS018060: Exception acquiring ownership of qLQps+CQJxEi6pJTBSzis0g3 {noformat} {noformat} 12:55:49,556 INFO [org.jboss.as.clustering.impl.CoreGroupCommunicationService.ejb] (Incoming-2,null) JBAS010248: New cluster view for partition ejb: 6 (org.jboss.as.clustering.impl.CoreGroupCommunicationService$GroupView@327579f6 delta: -1, merge: false) 12:55:49,557 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-2,null) ISPN000094: Received new cluster view: [perf21/ejb|6] [perf21/ejb, perf20/ejb, perf18/ejb] 12:56:31,694 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20-10.16.90.58-8009-211) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.RuntimeException: JBAS018060: Exception acquiring ownership of MvwC8KGWTuKPjD1-JjLW7URZ at org.jboss.as.web.session.ClusteredSession.acquireSessionOwnership(ClusteredSession.java:528) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.web.session.ClusteredSession.expire(ClusteredSession.java:1260) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.web.session.ClusteredSession.isValid(ClusteredSession.java:1208) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.web.session.ClusteredSession.isValid(ClusteredSession.java:598) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.web.session.DistributableSessionManager.add(DistributableSessionManager.java:917) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.web.session.DistributableSessionManager.loadSession(DistributableSessionManager.java:1407) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:686) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:85) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.apache.catalina.connector.Request.doGetSession(Request.java:2618) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.Request.getSession(Request.java:2375) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:841) [jbossweb-7.0.13.Final.jar:] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.getSession(LazySessionBeanStore.java:72) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.<init>(LazySessionBeanStore.java:58) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:31) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:16) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.jboss.weld.servlet.WeldListener.requestInitialized(WeldListener.java:134) [weld-core-1.1.5.AS71.Final.jar:2012-02-10 15:31] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.13.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:505) [jbossweb-7.0.13.Final.jar:] at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:445) [jbossweb-7.0.13.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.13.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] Caused by: org.jboss.as.clustering.lock.TimeoutException: JBAS010223: Cannot acquire lock //default-host//clusterbench/MvwC8KGWTuKPjD1-JjLW7URZ from cluster at org.jboss.as.clustering.lock.SharedLocalYieldingClusterLockManager.lock(SharedLocalYieldingClusterLockManager.java:439) at org.jboss.as.clustering.web.infinispan.DistributedCacheManager.acquireSessionOwnership(DistributedCacheManager.java:372) at org.jboss.as.web.session.ClusteredSession.acquireSessionOwnership(ClusteredSession.java:520) [jboss-as-web-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] ... 23 more {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

11 years, 10 months

8
28
0 / 0

[JBoss JIRA] (AS7-5326) Upgrade to JBoss SASL 1.0.2.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-5326: ------------------------------------- Summary: Upgrade to JBoss SASL 1.0.2.Final Key: AS7-5326 URL: https://issues.jboss.org/browse/AS7-5326 Project: Application Server 7 Issue Type: Task Components: Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- 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

11 years, 10 months

1
1
0 / 0

[JBoss JIRA] (SASL-11) From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-11?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-11: --------------------------------- Fix Version/s: 1.0.3.CR1 (was: 1.0.2.Final) > From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect > --------------------------------------------------------------------------------------------------------------------------- > > Key: SASL-11 > URL: https://issues.jboss.org/browse/SASL-11 > Project: JBoss SASL Provider > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.3.CR1 > > > By using space as the separator a single realm name that contains a space is split into two realms. > Either support quoted realm names if they contain a space or choose a different delimiter - (A different delimiter other than a control character may be difficult as the rest can appear in a realm name) -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SASL-10) Pluggable nonce handling strategy

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-10?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated SASL-10: --------------------------------- Fix Version/s: 1.0.3.CR1 (was: 1.0.2.Final) > Pluggable nonce handling strategy > --------------------------------- > > Key: SASL-10 > URL: https://issues.jboss.org/browse/SASL-10 > Project: JBoss SASL Provider > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.3.CR1 > > > Implement a pluggable nonce handling strategy. > At the very least we need to be able to switch to using a SecureRandom instead of Random. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SASL-36) Release 1.0.2.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created SASL-36: ------------------------------------ Summary: Release 1.0.2.Final Key: SASL-36 URL: https://issues.jboss.org/browse/SASL-36 Project: JBoss SASL Provider Issue Type: Task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.2.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

11 years, 10 months

1
1
0 / 0

[JBoss JIRA] (SASL-35) Clean up of temporary files created during authentication process for local mechanism.

by Darran Lofthouse (JIRA)

Darran Lofthouse created SASL-35: ------------------------------------ Summary: Clean up of temporary files created during authentication process for local mechanism. Key: SASL-35 URL: https://issues.jboss.org/browse/SASL-35 Project: JBoss SASL Provider Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.0.1.Final Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.2.CR1 The local mechanism creates a temporary file as part of the verification process, if this is not used then the file is left to be deleted only when the JVM terminates. -- 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

11 years, 10 months

1
2
0 / 0

[JBoss JIRA] (AS7-5325) Can't set attribute "suffix" on web access-log

by Ed Roberts (JIRA)

Ed Roberts created AS7-5325: ------------------------------- Summary: Can't set attribute "suffix" on web access-log Key: AS7-5325 URL: https://issues.jboss.org/browse/AS7-5325 Project: Application Server 7 Issue Type: Enhancement Components: Web Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Environment: N/A Reporter: Ed Roberts Assignee: Remy Maucherat In JBoss 5.x you used to be able to specify a suffix attribute value for the JBossWeb access log file, which would be appended to generated log file names. In JBoss 7.x you can only specify a prefix. For the logging handlers you can specify both a prefix and a suffix, which is inconsistent. Please add the suffix attribute to the access-log element within the parent virtual-server element of the web subsystem xml configuration. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-5310) javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL not honored

by Michael Locher (JIRA)

Michael Locher created AS7-5310: ----------------------------------- Summary: javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL not honored Key: AS7-5310 URL: https://issues.jboss.org/browse/AS7-5310 Project: Application Server 7 Issue Type: Bug Components: JSF Affects Versions: 7.1.2.Final (EAP) Reporter: Michael Locher Assignee: Stan Silvert The javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL params seems not to be working on EAP 6: <context-param> <param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name> <param-value>true</param-value> </context-param> -- 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

11 years, 10 months

2
5
0 / 0

[JBoss JIRA] (AS7-5324) Attribute "allow-multiple-users" not handled for xml datasources

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5324: ------------------------------------- Summary: Attribute "allow-multiple-users" not handled for xml datasources Key: AS7-5324 URL: https://issues.jboss.org/browse/AS7-5324 Project: Application Server 7 Issue Type: Feature Request Components: JCA Affects Versions: 7.1.2.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 XMLDataSourceRuntimeHandler and XMLXaDataSourceRuntimeHandler don't handle attribute "allow-multiple-users". So if you do a read-attribute for that attribute or do a :read-resource(include-runtime=true) the op fails with an ISE. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-5291) JBOSS7 server calls getPrimaryKey() on Home interface business method on second call in same transaction

by Mayank Gupta (JIRA)

Mayank Gupta created AS7-5291: --------------------------------- Summary: JBOSS7 server calls getPrimaryKey() on Home interface business method on second call in same transaction Key: AS7-5291 URL: https://issues.jboss.org/browse/AS7-5291 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Reporter: Mayank Gupta Assignee: jaikiran pai If any ejbHome business method is called more then once in same EJB transaction JBOSS7.1.1 server calls getPrimaryKey() on entity home interface. Following exception is thrown by JBOSS server. (java.lang.String): javax.ejb.EJBTransactionRolledbackException: JBAS014527: Cannot call getPrimaryKey() when state is entity bean home method at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:139) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:204) at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:306) at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) -- 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

11 years, 10 months

2
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2012