October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-654) Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout in SSLSessionContext.

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-654?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev updated ELY-654: ------------------------------ Summary: Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout in SSLSessionContext. (was: Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout on SSLSessionContext.) > Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout in SSLSessionContext. > ------------------------------------------------------------------------------------------------------------------------ > > Key: ELY-654 > URL: https://issues.jboss.org/browse/ELY-654 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.1.0.Beta10 > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > > Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout on SSLSessionContext. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-654) Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout on SSLSessionContext.

by Ilia Vassilev (JIRA)

Ilia Vassilev created ELY-654: --------------------------------- Summary: Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout on SSLSessionContext. Key: ELY-654 URL: https://issues.jboss.org/browse/ELY-654 Project: WildFly Elytron Issue Type: Bug Components: SSL Affects Versions: 1.1.0.Beta10 Reporter: Ilia Vassilev Assignee: Darran Lofthouse Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout on SSLSessionContext. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-654) Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout on SSLSessionContext.

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-654?page=com.atlassian.jira.plugin.sy... ] Ilia Vassilev reassigned ELY-654: --------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout on SSLSessionContext. > ------------------------------------------------------------------------------------------------------------------------ > > Key: ELY-654 > URL: https://issues.jboss.org/browse/ELY-654 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.1.0.Beta10 > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > > Ensure that negative values are converted to zero when setting sessionCacheSize and sessionTimeout on SSLSessionContext. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7111) Distributable web applications cause Infinispan exceptions when Elytron is used

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-7111?page=com.atlassian.jira.plugin.... ] Pedro Igor reassigned WFLY-7111: -------------------------------- Assignee: Pedro Igor (was: Darran Lofthouse) > Distributable web applications cause Infinispan exceptions when Elytron is used > ------------------------------------------------------------------------------- > > Key: WFLY-7111 > URL: https://issues.jboss.org/browse/WFLY-7111 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Pedro Igor > Priority: Blocker > > When a distributable secured web application mapped to Elytron domain is deployed to EAP and accessed. It throws intermittently {{org.infinispan.util.concurrent.TimeoutException}} > *Expected behavior:* > Distributable applications should be accessible without exceptions when Elytron is used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1857) Invalid operation shouldn't be completed at all

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1857?page=com.atlassian.jira.plugi... ] Jean-Francois Denise edited comment on WFCORE-1857 at 10/7/16 8:50 AM: ----------------------------------------------------------------------- The elytron subsystem is not present in JBEAP-6143 although the operation is completed. was (Author: jdenise): The elytron subsystem is not present in JBEAP-6134 although the operation is completed. > Invalid operation shouldn't be completed at all > ----------------------------------------------- > > Key: WFCORE-1857 > URL: https://issues.jboss.org/browse/WFCORE-1857 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > When an operation doesn't exist, the character ')' is added by completion although nothing should be proposed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1857) Invalid operation shouldn't be completed at all

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1857?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-1857: ---------------------------------------------- The elytron subsystem is not present in JBEAP-6134 although the operation is completed. > Invalid operation shouldn't be completed at all > ----------------------------------------------- > > Key: WFCORE-1857 > URL: https://issues.jboss.org/browse/WFCORE-1857 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > When an operation doesn't exist, the character ')' is added by completion although nothing should be proposed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1857) Invalid operation shouldn't be completed at all

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-1857: -------------------------------------------- Summary: Invalid operation shouldn't be completed at all Key: WFCORE-1857 URL: https://issues.jboss.org/browse/WFCORE-1857 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise When an operation doesn't exist, the character ')' is added by completion although nothing should be proposed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7274) Undertow request failed HttpServerExchange due to replication timeout

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7274?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-6343 to WFLY-7274: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7274 (was: JBEAP-6343) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR5) > Undertow request failed HttpServerExchange due to replication timeout > --------------------------------------------------------------------- > > Key: WFLY-7274 > URL: https://issues.jboss.org/browse/WFLY-7274 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Occured on server during eap-7x-failover-ejb-ejbservlet-shutdown-dist-async scenario. > Server log stacktrace: > {code} > 15:29:15,717 WARN [org.jboss.weld.Servlet] (default task-104) WELD-000717: Unable to deactivate context org.jboss.weld.context.http.HttpSessionContextImpl@351bc717 when destroying request HttpServletRequestImpl [ GET /clusterbench/ejbservlet ] > [JBossINF] 15:29:15,718 ERROR [io.undertow.request] (default task-104) UT005071: Undertow request failed HttpServerExchange{ GET /clusterbench/ejbservlet request {Cookie=[$Version=0; JSESSIONID=YiEdTzoqqzKiWxjI1VqEQNz8BB0id8L6GKrA1Uix.dev215; $Path=/clusterbench], Content-Length=[0], User-Agent=[Jakarta Commons-HttpClient/3.1], Host=[dev220:8080]} response {Set-Cookie=[JSESSIONID=YiEdTzoqqzKiWxjI1VqEQNz8BB0id8L6GKrA1Uix.dev213; path=/clusterbench], Content-Type=[text/html;charset=UTF-8], Content-Length=[80], Date=[Wed, 21 Sep 2016 19:29:00 GMT]}}: org.infinispan.util.concurrent.TimeoutException: Replication timeout for dev213 > [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:801) > [JBossINF] at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$1(JGroupsTransport.java:642) > [JBossINF] at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) > [JBossINF] at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) > [JBossINF] at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) > [JBossINF] at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962) > [JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47) > [JBossINF] at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16) > [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > [JBossINF] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [JBossINF] at java.lang.Thread.run(Thread.java:745) > {code} > Followed by: > {code} > 15:29:15,720 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (remote-thread--p7-t17) ISPN000136: Error executing command LockControlCommand, writing keys []: org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on SessionCreationMetaDataKey(bprpzS1jzQGMjU9vmr1uwUvsN0ehaPpWtpRQYUhA) in behalf of transaction GlobalTransaction:<dev213>:108660:remote. Current owner GlobalTransaction:<dev213>:90576:remote. > [JBossINF] at org.infinispan.util.concurrent.locks.impl.DefaultPendingLockManager.timeout(DefaultPendingLockManager.java:261) > ... > {code} > or: > {code} > 15:29:19,720 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-54) ISPN000136: Error executing command GetKeyValueCommand, writing keys []: org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on SessionCreationMetaDataKey(bprpzS1jzQGMjU9vmr1uwUvsN0ehaPpWtpRQYUhA) in behalf of transaction GlobalTransaction:<dev215>:112942:local. Current owner GlobalTransaction:<dev213>:90576:remote. > [JBossINF] at org.infinispan.util.concurrent.locks.impl.DefaultPendingLockManager.timeout(DefaultPendingLockManager.java:261) > ... > {code} > Server logs: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1321) Prefer https over http for absolute links on drools.org, optaplanner.org, jbpm.org and kiegroup.org

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1321?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-1321: ------------------------------------- Description: Motivation: 1) Chrome has "a long-term plan to mark all HTTP sites as non-secure." https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html 2) SEO: Google/Bing penalize website (lower ranking) that use http or mix http and https. To do: - Change all absolute links on our websites _and in our user manuals_ that lead to redhat.com, jboss.org, drools.org, optaplanner.org, jbpm.org and kiegroup.org to https. - This includes canonical meta elements - This includes tabzilla.js/.css loading of images (those actually give us the mixed https and http errors in chrome's inspect tooling if you go to https://www.drools.org today) - This does not include external links, such as to wikipedia etc. Keep an eye out on google webmaster tools to verify this doesn't introduce broken links. Exceptions: - ci.optaplanner.org must be on http, because those sites don't work over https... Note: I've asked eng-ops to do ssl monitoring of our websites. So basically no risk of out of date certifications etc. was: Motivation: 1) Chrome has "a long-term plan to mark all HTTP sites as non-secure." https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html 2) SEO: Google/Bing penalize website (lower ranking) that use http or mix http and https. To do: - Change all absolute links on our websites _and in our user manuals_ that lead to redhat.com, jboss.org, drools.org, optaplanner.org, jbpm.org and kiegroup.org to https. - This includes canonical meta elements - This includes tabzilla.js/.css loading of images (those actually give us the mixed https and http errors in chrome's inspect tooling if you go to https://www.drools.org today) - This does not include external links, such as to wikipedia etc. Keep an eye out on google webmaster tools to verify this doesn't introduce broken links. Exceptions: - ci.optaplanner.org must be on http, because those sites don't work over https... > Prefer https over http for absolute links on drools.org, optaplanner.org, jbpm.org and kiegroup.org > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1321 > URL: https://issues.jboss.org/browse/DROOLS-1321 > Project: Drools > Issue Type: Task > Components: build > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > > Motivation: > 1) Chrome has "a long-term plan to mark all HTTP sites as non-secure." > https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html > 2) SEO: Google/Bing penalize website (lower ranking) that use http or mix http and https. > To do: > - Change all absolute links on our websites _and in our user manuals_ that lead to redhat.com, jboss.org, drools.org, optaplanner.org, jbpm.org and kiegroup.org to https. > - This includes canonical meta elements > - This includes tabzilla.js/.css loading of images (those actually give us the mixed https and http errors in chrome's inspect tooling if you go to https://www.drools.org today) > - This does not include external links, such as to wikipedia etc. > Keep an eye out on google webmaster tools to verify this doesn't introduce broken links. > Exceptions: > - ci.optaplanner.org must be on http, because those sites don't work over https... > Note: I've asked eng-ops to do ssl monitoring of our websites. So basically no risk of out of date certifications etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1321) Prefer https over http for absolute links on drools.org, optaplanner.org, jbpm.org and kiegroup.org

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1321?page=com.atlassian.jira.plugi... ] Geoffrey De Smet edited comment on DROOLS-1321 at 10/7/16 7:04 AM: ------------------------------------------------------------------- I've already done the change for optaplanner.org: http://github.com/droolsjbpm/optaplanner-website/commit/3b25c74d6 http://github.com/droolsjbpm/optaplanner/commit/77ef50f00 Michael, if you can do similar changes for the other websites and user manuals, that would be great :) was (Author: ge0ffrey): I've already done the change for optaplanner.org: http://github.com/droolsjbpm/optaplanner-website/commit/3b25c74d6 Michael, if you can do similar changes for the other websites and user manuals, that would be great :) > Prefer https over http for absolute links on drools.org, optaplanner.org, jbpm.org and kiegroup.org > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1321 > URL: https://issues.jboss.org/browse/DROOLS-1321 > Project: Drools > Issue Type: Task > Components: build > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > > Motivation: > 1) Chrome has "a long-term plan to mark all HTTP sites as non-secure." > https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html > 2) SEO: Google/Bing penalize website (lower ranking) that use http or mix http and https. > To do: > - Change all absolute links on our websites _and in our user manuals_ that lead to redhat.com, jboss.org, drools.org, optaplanner.org, jbpm.org and kiegroup.org to https. > - This includes canonical meta elements > - This includes tabzilla.js/.css loading of images (those actually give us the mixed https and http errors in chrome's inspect tooling if you go to https://www.drools.org today) > - This does not include external links, such as to wikipedia etc. > Keep an eye out on google webmaster tools to verify this doesn't introduce broken links. > Exceptions: > - ci.optaplanner.org must be on http, because those sites don't work over https... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 2016