[JBoss JIRA] (DROOLS-1098) Equals behaviour faulty when loading sessions after exception
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1098?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-1098.
---------------------------------
Resolution: Rejected
The provided reproducer has exactly the same defect of what reported in https://issues.jboss.org/browse/DROOLS-1097
> Equals behaviour faulty when loading sessions after exception
> -------------------------------------------------------------
>
> Key: DROOLS-1098
> URL: https://issues.jboss.org/browse/DROOLS-1098
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Environment: Mac OS 10.10.5, Eclipse Mars Release, Java 1.8, Drools 6.3.0.Final
> Reporter: Artur Kronenberg
> Assignee: Mario Fusco
> Attachments: test-standalone.zip
>
>
> This is in a series of debugging and I think a few issues boil down to this:
> https://issues.jboss.org/browse/DROOLS-1093
> https://issues.jboss.org/browse/DROOLS-1097
> This bug demonstrates how two identical sessions with identical input and rules produce a NPE when loading with equals behaviour vs identity behaviour. I am currently battling that issue and looking for a workaround.
> Essentially, you can run the unit tests I attached in the test project: (ExceptionTest)
> testIdentity - passes
> testIdentityWithReload - passes
> testEquals - NPE
> testEqualsWithReload- NPE
> The tests do the same thing:
> * Create new persistent session
> * Load facts into it
> * Run 20 times either reloading the session (depending on the test cases) or using the old session. Each run, insert one fact and run all the rules. Eventually the equals tests (I believe after iteration 2) NPE when trying to deserialise the session. Identity has no issues and functions correctly.
> Let me know if you need anything else and please do let me know if there is a workaround. I am currently exploring the workaround avenue myself as well and will come back here with an update should I find one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1099) Couldn't access any web service of drools or kie which run in docker container
by Petr Široký (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1099?page=com.atlassian.jira.plugi... ]
Petr Široký commented on DROOLS-1099:
-------------------------------------
The kie-server.log seems OK. The app deployed successfully, so you are likely not using the correct end-point. Try accessing http://<container_ip_address>:8080/kie-server/services/rest/server/ (this is for the kie-server-showcase which has some users enabled by default).
For the drools-wb.log, it seems the deployment just hanged for some reason. Is the log complete, could you e.g. try to wait ~10 minutes to see if the deployment finished by then? Other thing that comes to my mind is that the container may not have enough entropy for SecureRandom calls inside the conainter/sshd stuff. See https://wiki.apache.org/tomcat/HowTo/FasterStartUp#Entropy_Source for more info. If that would be the case we would need to fix it in the container.
> 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
[JBoss JIRA] (JGRP-2040) Seeing a OOM in JGroup 3.4
by Kshitiz Saxena (JIRA)
Kshitiz Saxena created JGRP-2040:
------------------------------------
Summary: Seeing a OOM in JGroup 3.4
Key: JGRP-2040
URL: https://issues.jboss.org/browse/JGRP-2040
Project: JGroups
Issue Type: Bug
Affects Versions: 3.4
Environment: Linux Operating System
Reporter: Kshitiz Saxena
Assignee: Bela Ban
We are seeing an OOM in our application where thread dump points to JGroup.
We see the below in thread dumps,
3XEHSTTYPE 07:33:24:346241000 GMT j9vm.294 - >setCurrentException index=11 constructorIndex=0 detailMessage=0000000000F61678
3XEHSTTYPE 07:33:24:346183000 GMT j9mm.126 - at 0000000050F8CD60 java/lang/Thread.run()V, jit 00007FCF323EA580, pc 00007FCF489E0A36
3XEHSTTYPE 07:33:24:346179000 GMT j9mm.126 - at 0000000053644748 *org/jgroups/blocks/TCPConnectionMap$TCPConnection$Receiver.run()*V, jit 0000000000000000, pc 00007FCF3354D334
3XEHSTTYPE 07:33:24:346175000 GMT j9mm.101 - J9AllocateIndexableObject() returning NULL! *1650814064 bytes* requested for object of class 0000000050F79700 from memory space 'Generational' id=00007FCF440427C0
In the thread dump we also see
WARNING : OutOfMemoryError possibly caused by 1650814064 bytes requested for object of class 0000000050F79700 from memory space 'Generational' id=00007FCF440427C0
Java Heap Information
-Xmx (Maximum Java heap size) : 1280m
-Xms (Initial Java heap size) : 640m
-Xss (Maximum stack size for Java threads) : 256k
Total Java heap size: 1.25 GB
Used Java heap size: 174.27 MB
Free Java heap size: 1.08 GB
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1097) Loading Session and running rules re-executes all rules
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1097?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-1097.
---------------------------------
Resolution: Rejected
Your reproducer was a bit convoluted and I took awhile to figure out what was going wrong there. I think I captured the essence of the problem with the following test case:
{code}
@Test
public void test1097() throws Exception {
String drl =
"import " + MyModel.class.getCanonicalName() + ";\n" +
"rule \"expiry\" when \n" +
" $p : MyModel( expired );\n" +
"then\n" +
" System.out.println(\"Expired \" + $p);\n" +
" delete($p)\n" +
"end";
KieServices ks = KieServices.Factory.get();
KieBase kbase = new KieHelper().addContent( drl, ResourceType.DRL ).build();
KieSession ksession = kbase.newKieSession();
ksession.insert(new MyModel( 0 ));
Assert.assertEquals( 1, ksession.getFactCount() );
ksession.fireAllRules();
ksession = SerializationHelper.getSerialisedStatefulKnowledgeSession(ksession, true);
int fireAllRules = ksession.fireAllRules();
Assert.assertEquals(0, fireAllRules);
}
public static class MyModel implements Serializable {
private boolean expired = false;
private final int id;
public MyModel( int id ) {
this.id = id;
}
@Override
public String toString() {
return "MyModel[" + id + "]";
}
public boolean isExpired() {
boolean result = expired;
expired = true;
return result;
}
}
{code}
Note the isExpired() method of the MyModel bean. In your implementation you used a Random generator and I rewrote it that way only because I wanted a deterministic behaviour. Anyway for what concerns Drools your implementation of that method and mine present exactly the same problem: the value returned by that method in 2 different invocations changes (or may change in your version). This corresponds under Drools point of view to a change of a fact without notifying the engine that the fact is changed. In other words this is exactly equivalent to doing in a rule consequence something like:
{code}
myModel.setExpired(true);
{code}
instead of
{code}
modify( myModel ) { setExpired( true ) };
{code}
and then complaining that Drools wasn't reacting to a change in your model.
When you serialize and deserialize the session the facts are reasserted into it thus causing the rule to fire even if you don't expect it. However the flaw is not in the serialization mechanism but it is caused by the fact that you're effectively changing the state of a fact stored in Drools working memory without notifying the engine. This can cause many other "unexpected" behaviours regardless of serialization.
> Loading Session and running rules re-executes all rules
> --------------------------------------------------------
>
> Key: DROOLS-1097
> URL: https://issues.jboss.org/browse/DROOLS-1097
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Environment: Mac OS 10.10.5, Eclipse Mars Release, Java 1.8, Drools 6.3.0.Final
> Reporter: Artur Kronenberg
> Assignee: Mario Fusco
> Attachments: test-standalone.zip
>
>
> This is possibly directly related to: (or rather that one relates to this one)
> https://issues.jboss.org/browse/DROOLS-1093
> The situation:
> * Create a session with 2 rules. 1 Rule expires facts that are in the working memory by retracting them.
> * Add the ExpiryFact to expire some facts
> * Execute all rules -> X facts get expired
> * dispose the existing session
> * re-load the session
> * without adding more facts to the working memory, run all rules
> * The session re-executes more rules and retracts things from memory
> Now there seem to be 2 problems with this:
> 1. The session does not remember what facts it expired. So it will delete more infos, that are still "somewhere". When re-loading the session from the database, we will see an NPE
> 2. Surely since it already ran the rules against the Expiry fact, it should not run them again.
> I will attach a unit test ExceptionTest#testRulesAreFiredTwice with this bug.
> Let me know if this can be worked around please and/or if there are any more questions.
> Thanks,
> Artur
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFCORE-1466) Wildfly SSL Setup Fails on HSM-Backed Keystore
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1466?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFCORE-1466:
------------------------------------------
If aliases are not necessary can you not just remove the alias attribute from your WildFly configuration to eliminate this error?
> Wildfly SSL Setup Fails on HSM-Backed Keystore
> ----------------------------------------------
>
> Key: WFCORE-1466
> URL: https://issues.jboss.org/browse/WFCORE-1466
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Environment: Any host environment with an HSM for key management
> Reporter: Gregory Ramsperger
> Assignee: Darran Lofthouse
>
> Using a keystore type that does not allow or returns empty from getEncoded() on private keys causes a KeyStoreException at startup. This is common in HSM-backed key operations.
> Storing SSL keys and certs in an HSM is a common method of securing keys and offloading SSL overhead.
> FileKeyStore.java copies a KeyStore.Entry value into a JKS KeyStore but JKS and PKCS12 KeyStore implementations maintain a copy of the encoded PKCS#8 data for private keys. When applying a KeyStore.Entry from a source that does not return the data for security reasons, the import fails.
> While it's still not guaranteed to work with all KeyStore providers, switching {{KeyStore.getInstance("JKS")}} to {{KeyStore.getInstance(provider)}} fixes the issue for SafeNet "Luna" and SunPKCS11 "PKCS11" KeyStore implementations while not breaking the "PKCS12" and "JKS" cases.
> See [https://github.com/wildfly/wildfly-core/blob/master/domain-management/src...]
> Log output:
> {noformat}
> 2016-04-04 18:53:51,100 i-4b6f79d1 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.server.controller.management.security_realm.test.key-manager: org.jboss.msc.service.StartException in service jboss.server.controller.management.security_realm.test.key-manager: JBAS015229: Unable to start service
> at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:148)
> at org.jboss.as.domain.management.security.FileKeyManagerService.start(FileKeyManagerService.java:119)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60]
> Caused by: java.security.KeyStoreException: Cannot get key bytes, not PKCS#8 encoded
> at sun.security.provider.KeyProtector.protect(KeyProtector.java:174) [rt.jar:1.8.0_60]
> at sun.security.provider.JavaKeyStore.engineSetKeyEntry(JavaKeyStore.java:267) [rt.jar:1.8.0_60]
> at sun.security.provider.JavaKeyStore$JKS.engineSetKeyEntry(JavaKeyStore.java:56) [rt.jar:1.8.0_60]
> at java.security.KeyStoreSpi.engineSetEntry(KeyStoreSpi.java:537) [rt.jar:1.8.0_60]
> at sun.security.provider.KeyStoreDelegator.engineSetEntry(KeyStoreDelegator.java:179) [rt.jar:1.8.0_60]
> at sun.security.provider.JavaKeyStore$DualFormatJKS.engineSetEntry(JavaKeyStore.java:70) [rt.jar:1.8.0_60]
> at java.security.KeyStore.setEntry(KeyStore.java:1557) [rt.jar:1.8.0_60]
> at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:136)
> ... 6 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1079) Kie navigator cannot show organizational units content
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1079?page=com.atlassian.jira.plugi... ]
Tomas David closed DROOLS-1079.
-------------------------------
> Kie navigator cannot show organizational units content
> ------------------------------------------------------
>
> Key: DROOLS-1079
> URL: https://issues.jboss.org/browse/DROOLS-1079
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Environment: JBoss Developer Studio 9.1.0.Beta2
> Drools plugin 6.4.0.201601201107
> Reporter: Tomas David
> Assignee: Robert (Bob) Brodt
> Priority: Blocker
> Labels: qe-recommend-fix-before-ga, reported-by-qe
> Attachments: server.log
>
>
> It is not possible to open organizational units and display associated repositories. Also when you create a new repository in org unit, it is not displayed in kie navigator but in business central app it is correctly created.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1076) Initial opening of kie navigator server properties shows error dialog
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1076?page=com.atlassian.jira.plugi... ]
Tomas David closed DROOLS-1076.
-------------------------------
Resolution: Done
Verified with 6.4.0.CR2.
> Initial opening of kie navigator server properties shows error dialog
> ----------------------------------------------------------------------
>
> Key: DROOLS-1076
> URL: https://issues.jboss.org/browse/DROOLS-1076
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Environment: JBoss Developer Studio 9.1.0.Beta2
> Drools plugin 6.4.0.201601201107
> Reporter: Tomas David
> Assignee: Robert (Bob) Brodt
> Priority: Minor
> Labels: qe-recommend-fix-before-ga, reported-by-qe
> Attachments: kn_server_prop_error.png
>
>
> If you open server properties of the the kie navigator tool, you will get error dialog "The currently displayed page contains invalid values". This happens only when you create new server in server view and then you open server properties in kie navigator view.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (DROOLS-1079) Kie navigator cannot show organizational units content
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1079?page=com.atlassian.jira.plugi... ]
Tomas David resolved DROOLS-1079.
---------------------------------
Resolution: Done
Verified with 6.4.0.CR2.
> Kie navigator cannot show organizational units content
> ------------------------------------------------------
>
> Key: DROOLS-1079
> URL: https://issues.jboss.org/browse/DROOLS-1079
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Environment: JBoss Developer Studio 9.1.0.Beta2
> Drools plugin 6.4.0.201601201107
> Reporter: Tomas David
> Assignee: Robert (Bob) Brodt
> Priority: Blocker
> Labels: qe-recommend-fix-before-ga, reported-by-qe
> Attachments: server.log
>
>
> It is not possible to open organizational units and display associated repositories. Also when you create a new repository in org unit, it is not displayed in kie navigator but in business central app it is correctly created.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6041) <node> failed submitting DONT_BUNDLE message to thread pool during server startup
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6041?page=com.atlassian.jira.plugin.... ]
Radoslav Husar resolved WFLY-6041.
----------------------------------
Fix Version/s: 10.1.0.Final
Resolution: Done
> <node> failed submitting DONT_BUNDLE message to thread pool during server startup
> ---------------------------------------------------------------------------------
>
> Key: WFLY-6041
> URL: https://issues.jboss.org/browse/WFLY-6041
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR5
> Reporter: Michal Vinkler
> Assignee: Paul Ferraro
> Priority: Minor
> Fix For: 10.1.0.Final
>
>
> Seen in these scenarios in ER4:
> http-session-shutdown-repl-async-tcpStack
> ejb-ejbservlet-shutdown-dist-async
> During server startup (the server was restarted after previous graceful shutdown), this error was logged several times:
> {code}
> [JBossINF] [0m[31m20:12:25,912 ERROR [org.jgroups.protocols.UDP] (multicast receiver,ee,perf19) perf19: failed submitting DONT_BUNDLE message to thread pool: java.util.concurrent.RejectedExecutionException: Task org.jgroups.protocols.TP$SingleMessageHandler@7a718788 rejected from java.util.concurrent.ThreadPoolExecutor@66f4f3ee[Running, pool size = 300, active threads = 300, queued tasks = 0, completed tasks = 1130]. Msg: RequestCorrelator: id=200, type=REQ, id=125094, rsp_expected=true, FORK: ee:web, NAKACK2: [MSG, seqno=123637], UDP: [cluster_name=ee]
> {code}
> It had no impact on the client though.
> Link:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-http-...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month