August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBESB-39) Add more QA and unit tests

by Tom Fennelly (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-39?page=all ] Tom Fennelly updated JBESB-39: ------------------------------ Fix Version/s: 4.0 (was: 4.0 Beta 1) > Add more QA and unit tests > -------------------------- > > Key: JBESB-39 > URL: http://jira.jboss.com/jira/browse/JBESB-39 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Mark Little > Assigned To: Tom Fennelly > Fix For: 4.0 > > Time Spent: 1 week, 4 minutes > Remaining Estimate: 0 minutes > > The Rosetta codebase does not come with a lot of tests. We need a lot more before the beta release and certainly for the GA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-95) Add unit tests for common

by Mark Little (JIRA)

Add unit tests for common ------------------------- Key: JBESB-95 URL: http://jira.jboss.com/jira/browse/JBESB-95 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.0 Alpha 1 Reporter: Mark Little Assigned To: Tom Fennelly Fix For: 4.0 Beta 1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

2
2
0 / 0

[JBoss JIRA] Reopened: (BPEL-85) Docu on the purpose of BPEL

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-85?page=all ] Thomas Diesler reopened BPEL-85: -------------------------------- Please post a link to the BPEL section in the online jbossws user guide. > Docu on the purpose of BPEL > --------------------------- > > Key: BPEL-85 > URL: http://jira.jboss.com/jira/browse/BPEL-85 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documents > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Thomas Diesler > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 2 > > > Please expand the user documentation to a section about the purpose of BPEL. It should show a not so trivial use case that illustrates (with pictures) why I should care about BPEL -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JGRP-217) unplugging of network cable makes jgroups behave weirdly

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-217?page=comments#action_12341159 ] Bela Ban commented on JGRP-217: ------------------------------- Works for me: both pulltheplug.xml and pull-tcp.xml work. I pulled the plug and - after the group falls apart - put it back in, and the subgroups merged into one. I did this multiple times. However, only in the pull-tcp.xml case did I get the warnings posted in this case. I'll investigate further. P.S.: This worked *with* VIEW_SYNC > unplugging of network cable makes jgroups behave weirdly > -------------------------------------------------------- > > Key: JGRP-217 > URL: http://jira.jboss.com/jira/browse/JGRP-217 > Project: JGroups > Issue Type: Bug > Affects Versions: 2.2.8, 2.2.9, 2.3 > Reporter: Manoranjan Sahu > Assigned To: Bela Ban > Fix For: 2.4 > > Attachments: logs.jar, mping.xml, pull-tcp.xml, pulltheplug.xml > > > Hi, > I am using jgroups 2.2.9 for communication in my cluster. > I was checking the behaviour of jgroups to network fluctuation. > for that I manually unplug the network cable and plug it back after some time. > But jgroups keeps sending suspected messages and never bring that into the cluster. > I have two machines in my cluster A(10.200.1.92) & B(10.200.1.74). > I unplug the cable in machine B. and plug it back . but B never joined the cluster. > Please find the attachment for the log files from both the machines. > I am using TCP based communication. I set up my protocol stack using . MPING,MERGE2,FD,VERIFY_SUSPECT,pbcast.NAKACK,pbcast.STABLE,VIEW_SYNC,pbcast.GMS. > The following are the confuguration in both the machines. > configuration setting in Machine-A > notificationbus.properties: > TCP(bind_addr=boca;recv_buf_size=200000;send_buf_size=100000;loopback=true; > start_port=7880): > MPING(timeout=4000;bind_to_all_interfaces=true;mcast_addr=228.8.8.8;mcast_port=7500; > ip_ttl=8;num_initial_members=4;num_ping_requests=1): > MERGE2(max_interval=10000;min_interval=5000): > FD(timeout=2000;max_tries=3): > VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false): > pbcast.NAKACK(max_xmit_size=60000;gc_lag=50; > retransmit_timeout=100,200,300,600,1200,2400,4800): > pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;down_thread=false; > up_thread=false;max_bytes=0): > VIEW_SYNC(avg_send_interval=60000;down_thread=false;up_thread=false): > pbcast.GMS(print_local_addr=true;join_timeout=5000;join_retry_timeout=2000;shun=true) > ------------------------------- > configuration setting in Machine-B > notificationbus.properties: > TCP(bind_addr=rizal;recv_buf_size=200000;send_buf_size=100000; > loopback=true;start_port=7880): > MPING(timeout=4000;bind_to_all_interfaces=true;mcast_addr=228.8.8.8; > mcast_port=7500;ip_ttl=8;num_initial_members=4;num_ping_requests=1): > MERGE2(max_interval=10000;min_interval=5000):FD(timeout=2000;max_tries=3): > VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false): > pbcast.NAKACK(max_xmit_size=60000;gc_lag=50; > retransmit_timeout=100,200,300,600,1200,2400,4800): > pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;down_thread=false; > up_thread=false;max_bytes=0): > VIEW_SYNC(avg_send_interval=60000;down_thread=false;up_thread=false): > pbcast.GMS(print_local_addr=true;join_timeout=5000;join_retry_timeout=2000;shun=true) > ---------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JGRP-217) unplugging of network cable makes jgroups behave weirdly

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-217?page=all ] Bela Ban updated JGRP-217: -------------------------- Attachment: pulltheplug.xml > unplugging of network cable makes jgroups behave weirdly > -------------------------------------------------------- > > Key: JGRP-217 > URL: http://jira.jboss.com/jira/browse/JGRP-217 > Project: JGroups > Issue Type: Bug > Affects Versions: 2.2.8, 2.2.9, 2.3 > Reporter: Manoranjan Sahu > Assigned To: Bela Ban > Fix For: 2.4 > > Attachments: logs.jar, mping.xml, pull-tcp.xml, pulltheplug.xml > > > Hi, > I am using jgroups 2.2.9 for communication in my cluster. > I was checking the behaviour of jgroups to network fluctuation. > for that I manually unplug the network cable and plug it back after some time. > But jgroups keeps sending suspected messages and never bring that into the cluster. > I have two machines in my cluster A(10.200.1.92) & B(10.200.1.74). > I unplug the cable in machine B. and plug it back . but B never joined the cluster. > Please find the attachment for the log files from both the machines. > I am using TCP based communication. I set up my protocol stack using . MPING,MERGE2,FD,VERIFY_SUSPECT,pbcast.NAKACK,pbcast.STABLE,VIEW_SYNC,pbcast.GMS. > The following are the confuguration in both the machines. > configuration setting in Machine-A > notificationbus.properties: > TCP(bind_addr=boca;recv_buf_size=200000;send_buf_size=100000;loopback=true; > start_port=7880): > MPING(timeout=4000;bind_to_all_interfaces=true;mcast_addr=228.8.8.8;mcast_port=7500; > ip_ttl=8;num_initial_members=4;num_ping_requests=1): > MERGE2(max_interval=10000;min_interval=5000): > FD(timeout=2000;max_tries=3): > VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false): > pbcast.NAKACK(max_xmit_size=60000;gc_lag=50; > retransmit_timeout=100,200,300,600,1200,2400,4800): > pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;down_thread=false; > up_thread=false;max_bytes=0): > VIEW_SYNC(avg_send_interval=60000;down_thread=false;up_thread=false): > pbcast.GMS(print_local_addr=true;join_timeout=5000;join_retry_timeout=2000;shun=true) > ------------------------------- > configuration setting in Machine-B > notificationbus.properties: > TCP(bind_addr=rizal;recv_buf_size=200000;send_buf_size=100000; > loopback=true;start_port=7880): > MPING(timeout=4000;bind_to_all_interfaces=true;mcast_addr=228.8.8.8; > mcast_port=7500;ip_ttl=8;num_initial_members=4;num_ping_requests=1): > MERGE2(max_interval=10000;min_interval=5000):FD(timeout=2000;max_tries=3): > VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false): > pbcast.NAKACK(max_xmit_size=60000;gc_lag=50; > retransmit_timeout=100,200,300,600,1200,2400,4800): > pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;down_thread=false; > up_thread=false;max_bytes=0): > VIEW_SYNC(avg_send_interval=60000;down_thread=false;up_thread=false): > pbcast.GMS(print_local_addr=true;join_timeout=5000;join_retry_timeout=2000;shun=true) > ---------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (BPEL-84) Provide an initial release that works with jbossws

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-84?page=all ] Thomas Diesler reopened BPEL-84: -------------------------------- Please post the command line that shows how to run your tests, i.e. [tdiesler@tddell test]$ ant -Dtest=samples/secureejb test tests-main: [junit] Running org.jboss.test.ws.samples.secureejb.SecureEJBTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 7.106 sec The BPEL tests should be in the samples directory, so that they are automatically bundled with the standalone samples. > Provide an initial release that works with jbossws > -------------------------------------------------- > > Key: BPEL-84 > URL: http://jira.jboss.com/jira/browse/BPEL-84 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Reporter: Thomas Diesler > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 beta 1 > > Attachments: jbpm.bpel.guide.pdf > > > The bpel release that I am looking for should be independent of Apache Axis and have the integration points to the tools layer sufficiently abstracted so that it can use wstools -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JGRP-217) unplugging of network cable makes jgroups behave weirdly

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-217?page=all ] Bela Ban updated JGRP-217: -------------------------- Attachment: pull-tcp.xml > unplugging of network cable makes jgroups behave weirdly > -------------------------------------------------------- > > Key: JGRP-217 > URL: http://jira.jboss.com/jira/browse/JGRP-217 > Project: JGroups > Issue Type: Bug > Affects Versions: 2.2.8, 2.2.9, 2.3 > Reporter: Manoranjan Sahu > Assigned To: Bela Ban > Fix For: 2.4 > > Attachments: logs.jar, mping.xml, pull-tcp.xml, pulltheplug.xml > > > Hi, > I am using jgroups 2.2.9 for communication in my cluster. > I was checking the behaviour of jgroups to network fluctuation. > for that I manually unplug the network cable and plug it back after some time. > But jgroups keeps sending suspected messages and never bring that into the cluster. > I have two machines in my cluster A(10.200.1.92) & B(10.200.1.74). > I unplug the cable in machine B. and plug it back . but B never joined the cluster. > Please find the attachment for the log files from both the machines. > I am using TCP based communication. I set up my protocol stack using . MPING,MERGE2,FD,VERIFY_SUSPECT,pbcast.NAKACK,pbcast.STABLE,VIEW_SYNC,pbcast.GMS. > The following are the confuguration in both the machines. > configuration setting in Machine-A > notificationbus.properties: > TCP(bind_addr=boca;recv_buf_size=200000;send_buf_size=100000;loopback=true; > start_port=7880): > MPING(timeout=4000;bind_to_all_interfaces=true;mcast_addr=228.8.8.8;mcast_port=7500; > ip_ttl=8;num_initial_members=4;num_ping_requests=1): > MERGE2(max_interval=10000;min_interval=5000): > FD(timeout=2000;max_tries=3): > VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false): > pbcast.NAKACK(max_xmit_size=60000;gc_lag=50; > retransmit_timeout=100,200,300,600,1200,2400,4800): > pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;down_thread=false; > up_thread=false;max_bytes=0): > VIEW_SYNC(avg_send_interval=60000;down_thread=false;up_thread=false): > pbcast.GMS(print_local_addr=true;join_timeout=5000;join_retry_timeout=2000;shun=true) > ------------------------------- > configuration setting in Machine-B > notificationbus.properties: > TCP(bind_addr=rizal;recv_buf_size=200000;send_buf_size=100000; > loopback=true;start_port=7880): > MPING(timeout=4000;bind_to_all_interfaces=true;mcast_addr=228.8.8.8; > mcast_port=7500;ip_ttl=8;num_initial_members=4;num_ping_requests=1): > MERGE2(max_interval=10000;min_interval=5000):FD(timeout=2000;max_tries=3): > VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false): > pbcast.NAKACK(max_xmit_size=60000;gc_lag=50; > retransmit_timeout=100,200,300,600,1200,2400,4800): > pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;down_thread=false; > up_thread=false;max_bytes=0): > VIEW_SYNC(avg_send_interval=60000;down_thread=false;up_thread=false): > pbcast.GMS(print_local_addr=true;join_timeout=5000;join_retry_timeout=2000;shun=true) > ---------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JGRP-227) Distributed Hashtable call to put() blocks indefinitely

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-227?page=all ] Bela Ban resolved JGRP-227. --------------------------- Resolution: Done I ran the unit test 5 times, all 5 passed. Okay, actually, I don't support calling put()/remove()/clear() etc from within a callback. As you mentioned, this has to be done on a separate thread, otherwise you will get into deadlocks, as described in http://www.jgroups.org/javagroupsnew/docs/papers/Middleware.ps. So, while this is unsupported, I added a method setDeadlockDetection() to DistributedHashtable, which you can call with a "true" argument, before calling start(). That might help, let me know. > Distributed Hashtable call to put() blocks indefinitely > ------------------------------------------------------- > > Key: JGRP-227 > URL: http://jira.jboss.com/jira/browse/JGRP-227 > Project: JGroups > Issue Type: Bug > Affects Versions: 2.2.9.1 > Environment: Mandrake Linux 9.1, Java 1.4.2 > Reporter: Mark Kopec > Assigned To: Bela Ban > Fix For: 2.4 > > Attachments: JGroupsDistTest.java > > > Distributed hashtable put(x,y) without any ERROR level locks up and creates inconsistent DHT values across cluster. > Here is the code that exposes this error: > MyListener implements DistributedHashtable.notification{ > // other methods > public void entryRemoved(Object key) { > distributedHashTableObject.put(key,"xxxsomeval"); //<-- this and subsequent on the distributedHashTableObject put() or remove() get stuck!!!! > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBRULES-341) language support for 'from'

by Michael Neale (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-341?page=all ] Michael Neale resolved JBRULES-341. ----------------------------------- Resolution: Done Is done. May need to open other tasks for marking parameter types (String, Number, Variable is probably all the parser could do easily). > language support for 'from' > --------------------------- > > Key: JBRULES-341 > URL: http://jira.jboss.com/jira/browse/JBRULES-341 > Project: JBoss Rules > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assigned To: Michael Neale > Fix For: 3.1-m1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-92) Add unit tests for listeners

by Mark Little (JIRA)

Add unit tests for listeners ---------------------------- Key: JBESB-92 URL: http://jira.jboss.com/jira/browse/JBESB-92 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.0 Alpha 1 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.0 Beta 1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 11 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006