[JBoss JIRA] (WFCORE-3310) mechanism-configuration in http/sasl authentication factory in server configuration should fail when includes some attribute
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFCORE-3310?page=com.atlassian.jira.plugi... ]
Martin Choma commented on WFCORE-3310:
--------------------------------------
When now extra attributes are ignored in whole standalone.xml configuration, change (if ever made) should be as well global . Probably worst we can do is to make exceptions from global rule.
Another argument for justification, when editing model through management API (recommended approach) this should not happen at all. Users should not edit standalone.xml manually.
But when they do and there is a typo in attribute, this will let him know. Now it just silently continues. So that is when this feature become useful.
> mechanism-configuration in http/sasl authentication factory in server configuration should fail when includes some attribute
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3310
> URL: https://issues.jboss.org/browse/WFCORE-3310
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Affects Versions: 3.0.3.Final
> Reporter: Ondrej Lukas
> Assignee: Jiri Ondrusek
> Priority: Major
>
> Based on wildfly-elytron XSD mechanism-configuration element of http-authentication-factory or sasl-authentication-factory should not contain any attribute. However when some attribute is added for this element in standalone.xml then it does not fail during server start. In correct behavior Validation error should be thrown during starting server.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3412) Performance degradation with session pools
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3412?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-3412:
--------------------------------
Sprint: 2018 Week 48-50
> Performance degradation with session pools
> ------------------------------------------
>
> Key: DROOLS-3412
> URL: https://issues.jboss.org/browse/DROOLS-3412
> Project: Drools
> Issue Type: Bug
> Reporter: Christian Liebhardt
> Assignee: Mario Fusco
> Priority: Major
> Attachments: gc.png
>
>
> Hello,
> We've today updates to Drools 7.15 and as discussed with DROOLS-3228 we changed our code from calling _StatefulKnowledgeSessionImpl.reset_ ourselves to _KieSessionsPool_. However we then recognized that our application quickly became slower and slower over time (roughly after a few minutes of uptime, or a couple of hundred session create/dispose cycles).
> I haven't yet found the reason what is causing the slow down. However I think there is a difference in how we reset our sessions before session pools and how session pools do it. Perhaps that is a lead.
> *What we did*
> # Create a session
> # Use the session
> # Dispose and reset the session and go back to 2 for the next facts
> *What happens with session pools*
> # Create a session
> # Use the session
> # Skip dispose (because of _pool != null_ in the dispose method), reset the session and go back to 2 for the next facts
> So the difference seems to be that with session pools the session doesn't get disposed before reset it called. If I do the same without session pools then I also see the same slow down. So it seems that something is left behind and causes a slow down. The results however seem to be correct, so the right consequences appear to be triggered.
> An example on how we use the session pool can be found here: https://github.com/liebharc/JavaRules/blob/master/src/main/java/com/githu...
> Thanks once more for your help.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3406) [DMN Designer] Decision Service splitter should be movable
by Roger Martínez (Jira)
[ https://issues.jboss.org/browse/DROOLS-3406?page=com.atlassian.jira.plugi... ]
Roger Martínez edited comment on DROOLS-3406 at 12/9/18 9:46 PM:
-----------------------------------------------------------------
Hey [~manstis], here are some comments:
* If you recall correctly in Stunner we have "viewers", "editors", and other kind of "working modes" available. So they way this works is usually via "CanvasControl"'s, by enabling or disabling them for each case, or at least that's the way it was initially designed... hehe. So this is why I would recommend doing your work, if makes sense, by mixing code in some existing/new canvas control type and/or the shape view instance if self. This way, for example, you can just enable your control in case of edit mode, and keep it not available when just "vieweing" the diagram
* This way the idea is to add as much logic as possible in the CanvasControl rather than in the ShapeView itself, allowing this way to handle this new feature with the canvas control API. For example we use to handle all events and user interactions in the control classes, rather than on the shape views
* Anyway I know that word is not ideal and sometimes it's necessary to add custom logic on top of the ShapeView, which is also usually built and generated automatically by the SVG annotation processor. This ability was also missing for the new Case Modeller editor, which is using SVG views and also provides custom logic on top of ShapeView. So you can do this, if applies for you, in the same way. The idea is:
** Create a custom _ShapeViewBuilder_ and use in your _SVGViewFactory_ declaration, by specifying it in the _builder_ field. Eg: [CaseManagementSVGViewFactory|https://github.com/kiegroup/kie-wb-common/bl...]
** This way you can also create a custom ShapeView type, for example as the [CaseManagementShapeView|https://github.com/kiegroup/kie-wb-common/blob/ma...], which is being built in your custom _ShapeViewBuilder_.
** By following this, you can then _cast_ the _ShapeView_, in your _CanvasHandler_ type or any of your custom components, from ShapeView to your concrete implementation.
So hope this helps a bit. Feel tree to ask for whatever you need or if any Qs, np!!
Thanks!
was (Author: roger600):
Hey [~manstis], here are some comments:
* If you recall correctly in Stunner we have "viewers", "editors", and other kind of "working modes" available. So they way this works is usually via "CanvasControl"'s, by enabling or disabling them for each case, or at least that's the way it was initially designed... hehe. So this is why I would recommend doing your work, if makes sense, by mixing code in some existing/new canvas control type and/or the shape view instance if self. This way, for example, you can just enable your control in case of edit mode, and keep it not available when just "vieweing" the diagram
* This way the idea is to add as much logic as possible in the CanvasControl rather than in the ShapeView itself, allowing this way to handle this new feature with the canvas control API. For example we use to handle all events and user interactions in the control classes, rather than on the shape views
* Anyway I know that word is not ideal and sometimes it's necessary to add custom logic on top of the ShapeView, which is also usually built and generated automatically by the SVG annotation processor. This ability was also already necessary for the new Case Modeller editor, which is using SVG views and also provides custom logic on top of ShapeView. So you can do this, if applies for you, in the same way. The idea is:
** Create a custom _ShapeViewBuilder_ and use in your _SVGViewFactory_ declaration, by specifying it in the _builder_ field. Eg: [CaseManagementSVGViewFactory|https://github.com/kiegroup/kie-wb-common/bl...]
** This way you can also create a custom ShapeView type, for example as the [CaseManagementShapeView|https://github.com/kiegroup/kie-wb-common/blob/ma...], which is being built in your custom _ShapeViewBuilder_.
** By following this, you can then _cast_ the _ShapeView_, in your _CanvasHandler_ type or any of your custom components, from ShapeView to your concrete implementation.
So hope this helps a bit. Feel tree to ask for whatever you need or if any Qs, np!!
Thanks!
> [DMN Designer] Decision Service splitter should be movable
> ----------------------------------------------------------
>
> Key: DROOLS-3406
> URL: https://issues.jboss.org/browse/DROOLS-3406
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> The _splitter_ within a Decision Service is static.
> It needs to be movable (vertically) maintaining it's alignment with the Decision Service bounds. At this point we need to either decide to add _result_ decision(s) and _encapsulated_ decisions to the Decision Service by Command (depending on where the node is dropped) or update the Marshaller to determine the type of decision based on its vertical positioning and location of the _splitter_.
> h2. Acceptance test
> Decision state is updated according to _splitter_ movement. Example if area of result decision expanded so some decision belongs there now, this decision should have state _rusult decision_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3406) [DMN Designer] Decision Service splitter should be movable
by Roger Martínez (Jira)
[ https://issues.jboss.org/browse/DROOLS-3406?page=com.atlassian.jira.plugi... ]
Roger Martínez commented on DROOLS-3406:
----------------------------------------
Hey [~manstis], here are some comments:
* If you recall correctly in Stunner we have "viewers", "editors", and other kind of "working modes" available. So they way this works is usually via "CanvasControl"'s, by enabling or disabling them for each case, or at least that's the way it was initially designed... hehe. So this is why I would recommend doing your work, if makes sense, by mixing code in some existing/new canvas control type and/or the shape view instance if self. This way, for example, you can just enable your control in case of edit mode, and keep it not available when just "vieweing" the diagram
* This way the idea is to add as much logic as possible in the CanvasControl rather than in the ShapeView itself, allowing this way to handle this new feature with the canvas control API. For example we use to handle all events and user interactions in the control classes, rather than on the shape views
* Anyway I know that word is not ideal and sometimes it's necessary to add custom logic on top of the ShapeView, which is also usually built and generated automatically by the SVG annotation processor. This ability was also already necessary for the new Case Modeller editor, which is using SVG views and also provides custom logic on top of ShapeView. So you can do this, if applies for you, in the same way. The idea is:
** Create a custom _ShapeViewBuilder_ and use in your _SVGViewFactory_ declaration, by specifying it in the _builder_ field. Eg: [CaseManagementSVGViewFactory|https://github.com/kiegroup/kie-wb-common/bl...]
** This way you can also create a custom ShapeView type, for example as the [CaseManagementShapeView|https://github.com/kiegroup/kie-wb-common/blob/ma...], which is being built in your custom _ShapeViewBuilder_.
** By following this, you can then _cast_ the _ShapeView_, in your _CanvasHandler_ type or any of your custom components, from ShapeView to your concrete implementation.
So hope this helps a bit. Feel tree to ask for whatever you need or if any Qs, np!!
Thanks!
> [DMN Designer] Decision Service splitter should be movable
> ----------------------------------------------------------
>
> Key: DROOLS-3406
> URL: https://issues.jboss.org/browse/DROOLS-3406
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Affects Versions: 7.15.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> The _splitter_ within a Decision Service is static.
> It needs to be movable (vertically) maintaining it's alignment with the Decision Service bounds. At this point we need to either decide to add _result_ decision(s) and _encapsulated_ decisions to the Decision Service by Command (depending on where the node is dropped) or update the Marshaller to determine the type of decision based on its vertical positioning and location of the _splitter_.
> h2. Acceptance test
> Decision state is updated according to _splitter_ movement. Example if area of result decision expanded so some decision belongs there now, this decision should have state _rusult decision_
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-10864) MP Health reports UP when there is port collision for port 8080
by Lin Gao (Jira)
[ https://issues.jboss.org/browse/WFLY-10864?page=com.atlassian.jira.plugin... ]
Lin Gao reassigned WFLY-10864:
------------------------------
Assignee: Lin Gao (was: Jeff Mesnil)
> MP Health reports UP when there is port collision for port 8080
> ---------------------------------------------------------------
>
> Key: WFLY-10864
> URL: https://issues.jboss.org/browse/WFLY-10864
> Project: WildFly
> Issue Type: Bug
> Components: MP Health
> Reporter: Rostislav Svoboda
> Assignee: Lin Gao
> Priority: Critical
>
> MP Health reports UP when there is port collision for port 8080.
> I have simple python app to acquire port 8080 and once it runs I start WF server
> {code}
> import SimpleHTTPServer
> import SocketServer
> PORT = 8080
> Handler = SimpleHTTPServer.SimpleHTTPRequestHandler
> httpd = SocketServer.TCPServer(("127.0.0.1", PORT), Handler)
> print "serving at port", PORT
> httpd.serve_forever()
> {code}
> WF reports Address already in use /127.0.0.1:8080, deployments are not deployed.
> Accessing http://localhost:9990/health/ reports "outcome":"UP"
> I think this is wrong and DOWN should be reported.
> Spec is misleading because it says {{A producer without health check procedures installed MUST returns positive overall outcome (i.e. HTTP 200)}} but it silently assumes server started correctly.
> I believe authors of the spec expected that if there is some trouble like port collision the server doesn't start, WildFly is a bit further as it allows to boot even if some services are not started properly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months