[JBossCache] - JBoss PojoCache 2.0: Bug in CachedListImpl?
by chasta
Hi,
it seems there's a bug in the latest CVS version of PojoCache 2.0, in CachedListImpl (though it looks like it's probably a bug in another place in the code, that affects CachedListImpl). The bug causes any list which is inserted to the PojoCache to only keep its last item (all other items are discarded).
How so?
When attaching a list to the PojoCache, the CollectionClassHandler iterates through it and adds the items from the original list to the List proxy. When an item is added, CacheListImpl inserts the item at an index determined by the current size of the list (which in turn is the number of children of the node). However, the node constantly indicates it has no children - therefore, CachedListImpl.size() constantly returns 0 and all of the items in the list are inserted under '0'. (This is when working in optimistic locking mode).
What do you say? Any idea for a workaround?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992896#3992896
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992896
19 years, 4 months
[Persistence, JBoss/CMP, Hibernate, Database] - TransactionRolledbackException
by dani-cas
Well I dont even know where to start.
I have some session beans and some entity beans (CMP) I am using JBoss 4.0.4 with Oracle 10g, with Java 1.5.
I am getting the exception after the ejbStore. The database issues the Update, or at least thats what the log show, but the update never get executed. The exception is the following:
15:38:36,681 DEBUG [AbogadoBean] Executing SQL: UPDATE ABOGADO SET Especializacion=? WHERE userName=?
| 15:39:27,399 DEBUG [IdleRemover] run: IdleRemover notifying pools, interval: 450000
| 15:39:38,180 ERROR [LogInterceptor] TransactionRolledbackException in method: public abstract void org.invias.interfaces.Central.saveUser(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String) throws java.rmi.RemoteException, causedBy:
| org.jboss.tm.JBossRollbackException: Unable to commit, tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=evildani/22, BranchQual=, localId=22] status=STATUS_NO_TRANSACTION; - nested throwable: (javax.ejb.EJBException: Store failed)
I have posted the full stacktrace (very long) in the following address (I hate log posts):
http://atlantis.uniandes.edu.co/errores_jboss/
I have no idea what is going on, I can create the entity, as well as destroy it, but not update it.
Thanks for all the help, If you need more data (classes, logs, xml) email me at:
dani-cas at uniandes (.) edu (.) co
I will post the solution once I figure it out. (I hate threads without a solution)
Thanks again
Daniel Castro
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992894#3992894
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992894
19 years, 4 months
[Messaging, JMS & JBossMQ] - Modifying threadpool in JMS under 4.0.5 using EJB3 + JEE?
by dbs
'Lo folks. We're implementing our first messaging queue, and we need to enforce a single thread model reading from the queue. We may spin off multiple threads, but there are many times we need to only read one item from the queue, process it, finish and close, then pull the next item.
Best situation for that seems to be to modify the Threadpool for queue, specifying only one thread active at a time. But I can't figure out how to do that the EJB3 JEE way (remember we have no deployment descriptor for this MBean)
Here's our configuration code for the MDB:
@MessageDriven(activationConfig =
| {
| @ActivationConfigProperty(propertyName="destinationType",
| propertyValue="javax.jms.Queue"),
| @ActivationConfigProperty(propertyName="destination",
| propertyValue="queue/jobs")
| })
Any suggestions? The onMessage() in this MDB is triggering fine, but if we pile 5 items into the queue, we end up with 5 simultaneously executing threads. Not what we want.
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992893#3992893
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992893
19 years, 4 months
[JBoss jBPM] - Fork + Join
by nlmarco
Hello *,
I've got a question about Fork+Join behaviour:
When the root token enters the Fork, it creates a new child token for every outgoing transition. That's exactly what I expected according to the docs and my intuition.
When these child tokens enter the Join, however, they don't end there, but continue their way through the rest of the workflow. That means, even though the Join can be understood as the counterpart of the Fork, it doesn't behave that way. In my opinion, every child token should end in the Join by default.
Is there a way to configure a Join this way? I didn't find anything in the Join's source code...
What's the preferred way to do this? End the child tokens in an action? Are there best practices?
Thousand thanks in advance!
Best regards, Marco :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992885#3992885
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992885
19 years, 4 months