February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6350) Remove hard-coded paths to AS distribution

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-6350?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-6350 at 2/1/13 8:02 PM: ----------------------------------------------------------- Paul, let me know if you decided to rename the directory afterwards. If not, I'll change Arquillian pom property name to jboss.dist. was (Author: ozizka): Paul, let me know if you decided to rename the directory afterwards. > Remove hard-coded paths to AS distribution > ------------------------------------------ > > Key: AS7-6350 > URL: https://issues.jboss.org/browse/AS7-6350 > Project: Application Server 7 > Issue Type: Enhancement > Components: Build System, Test Suite > Reporter: Paul Gier > Assignee: Ondrej Zizka > Fix For: 7.2.0.Alpha1 > > > There are currently a lot of places in the arquillian and testsuite modules which contain a hard-coded path to the location of the AS distribution (build/target/jbossas). This makes it difficult to change this path when re-branding the AS. > It would be good if these could be configured to use a single POM property such as jboss.home and/or jboss.dist so that the path can be updated in a single place. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6350) Remove hard-coded paths to AS distribution

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-6350?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-6350 at 2/1/13 8:03 PM: ----------------------------------------------------------- Paul, let me know if you decided to rename the directory afterwards. If not, reassign to me and I'll change Arquillian pom property name to jboss.dist. was (Author: ozizka): Paul, let me know if you decided to rename the directory afterwards. If not, I'll change Arquillian pom property name to jboss.dist. > Remove hard-coded paths to AS distribution > ------------------------------------------ > > Key: AS7-6350 > URL: https://issues.jboss.org/browse/AS7-6350 > Project: Application Server 7 > Issue Type: Enhancement > Components: Build System, Test Suite > Reporter: Paul Gier > Assignee: Ondrej Zizka > Fix For: 7.2.0.Alpha1 > > > There are currently a lot of places in the arquillian and testsuite modules which contain a hard-coded path to the location of the AS distribution (build/target/jbossas). This makes it difficult to change this path when re-branding the AS. > It would be good if these could be configured to use a single POM property such as jboss.home and/or jboss.dist so that the path can be updated in a single place. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6350) Remove hard-coded paths to AS distribution

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-6350?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka reassigned AS7-6350: --------------------------------- Assignee: Paul Gier (was: Ondrej Zizka) > Remove hard-coded paths to AS distribution > ------------------------------------------ > > Key: AS7-6350 > URL: https://issues.jboss.org/browse/AS7-6350 > Project: Application Server 7 > Issue Type: Enhancement > Components: Build System, Test Suite > Reporter: Paul Gier > Assignee: Paul Gier > Fix For: 7.2.0.Alpha1 > > > There are currently a lot of places in the arquillian and testsuite modules which contain a hard-coded path to the location of the AS distribution (build/target/jbossas). This makes it difficult to change this path when re-branding the AS. > It would be good if these could be configured to use a single POM property such as jboss.home and/or jboss.dist so that the path can be updated in a single place. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6350) Remove hard-coded paths to AS distribution

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-6350?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-6350: ----------------------------------- Paul, let me know if you decided to rename the directory afterwards. > Remove hard-coded paths to AS distribution > ------------------------------------------ > > Key: AS7-6350 > URL: https://issues.jboss.org/browse/AS7-6350 > Project: Application Server 7 > Issue Type: Enhancement > Components: Build System, Test Suite > Reporter: Paul Gier > Assignee: Ondrej Zizka > Fix For: 7.2.0.Alpha1 > > > There are currently a lot of places in the arquillian and testsuite modules which contain a hard-coded path to the location of the AS distribution (build/target/jbossas). This makes it difficult to change this path when re-branding the AS. > It would be good if these could be configured to use a single POM property such as jboss.home and/or jboss.dist so that the path can be updated in a single place. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6436) ServerSetupTask.tearDown methods should be called in the reverse order

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/AS7-6436?page=com.atlassian.jira.plugin.s... ] Josef Cacek updated AS7-6436: ----------------------------- Git Pull Request: https://github.com/jbossas/jboss-as/pull/3986 > ServerSetupTask.tearDown methods should be called in the reverse order > ---------------------------------------------------------------------- > > Key: AS7-6436 > URL: https://issues.jboss.org/browse/AS7-6436 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Labels: arquillian > > The ServerSetupObserver should call the {{tearDown()}} methods in the reverse order. Otherwise it breaks setup/service dependencies. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ] James Perkins updated AS7-6334: ------------------------------- Description: Task to track the work we've all been doing on expressions/transformers. See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem: 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute. 2) Basic transformation testing against 7.1.2 and 7.1.3 3) Reject-expression testing against 7.1.2 and 7.1.3 Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something. Please edit this description and put an OK after the subsystem name to indicate it's good to go. clustering/jgroups [OK] clustering/infinispan - PR https://github.com/jbossas/jboss-as/pull/3971 cmp [OK] configadmin [OK] connector/datasource connector/jca [OK] connector/resource-adapter deployment-scanner - https://github.com/jbossas/jboss-as/pull/3970 this cannot be used in domain mode and gives an error when initializing the extension. I created a nicer error message. ee - [OK] ejb3 [OK] jacorb - PR https://github.com/jbossas/jboss-as/pull/3974 jaxr [OK] jaxrs [OK] empty subsystem jdr - [OK] empty subsystem jmx [OK] jpa [OK] jsf [OK] jsr77 [OK] empty subsystem logging - PR sent https://github.com/jbossas/jboss-as/pull/3987 mail PR sent https://github.com/jbossas/jboss-as/pull/3979 messaging [OK] modcluster [OK] naming [OK] osgi [OK] pojo [OK] empty subsystem remoting - [OK] sar [OK] empty subsystem security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407] threads [OK] transactions [OK] web [OK] webservices - PR sent https://github.com/jbossas/jboss-as/pull/3979 weld [OK] empty subsystem xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3 was: Task to track the work we've all been doing on expressions/transformers. See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem: 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute. 2) Basic transformation testing against 7.1.2 and 7.1.3 3) Reject-expression testing against 7.1.2 and 7.1.3 Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something. Please edit this description and put an OK after the subsystem name to indicate it's good to go. clustering/jgroups [OK] clustering/infinispan - PR https://github.com/jbossas/jboss-as/pull/3971 cmp [OK] configadmin [OK] connector/datasource connector/jca [OK] connector/resource-adapter deployment-scanner - https://github.com/jbossas/jboss-as/pull/3970 this cannot be used in domain mode and gives an error when initializing the extension. I created a nicer error message. ee - [OK] ejb3 [OK] jacorb - PR https://github.com/jbossas/jboss-as/pull/3974 jaxr [OK] jaxrs [OK] empty subsystem jdr - [OK] empty subsystem jmx [OK] jpa [OK] jsf [OK] jsr77 [OK] empty subsystem logging - PR sent https://github.com/jbossas/jboss-as/pull/3930 mail PR sent https://github.com/jbossas/jboss-as/pull/3979 messaging [OK] modcluster [OK] naming [OK] osgi [OK] pojo [OK] empty subsystem remoting - [OK] sar [OK] empty subsystem security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407] threads [OK] transactions [OK] web [OK] webservices - PR sent https://github.com/jbossas/jboss-as/pull/3979 weld [OK] empty subsystem xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3 > Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems > -------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-6334 > URL: https://issues.jboss.org/browse/AS7-6334 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 7.2.0.Alpha1 > > > Task to track the work we've all been doing on expressions/transformers. > See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem: > 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute. > 2) Basic transformation testing against 7.1.2 and 7.1.3 > 3) Reject-expression testing against 7.1.2 and 7.1.3 > Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something. > Please edit this description and put an OK after the subsystem name to indicate it's good to go. > clustering/jgroups [OK] > clustering/infinispan - PR https://github.com/jbossas/jboss-as/pull/3971 > cmp [OK] > configadmin [OK] > connector/datasource > connector/jca [OK] > connector/resource-adapter > deployment-scanner - https://github.com/jbossas/jboss-as/pull/3970 this cannot be used in domain mode and gives an error when initializing the extension. I created a nicer error message. > ee - [OK] > ejb3 [OK] > jacorb - PR https://github.com/jbossas/jboss-as/pull/3974 > jaxr [OK] > jaxrs [OK] empty subsystem > jdr - [OK] empty subsystem > jmx [OK] > jpa [OK] > jsf [OK] > jsr77 [OK] empty subsystem > logging - PR sent https://github.com/jbossas/jboss-as/pull/3987 > mail PR sent https://github.com/jbossas/jboss-as/pull/3979 > messaging [OK] > modcluster [OK] > naming [OK] > osgi [OK] > pojo [OK] empty subsystem > remoting - [OK] > sar [OK] empty subsystem > security [PR sent - https://github.com/jbossas/jboss-as/pull/3941 - needs more work as mentioned in https://issues.jboss.org/browse/AS7-6407] > threads [OK] > transactions [OK] > web [OK] > webservices - PR sent https://github.com/jbossas/jboss-as/pull/3979 > weld [OK] empty subsystem > xts - [OK] susbystem model has not changed since 7.1.2 & 7.1.3 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-430) DomainController discovery system

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/AS7-430?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated AS7-430: --------------------------- Git Pull Request: https://github.com/jbossas/jboss-as/pull/3982 (was: https://github.com/jbossas/jboss-as/pull/3593) > DomainController discovery system > --------------------------------- > > Key: AS7-430 > URL: https://issues.jboss.org/browse/AS7-430 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Farah Juma > Fix For: 7.3.0.Alpha1 > > > Mechanism(s) by which a Host Controller finds a Domain Controller so it can begin the process of integrating into the domain. > Task includes the host.xml schema elements to configure this, the domain object model classes behind those elements, and the actual implementation of discovery from both the ServerManager and DomainController sides. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6441) Transaction automatically started for MDB even though it uses BMT

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/AS7-6441?page=com.atlassian.jira.plugin.s... ] Justin Bertram updated AS7-6441: -------------------------------- Issue Type: Bug (was: Feature Request) > Transaction automatically started for MDB even though it uses BMT > ----------------------------------------------------------------- > > Key: AS7-6441 > URL: https://issues.jboss.org/browse/AS7-6441 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Justin Bertram > Assignee: jaikiran pai > > When an MDB uses BMT a transaction is still begun when onMessage() is invoked. This is because org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent#isDeliveryTransacted doesn't check whether or not the MDB is using BMT. > You can workaround this issue by using CMT with NOT_SUPPORTED. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6397) Cluster Environment Web Session Locks

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/AS7-6397?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-6397: ------------------------------------------ Hi Manuel If you have the possibility to upgrade and test in a non-production environment, this would be preferable. AS 7.1.3 is a bug fix release (containing fixes to some 400 issues, including the current issue). Your installation would also benefit from those extra fixes; the chances that those additional bugs fixes would raise yet further issues is small, although I can't guarantee that no additional issues would not arise. However, if you don't feel comfortable with that option, I have attached the patch for fix AS7-4260 in the file AS7-4260.patch. You can download AS 7.1.1 from GitHub, apply the patch and then rebuild to create a new AS 7.1.1 binary with the patch included. I have done this, ran the AS 7.1.1 testsuite (including clustering tests) and the testsuite passes. 1. Download AS 7.1.1 sources as a zip file from here: https://github.com/jbossas/jboss-as/tree/7.1.1.Final (just click on the Zip icon to download the zip file) 2. Unzip the zip file, creating a directory jboss-as-7.1.1.Final 3. Apply the attached patch - I use Linux patch and would do the following: cd jboss-as-7.1.1.Final patch -p1 < /tmp/AS7-4260.patch 4. Rebuild AS 7.1.1 cd jboss-as-7.1.1.Final ./build.sh clean install 5. Pick up the modified AS 7.1.1.Final binary which is located at jboss-as-7.1.1.Final/build/target/jboss-as-7.1.1.Final Let me know if you have any issues. > Cluster Environment Web Session Locks > ------------------------------------- > > Key: AS7-6397 > URL: https://issues.jboss.org/browse/AS7-6397 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.1.Final > Environment: Windows 7 64bits, 8 GB RAM > Reporter: Manuel Pinto > Assignee: Paul Ferraro > Attachments: AS7-4260.patch > > > Hi, > I found a problem with web session locks in a cluster environment. We have two Liferay 6.1.1 nodes (over JBoss 7.1.1 Final) in standalone-ha.xml configuration with infinispan "web" cache-container, replicated-cache and file store. The load balancer is configured in non sticky session mode. > Problem: when a node processes requests in some cases locks the session and never unlock it, preventing other node from processing requests for that session. The affected node never regain the locked session and keep throwing the following exception for all subsequent requests and only recover a session when other node shutdown: > Note: we also tried invalidation-cache and distributed-cache and all locking modes but without success. > 17:39:00,174 ERROR [org.apache.catalina.connector.CoyoteAdapter] (http--172.16.250.105-8080-4) An exception or error occurred in the container during the request processing: java.lang.RuntimeException: JBAS018060: Exception acquiring ownership of Cvn-K+r-cBGesIBoDrakJhrO > at org.jboss.as.web.session.ClusteredSession.acquireSessionOwnership(ClusteredSession.java:528) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.web.session.ClusteredSession.access(ClusteredSession.java:496) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.connector.Request.doGetSession(Request.java:2625) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.Request.getSession(Request.java:2375) [jbossweb-7.0.13.Final.jar:] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:81) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [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.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [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_32] > Caused by: org.jboss.as.clustering.lock.TimeoutException: JBAS010223: Cannot acquire lock //default-host//Cvn-K+r-cBGesIBoDrakJhrO 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.1.Final.jar:7.1.1.Final] > ... 12 more > The standalone-ha.xml "web" cache-container config is the following: > <cache-container name="web" aliases="standard-session-cache" default-cache="repl"> > <transport lock-timeout="60000"/> > <replicated-cache name="repl" mode="SYNC" batching="true"> > <file-store/> > </replicated-cache> > <replicated-cache name="sso" mode="SYNC" batching="true"/> > <distributed-cache name="dist" mode="ASYNC" batching="true"> > <file-store/> > </distributed-cache> > </cache-container> > Thanks, > Manuel Pinto -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6397) Cluster Environment Web Session Locks

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/AS7-6397?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz updated AS7-6397: ------------------------------------- Attachment: AS7-4260.patch > Cluster Environment Web Session Locks > ------------------------------------- > > Key: AS7-6397 > URL: https://issues.jboss.org/browse/AS7-6397 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.1.1.Final > Environment: Windows 7 64bits, 8 GB RAM > Reporter: Manuel Pinto > Assignee: Paul Ferraro > Attachments: AS7-4260.patch > > > Hi, > I found a problem with web session locks in a cluster environment. We have two Liferay 6.1.1 nodes (over JBoss 7.1.1 Final) in standalone-ha.xml configuration with infinispan "web" cache-container, replicated-cache and file store. The load balancer is configured in non sticky session mode. > Problem: when a node processes requests in some cases locks the session and never unlock it, preventing other node from processing requests for that session. The affected node never regain the locked session and keep throwing the following exception for all subsequent requests and only recover a session when other node shutdown: > Note: we also tried invalidation-cache and distributed-cache and all locking modes but without success. > 17:39:00,174 ERROR [org.apache.catalina.connector.CoyoteAdapter] (http--172.16.250.105-8080-4) An exception or error occurred in the container during the request processing: java.lang.RuntimeException: JBAS018060: Exception acquiring ownership of Cvn-K+r-cBGesIBoDrakJhrO > at org.jboss.as.web.session.ClusteredSession.acquireSessionOwnership(ClusteredSession.java:528) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.jboss.as.web.session.ClusteredSession.access(ClusteredSession.java:496) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.connector.Request.doGetSession(Request.java:2625) [jbossweb-7.0.13.Final.jar:] > at org.apache.catalina.connector.Request.getSession(Request.java:2375) [jbossweb-7.0.13.Final.jar:] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:81) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [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.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.13.Final.jar:] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [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_32] > Caused by: org.jboss.as.clustering.lock.TimeoutException: JBAS010223: Cannot acquire lock //default-host//Cvn-K+r-cBGesIBoDrakJhrO 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.1.Final.jar:7.1.1.Final] > ... 12 more > The standalone-ha.xml "web" cache-container config is the following: > <cache-container name="web" aliases="standard-session-cache" default-cache="repl"> > <transport lock-timeout="60000"/> > <replicated-cache name="repl" mode="SYNC" batching="true"> > <file-store/> > </replicated-cache> > <replicated-cache name="sso" mode="SYNC" batching="true"/> > <distributed-cache name="dist" mode="ASYNC" batching="true"> > <file-store/> > </distributed-cache> > </cache-container> > Thanks, > Manuel Pinto -- 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, 5 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 February 2013