February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HIBERNATE-132) The license information for hibernate-jpa-2.0-api has no name, only an URL: "license.txt"

by Alix Warnke (JIRA)

[ https://issues.jboss.org/browse/HIBERNATE-132?page=com.atlassian.jira.plu... ] Alix Warnke commented on HIBERNATE-132: --------------------------------------- Hi, can I get a comment about this issue? It is resolved within ten minutes or so :-) Regards A > The license information for hibernate-jpa-2.0-api has no name, only an URL: "license.txt" > ----------------------------------------------------------------------------------------- > > Key: HIBERNATE-132 > URL: https://issues.jboss.org/browse/HIBERNATE-132 > Project: Hibernate Integration > Issue Type: Feature Request > Environment: Maven 3 > Reporter: Alix Warnke > Assignee: Steve Ebersole > Priority: Minor > Labels: license > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Today in the pom-file of hibernate-jpa-2.0-api: > <licenses> -<license> <url>license.txt</url> </license> </licenses> > I would like it to say: > <licenses> -<license> <name>Eclipse Public License, V 1.0</name> <url>license.txt</url> </license> </licenses> > as this would help when using a license plugin to automatically validate against a whitelist of licenses. It is impossible for the maven plugin to know what "license.txt" is. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6432) Incorrect evaluation of system property for expression substitution

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6432?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6432: --------------------------------------- Be sure in your Utils to throw an exception if the operation "outcome" != "success". That may shed more light on why getJBossProperty() isn't producing the expected value. If you could attach test report output that would be great as well. I don't see any setInnerExpression test but that sounds like ${outer:${inner}} or something like that and that's not supported. > Incorrect evaluation of system property for expression substitution > ------------------------------------------------------------------- > > Key: AS7-6432 > URL: https://issues.jboss.org/browse/AS7-6432 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.2.0.Alpha1 > Reporter: Ondřej Chaloupka > Assignee: Brian Stansberry > > Finally I think that I've got a way how to resolve expressions on VM where container resides. > My test case: > https://github.com/ochaloup/jboss-as/blob/expression-substitution-run-in-... > From this I've found issues for system property evaluation. I mean the case when System.getProperty(someName) is called. > The application should get the evaluated value from expression but instead of it it gets the default value from expression. > The problematic test cases are > testSystemPropertyEvaluation - there is defined system property by calling System.setProperty and it's expected that the expression which uses this defined property will evaluate itself to the value of the System.setProperty. For the way of :resolve-expression it works fine but for getting value with System.getProperty the old default value is returned. > setInnerExpression - it defines two levels of evaluation of expression and it seems that then the System.getProperty on the second level of evaluation does not get the evaluated/substituted value > I hope that the test code will be more comprehensible than my explanation. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6168) component upgrade to Hibernate ORM 4.2.0.CR1

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6168?page=com.atlassian.jira.plugin.s... ] Scott Marlow edited comment on AS7-6168 at 1/31/13 7:47 PM: ------------------------------------------------------------ rejected 4.1.9 due to regression in StatefulWithXPCFailoverTestCase (see http://hudson.jboss.org/hudson/job/as7-param-pull/5123/) was (Author: smarlow): rejecting due to regression in StatefulWithXPCFailoverTestCase (see http://hudson.jboss.org/hudson/job/as7-param-pull/5123/) > component upgrade to Hibernate ORM 4.2.0.CR1 > -------------------------------------------- > > Key: AS7-6168 > URL: https://issues.jboss.org/browse/AS7-6168 > Project: Application Server 7 > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Blocker > Fix For: 7.2.0.Alpha1 > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6168) component upgrade to Hibernate ORM 4.2.0.CR1

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6168?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-6168: ----------------------------------- HHH-7928 is fixed in Hibernate ORM 4.2.0.CR1 > component upgrade to Hibernate ORM 4.2.0.CR1 > -------------------------------------------- > > Key: AS7-6168 > URL: https://issues.jboss.org/browse/AS7-6168 > Project: Application Server 7 > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Blocker > Fix For: 7.2.0.Alpha1 > > -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6168) component upgrade to Hibernate ORM 4.2.0.CR1

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6168?page=com.atlassian.jira.plugin.s... ] Scott Marlow updated AS7-6168: ------------------------------ Summary: component upgrade to Hibernate ORM 4.2.0.CR1 (was: component upgrade to a Hibernate ORM build from the 4.1-perf branch) > component upgrade to Hibernate ORM 4.2.0.CR1 > -------------------------------------------- > > Key: AS7-6168 > URL: https://issues.jboss.org/browse/AS7-6168 > Project: Application Server 7 > Issue Type: Component Upgrade > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Blocker > Fix For: 7.2.0.Alpha1 > > -- 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

11 years, 2 months

1
0
0 / 0

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

by Manuel Pinto (JIRA)

[ https://issues.jboss.org/browse/AS7-6397?page=com.atlassian.jira.plugin.s... ] Manuel Pinto commented on AS7-6397: ----------------------------------- Hi Richard, The problem is, the latest Liferay version (6.1.1) executes over the JBoss 7.1.1 and in this phase of project is complicated to change to JBoss 7.1.3, on the other hand we do not know the implications of this change in this version of liferay. How complicated are for you indicate the fixes to resolve that issue in version 7.1.1? Thanks, MPinto > 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 > > 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2013