[JBossCache] - Re: Node locking question
by darose
"genman" wrote :
| Although there could easily be an API for handling atomic data clear/put, there is none and will be none for many other similar situations, such as bulk put or bulk remove. So, your best bet is to learn to like transactions.
"genman" wrote : I would say the DummyTransactionManager is suitable for these sorts of things, so I don't see why it's not production ready. Certainly, it would not be suitable for distributed transaction cases or durable transaction processing. And so the DummyTransactionManager really should be renamed. Maybe it should be called the "MemoryTM" or "NonDurableTM" as it does confuse users.
|
| I'll file an issue to clarify this.
OK, I'll use that, then. Thanks much for the clarification and filing the issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040059#4040059
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040059
19 years
[JBoss Seam] - Nested conversation ending problem
by andrew.rw.robinson
I have an AJAX'd (A4J) page that shows a dialog. There is a link that opens that dialog. The action of that link is annotated with @Begin(ifOutcome="success", nested=true)
The "OK" button of the dialog (a4j:commandLink) calls:
@End(ifOutcome="success")
| public String applyChanges()...
There is no navigation for "success", so the view should stay on the same page and the parent conversation should resume. The page that I'm on is in pages.xml:
| <page
| view-id="/pages/jobManagement/jobs.xhtml"
| action="#{jobMgmtJobBean.onLoad}"
| conversation-required="true"
| no-conversation-view-id="/pages/jobManagement/tasks.xhtml" />
|
What is happening is that "Manager.endConversation(boolean)" is called, and that method calls "setLongRunningConversation(false);". After this, the SeamPhaseListener gets to the "Pages.enterPage" method. It finds my page from the pages.xml definition and "Manager.instance().isLongRunningConversation()" returns false. The Manager then redirects to the "no-conversation-view-id".
Why is this happening? What I think should be happening:
| * @End encountered
| * Manager.endConversation called
| * Manager should notice that it is ending a nested conversation and pop the conversation
| * Manager should resume the parent conversation (isLongRunningConversation() should still be true)
| * Pages should then be happy and the view re-rendered
|
Is this a shortcoming or a bug, or is there something I am missing? (FYI, I tried both "beforeRedirect=false" and "beforeRedirect=true", and it didn't make a difference in the behavior of the Manager code.
Thanks for any help.
Environment:
Seam version 1.1.6 GA
Ajax4Jsf 1.1.0
Facelets 1.1.11
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040055#4040055
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040055
19 years
[JBossCache] - Threading Bug in PojoCache?
by vincent.marquez
I have strong reason to suspect a bug in jbossCache which can result in an exception being thrown when multiple threads are dealing with an object. I discovered this when I was adding a pojo to a cached/advised ArrayList, and at the same time in another thread reading data from that pojo.
The exception being thrown:
org.jboss.cache.pojo.PojoCacheException: PojoCacheDelegate.getObjectInternal(): null PojoInstance for fqn: /__JBossInternal__/cachedVars/class JoinPoint_w_clients_4clients/_ID_/a232u-bqwm2c-f0vhanwn-1-f0vhb667-h
at org.jboss.cache.pojo.impl.PojoCacheDelegate.getObjectInternal(PojoCacheDelegate.java:341)
at org.jboss.cache.pojo.impl.PojoCacheDelegate.getObject(PojoCacheDelegate.java:109)
at org.jboss.cache.pojo.impl.PojoCacheImpl.getObject(PojoCacheImpl.java:203)
at org.jboss.cache.pojo.interceptors.dynamic.CacheFieldInterceptor.invoke(CacheFieldInterceptor.java:165)
at JoinPoint_r_user_48.invokeNext(JoinPoint_r_user_48.java)
at JoinPoint_r_user_48.invokeJoinpoint(JoinPoint_r_user_48.java)
at com.deltel.dtaf.core.services.network.test.irc.Client$ClientAdvisor.Client$ClientAdvisor$user_r_$aop(Client$ClientAdvisor.java)
at com.deltel.dtaf.core.services.network.test.irc.Client$ClientInstanceAdvisor.Client$ClientAdvisor$user_r_$aop(Client$ClientInstanceAdvisor.java)
at com.deltel.dtaf.core.services.network.test.irc.Client.user_r_$aop(Client.java)
at com.deltel.dtaf.core.services.network.test.irc.Client.processData(Client.java:111)
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:585)
at com.deltel.event.flex.FlexSignal.com$deltel$event$flex$FlexSignal$invokeMethod$aop(FlexSignal.java:204)
at com.deltel.event.flex.FlexSignal$FlexSignalAdvisor.invokeMethod6497039208490023269(FlexSignal$FlexSignalAdvisor.java)
at com.deltel.event.flex.FlexSignal.invokeMethod(FlexSignal.java)
at com.deltel.dtaf.api.event.EventSignal.syncExecuteMatch(EventSignal.java:51)
at com.deltel.dtaf.core.as.event.manager.EventProcessor.fireEvent(EventProcessor.java:64)
at com.deltel.dtaf.core.as.event.manager.EventProcessor.run(EventProcessor.java:46)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
I've done some research, and the problem seems like it might be caused by the fact that the AdvisedPojoHandler object adds a CachedFieldInterceptor to the pojo, before it actually adds the pojo to the Cache. This is a problem beacause CachedFieldInterceptor tries to pull field information out of the cache for a FieldReadInvocation.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040053#4040053
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040053
19 years
[JBoss Seam] - TestNG @PersistenceContext Error
by pr57001
I'm trying to develop some testNG unit tests, following the model in the booking example. Any of my beans that use @PersistenceContext generate the following error as the tests try to start:
| Caused by: java.lang.IllegalArgumentException: @PersistenceContext may only be used on session bean or message driven bean components: coverageClassFactory
|
I have also noticed that unlike the booking example, the JNDI Name does not show up as the classes are processed:
| 12:56:03,213 INFO [Component] Component: authenticator, scope: STATELESS, type: STATELESS_SESSION_BEAN, class: org.jboss.seam.example.booking.AuthenticatorAction, JNDI: AuthenticatorAction/local
|
In the booking example, in mine I do not have the
| JNDI: AuthenticatorAction/local
|
part.
Does anyone know what might cause this?
Full log
| 16:14:22,019 INFO [Scanner] scanning: /C:/Java/Seam/jboss-seam-1.2.1.GA/jboss-seam-remoting.jar
| 16:14:22,035 INFO [Scanner] scanning: /C:/Java/Seam/jboss-seam-1.2.1.GA/jboss-seam.jar
| 16:14:22,050 INFO [Initialization] Namespace: http://jboss.com/products/seam/security, package: org.jboss.seam.security, prefix: org.jboss.seam.security
| 16:14:22,050 INFO [Initialization] Namespace: http://jboss.com/products/seam/drools, package: org.jboss.seam.drools, prefix: org.jboss.seam.drools
| 16:14:22,050 INFO [Initialization] Namespace: http://jboss.com/products/seam/mail, package: org.jboss.seam.mail, prefix: org.jboss.seam.mail
| 16:14:22,050 INFO [Initialization] Namespace: http://jboss.com/products/seam/web, package: org.jboss.seam.web, prefix: org.jboss.seam.web
| 16:14:22,050 INFO [Initialization] Namespace: http://jboss.com/products/seam/remoting, package: org.jboss.seam.remoting, prefix: org.jboss.seam.remoting
| 16:14:22,050 INFO [Initialization] Namespace: http://jboss.com/products/seam/theme, package: org.jboss.seam.theme, prefix: org.jboss.seam.theme
| 16:14:22,050 INFO [Initialization] Namespace: http://jboss.com/products/seam/core, package: org.jboss.seam.core, prefix: org.jboss.seam.core
| 16:14:22,050 INFO [Initialization] Namespace: http://jboss.com/products/seam/jms, package: org.jboss.seam.jms, prefix: org.jboss.seam.jms
| 16:14:22,050 INFO [Initialization] Namespace: http://jboss.com/products/seam/framework, package: org.jboss.seam.framework, prefix: org.jboss.seam.core.framework
| 16:14:22,066 INFO [Scanner] scanning: C:\Documents and Settings\rpape\My Documents\Java Projects\DAPSettings\build\test
| 16:14:22,082 INFO [Initialization] reading /WEB-INF/components.xml
| 16:14:22,207 INFO [Initialization] reading jar:file:/C:/Java/Seam/jboss-seam-1.2.1.GA/jboss-seam-remoting.jar!/META-INF/components.xml
| 16:14:22,207 INFO [Initialization] reading jar:file:/C:/Java/Seam/jboss-seam-1.2.1.GA/jboss-seam.jar!/META-INF/components.xml
| 16:14:22,238 INFO [Initialization] reading properties from: /seam.properties
| 16:14:22,238 INFO [Initialization] reading properties from: /jndi.properties
| 16:14:22,238 INFO [Initialization] initializing Seam
| 16:14:22,269 INFO [Scanner] scanning: C:\Documents and Settings\rpape\My Documents\Java Projects\DAPSettings\build\test
| 16:14:22,535 INFO [Scanner] scanning: /C:/Java/Seam/jboss-seam-1.2.1.GA/jboss-seam-remoting.jar
| 16:14:22,660 INFO [Scanner] scanning: /C:/Java/Seam/jboss-seam-1.2.1.GA/jboss-seam.jar
| 16:14:23,957 INFO [Initialization] two components with same name, higher precedence wins: org.jboss.seam.persistence.persistenceProvider
| 16:14:23,972 INFO [Initialization] two components with same name, higher precedence wins: org.jboss.seam.security.identity
| 16:14:24,019 INFO [Component] Component: org.jboss.seam.core.init, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.core.Init
| 16:14:24,113 INFO [Initialization] Installing components...
| 16:14:24,144 INFO [Component] Component: Customer, scope: CONVERSATION, type: ENTITY_BEAN, class: com.foo.customer.Customer
| 16:14:24,160 INFO [Component] Component: CustomerDivision, scope: CONVERSATION, type: ENTITY_BEAN, class: com.foo.customer.CustomerDivision
| 16:14:24,160 WARN [Component] Component class should be serializable: catalogBean
| 16:14:24,160 INFO [Component] Component: catalogBean, scope: SESSION, type: JAVA_BEAN, class: com.foo.dap.catalog.DAPCatalogBean
| 16:14:24,222 INFO [Component] Component: coverageClassFactory, scope: EVENT, type: JAVA_BEAN, class: com.foo.dap.settings.labor.CoverageClassFactoryAction
| Failed to invoke @Configuration method org.jboss.seam.mock.SeamTest.init:Could not create Component: coverageClassFactory
| FAILED: init
| java.lang.RuntimeException: Could not create Component: coverageClassFactory
| at org.jboss.seam.init.Initialization.addComponent(Initialization.java:865)
| at org.jboss.seam.init.Initialization.installComponents(Initialization.java:796)
| at org.jboss.seam.init.Initialization.init(Initialization.java:503)
| at org.jboss.seam.mock.SeamTest.init(SeamTest.java:701)
| Caused by: java.lang.IllegalArgumentException: @PersistenceContext may only be used on session bean or message driven bean components: coverageClassFactory
| at org.jboss.seam.Component.initMembers(Component.java:663)
| at org.jboss.seam.Component.<init>(Component.java:253)
| at org.jboss.seam.Component.<init>(Component.java:203)
| at org.jboss.seam.init.Initialization.addComponent(Initialization.java:851)
| ... 25 more
| ... Removed 22 stack frames
| SKIPPED: begin
| SKIPPED: end
| SKIPPED: testSubmit
| SKIPPED: cleanup
|
| ===============================================
| Login
| Tests run: 5, Failures: 1, Skips: 4
| ===============================================
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040051#4040051
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040051
19 years