January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3512) EJBs can't inherit a JDK8 default method when default implementation is in a third interface

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3512?page=com.atlassian.jira.plugi... ] Stuart Douglas moved WFLY-9680 to WFCORE-3512: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-3512 (was: WFLY-9680) Component/s: Server (was: EJB) Affects Version/s: (was: 10.1.0.Final) (was: 11.0.0.Final) > EJBs can't inherit a JDK8 default method when default implementation is in a third interface > -------------------------------------------------------------------------------------------- > > Key: WFCORE-3512 > URL: https://issues.jboss.org/browse/WFCORE-3512 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Daniel Bildhauer > Assignee: Stuart Douglas > Attachments: ejb-in-ear.zip, wildfly-ejb-in-ear-ear.ear > > > Given the following class/interface inheritance structure, the interface method doMagic could not be called from a remote view, even if there is a default implementation as given in the mixin interface. A local call works, but the remote call fails with a message like > {code} > org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) > {code} > Example code: > {code} > @Remote > interface MyEJBInterface { > void doMagic(); > } > interface MyEJBMixin extends MyEJBInterface { > default void doMagic() { .... } > } > @Stateless > class MyEJBBean extends MyEJBMixin { > } > {code} > The problem is inside the fix for WFLY-4354 bug, which checks only for the default method implementation in the interface declaring the method the first time but not in other interfaces. > A example is attached and I will submitt a pull request with a fix. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9666) ClassLoader leak in org.jboss.el.cache.FactoryFinderCache (Wildfly 11)

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9666?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-9666: -------------------------------------- It should work fine for EAR deployments, I think the real issue is the ordering. If shutdown causes EL to be used at all then the ClassLoader can be re-added to the cache. [~brunojcm] do you have a simple reproducer we can use? > ClassLoader leak in org.jboss.el.cache.FactoryFinderCache (Wildfly 11) > ---------------------------------------------------------------------- > > Key: WFLY-9666 > URL: https://issues.jboss.org/browse/WFLY-9666 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 11.0.0.Final > Environment: macOS > Reporter: Bruno Medeiros > Assignee: Stuart Douglas > Priority: Critical > Attachments: Screen Shot 2018-01-14 at 19.32.10.png > > > I was investigating why my class loader was leaking and after fixing all the problems within my application classes I got the leak shown in the attachment. > !Screen Shot 2018-01-14 at 19.32.10.png|thumbnail! > This is pretty similar with WFLY-3365, not sure if I should have reopened that one o raised this one, sorry if I took the wrong decision. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9681) Deleting ExampleDS Leaves Remnants in standalone.xml

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9681?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-9681: ----------------------------------- This are EE default bindings. a tricky thing all in all. > Deleting ExampleDS Leaves Remnants in standalone.xml > ---------------------------------------------------- > > Key: WFLY-9681 > URL: https://issues.jboss.org/browse/WFLY-9681 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 11.0.0.Final > Reporter: Chris Giddings > Assignee: Stefano Maestri > Priority: Minor > Labels: JDBC > > h2. SUMMARY > When initially installing Wildfly 11.0.0 Final, the installation comes pre-configured with a datasource labeled "Example DS". > When this datasource is deleted, some configuration for it remains in the standalone.xml file for the standalone server mode. > h2. WORKAROUND > Removing this configuration manually and restarting Wildfly in standalone mode resolves the issue. (I tested by searching for "ExampleDS" as a string match in vi and deleting the one line the match found) > h2. BUG JUSTIFICATION > # I would expect anything labeled as "Example" to be deleted by an administrator in most environments > # I would expect deleted items to be fully removed upon deletion so remnant configuration couldn't cause issues with unrelated deployments (i.e. deployments which don't specifically require the deleted item) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9680) EJBs can't inherit a JDK8 default method when default implementation is in a third interface

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9680?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-9680: --------------------------------- Assignee: Stuart Douglas > EJBs can't inherit a JDK8 default method when default implementation is in a third interface > -------------------------------------------------------------------------------------------- > > Key: WFLY-9680 > URL: https://issues.jboss.org/browse/WFLY-9680 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.1.0.Final, 11.0.0.Final > Reporter: Daniel Bildhauer > Assignee: Stuart Douglas > Attachments: ejb-in-ear.zip, wildfly-ejb-in-ear-ear.ear > > > Given the following class/interface inheritance structure, the interface method doMagic could not be called from a remote view, even if there is a default implementation as given in the mixin interface. A local call works, but the remote call fails with a message like > {code} > org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) > {code} > Example code: > {code} > @Remote > interface MyEJBInterface { > void doMagic(); > } > interface MyEJBMixin extends MyEJBInterface { > default void doMagic() { .... } > } > @Stateless > class MyEJBBean extends MyEJBMixin { > } > {code} > The problem is inside the fix for WFLY-4354 bug, which checks only for the default method implementation in the interface declaring the method the first time but not in other interfaces. > A example is attached and I will submitt a pull request with a fix. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9678) Expand clustering test cases to 3-node cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9678?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9678: --------------------------------- Fix Version/s: 12.0.0.Alpha1 > Expand clustering test cases to 3-node cluster > ---------------------------------------------- > > Key: WFLY-9678 > URL: https://issues.jboss.org/browse/WFLY-9678 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 12.0.0.Alpha1 > > > The core of the problem is that since all cases run against 2-node cluster a remote fetch is never tested given that numOwners defaults to 2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8913) It is not possible to add cache store in infinispan subsystem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8913?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-8913: -------------------------------------- [~Maxoid] Alternatively (to the previous 2 options) you can boot the server in the admin only mode {{--admin-only}}, run the commands which will succeed since there won't be any runtime services and then just {{reload}}. > It is not possible to add cache store in infinispan subsystem > ------------------------------------------------------------- > > Key: WFLY-8913 > URL: https://issues.jboss.org/browse/WFLY-8913 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > Adding cache store to already created cache ends by failure even if it should succeed: > {code} > [standalone@localhost:9990 /] /subsystem=infinispan/cache-container=hibernate/invalidation-cache=foobar/store=STORE:add(class="org.infinispan.configuration.cache.SingleFileStoreConfigurationBuilder") > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service org.wildfly.clustering.infinispan.cache.store.hibernate.foobar is already registered", > "rolled-back" => true > } > {code} > This is a regression against 7.1.0.DR18. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9682) ApplicationSecurityDomain in EJB3, doesn't need to use a method reference lambda

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9682?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-9682: ----------------------------------- Summary: ApplicationSecurityDomain in EJB3, doesn't need to use a method reference lambda (was: ApplicationSecurityDomain in Undertow, doesn't need to use a method reference lambda) > ApplicationSecurityDomain in EJB3, doesn't need to use a method reference lambda > -------------------------------------------------------------------------------- > > Key: WFLY-9682 > URL: https://issues.jboss.org/browse/WFLY-9682 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9682) ApplicationSecurityDomain in EJB3, doesn't need to use a method reference lambda

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9682?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-9682: ----------------------------------- Component/s: EJB (was: Web (Undertow)) > ApplicationSecurityDomain in EJB3, doesn't need to use a method reference lambda > -------------------------------------------------------------------------------- > > Key: WFLY-9682 > URL: https://issues.jboss.org/browse/WFLY-9682 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9682) ApplicationSecurityDomain in Undertow, doesn't need to use a method reference lambda

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-9682: -------------------------------------- Summary: ApplicationSecurityDomain in Undertow, doesn't need to use a method reference lambda Key: WFLY-9682 URL: https://issues.jboss.org/browse/WFLY-9682 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 12.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1489) FormAuthenticationMechanism should only create a session if an identity is being stored

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1489: ------------------------------------- Summary: FormAuthenticationMechanism should only create a session if an identity is being stored Key: ELY-1489 URL: https://issues.jboss.org/browse/ELY-1489 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.2.0.Beta12 We don't need this internal method to contain the boolean argument: - {code} private IdentityCache createIdentityCache(HttpServerRequest request, boolean createSession) { {code} A subsequent call to put is sufficient for us to know a session is needed, an all other cases don't create the session. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 January 2018