July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10720) module with non existent dependency fails to load with no message

by Bartosz Spyrko-Śmietanko (JIRA)

[ https://issues.jboss.org/browse/WFLY-10720?page=com.atlassian.jira.plugin... ] Bartosz Spyrko-Śmietanko moved JBEAP-15076 to WFLY-10720: --------------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-10720 (was: JBEAP-15076) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Server (was: Server) Affects Version/s: (was: 7.1.3.GA) > module with non existent dependency fails to load with no message > ------------------------------------------------------------------ > > Key: WFLY-10720 > URL: https://issues.jboss.org/browse/WFLY-10720 > Project: WildFly > Issue Type: Enhancement > Components: Server > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Bartosz Spyrko-Śmietanko > Priority: Minor > > module with non existent dependency fails to load with no message > If a user configures a custom module for a datasource and misspells one of the dependencies, then it will fail to load the module but does not indicate why. As the module is defined, but one of its dependencies does not exist, it would be good if it logged why the module failed to load. > Can reproduce by editing: modules/system/layers/base/com/h2database/h2/main/module.xml > Change > <module name="javax.transaction.api"/> > to > <module name="jaxax.transaction.api"/> > {code} > 14:01:58,896 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 33) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "datasources"), > ("jdbc-driver" => "h2") > ]) - failure description: "WFLYJCA0041: Failed to load module for driver [com.h2database.h2]" > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ] David Lloyd commented on WFLY-10520: ------------------------------------ Another option is to have the transformer be in some unspecified module which is included by deployments by default. This could be a module which only exists for one release. It would be designated "private" so explicit dependencies on this module would generate a warning. Then the user should be able to reference the transformer class by name without referencing a module name. We do not need an EAP7 because this is covered by EAP7-999. > Add Hibernate ORM 5.3 compatibility transformer > ----------------------------------------------- > > Key: WFLY-10520 > URL: https://issues.jboss.org/browse/WFLY-10520 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Scott Marlow > Fix For: 14.0.0.CR1 > > > A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1. > From https://docs.google.com/document/d/1cAVBdeQXQfpTwH0f_GKSahh_gRd7bKI6kII-w... > # Change calls to org.hibernate.BasicQueryContract.getFlushMode(), to instead call BasicQueryContract.getHibernateFlushMode(). > # Change calls to org.hibernate.Session.getFlushMode, to instead call Session.getHibernateFlushMode() > # Change references to Enum org.hibernate.FlushMode.NEVER (0), to FlushMode.MANUAL (0). > # Change calls to org.hibernate.Query.getMaxResults() returning Integer, to instead call org.hibernate.Query.getHibernateMaxResults() (returning Integer). > # Change calls to org.hibernate.Query.setMaxResults(int), to instead call org.hibernate.Query.setHibernateMaxResults(int). > # Change calls to org.hibernate.Query.getFirstResult(int) returning Integer, to instead call org.hibernate.Query.getHibernateFirstResult() (returning Integer). > # Change calls to org.hibernate.Query.setFirstResult(int), to instead call org.hibernate.Query.setHibernateFirstResult(int). > # Fill in rules here for UserType handling, which we are exploring still ([see list of methods in rejected ORM pr|https://github.com/hibernate/hibernate-orm/pull/2412/files]). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2755) [DMN Designer] Error when the user switches between DMN files

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2755?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2755: ----------------------------------- Component/s: DMN Editor > [DMN Designer] Error when the user switches between DMN files > ------------------------------------------------------------- > > Key: DROOLS-2755 > URL: https://issues.jboss.org/browse/DROOLS-2755 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Guilherme Carreiro > Assignee: Michael Anstis > Labels: drools-tools > Attachments: demo.gif > > > When the user switches between DMN files, the following error happens: > !demo.gif|thumbnail! > It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2755) [DMN Designer] Error when the user switches between DMN files

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2755?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2755: ----------------------------------- Sprint: 2018 Week 27-29 > [DMN Designer] Error when the user switches between DMN files > ------------------------------------------------------------- > > Key: DROOLS-2755 > URL: https://issues.jboss.org/browse/DROOLS-2755 > Project: Drools > Issue Type: Bug > Affects Versions: 7.9.0.Final > Reporter: Guilherme Carreiro > Assignee: Michael Anstis > Labels: drools-tools > Attachments: demo.gif > > > When the user switches between DMN files, the following error happens: > !demo.gif|thumbnail! > It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2744) [DMN Designer] Global diagram properties

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2744?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2744: ---------------------------------------- [~jomarko] I'm proposing we remove those properties from "Diagram" and have prepared a PR to achieve the same. My reasoning being, (1) changing them has no visual affect, (2) they are not persisted to XML anyway, (3) for consistency across editors (BPMN has elected to remove them). > [DMN Designer] Global diagram properties > ---------------------------------------- > > Key: DROOLS-2744 > URL: https://issues.jboss.org/browse/DROOLS-2744 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > The global diagram properties for DMN diagram contains sections settings for: > - dimensions > - backround > - font > However change of any of them (globally, for the whole diagram) doesn't seem to affect particular nodes somehow. We should hide these settings or implement the logic that would affect all nodes in diagram by change on this place. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-346) Bookinfo Timeouts

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-346?page=com.atlassian.jira.plugin.... ] Matt Mahoney resolved SWSQE-346. -------------------------------- Resolution: Done > Bookinfo Timeouts > ----------------- > > Key: SWSQE-346 > URL: https://issues.jboss.org/browse/SWSQE-346 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Bookinfo has been timing out waiting for the app to be ready. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-10520: ------------------------------------- Is it worth moving the transformer into its own module? Once an application adds a dependency on that module, the application will not work with the future releases that no longer contain that module. Some choices are: # Leave the transformer in the JPA subsystem and document that the only way to use it, is via the -DHibernate51CompatibilityTransformer=true system property option. # Move the transformer into its own (Hibernate orm 5.1 native app transformer) module that applications can add a dependency on, but those applications will break when we remove that module in the future, so it might be better to only support the system property option. Also, do we need an EAP7 jira for this issue? > Add Hibernate ORM 5.3 compatibility transformer > ----------------------------------------------- > > Key: WFLY-10520 > URL: https://issues.jboss.org/browse/WFLY-10520 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Scott Marlow > Fix For: 14.0.0.CR1 > > > A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1. > From https://docs.google.com/document/d/1cAVBdeQXQfpTwH0f_GKSahh_gRd7bKI6kII-w... > # Change calls to org.hibernate.BasicQueryContract.getFlushMode(), to instead call BasicQueryContract.getHibernateFlushMode(). > # Change calls to org.hibernate.Session.getFlushMode, to instead call Session.getHibernateFlushMode() > # Change references to Enum org.hibernate.FlushMode.NEVER (0), to FlushMode.MANUAL (0). > # Change calls to org.hibernate.Query.getMaxResults() returning Integer, to instead call org.hibernate.Query.getHibernateMaxResults() (returning Integer). > # Change calls to org.hibernate.Query.setMaxResults(int), to instead call org.hibernate.Query.setHibernateMaxResults(int). > # Change calls to org.hibernate.Query.getFirstResult(int) returning Integer, to instead call org.hibernate.Query.getHibernateFirstResult() (returning Integer). > # Change calls to org.hibernate.Query.setFirstResult(int), to instead call org.hibernate.Query.setHibernateFirstResult(int). > # Fill in rules here for UserType handling, which we are exploring still ([see list of methods in rejected ORM pr|https://github.com/hibernate/hibernate-orm/pull/2412/files]). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBVFS-206) URL.getContent() returns VirtualFile instead of ImageProducer

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/JBVFS-206?page=com.atlassian.jira.plugin.... ] Tomas Hofman resolved JBVFS-206. -------------------------------- Fix Version/s: 3.5.0.Alpha1 3.2.13.Final Resolution: Done > URL.getContent() returns VirtualFile instead of ImageProducer > ------------------------------------------------------------- > > Key: JBVFS-206 > URL: https://issues.jboss.org/browse/JBVFS-206 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.12.Final > Environment: Windows XP > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Fix For: 3.5.0.Alpha1, 3.2.13.Final > > > URL.getContent() behaves differently within JBoss than it does in a normal JVM. In our case, when a jar is used in a normal JVM, URL.getContent() returns an ImageProducer. When the same jar is used from within JBoss, a VirtualFile is returned which then causes a ClassCastException. > Note: This worked fine in JBoss 4.2.3.GA. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-338) Checker script needs replacement for --show-all flag as it will not be supported in future

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/SWSQE-338?page=com.atlassian.jira.plugin.... ] Sunil kondkar resolved SWSQE-338. --------------------------------- Resolution: Done > Checker script needs replacement for --show-all flag as it will not be supported in future > ------------------------------------------------------------------------------------------ > > Key: SWSQE-338 > URL: https://issues.jboss.org/browse/SWSQE-338 > Project: Kiali QE > Issue Type: Task > Reporter: Sunil kondkar > Assignee: Sunil kondkar > Priority: Minor > > 1. Checker script uses the flag -show-all=false to hide the terminated/evicted pods. In jenkins run, we get messages like: > Flag --show-all has been deprecated, will be removed in an upcoming release > Some replacement is needed for the flag in the script. > 2. Fix a corner case where istio is not deployed successfuly and checker script shows istio pods deployed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3962) Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ] David Lloyd commented on WFCORE-3962: ------------------------------------- That's disappointing... will keep digging. > Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se > ----------------------------------------------------------------------- > > Key: WFCORE-3962 > URL: https://issues.jboss.org/browse/WFCORE-3962 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Affects Versions: 6.0.0.Alpha3 > Reporter: Matej Novotny > Assignee: David Lloyd > Priority: Blocker > Labels: Java11 > > As per request, copying MODULES-372 to WFCORE as well. > Starting WFLY with JDK 11 using {{standalone.sh}} yields: > {code} > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > {code} > Output of {{java -version}}: > {code} > openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+21) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 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 July 2018