December 2008 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ConsumerTest Hudson intermittent failure

by ataylor

Ive added a method to queue:referenceHandled() that increments the delivery count. The consumer calls this before it sends each message. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195937#4195937 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195937

17 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: SubjectAuthenticationService / ActorId from JAAS

by kukeltje

I support everything that makes it more pluggable (a real 'service') with factories etc... and a lot of cleanup needs to take place... old code etc... Is this proposal for jBPM 3? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195923#4195923 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195923

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Methods for testing only

by clebert.suconic＠jboss.com

I didn' t realize that was marked for testing. I was just using Andy' s suggestion on getting the valid addresses. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195916#4195916 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195916

17 years, 3 months

1
0
0 / 0

[Design of JBoss Transaction Services] - JBossAS transaction test regression

by jhalliday

In pre-release testing of the new JBossTS 4.5, I see a regression for org.jboss.test.tm.test.MTTransactionManagerUnitTestCase.testCommitSameTxInTwoThreads The test assumes that TransactioManager.commit() will barf if the transaction associated to the thread has already been committed. This is no longer the case. The new JBossTS assumes that if you ask to commit the transaction and it's committed by the time the method returns then all is well. You'll get an warn in the logs but no exception. I believe this is consistent with the JTA API specification and more user friendly, so I'm challenging the test rather than rolling back our modification. Please let me know if you have any reason to believe this behaviour will break things other than the test and if so, on what grounds they rely on getting an exception. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195909#4195909 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195909

17 years, 3 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: Thread dumps generated by triggers/events?

by bela＠jboss.com

Formatting is the same as the JVM dumps. Regarding the API: the benefit here would be that you can drop responses from different clusters. Well, you can do that too with probe.sh, but you'd need a little help from sed/awk/cut and friends View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195906#4195906 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195906

17 years, 3 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: Thread dumps generated by triggers/events?

by galder.zamarreno＠jboss.com

Probe dump would indeed be really handy for trying to retrieve the thread dumps accross the cluster but it would be called from some Java logic (notification consumer for each different type of situation when to generate a thread) and hence I would need to call JGroups API to get the same that "probe.sh dump" would return. Also, I would expect all thread dumps from problem X to be dumped locally and then someone to inspect them with TDA or Samurai, so string sounds good to me. Note that it would help that the thread dump string is formatted in the same way as the JVM does (kill -3) as this would help compatibility with tools that are already able to read these type of dumps. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195904#4195904 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195904

17 years, 3 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: Thread dumps generated by triggers/events?

by bela＠jboss.com

To get a stack trace of all nodes in a cluster, you can use JGroups' probe: probe.sh dump http://www.jboss.org/community/docs/DOC-11689 discusses how probe can be extended, e.g. to add custom functionality. The down side is that you get back a string, there is currently no API to access the results. This is planned though View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195898#4195898 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195898

17 years, 3 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: Thread dumps generated by triggers/events?

by galder.zamarreno＠jboss.com

I finally created a JIRA for this: https://jira.jboss.org/jira/browse/JBAS-6311 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195890#4195890 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195890

17 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Why are the destinations looked up twice? (jbm1.4)

by gaohoward

In Bridge.java, this code sets up the bridge stuff, at the beginning and after setting the QoS, the same source and target dests are looked up twice, any reason? private boolean setupJMSObjects() { try { //Lookup the destinations sourceDestination = sourceDestinationFactory.createDestination(); targetDestination = targetDestinationFactory.createDestination(); if (sourceCff == targetCff) { //Source and target destinations are on the server - we can get once and only once //just using a local transacted session //everything becomes once and only once forwardMode = FORWARD_MODE_LOCALTX; } else { //Different servers if (qualityOfServiceMode == QOS_ONCE_AND_ONLY_ONCE) { //Use XA forwardMode = FORWARD_MODE_XA; } else { forwardMode = FORWARD_MODE_NONTX; } } //Lookup the destinations sourceDestination = sourceDestinationFactory.createDestination(); targetDestination = targetDestinationFactory.createDestination(); sourceConn = createConnection(sourceUsername, sourcePassword, sourceCff); ...... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195875#4195875 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195875

17 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1607 Update EJB3.0 Tutorials

by jaikiran

In the meantime, i have commited the initial version of the user guide for using the tutorials. Right now the guide only has the documentation for "stateless" tutorial. The guide is built using jdocbook Maven plugin and is available at https://svn.jboss.org/repos/jbossas/projects/ejb3/trunk/docs/tutorial/guide/ Anonymous: http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/docs/tutorial/... The user guide can be built using either cd docs/tutorial/guide | mvn clean compile or cd docs/tutorial/guide | mvn clean install The html version of the guide can then be found under docs/tutorial/guide/target/docbook/html/index.html View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195866#4195866 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4195866

17 years, 3 months

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 December 2008