[JBoss JIRA] (DROOLS-1462) not( null ) unary test not working
by Edson Tirelli (JIRA)
Edson Tirelli created DROOLS-1462:
-------------------------------------
Summary: not( null ) unary test not working
Key: DROOLS-1462
URL: https://issues.jboss.org/browse/DROOLS-1462
Project: Drools
Issue Type: Bug
Components: dmn engine
Affects Versions: 7.0.0.Beta6
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 7.0.0.Final
The engine is not properly creating the unary test ```not( null )``` and raising a NPE.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (WFCORE-2077) OutOfMemoryError: Metaspace after several client calls
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2077?page=com.atlassian.jira.plugi... ]
Tomaz Cerar resolved WFCORE-2077.
---------------------------------
Fix Version/s: 3.0.0.Beta5
Resolution: Done
I think it is safe to resolve this now.
If noting else, initial problems ware addressed.
If new ones are found, new jira should be opened.
> OutOfMemoryError: Metaspace after several client calls
> ------------------------------------------------------
>
> Key: WFCORE-2077
> URL: https://issues.jboss.org/browse/WFCORE-2077
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha13
> Reporter: Petr Kremensky
> Assignee: Tomaz Cerar
> Priority: Blocker
> Fix For: 3.0.0.Beta5
>
>
> I saw some java.lang.OutOfMemoryError: Metaspace in our AS-Testsuite runs. Here is a really simple (and clumsy) reproducer for the leak.
> *repreduce*
> {noformat}
> # lower the metaspace size in jboss-eap-7.1/bin/standalone.conf to
> # -XX:MaxMetaspaceSize=64m
> # start standalone
> ./jboss-eap-7.1/bin/standalone.sh
> # run the following loop (any other mgmt operation should serve the same)
> for i in `seq 1 1000` ; do ./jboss-eap-7.1/bin/jboss-cli.sh -c :read-resource ; done
> # wait for OOM
> {noformat}
> {noformat}
> 14:24:29,629 WARN [org.jboss.modules] (MSC service thread 1-3) Failed to define class io.undertow.security.impl.SimpleNonceManager in Module "io.undertow.core:main" from local module loader @629f0666 (finder: local module finder @1bc6a36e (roots: /home/pkremens/workspace/jboss-eap-7.1/modules,/home/pkremens/workspace/jboss-eap-7.1/modules/system/layers/base)): java.lang.OutOfMemoryError: Metaspace
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:359)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:438)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:275)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:79)
> at org.jboss.modules.Module.loadModuleClass(Module.java:612)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:377)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:365)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:94)
> at org.jboss.as.domain.http.server.security.LogoutHandler.<init>(LogoutHandler.java:76)
> at org.jboss.as.domain.http.server.ManagementHttpServer.addLogoutHandler(ManagementHttpServer.java:316)
> at org.jboss.as.domain.http.server.ManagementHttpServer.setupOpenListener(ManagementHttpServer.java:395)
> at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:271)
> at org.jboss.as.domain.http.server.ManagementHttpServer.access$2400(ManagementHttpServer.java:107)
> at org.jboss.as.domain.http.server.ManagementHttpServer$Builder.build(ManagementHttpServer.java:589)
> at org.jboss.as.server.mgmt.UndertowHttpManagementService.start(UndertowHttpManagementService.java:292)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (WFCORE-2348) Error while starting WildFly as service in domain mode using init scripts.
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2348?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-2348:
------------------------------------------
There is no downstream dependency here. These files are not used in EAP. There is no docs/contrib folder in the EAP distribution.
> Error while starting WildFly as service in domain mode using init scripts.
> --------------------------------------------------------------------------
>
> Key: WFCORE-2348
> URL: https://issues.jboss.org/browse/WFCORE-2348
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Affects Versions: 3.0.0.Beta7
> Environment: Fedora, RHEL
> Reporter: Radovan Stancel
> Assignee: Radovan Stancel
> Priority: Minor
> Labels: downstream_dependency
> Original Estimate: 4 hours
> Time Spent: 3 hours
> Remaining Estimate: 1 hour
>
> When starting WildFly as a service in domain mode using init scripts there appears in console.log error:
> /usr/bin/dirname: unrecognized option '--domain-config=domain.xml'
> Try '/usr/bin/dirname --help' for more information.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (WFCORE-2360) Misleading failure description upon attempt of /host=slave/server-config=x:remove() when server-config=x is still running
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2360?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved JBEAP-9300 to WFCORE-2360:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2360 (was: JBEAP-9300)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
(was: User Experience)
Affects Version/s: 3.0.0.Beta6
(was: 7.1.0.DR13)
> Misleading failure description upon attempt of /host=slave/server-config=x:remove() when server-config=x is still running
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2360
> URL: https://issues.jboss.org/browse/WFCORE-2360
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Beta6
> Reporter: Michal Jurc
> Assignee: ehsavoie Hugonnet
>
> When trying to remove a running {{server-config}} on slave host from {{host-master}} controller, the following message is produced in CLI:
> {code}[domain@localhost:9990 /] /host=hc1/server-config=server-two:remove()
> {
> "outcome" => "failed",
> "result" => {},
> "failure-description" => {"host-failure-descriptions" => {"hc1" => "WFLYHC0201: Error synchronizing the host model with the domain controller model with failure : WFLYCTL0063: Composite operation was rolled back."}},
> "rolled-back" => true
> }
> {code}
> This is not very informative. The error message from just removing running {{server-config}} managed by controller is different, and also much more informative:
> {code}[domain@localhost:9990 /] /host=master/server-config=server-two:remove()
> {
> "outcome" => "failed",
> "result" => {},
> "failure-description" => {"host-failure-descriptions" => {"master" => "WFLYHC0078: Server (server-two) still running"}},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (WFCORE-2360) Misleading failure description upon attempt of /host=slave/server-config=x:remove() when server-config=x is still running
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2360?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-2360:
-------------------------------------
Affects Version/s: (was: 3.0.0.Beta6)
> Misleading failure description upon attempt of /host=slave/server-config=x:remove() when server-config=x is still running
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2360
> URL: https://issues.jboss.org/browse/WFCORE-2360
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: ehsavoie Hugonnet
>
> When trying to remove a running {{server-config}} on slave host from {{host-master}} controller, the following message is produced in CLI:
> {code}[domain@localhost:9990 /] /host=hc1/server-config=server-two:remove()
> {
> "outcome" => "failed",
> "result" => {},
> "failure-description" => {"host-failure-descriptions" => {"hc1" => "WFLYHC0201: Error synchronizing the host model with the domain controller model with failure : WFLYCTL0063: Composite operation was rolled back."}},
> "rolled-back" => true
> }
> {code}
> This is not very informative. The error message from just removing running {{server-config}} managed by controller is different, and also much more informative:
> {code}[domain@localhost:9990 /] /host=master/server-config=server-two:remove()
> {
> "outcome" => "failed",
> "result" => {},
> "failure-description" => {"host-failure-descriptions" => {"master" => "WFLYHC0078: Server (server-two) still running"}},
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months