Excellent, I deleted the jms configuration, and copied the one in default,
made the necesary changes, and it worked. The problem with PokQueryDs was that
in the AS, the pool was named PokQueryDS (that makes me feel like dumb). Thanks
for all.
View the original post :
Well, in the default config it seems that JMS uses the hypersonic db, and I
read everywhere that this is a bad idea in a production environment (I couldn't
find why), so I changed the DefaultDS to use mysql locally, and then I changed
the DataSourceBinding at mysql-jdbc2-service.xml to use it,
No, using Hypersonic in production is not recommended. It's an in-process DB;
if your app server process crashes, so does your DB. The app server needs a
database, so we bundle Hypersonic so the AS will work out of the box on a
developer's workstation, but it's not meant for production.
For
If you're getting that same Incomplete Deployment listing on more than one
server in the cluster, that tells me you are not using JMS configured to deploy
from the deploy-hasingleton directory, the way it comes in the 'all' config.
If you want clustered JBossMQ, it should be deployed from
Yes, I get the same Incomplete Deployment listing on all servers, except the
first I start, no matter which of all is. I don't want JMS being clustered, I
want it standalone for each server. The DefaultDS uses a local mysql in each
server. I have two more datasources which they point to two
OK, that's fine. Then I assume you are deploying JMS as it's done in the
'default' config. If not, that's what you need to do.
As for the NPE, please post the stack trace.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4024019#4024019
Reply to the post :
