July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-619) Change getState semantics

by Vladimir Blagojevic (JIRA)

Change getState semantics ------------------------- Key: JGRP-619 URL: http://jira.jboss.com/jira/browse/JGRP-619 Project: JGroups Issue Type: Task Affects Versions: 2.5, 2.4, 2.3, 2.2.9 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 3.0 Currently Channel's getState method returns boolean indicating only whether state was successfully received by state receiver and not whether it was successfully processed at relevant channel listener. This anomaly lead convoluted application code that had to do rather complicated lock synchronization and notification mechanism on the progress of entire state transfer. We have to simplify this process! State receiver should simply call blocking getState and be notified in the form of Exception of anything that went wrong; be it that state could not be received at all or that it was received but could not be installed at channel listener. This issue is closely related to revamping of channel state transfer callbacks - JGRP-563 -- 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

14 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JGRP-1344) Replace ChannelException with Exception

by Bela Ban (JIRA)

Replace ChannelException with Exception --------------------------------------- Key: JGRP-1344 URL: https://issues.jboss.org/browse/JGRP-1344 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 public void JChannel.connect(String cluster) throws ChannelException --> throws Exception This is more generic, and we can still throw ChannelClosedExceptions (needs to be listed in the javadoc) This way, we don't have to wrap an Exception received from state transfer (fetching state or setting state) into a StateTransferException -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1335) Collapse setState and getState callbacks

by Vladimir Blagojevic (JIRA)

Collapse setState and getState callbacks ---------------------------------------- Key: JGRP-1335 URL: https://issues.jboss.org/browse/JGRP-1335 Project: JGroups Issue Type: Feature Request Affects Versions: 2.12, 2.11, 2.10, 2.9, 2.6 Reporter: Vladimir Blagojevic Assignee: Bela Ban Fix For: 3.0 Currently we maintain two sets of getState and setState callbacks, one for byte based transfer and the other for stream based transfer. Users had to implement both types of callbacks if the wanted to interchange STREAMING_STATE_TRANSFER and STATE_TRANSFER. If we use only stream based callbacks we can simplify client code and users can choose what type of transfer they want as a protocol option of STREAMING_STATE_TRANSFER. Finally, we could potentially drop STATE_TRANSFER all together. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1201) test for en/diable xa datasources

by Stefano Maestri (JIRA)

test for en/diable xa datasources --------------------------------- Key: AS7-1201 URL: https://issues.jboss.org/browse/AS7-1201 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1206) test for jndi binding isn't unbound during remove if jndi name and data-source name are different

by Stefano Maestri (JIRA)

test for jndi binding isn't unbound during remove if jndi name and data-source name are different ------------------------------------------------------------------------------------------------- Key: AS7-1206 URL: https://issues.jboss.org/browse/AS7-1206 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1202) test for enable datasource

by Stefano Maestri (JIRA)

test for enable datasource -------------------------- Key: AS7-1202 URL: https://issues.jboss.org/browse/AS7-1202 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1200) test case for xa datasource persistence to xml

by Stefano Maestri (JIRA)

test case for xa datasource persistence to xml ---------------------------------------------- Key: AS7-1200 URL: https://issues.jboss.org/browse/AS7-1200 Project: Application Server 7 Issue Type: Sub-task Reporter: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1290) add cls/clear command

by Alexey Loubyansky (JIRA)

add cls/clear command --------------------- Key: AS7-1290 URL: https://issues.jboss.org/browse/AS7-1290 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.1.Final Add a command to clear the terminal. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1166) Quit the CLI on EOF

by Marek Schmidt (JIRA)

Quit the CLI on EOF ------------------- Key: AS7-1166 URL: https://issues.jboss.org/browse/AS7-1166 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.0.0.CR1 Reporter: Marek Schmidt jboss-admin.sh should behave more like a shell and terminate on EOF (ctrl-D) The current behavior is quite counter-intuitive and trying to do e.g. echo "deploy foo.war" | ./jboss-admin.sh --connect leads the CLI into an infinite-loop generating infinite number of prompts. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1312) Invalid class in deployment causes deployment to fail

by Stuart Douglas (JIRA)

Invalid class in deployment causes deployment to fail ----------------------------------------------------- Key: AS7-1312 URL: https://issues.jboss.org/browse/AS7-1312 Project: Application Server 7 Issue Type: Bug Reporter: Stuart Douglas If jandex fails to process a class the whole deployment blow up. This should really just log a warning. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
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 July 2011