Weston, is the recent entry in
http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAOracleDatasource
related to this? Still having intermittent connection problems (JBoss 4.0.4.GA
- Oracle RAC), but I don't have the failover/loadbalance options set in my
connection url - would this make a
The default is for loadbalancing and failover to be on, addresslist is old
syntax, just use DESCRIPTION.
Problem Resolved -
Due to Oracle bug 4338578, the public hostname was being returned to clients
instead of the virtualhost name.
This resulted in intermittent ORA-12545 errors.
Thanks
Did you check the logs to determine if the MDB was still active. In extreme
cases, like deadlock on database or huge load due to redelivery, it can freeze
and fallover..?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3989631#3989631
Reply to the post :
I get the following error intermittently (sometimes on startup of JBoss with
the quartz scheduler, sometimes not) and have read all FAQ and Wiki material,
tried all the connection checkers/sql statements in the oracle-xa-ds.xml config
but nothing effects it.
I am using JBoss-4.0.4.GA and
Thanks for clearing that up Brian.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3982036#3982036
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3982036
___
jboss-user mailing list
http://docs.jboss.org/jbossas/jboss4guide/r5/html/cluster.chapt.html#clustering-http-state
I have implemented SSO and http-session state replication as per the above
documentation on JBoss 4.0.4.GA (with Apache/mod_jk). I am using SSO through
Tomcat's j_security and have enabled this in
Working on a similar area, I added the security-domain with short name to
jboss-app.xml (under META-INF) and the annotations for RolesAllowed in my
Stateless Session beans started working, when previous access exceptions
weren't triggered.
View the original post :
Is there any functional difference between putting the annotations in one
place vs another?
Yes, Eclipse will usually pick up on the error.
Don't know about fields themselves, but getters and setters depends on whether
or not you need to set TransactionAttributes.
View the original post :
I got the same exception, and yes its simply due to closing your client
connection before the reply of acknowledgement is sent (can be 5 seconds even
on local machine for small message).
Either keep connection open or set a timer to keep it open long enough if the
exception annoys you.
