March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1153) Shared transport badly broken

by BjÃ¶rn Kautler (JIRA)

Shared transport badly broken ----------------------------- Key: JGRP-1153 URL: https://jira.jboss.org/jira/browse/JGRP-1153 Project: JGroups Issue Type: Bug Affects Versions: 2.7 Environment: EHCache 1.7.2 ehcache-jgroupsreplication 1.3 JGroups 2.7.0.GA Reporter: BjÃ¶rn Kautler Assignee: Bela Ban I tried to use JGroups with a shared transport (while using only one JChannel, the one EHCache uses for replication). At ProtocolStack.java:719 the TP.ProtocolAdapter is added to the protocol stack when a shared transport is used. This leads to problems after shunning. When the JChannel.CloserThread tries in line 2018 to reopen the JChannel, the Protocol Stack is recreated. But now the TP$ProtocolAdapter is part of the protocol stack and thus of the config string created from the protocol stack at JChannel:327. As the ProtocolAdapter does not have a default constructor, the whole thing explodes at Configurator:732 where the newInstance() call of course fails while the ProtocolAdapter probably shouldn't be in the protocol stack anyway at this point in time. I guess it would be added a second time at ProtocolStack.java:719 then. Also after disabling the shared transport it seems that the problem I was able to reproduce halfway reliably through restarting both instances simultaneously doesn't arise again without shared transport. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
4
0 / 0

[JBoss JIRA] Deleted: (JGRP-1172) UnicastTestRpcDist: show perf numbers for reads and writes separately

by Bela Ban (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-1172?page=com.atlassian.jira.plug... ] Bela Ban deleted JGRP-1172: --------------------------- > UnicastTestRpcDist: show perf numbers for reads and writes separately > --------------------------------------------------------------------- > > Key: JGRP-1172 > URL: https://jira.jboss.org/jira/browse/JGRP-1172 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > > In addition to requests -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-822) NAKACK: concurrent delivery of messages from the same sender

by Bela Ban (JIRA)

NAKACK: concurrent delivery of messages from the same sender ------------------------------------------------------------ Key: JGRP-822 URL: https://jira.jboss.org/jira/browse/JGRP-822 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.x JGroups delivers messages from different senders concurrently. However, it delivers messages from the same sender sequentially. Sometimes, we can deliver messages from the same sender concurrently too, if the app tells us it is okay. For example: - Node N was 3 HTTP sessions: A, B and C - Clients update those sessions concurrently - As a result, N sends the following messages: A1, B1, A2, C1, C2, C3, B2, A3 - As NAKACK assigns sequence numbers (seqnos) based on JGroups instances, all messages from N will have to be delivered in the same order in which they were sent, e.g. (-> means followed by): A1 -> B1 -> A2 -> C1 -> C2 -> C3 -> B2 -> A3 - This means that, for example, the first update to C (C1) has to wait until A1, B1 and A2 have been delivered - This is not optimal, as updates for A, B and C are completely independent, and can be delivered in parallel - So a better delivery would be ('||' means concurrent delivery): A1 -> A2 -> A3 || B1 -> B2 || C1 -> C2 -> C3 - A3 needs to be delivered after A2 which needs to be delivered after A1. However, all updates for A can be delivered concurrently with messages for B or C. - OOB doesn't help: here all messages are delivered concurrently, but there is also no ordering within A, B or C ! SOLUTION: the sender adds a 'scope' token to a Message, e.g. the jsessionid (A, B or C). JGroups maintains NakReceiverWindows per *scope*, not per sender. The sender's address is the default token, so in the absence of a scope token, JGroups of course maintains NakReceiverWindows per sender. (NakReceiverWindows are used to keep track of seqnos). In the above example, if the scopes sent with *each message* are A, B and C, then we'd have 3 NakReceiverWindows: N::A, N::B, N::C. Each window would start with seqno 1, so updates for A, B and C are delivered concurrently with respect to each other, but sequentially within the scope. Issues: - This is an API change, and should probably be propagated up to the building blocks, such as RpcDispatcher. - A scope needs to be associated with an address A (of a JGroups instance): when A leaves or crashes, all associated scopes and their NakReceiverWindows needs to be released, too - Should this be done for UNICAST too ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
12
0 / 0

[JBoss JIRA] Created: (JGRP-930) Provide hooks for scopes

by Bela Ban (JIRA)

Provide hooks for scopes ------------------------ Key: JGRP-930 URL: https://jira.jboss.org/jira/browse/JGRP-930 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 Just implement the scope field in a Message (a header?) and provide the impl later -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-7860) Bring in the EJB3 proxy component required for EJB3 nointerface component

by jaikiran pai (JIRA)

Bring in the EJB3 proxy component required for EJB3 nointerface component ------------------------------------------------------------------------- Key: JBAS-7860 URL: https://jira.jboss.org/jira/browse/JBAS-7860 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System, EJB3 Reporter: jaikiran pai Assignee: jaikiran pai Update the build scripts to include the proxy component jars in the common/lib folder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6293) Chapter 11 example missing from JBoss AS 5.0.0.GA

by Bruce Link (JIRA)

Chapter 11 example missing from JBoss AS 5.0.0.GA ------------------------------------------------- Key: JBAS-6293 URL: https://jira.jboss.org/jira/browse/JBAS-6293 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Affects Versions: JBossAS-5.0.0.GA Environment: Not applicable Reporter: Bruce Link Assignee: Samson Kittoli The installation and getting started guide discusses a jsfejb3 example. "11.4.1. Building The Application Let's look at building the example application and then explore the configuration files in detail. In Chapter 10, Sample Applications , we looked at the directory structure of the jsfejb3 sample application. " The example directory does not exist in the referenced %JBOSS_HOME%/docs/examples directory. Chapter 10 does not look at the directory structure of this or any other sample application. Reference to actual application directory and code/configuration and build files needs to be provided -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

7
13
0 / 0

[JBoss JIRA] Created: (JBAS-7867) Spelling mistake in document

by Mark Jeffery (JIRA)

Spelling mistake in document ---------------------------- Key: JBAS-7867 URL: https://jira.jboss.org/jira/browse/JBAS-7867 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Reporter: Mark Jeffery Priority: Trivial Table 9.1 Server Configuration Directory Structure The last sentence in the "data" entry Description column reads "Serveral JBoss services" and should read "Several JBoss services" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7870) Typo in document

by Mark Jeffery (JIRA)

Typo in document ---------------- Key: JBAS-7870 URL: https://jira.jboss.org/jira/browse/JBAS-7870 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Reporter: Mark Jeffery Priority: Trivial Chapter 3 Installation Alternatives Bullet point Source Files Download on page 15 Reads "Three types of server configurations" should read "Five types of server configurations" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7866) Typo in document

by Mark Jeffery (JIRA)

Typo in document ---------------- Key: JBAS-7866 URL: https://jira.jboss.org/jira/browse/JBAS-7866 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Reporter: Mark Jeffery Priority: Trivial Section 9.2 Server Configurations 4th paragraph reads The JBoss Application Server ships with three different server configurations. Should this read "The JBoss Application Server ships with five different server configurations" ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1792) NPE on org.jboss.ejb3.BaseSessionContext.isCallerInRole

by Dmitri Voronov (JIRA)

NPE on org.jboss.ejb3.BaseSessionContext.isCallerInRole ------------------------------------------------------- Key: EJBTHREE-1792 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1792 Project: EJB 3.0 Issue Type: Bug Components: ejb3 Affects Versions: AS 4.2.3.GA Reporter: Dmitri Voronov We get NPE on calling org.jboss.ejb3.BaseSessionContext.isCallerInRole(String roleName) if the in ejb-jar.xml defines: <security-role-ref> <role-name>aRole</role-name> </security-role-ref> (without role-link) and roleName = aRole, because further method tries to use the role-link which is null. role-link is actually optional according to EJB3.0 specification. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
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 2010