[JBoss-user] JMS persistence manager for Oracle8
Hi, I just can't get the JBossMQ persistence manager to work with an Oracle8 data source. The tables JMS_TRANSACTIONS and JMS_MESSAGES are successfully created (using BLOB_TYPE=BLOB and the sql statement CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \ DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \ MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) ) from jbossmq-service.xml. When a message should be inserted, it fails throwing this SQL Exception: An exception occured while sending message to the jms queue: org.jboss.mq.SpyJMSException: Could not store message: 4 msg=1 hard NOT_STORED PERSISTENT queue=QUEUE.smsMessageQueue priority=4 hashCode=11632138; - nested throwable: (java.sql.SQLException: invalid column type) I think the problem is related to the oracle BLOB type. Is there a solution for this? Thanks, -marek --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] build jboss-head fail
Hi,Hope someone can help me out.I just checkout jboss-head using WinCvs 1.3.10I was unable to build, as the error shown below :I:\Download\JBoss\jboss-head\buildbuild initCalling ..\tools\bin\ant.bat -logger org.apache.tools.ant.NoBannerLogger initBuildfile: build.xml_buildmagic:init:Trying to override old definition of task property_buildmagic:init:local-properties:[copy] Copying 1 file to I:\Download\JBoss\jboss-head\buildBUILD FAILEDfile:I:/Download/JBoss/jboss-head/build/../tools/etc/buildfragments/tools.ent:35: taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be foundTotal time: 3 secondsPress any key to continue . . .Am I missing something ?Thanks for any help.
AW: [JBoss-user] Strange Classloading behaviour with singletons in JBoss 3.0.6 while using the loader-repository tag
Hi David I don't know the cause of the behavior you are seeing, but I would not depend on it. I would give both .ears loader-repository tags. I think this behaviour arise from the fact that the org.jboss.mx.loading.HeirarchicalLoaderRepository3 asks his parent repository before looking if he could load the class by itself. I'm not sure if this behaviour is desirable, but wouldn't it be better if the HeirarchicalLoaderRepository3 should try to load the class be itself before delegate the call to his parent repository? (If no other application loaded the class before everything works fine but if an other application loaded the class the parent repository returns this class and the class shipped within the ear is never be used.) I think if someone uses the loader-repository tag he or she would expect (as we did) that all classes packaged within the .ear would be used rather than classes loaded by other applications? This could be a tricky problem in a bigger application environment i think. :-) Thanks in advance Kristian On 2003.02.14 10:02 Kristian Köhler wrote: Hi all we've got a question regarding the class-loading behaviour in JBoss-3.0.6. The following simple scenario demonstrates our problem: We've got a util class with a static getInstance method (singleton). We are using this class in a regular application packaged as a EAR containing this class in a JAR. So far so good. As soon as we're deploying a second EAR containing the same class they start to interfere or more precisely calling getInstance() returns the same reference in both EARs. This behaviour is correct according to the JBoss classloading.pdf as far as we can tell. To suppress this behaviour (thereby separating the two EARs) we added a loader-repository tag to one of the jboss-app.xml files. Now comes the part that is puzzling for us, if we do so, the behaviour seems to depend on the order in which the EARs are deployed. If the EAR with the loader-repository tag is deployed first, the two references to the singleton object are different. If the EAR without the loader-repository tag is deployed first, the reference of the singleton object seems to be used in each of the two EARs. Shouldn't it be the case that when a loader-repository tag is supplied the singleton class of the respective EAR should be used rather then using the one of an EAR which has been deployed before without such a tag? Thanks very much in advance Steffen Kristian -- Orientation in Objects GmbH http://www.oio.de --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JMS persistence manager for Oracle8
Is this JBoss 2.4? Anyway, it smells like a problem with your JDBC driver - get the latest Oracle 9.2 JDBC drivers, even if you're backend is Oracle 8. For more information, see the Oracle BLOB FAQ in the JBoss FAQ forum. Steve Coy On Saturday, February 15, 2003, at 10:20 PM, Marek Lange wrote: Hi, I just can't get the JBossMQ persistence manager to work with an Oracle8 data source. The tables JMS_TRANSACTIONS and JMS_MESSAGES are successfully created (using BLOB_TYPE=BLOB and the sql statement CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \ DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \ MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) ) from jbossmq-service.xml. When a message should be inserted, it fails throwing this SQL Exception: An exception occured while sending message to the jms queue: org.jboss.mq.SpyJMSException: Could not store message: 4 msg=1 hard NOT_STORED PERSISTENT queue=QUEUE.smsMessageQueue priority=4 hashCode=11632138; - nested throwable: (java.sql.SQLException: invalid column type) I think the problem is related to the oracle BLOB type. Is there a solution for this? Thanks, -marek --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Strange Classloading behaviour with singletons in JBoss 3.0.6 while using the loader-repository tag
HeirarchicalLoaderRepository is a traditional parent delegation model loader. Its usage only allows one to not pollute the shared class loading space with a deployments' classes. As David said you can achieve the desired affect by having both ears use a scoped loader repository. In general singletons in server envrionments are problematic as they depend entirely on the class loading architecture of the server and this is largely undefined by the specs. I'll add a config flag that allows the HeirarchicalLoaderRepository to change the order of loading to be child first and then the parent ala the servlet 2.3 model. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: Kristian Köhler [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, February 15, 2003 6:11 AM Subject: AW: [JBoss-user] Strange Classloading behaviour with singletons in JBoss 3.0.6 while using the loader-repository tag Hi David I don't know the cause of the behavior you are seeing, but I would not depend on it. I would give both .ears loader-repository tags. I think this behaviour arise from the fact that the org.jboss.mx.loading.HeirarchicalLoaderRepository3 asks his parent repository before looking if he could load the class by itself. I'm not sure if this behaviour is desirable, but wouldn't it be better if the HeirarchicalLoaderRepository3 should try to load the class be itself before delegate the call to his parent repository? (If no other application loaded the class before everything works fine but if an other application loaded the class the parent repository returns this class and the class shipped within the ear is never be used.) I think if someone uses the loader-repository tag he or she would expect (as we did) that all classes packaged within the .ear would be used rather than classes loaded by other applications? This could be a tricky problem in a bigger application environment i think. :-) Thanks in advance Kristian On 2003.02.14 10:02 Kristian Köhler wrote: Hi all we've got a question regarding the class-loading behaviour in JBoss-3.0.6. The following simple scenario demonstrates our problem: We've got a util class with a static getInstance method (singleton). We are using this class in a regular application packaged as a EAR containing this class in a JAR. So far so good. As soon as we're deploying a second EAR containing the same class they start to interfere or more precisely calling getInstance() returns the same reference in both EARs. This behaviour is correct according to the JBoss classloading.pdf as far as we can tell. To suppress this behaviour (thereby separating the two EARs) we added a loader-repository tag to one of the jboss-app.xml files. Now comes the part that is puzzling for us, if we do so, the behaviour seems to depend on the order in which the EARs are deployed. If the EAR with the loader-repository tag is deployed first, the two references to the singleton object are different. If the EAR without the loader-repository tag is deployed first, the reference of the singleton object seems to be used in each of the two EARs. Shouldn't it be the case that when a loader-repository tag is supplied the singleton class of the respective EAR should be used rather then using the one of an EAR which has been deployed before without such a tag? Thanks very much in advance Steffen Kristian -- Orientation in Objects GmbH http://www.oio.de --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf
Re: [JBoss-user] JMS persistence manager for Oracle8
Is this JBoss 2.4? This is JBoss 3.2RC1. Anyway, it smells like a problem with your JDBC driver - get the latest Oracle 9.2 JDBC drivers, even if you're backend is Oracle 8. For more information, see the Oracle BLOB FAQ in the JBoss FAQ forum. Thanks for your tip, Stephen, I tried the 9.2 driver and read your FAQ but the error is still the same. Perhaps there is a problem in the persistence manager with the blob?: at org.jboss.mq.pm.jdbc2.PersistenceManager.setBlob(PersistenceManager.java:770) -marek --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JMS persistence manager for Oracle8
How is your datasource configured to connect to Oracle: oci or thin? I've never stored BLOBs in Oracle - don't believe in it. But I've read on this list repeatedly that using the thin driver to store blobs won't work, you need the oci driver. - Original Message - From: Marek Lange [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, February 15, 2003 6:20 AM Subject: [JBoss-user] JMS persistence manager for Oracle8 Hi, I just can't get the JBossMQ persistence manager to work with an Oracle8 data source. The tables JMS_TRANSACTIONS and JMS_MESSAGES are successfully created (using BLOB_TYPE=BLOB and the sql statement CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \ DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \ MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) ) from jbossmq-service.xml. When a message should be inserted, it fails throwing this SQL Exception: An exception occured while sending message to the jms queue: org.jboss.mq.SpyJMSException: Could not store message: 4 msg=1 hard NOT_STORED PERSISTENT queue=QUEUE.smsMessageQueue priority=4 hashCode=11632138; - nested throwable: (java.sql.SQLException: invalid column type) I think the problem is related to the oracle BLOB type. Is there a solution for this? Thanks, -marek --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] EJB Timer Service
Sorry, don't remember if I replied to this or not. JBoss has had a timer service in it for as long as I've been using it, since 2.2. For 3.2, take a look at server\default\deploy\schedule-manager-service.xml server\default\deploy\scheduler-service.xml for examples of two different implementations available. - Original Message - From: Marek Lange [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, February 13, 2003 5:17 AM Subject: [JBoss-user] EJB Timer Service Hi all, after going through the forums and the archives I am still not sure about this: is it possible to use a timer service in jboss 3.2? If yes, is it possible to define scheduled tasks similar to cronjobs in Unix? So, can I say the ejb should run at 1 am every night? Or, is there a way to implement this fuctionality with the JMX scheduler service? Thanks, marek --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JMS persistence manager for Oracle8
This is JBoss 3.2RC1.
Anyway, it smells like a problem with your JDBC driver - get the
latest Oracle 9.2 JDBC drivers, even if you're backend is Oracle 8.
For more information, see the Oracle BLOB FAQ in the JBoss FAQ forum.
Thanks for your tip, Stephen, I tried the 9.2 driver and read your FAQ
but the error is still the same. Perhaps there is a problem in the
persistence manager with the blob?:
at
org.jboss.mq.pm.jdbc2.PersistenceManager.setBlob(PersistenceManager.java:770)
I found a solution for Oracle: create the table with a BLOB and set the
BLOB_TYPE=BINARYSTREAM_BLOB.
The BLOB_BLOB type seems to be not yet implemented in the 3.2:
else if (blobType == BLOB_BLOB)
{
throw new RuntimeException(BLOB_TYPE: BLOB_BLOB is not yet implemented.);
-marek
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JMS persistence manager for Oracle8
How is your datasource configured to connect to Oracle: oci or thin? I've never stored BLOBs in Oracle - don't believe in it. But I've read on this list repeatedly that using the thin driver to store blobs won't work, you need the oci driver. It's a 9i thin driver. From the Oracle JDBC Drivers release 9.2.0 README: Direct support for LOBs in the Thin driver. The Thin driver now provides direct support for BFILEs, BLOBs, and CLOBs. Anyhow, it seems to work... -marek --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JMS persistence manager for Oracle8
Storing LOBs with the thin driver fails in jboss but the same code runs and the same driver works fine in weblogic and as an stand-alone executable: verified several times on several jbi: 3.02 ... 3.06. Solution is to install oracle client and use OCI as you mentioned. Reason we're storing LOBs in the database (oracle or otherwise) is so we can write from a zipped war without having to set up external path access for each client's documents and images. - Original Message - From: Guy Rouillier [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, February 15, 2003 9:39 AM Subject: Re: [JBoss-user] JMS persistence manager for Oracle8 How is your datasource configured to connect to Oracle: oci or thin? I've never stored BLOBs in Oracle - don't believe in it. But I've read on this list repeatedly that using the thin driver to store blobs won't work, you need the oci driver. - Original Message - From: Marek Lange [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, February 15, 2003 6:20 AM Subject: [JBoss-user] JMS persistence manager for Oracle8 Hi, I just can't get the JBossMQ persistence manager to work with an Oracle8 data source. The tables JMS_TRANSACTIONS and JMS_MESSAGES are successfully created (using BLOB_TYPE=BLOB and the sql statement CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \ DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \ MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) ) from jbossmq-service.xml. When a message should be inserted, it fails throwing this SQL Exception: An exception occured while sending message to the jms queue: org.jboss.mq.SpyJMSException: Could not store message: 4 msg=1 hard NOT_STORED PERSISTENT queue=QUEUE.smsMessageQueue priority=4 hashCode=11632138; - nested throwable: (java.sql.SQLException: invalid column type) I think the problem is related to the oracle BLOB type. Is there a solution for this? Thanks, -marek --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] jboss backup management: howto?
Here are the complete set of docs for you and David to munch on.. Hope this helps out with your needs and an overall solution from David (if the current option(s) don't meet your needs). This also hints to the multipool setup they have for DB failover if you are running hot spares, etc. James --- http://e-docs.bea.com/wls/docs61/jdbc/programming.html : snip/ Test Table Name (Required only if you set Refresh Period, Test Reserved Connections, or Test Released Connections.) The name of a table in the database that is used to test the viability of connections in the connection pool. The query select count(*) from Test Table Name is used to test a connection. The Test Table Name must exist and be accessible to the database user for the connection. Most database servers optimize this SQL to avoid a table scan, but it is still a good idea to set Test Table Name to the name of a table that is known to have few rows, or even no rows. Refresh Period (Optional) This property, together with the Test Table Name property, enables autorefresh of connections in the pools. At a specified interval, each unused connection in the connection pool is tested by executing a simple SQL query on the connection. If the test fails, the connection's resources are dropped and a new connection is created to replace the failed connection. The default value is 1. To enable autorefresh, set Refresh Period to the number of minutes between connection test cycles-a value greater than or equal to 1. If you set an invalid Refresh Period value, the value defaults to 5 minutes. Set Test Table Name to the name of an existing database table to use for the test (required). Test Reserved Connections (Optional) When set to true, the WebLogic Server tests a connection after removing it from the pool and before giving it to the client. The test adds a small delay in serving the client's request for a connection from the pool, but ensures that the client receives a working connection (assuming that the DBMS is available and accessible). The Test Table Name parameter must be set to use this feature. When using a connection pool in a MultiPool with the High Availability algorithm, you must set this attribute to true so that the MultiPool can determine when to fail over to the next connection pool in the list. See MultiPool Fail-Over Limitations and Requirements. Test Released Connections (Optional) When set to true, the WebLogic Server tests a connection before returning it to the connection pool. If all connections in the pool are already in use and a client is waiting for a connection, the client's wait will be slightly longer while the connection is tested. The Test Table Name parameter must be set to use this feature. snip/ --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] build jboss-head fail
just type build -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Henny AumarsSent: Saturday, February 15, 2003 8:19 AMTo: [EMAIL PROTECTED]Subject: [JBoss-user] build jboss-head fail Hi,Hope someone can help me out.I just checkout jboss-head using WinCvs 1.3.10I was unable to build, as the error shown below :I:\Download\JBoss\jboss-head\buildbuild initCalling ..\tools\bin\ant.bat -logger org.apache.tools.ant.NoBannerLogger initBuildfile: build.xml_buildmagic:init:Trying to override old definition of task property_buildmagic:init:local-properties:[copy] Copying 1 file to I:\Download\JBoss\jboss-head\buildBUILD FAILEDfile:I:/Download/JBoss/jboss-head/build/../tools/etc/buildfragments/tools.ent:35: taskdef class xdoclet.modules.jmx.JMXDocletTask cannot be foundTotal time: 3 secondsPress any key to continue . . .Am I missing something ?Thanks for any help.
Re: [JBoss-user] JMS persistence manager for Oracle8
On Sunday, February 16, 2003, at 05:14 AM, Marek Lange wrote: It's a 9i thin driver. From the Oracle JDBC Drivers release 9.2.0 README: Direct support for LOBs in the Thin driver. The Thin driver now provides direct support for BFILEs, BLOBs, and CLOBs. But you have to read between the lines :-) I believe the direct support is through Oracle specific API's. Using pure jdbc api's, the size of the LOB will be limited to 4-5k when using the thin driver. This limitation vanishes when using the oci drivers. Steve Coy --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JMS persistence manager for Oracle8
Sorry, I really should not respond to questions at 2:00AM! If you have just hacked, er, modified the standard jbossmq-service.xml file, then the CREATE_MESSAGE_TABLE string will be wrong for Oracle, and this will yield the invalid column type exception that you are seeing below. There's an example of an Oracle jbossmq-service.xml in CVS (messaging/src/etc/server/examples/deploy/oracle-jbossmq-service.xml) which looks OK to me. Steve Coy On Saturday, February 15, 2003, at 10:20 PM, Marek Lange wrote: Hi, I just can't get the JBossMQ persistence manager to work with an Oracle8 data source. The tables JMS_TRANSACTIONS and JMS_MESSAGES are successfully created (using BLOB_TYPE=BLOB and the sql statement CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, \ DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), \ MESSAGEBLOB BLOB, PRIMARY KEY (MESSAGEID, DESTINATION) ) from jbossmq-service.xml. When a message should be inserted, it fails throwing this SQL Exception: An exception occured while sending message to the jms queue: org.jboss.mq.SpyJMSException: Could not store message: 4 msg=1 hard NOT_STORED PERSISTENT queue=QUEUE.smsMessageQueue priority=4 hashCode=11632138; - nested throwable: (java.sql.SQLException: invalid column type) I think the problem is related to the oracle BLOB type. Is there a solution for this? Thanks, -marek --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
