March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1025) NPE removing a rule that contains a subnetwork

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1025?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on DROOLS-1025: ------------------------------------------------- Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1298579|https://bugzilla.redhat.com/show_bug.cgi?id=1298579] from ON_QA to MODIFIED > NPE removing a rule that contains a subnetwork > ---------------------------------------------- > > Key: DROOLS-1025 > URL: https://issues.jboss.org/browse/DROOLS-1025 > Project: Drools > Issue Type: Bug > Reporter: Mario Fusco > Assignee: Mario Fusco > > Removing a rule containing a subnetwork causes the following NPE: > {code} > java.lang.NullPointerException > at org.drools.core.phreak.AddRemoveRule.deletePeerLeftTuple(AddRemoveRule.java:777) > at org.drools.core.phreak.AddRemoveRule.followPeer(AddRemoveRule.java:749) > at org.drools.core.phreak.AddRemoveRule.processLeftTuples(AddRemoveRule.java:713) > at org.drools.core.phreak.AddRemoveRule.flushStagedTuples(AddRemoveRule.java:281) > at org.drools.core.phreak.AddRemoveRule.removeRule(AddRemoveRule.java:153) > at org.drools.core.reteoo.ReteooBuilder.removeTerminalNode(ReteooBuilder.java:173) > at org.drools.core.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:163) > at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1635) > at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1626) > at org.drools.core.impl.KnowledgeBaseImpl.internalRemoveRule(KnowledgeBaseImpl.java:1610) > at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1581) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6410) Domain server suspend does not accept -1 timeout(indefinite)

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFLY-6410: ---------------------------------------- Summary: Domain server suspend does not accept -1 timeout(indefinite) Key: WFLY-6410 URL: https://issues.jboss.org/browse/WFLY-6410 Project: WildFly Issue Type: Bug Reporter: Bartosz Baranowski Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1099) Couldn't access any web service of drools or kie which run in docker container

by Jackey Lee (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1099?page=com.atlassian.jira.plugi... ] Jackey Lee edited comment on DROOLS-1099 at 3/20/16 10:54 PM: -------------------------------------------------------------- Hi Petr, I Have provided the logs when accessing drools-work-bench and kie-server running in docker [^drools-wb.log][^kie-server.log] Would you please help to check? I must have missed something. Thanks & Regards Pengcheng was (Author: jackeylee): Hi Peter, I Have provided the logs when accessing drools-work-bench and kie-server running in docker [^drools-wb.log][^kie-server.log] Would you please help to check? I must have missed something. Thanks & Regards Pengcheng > Couldn't access any web service of drools or kie which run in docker container > ------------------------------------------------------------------------------ > > Key: DROOLS-1099 > URL: https://issues.jboss.org/browse/DROOLS-1099 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 6.2.0.Final, 6.4.0.CR1 > Environment: Ubuntu 15.04, Docker 1.10.3 > Reporter: Jackey Lee > Assignee: Mario Fusco > Attachments: drools-wb.log, kie-server.log > > > I followed the instructions to run drools and KIE workbenches in docker. But the browser shows "404-Not Found" when I tried to access http://localhost:8080/drools-wb. > It shows "Forbidden" when I tried to access http://localhost:32769/kie-server -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1099) Couldn't access any web service of drools or kie which run in docker container

by Jackey Lee (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1099?page=com.atlassian.jira.plugi... ] Jackey Lee edited comment on DROOLS-1099 at 3/20/16 10:53 PM: -------------------------------------------------------------- Hi Peter, I Have provided the logs when accessing drools-work-bench and kie-server running in docker [^drools-wb.log][^kie-server.log] Would you please help to check? I must have missed something. Thanks & Regards Pengcheng was (Author: jackeylee): Logs when accessing drools-work-bench and kie-server running in docker [^drools-wb.log][^kie-server.log] > Couldn't access any web service of drools or kie which run in docker container > ------------------------------------------------------------------------------ > > Key: DROOLS-1099 > URL: https://issues.jboss.org/browse/DROOLS-1099 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 6.2.0.Final, 6.4.0.CR1 > Environment: Ubuntu 15.04, Docker 1.10.3 > Reporter: Jackey Lee > Assignee: Mario Fusco > Attachments: drools-wb.log, kie-server.log > > > I followed the instructions to run drools and KIE workbenches in docker. But the browser shows "404-Not Found" when I tried to access http://localhost:8080/drools-wb. > It shows "Forbidden" when I tried to access http://localhost:32769/kie-server -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1099) Couldn't access any web service of drools or kie which run in docker container

by Jackey Lee (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1099?page=com.atlassian.jira.plugi... ] Jackey Lee updated DROOLS-1099: ------------------------------- Attachment: kie-server.log drools-wb.log Logs when accessing drools-work-bench and kie-server running in docker > Couldn't access any web service of drools or kie which run in docker container > ------------------------------------------------------------------------------ > > Key: DROOLS-1099 > URL: https://issues.jboss.org/browse/DROOLS-1099 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 6.2.0.Final, 6.4.0.CR1 > Environment: Ubuntu 15.04, Docker 1.10.3 > Reporter: Jackey Lee > Assignee: Mario Fusco > Attachments: drools-wb.log, kie-server.log > > > I followed the instructions to run drools and KIE workbenches in docker. But the browser shows "404-Not Found" when I tried to access http://localhost:8080/drools-wb. > It shows "Forbidden" when I tried to access http://localhost:32769/kie-server -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1099) Couldn't access any web service of drools or kie which run in docker container

by Jackey Lee (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1099?page=com.atlassian.jira.plugi... ] Jackey Lee edited comment on DROOLS-1099 at 3/20/16 10:50 PM: -------------------------------------------------------------- Logs when accessing drools-work-bench and kie-server running in docker [^drools-wb.log][^kie-server.log] was (Author: jackeylee): Logs when accessing drools-work-bench and kie-server running in docker > Couldn't access any web service of drools or kie which run in docker container > ------------------------------------------------------------------------------ > > Key: DROOLS-1099 > URL: https://issues.jboss.org/browse/DROOLS-1099 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 6.2.0.Final, 6.4.0.CR1 > Environment: Ubuntu 15.04, Docker 1.10.3 > Reporter: Jackey Lee > Assignee: Mario Fusco > Attachments: drools-wb.log, kie-server.log > > > I followed the instructions to run drools and KIE workbenches in docker. But the browser shows "404-Not Found" when I tried to access http://localhost:8080/drools-wb. > It shows "Forbidden" when I tried to access http://localhost:32769/kie-server -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6296) Method duplication in undertow tests

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6296?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-6296: ------------------------------------ Assignee: (was: Stuart Douglas) > Method duplication in undertow tests > ------------------------------------ > > Key: WFLY-6296 > URL: https://issues.jboss.org/browse/WFLY-6296 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Shishir Subramanyam > Priority: Trivial > > All the undertow subsystems classes: UndertowSubsystemTestCase (6 files) contain the same definition of the method testRuntime. This method contains some hard coded settings (65 lines) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5969) io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents

by Matthew Casperson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5969?page=com.atlassian.jira.plugin.... ] Matthew Casperson commented on WFLY-5969: ----------------------------------------- Apologies - it does appear that context path has no effect. With or without context path, setting resolve-against-context-root does allow the delivery of static context when the default servlet is mapped to a subpath. However, I'm still a bit unclear on the intended functionality when resolve-against-context-root is mixed with something like this in web.xml: <servlet-mapping> <servlet-name>default</servlet-name> <url-pattern>/static/*</url-pattern> </servlet-mapping> i.e. this: https://github.com/mcasperson/wildfly-default-servlet-bug/blob/master/src... I would have expected the servlet mapping to allow only the static resources in the "static" directory to browsed and opened. With resolve-against-context-root set to true, browsing and downloading works for all directories, apparently ignoring the servlet-mapping. To demonstrate this I have deployed the war file generated from the sample app at https://github.com/mcasperson/wildfly-default-servlet-bug deployed to Wildfly 10 Final in Openshift at http://wildflybug1-kuna.rhcloud.com/wildfly-default-servlet-bug/. You'll note that http://wildflybug1-kuna.rhcloud.com/wildfly-default-servlet-bug/static2 can be browsed (ignore the fact that the response is plain text, I think that is an Openshift issue, as it is a valid HTML page when you run this locally), and http://wildflybug1-kuna.rhcloud.com/wildfly-default-servlet-bug/static2/d... can be downloaded, despite the default servlet being mapped only to the "static" directory. > io.undertow.servlet.handlers.DefaultServlet will list incorrect directory contents > ---------------------------------------------------------------------------------- > > Key: WFLY-5969 > URL: https://issues.jboss.org/browse/WFLY-5969 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.CR5 > Environment: MacOS with Java 8u65 > Reporter: Matthew Casperson > Assignee: Stuart Douglas > Attachments: Screen Shot 2016-01-11 at 11.24.34 am.png, Screen Shot 2016-01-11 at 11.24.41 am.png > > > The Untertow DefaultServlet exhibits some odd behaviour when it has been mapped to a subdirectory. > To see this behaviour, build the WAR file from the sample project at https://github.com/mcasperson/wildfly-default-servlet-bug. Deploy to WildFly 10 CR5, and open the link http://localhost:8080/wildfly-default-servlet-bug/static (note no slash on the end of the URL). You'll see the expected directory listing. > !Screen Shot 2016-01-11 at 11.24.41 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/ (note the slash on the end). You'll actually now be browsing the root directory of the application. > !Screen Shot 2016-01-11 at 11.24.34 am.png|thumbnail! > Now open http://localhost:8080/wildfly-default-servlet-bug/static/static/data.xml (note the double static in the URL). You'll be able to open the XML file. This is not what I would have expected. > Now open http://localhost:8080/wildfly-default-servlet-bug/static/data.xml. You'll get a 404. I would have expected to be able to open the file using this URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1100) Decision table conversion to DRL logic change in some version later than 6.1.0.Final

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1100?page=com.atlassian.jira.plugi... ] Michael Anstis moved GUVNOR-2471 to DROOLS-1100: ------------------------------------------------ Project: Drools (was: Guvnor) Key: DROOLS-1100 (was: GUVNOR-2471) Workflow: GIT Pull Request workflow (was: classic default workflow) > Decision table conversion to DRL logic change in some version later than 6.1.0.Final > ------------------------------------------------------------------------------------ > > Key: DROOLS-1100 > URL: https://issues.jboss.org/browse/DROOLS-1100 > Project: Drools > Issue Type: Bug > Reporter: Vytautas Gimbutas > Attachments: Screen Shot 2016-03-19 at 8.40.40 PM.png > > > It seems there was a change of how decision tables are converted to DRL in some version later than 6.1.0. See attached screenshot for decision table i'm trying to generate. > In 6.1.0.Final this gets converted to: > {code} > // rule values at C42, header at C37 > rule "X_42" > no-loop true > salience 65494 > when > $p: Project(id == "40098") > $c: Client() > then > modify($c) { incrementPricingStep(2, 8); } > end > {code} > but in 6.4.0.CR1 it gets converted to: > {code} > // rule values at C42, header at C37 > rule "X_42" > no-loop true > salience 65494 > when > $p: Project() > $c: Client(id == "40098") > then > modify($c) { incrementPricingStep(2, 8); } > end > {code} > Maybe this is not intentional and caused by accident? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6409) Update default domain configuration to use http-remoting

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6409?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6409: ---------------------------------------- This is a clone of WFCORE-1182 needed because the host.xml files used in full are not the ones that the fix for the core issue uses; full overrides the ones from core. So both repos need fixes. Also, full has host.xml files in both its feature-pack and servlet-feature-pack modules, so both should be updated. > Update default domain configuration to use http-remoting > -------------------------------------------------------- > > Key: WFLY-6409 > URL: https://issues.jboss.org/browse/WFLY-6409 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > Our default domain configuration still use the native remote protocol on port 9999 for DC-HC communication. Update those files so that we use http-remoting on port 9990. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016