August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1024) Better JGroups defaults

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/WFLY-1024?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on WFLY-1024: ------------------------------------ Infinispan needs OOB thread pool to be queueless. > Better JGroups defaults > ----------------------- > > Key: WFLY-1024 > URL: https://issues.jboss.org/browse/WFLY-1024 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: NadirX > Assignee: Paul Ferraro > > The JGroups subsystem needs optimal defaults out of the box, that are also good for derived products (e.g. JDG), both for protocols and thread pools. > Use a bounded thread pool for the default executor > core-size==number of members (32 for JDG) > max-threads = 1.5*core-size > oob should be queueless > AS7 protocol list (UDP): PING, MERGE2, FD_SOCK, FD, VERIFY_SUSPECT, BARRIER, pbcast.NAKACK, UNICAST2, pbcast.STABLE, pbcast.GMS, UFC, MFC, FRAG2, RSVP > JDG protocol list (UDP): PING, MERGE2, FD_SOCK, FD_ALL, pbcast.NAKACK, UNICAST2, pbcast.STABLE, pbcast.GMS, UFC, MFC, FRAG2, RSVP > AS7 protocol list (TCP): MPING, MERGE2, FD_SOCK, FD, VERIFY_SUSPECT, BARRIER, pbcast.NAKACK, UNICAST2, pbcast.STABLE, pbcast.GMS, UFC, MFC, FRAG2, RSVP > JDG protocol list (TCP): MPING, MERGE2, FD_SOCK, FD, VERIFY_SUSPECT, pbcast.NAKACK, UNICAST2, pbcast.STABLE, pbcast.GMS, UFC, MFC, FRAG2, RSVP -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3788) Upgrade org.apache.httpcomponents:httpclient to 4.3.2

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-3788?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated WFLY-3788: ---------------------------------- Assignee: Jim Ma (was: Alessio Soldano) > Upgrade org.apache.httpcomponents:httpclient to 4.3.2 > ----------------------------------------------------- > > Key: WFLY-3788 > URL: https://issues.jboss.org/browse/WFLY-3788 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 8.1.0.Final > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: 9.0.0.Final > > > Webservice needs this upgrade to enable asynchronous client http transport in cxf 3.x. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3788) Upgrade org.apache.httpcomponents:httpclient to 4.3.2

by Jim Ma (JIRA)

Jim Ma created WFLY-3788: ---------------------------- Summary: Upgrade org.apache.httpcomponents:httpclient to 4.3.2 Key: WFLY-3788 URL: https://issues.jboss.org/browse/WFLY-3788 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 8.1.0.Final Reporter: Jim Ma Assignee: Alessio Soldano Fix For: 9.0.0.Final Webservice needs this upgrade to enable asynchronous client http transport in cxf 3.x. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3787) Add apache.cxf:cxf-rt-transports-http-hc to cxf impl module

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/WFLY-3787?page=com.atlassian.jira.plugin.... ] Jim Ma updated WFLY-3787: ------------------------- Description: Add cxf-rt-transports-http-hc dependency to enable asynchronous http transport(http://cxf.apache.org/docs/asynchronous-client-http-transport.h... in the comming cxf 3.x upgrade. This also requires add org.apache.httpcomponents.httpasyncclient in org.apache.httpcomponents module. (was: Add cxf-rt-transports-http-hc dependency to enable http://cxf.apache.org/docs/asynchronous-client-http-transport.html) > Add apache.cxf:cxf-rt-transports-http-hc to cxf impl module > ----------------------------------------------------------- > > Key: WFLY-3787 > URL: https://issues.jboss.org/browse/WFLY-3787 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 8.1.0.Final > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: 9.0.0.Final > > > Add cxf-rt-transports-http-hc dependency to enable asynchronous http transport(http://cxf.apache.org/docs/asynchronous-client-http-transport.h... in the comming cxf 3.x upgrade. This also requires add org.apache.httpcomponents.httpasyncclient in org.apache.httpcomponents module. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1875) UNICAST3/UNICAST2: sync receiver table with sender table

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1875?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1875: --------------------------- Description: If a receiver B closes its recv-table and the sender A doesn't, then (when receiving msgs from the sender) the receiver engages in a protocol using {{GET-FIRST-SEQNO}} to sync itself with the sender. This has several problems, detailed in JGRP-1873 and JGRP-1874. (Note that the other way round (sender closing send-table), there is no issue, as the sender will create a new connection with a new {{conn-id}}). To prevent {{STABLE}} messages interfering with {{GET-FIRST-SEQNO}} messages (JGRP-1873), we could run an additional {{SYNC}} protocol round, e.g. * B needs to get the lowest and highest seqno sent from A * B sends a {{SYNC}} message to A (instead of a {{GET-FIRST-SEQNO}} message) * B sets a flag that discards all {{STABLE}} or {{ACK}} messages on reception of {{SYNC}} * B replies with a {{SYNC-OK}} containing the _lowest_ and _highest_ sent seqnos * B creates an entry for A with the lowest and highest seqnos * B sends a {{SYNC-ACK}} to A * A resets the flag and starts accepting {{STABLE}} / {{ACK}} messages from B again * A and B now use the usual protocols to retransmit missing messages was: If a receiver B closes its recv-table and the sender A doesn't, then (when receiving msgs from the sender) the receiver engages in a protocol using {{GET-FIRST-SEQNO}} to sync itself with the sender. This has several problems, detailed in JGRP-1873 and JGRP-1874. (Note that the other way round (sender closing send-table), there is no issue, as the sender will create a new connection with a new {{conn-id}}). To prevent {{STABLE}} messages interfering with {{GET-FIRST-SEQNO}} messages (JGRP-1873), we could run an additional {{SYNC}} protocol round, e.g. * B needs to get the lowest and highest seqno sent from A * B sends a {{SYNC}} message to A (instead of a {{GET-FIRST-SEQNO}} message) * B sets a flag that discards all {{STABLE}} messages on reception of {{SYNC}} * B replies with a {{SYNC-OK}} containing the _lowest_ and _highest_ sent seqnos * B creates an entry for A with the lowest and highest seqnos * B sends a {{SYNC-DONE}} to A * A resets the flag and starts accepting {{STABLE}} messages from B again * A and B now use the usual protocols to retransmit missing messages > UNICAST3/UNICAST2: sync receiver table with sender table > -------------------------------------------------------- > > Key: JGRP-1875 > URL: https://issues.jboss.org/browse/JGRP-1875 > Project: JGroups > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.5 > > > If a receiver B closes its recv-table and the sender A doesn't, then (when receiving msgs from the sender) the receiver engages in a protocol using {{GET-FIRST-SEQNO}} to sync itself with the sender. This has several problems, detailed in JGRP-1873 and JGRP-1874. (Note that the other way round (sender closing send-table), there is no issue, as the sender will create a new connection with a new {{conn-id}}). > To prevent {{STABLE}} messages interfering with {{GET-FIRST-SEQNO}} messages (JGRP-1873), we could run an additional {{SYNC}} protocol round, e.g. > * B needs to get the lowest and highest seqno sent from A > * B sends a {{SYNC}} message to A (instead of a {{GET-FIRST-SEQNO}} message) > * B sets a flag that discards all {{STABLE}} or {{ACK}} messages on reception of {{SYNC}} > * B replies with a {{SYNC-OK}} containing the _lowest_ and _highest_ sent seqnos > * B creates an entry for A with the lowest and highest seqnos > * B sends a {{SYNC-ACK}} to A > * A resets the flag and starts accepting {{STABLE}} / {{ACK}} messages from B again > * A and B now use the usual protocols to retransmit missing messages -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3787) Add apache.cxf:cxf-rt-transports-http-hc to cxf impl module

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/WFLY-3787?page=com.atlassian.jira.plugin.... ] Jim Ma updated WFLY-3787: ------------------------- Description: Add cxf-rt-transports-http-hc dependency to enable http://cxf.apache.org/docs/asynchronous-client-http-transport.html (was: Add this dependency to enable ) > Add apache.cxf:cxf-rt-transports-http-hc to cxf impl module > ----------------------------------------------------------- > > Key: WFLY-3787 > URL: https://issues.jboss.org/browse/WFLY-3787 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 8.1.0.Final > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: 9.0.0.Final > > > Add cxf-rt-transports-http-hc dependency to enable http://cxf.apache.org/docs/asynchronous-client-http-transport.html -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3787) Add apache.cxf:cxf-rt-transports-http-hc to cxf impl module

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/WFLY-3787?page=com.atlassian.jira.plugin.... ] Jim Ma updated WFLY-3787: ------------------------- Description: Add this dependency to enable > Add apache.cxf:cxf-rt-transports-http-hc to cxf impl module > ----------------------------------------------------------- > > Key: WFLY-3787 > URL: https://issues.jboss.org/browse/WFLY-3787 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 8.1.0.Final > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: 9.0.0.Final > > > Add this dependency to enable -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3787) Add apache.cxf:cxf-rt-transports-http-hc to cxf impl module

by Jim Ma (JIRA)

Jim Ma created WFLY-3787: ---------------------------- Summary: Add apache.cxf:cxf-rt-transports-http-hc to cxf impl module Key: WFLY-3787 URL: https://issues.jboss.org/browse/WFLY-3787 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 8.1.0.Final Reporter: Jim Ma Assignee: Jim Ma Fix For: 9.0.0.Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3782) add-user.sh actually does not honor JBOSS_BASE_DIR

by Claudio Miranda (JIRA)

[ https://issues.jboss.org/browse/WFLY-3782?page=com.atlassian.jira.plugin.... ] Claudio Miranda commented on WFLY-3782: --------------------------------------- You can use -sc option. The help says "Define the location the server config directory." Sample: ./add-user.sh -u admin -p admin123@ -sc /jboss_domains/domain1/configuration/ > add-user.sh actually does not honor JBOSS_BASE_DIR > -------------------------------------------------- > > Key: WFLY-3782 > URL: https://issues.jboss.org/browse/WFLY-3782 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scripts > Affects Versions: 8.1.0.Final > Environment: linux > Reporter: David Tonhofer > Assignee: Darran Lofthouse > Fix For: Awaiting Volunteers > > > add-user.sh does not check whether the JBOSS_BASE_DIR points to another directory that the one which can be deduced from JBOSS_HOME assuming the default installation. This may not be what one wants, as one actually wants to update files: > JBOSS_BASE_DIR/configuration/mgmt-users.properties' > JBOSS_BASE_DIR/configuration/mgmt-users.properties' > instead of > JBOSS_HOME/standalone/configuration/mgmt-users.properties' > JBOSS_HOME/standalone/configuration/mgmt-users.properties' -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3786) Validator interceptor does not work in 8.1 on EJBs

by John Ament (JIRA)

John Ament created WFLY-3786: -------------------------------- Summary: Validator interceptor does not work in 8.1 on EJBs Key: WFLY-3786 URL: https://issues.jboss.org/browse/WFLY-3786 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 8.1.0.Final Reporter: John Ament Assignee: Jason Greene Take a look at the following git repo https://github.com/johnament/hornetq-jms-issue Run the test ValidationTest. When you execute, you'll see the following error: Caused by: org.jboss.arquillian.test.spi.ArquillianProxyException: org.jboss.weld.exceptions.IllegalArgumentException : WELD-001456: Argument bean must not be null [Proxied because : Original exception caused: class java.lang.ClassNotFoundException: org.jboss.weld.exceptions.IllegalArgumentException] Looking at it at first, you might think it's the result of validation execution (since the bean's @notNull). What's actually happening is the interceptor is trying to get a reference to the validator and failing, hence the "argument bean must not be null" part. It seems like the validation extension doesn't get activated properly when I'm dealing with a JAR within a WAR file. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2014