February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13079) org.eclipse.yasson.internal.Unmarshaller Invalid token=EOF

by Cheng Fang (Jira)

Cheng Fang created WFLY-13079: --------------------------------- Summary: org.eclipse.yasson.internal.Unmarshaller Invalid token=EOF Key: WFLY-13079 URL: https://issues.redhat.com/browse/WFLY-13079 Project: WildFly Issue Type: Bug Components: REST Affects Versions: 19.0.0.Beta2 Reporter: Cheng Fang Assignee: Alessio Soldano {code} 23:30:45,307 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 29) WFLYUT0021: Registered web context: '/numbers-chunk' for server 'default-server' 23:30:45,404 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "numbers-chunk.war" (runtime-name : "numbers-chunk.war") 23:31:00,750 SEVERE [org.eclipse.yasson.internal.Unmarshaller] (default task-1) Invalid token=EOF at (line no=1, column no=0, offset=-1). Expected tokens are: [CURLYOPEN, SQUAREOPEN, STRING, NUMBER, TRUE, FALSE, NULL] {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13072) Support multiple module layers in HostExcludesTestCase

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13072?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFLY-13072: ------------------------------------- > Support multiple module layers in HostExcludesTestCase > ------------------------------------------------------- > > Key: WFLY-13072 > URL: https://issues.redhat.com/browse/WFLY-13072 > Project: WildFly > Issue Type: Task > Components: Management, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 19.0.0.Beta3, 20.0.0.Beta1 > > > When HostExcludesTestCase searches for available extensions it should test in other module locations besides system/layers/base. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13072) Support multiple module layers in HostExcludesTestCase

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13072?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13072: ------------------------------------ Fix Version/s: 19.0.0.Beta3 20.0.0.Beta1 (was: 19.0.0.Beta2) > Support multiple module layers in HostExcludesTestCase > ------------------------------------------------------- > > Key: WFLY-13072 > URL: https://issues.redhat.com/browse/WFLY-13072 > Project: WildFly > Issue Type: Task > Components: Management, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 19.0.0.Beta3, 20.0.0.Beta1 > > > When HostExcludesTestCase searches for available extensions it should test in other module locations besides system/layers/base. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5795) HA JMS Topic Subscriber of Colocated life backup symmetrical 2 nodes cluster violates Publish-Subscribe pattern.

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-5795?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-5795: ----------------------------------- Fix Version/s: (was: 10.x.x TBD) [~ehugonnet] Is this out of date? > HA JMS Topic Subscriber of Colocated life backup symmetrical 2 nodes cluster violates Publish-Subscribe pattern. > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5795 > URL: https://issues.redhat.com/browse/WFLY-5795 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR4 > Environment: 2 node symmetrical colocated life backup cluster (domain mode). Configuration (domain.xml, host.xml) provided as attachment. > Reporter: Michal Sudra > Assignee: Jeff Mesnil > Priority: Major > Attachments: ClusteredTopicTest.java, domain.xml, domain.xml, host-slave.xml, host.xml, host.xml, master.log, slave.log > > > Test Client is producing 10 messages on topic on node 1 and 2 consumers connected to node 1 and the other to node 2 are then consuming the messages. > Expectation: Every consumer receives 10 Messages. > Result of test: Consumer connected to node 1 is only getting every second message. Consumer connected to node 2 is receiving all 10 messages: > Output of test program: > Sent message: This is text message 0 > Sent message: This is text message 1 > Sent message: This is text message 2 > Sent message: This is text message 3 > Sent message: This is text message 4 > Sent message: This is text message 5 > Sent message: This is text message 6 > Sent message: This is text message 7 > Sent message: This is text message 8 > Sent message: This is text message 9 > 0 Recieved message: This is text message 0 from node 0 from java:/jms/topic/ClusterStateTopic > 1 Recieved message: This is text message 2 from node 0 from java:/jms/topic/ClusterStateTopic > 2 Recieved message: This is text message 4 from node 0 from java:/jms/topic/ClusterStateTopic > 3 Recieved message: This is text message 6 from node 0 from java:/jms/topic/ClusterStateTopic > 4 Recieved message: This is text message 8 from node 0 from java:/jms/topic/ClusterStateTopic > 5 error receiving message from node 0 > 6 error receiving message from node 0 > 7 error receiving message from node 0 > 8 error receiving message from node 0 > 9 error receiving message from node 0 > 0 Recieved message: This is text message 0 from node 1 from java:/jms/topic/ClusterStateTopic > 1 Recieved message: This is text message 1 from node 1 from java:/jms/topic/ClusterStateTopic > 2 Recieved message: This is text message 2 from node 1 from java:/jms/topic/ClusterStateTopic > 3 Recieved message: This is text message 3 from node 1 from java:/jms/topic/ClusterStateTopic > 4 Recieved message: This is text message 4 from node 1 from java:/jms/topic/ClusterStateTopic > 5 Recieved message: This is text message 5 from node 1 from java:/jms/topic/ClusterStateTopic > 6 Recieved message: This is text message 6 from node 1 from java:/jms/topic/ClusterStateTopic > 7 Recieved message: This is text message 7 from node 1 from java:/jms/topic/ClusterStateTopic > 8 Recieved message: This is text message 8 from node 1 from java:/jms/topic/ClusterStateTopic > 9 Recieved message: This is text message 9 from node 1 from java:/jms/topic/ClusterStateTopic > The test program is added and the 2 node names are given as parameters for main. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11868) Documentation for Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-11868?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-11868: ------------------------------------ Fix Version/s: 20.0.0.Beta1 (was: 19.0.0.Beta2) > Documentation for Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-11868 > URL: https://issues.redhat.com/browse/WFLY-11868 > Project: WildFly > Issue Type: Feature Request > Components: REST, Security > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > Labels: EAP-CD19 > Fix For: 20.0.0.Beta1 > > > This feature request is about making use of authentication configuration on the client side of the REST deployment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12674) wildfly.jpa.skipquerydetach set to true, will now skip clearing of query results

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12674?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12674: ------------------------------------ Fix Version/s: 20.0.0.Beta1 (was: 19.0.0.Beta2) > wildfly.jpa.skipquerydetach set to true, will now skip clearing of query results > -------------------------------------------------------------------------------- > > Key: WFLY-12674 > URL: https://issues.redhat.com/browse/WFLY-12674 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 20.0.0.Beta1 > > > Introduce wildfly.jpa.skipquerydetach that defaults to false (to wrap query objects with detacher that clears query results when obtained) but could be set to true, for JBoss AS 5/6 compatibility. This could of been part of [WFLY-3674] but was overlooked. > An example of setting wildfly.jpa.skipquerydetach to true, so that the various query detacher will not be used (e.g. underlying query is returned instead of instance of QueryNonTxInvocationDetacher/TypedQueryNonTxInvocationDetacher/StoredProcedureQueryNonTxInvocationDetacher wrapper): > {code} > <property name="wildfly.jpa.skipquerydetach" value="true" /> > {code} > The below reference notes are more for background information but provide the explanation of why the AS5/6 way of detaching loaded entities changed later, to ensure the returned results from Query objects, are detached, instead of the current persistence context at the time of creating the query object, as per feedback below from JPA lead Linda DeMichiel. > [From related JPA expert group discussion|https://download.oracle.com/javaee-archive/jpa-spec.java.net/u...]: > {code} > >>>>> Perhaps a clearer proposal could be: > >>>>> > >>>>> " > >>>>> If the entity manager is invoked outside the scope of a transaction, > >>>>> any entities loaded from the database will > >>>>> immediately become detached at the end of the container level method > >>>>> invocation call (e.g. when the session bean method > >>>>> ends). > >>>>> " > >>>> > >>>> Ah, thanks. That is not the intended semantics. Rather it is that the > >>>> persistence context is created to service the method call that is made > >>>> on the entity manager only. It doesn't have the duration of a business > >>>> method invocation. > >>> > >>> Is it really? > >>> > >> > >> Yes. See also section 3.8.7, which is quite explicit with regard to > >> queries. > >> BTW, these decisions date back to JPA 1.0 (aka EJB 3.0). > > > > My updated proposal for the 7.6.2 wording is: > > > > " > > If the entity manager is invoked outside the scope of a transaction, any entities loaded from the database will > > immediately become detached at the end of the entity manager method call. > > " > OK, sure + "... or query invocation" > {code} > Note that we (JPA expert group) missed Linda's response of "... or query invocation" in the JPA spec update, as the JPA 2.2 spec today states: > {quote} > 7.6.2 Container-managed Transaction-scoped Persistence Context > The application can obtain a container-managed entity manager with transaction-scoped persistence context by injection or direct lookup in the JNDI namespace. The persistence context type for the entity manager is defaulted or defined as PersistenceContextType.TRANSACTION. > A new persistence context begins when the container-managed entity manager is invoked [84] in the scope of an active JTA transaction, and there is no current persistence context already associated with the JTA transaction. The persistence context is created and then associated with the JTA transaction. This association of the persistence context with the JTA transaction is independent of the synchronization type of the persistence context and whether the persistence context has been joined to the transaction. > {quote} > [Some related AS5/6 JPA container code.|https://anonsvn.jboss.org/repos/jbossas/projects/jpa/trunk/impl/src...] which simply cleared the persistence context as we were creating a new Query, for example see: > {code} > public Query createQuery(String ejbqlString) > { > EntityManager em = getEntityManager(); > detachEntitiesIfNoTx(em); > return em.createQuery(ejbqlString); > } > {code} > Also of reference, is from issue description [WFLY-3674]: > {quote} > For compatibility with earlier JBoss application server versions (5.0/6.0), add an extension that allows the persistence context to last until the referencing persistence context is closed. > For example, in a session method that has no active JTA transaction, entities returned, will not cleared from the persistence context, until the session method completes. This extension is only introduced to allow compatibility with older application server versions. > {quote} > [WFLY-12674] is about doing the same for Queries (if wildfly.jpa.skipquerydetach is set to true). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12654) Switch from javax.jws:jsr181-api to jakarta.jws:jakarta.jws-api

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12654?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12654: ------------------------------------ Fix Version/s: 20.0.0.Beta1 (was: 19.0.0.Beta2) > Switch from javax.jws:jsr181-api to jakarta.jws:jakarta.jws-api > --------------------------------------------------------------- > > Key: WFLY-12654 > URL: https://issues.redhat.com/browse/WFLY-12654 > Project: WildFly > Issue Type: Task > Components: Web Services > Reporter: Scott Marlow > Assignee: Jim Ma > Priority: Major > Fix For: 20.0.0.Beta1 > > > Update WildFly to use jakarta.jws:jakarta.jws-api from https://github.com/eclipse-ee4j/jws-api, note that version 2.1 is not yet available as mentioned on [https://github.com/eclipse-ee4j/jws-api/issues/48]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12589) Add way for Hibernate bytecode transformer to ignore certain class packages or class names

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12589?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12589: ------------------------------------ Fix Version/s: 20.0.0.Beta1 (was: 19.0.0.Beta2) > Add way for Hibernate bytecode transformer to ignore certain class packages or class names > ------------------------------------------------------------------------------------------ > > Key: WFLY-12589 > URL: https://issues.redhat.com/browse/WFLY-12589 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 20.0.0.Beta1 > > > Add Hibernate51CompatibilityTransformer.excludeClasses system property for specifying comma separated list of classes or class packages to exclude. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12537) Incoming RunAsPrincipal is not being propagated to an unsecured EJB

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12537?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12537: ------------------------------------ Fix Version/s: 20.0.0.Beta1 (was: 19.0.0.Beta2) > Incoming RunAsPrincipal is not being propagated to an unsecured EJB > ------------------------------------------------------------------- > > Key: WFLY-12537 > URL: https://issues.redhat.com/browse/WFLY-12537 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > Fix For: 20.0.0.Beta1 > > > This is a follow-up on WFLY-11604. When Elytron is activated, run-as-principal identity is not being propagated the same way it was for legacy. For JBEAP-9744, we updated EJBContext.getCallerPrincipal() so that when called from an unsecured bean with no incoming runas identity, an `anonymous` principal will be returned. The issue WFLY-11604 discovered that EJBContext.getCallerPrincipal is returning 'anonymous' when called on an unsecured EJB even when incoming RunAsPrincipal identity should have been propagated. This issue is to see whether this can be fixed without breaking the fix for JBEAP-9744. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12516) EJBContext principal is not popped back after invoking another EJB using a different Security Domain

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12516?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12516: ------------------------------------ Fix Version/s: 20.0.0.Beta1 (was: 19.0.0.Beta2) > EJBContext principal is not popped back after invoking another EJB using a different Security Domain > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-12516 > URL: https://issues.redhat.com/browse/WFLY-12516 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 February 2020