March 2009 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JOIN not working..

by timfox

Can you explain what the race condition is? Not so interested in the solution at this point. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217290#4217290 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217290

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Why is this so written?

by gaohoward

In JBM 14 SimpleConnectionManager.cleanupForSessionID((String jmsSessionID), | ..... | ConnectionEndpoint conn = null; | | for (Map.Entry<String, ConnectionEndpoint> entry: endpoints.entrySet()) | { | if (entry.getKey().equals(jmsSessionID)) | { | conn = entry.getValue(); | | break; | } | } | ........ | Why don't use | ..... | ConnectionEndpoint conn = null; | | conn = endpoints.get(jmsSessionID); | ........ | instead of the for loop? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217277#4217277 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217277

17 years

1
0
0 / 0

[Design of EJB 3.0] - Plugin is Broken

by ALRubinger

@see https://jira.jboss.org/jira/browse/EJBTHREE-1767 I've separated out jboss-ejb3-proxy into: * jboss-ejb3-proxy-spi * jboss-ejb3-proxy-impl Each project has its own client assembly. However, the Plugin currently can't patch up the jbossall-client.jar to change the references in the manifest, so the TestSuite runs are failing with, for instance: Testcase: testXml1 took 0.005 sec | Caused an ERROR | javax.naming.Reference | java.lang.ClassCastException: javax.naming.Reference | at org.jboss.ejb3.test.ejbthree1060.unit.InvokedBusinessInterfaceUnitTestCase.testXml1(InvokedBusinessInterfaceUnitTestCase.java:76) This is because the client CP doesn't have the ObjectFactory on it, so we get CCE from the JNDI Reference. Any hot ideas for patching jbossall-client? S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217276#4217276 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217276

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Can we cleanup the svn repository a little?

by gaohoward

Yes, Jay, please don't delete Branch_1416_merge, my work is still in that branch and is nor merged to Branch_1_4. Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217268#4217268 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217268

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JOIN not working..

by clebert.suconic＠jboss.com

getPageOperation would also be the same case. Tim: I will commit this on my morning (your afternoon) only after talking to you as you may have another suggestion. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217247#4217247 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217247

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JOIN not working..

by clebert.suconic＠jboss.com

Synchronizing QueueImpl::getRefsOperation (per TX) would fix the test: final RefsOperation getRefsOperation(final Transaction tx) | { | - RefsOperation oper = (RefsOperation)tx.getProperty(TransactionPropertyIndexes.REFS_OPERATION); | - | - if (oper == null) | + synchronized (tx) | { | - oper = new RefsOperation(); | - | - tx.putProperty(TransactionPropertyIndexes.REFS_OPERATION, oper); | - | - tx.addOperation(oper); | + RefsOperation oper = (RefsOperation)tx.getProperty(TransactionPropertyIndexes.REFS_OPERATION); | + | + if (oper == null) | + { | + oper = new RefsOperation(); | + | + tx.putProperty(TransactionPropertyIndexes.REFS_OPERATION, oper); | + | + tx.addOperation(oper); | + } | + | + return oper; | } | - | - return oper; | } | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217224#4217224 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217224

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JOIN not working..

by clebert.suconic＠jboss.com

The problem I see is here: | prodA.send(createTextMessage(sessionA, "A")); | prodB.send(createTextMessage(sessionB, "B")); | prodA and prodB will both send Async, in parallel execution, since they use two distinct Sessions. TransactionImpl is not synchronizing some of its collections, as the whole thing was not really planned for concurrency, what was an exception when playing with Joining as the test was written.... creating some race conditions. Those tests will aways fail in the first time, and pass at the second time. (probably because of ClassLoading creating more race conditions). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217221#4217221 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217221

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JOIN not working..

by clebert.suconic＠jboss.com

I forgot to tell what's the failure. The messages are not being delivered. The following assertion will fail: | ClientMessage msg = cons1.receive(1000); | assertNotNull(msg); | msg.acknowledge(); | Also... if both messages are sent using only sessionA or only sessionB, the test will pass. So, if I make this change. the test will pass also: | ClientProducer prodA = sessionB.createProducer(ADDRESS1); | ClientProducer prodB = sessionB.createProducer(ADDRESS2); | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217213#4217213 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217213

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JOIN not working..

by clebert.suconic＠jboss.com

Unless I made some mistake on the following testCase, there is some problem on JOIN (which I will be investigating). But if you guys could please take a look on this testcase... just to make sure I'm not missing anything obvious: | public void testSimpleJoin() throws Exception | { | SimpleString ADDRESS1 = new SimpleString("Address-1"); | SimpleString ADDRESS2 = new SimpleString("Address-2"); | | clientSession.createQueue(ADDRESS1, ADDRESS1, true); | clientSession.createQueue(ADDRESS2, ADDRESS2, true); | | Xid xid = newXID(); | ClientSession sessionA = sessionFactory.createSession(true, false, false); | sessionA.start(xid, XAResource.TMNOFLAGS); | | ClientSession sessionB = sessionFactory.createSession(true, false, false); | sessionB.start(xid, XAResource.TMJOIN); | | | ClientProducer prodA = sessionA.createProducer(ADDRESS1); | ClientProducer prodB = sessionB.createProducer(ADDRESS2); | | prodA.send(createTextMessage(sessionA, "A")); | prodB.send(createTextMessage(sessionB, "B")); | | sessionA.end(xid, XAResource.TMSUCCESS); | sessionB.end(xid, XAResource.TMSUCCESS); | | // Since sessionA and B are from the same server, we could close B and commit the XID through sessionA, as B was JOINED | sessionB.close(); | | sessionA.commit(xid, true); | | sessionA.close(); | | | xid = newXID(); | | clientSession.start(xid, XAResource.TMNOFLAGS); | | ClientConsumer cons1 = clientSession.createConsumer(ADDRESS1); | ClientConsumer cons2 = clientSession.createConsumer(ADDRESS2); | | clientSession.start(); | | ClientMessage msg = cons1.receive(1000); | assertNotNull(msg); | msg.acknowledge(); | | assertNull(cons1.receiveImmediate()); | | | msg = cons2.receive(1000); | assertNotNull(msg); | msg.acknowledge(); | | | assertNull(cons2.receiveImmediate()); | | clientSession.end(xid, XAResource.TMSUCCESS); | | clientSession.commit(xid, true); | | clientSession.close(); | } | And the same test, but using a real TransactionManager instead: | public void testSimpleJoinWithTM() throws Exception | { | | SimpleString ADDRESS1 = new SimpleString("Address-1"); | SimpleString ADDRESS2 = new SimpleString("Address-2"); | | clientSession.createQueue(ADDRESS1, ADDRESS1, true); | clientSession.createQueue(ADDRESS2, ADDRESS2, true); | | TransactionManager tm = new TransactionManagerImple(); | tm.begin(); | | Transaction tx = tm.getTransaction(); | | ClientSession sessionA = sessionFactory.createSession(true, false, false); | | tx.enlistResource(sessionA); | | ClientSession sessionB = sessionFactory.createSession(true, false, false); | | tx.enlistResource(sessionB); | | ClientProducer prodA = sessionA.createProducer(ADDRESS1); | ClientProducer prodB = sessionB.createProducer(ADDRESS2); | | prodA.send(createTextMessage(sessionA, "A")); | prodB.send(createTextMessage(sessionA, "B")); | | tx.delistResource(sessionA, XAResource.TMSUCCESS); | tx.delistResource(sessionB, XAResource.TMSUCCESS); | | tm.commit(); | | sessionB.close(); | sessionA.close(); | | tm.begin(); | | tx = tm.getTransaction(); | tx.enlistResource(clientSession); | | ClientConsumer cons1 = clientSession.createConsumer(ADDRESS1); | ClientConsumer cons2 = clientSession.createConsumer(ADDRESS2); | | clientSession.start(); | | ClientMessage msg = cons1.receive(1000); | assertNotNull(msg); | msg.acknowledge(); | | assertNull(cons1.receiveImmediate()); | | msg = cons2.receive(1000); | assertNotNull(msg); | msg.acknowledge(); | | | assertNull(cons2.receiveImmediate()); | | tx.delistResource(clientSession, XAResource.TMSUCCESS); | | tm.commit(); | | clientSession.close(); | } | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217211#4217211 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217211

17 years

1
0
0 / 0

[Design of JBoss Wiki] - Re: Installation of JBoss Wiki

by PeterJ

Well, while the build did not complain, I don't think that the end result is correct. In the target directory I end up with: target/lib/wiki-common.jar target/wiki-management.jar target/wiki-test.war The build apparently still needs some fixing before it works correctly. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217197#4217197 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217197

17 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2009