Hi!
Has anyone an idea on that problem?
I also found the following exception and I'm wondering if both belong together
in any way ...
09:39:18,926 INFO [STDOUT] java.util.ConcurrentModificationException
09:39:18,928 INFO [STDOUT] at
java.util.HashMap$HashIterator.nextEntry(HashMap.java:7
Yes, without problems, just need to start both nodes:
12:44:50,211 ERROR [IdentityLock] read lock for
/JSESSION/localhost/ROOT/gcTJP89MyXji07wLwJgkGA** could not be acquired by
Thread[TP-Process
or2,5,jboss] after 15000 ms. Locks: Read lock owners: []
Write lock owner: <192.168.130.63:7850>:2
,
Hi,
I found the following lines in my debug output, I'm wondering if this is a
deadlock? Version is 4.0.3SP1. We have two JBoss nodes (192.168.130.62:7850,
192.168.130.63:7850), this log is from 192.168.130.63:7850.
09:29:07,215 INFO [STDOUT] org.jboss.cache.lock.TimeoutException: read lock
f
Thanks for the info!
I read the thread and I understand now that read-only entity beans do not
participate in a transaction. Therefore commit-option A is required which we
can't use, so again: bad luck!
The things I don't understand: why don't they participate in a transaction? And
why am I told
Oh I forget it's jboss 4.0.1sp1 with default server.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871507#3871507
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871507
Hi!
I'm unsure about the following scenario:
I have a stateless session bean. this session bean calls multiple different
entity beans. every entity bean is deploy twice, once r/o and once r/w.
If the session bean only tries to read from the database it uses the local home
interfaces for the r/o
Hi!
We set up a cluster of 2 JBoss/Tomcat (4.0.1) nodes using both EJB and HTTP
session clustering (replication). Although in most cases the HTTP session
replication works fine (you can access servlets on both nodes with the same
session id :-)) after some time, say 1 minute up to 1 day, the ses
