We've been using the WebLogic bridge, with some success. The only
recommendation is to use as few of them as possible (i.e. use a limited number
of destinations), because WebLogic seems to fall over when the number of
destinations gets above 30 or so.
View the original post :
I'm having some problems configuring Firebird as the JBoss MQ persistence,
JBoss 3.2.7, using the Firebird RAR. I think it's my connection factory
deployment, and how that gets referenced in the state-service and jdbc2-service
xmls.
My connection factory looks like this:
connection-factories
When I added xa-transaction/ to the connection factory definition it worked.
In the Wiki, it says that JBoss does not need an XA connection for JMS
persistence, so I didn't add it.
Is this (another) limitation of Firebird's JCA adapter?
View the original post :
I communicated with the author of the Firebird JCA adapter, and he indicated
that track-connection-by-tx/ is a required setting for Firebird. Does it
make sense to update the FirebirdDS.xml example in the JBoss distribution?
View the original post :
I'm using JBoss 3.2.7 with an older Firebird JCA adapter (1.5.0 beta3) which
I'm looking to upgrade immediately. The big problem with it is that after it
runs for a while, I get Failure to delist resource exceptions when attempting
to get a connection from the pool. It's an xa connection
I'm trying to test sending a JMS message from one JBoss Server (3.2.7) to
another, while both servers are on the same machine (I used ports-binding.xml
to sort the two instances out). The two servers run exactly the same ear, and
have the same exact JMS destinations.
An EJB is sending the
Still working on this. I was able to upgrade to 3.2.7, but I'm still seeing
the same problem. I think that deploying the xml jars in my ear is wrong, so
I'm trying to pursue why I'm getting the following:
anonymous wrote : 2005-04-27 15:50:09,583 ERROR
[org.jboss.web.localhost.Engine]
Ok, I'm the jerk.
There was a rogue utility jar (one of about 50) in my deployment that had
org.w3c.dom.* in it. I removed those classes from the jar, redeployed the app,
and Voila!
Problem solved.
View the original post :
I followed the instructions on the wiki to use scoped and isolated classloaders
for log4j separation. I am stuck on the following problem, and I can't seem to
get around it...any help would be much appreciated. I'm using JBoss 3.2.3
(have to use this version, unfortunately) on WinXp. My
