June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10618) [GSS](7.1.z) Problem with @Schedule and daylight-saving time

by Jörg Bäsner (JIRA)

Jörg Bäsner created WFLY-10618: ---------------------------------- Summary: [GSS](7.1.z) Problem with @Schedule and daylight-saving time Key: WFLY-10618 URL: https://issues.jboss.org/browse/WFLY-10618 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 12.0.0.Final Reporter: Jörg Bäsner Assignee: Yeray Borges Priority: Critical Fix For: 14.0.0.CR1 The method anotated with @Schedule is executed repeatedly just before entering the day of daylight-saving time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9420) Cluster partitions can take up to cca 2 minutes to merge with TCP stack

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9420?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-9420: -------------------------------------- No improvement even in 4.0.12.Final which brought MERGE3 fixes. > Cluster partitions can take up to cca 2 minutes to merge with TCP stack > ----------------------------------------------------------------------- > > Key: WFLY-9420 > URL: https://issues.jboss.org/browse/WFLY-9420 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: partition_handling > > Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. > The info sender interval is up to 45 seconds > {code:java} > public long nextInterval() { > return Math.max(min_interval, Util.random(max_interval) + max_interval/2); > } > {code} > and the view consistency checker interval is 48 seconds > {code:java} > protected long computeCheckInterval() { > return (long)(max_interval * 1.6); > } > {code} > which depending on the timing seem to take significant amount of time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9420) Cluster partitions can take up to cca 2 minutes to merge with TCP stack

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9420?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9420: --------------------------------- Summary: Cluster partitions can take up to cca 2 minutes to merge with TCP stack (was: Cluster partitions can take up to cca 2 minutes to merge) > Cluster partitions can take up to cca 2 minutes to merge with TCP stack > ----------------------------------------------------------------------- > > Key: WFLY-9420 > URL: https://issues.jboss.org/browse/WFLY-9420 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Labels: partition_handling > > Using the {{MERGE3}} protocol, it can take significantly longer than {{max_interval}} for merge to happen. > The info sender interval is up to 45 seconds > {code:java} > public long nextInterval() { > return Math.max(min_interval, Util.random(max_interval) + max_interval/2); > } > {code} > and the view consistency checker interval is 48 seconds > {code:java} > protected long computeCheckInterval() { > return (long)(max_interval * 1.6); > } > {code} > which depending on the timing seem to take significant amount of time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1582) Support hex encoding in jdbc-realm for elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1582?page=com.atlassian.jira.plugin.s... ] Jan Kalina updated ELY-1582: ---------------------------- Summary: Support hex encoding in jdbc-realm for elytron (was: [GSS](7.2) Support hex encoding in jdbc-realm for elytron) > Support hex encoding in jdbc-realm for elytron > ---------------------------------------------- > > Key: ELY-1582 > URL: https://issues.jboss.org/browse/ELY-1582 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Realms > Affects Versions: 1.3.2.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Labels: elytron > Fix For: 1.4.0.CR1 > > > Old database login-module can be configured passing the attribute {{hashEncoding}}, for example: > {code:xml} > <login-module code="Database" flag="required"> > <module-option name="dsJndiName" value="java:jboss/datasources/ExampleDS"/> > <module-option name="principalsQuery" value="SELECT password FROM User WHERE username = ?"/> > <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM User WHERE username = ?"/> > <module-option name="hashAlgorithm" value="SHA-1"/> > <module-option name="hashEncoding" value="hex"/> > <module-option name="hashCharset" value="UTF-8"/> > </login-module> > {code} > Currently jdbc-realm in elytron only uses base64 encoding if hash is stored in a text column. This way the migration is more complicated cos the password hash is not valid changing from old security system to elytron. > Think also about the charset attribute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3832) Support hex encoding in jdbc-realm for elytron

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3832?page=com.atlassian.jira.plugi... ] Jan Kalina updated WFCORE-3832: ------------------------------- Summary: Support hex encoding in jdbc-realm for elytron (was: [GSS](7.2) Support hex encoding in jdbc-realm for elytron) > Support hex encoding in jdbc-realm for elytron > ---------------------------------------------- > > Key: WFCORE-3832 > URL: https://issues.jboss.org/browse/WFCORE-3832 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 5.0.0.Alpha7 > Reporter: Jan Kalina > Assignee: Jan Kalina > Labels: elytron > > Old database login-module can be configured passing the attribute {{hashEncoding}}, for example: > {code:xml} > <login-module code="Database" flag="required"> > <module-option name="dsJndiName" value="java:jboss/datasources/ExampleDS"/> > <module-option name="principalsQuery" value="SELECT password FROM User WHERE username = ?"/> > <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM User WHERE username = ?"/> > <module-option name="hashAlgorithm" value="SHA-1"/> > <module-option name="hashEncoding" value="hex"/> > <module-option name="hashCharset" value="UTF-8"/> > </login-module> > {code} > Currently jdbc-realm in elytron only uses base64 encoding if hash is stored in a text column. This way the migration is more complicated cos the password hash is not valid changing from old security system to elytron. > Think also about the charset attribute. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10611) Missing subsystem component to use a custom audit endpoint

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-10611?page=com.atlassian.jira.plugin... ] Jan Kalina updated WFLY-10611: ------------------------------ Summary: Missing subsystem component to use a custom audit endpoint (was: [GSS](7.1.z) Missing subsystem component to use a custom audit endpoint) > Missing subsystem component to use a custom audit endpoint > ---------------------------------------------------------- > > Key: WFLY-10611 > URL: https://issues.jboss.org/browse/WFLY-10611 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 13.0.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > Elytron has the ability to create custom audit endpoints to develop your own audit logs. Nevertheless there is no configuration under the {{subsystem=elytron}} to configure a custom audit class (something like {{subsystem=elytron/custom-audit-log=example:add(...}} is needed). > Feature implementation is in WFCORE-3819, this issue is for tests and docs into wildfly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3819) Missing subsystem component to use a custom audit endpoint

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3819?page=com.atlassian.jira.plugi... ] Jan Kalina updated WFCORE-3819: ------------------------------- Summary: Missing subsystem component to use a custom audit endpoint (was: [GSS](7.1.z) Missing subsystem component to use a custom audit endpoint) > Missing subsystem component to use a custom audit endpoint > ---------------------------------------------------------- > > Key: WFCORE-3819 > URL: https://issues.jboss.org/browse/WFCORE-3819 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 5.0.0.Alpha7 > Reporter: Jan Kalina > Assignee: Jan Kalina > > Elytron has the ability to create custom audit endpoints to develop your own audit logs. Nevertheless there is no configuration under the {{subsystem=elytron}} to configure a custom audit class (something like {{subsystem=elytron/custom-audit-log=example:add(...}} is needed). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10230) Premature end of file if PathParam and PUT/POST are used together

by Marek Marusic (JIRA)

[ https://issues.jboss.org/browse/WFLY-10230?page=com.atlassian.jira.plugin... ] Marek Marusic commented on WFLY-10230: -------------------------------------- I'm not able to reproduce this either on the wildfly 11/12/13. Moreover, I used different versions of Resteasy with no luck. [~raytucson] could you please provide more info about this issue please? What version of the Resteasy do you use? How do you send the PUT request? Does the xml contain any special characters? Thank you in advance. > Premature end of file if PathParam and PUT/POST are used together > ----------------------------------------------------------------- > > Key: WFLY-10230 > URL: https://issues.jboss.org/browse/WFLY-10230 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 11.0.0.Final > Reporter: Ray Ramos > Assignee: Marek Marusic > > The below fails with "Premature End of File". It is a PUT with a PathParam and a JAXB serializeable entity. > {code:java} > @PUT > @Path("{tenant}") > @Consumes(MediaType.APPLICATION_XML) > public void upsert(@PathParam("tenant") String tenant, DataTransferModel model) > {code} > {noformat} > 2:58:03,715 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-2) RESTEASY002005: Failed executing PUT /gateway/tenant: org.jboss.resteasy.plugins.providers.jaxb.JAXBUnmarshalException: javax.xml.bind.UnmarshalException > - with linked exception: > [org.xml.sax.SAXParseException; Premature end of file.] > at org.jboss.resteasy.plugins.providers.jaxb.AbstractJAXBProvider.readFrom(AbstractJAXBProvider.java:136) > at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.readFrom(AbstractReaderInterceptorContext.java:66) > at org.jboss.resteasy.core.interception.ServerReaderInterceptorContext.readFrom(ServerReaderInterceptorContext.java:61) > at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.proceed(AbstractReaderInterceptorContext.java:56) > at org.jboss.resteasy.security.doseta.DigitalVerificationInterceptor.aroundReadFrom(DigitalVerificationInterceptor.java:36) > at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.proceed(AbstractReaderInterceptorContext.java:59) > at org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:151) > at org.jboss.resteasy.core.MethodInjectorImpl.injectArguments(MethodInjectorImpl.java:92) > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:115) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:406) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:213) > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:228) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) > {noformat} > However, if you remove the PathParam, it works. > {code:java} > @PUT > @Path("tenant") > @Consumes(MediaType.APPLICATION_XML) > public void upsert(DataTransferModel model) > {code} > I tried swapping the order of the parameters and I get a "Stream Closed" exception instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10611) [GSS](7.1.z) Missing subsystem component to use a custom audit endpoint

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-10611?page=com.atlassian.jira.plugin... ] Jan Kalina updated WFLY-10611: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/11367 (was: https://github.com/wildfly/wildfly-core/pull/3285) > [GSS](7.1.z) Missing subsystem component to use a custom audit endpoint > ----------------------------------------------------------------------- > > Key: WFLY-10611 > URL: https://issues.jboss.org/browse/WFLY-10611 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 13.0.0.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > > Elytron has the ability to create custom audit endpoints to develop your own audit logs. Nevertheless there is no configuration under the {{subsystem=elytron}} to configure a custom audit class (something like {{subsystem=elytron/custom-audit-log=example:add(...}} is needed). > Feature implementation is in WFCORE-3819, this issue is for tests and docs into wildfly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-310) Istio Upstream Installer 0.8.0 bug

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-310?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo moved KIALI-1016 to SWSQE-310: ------------------------------------------------------ Project: Kiali QE (was: Kiali) Key: SWSQE-310 (was: KIALI-1016) Issue Type: Task (was: Bug) Workflow: GIT Pull Request workflow (was: SWS Workflow) > Istio Upstream Installer 0.8.0 bug > ---------------------------------- > > Key: SWSQE-310 > URL: https://issues.jboss.org/browse/SWSQE-310 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Track changes on the PR -https://github.com/istio/istio/pull/6144 > This PR is going to fix Istio 0.8.0 upstream installer -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 June 2018