Hi,
When using JBoss 4.0.5 with Oracle an exception occured while quering a quite
complex object from database. Hibernate constructs a query that is not
compatible with Oracle: ' select from T_COLUMN_TYPE as a14 ..'. It looks
like that an other than Oracle9Dialect is taken somewhere.
Hallo,
due to some compatibility issues with some other running JBoss systems, we have
to use JBoss Version 4.0.2.
JBoss 4.0.2 comes with with Jacorb library '2.2.1 (JBoss patch2)'
Because of some fixed bugs in the jacorb.jar, e.g.
http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=652
I am quite sure the Corba-Services are thread safe. They are not the origin of
the Problem.
We made some tests with thousand of messages sent to the message queues from
multiple Clients in parallel. Most of the time all went fine. In let's say 1 of
20 bulk tests the failure situation occurs.
The server.log looked fine. The last debug output from the relevant MDB was a
message of an succesfully processed message. There wasn't any indication that
anything went wrong.
Should I use special settings or log levels in order to get more information
about the status of the MDB?
View the
The MDB takes the messages, parses them and calls a Corba-Services with message
data as argument. It is simliar as an remote procedure call of the
Corba-Service.
The messages transfered via JMS are of type javax.jms.MapMessage. We do not use
a ftp server.
There are 7 similar MDBs and 7
Hi,
after one week of normal operation messages are not read anymore from one
message queue. More and more messages are written into the queue but the MDB
doesn't get triggered in order to process the messages. Other message queues on
the same machine worked fine.
It was necessary to restart
