[JBoss JIRA] (WFCORE-5068) Bootable JAR doesn't create install directories
by James Perkins (Jira)
James Perkins created WFCORE-5068:
-------------------------------------
Summary: Bootable JAR doesn't create install directories
Key: WFCORE-5068
URL: https://issues.redhat.com/browse/WFCORE-5068
Project: WildFly Core
Issue Type: Bug
Components: Bootable JAR
Reporter: Jean Francois Denise
Assignee: James Perkins
The issue occurs with --install-dir Bootable JAR option,
In case the first entry to be unzipped is not a directory, the unzip fails because the install dir doesn't exist.
This issue is hidden on some platforms where the first entries are directories, in such case, directories hierarchy is created.
This issue impacts Arquilian container for Bootable JAR that contains a workaround for it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (DROOLS-5203) Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ]
Toni Rikkola updated DROOLS-5203:
---------------------------------
Sprint: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27))
> Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows
> --------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5203
> URL: https://issues.redhat.com/browse/DROOLS-5203
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (DROOLS-4865) Add i18n reporting for DMN V&V
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-4865?page=com.atlassian.jira.plug... ]
Toni Rikkola updated DROOLS-4865:
---------------------------------
Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27))
> Add i18n reporting for DMN V&V
> ------------------------------
>
> Key: DROOLS-4865
> URL: https://issues.redhat.com/browse/DROOLS-4865
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> The current reporting from the shared V&V is showing debug messages that are not meant for user to see and the custom DMN V&V is not i18n.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (DROOLS-5259) DMN Validation takes 15s in the BC while the same file takes half a second as an unit test
by Toni Rikkola (Jira)
[ https://issues.redhat.com/browse/DROOLS-5259?page=com.atlassian.jira.plug... ]
Toni Rikkola updated DROOLS-5259:
---------------------------------
Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27))
> DMN Validation takes 15s in the BC while the same file takes half a second as an unit test
> ------------------------------------------------------------------------------------------
>
> Key: DROOLS-5259
> URL: https://issues.redhat.com/browse/DROOLS-5259
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Problem might be related to some limitation with Wildfly. It felt even slower with drools-wb-showcase, but need to time it.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (WFLY-10099) ClusteredJPA2LCTestCase fails intermittently
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-10099?page=com.atlassian.jira.plugi... ]
Cheng Fang commented on WFLY-10099:
-----------------------------------
still seeing this intermitten failure 2020-07-28:
https://ci.wildfly.org/buildConfiguration/WF_PullRequest_LinuxElytro/214052?
Build history shows it has a success rate of 99.1%
{code}
org.wildfly:wildfly-ts-integ-clustering
23:33:53
Importing data from '/store/work/tc-work/f5da3564a57e9d74/testsuite/integration/clustering/target/failsafe-reports/TEST-*.xml' (not existing file) with 'surefire' processor
23:33:53
Importing data from '/store/work/tc-work/f5da3564a57e9d74/testsuite/integration/clustering/target/surefire-reports/TEST-*.xml' (not existing file) with 'surefire' processor
23:33:54
Surefire report watcher
23:33:54
Surefire report watcher
23:44:22
org.jboss.as.test.clustering.cluster.jpa.ClusteredJPA2LCTestCase
23:44:22
testEntityCacheReplication
23:44:22
java.lang.AssertionError
23:44:22
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.jboss.as.test.clustering.cluster.jpa.ClusteredJPA2LCTestCase.testEntityCacheReplication(ClusteredJPA2LCTestCase.java:115)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
{code}
> ClusteredJPA2LCTestCase fails intermittently
> --------------------------------------------
>
> Key: WFLY-10099
> URL: https://issues.redhat.com/browse/WFLY-10099
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, JPA / Hibernate
> Affects Versions: 13.0.0.Final
> Reporter: Stuart Douglas
> Assignee: Paul Ferraro
> Priority: Major
> Fix For: 13.0.0.Beta1
>
>
> E.g.: https://ci.wildfly.org/viewLog.html?buildId=96134&tab=buildResultsDiv&bui...
> This is a complete guess but maybe the hibernate cache mode for the entity needs to be set to Transactional using the hibernate @Cache annotation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (DROOLS-5535) Drools - KieServices.Factory.get() returns null
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5535?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5535:
--------------------------------
Sprint: (was: 2020 Week 31-33 (from Jul 27))
> Drools - KieServices.Factory.get() returns null
> -----------------------------------------------
>
> Key: DROOLS-5535
> URL: https://issues.redhat.com/browse/DROOLS-5535
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.36.0.Final
> Reporter: Ashish Srivastava
> Assignee: Mario Fusco
> Priority: Major
>
> I try to integrate a Drools project in a maven application. The Drools app is running perfectly on his own, but when I try to integrate it in the *quarkus project*, I get a java.lang.NullPointerException.
> After some researches, it seems to happen because KieServices.Factory.get() return me null because of kie.conf.
> Drools Site Quote is: Many modules of Drools (e.g. drools-core, drools-compiler) have a file named {{kie.conf}} containing the names of the classes implementing the services provided by the corresponding module. When running Drools in a fat JAR, for example created by the Maven Shade Plugin, those various {{kie.conf}} files need to be merged, otherwise , the fat JAR will contain only 1 kie.conf from a single dependency, resulting into errors. You can merge resources in the Maven Shade Plugin using transformers, like this:
> ([https://docs.jboss.org/drools/release/7.14.0.Final/drools-docs/html_singl...])
> how can we configure the same for Quarkus Project ? or is there any way to load these file externally ..
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (WFLY-12815) Wildfly 13 - Thread local state corrupted by deployed application explosion during session timeout leading to WELD-001304 - More than one context active for scope type javax.enterprise.context.SessionScoped
by NUNO GODINHO DE MATOS (Jira)
[ https://issues.redhat.com/browse/WFLY-12815?page=com.atlassian.jira.plugi... ]
NUNO GODINHO DE MATOS edited comment on WFLY-12815 at 7/28/20 9:40 AM:
-----------------------------------------------------------------------
Hi,
I would Just like to let you know I have dome some small modifications to a sample application to try to make it reproduce the issue discussed here.
Uploadd:
I have uploaded a log file Sample_App_To_reproduceBug_001_RollingFileAppender.7z from my C:\dev\appserver\wildfly\wildfly-13.0.0.Final\user_projects\domains\SampleApp_Postgres\log.
Where you can see the sample application can be used to make the issue happen.
I have also uploaded on a different zip, the 01_snippets_of_code_of_sample_app.7z the interesting parts of the code of the sample app to make the issue happen.
I am not uploading the full sample app because I would need to remove content from it... and there is not much point to it. The code uploaded there can easily be bundled into any WAR file.
The thing to remember is that for this issue, you want to change the standalone.xml to have the servlet container default looking like this:
servlet-container name="default" default-session-timeout="1"
this helps with reproduce the issue, since after 1 minute wildfly will kill of the session.
Having a breakpoint in:
web.wildfly12815.WFLY12815SessionListener.sessionDestroyed(HttpSessionEvent)
Also helps, since this will allow you to login several sessions and have the session destroyed stop in your breakpoint thus corrupting multiple threads.
Testing the patch:
I will now try to build weld core and check if with it the issue stops being reproducible.
By the way yo get your pull request I actually needed to do:
git fetch origin refs/pull/2005/head:pull/2005
The command on the instruction above seemed to not work.
NOTE:
Seems like some siginifcant changes with some literals were done on the HttpContextLifecycle.java since version 3.0.4.Final that comes with wildfly 13, so doing tiny spot class replacement based on the:
weld-web-3.1.5-SNAPSHOT.jar would not work.
There is no alternative other than to do complete weld replacement following your instructions I believe.
Many thanks
was (Author: nuno.godinhomatos):
Hi,
I would Just like to let you know I have dome some small modifications to a sample application to try to make it reproduce the issue discussed here.
Uploadd:
I have uploaded a log file Sample_App_To_reproduceBug_001_RollingFileAppender.7z from my C:\dev\appserver\wildfly\wildfly-13.0.0.Final\user_projects\domains\SampleApp_Postgres\log.
Where you can see the sample application can be used to make the issue happen.
I have also uploaded on a different zip, the 01_snippets_of_code_of_sample_app.7z the interesting parts of the code of the sample app to make the issue happen.
I am not uploading the full sample app because I would need to remove content from it... and there is not much point to it. The code uploaded there can easily be bundled into any WAR file.
The thing to remember is that for this issue, you want to change the standalone.xml to have the servlet container default looking like this:
servlet-container name="default" default-session-timeout="1"
this helps with reproduce the issue, since after 1 minute wildfly will kill of the session.
Having a breakpoint in:
web.wildfly12815.WFLY12815SessionListener.sessionDestroyed(HttpSessionEvent)
Also helps, since this will allow you to login several sessions and have the session destroyed stop in your breakpoint thus corrupting multiple threads.
Testing the patch:
I will now try to build weld core and check if with it the issue stops being reproducible.
I will probably not follow the instruction on doing a FULL scale replacement of the weld core.
I need to continue working with Wildfly 13 for now the way it is vanilla, to experience the same sort of issues of projects using wildfly 13.
So i want o be perfectly in control of what code gets changed or not in my installation...
What I believe I will do is to build the weld code, and then grab the specific classes you have modified in your pull request.
And they I will go the "hacker" way and extract the weld code from my wildfly 13 and sneak in their your new classes.
IF I am lucky they are still compatible and not significant changes have gone into those two files since widlfly 13.
If I am not lucky I would need to replaye the full weld core...
But I will do that as a last resort.
By the way yo get your pull request I actually needed to do:
git fetch origin refs/pull/2005/head:pull/2005
The command on the instruction above seemed to not work.
Many thanks
> Wildfly 13 - Thread local state corrupted by deployed application explosion during session timeout leading to WELD-001304 - More than one context active for scope type javax.enterprise.context.SessionScoped
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12815
> URL: https://issues.redhat.com/browse/WFLY-12815
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 13.0.0.Final
> Environment: Environment independent the issue, it is purely a logical problem
> Reporter: NUNO GODINHO DE MATOS
> Assignee: Matěj Novotný
> Priority: Major
> Attachments: 01_snippets_of_code_of_sample_app.7z, Sample_App_To_reproduceBug_001_RollingFileAppender.7z, sourceCodeToSendToWildfly.7z
>
>
> The full description of the problem can be seen in stack overflow.
> Please consulder the issue:
> https://stackoverflow.com/questions/58930939/wildflt-13-weld-001304-more-...
> SUMMARY:
> (1) Setup you wildfly to have a session timeout of 1 minute - so that you can esaily make your http sessions timeout
> (2) Program in your WAR application a sessionDestroyed listener that will be broken.
> In our case whenever the session is timing out, we have some code that explodes in wildfly and not in weblogic because it expected for the RequestScope context to be active, but apparently in wildfly when Undertow to start killing of a session the request scope context is not made active so that caused our session destroyed handling to break
> (3) Do this sufficient amount of times to corrupted as may threads in the thread pool as possible
> (4) Now try to interact with your application making use of some session scoped beans .
> If you travel to ay sort of view that makes use of a session scoped bean that thread will be broken with the exception that multiple session scope context implementation are active.
> But this exception will only come out and aply if the thread handling the HTTP request is one of the threads that in the past were used by undertow to handle the session timeout.
> The only threads that have been corrupted forever are those that had a broken sessin timeout
> Explanation for the issue:
> - When the session timeout is being orchestrated by underdow, wildfly is activating a special HttpSessionDescrutionContext and making it active.
> This ACTIVE TRUE/FALSE flag is a ThreadLocal variable.
> So the activation of the scope context is marked on the thread itself.
> - When the thread blows up the thread context will remain for as long at the thread lives
> - in a future request the flag had that thread local variable active already.
> So when the BeanManagaerImpl is hunting to the one and only active http session context it finds the traditional happy path http session context active plust the DestructionSession context that was activated in a previous call.
> All of the illustrative stack traces that facilitate the comprehention of the issue are shown in the stack overflow thread.
> I am of the oppinion that errors like this can happen in the deployed applications.
> It would not hurt if wildfly would somehow be able to ensure that the thread that hand an explosion in a previous request is not corrupted when it is used to handle new requests.
> Many thanks for having a look.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months