[JBoss JIRA] (WFLY-6610) Default singleton policy capability needs distinct name
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-6610:
----------------------------------
Summary: Default singleton policy capability needs distinct name
Key: WFLY-6610
URL: https://issues.jboss.org/browse/WFLY-6610
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 10.1.0.Final
Currently, the "org.wildfly.clustering.singleton.policy" capability name is used by 2 capabilities:
1. The default singleton policy, using the static name
2. A named singleton policy, using a dynamic name
Even though this works, it's not future-proof, as determined by a chat session from today:
{noformat}
Paul Ferraro·15:11
@BrianStansberry question - is it valid for a capability to be both static and dynamic?
@BrianStansberry e.g. I have 2 resources, one registers a capability using a static name, the other resource registers a capability using the same name, but dynamic
@BrianStansberry it works fine - but it occurs to me, when completing my capability.adoc, that the DYNAMIC field is intended to be true or false - not both
@BrianStansberry I could certainly use a different name for the static variant, but I'm wondering if that is really necessary
Brian Stansberry·15:17
@PaulFerraro the intent is they have different names
basically because for a dynamic capability the way you learn its contract is by looking up the static part of the name
I suppose if the static and dynamic had the same contract except for that one piece of data it could be ok
but it sounds like something that some day would bite us in the rear
Paul Ferraro·15:18
@BrianStansberry an example of this is the SingletonPolicy capability
@BrianStansberry there are named policies (i.e. dynamic), and there is the default policy, which references a named policy, but registers itself using the same name (but is static)
Brian Stansberry·15:20
hmm, yeah i can see the advantage of just using the static name
Paul Ferraro·15:20
so, a dependency on org.wildfly.clustering.singleton.policy gives you the default policy, but a dependency on so, a dependency on org.wildfly.clustering.singleton.policy.foo gives you the foo policy
Brian Stansberry·15:21
is org.wildfly.clustering.singleton.default-policy better?
I'd need to poke a bit to see if I can identify any real problems
I mean the registry info could just say (in template.adoc) DYNAMIC: true | false | both
or something
Paul Ferraro·15:22Hide card
I used "both", https://github.com/wildfly/wildfly-capabilities/pull/4
Add missing capability description for singleton policy. by pferraro · Pull Request #4 · wildfly/wildfly-capabilities
github.com
wildfly-capabilities - Registry of capabilities accessible via the management layer of a WildFly Core base server
Brian Stansberry·15:22
the capability names are just string so the dynamic business is just string concatenation
hmm, maybe it would be a problem with the "possible" capability thing
Paul Ferraro·15:23
"possible"?
what is that?
Brian Stansberry·15:24
caps are declared in the ResourceDefintion. so when the RD is used to create a ManagementResourceRegistration, the cap info is associated with the MRR
and is part of the resource def metadata
but, for a typical MRR there is no dynamic part
the point of all this is tools that are trying to help a user create a config can see which addresses could provide the cap if a resource was added
i.e. what caps are "possible" given the set of extensions that are available
but your case becomes ambiguous
maybe that's not a big problem; it's kind of a question of data representation
Brian Stansberry goes to look how it's displayed now
Brian Stansberry·15:29
ok, good so far; it's a list not a map keyed on the static cap name:
[standalone@embedded socket-binding=management-http] :read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "Configuration information for a socket.",
"capabilities" => [{
"name" => "org.wildfly.network.socket-binding",
"dynamic" => true
}],
Show more
Alexey Loubyansky joined the room
Brian Stansberry·15:30
@ctomc @HaraldPehl I'm curious what your thoughts are on ^^^ (tomorrow is fine)
Paul Ferraro·15:33
@BrianStansberry Here are the resource descriptions containing the singleton policy capability:
[standalone@localhost:9990 /] /subsystem=singleton:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "The configuration of the singleton subsystem",
"capabilities" => [{
"name" => "org.wildfly.clustering.singleton.policy",
"dynamic" => false
}],
"attributes" => {"default" => {
"type" => STRING,
"description" => "The default singleton policy",
"expressions-allowed" => false,
"nillable" => false,
"capability-reference" => "org.wildfly.clustering.singleton.policy",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
}},
"operations" => undefined,
"notifications" => undefined,
"children" => {"singleton-policy" => {
"description" => "A singleton policy",
"model-description" => undefined
}}
}
}
[standalone@localhost:9990 /] /subsystem=singleton/singleton-policy=default:read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "A singleton policy",
"capabilities" => [{
"name" => "org.wildfly.clustering.singleton.policy",
"dynamic" => true
}],
"attributes" => {
"cache" => {
"type" => STRING,
"description" => "The cache backing the singleton policy's singleton service",
"expressions-allowed" => true,
"nillable" => true,
"default" => "default",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"cache-container" => {
"type" => STRING,
"description" => "The cache container backing the singleton policy's singleton service",
"expressions-allowed" => true,
"nillable" => false,
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
},
"quorum" => {
"type" => INT,
"description" => "The minimum number of nodes required before this singleton service will start",
"expressions-allowed" => true,
"nillable" => true,
"default" => 1,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"
}
},
"operations" => undefined,
"notifications" => undefined,
"children" => {"election-policy" => {
"description" => "The election policy of this singleton policy",
"model-description" => undefined
}}
}
}
Show more
Kabir Khan joined the room
Brian Stansberry·15:34
@PaulFerraro ok, so there it's not even the same MRR registering both variants, so list vs map doesn't matter
I think @HaraldPehl 's input is important as he's the one who'd need to deal with this situation
the fact that the same string can have two different meanings
it may not be a big deal for what he's doing now though
which is probably focused on giving people the valid values for attributes
and those are always for dynamic caps
Harald Pehl·15:45
@BrianStansberry For me it's important to get the possible resources for an attribute which declares a "capability-reference" in its metadata
For instance the "profile" attribute in "/server-group=*:read-resource-description" has a "capability-reference" => "org.wildfly.domain.profile"
So I need a way to resolve this reference to a list of resource names which the admin can select from
Brian Stansberry·15:50
@HaraldPehl thanks. that confirms what I thought; for right now you need to find out dynamic capabilities
I think the tricky thing for you would be if the string "org.wildfly.domain.profile" appeared in two different forms, one dynamic (the one you want) and one static (irrelevant to you)
you'd have to dig a bit deeper to make sure you were looking at the right one
@BrianStansberry I think that is addressed by @ctomc PR: https://github.com/wildfly/wildfly-core/pull/1554
WFCORE-1540 Expose capability registry via mgmt api by ctomc · Pull Request #1554 · wildfly/wildfly-core
github.com
wildfly-core - The core runtime that is used by the Wildfly application server
Harald Pehl·15:53
It introduces some mgmt ops to query capabilities
Harald Pehl·15:54
1. /core-service=capability-registry:read-resource which returns a list of
possible capabilities
2. /core-service=capability-registry:get-provider-points(name=org.wildfly.domain.profile)
Harald Pehl·15:56
which returns the address for a given capability
Brian Stansberry·15:56
@HaraldPehl with what @PaulFerraro is proposing, you'd probably need a 2nd param for your #2
and probably some more parsing of the result of your #1 to get the particular data you want
"probably" as I'm just guessing what you do with #1
Harald Pehl·15:58
I use #1 to bootstrap a registry of all known capabilities when the console starts
Brian Stansberry·15:58
does that registry include whether the cap is dynamic?
Harald Pehl·15:58
and #2 if I cannot find a capability in that registry
yes
Brian Stansberry·15:59
is the name the registry key?
Harald Pehl·16:00
yes its actually a Map<String, CapabilityInfo> with the capability name as key and some info about that cap as value (including dynamic)
Brian Stansberry·16:01
yeah, so you need some kind of custom type as the key, or a List<CapabilityInfo> as the value
tbh @PaulFerraro doing this sounds like a likely bug nest
Harald, I should have said "you *would* need..." -- you don't now
Paul Ferraro·16:02
@BrianStansberry ok - I'll give the static capabilities a separate name
Kabir Khan joined the room
Paul Ferraro·16:03
not a huge deal - just one more capability name to keep track of
Brian Stansberry·16:04
yeah, it's a good thought though. perhaps it will be easier for users anyway, since 2 names for two things may require less brainpower to understand
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6599) JDBC_PING can't use a JNDI database connection because it is closed on shutdown
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6599?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-6599 at 5/12/16 4:31 PM:
---------------------------------------------------------------
The problem here is the missing dependency establishement (i.e. JNDI lookup doesn't guarantee any lifecycle coupling). This needs to ideally make use of capabilities API, expose datasource reference in the model (rather than a property) and also require a change in JGroups to be able to supply datasource directly (rather than JNDI lookup).
was (Author: rhusar):
The problem here is the missing dependency being established. This needs to ideally make use of capabilities API, expose datasource reference in the model (rather than a property) and also require a change in JGroups to be able to supply datasource directly (rather than JNDI lookup).
> JDBC_PING can't use a JNDI database connection because it is closed on shutdown
> -------------------------------------------------------------------------------
>
> Key: WFLY-6599
> URL: https://issues.jboss.org/browse/WFLY-6599
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Matthew Casperson
> Assignee: Radoslav Husar
>
> If you configure the JDBC_PING protocol in JGroups to use a datasource provided by WildFly via the *datasource_jndi_name* setting, you'll get the following exception when WildFly is shutdown:
> {code}
> [Server:main-server] 2016-05-10 11:05:45+1000 ERROR [[org.jgroups.protocols.JDBC_PING]] [[MSC service thread 1-4]] Could not open connection to database: java.sql.SQLException: javax.resource.ResourceException: IJ000470: You are trying to use a connection factory that has been shut down: java:/comp/env/jdbc/jgroups
> [Server:main-server] at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:146)
> [Server:main-server] at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:66)
> [Server:main-server] at org.jgroups.protocols.JDBC_PING.getConnection(JDBC_PING.java:348)
> [Server:main-server] at org.jgroups.protocols.JDBC_PING.delete(JDBC_PING.java:379)
> [Server:main-server] at org.jgroups.protocols.JDBC_PING.deleteSelf(JDBC_PING.java:395)
> [Server:main-server] at org.jgroups.protocols.JDBC_PING.stop(JDBC_PING.java:144)
> [Server:main-server] at org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:1015)
> [Server:main-server] at org.jgroups.JChannel.stopStack(JChannel.java:1002)
> [Server:main-server] at org.jgroups.JChannel.disconnect(JChannel.java:373)
> [Server:main-server] at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.stop(ChannelConnectorBuilder.java:103)
> [Server:main-server] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
> [Server:main-server] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
> [Server:main-server] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:main-server] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:main-server] at java.lang.Thread.run(Thread.java:745)
> [Server:main-server] Caused by: javax.resource.ResourceException: IJ000470: You are trying to use a connection factory that has been shut down: java:/comp/env/jdbc/jgroups
> [Server:main-server] at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:735)
> [Server:main-server] at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
> [Server:main-server] ... 14 more
> {code}
> The solution is to configure the database connection directly, but then it seems that you loose the ability to use features like database connection validation, reconnection and the other settings provided by a WildFly datasource the improve the reliability of a database connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6599) JDBC_PING can't use a JNDI database connection because it is closed on shutdown
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6599?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-6599:
--------------------------------------
The problem here is the missing dependency being established. This needs to ideally make use of capabilities API, expose datasource reference in the model (rather than a property) and also require a change in JGroups to be able to supply datasource directly (rather than JNDI lookup).
> JDBC_PING can't use a JNDI database connection because it is closed on shutdown
> -------------------------------------------------------------------------------
>
> Key: WFLY-6599
> URL: https://issues.jboss.org/browse/WFLY-6599
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Matthew Casperson
> Assignee: Radoslav Husar
>
> If you configure the JDBC_PING protocol in JGroups to use a datasource provided by WildFly via the *datasource_jndi_name* setting, you'll get the following exception when WildFly is shutdown:
> {code}
> [Server:main-server] 2016-05-10 11:05:45+1000 ERROR [[org.jgroups.protocols.JDBC_PING]] [[MSC service thread 1-4]] Could not open connection to database: java.sql.SQLException: javax.resource.ResourceException: IJ000470: You are trying to use a connection factory that has been shut down: java:/comp/env/jdbc/jgroups
> [Server:main-server] at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:146)
> [Server:main-server] at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:66)
> [Server:main-server] at org.jgroups.protocols.JDBC_PING.getConnection(JDBC_PING.java:348)
> [Server:main-server] at org.jgroups.protocols.JDBC_PING.delete(JDBC_PING.java:379)
> [Server:main-server] at org.jgroups.protocols.JDBC_PING.deleteSelf(JDBC_PING.java:395)
> [Server:main-server] at org.jgroups.protocols.JDBC_PING.stop(JDBC_PING.java:144)
> [Server:main-server] at org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:1015)
> [Server:main-server] at org.jgroups.JChannel.stopStack(JChannel.java:1002)
> [Server:main-server] at org.jgroups.JChannel.disconnect(JChannel.java:373)
> [Server:main-server] at org.wildfly.clustering.jgroups.spi.service.ChannelConnectorBuilder.stop(ChannelConnectorBuilder.java:103)
> [Server:main-server] at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
> [Server:main-server] at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
> [Server:main-server] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [Server:main-server] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [Server:main-server] at java.lang.Thread.run(Thread.java:745)
> [Server:main-server] Caused by: javax.resource.ResourceException: IJ000470: You are trying to use a connection factory that has been shut down: java:/comp/env/jdbc/jgroups
> [Server:main-server] at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:735)
> [Server:main-server] at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:138)
> [Server:main-server] ... 14 more
> {code}
> The solution is to configure the database connection directly, but then it seems that you loose the ability to use features like database connection validation, reconnection and the other settings provided by a WildFly datasource the improve the reliability of a database connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6609) STOMP netty connector failing when a messaging cluster node drops out.
by Chris Orser (JIRA)
Chris Orser created WFLY-6609:
---------------------------------
Summary: STOMP netty connector failing when a messaging cluster node drops out.
Key: WFLY-6609
URL: https://issues.jboss.org/browse/WFLY-6609
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 10.0.0.Final
Reporter: Chris Orser
Assignee: Jeff Mesnil
If a client uses STOMP to publish or subscribe to the messaging server the client will cease to function when a messaging server node drops out of the cluster. They will only work again once the cluster has been fully terminated and at least one instance is brought back online.
The error I received when sending messages:
"AMQ339001: Destination does not exist: <queue_name>"
lead me to a bug report ARTEMIS-358
I built an Artemis 1.3 snapshot and the problem has been solved. I don't know if that particular bug was the cause but they have addressed the issue in an upcoming version of Artemis.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6608) Not clear which input fields are required in resouce adapter add dialog
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-6608?page=com.atlassian.jira.plugin.... ]
Chao Wang updated WFLY-6608:
----------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/8911 (was: https://github.com/hal/core/pull/207, https://github.com/hal/core/pull/208)
> Not clear which input fields are required in resouce adapter add dialog
> -----------------------------------------------------------------------
>
> Key: WFLY-6608
> URL: https://issues.jboss.org/browse/WFLY-6608
> Project: WildFly
> Issue Type: Enhancement
> Affects Versions: 10.0.0.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> It is not clear which of inputs are required when I want to add new resource adapter. Only name is marked as required, but when I fill only name this error message appears:
> {code}
> Unexpected HTTP response: 500
> Request
> {
> "name" => "foobar",
> "archive" => undefined,
> "module" => undefined,
> "transaction-support" => undefined,
> "operation" => "add",
> "address" => [
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "foobar")
> ]
> }
> Response
> Internal Server Error
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0077: At least one of ARCHIVE or MODULE is required",
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFLY-6608) Not clear which input fields are required in resouce adapter add dialog
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-6608?page=com.atlassian.jira.plugin.... ]
Chao Wang moved HAL-1097 to WFLY-6608:
--------------------------------------
Project: WildFly (was: HAL)
Key: WFLY-6608 (was: HAL-1097)
Issue Type: Enhancement (was: Bug)
Workflow: GIT Pull Request workflow (was: classic default workflow)
Steps to Reproduce: (was: # Run EAP
# Navigate to resource adapters (Subsystems->Resource Adapters)
# Click on add
# Fill only name
# Click on save)
Affects Version/s: 10.0.0.Final
(was: 2.8.23.Final)
> Not clear which input fields are required in resouce adapter add dialog
> -----------------------------------------------------------------------
>
> Key: WFLY-6608
> URL: https://issues.jboss.org/browse/WFLY-6608
> Project: WildFly
> Issue Type: Enhancement
> Affects Versions: 10.0.0.Final
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> It is not clear which of inputs are required when I want to add new resource adapter. Only name is marked as required, but when I fill only name this error message appears:
> {code}
> Unexpected HTTP response: 500
> Request
> {
> "name" => "foobar",
> "archive" => undefined,
> "module" => undefined,
> "transaction-support" => undefined,
> "operation" => "add",
> "address" => [
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "foobar")
> ]
> }
> Response
> Internal Server Error
> {
> "outcome" => "failed",
> "failure-description" => "WFLYJCA0077: At least one of ARCHIVE or MODULE is required",
> "rolled-back" => true
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-483) Allow hooking into logging subsystem through Management API
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-483?page=com.atlassian.jira.plugin... ]
James Perkins closed WFCORE-483.
--------------------------------
Resolution: Won't Do
More than likely yes. I'll go ahead and close this as really log messages are not the way to determine server liveness anyway.
> Allow hooking into logging subsystem through Management API
> -----------------------------------------------------------
>
> Key: WFCORE-483
> URL: https://issues.jboss.org/browse/WFCORE-483
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging
> Reporter: Ondrej Zizka
> Assignee: James Perkins
> Priority: Optional
> Labels: logging
>
> Provide a way to poll log messages through the management API.
> Could be then used in the AS console. Some kind of detached window, or perhaps tab, with log, perhaps pushed through Servlet 3.2's onDataAvailable() ...
> Note that this is different from AS7-2213, which needs AS to keep some history. This doesn't.
> BTW, JBDS gets the logs through SSH, because the AS may fail booting before anything is able to hook in like this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (WFCORE-483) Allow hooking into logging subsystem through Management API
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-483?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-483:
-----------------------------------------
This sounds like a use case for management notifications.
> Allow hooking into logging subsystem through Management API
> -----------------------------------------------------------
>
> Key: WFCORE-483
> URL: https://issues.jboss.org/browse/WFCORE-483
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging
> Reporter: Ondrej Zizka
> Assignee: James Perkins
> Priority: Optional
> Labels: logging
>
> Provide a way to poll log messages through the management API.
> Could be then used in the AS console. Some kind of detached window, or perhaps tab, with log, perhaps pushed through Servlet 3.2's onDataAvailable() ...
> Note that this is different from AS7-2213, which needs AS to keep some history. This doesn't.
> BTW, JBDS gets the logs through SSH, because the AS may fail booting before anything is able to hook in like this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (DROOLS-1174) Regression score corruption in dinner party probably due PLANNER-488
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1174?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1174:
-------------------------------------
Description:
to reproduce run DinnerPartySolveAllTurtleTest with VM option -DrunTurtleTests=true in optaplanner-examples.
{code}
2016-05-12 16:06:02,121 [main] INFO Opened: data/dinnerparty/unsolved/wedding01.xml
2016-05-12 16:06:02,226 [main] TRACE Model annotations parsed for Solution DinnerParty:
2016-05-12 16:06:02,226 [main] TRACE Entity SeatDesignation:
2016-05-12 16:06:02,226 [main] TRACE Variable seat (genuine)
2016-05-12 16:06:03,436 [main] INFO Solving started: time spent (137), best score (144uninitialized/-14400), environment mode (NON_INTRUSIVE_FULL_ASSERT), random (JDK with seed 0).
2016-05-12 16:06:03,913 [main] DEBUG Custom step (0), time spent (615), score (-2890), new best score (-2890).
2016-05-12 16:06:03,913 [main] INFO Custom phase (0) ended: step total (1), time spent (615), best score (-2890), score calculation speed (11050/sec).
2016-05-12 16:06:03,937 [main] TRACE Created cachedMoveList: size (10368), moveSelector (Shuffling(Filtering(SwapMoveSelector(FromSolutionEntitySelector(SeatDesignation), FromSolutionEntitySelector(SeatDesignation))))).
2016-05-12 16:06:03,941 [main] TRACE Shuffled cachedMoveList with size (10368) in moveSelector(Shuffling(Filtering(SwapMoveSelector(FromSolutionEntitySelector(SeatDesignation), FromSolutionEntitySelector(SeatDesignation))))).
2016-05-12 16:06:03,950 [main] TRACE Move index (0), score (-2890), accepted (true), move (Grayson {1.4} <-> Oliver {0.4}).
2016-05-12 16:06:03,957 [main] TRACE Move index (1), score (-2890), accepted (true), move (James {10.4} <-> Cameron {10.10}).
java.lang.IllegalStateException: Score corruption: the workingScore (-3190) is not the uncorruptedScore (-3090) after completedAction (Eliana {8.9} <-> Allison {9.3}):
The corrupted scoreDirector has 1 ConstraintMatch(s) which are in excess (and should not be there):
org.optaplanner.examples.dinnerparty.solver/twoSameJobTypePerTable/level0/[8, SOCIALITE]=-100
The corrupted scoreDirector has no ConstraintMatch(s) which are missing.
Check your score constraints.
at org.optaplanner.core.impl.score.director.AbstractScoreDirector.assertWorkingScoreFromScratch(AbstractScoreDirector.java:418)
at org.optaplanner.core.impl.solver.scope.DefaultSolverScope.assertWorkingScoreFromScratch(DefaultSolverScope.java:118)
at org.optaplanner.core.impl.phase.scope.AbstractPhaseScope.assertWorkingScoreFromScratch(AbstractPhaseScope.java:156)
at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.processMove(LocalSearchDecider.java:167)
at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.doMove(LocalSearchDecider.java:153)
at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.decideNextStep(LocalSearchDecider.java:125)
at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.solve(DefaultLocalSearchPhase.java:63)
at org.optaplanner.core.impl.solver.DefaultSolver.runPhases(DefaultSolver.java:229)
at org.optaplanner.core.impl.solver.DefaultSolver.solve(DefaultSolver.java:191)
at org.optaplanner.examples.common.app.SolveAllTurtleTest.buildAndSolve(SolveAllTurtleTest.java:75)
at org.optaplanner.examples.common.app.SolveAllTurtleTest.runFastAndFullAssert(SolveAllTurtleTest.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
{code}
I enabled trace logging above, it happens in the 3th move of the first step.
It seems like this rule is responsible:
{code}
// 1 democrat and 1 republican = 2 politians at each table but NOT two of the same kind
// 2 doctors at each table but NOT two of the same kind
// 2 coaches at each table but NOT two of the same kind
// 2 programmers at each table but NOT two of the same kind
// 2 socialites at each table
// 2 teachers at each table
rule "twoSameJobTypePerTable"
when
$jobType : JobType()
$table : Table()
not (
SeatDesignation(guestJobType == $jobType, seatTable == $table, $leftId : id, $firstJob : guestJob)
and SeatDesignation(guestJobType == $jobType, seatTable == $table, id > $leftId,
differentKindIfNeeded($firstJob))
)
then
scoreHolder.addConstraintMatch(kcontext, -100);
end
{code}
was:
to reproduce run DinnerPartySolveAllTurtleTest with VM option -DrunTurtleTests=true in optaplanner-examples.
{code}
2016-05-12 16:06:02,121 [main] INFO Opened: data/dinnerparty/unsolved/wedding01.xml
2016-05-12 16:06:02,226 [main] TRACE Model annotations parsed for Solution DinnerParty:
2016-05-12 16:06:02,226 [main] TRACE Entity SeatDesignation:
2016-05-12 16:06:02,226 [main] TRACE Variable seat (genuine)
2016-05-12 16:06:03,436 [main] INFO Solving started: time spent (137), best score (144uninitialized/-14400), environment mode (NON_INTRUSIVE_FULL_ASSERT), random (JDK with seed 0).
2016-05-12 16:06:03,913 [main] DEBUG Custom step (0), time spent (615), score (-2890), new best score (-2890).
2016-05-12 16:06:03,913 [main] INFO Custom phase (0) ended: step total (1), time spent (615), best score (-2890), score calculation speed (11050/sec).
2016-05-12 16:06:03,937 [main] TRACE Created cachedMoveList: size (10368), moveSelector (Shuffling(Filtering(SwapMoveSelector(FromSolutionEntitySelector(SeatDesignation), FromSolutionEntitySelector(SeatDesignation))))).
2016-05-12 16:06:03,941 [main] TRACE Shuffled cachedMoveList with size (10368) in moveSelector(Shuffling(Filtering(SwapMoveSelector(FromSolutionEntitySelector(SeatDesignation), FromSolutionEntitySelector(SeatDesignation))))).
2016-05-12 16:06:03,950 [main] TRACE Move index (0), score (-2890), accepted (true), move (Grayson {1.4} <-> Oliver {0.4}).
2016-05-12 16:06:03,957 [main] TRACE Move index (1), score (-2890), accepted (true), move (James {10.4} <-> Cameron {10.10}).
java.lang.IllegalStateException: Score corruption: the workingScore (-3190) is not the uncorruptedScore (-3090) after completedAction (Eliana {8.9} <-> Allison {9.3}):
The corrupted scoreDirector has 1 ConstraintMatch(s) which are in excess (and should not be there):
org.optaplanner.examples.dinnerparty.solver/twoSameJobTypePerTable/level0/[8, SOCIALITE]=-100
The corrupted scoreDirector has no ConstraintMatch(s) which are missing.
Check your score constraints.
at org.optaplanner.core.impl.score.director.AbstractScoreDirector.assertWorkingScoreFromScratch(AbstractScoreDirector.java:418)
at org.optaplanner.core.impl.solver.scope.DefaultSolverScope.assertWorkingScoreFromScratch(DefaultSolverScope.java:118)
at org.optaplanner.core.impl.phase.scope.AbstractPhaseScope.assertWorkingScoreFromScratch(AbstractPhaseScope.java:156)
at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.processMove(LocalSearchDecider.java:167)
at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.doMove(LocalSearchDecider.java:153)
at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.decideNextStep(LocalSearchDecider.java:125)
at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.solve(DefaultLocalSearchPhase.java:63)
at org.optaplanner.core.impl.solver.DefaultSolver.runPhases(DefaultSolver.java:229)
at org.optaplanner.core.impl.solver.DefaultSolver.solve(DefaultSolver.java:191)
at org.optaplanner.examples.common.app.SolveAllTurtleTest.buildAndSolve(SolveAllTurtleTest.java:75)
at org.optaplanner.examples.common.app.SolveAllTurtleTest.runFastAndFullAssert(SolveAllTurtleTest.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
{code}
I enabled trace logging above, it happens in the 3th move of the first step.
> Regression score corruption in dinner party probably due PLANNER-488
> --------------------------------------------------------------------
>
> Key: DROOLS-1174
> URL: https://issues.jboss.org/browse/DROOLS-1174
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
>
> to reproduce run DinnerPartySolveAllTurtleTest with VM option -DrunTurtleTests=true in optaplanner-examples.
> {code}
> 2016-05-12 16:06:02,121 [main] INFO Opened: data/dinnerparty/unsolved/wedding01.xml
> 2016-05-12 16:06:02,226 [main] TRACE Model annotations parsed for Solution DinnerParty:
> 2016-05-12 16:06:02,226 [main] TRACE Entity SeatDesignation:
> 2016-05-12 16:06:02,226 [main] TRACE Variable seat (genuine)
> 2016-05-12 16:06:03,436 [main] INFO Solving started: time spent (137), best score (144uninitialized/-14400), environment mode (NON_INTRUSIVE_FULL_ASSERT), random (JDK with seed 0).
> 2016-05-12 16:06:03,913 [main] DEBUG Custom step (0), time spent (615), score (-2890), new best score (-2890).
> 2016-05-12 16:06:03,913 [main] INFO Custom phase (0) ended: step total (1), time spent (615), best score (-2890), score calculation speed (11050/sec).
> 2016-05-12 16:06:03,937 [main] TRACE Created cachedMoveList: size (10368), moveSelector (Shuffling(Filtering(SwapMoveSelector(FromSolutionEntitySelector(SeatDesignation), FromSolutionEntitySelector(SeatDesignation))))).
> 2016-05-12 16:06:03,941 [main] TRACE Shuffled cachedMoveList with size (10368) in moveSelector(Shuffling(Filtering(SwapMoveSelector(FromSolutionEntitySelector(SeatDesignation), FromSolutionEntitySelector(SeatDesignation))))).
> 2016-05-12 16:06:03,950 [main] TRACE Move index (0), score (-2890), accepted (true), move (Grayson {1.4} <-> Oliver {0.4}).
> 2016-05-12 16:06:03,957 [main] TRACE Move index (1), score (-2890), accepted (true), move (James {10.4} <-> Cameron {10.10}).
> java.lang.IllegalStateException: Score corruption: the workingScore (-3190) is not the uncorruptedScore (-3090) after completedAction (Eliana {8.9} <-> Allison {9.3}):
> The corrupted scoreDirector has 1 ConstraintMatch(s) which are in excess (and should not be there):
> org.optaplanner.examples.dinnerparty.solver/twoSameJobTypePerTable/level0/[8, SOCIALITE]=-100
> The corrupted scoreDirector has no ConstraintMatch(s) which are missing.
> Check your score constraints.
> at org.optaplanner.core.impl.score.director.AbstractScoreDirector.assertWorkingScoreFromScratch(AbstractScoreDirector.java:418)
> at org.optaplanner.core.impl.solver.scope.DefaultSolverScope.assertWorkingScoreFromScratch(DefaultSolverScope.java:118)
> at org.optaplanner.core.impl.phase.scope.AbstractPhaseScope.assertWorkingScoreFromScratch(AbstractPhaseScope.java:156)
> at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.processMove(LocalSearchDecider.java:167)
> at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.doMove(LocalSearchDecider.java:153)
> at org.optaplanner.core.impl.localsearch.decider.LocalSearchDecider.decideNextStep(LocalSearchDecider.java:125)
> at org.optaplanner.core.impl.localsearch.DefaultLocalSearchPhase.solve(DefaultLocalSearchPhase.java:63)
> at org.optaplanner.core.impl.solver.DefaultSolver.runPhases(DefaultSolver.java:229)
> at org.optaplanner.core.impl.solver.DefaultSolver.solve(DefaultSolver.java:191)
> at org.optaplanner.examples.common.app.SolveAllTurtleTest.buildAndSolve(SolveAllTurtleTest.java:75)
> at org.optaplanner.examples.common.app.SolveAllTurtleTest.runFastAndFullAssert(SolveAllTurtleTest.java:55)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
> {code}
> I enabled trace logging above, it happens in the 3th move of the first step.
> It seems like this rule is responsible:
> {code}
> // 1 democrat and 1 republican = 2 politians at each table but NOT two of the same kind
> // 2 doctors at each table but NOT two of the same kind
> // 2 coaches at each table but NOT two of the same kind
> // 2 programmers at each table but NOT two of the same kind
> // 2 socialites at each table
> // 2 teachers at each table
> rule "twoSameJobTypePerTable"
> when
> $jobType : JobType()
> $table : Table()
> not (
> SeatDesignation(guestJobType == $jobType, seatTable == $table, $leftId : id, $firstJob : guestJob)
> and SeatDesignation(guestJobType == $jobType, seatTable == $table, id > $leftId,
> differentKindIfNeeded($firstJob))
> )
> then
> scoreHolder.addConstraintMatch(kcontext, -100);
> end
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months