[JBoss JIRA] (WFCORE-1658) JBEAP-2830 enhancements were not forward ported to upstream
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1658?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1658:
------------------------------------------
I don't think this supplement should be called "full-ha" as that's the name of the thing that uses it, not an identifying characteristic of the supplement itself. Which is a bit off, and is confusing in this case since in WildFly standalone-full-ha.xml doesn't actually use this supplement. Perhaps "no-console"?
> JBEAP-2830 enhancements were not forward ported to upstream
> -----------------------------------------------------------
>
> Key: WFCORE-1658
> URL: https://issues.jboss.org/browse/WFCORE-1658
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Brian Stansberry
> Assignee: Dmitrii Tikhomirov
> Priority: Blocker
> Fix For: 2.2.0.CR8
>
>
> JBEAP-2830 includes changes to the logging subsystem's template.xml that EAP full relies upon. These were never forward ported to upstream, meaning that EAP builds can't consume core 2.2 or later.
> I believe there's no problem applying the changes. EAP will use one of the supplements while WildFly will not.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6856) Jboss CLI reporting wrong readings of datasource
by ritesh ranjan (JIRA)
ritesh ranjan created WFLY-6856:
-----------------------------------
Summary: Jboss CLI reporting wrong readings of datasource
Key: WFLY-6856
URL: https://issues.jboss.org/browse/WFLY-6856
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 8.2.0.Final
Reporter: ritesh ranjan
Assignee: Scott Marlow
Jboss's CLI is reporting wrong values of datasource parameters.(active count,idlecount etc..)
As per the reading , idle connections on the database side have been closed but actually the connections are indeed active.
Probably, jboss isn't checking on the oracle side.
PS : found in wildfly 8 and our db is Oracle
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1658) JBEAP-2830 enhancements were not forward ported to upstream
by Dmitrii Tikhomirov (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1658?page=com.atlassian.jira.plugi... ]
Dmitrii Tikhomirov reassigned WFCORE-1658:
------------------------------------------
Assignee: Dmitrii Tikhomirov (was: Brian Stansberry)
> JBEAP-2830 enhancements were not forward ported to upstream
> -----------------------------------------------------------
>
> Key: WFCORE-1658
> URL: https://issues.jboss.org/browse/WFCORE-1658
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Brian Stansberry
> Assignee: Dmitrii Tikhomirov
> Priority: Blocker
> Fix For: 2.2.0.CR8
>
>
> JBEAP-2830 includes changes to the logging subsystem's template.xml that EAP full relies upon. These were never forward ported to upstream, meaning that EAP builds can't consume core 2.2 or later.
> I believe there's no problem applying the changes. EAP will use one of the supplements while WildFly will not.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (DROOLS-1158) NullpointerException when trying to reuse KnowledgePackage into a new KnowledgeBase
by Juan Carlos Garcia (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1158?page=com.atlassian.jira.plugi... ]
Juan Carlos Garcia commented on DROOLS-1158:
--------------------------------------------
After going thru the DOC, it seems the KieScanner is not an option as we don't deploy our DTables withing jar files, they are access thru WebDav.
Regardless we have started to make the necessary changes to get rid of the OLD API and just uses the new KIE interfaces and factories for bootstrapping.
Thanks
> NullpointerException when trying to reuse KnowledgePackage into a new KnowledgeBase
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-1158
> URL: https://issues.jboss.org/browse/DROOLS-1158
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.3.0.Final, 6.4.0.Final
> Reporter: Juan Carlos Garcia
> Assignee: Matteo Mortari
> Attachments: drools-reusepackage.tar, screenshot-1.png
>
>
> Having a set of DecisionTables which KnowledgePackages are cached in our application, after we detect a change in any of those XLS files, we build a KnowledgePackages from it, and then try to create a new KnowledgeBase with the new KnowledgePackages + the rest of the cached one that that were not modified, but it fails with a NPE internally in Drools (6.3.0 and 6.4.0)
> This is not a problem for the drools version (6.0.1.Final) that we currently uses using in production.
> After debugging and putting a breakpoint into the *MvelConstraint.java:619*, it shows that it is trying to look for a packageName which hasn't being loaded yet in the new kbase (but belong to others XLS).
> I have attached a project with a testcase that shows the problem, it has 2 DecisionTable which i had to cut down a little bit (from our real files) and removes some sensitive information (replacing some of text with FOO-BAR).
> {code}
> java.lang.NullPointerException
> at org.drools.core.rule.constraint.MvelConstraint.equals(MvelConstraint.java:619)
> at org.drools.core.reteoo.AlphaNode.internalEquals(AlphaNode.java:199)
> at org.drools.core.common.BaseNode.thisNodeEquals(BaseNode.java:194)
> at org.drools.core.reteoo.CompositeObjectSinkAdapter.getMatchingNode(CompositeObjectSinkAdapter.java:531)
> at org.drools.core.reteoo.builder.BuildUtils.attachNode(BuildUtils.java:121)
> at org.drools.core.reteoo.builder.PatternBuilder.buildAlphaNodeChain(PatternBuilder.java:332)
> at org.drools.core.reteoo.builder.PatternBuilder.attachAlphaNodes(PatternBuilder.java:313)
> at org.drools.core.reteoo.builder.PatternBuilder.attachPattern(PatternBuilder.java:130)
> at org.drools.core.reteoo.builder.PatternBuilder.build(PatternBuilder.java:78)
> at org.drools.core.reteoo.builder.GroupElementBuilder$AndBuilder.build(GroupElementBuilder.java:108)
> at org.drools.core.reteoo.builder.GroupElementBuilder.build(GroupElementBuilder.java:68)
> at org.drools.core.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:161)
> at org.drools.core.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:133)
> at org.drools.core.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:106)
> at org.drools.core.impl.KnowledgeBaseImpl.addRule(KnowledgeBaseImpl.java:1567)
> at org.drools.core.impl.KnowledgeBaseImpl.addRule(KnowledgeBaseImpl.java:1547)
> at org.drools.core.impl.KnowledgeBaseImpl.internalAddPackages(KnowledgeBaseImpl.java:920)
> at org.drools.core.impl.KnowledgeBaseImpl.access$000(KnowledgeBaseImpl.java:117)
> at org.drools.core.impl.KnowledgeBaseImpl$1.run(KnowledgeBaseImpl.java:708)
> at org.drools.core.impl.KnowledgeBaseImpl.enqueueModification(KnowledgeBaseImpl.java:716)
> at org.drools.core.impl.KnowledgeBaseImpl.addPackages(KnowledgeBaseImpl.java:705)
> at org.drools.core.impl.KnowledgeBaseImpl.addKnowledgePackages(KnowledgeBaseImpl.java:273)
> at org.drools.impl.adapters.KnowledgeBaseAdapter.addKnowledgePackages(KnowledgeBaseAdapter.java:62)
> at bug.demo.BugReloadableDecisionTableTest.addRuleSetToKnowledgeBase(BugReloadableDecisionTableTest.java:63)
> at bug.demo.BugReloadableDecisionTableTest.testReuseKnowledgePackage(BugReloadableDecisionTableTest.java:53)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6854) Upgrade Hibernate ORM to 5.1.x
by Sanne Grinovero (JIRA)
[ https://issues.jboss.org/browse/WFLY-6854?page=com.atlassian.jira.plugin.... ]
Sanne Grinovero commented on WFLY-6854:
---------------------------------------
Wondering if we could have this sooner, in a minor or micro update of WildFly 10 ?
> Upgrade Hibernate ORM to 5.1.x
> ------------------------------
>
> Key: WFLY-6854
> URL: https://issues.jboss.org/browse/WFLY-6854
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Reporter: Emmanuel Bernard
> Assignee: Scott Marlow
> Fix For: 11.0.0.Alpha1
>
>
> This is a follow up on WFLY-6682.
> After looking at the list of potential incompatibilities, we decided to not upgrade to 5.2 but instead to 5.1 to provide a smoother experience to users.
> We can consider adding a 5.2 optional switch via Jipijapa if bandwidth permit but let's treat it as a second issue and have [~smarlow] lead it.
> PS: I put v11Alpha1 but feel free to adjust it to any WF 11 version that fits best.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-6854) Upgrade Hibernate ORM to 5.1.x
by Emmanuel Bernard (JIRA)
Emmanuel Bernard created WFLY-6854:
--------------------------------------
Summary: Upgrade Hibernate ORM to 5.1.x
Key: WFLY-6854
URL: https://issues.jboss.org/browse/WFLY-6854
Project: WildFly
Issue Type: Feature Request
Components: JPA / Hibernate
Reporter: Emmanuel Bernard
Assignee: Scott Marlow
Fix For: 11.0.0.Alpha1
This is a follow up on WFLY-6682.
After looking at the list of potential incompatibilities, we decided to not upgrade to 5.2 but instead to 5.1 to provide a smoother experience to users.
We can consider adding a 5.2 optional switch via Jipijapa if bandwidth permit but let's treat it as a second issue and have [~smarlow] lead it.
PS: I put v11Alpha1 but feel free to adjust it to any WF 11 version that fits best.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months