May 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6305) Add CXF artefacts required by Camel integration

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-6305?page=com.atlassian.jira.plugin.... ] Thomas Diesler closed WFLY-6305. -------------------------------- Fix Version/s: (was: 10.1.0.Final) Resolution: Won't Do > Add CXF artefacts required by Camel integration > ------------------------------------------------ > > Key: WFLY-6305 > URL: https://issues.jboss.org/browse/WFLY-6305 > Project: WildFly > Issue Type: Task > Components: Web Services > Affects Versions: 10.0.0.Final > Reporter: Thomas Diesler > Assignee: Thomas Diesler > > CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1046 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2071) FlowControl: credits are unserialized incorrectly

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2071?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2071. ---------------------------- Resolution: Done Fixed using longToBuffer() in the Message constructor rather than Message(dest, credits) > FlowControl: credits are unserialized incorrectly > ------------------------------------------------- > > Key: JGRP-2071 > URL: https://issues.jboss.org/browse/JGRP-2071 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.9 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 3.6.10 > > > This is a regression in 3.6.9 (3.6.8 is fine). In {{FlowControl.sendCredits()}} and {{.sendCreditRequest()}}, we use Util.objectToBuffer() to serialize the credits, but on the receiver side we use Bits.readLong(), which interprets the {{TYPE_LONG}} sent as first byte as being part of the long. > The reason is an imcomplete backport of from the master branch. The problem does not exist on master. > The faulty commit is {{ac5f507}} on the 3.6 branch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2071) FlowControl: credits are unserialized incorrectly

by Bela Ban (JIRA)

Bela Ban created JGRP-2071: ------------------------------ Summary: FlowControl: credits are unserialized incorrectly Key: JGRP-2071 URL: https://issues.jboss.org/browse/JGRP-2071 Project: JGroups Issue Type: Bug Affects Versions: 3.6.9 Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.6.10 This is a regression in 3.6.9 (3.6.8 is fine). In {{FlowControl.sendCredits()}} and {{.sendCreditRequest()}}, we use Util.objectToBuffer() to serialize the credits, but on the receiver side we use Bits.readLong(), which interprets the {{TYPE_LONG}} sent as first byte as being part of the long. The reason is an imcomplete backport of from the master branch. The problem does not exist on master. The faulty commit is {{ac5f507}} on the 3.6 branch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6660) Allow to dump Artemis journal to file by CLI operation

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-6660?page=com.atlassian.jira.plugin.... ] Miroslav Novak updated WFLY-6660: --------------------------------- Description: For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory. New CLI operation like {{print-journal-date-content}} would print content of journal to a file. It would do the same thing like following Artemis CLI command: {code} .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages {code} This should work only in Admin only mode as dumping journal in run-time is not possible when data changes. was: For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory. New CLI operation like {{print-journal-date-content}} would print content of journal to a file. It would do the same thing like following Artemis CLI command: {code} .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages {code} > Allow to dump Artemis journal to file by CLI operation > ------------------------------------------------------ > > Key: WFLY-6660 > URL: https://issues.jboss.org/browse/WFLY-6660 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > > For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory. > New CLI operation like {{print-journal-date-content}} would print content of journal to a file. > It would do the same thing like following Artemis CLI command: > {code} > .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages > {code} > This should work only in Admin only mode as dumping journal in run-time is not possible when data changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6660) Allow to dump Artemis journal to file by CLI operation

by Miroslav Novak (JIRA)

Miroslav Novak created WFLY-6660: ------------------------------------ Summary: Allow to dump Artemis journal to file by CLI operation Key: WFLY-6660 URL: https://issues.jboss.org/browse/WFLY-6660 Project: WildFly Issue Type: Feature Request Components: JMS Affects Versions: 10.0.0.Final Reporter: Miroslav Novak Assignee: Jeff Mesnil For debugging and investigation purposes it would useful to have CLI operation which would dump content of Artemis journal directory. New CLI operation like {{print-journal-date-content}} would print content of journal to a file. It would do the same thing like following Artemis CLI command: {code} .../activemq-artemis/artemis-distribution/target/apache-artemis-1.3.0-SNAPSHOT-bin/apache-artemis-1.3.0-SNAPSHOT/bin/artemis data print --bindings bindings --journal journal --paging paging --large-messages largemessages {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4747) xercesImpl-2.9.1-jbossas-1.jar is susceptible to CVE-2009-2625 (DoS Attack)

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-4747?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-4747 at 5/30/16 6:04 AM: ------------------------------------------------------------ For the record: https://github.com/victims/victims-cve-db/issues/45 was (Author: ozizka): For the record: https://github.com/victims/victims-cve-db/issues/44 > xercesImpl-2.9.1-jbossas-1.jar is susceptible to CVE-2009-2625 (DoS Attack) > --------------------------------------------------------------------------- > > Key: AS7-4747 > URL: https://issues.jboss.org/browse/AS7-4747 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Arun Neelicattu > Assignee: Jason Greene > Labels: xercesImpl > Fix For: 7.1.2.Final (EAP) > > > The current version of xerces (_xercesImpl-2.9.1-jbossas-1.jar_) is vulnerable to [CVE-2009-2625|https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-2625] > This vulnerability was fixed in xerces versions >= 2.10 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4747) xercesImpl-2.9.1-jbossas-1.jar is susceptible to CVE-2009-2625 (DoS Attack)

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-4747?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-4747: ----------------------------------- For the record: https://github.com/victims/victims-cve-db/issues/44 > xercesImpl-2.9.1-jbossas-1.jar is susceptible to CVE-2009-2625 (DoS Attack) > --------------------------------------------------------------------------- > > Key: AS7-4747 > URL: https://issues.jboss.org/browse/AS7-4747 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Arun Neelicattu > Assignee: Jason Greene > Labels: xercesImpl > Fix For: 7.1.2.Final (EAP) > > > The current version of xerces (_xercesImpl-2.9.1-jbossas-1.jar_) is vulnerable to [CVE-2009-2625|https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-2625] > This vulnerability was fixed in xerces versions >= 2.10 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6626) Add log message indicating disabled <distributable/> flag from web-fragments

by Panagiotis Sotiropoulos (JIRA)

[ https://issues.jboss.org/browse/WFLY-6626?page=com.atlassian.jira.plugin.... ] Panagiotis Sotiropoulos commented on WFLY-6626: ----------------------------------------------- PR : https://github.com/wildfly/wildfly/pull/8939 > Add log message indicating disabled <distributable/> flag from web-fragments > ---------------------------------------------------------------------------- > > Key: WFLY-6626 > URL: https://issues.jboss.org/browse/WFLY-6626 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Aaron Ogburn > Assignee: Stuart Douglas > Attachments: undistributable.war > > > If a web-fragment doesn't have distributable set, then replication is not enabled. This happens silently so it may be confusing to some users that are expecting replication to be enabled when they have set <distributable/> in their WEB-INF/web.xml. > Other third party libraries they included may have web-fragments without distributable set so it'd be nice to log a notification when this happens so that users are easily informed why replication was not enabled as they may have expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6538) https-listener does not support proxy-address-forwarding

by Emond Papegaaij (JIRA)

[ https://issues.jboss.org/browse/WFLY-6538?page=com.atlassian.jira.plugin.... ] Emond Papegaaij commented on WFLY-6538: --------------------------------------- Any news on this issue? The pull request was sent 6 weeks ago, but is still not merged. It would be really nice if this could be fixed before 10.1. > https-listener does not support proxy-address-forwarding > -------------------------------------------------------- > > Key: WFLY-6538 > URL: https://issues.jboss.org/browse/WFLY-6538 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 9.0.2.Final, 10.0.0.Final > Reporter: Emond Papegaaij > Assignee: Tomaz Cerar > > HttpsListenerService explicitly passes false to its superclass for proxyAddressForwarding and certificateForwarding, making it impossible to enable these features. For a security-sensitive application, we need a secure connection from our proxy to WildFly and we need WildFly to respect the headers sent by our proxy. It seems easy to support these options by reading them in HttpsListenerAdd and passing them to HttpsListenerService, which can simply pass them to the super constructor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1320) Unable to create JDBC local datasource without properties on JBoss EAP 7

by ted won (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1320?page=com.atlassian.jira.plugin... ] ted won updated JBJCA-1320: --------------------------- Issue Type: Bug (was: Enhancement) > Unable to create JDBC local datasource without properties on JBoss EAP 7 > ------------------------------------------------------------------------ > > Key: JBJCA-1320 > URL: https://issues.jboss.org/browse/JBJCA-1320 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: WildFly/IronJacamar 1.3.3.Final > Reporter: ted won > Assignee: ted won > Priority: Minor > Attachments: com.msql.tar.gz > > > It's failed with error "IJ031103: At least one connection property must be defined for datasource-class" when it's doing migration from JBoss EAP 6 / WildFly 10 or creating non-XA datasource, using local transactions in JBoss EAP 7. > It should display warning message than throwing error like [WFLY-6198|https://issues.jboss.org/browse/WFLY-6198]. > In case of MySQL datasource classes it's possible to use datasource-class and create non-XA datasource in JBoss EAP 6 and WildFly 10 but EAP 7. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 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

jboss-jira May 2016