December 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3084) Enable control of chunked encoding when using SOAPConnection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3084?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3084: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 900032|https://bugzilla.redhat.com/show_bug.cgi?id=900032] from VERIFIED to CLOSED > Enable control of chunked encoding when using SOAPConnection > ------------------------------------------------------------ > > Key: JBWS-3084 > URL: https://issues.jboss.org/browse/JBWS-3084 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-native > Affects Versions: jbossws-cxf-3.3.1, jbossws-native-3.3.1 > Reporter: Darran Lofthouse > Assignee: Richard Opalka > Fix For: jbossws-cxf-3.4.0, jbossws-native-3.4.0 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3671) AbstractServerConfig keep stale reference to server config after reboot

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3671?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3671: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 959426|https://bugzilla.redhat.com/show_bug.cgi?id=959426] from VERIFIED to CLOSED > AbstractServerConfig keep stale reference to server config after reboot > ----------------------------------------------------------------------- > > Key: JBWS-3671 > URL: https://issues.jboss.org/browse/JBWS-3671 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Affects Versions: jbossws-cxf-4.1.1 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > As a consequence of JBWS-3576 fix, the AbstractServerConfig's reference to the AS container ServerConfig might turn into a stale object if the server is reloaded through management. We need to clean up the static references in such cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3719) ServiceContainerEndpointRegistry#getRegisteredEndpoints() returns set containing null

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3719?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3719: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1017550|https://bugzilla.redhat.com/show_bug.cgi?id=1017550] from VERIFIED to CLOSED > ServiceContainerEndpointRegistry#getRegisteredEndpoints() returns set containing null > ------------------------------------------------------------------------------------- > > Key: JBWS-3719 > URL: https://issues.jboss.org/browse/JBWS-3719 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration, jbossws-native > Affects Versions: jbossws-cxf-4.2 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.2 > > > The ServiceContainerEndpointRegistry#getRegisteredEndpoints() can return a set containing null as the retrieval of the service list from the container service registry plus the lookup of each service corresponding to the name is not atomic. We need to protect against this, as the consumers of org.jboss.wsf.spi.management.EndpointRegistry#resolve(EndpointResolver resolver) choke on it with NPEs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3717) EndpointResolver implementations do not verify endpoint state before using endpoint

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3717?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3717: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1017550|https://bugzilla.redhat.com/show_bug.cgi?id=1017550] from VERIFIED to CLOSED > EndpointResolver implementations do not verify endpoint state before using endpoint > ----------------------------------------------------------------------------------- > > Key: JBWS-3717 > URL: https://issues.jboss.org/browse/JBWS-3717 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration, jbossws-native > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.2 > > > Currently the implementors of EndpointResolver (namely, WebAppResolver and PortComponentResolver do not check the state of an endpoint before trying using it. This is a problem as with JBWS-3643 the EndpointRegistry is now based on the AS service registry, so it's possible for the resolvers to see endpoints that are not started yet. The issue would likely affect scenarios with frequent and concurrent deploy/undeploy sequences or requests reaching the AS during boot. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3642) Replace gnu-getopt:getopt with gnu.getopt:java-getopt

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3642?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3642: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 1007527|https://bugzilla.redhat.com/show_bug.cgi?id=1007527] from VERIFIED to CLOSED > Replace gnu-getopt:getopt with gnu.getopt:java-getopt > ----------------------------------------------------- > > Key: JBWS-3642 > URL: https://issues.jboss.org/browse/JBWS-3642 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > We're including gnu getopt (for jaxws tooling) from the jboss thirdparty repository; we should replace that with the gnu.getopt:java-getopt from maven central. That would help for building jbossws using the maven central repo only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3745) Allow disabling Nagle's algorithm on Web Service calls

by Navin Surtani (JIRA)

[ https://issues.jboss.org/browse/JBWS-3745?page=com.atlassian.jira.plugin.... ] Navin Surtani updated JBWS-3745: -------------------------------- Comment: was deleted (was: A comment with security level 'JBoss Employee' was removed.) > Allow disabling Nagle's algorithm on Web Service calls > ------------------------------------------------------ > > Key: JBWS-3745 > URL: https://issues.jboss.org/browse/JBWS-3745 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-native > Reporter: Navin Surtani > Assignee: Navin Surtani > Attachments: JBWS-3745-native.patch > > > From EAP5-8: > Within the Socket class we would like to be able to configure the ability to pass a parameter for the socket.setTcpNoDelay(boolean) method. > We've found certain cases where having the algorithm enabled actually slows the overall performance of transactions. By setting the TCP No Delay to 'true' it will bypass the algorithm, allowing packets to flow through the network immediately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3745) Allow disabling Nagle's algorithm on Web Service calls

by Navin Surtani (JIRA)

[ https://issues.jboss.org/browse/JBWS-3745?page=com.atlassian.jira.plugin.... ] Navin Surtani updated JBWS-3745: -------------------------------- Attachment: (was: JBWS-3745-cxf-trunk.patch) > Allow disabling Nagle's algorithm on Web Service calls > ------------------------------------------------------ > > Key: JBWS-3745 > URL: https://issues.jboss.org/browse/JBWS-3745 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-native > Reporter: Navin Surtani > Assignee: Navin Surtani > Attachments: JBWS-3745-native.patch > > > From EAP5-8: > Within the Socket class we would like to be able to configure the ability to pass a parameter for the socket.setTcpNoDelay(boolean) method. > We've found certain cases where having the algorithm enabled actually slows the overall performance of transactions. By setting the TCP No Delay to 'true' it will bypass the algorithm, allowing packets to flow through the network immediately. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3747) Higher precision in endpoint metrics

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3747?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3747: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 > Higher precision in endpoint metrics > ------------------------------------ > > Key: JBWS-3747 > URL: https://issues.jboss.org/browse/JBWS-3747 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > Use System.nanoTime() instead of System.currentTimeMillis() > https://blogs.oracle.com/dholmes/entry/inside_the_hotspot_vm_clocks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3747) Higher precision in endpoint metrics

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3747: ------------------------------------- Summary: Higher precision in endpoint metrics Key: JBWS-3747 URL: https://issues.jboss.org/browse/JBWS-3747 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Use System.nanoTime() instead of System.currentTimeMillis() https://blogs.oracle.com/dholmes/entry/inside_the_hotspot_vm_clocks -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3733) Allow enabling/disabling endpoint metrics

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3733?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3733: --------------------------------------- Brian wrote: Thanks, everyone, for the input on this. I'd like to do the following about getting configuration of these consistent for WF 8.0: 1) For all resources that currently expose an attribute to enable/disable statistics, I'll add an attribute that will be named "statistics-enabled". Why that? a) it's an attribute, so it's name should reflect a state, not an action like, for example, "enable-statistics" b) simply using "statistics" is shorter, but in some places that key is used as a child type (e.g. statistics=pool) and a resource can't have a child type and an attribute with the same name. 2) For compatibility, the existing attribute will be retained as an alias to the new one. I'll add deprecation metadata. I'll also set up the appropriate transformation stuff for mixed domain usage. 3) Any new stuff people do (e.g. [1], [2]), please use "statistics-enabled". 4) My intent is to make the default values for these attributes be "false". I won't change any default though unless the relative compoent lead has indicated agreement in this thread or elsewhere. But, if you disagree with "false" as the default, please let's use this thread to sort that out, get input from the performance team, etc, so we can have at least a clear understanding of why some uses have 'true'. Jesper, ^^^. That's for WF 8. For the next release I recommend that we also create subsystem-level attributes to hold the default value for the several cases where this setting is only configurable on a per-deployment level. An example would be the jpa subsystem could have a statistics-enabled attribute that drives the setting for all persistence units unless the PU descriptor overrides or the admin overrides using the existing per-deployment attribute. Besides being an aid to usability, having an attribute that ends up in the persistent configuration will also help deal with issues where, for example, the desired default for WildFly is different than the desired default for some future EAP release. The standard configs for the EAP release can just use a different value. [1] https://issues.jboss.org/browse/JBWS-3733 [2] https://issues.jboss.org/browse/WFLY-2453 > Allow enabling/disabling endpoint metrics > ----------------------------------------- > > Key: JBWS-3733 > URL: https://issues.jboss.org/browse/JBWS-3733 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > We need to offer a mechanism for enabling/disabling endpoint metrics. > We should probably have an element/attribute in the container DMR for enabling/disabling the metrics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues December 2013