We rolled back to the old libraries and config files and all is working fine. However, for those following this thread, would like to point out I'm not convinced this is a bug in JBM. We might have made a couple of mistakes during out deployment. Email thread posted for public interest:
anonymous wrote : Just a bit of background. | | We've been running with EAP 4.2 and JBM 1.4.0.GA for a while. I'm quite aware this is not the environment supported by Red Hat, but this is what we have and we've been on a steady path to becoming 100% compliant: We were running JBoss 4.2.1 GA and ActiveMQ, replaced ActiveMQ with JBM and then took on Red Hat support. At this point we upgraded to JBoss EAP 4.2 (but kept JBM in place). I've been working on a branch running JBoss EAP 4.3 and the default configured JBM 1.4.0.SP3, however this is not yet deployed into production. We had a couple of issue with JBM 1.4.0.GA (or really JBoss Remoting I should say) which was sorted out by using a slightly modified version of the remoting-biscoket-service.xml that bundles with JBM 1.4.0.SP3. Please note we were still at this time using the JBM 1.4.0.GA libraries. However, as JBM 1.4.0.SP3 is the stable release, we heeded a suggestion by Red Hat and decided to upgrade. That's when the problem occurred. | | As already mentioned, I'm going to run a couple of experiments today to see whether I can narrow down the reason for the problem. I'm not yet convinced it is a bug in JBM. My reasons are: | | 1. We used the same JBM database schema from 1.4.0.GA. This did not give any problems when we tested in the dev environments. However, after more careful inspection of the SQL in oracle-persistence.sql I noticed a couple of changes were in place (e.g. new index, delete_message sql script switched order of parameters arround ... this could be problem is JBM is not using name parameters, but positional, supports_blob_on_select flag, composite primary key for JBM_MSG_REF changed declaration order for composite columns, etc). I don't know if this could be the cause of our problem and the old schema certainly worked fine for us in the development environment, but I'll try and use the new schema and see whether that makes a difference. | | 2. The following customisations were dropped from connection-factories-service.xml | Setting attribute PrefetchSize to 1000. | Setting attribute SlowConsumers to false. | | 3. Were PostOffice was marked as not clustered before, it was deployed as clustered this time round (default from bundled oracle-persistence-service.xml). Do not anticipate this to be a problem since we are running just a single node. | | 4. Using EAP 4.3 build for JBR 2.2.2.SP4 --- Implementation-Version: 4.3.0.GA (build: VNTag=JBPAPP_4_3_0_GA date=200801031548) instead of the BREW library. I reckoned the EAP 4.3 one would be most stable since tested by Red Hat. However, perhaps there are modifications specific to EAP 4.3. | | PS. Clients were using the following libraries: | JBM: Implementation-Version: 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548). This taken from EAP 4.3\client | JBR: Implementation-Version: 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548). This taken from EAP 4.3\client View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133885#4133885 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133885 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
