[JBoss JIRA] Created: (JBSEAM-4760) PassivatedEntity class only passivates entities belonging to first entity manager
by Peter Brewer (JIRA)
PassivatedEntity class only passivates entities belonging to first entity manager
---------------------------------------------------------------------------------
Key: JBSEAM-4760
URL: https://issues.jboss.org/browse/JBSEAM-4760
Project: Seam
Issue Type: Bug
Components: Performance and Scalability
Affects Versions: 2.2.1.CR2
Environment: Seam 2.2.1.CR2, JBoss 5.1.0.GA, Windows 7, Java 1.6.0_22 (64-bit)
Reporter: Peter Brewer
This bug only applies when all of the following apply:
1. You have more than one entity manager e.g. "myEntityManager1" and "myEntityManager2"
2. You have enabled the MEI via the distributable="true" attribute on the init component in components xml
When performing fail-over from one node to another, the PassivatedEntity class should re-attached the the entity instance by cycling through each entity manager.
Extract from PassivatedEntity.java
158: for ( String persistenceContextName: PersistenceContexts.instance().getTouchedContexts() )
159: {
160: Object persistenceContext = Component.getInstance(persistenceContextName);
161: return createPassivatedEntity(value, entityClass, persistenceContextName, persistenceContext);
162: }
However, this loop only examines the first touched PersistenceContext and ignores all others. I have submitted a patch that changes this to:
158: for ( String persistenceContextName: PersistenceContexts.instance().getTouchedContexts() )
159: {
160: Object persistenceContext = Component.getInstance(persistenceContextName);
161: PassivatedEntity passivatedEntity = createPassivatedEntity(value, entityClass, persistenceContextName, persistenceContext);
162: if (passivatedEntity != null) {
163: return passivatedEntity ;
164: }
165: }
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Resolved: (SEAMWICKET-3) Deployment issues with numberguess example
by Dan Allen (JIRA)
[ https://issues.jboss.org/browse/SEAMWICKET-3?page=com.atlassian.jira.plug... ]
Dan Allen resolved SEAMWICKET-3.
--------------------------------
Fix Version/s: (was: 3.0.0.CR1)
Resolution: Out of Date
> Deployment issues with numberguess example
> ------------------------------------------
>
> Key: SEAMWICKET-3
> URL: https://issues.jboss.org/browse/SEAMWICKET-3
> Project: Seam Wicket
> Issue Type: Bug
> Environment: Using 'ant tomcat.deploy' with apache-tomcat-6.20
> Reporter: Christian Bauer
> Assignee: Clint Popetz
> Priority: Minor
>
> The CR1 release has the following issues with /examples/wicket/numberguess:
> 1. There is an empty org/jboss/webbeans/examples/ directory in the src/ folder.
> 2. slf4j is completely missing in the WAR, neither API nor implementation is deployed.
> 3. The main Weld JARs are also missing, only weld-wicket.jar is being deployed.
> 4. After copying slf4j, log4j, and weld-servlet.jar, I get this exception on startup:
> Oct 19, 2009 4:17:20 PM org.apache.catalina.core.StandardContext filterStart
> SEVERE: Exception starting filter wicket.numberguess-example
> org.apache.wicket.WicketRuntimeException: There is no application attached to current thread main
> at org.apache.wicket.Application.get(Application.java:179)
> at org.jboss.weld.wicket.BeanManagerLookup.getBeanManager(BeanManagerLookup.java:76)
> at org.jboss.weld.wicket.WeldApplication.<init>(WeldApplication.java:39)
> at org.jboss.weld.examples.wicket.SampleApplication.<init>(SampleApplication.java:5)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at java.lang.Class.newInstance0(Class.java:355)
> at java.lang.Class.newInstance(Class.java:308)
> at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:72)
> at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(ContextParamWebApplicationFactory.java:49)
> at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:678)
> at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
> at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
> at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:108)
> at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3800)
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:4450)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
> at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:987)
> at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:909)
> at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:495)
> at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206)
> at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
> at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
> at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
> at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
> at org.apache.catalina.core.StandardService.start(StandardService.java:516)
> at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
> (Which is btw the same I get in my own weld-wicket test app after upgrading from webbeans 10-day-old-SVN trunk.)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBSEAM-4745) EntityQuery.resultList throws a exception when the entity has composite key
by Alessandro Lazarotti (JIRA)
EntityQuery.resultList throws a exception when the entity has composite key
---------------------------------------------------------------------------
Key: JBSEAM-4745
URL: https://issues.jboss.org/browse/JBSEAM-4745
Project: Seam
Issue Type: Bug
Components: Framework
Affects Versions: 2.2.0.GA, 2.2.1.CR1
Environment: Fedora 12, JDK 1.6 sun/oracle, Seam 2.2.1 CR1, MySQL 5
Reporter: Alessandro Lazarotti
Fix For: 2.2.1.Final
Hibernate has a known trouble running queries using "count" when the entity has composite keys, like:
select count(foobar) from Foobar foobar:
- ERROR [JDBCExceptionReporter] Operand should contain 1 column(s)
Seam EntityQuery has a workaround, using count(*) instead of count(alias)(spec way) if you use entityQuery.resultCount.
It's works with Seam 2.0.x but no more in Seam 2.2.x
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBSEAM-4697) SubscriptionRegistry.subscribe can cause thread to freeze
by Mark Torres (JIRA)
SubscriptionRegistry.subscribe can cause thread to freeze
---------------------------------------------------------
Key: JBSEAM-4697
URL: https://jira.jboss.org/browse/JBSEAM-4697
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.2.GA
Environment: ubuntu hardy, j2se 64-bit build 1.6.0_17-b04, jboss 4.2.3
Reporter: Mark Torres
We ran into an issue where we got really high cpu usage on one instance of our application. Upon inspection in yourkit profiler, we found that the following threads we're consuming all the cpu(see stacktraces below).
Upon googling, we saw several posts where concurrent access to hashmap can cause it to enter into an infinite loop.
http://lightbody.net/blog/2005/07/hashmapget_can_cause_an_infini.html
Subscription registry is using a HashMap and HashSet(for user tokens) below the covers, so I think this issue can be fixed by just using ConcurrentHashMap and ConcurrentHashSet respectively.
Thread: ajp-172.17.8.20-8209-2 : priority:5, demon:true, threadId:228, threadState:RUNNABLE, lockName:null
java.util.HashMap.put(HashMap.java:405)
org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121)
org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22)
org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68)
org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111)
org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
Thread: ajp-172.17.8.20-8209-6 : priority:5, demon:true, threadId:279, threadState:RUNNABLE, lockName:null
java.util.HashMap.put(HashMap.java:405)
org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121)
org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22)
org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68)
org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111)
org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:368)
org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495)
Thread: ajp-172.17.8.20-8209-10 : priority:5, demon:true, threadId:5336, threadState:RUNNABLE, lockName:null
java.util.HashMap.put(HashMap.java:405)
org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121)
org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22)
org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68)
org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111)
org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
Thread: ajp-172.17.8.20-8209-18 : priority:5, demon:true, threadId:10515, threadState:RUNNABLE, lockName:null
java.util.HashMap.transfer(HashMap.java:527)
java.util.HashMap.resize(HashMap.java:506)
java.util.HashMap.addEntry(HashMap.java:810)
java.util.HashMap.put(HashMap.java:416)
org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121)
org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22)
org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68)
org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111)
org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
Thread: ajp-172.17.8.20-8209-21 : priority:5, demon:true, threadId:10518, threadState:RUNNABLE, lockName:null
java.util.HashMap.put(HashMap.java:405)
org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121)
org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22)
org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68)
org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111)
org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
Thread: ajp-172.17.8.20-8209-26 : priority:5, demon:true, threadId:10523, threadState:RUNNABLE, lockName:null
java.util.HashMap.put(HashMap.java:405)
org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121)
org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22)
org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68)
org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111)
org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
Thread: ajp-172.17.8.20-8209-29 : priority:5, demon:true, threadId:16450, threadState:RUNNABLE, lockName:null
java.util.HashMap.put(HashMap.java:405)
org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121)
org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22)
org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68)
org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111)
org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
Thread: ajp-172.17.8.20-8209-35 : priority:5, demon:true, threadId:26542, threadState:RUNNABLE, lockName:null
java.util.HashMap.put(HashMap.java:405)
org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121)
org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22)
org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68)
org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111)
org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBSEAM-4649) HibernatePersistenceProvider has issues with Hibernate Search 3.2.0
by Tom Fank (JIRA)
HibernatePersistenceProvider has issues with Hibernate Search 3.2.0
-------------------------------------------------------------------
Key: JBSEAM-4649
URL: https://jira.jboss.org/jira/browse/JBSEAM-4649
Project: Seam
Issue Type: Bug
Components: Core, Search
Affects Versions: 2.2.1.CR1, 2.2.1.CR2
Environment: JBoss AS 6.0.0.M2
Hibernate 3.5.1
Hibernate Search 3.2.0
Seam 2.2.1.CR1
Reporter: Tom Fank
The new proxied persistence provider (introduced in Seam 2.2.1.CR1) needs some rework in order to be compatible with the current release candidate of Hibernate Search...
1)
When org.jboss.seam.persistence.HibernatePersistenceProvider is trying to find out if HSearch is available it expects org.hibernate.search.Version to have some static VERSION field, but current release does not provide it.
2)
The org.jboss.seam.persistence.HibernateSessionInvocationHandler does not seem to respect the org.hibernate.event.EventSource interface of the delegated Hibernate session. But the (legacy) implementation of FullTextSession still relies on it, so invocations of methods like 'getActionQueue()' need to be handled correctly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months