Did not get any clue turning trace ON. Also no warnings found. But setting auto commit
to false on connection did the trick. Appears that auto commit set to true causes
separate transaction per statement execution. Since default is true, still at a loss
how it was working in dbcp.
View the
Hello,
Code that worked fine under commns-dbcp is not working under jboss. Essentially
subsequent read after write in same transaction is not seeing the records written.
Oracle's default behavior is to be able to see updates made within same transaction
even though not commited. Not sure why
I recently downloaded the src code for 3.2.3. This is what is happening with my build:
I'm trying to use the PollingNotificationListener which takes int, int as constructor
params. The class loader fails on trying to load sinature type int.
17:05:20,058 ERROR [MBeanServerImpl] Unhandled
Is it possible at all to get JMX notifications to work for clients behind a firewall.
I am almost on the verge of giving up on this. I tried all invokers JRMP, Pooled and
Http. For every one of these I'm able to reach my mbean on the server but
notifications do not come back. I've used the
incidentally changing the jboss-service.xml to pooled invoker in in
jmx-invoker-adapter-server.sar seems to have resolved my hang problem. But
notifications are not coming back. Don't see any exception either.
There's probably more to than just changing it to pooled invoker. I kept the client
Scott,
Thanks for your reply. I have found the problem and it appears to be with our firewall
situation. Well I found that connections initiated from server were being denied since
our clients are behind firewall themselves. Opening up a client box did resolve this
issue.
But this is not an
Hi,
I am hoping someone can give me some pointers to a problem I'm having in production
environment. Everything is fine in the development network. But JMX notifications are
frustratingly slow in production. I have opened up all the ports that JBoss uses and
still have the issue.
I am using
