anonymous wrote : How are the tables being created?
The JMS tables are manually created to match the commands defined in
sybase-jdb2-service.xml from the JBoss examples, and
hsqldb-jdbc-state-service.xml (which I modified to access my Sybase
datasource).
In addition, based on the recommendation
I've configured JMS to use Sybase for persistence. So far, I haven't
seen any problems during extended periods of light to moderate
message load (less than about 100 messages per second). However
once the load increases beyond that, deadlocks start getting thrown.
The most common example is a dea
There's an example JBoss MBean in the Quartz distribution (org.quartz.ee.jmx.jboss).
There's also an example deployment
descriptor.
Here's another example that creates a Quartz service with the name
NTScheduler, using a Sybase datasource.
|
|
|
|
|
| jboss.jca:se
Although I'm not using OJB, I am using JDO and I was having problems similar
to those mentioned in these (and lots of other) posts:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=49041
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=49044
I followed the suggested work-around in
