March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-421) Investigate correctness of SEQUENCER

by Bela Ban (JIRA)

Investigate correctness of SEQUENCER ------------------------------------ Key: JGRP-421 URL: http://jira.jboss.com/jira/browse/JGRP-421 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 In the current implementation, each member assigns the seqno. IMO, this should only be done by the coord ! E.g.: - Member forwards msg to coord - Coord assigns seqno and multicasts message to all members - Each member delivers message in order of seqnos, thereby establishing total ordering -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-369) ViewAccepted is not received as expected.

by ￘yvind Eikeland (JIRA)

ViewAccepted is not received as expected. ----------------------------------------- Key: JGRP-369 URL: http://jira.jboss.com/jira/browse/JGRP-369 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Environment: Windows XP. java version "1.6.0-rc" Java(TM) SE Runtime Environment (build 1.6.0-rc-b104) Java HotSpot(TM) Client VM (build 1.6.0-rc-b104, mixed mode, sharing) Version: 2.4.0 CVS: $Id: Version.java,v 1.42 2006/10/31 12:45:32 belaban Exp $ History: (see doc/history.txt for details) Reporter: ￘yvind Eikeland Assigned To: Bela Ban Hi, We're evaluating JGroups and find its functionality very useful so far. We have built an application using State transfer using JChannel.getState() and message sending using PushPullAdapter.send(). We depend on viewAccepted messages to be securely sent and received. I've discovered behaviour that seems like a bug - please advise if we can configure the protocol stack differently to avoid this issue. I've reproduced the behaviour using org.jgroups.demos.Draw application. It happens almost every time. You should be able to do the same. 1. start 3 clients in different dos shells. (java -classpath %CP% org.jgroups.demos.Draw) 2. stop the coordinator client using the "Leave" button in the GUI. Do not kill the VM. A viewAccepted message is sent to the other two apps. A new coordinator is elected by Jgroups. 3. start the first client again. A viewAccepted message is received by all clients 4. kill the coordinator client (kill the VM). I guess this is the same behaviour as if the network was partitioned. Now, only suspect messages are coming through - indefinetely (Draw does not print those messages). A view accepted is not received. If you skip step 2 and 3 above, and only do 1 and 4, a viewAccepted message is sent and it all works. I edited ExtendedReceiverAdapter to print this message for convenience: public void suspect(Address suspected_mbr) { System.out.println("Received suspect: " + suspected_mbr.toString()); } Question: - is this a bug, or is it something wrong with the protocol setup, that we can change to make this work? C:\data\mars\3rdparty\JGroups-2.4.0.src>java -classpath %CP% org.jgroups.demos.D raw log4j:WARN No appenders could be found for logger (org.jgroups.JChannel). log4j:WARN Please initialize the log4j system properly. ------------------------------------------------------- GMS: address is 192.168.2.128:2143 ------------------------------------------------------- ** View=[192.168.2.128:2136|4] [192.168.2.128:2136, 192.168.2.128:2139, 192.168. 2.128:2143] Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 Received suspect: 192.168.2.128:2136 -- 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, 3 months

4
10
0 / 0

[JBoss JIRA] Created: (JGRP-431) Join failure

by Bela Ban (JIRA)

Join failure ------------ Key: JGRP-431 URL: http://jira.jboss.com/jira/browse/JGRP-431 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Very elusive. Possibly connected to http://jira.jboss.com/jira/browse/JGRP-357 ? 0 [WARN] [main] ClientGmsImpl.join(): join(127.0.0.1:4575) sent to 127.0.0.1:4572 timed out, retrying 4078 [WARN] [ViewHandler] CoordGmsImpl.handleMembershipChange(): 127.0.0.1:4575 already present; returning existing view [127.0.0.1:4572|1] [127.0.0.1:4572, 127.0.0.1:4575] -- received [127.0.0.1:4572|1] [127.0.0.1:4572, 127.0.0.1:4575] -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-440) Throw exception when stack cannot be created

by Bela Ban (JIRA)

Throw exception when stack cannot be created -------------------------------------------- Key: JGRP-440 URL: http://jira.jboss.com/jira/browse/JGRP-440 Project: JGroups Issue Type: Task Affects Versions: 2.4.1 SP1 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 Currently, we sometimes 'eat' an issue (e.g. property not found) and return without a meaningful description of the problem -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-435) Add local address and cluster name for each thread (e.g. UDP threads)

by Bela Ban (JIRA)

Add local address and cluster name for each thread (e.g. UDP threads) --------------------------------------------------------------------- Key: JGRP-435 URL: http://jira.jboss.com/jira/browse/JGRP-435 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4.1 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JGRP-439) Drop sender from thread naming pattern

by Bela Ban (JIRA)

Drop sender from thread naming pattern -------------------------------------- Key: JGRP-439 URL: http://jira.jboss.com/jira/browse/JGRP-439 Project: JGroups Issue Type: Task Affects Versions: 2.4.1 SP1 Reporter: Bela Ban Assigned To: Bela Ban Priority: Optional Fix For: 2.5 Because the trace messages already contain the sender where necessary. http://jira.jboss.com/jira/browse/JGRP-438 requires this, as we cannot determine the sender when the thread is named at creation time -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-438) Move renaming of thread from IncomingPacket.run() out of the critical path

by Bela Ban (JIRA)

Move renaming of thread from IncomingPacket.run() out of the critical path -------------------------------------------------------------------------- Key: JGRP-438 URL: http://jira.jboss.com/jira/browse/JGRP-438 Project: JGroups Issue Type: Task Affects Versions: 2.4.1 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 For performance reasons, we cannot rename the current thread every time a job is submitted to the thread pool, this needs to be moved into the thread factory which is associated with the thread pool, so that a thread is only renamed when created, not every time a message is received -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-916) SQLGrammarException when Using Oracle and Map Collection

by Viktor Rees (JIRA)

SQLGrammarException when Using Oracle and Map Collection -------------------------------------------------------- Key: EJBTHREE-916 URL: http://jira.jboss.com/jira/browse/EJBTHREE-916 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: Oracle 9.2, Suse 9.1, JBoss 4.0.5, EJB3.0 RC9 (Error also occurs in RC7) Reporter: Viktor Rees When using a Mapping like this with Oracle: @ManyToMany (cascade = CascadeType.ALL) @JoinTable(name = "T_TABLE_COLUMN", joinColumns = { @JoinColumn(name = "tableName") }, inverseJoinColumns = { @JoinColumn(name = "columnName") }) @MapKey(name = "columnName") private Map<String,ColumnDef> columns; Following SQLStatement produces an Oracle Error: ORA-00907: Rechte Klammer fehlt " ... select a1.columnName from ColumnDef as a1 ... " The problem is is the 'as' keywort in the generated query. Oracle does not allow 'as' for alias table names. Deploying of the ear works fine. The problem occurs, when trying to access the object. If List instead of Map collection mapping is used all works fine. There is a simple source code exmple and ear distributable in order to reproduce the bug. How can I attach or upload? -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1234) Revise portal management portlets to react properly on IdentityException

by Boleslaw Dawidowicz (JIRA)

Revise portal management portlets to react properly on IdentityException ------------------------------------------------------------------------ Key: JBPORTAL-1234 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1234 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1288) put a matrix of supported ldap servers/configurations into reference documentation

by Boleslaw Dawidowicz (JIRA)

put a matrix of supported ldap servers/configurations into reference documentation ---------------------------------------------------------------------------------- Key: JBPORTAL-1288 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1288 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz -- 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, 3 months

2
3
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 March 2007