[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] murray armfield commented on JBMESSAGING-1491: ---------------------------------------------- Please note that I have left clustering on in this configuration file as that's what I came across browsing other dbms config files in the JBoss Messaging source repository. If this is not correct, please feel free to toggle clustering off before importing and/or if another file is required for clustering, please don't hesitate to ask. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] murray armfield commented on JBMESSAGING-1491: ---------------------------------------------- Just in case you can't tell which file is which, the correct one has 'NOT NULL' added to all fields which appear in a primary key. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] Howard Gao commented on JBMESSAGING-1491: ----------------------------------------- Ingres provides three release version download: ver 2.6, ver 2006, ver 9.2. The latest is 9.2, only available on Solaris and Windows. The other two has more options. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] murray armfield updated JBMESSAGING-1491: ----------------------------------------- Attachment: ingres-persistence-service.newrev.xml Hi Folks, I've been testing the JBoss Messaging examples on a standalone and clustered JBoss 4.2.3 application server with JBoss Messaging 1.4.2GA using the file included with this post, ingres-persistence-service.newrev.xml against an ingres 9.2 dbms all on linux 32-bit. The ingres-presistence-service.newrev.xml file has one small change to fix something that is not in the two earlier files I have posted. The change is to remove the 'FOR UPDATE' part on a SELECT query on the JBM_COUNTER table. Please disregard the earlier two files in favour of this one. With this configuration file and using a Ingres 9.2 on linux 32-bit, all examples work fine except for the queue-failover example. This fails for me with an error that I am looking into. Offhand, do any other dbms's have trouble with the queue-failover example? Take care, Murray -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] murray armfield commented on JBMESSAGING-1491: ---------------------------------------------- Hi Howard and folks, I've been running the examples shipped with JBoss-Messaging 1.4.2.GA on the above mentioned setup and have come to the following conclusion. The one example which I have problems with is the queue-failover mentioned above. What I found is that if I run the cluster with a data source jdbc connection with an isolation level of SERIALIZABLE, the queue-failover example works fine - hooray! Any lower level of isolation fails with the same error. The error is around accessing a LOB column more than once. I will continue to play around with this and some LOB settings on Ingres 9.2 If anyone is interested in using Ingres with JBoss 4.2.3.GA and JBoss-messaging-1.4.2.GA, you will need to create the timers table manually as the creation of this table is hard coded in a java class and has sql which is not entirely portable. Personally I use... CREATE TABLE TIMERS( TIMERID VARCHAR(80) NOT NULL, TARGETID VARCHAR(80) NOT NULL, INITIALDATE DATE, TIMERINTERVAL BIGINT, INSTANCEPK LONG VARCHAR, INFO LONG VARCHAR, PRIMARY KEY(TIMERID, TARGETID)); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] murray armfield commented on JBMESSAGING-1491: ---------------------------------------------- Hi Folks, I've finished working on JBoss Messaging and running the test suite against Ingres community edition 9.2 build 134 on linux 32 bit. I've been using the './build.sh report' version of the tests and have been tuning Ingres so that it works correctly and passes all tests. For those that are interested, the settings that should be used/configured in Ingres are: 1/ DBMS->system_locklevel = row 2/ DBMS->connect_limit = 512 3/ DBMS->table_auto_structure = ON 4/ DBMS->qsf_guideline = huge 5/ Locking->per_tx_limit = 2500 It should be noted that any version on Ingres lower than 9.2 will not work correctly due to the enhancements made in 9.2 specifically around (C/B)LOB's. I have also tried using build 140 and 141 on linux 32 bit and 64bit. That release of Ingres has some problems and should not be used. Ingres is currently in our release cycle for the 9.2 enterprise version(as opposed to the community version). Releases come out for all our different platforms one by one. It is my intention to support JBoss Messaging on Ingres 9.2 enterprise edition going forth. I will continue to test running the JBoss Messaging test suite against Ingres 9.2 enterprise editions that are released if I have hardware and community editions, again if I have hardware. I've made a svn diff file for adding ingres support against the JBoss-Messaging-1.4.2.GA code line for people to use/commit etc. It is attached to this jIRA. I'd like to also add a file documenting suggested Ingres settings for use with JBoss Messaging, and I would think that other db's also have recommended settings, but not sure where to put this. Would it be possible to get this patch applied to the 1.4.3 code so it is included in that release? If not, is there anything I need to do to help out in getting Ingres added to the supported database options? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] murray armfield updated JBMESSAGING-1491: ----------------------------------------- Attachment: ingresv2.diff Hi Folks, I've added a good optimisation on the JBM_MSG_REF_TX index definition for use against Ingres RDBMS. It produced noticable improvements in running time of my "./build.sh report" execution and continues to work successfully for those tests. This patch is a collection of all the work I've done. It is against the svn tags/1.4.2.GA source code and superseeds all the other patches/work uploaded. This patch should be the one used when working with Ingres. Take care, Murray -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] murray armfield commented on JBMESSAGING-1491: ---------------------------------------------- THanks, I've been putting in a lot of hours over this at work(gotta love beening able to do open source as your job at work...) I'm certainly interested in also looking at version 2 and testing ingres against that code line too. Is version 2 code in a good position to look at this, or is it a little early before going there? Cheers Howard. Take care, Murray -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] Howard Gao commented on JBMESSAGING-1491: ----------------------------------------- OK, I'll put it in next release (1.4.3.GA) and contact QA for that hudson matter. Thanks. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] murray armfield commented on JBMESSAGING-1491: ---------------------------------------------- Thanks Guys, I'll put together a little readme type file for some basic instructions on configuring Ingres for use with JBoss-Messaging. These settings would actually be the same as the set of setting's I'd recommend for using Ingres with any JBoss component, specifically if it is using blobs as a data type. This file could also include the 'not been QA'd by JBoss' messaging too. If anyone needs any help or I can help out with any of the work getting the test setup going, please feel free to ask. Today also gives us the release of Ingres 9.2 enterprise edition on 32-bit linux. This is the version that JBoss-Messaging should be used with. I've been testing with the community edition up until now and I am testing this release as from today. I will be doing all my future JBoss/jdbc work against this version. Cheers, Murray -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] Howard Gao updated JBMESSAGING-1491: ------------------------------------ Fix Version/s: 1.4.0.SP3.CP08 (was: 1.4.0.SP3.CP07) (was: 1.4.3.GA) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] murray armfield commented on JBMESSAGING-1491: ---------------------------------------------- Hi Folks, Just wanting to touch base on this issue and try and get things moving along. I've chased up a legitimate Ingres enterprise license for the JBoss Messaging project to use for a copy of Ingres for the continuous test centre. Where do we go from here? Is there anything that I need to do or get done? My aim is to be able to offer Ingres as a supported database platform for JBoss Messaging. Take care, Murray -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] Howard Gao updated JBMESSAGING-1491: ------------------------------------ Fix Version/s: 1.4.0.SP3.CP10 1.4.6.GA (was: 1.4.5.GA) (was: 1.4.0.SP3.CP09) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1491?page=com.atlassian.ji... ] Howard Gao updated JBMESSAGING-1491: ------------------------------------ Fix Version/s: 1.4.0.SP3.CP11 (was: 1.4.0.SP3.CP10) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBMESSAGING-1491?page=com.atlassian.jira.pl... ] Howard Gao updated JBMESSAGING-1491: ------------------------------------ Fix Version/s: 1.4.8.GA (was: 1.4.7.GA) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBMESSAGING-1491?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1491: -------------------------------------- Fix Version/s: 1.4.0.SP3.CP13 (was: 1.4.0.SP3.CP12) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBMESSAGING-1491?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1491: -------------------------------------- Fix Version/s: 1.4.8.SP2 (was: 1.4.8.SP1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBMESSAGING-1491?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1491: -------------------------------------- Fix Version/s: 1.4.0.SP3.CP15 (was: 1.4.0.SP3.CP14) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBMESSAGING-1491?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1491: -------------------------------------- Fix Version/s: 1.4.8.SP4 (was: 1.4.8.SP3) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBMESSAGING-1491?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1491: -------------------------------------- Fix Version/s: 1.4.8.SP6 (was: 1.4.8.SP5) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBMESSAGING-1491?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1491: -------------------------------------- Fix Version/s: 1.4.8.SP8 (was: 1.4.8.SP7) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBMESSAGING-1491?page=com.atlassian.jira.... ] Yong Hao Gao updated JBMESSAGING-1491: -------------------------------------- Fix Version/s: 1.4.8.SP10 (was: 1.4.8.SP9) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira