April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Deleted: (JBMESSAGING-1862) Enhancement - No duplicated messages when cluster is split up into to sub clusters

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1862?page=com.atlassian.jira.... ] Miroslav Novak deleted JBMESSAGING-1862: ---------------------------------------- > Enhancement - No duplicated messages when cluster is split up into to sub clusters > ---------------------------------------------------------------------------------- > > Key: JBMESSAGING-1862 > URL: https://issues.jboss.org/browse/JBMESSAGING-1862 > Project: JBoss Messaging > Issue Type: Enhancement > Reporter: Miroslav Novak > Assignee: Miroslav Novak > > For now the behaviour is following: > Test configuration: > 4 nodes EAP 4.3.8 in cluster, MySQL 5 for JBM, clustered queue deployed on all nodes. > Stand alone producer, receiver. > We use ConnectionFactory in following scenario for standalone producer and consumer (using auto_acknoledge mode) to be sure that client is connected to required node. > Test scenario: > 1) Start all nodes, There is now cluster of four nodes A - B - C - D with clustered queue "testDistributedQueue" > 2) Send 500 messages into each node > 3) Check status of DB, you should see 500 messages for each node > 4) Remove network connectivity between nodes A-C, A-D, B-C, B-D (so there are now connected only A-B,C-D) > 5) Wait (5 min) > 6) Disconnect all nodes from DB > 7) Try read from A > 8) Try read from B > 9) Look to database - each node have 500 messages in the queue > 10) Reconnect all nodes to DB > 11) Look to database you will see that fail-over occurs. Number of messages on each node - A: 1499 B:499 C:0 D:0 - two messages are lost - it's current behaviour > 12) Read from A - 1998 messages is received and there are no messages in DB (it's ok) > 13) Read from B - 0 messages is received (it's ok) > 14) Read from C - 500 messages is received. Those are duplicated messages and the new regression. > 15) Read from D - 500 messages is received. Those are duplicated messages and the new regression. > Also when A is reconnected to DB (step 10) then nodes C and D are removed from jbm_postoffice table. But those nodes still live. > As enhancement this should be fixed. > An expected behaviour should be specified but those things should hold: > a) No duplicated messages should occur in step 14. and 15. > b) No message loss after step 10. > c) Client should be able to read all the messages from clustered queue on any node. > Thanks, > Mirek -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1862) Enhancement - No duplicated messages when cluster is split up into to sub clusters

by Miroslav Novak (JIRA)

Enhancement - No duplicated messages when cluster is split up into to sub clusters ---------------------------------------------------------------------------------- Key: JBMESSAGING-1862 URL: https://issues.jboss.org/browse/JBMESSAGING-1862 Project: JBoss Messaging Issue Type: Enhancement Components: JMS Clustering Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA Reporter: Miroslav Novak Assignee: Miroslav Novak For now the behaviour is following: Test configuration: 4 nodes EAP 4.3.8 in cluster, MySQL 5 for JBM, clustered queue deployed on all nodes. Stand alone producer, receiver. We use ConnectionFactory in following scenario for standalone producer and consumer (using auto_acknoledge mode) to be sure that client is connected to required node. Test scenario: 1) Start all nodes, There is now cluster of four nodes A - B - C - D with clustered queue "testDistributedQueue" 2) Send 500 messages into each node 3) Check status of DB, you should see 500 messages for each node 4) Remove network connectivity between nodes A-C, A-D, B-C, B-D (so there are now connected only A-B,C-D) 5) Wait (5 min) 6) Disconnect all nodes from DB 7) Try read from A 8) Try read from B 9) Look to database - each node have 500 messages in the queue 10) Reconnect all nodes to DB 11) Look to database you will see that fail-over occurs. Number of messages on each node - A: 1499 B:499 C:0 D:0 - two messages are lost - it's current behaviour 12) Read from A - 1998 messages is received and there are no messages in DB (it's ok) 13) Read from B - 0 messages is received (it's ok) 14) Read from C - 500 messages is received. Those are duplicated messages and the new regression. 15) Read from D - 500 messages is received. Those are duplicated messages and the new regression. Also when A is reconnected to DB (step 10) then nodes C and D are removed from jbm_postoffice table. But those nodes still live. As enhancement this should be fixed. An expected behaviour should be specified but those things should hold: a) No duplicated messages should occur in step 14. and 15. b) No message loss after step 10. c) Client should be able to read all the messages from clustered queue on any node. Thanks, Mirek -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9332) Provide an operation to retrieve JDBC drives that installed as deployments

by Heiko Braun (JIRA)

Provide an operation to retrieve JDBC drives that installed as deployments -------------------------------------------------------------------------- Key: JBAS-9332 URL: https://issues.jboss.org/browse/JBAS-9332 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Heiko Braun Fix For: 7.0.0.Beta4 I managed to deploy JDBC drivers through the HTTP API. Creating datasources works as well. The remaining question is: How to I locate the JDBC drives that are installed as a deployment? They don't show up under /subsystem=datasources/jdbc-driver=* In order to create the Datasource I need to provide a list of available drives to the user. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (JBWEB-182) juli*.log created in the current directory intead of $CATALINA_BASE/logs

by Marcin Szewczyk (JIRA)

juli*.log created in the current directory intead of $CATALINA_BASE/logs ------------------------------------------------------------------------ Key: JBWEB-182 URL: https://jira.jboss.org/browse/JBWEB-182 Project: JBoss Web Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: JBossWeb-2.1.9.GA Environment: Ubuntu GNU/Linux Lucid 10.04.1 Reporter: Marcin Szewczyk Assignee: Remy Maucherat Priority: Minor Fix For: JBossWeb-2.1.9.GA juli*.log created in the current directory intead of $CATALINA_BASE/logs -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWEB-198) Backport ELSupport throws exception when passing null value and Number type to coerceToNumber method

by Jason Shepherd (JIRA)

Backport ELSupport throws exception when passing null value and Number type to coerceToNumber method ---------------------------------------------------------------------------------------------------- Key: JBWEB-198 URL: https://issues.jboss.org/browse/JBWEB-198 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossWeb-2.1.0.GA Reporter: Jason Shepherd Assignee: Remy Maucherat if (Number.class.equals(type)) { return number; } was added to protected final static Number coerceToNumber(final Number number, final Class<?> type) throws ELException as of tags/JBOSSWEB_3_0_0_BETA3 Need this backported to 2.1.x branch, and released with EAP 5.1.2 or similar. See attached Jira for EAP, JBPAPP-6382 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Commented: (AS7-668) Missing error when CLI connection fails

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-668?page=com.atlassian.jira.plugin.sy... ] Alexey Loubyansky commented on AS7-668: --------------------------------------- It's already fixed in my cli branch. It was committed w/o a reference to this issue or any equivalent. > Missing error when CLI connection fails > --------------------------------------- > > Key: AS7-668 > URL: https://issues.jboss.org/browse/AS7-668 > Project: Application Server 7 > Issue Type: Enhancement > Components: CLI > Reporter: Heiko Braun > Assignee: Alexey Loubyansky > > [localhost:9999 /] connect > Closed connection to localhost:9999 > Connected to localhost:9999 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (AS7-668) Missing error when CLI connection fails

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-668?page=com.atlassian.jira.plugin.sy... ] Heiko Braun reassigned AS7-668: ------------------------------- Assignee: Alexey Loubyansky (was: Jason Greene) > Missing error when CLI connection fails > --------------------------------------- > > Key: AS7-668 > URL: https://issues.jboss.org/browse/AS7-668 > Project: Application Server 7 > Issue Type: Enhancement > Components: CLI > Reporter: Heiko Braun > Assignee: Alexey Loubyansky > > [localhost:9999 /] connect > Closed connection to localhost:9999 > Connected to localhost:9999 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9286) Fix JVM references in server group model

by Heiko Braun (JIRA)

Fix JVM references in server group model ---------------------------------------- Key: JBAS-9286 URL: https://issues.jboss.org/browse/JBAS-9286 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 Requesting a server group resource I get this: { [INFO] "PROPERTY_VALUE" : { [INFO] "other-server-group" : { [INFO] "profile" : "default", [INFO] "jvm" : {"default" : { [INFO] "type" : null, [INFO] "agent-lib" : null, [INFO] "agent-path" : null, [INFO] "debug-enabled" : null, [INFO] "debug-options" : null, [INFO] "env-classpath-ignored" : null, [INFO] "environment-variables" : null, [INFO] "heap-size" : "64m", [INFO] "max-heap-size" : "512m", [INFO] "java-agent" : null, [INFO] "java-home" : null, [INFO] "jvm-options" : null, [INFO] "permgen-size" : null, [INFO] "max-permgen-size" : null, [INFO] "stack-size" : null, [INFO] "system-properties" : null [INFO] }}, [INFO] "deployment" : {}, [INFO] "socket-binding-group" : "standard-sockets" [INFO] } [INFO] } [INFO] }, The pice that's causing me a headache is again the JVm property. Can we agree that subresources like the JVM in this case are always referenced as ModelNode's of type property? Similar to the server-group itself? Currently it's returned as type Object, with a property of name 'jvm' This would simplify the way to get hold of the subresource name. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9162) Serve console from "/console" (w/o index.html)

by Heiko Braun (JIRA)

Serve console from "/console" (w/o index.html) ---------------------------------------------- Key: JBAS-9162 URL: https://issues.jboss.org/browse/JBAS-9162 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-9315) Provide open/save/model for domain resources

by Heiko Braun (JIRA)

Provide open/save/model for domain resources -------------------------------------------- Key: JBAS-9315 URL: https://issues.jboss.org/browse/JBAS-9315 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management, Web Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
5
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 April 2011