[JBoss JIRA] (DROOLS-3154) Minor UI improvements/bugfixes for Scenario
by Juraj Soltes (Jira)
[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ]
Juraj Soltes edited comment on DROOLS-3154 at 10/24/18 7:37 AM:
----------------------------------------------------------------
Hello, one more thing to update... the left margin on the Test Editor Tab - see the picture below,
There needs to be some, probably at the same level as the paragraph underneath.
!test-editor-margin.png|thumbnail!
was (Author: jsoltes):
Hello, one more thing to update... the left margin on the Test Editor Tab - see the picture !test-editor-margin.png|thumbnail!
There needs to be some, probably at the same level as the text below.
> Minor UI improvements/bugfixes for Scenario
> -------------------------------------------
>
> Key: DROOLS-3154
> URL: https://issues.jboss.org/browse/DROOLS-3154
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Critical
> Labels: UX-CSS
> Attachments: test-editor-margin.png
>
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3154) Minor UI improvements/bugfixes for Scenario
by Juraj Soltes (Jira)
[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ]
Juraj Soltes commented on DROOLS-3154:
--------------------------------------
Hello, one more thing to update... the left margin on the Test Editor Tab - see the picture !test-editor-margin.png|thumbnail!
There needs to be some, probably at the same level as the text below.
> Minor UI improvements/bugfixes for Scenario
> -------------------------------------------
>
> Key: DROOLS-3154
> URL: https://issues.jboss.org/browse/DROOLS-3154
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Critical
> Labels: UX-CSS
> Attachments: test-editor-margin.png
>
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3154) Minor UI improvements/bugfixes for Scenario
by Juraj Soltes (Jira)
[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ]
Juraj Soltes updated DROOLS-3154:
---------------------------------
Attachment: test-editor-margin.png
> Minor UI improvements/bugfixes for Scenario
> -------------------------------------------
>
> Key: DROOLS-3154
> URL: https://issues.jboss.org/browse/DROOLS-3154
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Critical
> Labels: UX-CSS
> Attachments: test-editor-margin.png
>
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11221) Agroal datasource cannot be used as DefaultDataSource without connector subsystem
by Martin Simka (Jira)
[ https://issues.jboss.org/browse/WFLY-11221?page=com.atlassian.jira.plugin... ]
Martin Simka updated WFLY-11221:
--------------------------------
Steps to Reproduce:
# remove datasources subsystem
# add agroal subsystem and define ExampleDS datasource
{code}
<extension module="org.wildfly.extension.datasources-agroal"/>
...
<subsystem xmlns="urn:jboss:domain:datasources-agroal:1.0">
<datasource name="ExampleDS" jndi-name="java:jboss/datasources/ExampleDS">
<connection-factory driver="h2" url="jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE" username="sa" password="sa">
</connection-factory>
<connection-pool max-size="30"/>
</datasource>
<drivers>
<driver name="h2" module="com.h2database.h2" class="org.h2.Driver"/>
</drivers>
</subsystem>
{code}
# Deploy application that injects DefaultDataSource
{code}
@Resource(lookup="java:comp/DefaultDataSource")
DataSource myDS;
{code}
was:
# remove datasources subsystem
# add agroal subsystem and define ExampleDS datasource
{code}
<extension module="org.wildfly.extension.datasources-agroal"/>
...
<subsystem xmlns="urn:jboss:domain:datasources-agroal:1.0">
<datasource name="ExampleDS" jndi-name="java:jboss/datasources/ExampleDS">
<connection-factory driver="h2" url="jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE" username="sa" password="sa">
</connection-factory>
<connection-pool max-size="30"/>
</datasource>
<drivers>
<driver name="h2" module="com.h2database.h2" class="org.h2.Driver"/>
</drivers>
</subsystem>
{code}
#Deploy application that injects DefaultDataSource
{code}
@Resource(lookup="java:comp/DefaultDataSource")
DataSource myDS;
{code}
> Agroal datasource cannot be used as DefaultDataSource without connector subsystem
> ---------------------------------------------------------------------------------
>
> Key: WFLY-11221
> URL: https://issues.jboss.org/browse/WFLY-11221
> Project: WildFly
> Issue Type: Bug
> Components: Agroal, EE, JCA
> Affects Versions: 14.0.0.Final
> Reporter: Martin Simka
> Assignee: Stefano Maestri
> Priority: Major
>
> If {{datasources}} subsystem is removed and {{Example}} datasource is created in {{datasources-agroal}} subsystem it is expected that Example datasource ({{java:jboss/datasources/ExampleDS}}) is bound to {{java:comp/DefaultDataSource}}, but it is not.
> {noformat}
> 12:33:17,605 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "testwebapplication.war")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.module.testwebapplication.testwebapplication.DefaultDataSource"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.testwebapplication.testwebapplication.env.\"org.jboss.qa.msimka.testwebapp.TestBean\".myDS is missing [jboss.naming.context.java.module.testwebapplication.testwebapplication.DefaultDataSource]"]
> }
> {noformat}
> JNDI of datasource that should be bound to default datasource can be defined in [ee subsystem|http://wildscribe.github.io/WildFly/14.0/subsystem/ee/service/default-bindings/index.html]
> Datasources subsystem is currently responsible for DefaultDatasource [binding|https://github.com/wildfly/wildfly/blob/master/connector/src/main...].
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-11235) Server with HA profile bound to 0.0.0.0 sends cluster topology containing this address to client
by Lin Gao (Jira)
[ https://issues.jboss.org/browse/WFLY-11235?page=com.atlassian.jira.plugin... ]
Lin Gao updated WFLY-11235:
---------------------------
Attachment: WFLY-11235-reproducer.zip
> Server with HA profile bound to 0.0.0.0 sends cluster topology containing this address to client
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-11235
> URL: https://issues.jboss.org/browse/WFLY-11235
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Minor
> Labels: downstream_dependency
> Attachments: WFLY-11235-reproducer.zip
>
> Original Estimate: 4 days
> Remaining Estimate: 4 days
>
> Scenario:
> - server-1
> -- Doesn't matter which profile
> -- Doesn't matter which bind address
> -- Has a remote-outbound-connection pointing at server-2 through server-2's public IP address
> - server-2
> -- On a different machine than server-1
> -- Bound to 0.0.0.0 (important)
> -- Running standalone-ha profile (important)
> - Standalone EJB client invokes a bean server-1, which as a result invokes another bean on server-2. Repeat this multiple times.
> The first invocation goes through correctly, but it can be seen in the log of server-1 that server-2 (10.8.246.90) has sent a cluster topology containing 0.0.0.0:
> {noformat}
> 04:04:24,651 TRACE [org.jboss.ejb.client.remoting] (default task-5) Running callback org.jboss.ejb.protocol.remote.RemoteEJBService$1$1$$Lambda$876/915175573@68823b7b(org.jboss.ejb.protocol.remote.EJBServerChannel(a)707ad04e, org.jboss.as.ejb3.remote.AssociationImpl@3eb54e9a)
> 04:04:24,919 INFO [org.wildfly.naming] (default task-7) WildFly Naming version 1.0.7.Final-redhat-1
> 04:04:24,930 INFO [org.jboss.ejb.client] (default task-7) JBoss EJB Client version 4.0.9.Final-redhat-1
> 04:04:24,941 DEBUG [org.jboss.ejb.client.invocation] (default task-7) Calling invoke(module = /server-side/WhoAmIBean, strong affinity = None, weak affinity = None):
> 04:04:24,948 TRACE [org.jboss.ejb.client.invocation] (default task-7) Calling executeDiscovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is None, weak affinity = None)
> 04:04:24,949 TRACE [org.jboss.ejb.client.invocation] (default task-7) Performing any discovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is None, weak affinity = None, filter spec = (ejb-module=server-side))
> 04:04:24,952 TRACE [org.jboss.ejb.client.invocation] (default task-7) EJB discovery provider: attempting to connect to configured connection remote+http://10.8.246.90:8080
> 04:04:25,317 DEBUG [org.jboss.ejb.client.invocation] (default task-18) Received CLUSTER_TOPOLOGY(15) message, registering cluster ejb to node localhost
> 04:04:25,319 DEBUG [org.jboss.ejb.client.invocation] (default task-18) Received CLUSTER_TOPOLOGY(15) message block, registering block ::/0 to address /0.0.0.0:8080
> 04:04:25,321 DEBUG [org.jboss.ejb.client.invocation] (default task-19) Received MODULE_AVAILABLE(8) message for module /server-side
> 04:04:25,324 TRACE [org.jboss.ejb.client.invocation] (default task-7) Performed first-match discovery(target affinity(node) = localhost, destination = remote+http://10.8.246.90:8080)
> 04:04:25,325 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from SENDING to SENT (org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:450))
> 04:04:25,326 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from SENT to WAITING (org.jboss.ejb.client.EJBClientInvocationContext.sendRequestInitial(EJBClientInvocationContext.java:339))
> 04:04:25,345 TRACE [org.jboss.ejb.client] (default task-22) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from WAITING to READY (org.jboss.ejb.client.EJBClientInvocationContext.resultReady(EJBClientInvocationContext.java:646))
> 04:04:25,345 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from READY to CONSUMING (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:546))
> 04:04:25,346 TRACE [org.jboss.ejb.client] (default task-7) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@5ffb94cb from CONSUMING to DONE (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:573))
> {noformat}
> After the first invocation, the bean proxy on server-1 sets it affinity to a ClusterAffinity, which means that the next invocation's destination is picked based on the cluster topology (which contains only 0.0.0.0). It will most likely fail, and after this, the affinity seems to be reset back to None, therefore we have a loop where always one invocation works correctly and the following one fails.
> The following is the log observed on server-1 when an invocation tries to go to 0.0.0.0 (so it either fails with connection refused, or server-1 tries to invoke itself in case that it's listening on 0.0.0.0 too)
> {noformat}
> 04:04:26,485 DEBUG [org.jboss.ejb.client.invocation] (default task-24) Calling invoke(module = /server-side/WhoAmIBean, strong affinity = Cluster "ejb", weak affinity = None):
> 04:04:26,485 TRACE [org.jboss.ejb.client.invocation] (default task-24) Calling executeDiscovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None)
> 04:04:26,486 TRACE [org.jboss.ejb.client.invocation] (default task-24) Performing cluster discovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None, filter spec = (&(cluster=ejb)))
> 04:04:26,486 TRACE [org.jboss.ejb.client.invocation] (default task-24) EJB discovery provider: attempting to connect to configured connection remote+http://10.8.246.90:8080
> 04:04:26,488 TRACE [org.jboss.ejb.client.invocation] (default task-24) EJB discovery provider: attempting to connect to cluster ejb connection remote+http://0.0.0.0:8080
> 04:04:26,492 TRACE [org.jboss.ejb.client.invocation] (default task-24) Performed cluster discovery (target affinity = Node "localhost", destination = remote+http://0.0.0.0:8080)
> 04:04:26,493 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENDING to SENT (org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:450))
> 04:04:26,495 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENT to WAITING (org.jboss.ejb.client.EJBClientInvocationContext.sendRequestInitial(EJBClientInvocationContext.java:339))
> 04:04:26,497 TRACE [org.jboss.ejb.client] (default task-32) Invocation marked failed, state is currently: WAITING
> 04:04:26,498 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from WAITING to CONSUMING (org.jboss.ejb.client.EJBClientInvocationContext.failed(EJBClientInvocationContext.java:975))
> 04:04:26,498 TRACE [org.jboss.ejb.client.invocation] (default task-32) Blacklisting destination (locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None, missing target = remote+http://0.0.0.0:8080)
> 04:04:26,499 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from CONSUMING to SENDING (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:600))
> 04:04:26,499 TRACE [org.jboss.ejb.client.invocation] (default task-32) Calling executeDiscovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None)
> 04:04:26,499 TRACE [org.jboss.ejb.client.invocation] (default task-32) Performing cluster discovery(locator = StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb", weak affinity = None, filter spec = (&(cluster=ejb)))
> 04:04:26,501 TRACE [org.jboss.ejb.client.invocation] (default task-32) Performed cluster discovery, nodes is empty; trying an initial
> 04:04:26,502 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENDING to SENT (org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:442))
> 04:04:26,503 TRACE [org.jboss.ejb.client] (default task-32) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from SENT to READY (org.jboss.ejb.client.EJBClientInvocationContext.sendRequestInitial(EJBClientInvocationContext.java:380))
> 04:04:26,503 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from READY to CONSUMING (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:546))
> 04:04:26,503 TRACE [org.jboss.ejb.client] (default task-24) Will not retry (requested = false, remaining = 0)
> 04:04:26,504 TRACE [org.jboss.ejb.client] (default task-24) Transitioning org.jboss.ejb.client.EJBClientInvocationContext@386576b9 from CONSUMING to DONE (org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:613))
> 04:04:26,505 ERROR [org.jboss.as.ejb3.invocation] (default task-24) WFLYEJB0034: EJB Invocation failed on component Intermediate for method public abstract java.lang.String example.ejb.WhoAmIBeanRemote.whoAmI(): javax.ejb.NoSuchEJBException: EJBCLIENT000079: Unable to discover destination for request for EJB StatelessEJBLocator for "/server-side/WhoAmIBean", view is interface example.ejb.WhoAmIBeanRemote, affinity is Cluster "ejb"
> (... rest of the error omitted, but it is a "connection refused")
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3180) Split RuleUnitRegistry
by Tibor Zimányi (Jira)
Tibor Zimányi created DROOLS-3180:
-------------------------------------
Summary: Split RuleUnitRegistry
Key: DROOLS-3180
URL: https://issues.jboss.org/browse/DROOLS-3180
Project: Drools
Issue Type: Enhancement
Components: core engine
Affects Versions: 7.13.0.Final
Reporter: Tibor Zimányi
Assignee: Tibor Zimányi
RuleUnitRegistry is currently used for two purposes:
- In KnowledgeBaseImpl as an aggregator of RuleUnitDescrs
- In KnowledgePackageImpl as a loader of RuleUnitDescrs
This is a bit confusing, because a class serves different purposes, so it needs to be split in two to encapsulate the different behaviours.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months