December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Serg Pol (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Serg Pol commented on WFLY-9610: -------------------------------- Are these batch threads (max-threads number) used by some other processes (infinispan?) in wildfly 9? Or this max number is just limit of threads of BatchJobs that run in the same time? > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-283: --------------------------- Attachment: openjdk-patch-native-mechs.patch > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > Attachments: openjdk-patch-native-mechs.patch > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6464) JPA 2.2 Support

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6464?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-6464: ------------------------------------ Close pr [https://github.com/wildfly/wildfly/pull/10715] contains initial changes, also need ability to switch between JPA 2.1 + 2.2 api jars. > JPA 2.2 Support > --------------- > > Key: WFLY-6464 > URL: https://issues.jboss.org/browse/WFLY-6464 > Project: WildFly > Issue Type: Sub-task > Components: JPA / Hibernate > Reporter: David Lloyd > Assignee: Scott Marlow > Fix For: 12.0.0.Alpha1 > > > From JPA 2.2 specification appendix section A.1: > {code} > A.1 Maintenance Release Draft > Created document from Java Persistence 2.1 Final Release specification. > The following annotations have been marked @Repeatable: > AssociationOverride > AttributeOverride > Convert > JoinColumn > MapKeyJoinColumn > NamedEntityGraph > NamedNativeQuery > NamedQuery > NamedStoredProcedureQuery > PersistenceContext > PersistenceUnit > PrimaryKeyJoinColumn > SecondaryTable > SqlResultSetMapping > SequenceGenerator > TableGenerator > Added SequenceGenerators and TableGenerators annotations. > Added support for CDI injection into AttributeConverter classes. > Added support for the mapping of the following java.time types: > java.time.LocalDate > java.time.LocalTime > java.time.LocalDateTime > java.time.OffsetTime > java.time.OffsetDateTime > Added default Stream getResultStream() method to Query interface. > Added default Stream<X> getResultStream() method to TypedQuery interface. > Replaced reference to JAR file specification in persistence provider bootstrapping section with more general reference to Java SE service provider requirements. > Updated persistence.xml and orm.xml schemas to 2.2 versions. > Updated Related Documents. > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2242) Narrow set of thrown exceptions in Streamable and Marshaller method signatures

by Paul Ferraro (JIRA)

Paul Ferraro created JGRP-2242: ---------------------------------- Summary: Narrow set of thrown exceptions in Streamable and Marshaller method signatures Key: JGRP-2242 URL: https://issues.jboss.org/browse/JGRP-2242 Project: JGroups Issue Type: Enhancement Affects Versions: 4.0 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 5.0 These methods all throw a generic Exception. Write methods should only need to throw IOException, while read methods should only need to throw IOException and ClassNotFoundException. Original PR, deferred to 5.0, is here: https://github.com/belaban/JGroups/pull/372 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-283: -------------------------------- Problem above was resolved, but currently there is JDK bug which looks currently prevents to use native GSS: In a lot of places in JDK there is *SunNativeProvider.INSTANCE* used, but it is initialized incorrectly - before list of supported GSS mechs is generated, so using this instance will raise exception - not existing mechanism: {code} GSSException: Provider SunNativeGSS does not support mechanism 1.2.840.113554.1.2.2 at java.security.jgss/sun.security.jgss.ProviderList.getMechFactory(ProviderList.java:253) at java.security.jgss/sun.security.jgss.ProviderList.getMechFactory(ProviderList.java:209) at java.security.jgss/sun.security.jgss.GSSManagerImpl.getMechanismContext(GSSManagerImpl.java:234) at java.security.jgss/sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:337) at java.security.jgss/sun.security.jgss.GSSContextImpl.acceptSecContext(GSSContextImpl.java:302) {code} It would be sufficient to change order of SunNativeProvider initializers, but it needs JDK patch. Reported to security-dev(a)openjdk.java.net list and will try to find workaround without JDK modification... > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2179) [DMN Editor] EditableHeaderMetaData DOMElement can span multiple columns

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2179?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-2179. ------------------------------------ Resolution: Done > [DMN Editor] EditableHeaderMetaData DOMElement can span multiple columns > ------------------------------------------------------------------------ > > Key: DROOLS-2179 > URL: https://issues.jboss.org/browse/DROOLS-2179 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > A {{EditableHeaderMetaData}} can span multiple columns. However when the User double-clicks to edit the header the {{DOMElement}} is sized and positioned for the single column in which the User double-clicked. It should span multiple columns if need be. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2179) [DMN Editor] EditableHeaderMetaData DOMElement can span multiple columns

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2179?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2179: ---------------------------------------- See https://github.com/manstis/kie-wb-common/commit/7910ab030a3c28ab2ab1e065b... > [DMN Editor] EditableHeaderMetaData DOMElement can span multiple columns > ------------------------------------------------------------------------ > > Key: DROOLS-2179 > URL: https://issues.jboss.org/browse/DROOLS-2179 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > > A {{EditableHeaderMetaData}} can span multiple columns. However when the User double-clicks to edit the header the {{DOMElement}} is sized and positioned for the single column in which the User double-clicked. It should span multiple columns if need be. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1466) Add configuration option to BASIC mechanism to switch off challenging

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-1466?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on ELY-1466: ---------------------------------- The optional auth RFC also talks about using regular WWW-Authenticate without a 401 response. See section 3.1 for more info. > Add configuration option to BASIC mechanism to switch off challenging > --------------------------------------------------------------------- > > Key: ELY-1466 > URL: https://issues.jboss.org/browse/ELY-1466 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta11 > > > This may be desirable where paired with FORM auth so users can use FORM auth and other clients use BASIC. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3435) Expose capability/requirements to deployments

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3435?page=com.atlassian.jira.plugi... ] Jeff Mesnil reassigned WFCORE-3435: ----------------------------------- Assignee: Jeff Mesnil > Expose capability/requirements to deployments > --------------------------------------------- > > Key: WFCORE-3435 > URL: https://issues.jboss.org/browse/WFCORE-3435 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 3.0.9.Final > Reporter: Bob McWhirter > Assignee: Jeff Mesnil > > For WildFly Swarm, we use a fair amount of ServiceActivators in deployments. > Moving to WF11, we have seen some of our dependencies on Service<T>, such as NamingService.SERVICE_NAME result in deprecation warnings suggesting we move to using CAPABILITY_NAME. From within a ServiceActivator, within a deployment, this appears to not be a possibility. > Filed per [~ctomc] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9615) Upgrade Hibernate Validator to 6.0.6.Final

by Guillaume Smet (JIRA)

Guillaume Smet created WFLY-9615: ------------------------------------ Summary: Upgrade Hibernate Validator to 6.0.6.Final Key: WFLY-9615 URL: https://issues.jboss.org/browse/WFLY-9615 Project: WildFly Issue Type: Component Upgrade Reporter: Guillaume Smet Assignee: Jason Greene We would like to upgrade Hibernate Validator to 6.0.6.Final in WildFly 12. Here is our migration guide: https://developer.jboss.org/wiki/HibernateValidatorMigrationGuide#jive_co... You'll notice that in 6.0.6, we have reintroduced a few APIs that we had removed in the previous versions of 6 for this WF upgrade: we had them deprecated in 5.4 then removed in 6 but as WF is still using 5.3, WF users didn't have any notice of that. That's why we decided to reintroduce them before proposing an upgrade in WildFly. The other APIs removed were marked as experimental and have been superseded by standard features in Bean Validation 2.0 (which is part of Java EE 8). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 December 2017