Hi,
I now have multiple jboss instances(not clustered) connecting to one database backend(happens to be oracle in thi s case). Could anyone advise of any "gotcha's" in doing this? It sits rather uncomfortably with me, as I have never used only one db backend before(normally I would use a separate db instance per jboss instance).
Or is this something that is very application specific?
Any pointers to or general advice appreciated...
Sc0tt....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067882#4067882
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067882
Hi,
I have two questions abour Clustering in Jboss 4.2.
1) EJB3.0 Entity Bean Clustering
Do I get it right that there is no other clustering mechanism for entity beans than the Entity Cache? What is best practise, if I want to avoid having a single database server? Would I use replication on DBMS level and have every cluster node use the local database? In such a setup: Has anyone got some experience with mysql NDB clustering?
2) Node Detection
In the documentation I found I only read about cluster node detection in the sense that the local network is scanned for nodes? I have a setup where cluster nodes would be distributed over different networks? Is there a way I can tell the cluster config an explicit list of addresses to check for?
Thanks for your help!
Regards from Munich -
Dennis
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067878#4067878
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067878
The AvailableConnections is actually the number of permits available to enter the pool.
Its not necessarily the same thing as the checked out connections
though it should be pretty similar and only transiently different.
If you can't reproduce the problem (with a test) or give logging then there's little more
I can do.
Even the CachedConnectionManager is not necessarily accurate since it uses a WeakHashMap (to avoid potential memory leaks).
i.e. If you don't close a connection handle and it gets
garbage collected then it will disappear from that information.
You could try changing that class to use a normal HashMap.
The potential memory leak is really bogus since if the connection is not getting removed
from the map you've a more serious connection leak.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067875#4067875
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067875
Well, even without the "." in the username, I get this exception when I try to stack login modules. The authentication happens in one of the earlier modules and the password is SHA encrypted. When I get to the last module, I create the JBoss Portal user (as the user would have been authenticated already before we get this far) and use the JBoss Tools API to MD5 encrypt the password (so the passwords in the 2 repositories are different but that shouldnt matter). I can access the "edit" mode of the dashboard but "view" mode fails with this exception. Any thoughts?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067869#4067869
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067869