[JBoss JIRA] (WFLY-8866) Legacy add-protocol/remove-protocol operations do not work for legacy protocols
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-8866?page=com.atlassian.jira.plugin.... ]
Paul Ferraro moved JBEAP-11255 to WFLY-8866:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8866 (was: JBEAP-11255)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
> Legacy add-protocol/remove-protocol operations do not work for legacy protocols
> -------------------------------------------------------------------------------
>
> Key: WFLY-8866
> URL: https://issues.jboss.org/browse/WFLY-8866
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Blocker
>
> As discussed in JBEAP-11190, this concerns the following use case:
> {noformat:title=#4 Adding TCPPING via add-protocol operation - NOK}
> /subsystem="jgroups"/stack="tcpping":add-protocol(type="TCPPING")
> # throws with DR19
> {noformat}
> which no longer works in DR19 because it requires socket bindings to be defined.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (DROOLS-1592) Deleted facts retained in memory, but removed after (de)serialization
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1592?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-1592:
-------------------------------------
Assignee: Mario Fusco (was: Edson Tirelli)
> Deleted facts retained in memory, but removed after (de)serialization
> ---------------------------------------------------------------------
>
> Key: DROOLS-1592
> URL: https://issues.jboss.org/browse/DROOLS-1592
> Project: Drools
> Issue Type: Bug
> Reporter: Nikolay Plekhanov
> Assignee: Mario Fusco
> Attachments: drools-memleak.zip
>
>
> Given:
> two agenda groups: A1 and A2.
> Rule R1 in agenda group A1 and rule R2 in agenda group A2.
> R1 matches facts of type T1, deletes them and creates facts of type T2.
> R2 matches facts of type T2 and does soemthing with them (it doesn't matter, because issue happens even if R2 never fired).
> Scenario:
> * Create session, add R1 and R2 rules
> * add some facts of T1 type
> * set focus on A1 agenda group
> * invoke "fireAllRules" method
> * Invoke "getObjects" and assure that session contains only T2 facts
> * analyze objects in memory (by jmap + memory analyzing tool or just traversing references by reflection) and assure that T1 facts are still reachable via session object.
> * serialize session using marshaller and deserialize in again
> * analyze deserialized session and see that it doesn't contain T1 fact references anymore.
> Thoughts:
> I assumed that T1 references storing is feature, because they can be necessary in some cases (like reverse of their deletion due to logical inversion of truth - not sure, but maybe), but T1 deletion after (de)serialization points out the opposite.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (DROOLS-1592) Deleted facts retained in memory, but removed after (de)serialization
by Nikolay Plekhanov (JIRA)
Nikolay Plekhanov created DROOLS-1592:
-----------------------------------------
Summary: Deleted facts retained in memory, but removed after (de)serialization
Key: DROOLS-1592
URL: https://issues.jboss.org/browse/DROOLS-1592
Project: Drools
Issue Type: Bug
Reporter: Nikolay Plekhanov
Assignee: Edson Tirelli
Attachments: drools-memleak.zip
Given:
two agenda groups: A1 and A2.
Rule R1 in agenda group A1 and rule R2 in agenda group A2.
R1 matches facts of type T1, deletes them and creates facts of type T2.
R2 matches facts of type T2 and does soemthing with them (it doesn't matter, because issue happens even if R2 never fired).
Scenario:
* Create session, add R1 and R2 rules
* add some facts of T1 type
* set focus on A1 agenda group
* invoke "fireAllRules" method
* Invoke "getObjects" and assure that session contains only T2 facts
* analyze objects in memory (by jmap + memory analyzing tool or just traversing references by reflection) and assure that T1 facts are still reachable via session object.
* serialize session using marshaller and deserialize in again
* analyze deserialized session and see that it doesn't contain T1 fact references anymore.
Thoughts:
I assumed that T1 references storing is feature, because they can be necessary in some cases (like reverse of their deletion due to logical inversion of truth - not sure, but maybe), but T1 deletion after (de)serialization points out the opposite.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-2893) Wrong schema version in several .xsd files
by Aurel Pintea (JIRA)
Aurel Pintea created WFCORE-2893:
------------------------------------
Summary: Wrong schema version in several .xsd files
Key: WFCORE-2893
URL: https://issues.jboss.org/browse/WFCORE-2893
Project: WildFly Core
Issue Type: Bug
Reporter: Aurel Pintea
Assignee: Aurel Pintea
Priority: Minor
Some schemas in ${EAP_HOME}/docs/schema has wrong version specified.
Version-Release number of selected component (if applicable):
EAP 6.4.0.ER2
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (DROOLS-1591) Problems in serialization/deserialization of KnowledgePackages
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1591?page=com.atlassian.jira.plugi... ]
Mario Fusco reassigned DROOLS-1591:
-----------------------------------
Assignee: Mario Fusco (was: Edson Tirelli)
> Problems in serialization/deserialization of KnowledgePackages
> --------------------------------------------------------------
>
> Key: DROOLS-1591
> URL: https://issues.jboss.org/browse/DROOLS-1591
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 6.5.0.Final, 7.0.0.Beta3
> Reporter: Vítor Moreira
> Assignee: Mario Fusco
> Attachments: jboss_issue.tar.gz
>
>
> Using {{DroolsStreamUtils}}, created an unit-test to serialize and deserialize a DRL file. In version "6.0.1.Final", the unit-test runs flawlessly. In other versions, deserialization gives an ClassNotFoundException for the declared event.
> I've checked StackOverflow and Drools' JIRA for similar problems and found nothing.
> I've also attached a junit. Please change property {{drools.version}} to test with different Drools versions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (DROOLS-1591) Problems in serialization/deserialization of KnowledgePackages
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1591?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-1591:
--------------------------------
Component/s: core engine
(was: dmn engine)
> Problems in serialization/deserialization of KnowledgePackages
> --------------------------------------------------------------
>
> Key: DROOLS-1591
> URL: https://issues.jboss.org/browse/DROOLS-1591
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.5.0.Final, 7.0.0.Beta3
> Reporter: Vítor Moreira
> Assignee: Mario Fusco
> Attachments: jboss_issue.tar.gz
>
>
> Using {{DroolsStreamUtils}}, created an unit-test to serialize and deserialize a DRL file. In version "6.0.1.Final", the unit-test runs flawlessly. In other versions, deserialization gives an ClassNotFoundException for the declared event.
> I've checked StackOverflow and Drools' JIRA for similar problems and found nothing.
> I've also attached a junit. Please change property {{drools.version}} to test with different Drools versions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (DROOLS-1591) Problems in serialization/deserialization of KnowledgePackages
by Vítor Moreira (JIRA)
Vítor Moreira created DROOLS-1591:
-------------------------------------
Summary: Problems in serialization/deserialization of KnowledgePackages
Key: DROOLS-1591
URL: https://issues.jboss.org/browse/DROOLS-1591
Project: Drools
Issue Type: Bug
Components: dmn engine
Affects Versions: 7.0.0.Beta3, 6.5.0.Final
Reporter: Vítor Moreira
Assignee: Edson Tirelli
Attachments: jboss_issue.tar.gz
Using {{DroolsStreamUtils}}, created an unit-test to serialize and deserialize a DRL file. In version "6.0.1.Final", the unit-test runs flawlessly. In other versions, deserialization gives an ClassNotFoundException for the declared event.
I've checked StackOverflow and Drools' JIRA for similar problems and found nothing.
I've also attached a junit. Please change property {{drools.version}} to test with different Drools versions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-8863) JDR throws NPE when running through jdr.sh with non-English locale
by Martin Švehla (JIRA)
[ https://issues.jboss.org/browse/WFLY-8863?page=com.atlassian.jira.plugin.... ]
Martin Švehla moved JBEAP-11250 to WFLY-8863:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8863 (was: JBEAP-11250)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JDR
(was: JDR)
Affects Version/s: (was: 7.1.0.DR19)
> JDR throws NPE when running through jdr.sh with non-English locale
> ------------------------------------------------------------------
>
> Key: WFLY-8863
> URL: https://issues.jboss.org/browse/WFLY-8863
> Project: WildFly
> Issue Type: Bug
> Components: JDR
> Reporter: Martin Švehla
> Assignee: Brad Maxwell
>
> When running jdr.sh script with non-English locale, the script throws NullPointerException. Problem seems to be that the generate-jdr-output always uses English locale, but when parsing start-date and end-date, SimpleDateFormat uses system defined locales.
> {code}
> Initializing JBoss Diagnostic Reporter...
> Trying to connect to http-remoting localhost:9990
> Exception in thread "main" java.lang.NullPointerException
> at org.jboss.as.jdr.CommandLineMain.printJdrReportInfo(CommandLineMain.java:150)
> at org.jboss.as.jdr.CommandLineMain.main(CommandLineMain.java:144)
> at org.jboss.modules.Module.run(Module.java:344)
> at org.jboss.modules.Main.main(Main.java:519)
> {code}
> This is not issue when running generate-jdr-report() from CLI. Also easy to workaround by enforcing locale for the script run
> {code}
> LC_ALL=C $JBOSS_HOME/bin/jdr.sh
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months