October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2378) Re-enable StatefulWithXPCFailoverTestCase

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-2378?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-2378: ------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/5357) > Re-enable StatefulWithXPCFailoverTestCase > ----------------------------------------- > > Key: WFLY-2378 > URL: https://issues.jboss.org/browse/WFLY-2378 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > So I don't forget... -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2391) Wildfly caches content in exploded mode, breaking developer productivity

by Chris R. (JIRA)

[ https://issues.jboss.org/browse/WFLY-2391?page=com.atlassian.jira.plugin.... ] Chris R. edited comment on WFLY-2391 at 10/29/13 10:34 AM: ----------------------------------------------------------- EDIT: I removed caching from servlet container, deploying is now possible I removed: <buffer-cache name="default" buffer-size="1024" buffers-per-region="1024" max-regions="10"/> I'm unable to deploy my projects now: 11:27:20,808 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "foo_frontend.war")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => ["jboss.deployment.unit.\"foo_frontend.war\".INSTALL"], "Services that may be the cause:" => [ "jboss.remoting.remotingConnectorInfoService.http-remoting-connector", "jboss.undertow.bufferCache.default" ] }} was (Author: goot): I removed <buffer-cache name="default" buffer-size="1024" buffers-per-region="1024" max-regions="10"/> I'm unable to deploy my projects now: 11:27:20,808 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "foo_frontend.war")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => { "Services that were unable to start:" => ["jboss.deployment.unit.\"foo_frontend.war\".INSTALL"], "Services that may be the cause:" => [ "jboss.remoting.remotingConnectorInfoService.http-remoting-connector", "jboss.undertow.bufferCache.default" ] }} > Wildfly caches content in exploded mode, breaking developer productivity > ------------------------------------------------------------------------ > > Key: WFLY-2391 > URL: https://issues.jboss.org/browse/WFLY-2391 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Beta1 > Environment: MacOSX with JBossTools 4.1.1.Beta1 > Reporter: Xavier Coulon > Assignee: Stuart Douglas > Attachments: jboss-as-kitchensink-html5-mobile.war.zip > > > While I was building a sample application with JBoss Tools 4.1.1.beta1 on WildFly 8.0.Beta1, I noticed that after a few minutes (or a few browser requests), the content of my index.html file seemed to be cached by the server, although I used the "exploded content" deployment mode (since I published the content using the WildFly Server Adapter in JBoss Tools). > > I checked the actual content of the index.html in the deployments folder and it contained the latest changes, which means that the JBoss Tools Server Adapter is doing its job well ;-) > I also tried to edit the index.html file directly in the deployments folder, and once again, I got no update in both Chrome and Firefox browsers. > > I checked in the "Network" tab of the browsers and could see that the server response for the index.html page had a "200 OK" status, which means that there's no browser caching involved. > I tried to get the index.html page with cUrl and got the same old version, which definitely excludes a browser caching issue. > At the end of the dat, this means that after a few changes, my browsers keep getting an old version of the deployed resources, which in turns means that I have to stop and restart the server to get the new content, and this is pretty bad in term of dev productivity. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1721) AUTH and ENCRYPT protocols configured with plain text passwords

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/JGRP-1721?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on JGRP-1721: --------------------------------------- Protocol property values in the jgroups subsystem support expressions, and therefore transitively support ${VAULT::...} expansion > AUTH and ENCRYPT protocols configured with plain text passwords > --------------------------------------------------------------- > > Key: JGRP-1721 > URL: https://issues.jboss.org/browse/JGRP-1721 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4 > Reporter: Martin Gencur > Assignee: Bela Ban > Labels: jdg620_dm > Fix For: 3.5 > > > The following parameters of AUTH protocol are stored as plain text: > * keystore_password > The following parameters of ENCRYPT protocol are stored as plain text: > * store_password > * key_password > Example: > {code} > <ENCRYPT key_store_name="defaultStore.keystore" store_password="changeit" alias="myKey"/> > {code} > Requirements for storing passwords: https://docspace.corp.redhat.com/docs/DOC-131628 -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1723) Corrupted input stream on STATE exchange

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1723?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1723. ---------------------------- Resolution: Done > Corrupted input stream on STATE exchange > ---------------------------------------- > > Key: JGRP-1723 > URL: https://issues.jboss.org/browse/JGRP-1723 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.3.4, 3.4 > Environment: java7u25 > Reporter: Mathieu Bernatet > Assignee: Bela Ban > Fix For: 3.4.1, 3.5 > > Attachments: corruptedStreamOnStateExchange.zip > > > Using the pbcast.STATE state transfer protocol with a high volume of data, the receiver member on setState seem to get a corrupted input stream. > I was able to reproduce this issue with a simple project in which the data get corrupted from the 8192th byte. So it may be related to frag size with default value of 8192. We get this bug either with FRAG or FRAG2. > Related discussion on the mailing list could be found here : http://jgroups.1086181.n5.nabble.com/Corrupted-input-stream-on-STATE-exch... -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1723) Corrupted input stream on STATE exchange

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1723?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1723: --------------------------- Fix Version/s: 3.4.1 > Corrupted input stream on STATE exchange > ---------------------------------------- > > Key: JGRP-1723 > URL: https://issues.jboss.org/browse/JGRP-1723 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.3.4, 3.4 > Environment: java7u25 > Reporter: Mathieu Bernatet > Assignee: Bela Ban > Fix For: 3.4.1, 3.5 > > Attachments: corruptedStreamOnStateExchange.zip > > > Using the pbcast.STATE state transfer protocol with a high volume of data, the receiver member on setState seem to get a corrupted input stream. > I was able to reproduce this issue with a simple project in which the data get corrupted from the 8192th byte. So it may be related to frag size with default value of 8192. We get this bug either with FRAG or FRAG2. > Related discussion on the mailing list could be found here : http://jgroups.1086181.n5.nabble.com/Corrupted-input-stream-on-STATE-exch... -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1723) Corrupted input stream on STATE exchange

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1723?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1723: -------------------------------- Re STATE_SOCK: if you use {{readFully()}} instead of {{read()}}, STATE_SOCK works as well. Tested your program with STATE_TRANSFER, STATE and STATE_SOCK and all 3 work. Note that it would make sense to wrap the output stream in a BufferedOutputStream, or else writing the length of the buffer (4 bytes) results in 4 messages being sent. > Corrupted input stream on STATE exchange > ---------------------------------------- > > Key: JGRP-1723 > URL: https://issues.jboss.org/browse/JGRP-1723 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.3.4, 3.4 > Environment: java7u25 > Reporter: Mathieu Bernatet > Assignee: Bela Ban > Fix For: 3.5 > > Attachments: corruptedStreamOnStateExchange.zip > > > Using the pbcast.STATE state transfer protocol with a high volume of data, the receiver member on setState seem to get a corrupted input stream. > I was able to reproduce this issue with a simple project in which the data get corrupted from the 8192th byte. So it may be related to frag size with default value of 8192. We get this bug either with FRAG or FRAG2. > Related discussion on the mailing list could be found here : http://jgroups.1086181.n5.nabble.com/Corrupted-input-stream-on-STATE-exch... -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2173) Get subsystem test framework working with AS 7.2.0 legacy controller

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2173?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2173: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> made a comment on [bug 1015245|https://bugzilla.redhat.com/show_bug.cgi?id=1015245] Verified on EAP 6.2.0.ER6. > Get subsystem test framework working with AS 7.2.0 legacy controller > -------------------------------------------------------------------- > > Key: WFLY-2173 > URL: https://issues.jboss.org/browse/WFLY-2173 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.CR1 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2185) Get core model test framework working with 7.2.0.Final legacy controller

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2185?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2185: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> made a comment on [bug 1015245|https://bugzilla.redhat.com/show_bug.cgi?id=1015245] Verified on EAP 6.2.0.ER6. > Get core model test framework working with 7.2.0.Final legacy controller > ------------------------------------------------------------------------ > > Key: WFLY-2185 > URL: https://issues.jboss.org/browse/WFLY-2185 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2185) Get core model test framework working with 7.2.0.Final legacy controller

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2185?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2185: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1015245|https://bugzilla.redhat.com/show_bug.cgi?id=1015245] from ON_QA to VERIFIED > Get core model test framework working with 7.2.0.Final legacy controller > ------------------------------------------------------------------------ > > Key: WFLY-2185 > URL: https://issues.jboss.org/browse/WFLY-2185 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2173) Get subsystem test framework working with AS 7.2.0 legacy controller

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2173?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2173: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1015245|https://bugzilla.redhat.com/show_bug.cgi?id=1015245] from ON_QA to VERIFIED > Get subsystem test framework working with AS 7.2.0 legacy controller > -------------------------------------------------------------------- > > Key: WFLY-2173 > URL: https://issues.jboss.org/browse/WFLY-2173 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.CR1 > > -- 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

12 years, 8 months

1
0
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 October 2013