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

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

by clebert.suconic＠jboss.com

Include Branch_New_Persistence on that list. That was the refactoring from Berkley DB to our own Journal. Jay, I guess silence will mean.. you can do clean those branches if you have time. :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217090#4217090 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217090

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XAResource.isSameRM

by timfox

Yes, this was from the old days when we had just a single remoting connection to each server, To correct it, need to check whether the connection managers are the same, not the remoting connections. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217082#4217082 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217082

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XAResource.isSameRM

by jmesnil

"jmesnil" wrote : (it thinks JBM allows 8 remoting connection to be created before sharing them) | I meant: *I think ...* View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217080#4217080 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217080

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XAResource.isSameRM

by jmesnil

Given how ClientSessionImpl.isSameRM() is written, it will return true only if both sessions share the same *remoting connection to the server*. If you create 2 sessions, they will have separate remoting connections and won't be considered as the same RM by the TM (it thinks JBM allows 8 remoting connection to be created before sharing them) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217078#4217078 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217078

17 years

1
0
0 / 0

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

by clebert.suconic＠jboss.com

I believe Branch_1416_merge is still in use by Howard. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217076#4217076 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217076

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - XAResource.isSameRM

by clebert.suconic＠jboss.com

The following test if failing: Shouldn't session1.isSameRM(session2) return true, since they refer to the same server? | public void testIsSameRM() throws Exception | { | ClientSession session1 = factory.createSession(true, false, false); | ClientSession session2 = factory.createSession(true, false, false); | | assertTrue(session1.isSameRM(session2)); | | session1.close(); | session2.close(); | } | | By consequence of that, the following JMS test that I wrote is also failing: public void testIsSamRM() throws Exception | { | XAConnection conn = null; | | conn = xacf.createXAConnection(); | | //Create a session | XASession sess1 = conn.createXASession(); | XAResource res1 = sess1.getXAResource(); | | //Create a session | XASession sess2 = conn.createXASession(); | XAResource res2 = sess2.getXAResource(); | | | assertTrue(res1.isSameRM(res2)); | | } | So, isSameRM is basically aways returning false, unless you compare res1 against itself.. BTW: (This failing test was actually the reason I was having a hard time understanding why JOIN was not being called). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217072#4217072 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217072

17 years

1
0
0 / 0

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

by jhowell＠redhat.com

Hey guys, Can we delete the following branches: Branch_1_0 Branch_1_0_1_SP Branch_1_2_0_SP Branch_Experimental_JBMESSAGING_1356 Branch_Experimental_JBMESSAGING_1356_2 Branch_1416_merge Branch_Stable Branch_Stable_temp And any other branches that might not serve any purpose anymore. I'm willing to pretend that nothing happened(no releases), prior to 1.3.0 or even 1.4.0sp3. ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217071#4217071 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217071

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: XA-related failures in JMS bridge reconnection tests

by clebert.suconic＠jboss.com

The setTreatAsNonTransactedWhenNotEnlisted was a hack to couple with TCK and the way that JCA would interact with JMS. We had to add that hack as we couldn't change the JCA code. But the use of the attribute on the Bridge seems non related to this. You probably need to make sure you aways have XA on the test. (Maybe the test is not valid for JBM2?) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217070#4217070 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217070

17 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - XA-related failures in JMS bridge reconnection tests

by jmesnil

I've ported the JMS Bridge tests to our integration tests (using 2 invm servers instead of spawned ones). Most tests pass but there are failures related to XA (QoS once-and-only-once + separate servers for the source and target queues). I've not touched that much the bridge code or the bridge tests so it's likely a regression we have on the trunk wrt XA. I'm still investigating the issue but a commented instruction caught my attention in BridgeImpl.setupJMSObjects(): | if (forwardMode == FORWARD_MODE_XA && sourceSession instanceof JBossSession) | { | JBossSession jsession = (JBossSession)sourceSession; | | ClientSession clientSession = jsession.getCoreSession(); | | //clientSession.setTreatAsNonTransactedWhenNotEnlisted(false); | } | this setTreatAsNonTransactedWhenNotEnlisted flag is no longer present in JBM trunk but I wonder if it rings any bell for people who worked on JBM 1.4 (it seems mostly related to JBMESSAGING-946)? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217063#4217063 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217063

17 years

1
0
0 / 0

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

by PeterJ

I also tried to download and build. Here is my checkout statement: svn co https://anonsvn.jboss.org/repos/portletswap/contrib/wikiPortlet/tags/1.0 wiki_1.0 I then cd'ed into wiki_1.0/wiki-common and ran: mvn install I got errors about 12 missing dependencies. Here is the last one, along with the information about the repositories searched: 12) jboss:portal-api-lib:jar:2.7.1 | | Try downloading the file manually from the project website. | | Then, install it using the command: | mvn install:install-file -DgroupId=jboss -DartifactId=portal-api-lib -Dver | sion=2.7.1 -Dpackaging=jar -Dfile=/path/to/file | | Alternatively, if you host your own repository you can deploy the file there: | | mvn deploy:deploy-file -DgroupId=jboss -DartifactId=portal-api-lib -Dversi | on=2.7.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] | | Path to dependency: | 1) jboss:wiki-common:jar:1.0 | 2) jboss:portal-api-lib:jar:2.7.1 | | ---------- | 12 required artifacts are missing. | | for artifact: | jboss:wiki-common:jar:1.0 | | from the specified remote repositories: | central (http://repo1.maven.org/maven2), | repository.jboss.org (http://repository.jboss.org/maven2), | snapshots.jboss.org (http://snapshots.jboss.org/maven2) I have successfully build JBoss AS 5.0.1.GA from the SVN sources - it has Maven portion that successfully downloaded the JARs for thirdparty, so my repositories should be correctly set. I hope this helps in resolving this issue. margomedia, all of the SVN URLs can be found by starting at http://anonsvn.jboss.org/repos/. Of course, not all projects build with Maven at this time. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217057#4217057 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217057

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