Some of my coworkers have reported similar behaviour of a sporadic nature...simple calls to EntityManager.find(Class,id) return null when the object is clearly in the DB. They've also stated that using EntityManager.createQuery("SELECT obj FROM ClassName obj WHERE obj.id=?") will sometimes return the object immediately after the finder fails.
Anyone have an easily deployable use case that reliably fails this query? Having problems believing that something as trivial as a "find by id" method has a bug.
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972657#3972657
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972657
Here's what I ended up doing...
Since CacheLoader.setCache(TreeCache treeCache) interface method sends in the controlling treeCache instance, I use it to add any additional nodes that should be added to the cache as a result of the initial cache miss. ( When I call my external service to get data, it returns additional data nodes to add to the cache.) As long as I am careful to not use the treeCache to add the node for the original get's Fqn, it works ok. ( Doing that would stick me in a recursive loop. )
I was not sure if there was another intended approach such as a callback to the cache loader interceptor directly, for example.
thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972654#3972654
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972654
One solution you might consider is creating a single queue to handle all the traffic of this dynamic type, then using metadata to distinguish one recipient from another. In this way, you configure a single real queue on the server, but have an infinite number of virtual queues.
For extremely high load, this is suboptimal, but for moderate volume should perform with roughly the same characteristics as a dynamic queue solution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972645#3972645
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972645
I know that SLSB should not have class member variables. Can someone verify that the following thinking is correct:
A client obtains an instance of the SLSB.
The client executes a method in the SLSB.
After execution the instance is returned to the pool.
Question:
Can a single instance be obtained by multiple clients at the same time?
We had an RMI factory service which returned a new instance of a class for each user. This new instance had member variables. We switched over to SLSBs, but when it was switched over the member variables were not moved into the methods. There is a call at the begining of every method that initializes these methods. We are planning on moving all of the class members into the method, but in the short term is it safe to assume that only one instance will be executed per user?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3972642#3972642
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3972642