[JBoss-dev] more standardjboss-cmp.xml
For postgresql the Boolean mapping is wrong. Should be mapping java-typejava.lang.Boolean/java-type jdbc-typeBIT/jdbc-type sql-typeBOOLEAN/sql-type /mapping ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-501820 ] Inconsistent behavior for non-tx queues
Bugs item #501820, was opened at 2002-01-10 06:40 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=501820group_id=22866 Category: JBossMQ Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Corby (corby) Assigned to: Nobody/Anonymous (nobody) Summary: Inconsistent behavior for non-tx queues Initial Comment: I have observed this problem in JBoss 2.4.4-Catalina, running on Windows 2000. I have an MDB that receives messages from a queue, Q1, for messages. It attempts to process the message, and this processing involves numerous database writes. If something goes wrong with the processing, then I wish to rollback my database updates, and copy the message into a second queue, Q2. I never want to rollback operations on Q1 or Q2. So I declare my database to be a managed resource for my MDB, but I do not declare Q1 or Q2 to be managed resources. And I use a non-XA connection factory to retrieve my queue connections. When my MDB uses bean-managed transactions, it behaves exactly as I expect. That is, committing or rolling back the transaction will determine whether or not writes occur to the database, but it has no effect on whether a message is pulled out of Q1 or sent into Q2. But when my MDB uses container-managed transactions, the behavior is inconsistent. Committing the transaction causes it to behave as expected. But if I call setRollbackOnly() on the MessageDrivenContext, it rolls back the datasource AND Q1, but not Q2. (Of course, this causes the message to infinitely redeliver, process with error, and successfully forward on to Q2). I think this is a bug, and that the bean should not rollback Q1 when it is CMT, just like it doesn't when it is BMT. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=501820group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-501826 ] Can't Stop the Queues
Bugs item #501826, was opened at 2002-01-10 06:44 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=501826group_id=22866 Category: JBossMQ Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Corby (corby) Assigned to: Nobody/Anonymous (nobody) Summary: Can't Stop the Queues Initial Comment: Queues can not be stopped in JBoss as per the JMS spec. This bug is acknowledged by Hiram in this thread: http://www.jboss.org/forums/thread.jsp? forum=48thread=6341 -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=501826group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: Auto Deployer
Adrian, all this is going away in a couple of hours (as soon as I commit which in my case always is slow). So don't spend cycle fixing this in the current deployer, the problem you raise can be fixed then, just hold on for a couple of hours, I am going as fast as I can... Classloader integration was never trivial, marcf __ View this jboss-dev thread in the online forums: http://jboss.org/forums/thread.jsp?forum=66thread=6902 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-501972 ] Messages can not be resent
Bugs item #501972, was opened at 2002-01-10 11:04 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=501972group_id=22866 Category: JBossMX Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Corby (corby) Assigned to: Juha Lindfors (juhalindfors) Summary: Messages can not be resent Initial Comment: When a message is received from a queue, if it is placed in another queue, acknowledgement of the message will fail. This occurs in JBoss 2.4.4-Catalina on Windows 2000. The following code fragment replicates the problem. mapMessage is a message that was received from a queue. queueConnection = JMSHelper.getQueueConnection( JMSHelper.NONXA_CONNECTION_FACTORY ); queueSession = JMSHelper.getQueueSession( queueConnection ); queueSender = JMSHelper.getQueueSender( queueSession, JMSHelper.FAILED_ALLOCATIONS_QUEUE ); queueConnection.start(); queueSender.send( mapMessage ); With this code, the message is forwarded into the new queue, but acknowledgement fails. When JBoss is restarted, the message will be delivered. Acknowlegement will succeed when I manually copy the message, like so: queueConnection = JMSHelper.getQueueConnection( JMSHelper.NONXA_CONNECTION_FACTORY ); queueSession = JMSHelper.getQueueSession( queueConnection ); queueSender = JMSHelper.getQueueSender( queueSession, JMSHelper.FAILED_ALLOCATIONS_QUEUE ); // NOTE: I am copying this message because of a bug in the current version // of JBossMQ. In future versions, we should be able to forward the message // without copying it. MapMessage sentMessage = JMSHelper.createMapMessage( queueSession ); sentMessage.setString( ACCOUNTING_LOCATION_NUMBER, mapMessage.getString( ACCOUNTING_LOCATION_NUMBER )); sentMessage.setString( DIRECTION_OF_FLOW, mapMessage.getString( DIRECTION_OF_FLOW )); sentMessage.setLong( BEGIN_PRODUCTION_TIME, mapMessage.getLong( BEGIN_PRODUCTION_TIME )); sentMessage.setLong( END_PRODUCTION_TIME, mapMessage.getLong( END_PRODUCTION_TIME )); queueConnection.start(); queueSender.send( sentMessage ); Peter claimed at the beginning of November that this problem had been fixed in CVS: http://www.jboss.org/forums/thread.jsp? forum=48thread=3789message=254709 However, subsequent build of the system, including the JBoss 2.4.4-Catalina distribution, continue to have this problem. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=501972group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Re: Auto Deployer
This is good news. The more I've dug into this the more problems I've discovered. e.g. ra.xml in the j2eedeployer file list. I've fixed a couple of 'em. I guess that's why it called the rabbit hole. Real Alice in Wonderland for me :-) On a completely unrelated point. Any chance of changing the forums to have FAQ at the top and with lettering twice as big. I'm pretty sure nobody bothers paging up, or using search for that matter :-) Regards, Adrian __ View this jboss-dev thread in the online forums: http://jboss.org/forums/thread.jsp?forum=66thread=6902 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-502025 ] JBoss fail to start
Bugs item #502025, was opened at 2002-01-10 12:37 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=502025group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ronan-Yann Lorin (ryl) Assigned to: Nobody/Anonymous (nobody) Summary: JBoss fail to start Initial Comment: It appears that when an XA/JDBC connection can't be established at startup, the server hang and never starts. I guess this is due to a connection test just atfer binding the name in JNDI. Code looks like that: datasource.getConnection().close(); It seems that the exception is not correctly catched. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=502025group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-502025 ] JBoss fail to start
Bugs item #502025, was opened at 2002-01-10 12:37 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=502025group_id=22866 Category: JBossServer Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ronan-Yann Lorin (ryl) Assigned to: Nobody/Anonymous (nobody) Summary: JBoss fail to start Initial Comment: It appears that when an XA/JDBC connection can't be established at startup, the server hang and never starts. I guess this is due to a connection test just atfer binding the name in JNDI. Code looks like that: datasource.getConnection().close(); It seems that the exception is not correctly catched. -- Comment By: David Jencks (d_jencks) Date: 2002-01-10 14:30 Message: Logged In: YES user_id=60525 Is this line of code actually throwing an exception? Normally it does not, it just hangs. Set BlockingTimeout to a nonzero value and you will get an exception instead. Blocking timeout is nonzero by default in jboss 3. -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=502025group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 268 Successful tests: 266 Errors:0 Failures: 2 [time of test: 11 January 2002 2:53 GMT] [java.version: 1.3.0] [java.vendor: IBM Corporation] [java.vm.version: 1.3.0] [java.vm.name: Classic VM] [java.vm.info: J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: jitc)] [os.name: Linux] [os.arch: x86] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 268 Successful tests: 267 Errors:0 Failures: 1 [time of test: 11 January 2002 3:21 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Java HotSpot(TM) Client VM] [java.vm.info: mixed mode] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Automated JBoss Testsuite Results
JBoss daily test results SUMMARY Number of tests run: 268 Successful tests: 267 Errors:0 Failures: 1 [time of test: 11 January 2002 4:8 GMT] [java.version: 1.3.1] [java.vendor: Blackdown Java-Linux Team] [java.vm.version: Blackdown-1.3.1-FCS] [java.vm.name: Classic VM] [java.vm.info: green threads, nojit] [os.name: Linux] [os.arch: i386] [os.version: 2.4.9-12] See http://lubega.com for full details NOTE: If there are any errors shown above - this mail is only highlighting them - it is NOT indicating that they are being looked at by anyone. It is assumed that whoever makes change(s) to jboss that break the test will be fixing the test or jboss, as appropriate! DETAILS OF ERRORS [details not shown - as this makes the mail too big to reach the sf mailing list] PS BEFORE you commit, run the test suite. Its easy, just run the target 'run-basic-testsuite' from the main build.xml. PPS Come on people - there were a few days back in July 2001 when we had ZERO tests failing! Oh, and thanks - remember we love you too! ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Autogenerated primary keys etc
Is somebody going to integrate autogenerated primary key support to jaws like patch #473280? A very useful feature, I wonder why jboss still doesn't have one. Where can I find information about which the EJB 2.0 features does jboss 2.4.4 support? How about that redeploying problem on Red Hat I've reported (see my last posting here)? I'm ready to help with everything I can just tell me what you need. Best wishes, Alexei Yudichev mailto:[EMAIL PROTECTED] ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
