[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by gunter zeilinger (JIRA)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
gunter zeilinger edited comment on WFLY-10531 at 7/6/18 5:15 AM:
-----------------------------------------------------------------
See the same(?) failure occurring after upgrading from wildfly 12 to 13, using an injected JMS Context in a SLSB which is itself invoked by an @ApplicationScoped CDI Bean. [Opened issue #11395 at GitHub|https://github.com/wildfly/wildfly/issues/11395].
was (Author: gunterze):
See the same failure occurring after upgrading from wildfly 12 to 13, using an injected JMS Context in a SLSB which is itself invoked by an @ApplicationScoped CDI Bean. [Opened issue #11395 at GitHub|https://github.com/wildfly/wildfly/issues/11395].
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by gunter zeilinger (JIRA)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
gunter zeilinger commented on WFLY-10531:
-----------------------------------------
See the same failure occurring after upgrading from wildfly 12 to 13, using an injected JMS Context in a SLSB which is itself invoked by an @ApplicationScoped CDI Bean. [Opened issue #11395 at GitHub|https://github.com/wildfly/wildfly/issues/11395].
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-1701) FEEL code generation and compilation
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1701?page=com.atlassian.jira.plugi... ]
Matteo Mortari edited comment on DROOLS-1701 at 7/6/18 5:04 AM:
----------------------------------------------------------------
Commits on master covering all FEEL to Java translation under feature flag (special FEELProfile to enable translation, compilation and bytecode load)
3af4fe86f3bd04d1599a7a0ef2b6c1a54e5180c2 3af4fe86f3 DROOLS-1701 Final refactoring accordingly to PR comments and feedback
fd9cb4596259ffa4b74c8816a47957a72058e71f fd9cb45962 DROOLS-1701 Final touches (#14)
76f09d67bf090959de43279826bdbd527f3aa028 76f09d67bf DROOLS-1701 decide unary `not` execution at runtime (#13)
8ca8264cf4ec3a744684665ec286d8d4ddeaa6c4 8ca8264cf4 DROOLS-1701 minor refactoring
d6ee27e57974477cc6a6b761f72ecc421b5c330f d6ee27e579 DROOLS-1701 unary not expression (#12)
5914a9ae68f65053275a8bd18d5936f6efa38dd3 5914a9ae68 DROOLS-1701 Properly escape strings on compile (#11)
7d7f3a00b3088a124e579aa8146e3ed9afb7041a 7d7f3a00b3 DROOLS-1701 Report compilation error as a runtime error (#10)
9717dfe6a815b6165fcd4c04050aecbc9c0af0ea 9717dfe6a8 DROOLS-1701 Fix list test cases (#9)
cc20df38fea3d62e73d3a9045841cffb77aff07a cc20df38fe DROOLS-1701 Fix closure context handling, misc fn issues (#8)
200b1aeb7d1ca42d3ec1376aad83420a47585c71 200b1aeb7d DROOLS-1701 fixes to `between` and `in` (esp. with `null` handling) (#7)
a75cf2af616b97393cf9f683cdaab3b8bf8c98ff a75cf2af61 DROOLS-1701 fix some `in` test cases (#6)
efbddeac1b7933729e3042f7ab87a8f22c79a8ec efbddeac1b DROOLS-1701 fix: ranges cannot be (always) promoted to fields (#5)
42589c3b42ff0b1a2de83f7090db1bfdf038fb00 42589c3b42 DROOLS-1701 misc fixes
5b9a64b5e8ae409d56bbd904eac54276788a9488 5b9a64b5e8 DROOLS-1701 migrate from upstream JP to org.drools:drlx-parser
316a3aebad43f179c738bef79efe2b916442bd84 316a3aebad DROOLS-1701 misc fixes
b9430c86817182ff5be688fe39d98f37ab4187a2 b9430c8681 DROOLS-1701 unify CompiledExpression interface and JIT FEEL compilation
bebd3b4bc7c98b734c9b212b04851fff42d2f363 bebd3b4bc7 DROOLS-1701 Use CoedegenStringUtils escape function
820a7435df8f895fe6de9da80f7bd8f14bedf99e 820a7435df DROOLS-1701 Support floating point constant values
26d1ab6aec0e549a779b74c0cb7cf41153f69bb6 26d1ab6aec DROOLS-1701 Support for FEEL fn invocation using named parameters
63345dbb3c5b7a086e8fae83f25b6a632d0b46b9 63345dbb3c DROOLS-1701 Support for FEEL fn definition (non-external, FEEL defined)
e46b03c04fe9422b16c8f6e282c0d7ad210d8314 e46b03c04f DROOLS-1701 Support for FEEL fn invocation using positional parameters
a886c076dc43ad54a1c637dd9b86f0d4e7d0c735 a886c076dc DROOLS-1701 Support for FEEL quantified expression `some`, `every`
6c470047adf10ac9ebbbdc9838b239f7c41d66f6 6c470047ad DROOLS-1701 Basic support for FEEL `for` expression
cbaa6b2e9ac2c1c7152a9afd7a27091a1a39d5c7 cbaa6b2e9a DROOLS-1701 Align with new signature of EvaluationContext
e2b91c8e5f93e6f3db9494b632e55baba06328e5 e2b91c8e5f DROOLS-1701 extend coverage for Qualified name
1e7994165b8214292ec604465a4df22e49062675 1e7994165b DROOLS-1701 coverage filter/path for PATH selection
3b5f243af94b76ecd2fa9419a3b29933f5bce4cd 3b5f243af9 DROOLS-1701 coverage filter/path ONLY ref Table 54: Semantics of lists
6cf9bd32a861dbd23666bb003cde816949efb72b 6cf9bd32a8 DROOLS-1701 coverage of "between" function
aafad227d30c9f13755138a525d37653d4bb7571 aafad227d3 DROOLS-1701 coverage of "instance of" function
da970d4577e3e33895195d729ec175b659e179a5 da970d4577 DROOLS-1701 Align with new signature of FEELParser.parse()
8a272f2a1c364e98d5f369a91052baebb31059fa 8a272f2a1c DROOLS-1701 !=, not() unary tests
1d50d778a0af60d90a3f7f6b513b380c95ac1d62 1d50d778a0 DROOLS-1701 Align with DROOLS-2143 for allowing '--1' expression
0bf22c4b43d4afe3e4e636dc136af08532786f44 0bf22c4b43 DROOLS-1701 Align with new signature of FEELParser.parse()
1d974606e2dd4c782836654358599cd076400fe5 1d974606e2 DROOLS-1701 initial coverage of unary test codegen
6a6f20e5640291c0b16202a617b17c0a789c6a77 6a6f20e564 DROOLS-1701 realign following grammar change of DROOLS-1670
45436f8c185e2d3412fcaee24c30311fcde1958a 45436f8c18 DROOLS-1701 Extend code generation support for more complex FEEL Context
5ef187bba4640bf006e3e7e74f8383d79bafda94 5ef187bba4 DROOLS-1701 Context compiled API support, codegen for literal contexts
d8e214472d8fc9b16eda8c10e2b15386e8f76e84 d8e214472d DROOLS-1701 Extend support for simple built-in FEEL list construct
654640d226c8680727f3c089e1b40fba193b14eb 654640d226 DROOLS-1701 Extend support for logicalNegation expression
478639fcab5bce23f64af48d63acad6f95d0a25d 478639fcab DROOLS-1701 Extend support to exponentiation Expression
80dc207a6c5a40b77adfa32f9920bc127650e3f5 80dc207a6c DROOLS-1701 Refactoring and extend support to multiplicative expression
d3df15ead603fa24c4ba2ef272f322dc2dc98c18 d3df15ead6 DROOLS-1701 Partial support FEEL +, -; optimize number literal ...
2782096272c644d9cbdcda17d48a54a30cbd209a 2782096272 DROOLS-1701 Cover if-then-else as a Java ternary op
50a97941c6de43dd3b1be3ecb2091fd8a6704604 50a97941c6 DROOLS-1701 Migrate to use EvaluationContext as input for compiled code
e795dd6b07d9a4c1b76b61f7a6a21b1bf436c1dc e795dd6b07 DROOLS-1701 Optimize Boolean and, or
ef318f4ea52a888255d5e745d713519c2d240b4b ef318f4ea5 DROOLS-1701 initial coverage for FEEL code generation and compilation
was (Author: tari_manga):
Commits on master covering all FEEL to Java translation under feature flag (special FEELProfile to enable translation, compilation and bytecode load)
3af4fe86f3bd04d1599a7a0ef2b6c1a54e5180c2 3af4fe86f3 DROOLS-1701 Final refactoring accordingly to PR comments and feedback
fd9cb4596259ffa4b74c8816a47957a72058e71f fd9cb45962 DROOLS-1701 Final touches (#14)
76f09d67bf090959de43279826bdbd527f3aa028 76f09d67bf DROOLS-1701 decide unary `not` execution at runtime (#13)
8ca8264cf4ec3a744684665ec286d8d4ddeaa6c4 8ca8264cf4 DROOLS-1701 minor refactoring
d6ee27e57974477cc6a6b761f72ecc421b5c330f d6ee27e579 DROOLS-1701 unary not expression (#12)
5914a9ae68f65053275a8bd18d5936f6efa38dd3 5914a9ae68 DROOLS-1701 Properly escape strings on compile (#11)
7d7f3a00b3088a124e579aa8146e3ed9afb7041a 7d7f3a00b3 DROOLS-1701 Report compilation error as a runtime error (#10)
9717dfe6a815b6165fcd4c04050aecbc9c0af0ea 9717dfe6a8 DROOLS-1701 Fix list test cases (#9)
cc20df38fea3d62e73d3a9045841cffb77aff07a cc20df38fe DROOLS-1701 Fix closure context handling, misc fn issues (#8)
200b1aeb7d1ca42d3ec1376aad83420a47585c71 200b1aeb7d DROOLS-1701 fixes to `between` and `in` (esp. with `null` handling) (#7)
a75cf2af616b97393cf9f683cdaab3b8bf8c98ff a75cf2af61 DROOLS-1701 fix some `in` test cases (#6)
efbddeac1b7933729e3042f7ab87a8f22c79a8ec efbddeac1b DROOLS-1701 fix: ranges cannot be (always) promoted to fields (#5)
42589c3b42ff0b1a2de83f7090db1bfdf038fb00 42589c3b42 DROOLS-1701 misc fixes
5b9a64b5e8ae409d56bbd904eac54276788a9488 5b9a64b5e8 DROOLS-1701 migrate from upstream JP to org.drools:drlx-parser
316a3aebad43f179c738bef79efe2b916442bd84 316a3aebad DROOLS-1701 misc fixes
b9430c86817182ff5be688fe39d98f37ab4187a2 b9430c8681 DROOLS-1701 unify CompiledExpression interface and JIT FEEL compilation
bebd3b4bc7c98b734c9b212b04851fff42d2f363 bebd3b4bc7 DROOLS-1701 Use CoedegenStringUtils escape function
820a7435df8f895fe6de9da80f7bd8f14bedf99e 820a7435df DROOLS-1701 Support floating point constant values
26d1ab6aec0e549a779b74c0cb7cf41153f69bb6 26d1ab6aec DROOLS-1701 Support for FEEL fn invocation using named parameters
63345dbb3c5b7a086e8fae83f25b6a632d0b46b9 63345dbb3c DROOLS-1701 Support for FEEL fn definition (non-external, FEEL defined)
e46b03c04fe9422b16c8f6e282c0d7ad210d8314 e46b03c04f DROOLS-1701 Support for FEEL fn invocation using positional parameters
a886c076dc43ad54a1c637dd9b86f0d4e7d0c735 a886c076dc DROOLS-1701 Support for FEEL quantified expression `some`, `every`
6c470047adf10ac9ebbbdc9838b239f7c41d66f6 6c470047ad DROOLS-1701 Basic support for FEEL `for` expression
cbaa6b2e9ac2c1c7152a9afd7a27091a1a39d5c7 cbaa6b2e9a DROOLS-1701 Align with new signature of EvaluationContext
e2b91c8e5f93e6f3db9494b632e55baba06328e5 e2b91c8e5f DROOLS-1701 extend coverage for Qualified name
1e7994165b8214292ec604465a4df22e49062675 1e7994165b DROOLS-1701 coverage filter/path for PATH selection
3b5f243af94b76ecd2fa9419a3b29933f5bce4cd 3b5f243af9 DROOLS-1701 coverage filter/path ONLY ref Table 54: Semantics of lists
6cf9bd32a861dbd23666bb003cde816949efb72b 6cf9bd32a8 DROOLS-1701 coverage of "between" function
aafad227d30c9f13755138a525d37653d4bb7571 aafad227d3 DROOLS-1701 coverage of "instance of" function
da970d4577e3e33895195d729ec175b659e179a5 da970d4577 DROOLS-1701 Align with new signature of FEELParser.parse()
8a272f2a1c364e98d5f369a91052baebb31059fa 8a272f2a1c DROOLS-1701 !=, not() unary tests
1d50d778a0af60d90a3f7f6b513b380c95ac1d62 1d50d778a0 DROOLS-1701 Align with DROOLS-2143 for allowing '--1' expression
0bf22c4b43d4afe3e4e636dc136af08532786f44 0bf22c4b43 DROOLS-1701 Align with new signature of FEELParser.parse()
1d974606e2dd4c782836654358599cd076400fe5 1d974606e2 DROOLS-1701 initial coverage of unary test codegen
6a6f20e5640291c0b16202a617b17c0a789c6a77 6a6f20e564 DROOLS-1701 realign following grammar change of DROOLS-1670
45436f8c185e2d3412fcaee24c30311fcde1958a 45436f8c18 DROOLS-1701 Extend code generation support for more complex FEEL Context
5ef187bba4640bf006e3e7e74f8383d79bafda94 5ef187bba4 DROOLS-1701 Context compiled API support, codegen for literal contexts
d8e214472d8fc9b16eda8c10e2b15386e8f76e84 d8e214472d DROOLS-1701 Extend support for simple built-in FEEL list construct
654640d226c8680727f3c089e1b40fba193b14eb 654640d226 DROOLS-1701 Extend support for logicalNegation expression
478639fcab5bce23f64af48d63acad6f95d0a25d 478639fcab DROOLS-1701 Extend support to exponentiation Expression
80dc207a6c5a40b77adfa32f9920bc127650e3f5 80dc207a6c DROOLS-1701 Refactoring and extend support to multiplicative expression
d3df15ead603fa24c4ba2ef272f322dc2dc98c18 d3df15ead6 DROOLS-1701 Partial support FEEL +, -; optimize number literal ...
2782096272c644d9cbdcda17d48a54a30cbd209a 2782096272 DROOLS-1701 Cover if-then-else as a Java ternary op
50a97941c6de43dd3b1be3ecb2091fd8a6704604 50a97941c6 DROOLS-1701 Migrate to use EvaluationContext as input for compiled code
e795dd6b07d9a4c1b76b61f7a6a21b1bf436c1dc e795dd6b07 DROOLS-1701 Optimize Boolean and, or
ef318f4ea52a888255d5e745d713519c2d240b4b ef318f4ea5 DROOLS-1701 initial coverage for FEEL code generation and compilation
> FEEL code generation and compilation
> ------------------------------------
>
> Key: DROOLS-1701
> URL: https://issues.jboss.org/browse/DROOLS-1701
> Project: Drools
> Issue Type: Task
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-1701) FEEL code generation and compilation
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1701?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-1701:
----------------------------------------
Commits on master covering all FEEL to Java translation under feature flag (special FEELProfile to enable translation, compilation and bytecode load)
3af4fe86f3bd04d1599a7a0ef2b6c1a54e5180c2 3af4fe86f3 DROOLS-1701 Final refactoring accordingly to PR comments and feedback
fd9cb4596259ffa4b74c8816a47957a72058e71f fd9cb45962 DROOLS-1701 Final touches (#14)
76f09d67bf090959de43279826bdbd527f3aa028 76f09d67bf DROOLS-1701 decide unary `not` execution at runtime (#13)
8ca8264cf4ec3a744684665ec286d8d4ddeaa6c4 8ca8264cf4 DROOLS-1701 minor refactoring
d6ee27e57974477cc6a6b761f72ecc421b5c330f d6ee27e579 DROOLS-1701 unary not expression (#12)
5914a9ae68f65053275a8bd18d5936f6efa38dd3 5914a9ae68 DROOLS-1701 Properly escape strings on compile (#11)
7d7f3a00b3088a124e579aa8146e3ed9afb7041a 7d7f3a00b3 DROOLS-1701 Report compilation error as a runtime error (#10)
9717dfe6a815b6165fcd4c04050aecbc9c0af0ea 9717dfe6a8 DROOLS-1701 Fix list test cases (#9)
cc20df38fea3d62e73d3a9045841cffb77aff07a cc20df38fe DROOLS-1701 Fix closure context handling, misc fn issues (#8)
200b1aeb7d1ca42d3ec1376aad83420a47585c71 200b1aeb7d DROOLS-1701 fixes to `between` and `in` (esp. with `null` handling) (#7)
a75cf2af616b97393cf9f683cdaab3b8bf8c98ff a75cf2af61 DROOLS-1701 fix some `in` test cases (#6)
efbddeac1b7933729e3042f7ab87a8f22c79a8ec efbddeac1b DROOLS-1701 fix: ranges cannot be (always) promoted to fields (#5)
42589c3b42ff0b1a2de83f7090db1bfdf038fb00 42589c3b42 DROOLS-1701 misc fixes
5b9a64b5e8ae409d56bbd904eac54276788a9488 5b9a64b5e8 DROOLS-1701 migrate from upstream JP to org.drools:drlx-parser
316a3aebad43f179c738bef79efe2b916442bd84 316a3aebad DROOLS-1701 misc fixes
b9430c86817182ff5be688fe39d98f37ab4187a2 b9430c8681 DROOLS-1701 unify CompiledExpression interface and JIT FEEL compilation
bebd3b4bc7c98b734c9b212b04851fff42d2f363 bebd3b4bc7 DROOLS-1701 Use CoedegenStringUtils escape function
820a7435df8f895fe6de9da80f7bd8f14bedf99e 820a7435df DROOLS-1701 Support floating point constant values
26d1ab6aec0e549a779b74c0cb7cf41153f69bb6 26d1ab6aec DROOLS-1701 Support for FEEL fn invocation using named parameters
63345dbb3c5b7a086e8fae83f25b6a632d0b46b9 63345dbb3c DROOLS-1701 Support for FEEL fn definition (non-external, FEEL defined)
e46b03c04fe9422b16c8f6e282c0d7ad210d8314 e46b03c04f DROOLS-1701 Support for FEEL fn invocation using positional parameters
a886c076dc43ad54a1c637dd9b86f0d4e7d0c735 a886c076dc DROOLS-1701 Support for FEEL quantified expression `some`, `every`
6c470047adf10ac9ebbbdc9838b239f7c41d66f6 6c470047ad DROOLS-1701 Basic support for FEEL `for` expression
cbaa6b2e9ac2c1c7152a9afd7a27091a1a39d5c7 cbaa6b2e9a DROOLS-1701 Align with new signature of EvaluationContext
e2b91c8e5f93e6f3db9494b632e55baba06328e5 e2b91c8e5f DROOLS-1701 extend coverage for Qualified name
1e7994165b8214292ec604465a4df22e49062675 1e7994165b DROOLS-1701 coverage filter/path for PATH selection
3b5f243af94b76ecd2fa9419a3b29933f5bce4cd 3b5f243af9 DROOLS-1701 coverage filter/path ONLY ref Table 54: Semantics of lists
6cf9bd32a861dbd23666bb003cde816949efb72b 6cf9bd32a8 DROOLS-1701 coverage of "between" function
aafad227d30c9f13755138a525d37653d4bb7571 aafad227d3 DROOLS-1701 coverage of "instance of" function
da970d4577e3e33895195d729ec175b659e179a5 da970d4577 DROOLS-1701 Align with new signature of FEELParser.parse()
8a272f2a1c364e98d5f369a91052baebb31059fa 8a272f2a1c DROOLS-1701 !=, not() unary tests
1d50d778a0af60d90a3f7f6b513b380c95ac1d62 1d50d778a0 DROOLS-1701 Align with DROOLS-2143 for allowing '--1' expression
0bf22c4b43d4afe3e4e636dc136af08532786f44 0bf22c4b43 DROOLS-1701 Align with new signature of FEELParser.parse()
1d974606e2dd4c782836654358599cd076400fe5 1d974606e2 DROOLS-1701 initial coverage of unary test codegen
6a6f20e5640291c0b16202a617b17c0a789c6a77 6a6f20e564 DROOLS-1701 realign following grammar change of DROOLS-1670
45436f8c185e2d3412fcaee24c30311fcde1958a 45436f8c18 DROOLS-1701 Extend code generation support for more complex FEEL Context
5ef187bba4640bf006e3e7e74f8383d79bafda94 5ef187bba4 DROOLS-1701 Context compiled API support, codegen for literal contexts
d8e214472d8fc9b16eda8c10e2b15386e8f76e84 d8e214472d DROOLS-1701 Extend support for simple built-in FEEL list construct
654640d226c8680727f3c089e1b40fba193b14eb 654640d226 DROOLS-1701 Extend support for logicalNegation expression
478639fcab5bce23f64af48d63acad6f95d0a25d 478639fcab DROOLS-1701 Extend support to exponentiation Expression
80dc207a6c5a40b77adfa32f9920bc127650e3f5 80dc207a6c DROOLS-1701 Refactoring and extend support to multiplicative expression
d3df15ead603fa24c4ba2ef272f322dc2dc98c18 d3df15ead6 DROOLS-1701 Partial support FEEL +, -; optimize number literal ...
2782096272c644d9cbdcda17d48a54a30cbd209a 2782096272 DROOLS-1701 Cover if-then-else as a Java ternary op
50a97941c6de43dd3b1be3ecb2091fd8a6704604 50a97941c6 DROOLS-1701 Migrate to use EvaluationContext as input for compiled code
e795dd6b07d9a4c1b76b61f7a6a21b1bf436c1dc e795dd6b07 DROOLS-1701 Optimize Boolean and, or
ef318f4ea52a888255d5e745d713519c2d240b4b ef318f4ea5 DROOLS-1701 initial coverage for FEEL code generation and compilation
> FEEL code generation and compilation
> ------------------------------------
>
> Key: DROOLS-1701
> URL: https://issues.jboss.org/browse/DROOLS-1701
> Project: Drools
> Issue Type: Task
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-294) Investigate ElasticSearch memory requirements on B24 cluster
by Pavol Loffay (JIRA)
[ https://issues.jboss.org/browse/SWSQE-294?page=com.atlassian.jira.plugin.... ]
Pavol Loffay commented on SWSQE-294:
------------------------------------
hi [~fbrychta]. I would probably suggest to go with default ECL settings. https://issues.jboss.org/browse/TRACING-61 summarizes what should be configured.
Can somebody describe when ES is failing? Locally I haven't seen any failures even when reporting 300k spans (minishift or istiooc).
> Investigate ElasticSearch memory requirements on B24 cluster
> ------------------------------------------------------------
>
> Key: SWSQE-294
> URL: https://issues.jboss.org/browse/SWSQE-294
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Kevin Earls
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
> Attachments: es1.log
>
>
> On minishift and the CNCF CI OpenShift cluster, we install ElasticSearch using the commands:
> curl https://raw.githubusercontent.com/RHsyseng/docker-rhel-elasticsearch/5.x/... --output es-cluster-deployment.yml
> oc create -f es-cluster-deployment.yml
> However, on B24 this fails. The first 2 elasticsearch pods will start up, but then elasticsearch-2 gets into the following failure loop like:
> elasticsearch-2 1/1 Running 3 1m
> elasticsearch-2 0/1 OOMKilled 3 1m
> elasticsearch-2 0/1 CrashLoopBackOff 3 2m
> If I increase memory in the es-cluster-deployment.yml to 1Gi it will at least start, but I've found I really need to increase it to 2Gi to do anything non trivial.
> We may need to track down the people who originally created this template for help on this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (LOGMGR-52) Add option to WriterHandler to collapse repeated messages
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-52?page=com.atlassian.jira.plugin.... ]
James Perkins updated LOGMGR-52:
--------------------------------
Fix Version/s: 2.1.5.Final
(was: 2.1.4.Final)
> Add option to WriterHandler to collapse repeated messages
> ---------------------------------------------------------
>
> Key: LOGMGR-52
> URL: https://issues.jboss.org/browse/LOGMGR-52
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 2.1.5.Final
>
>
> The WriterHandler could have a time interval configured wherein a repeated message would be collapsed.
> The last message would be stored in a field for comparison along with a nanoTime tag (the timestamp on the message is not adequate because the clock can have skew or be reset completely at any time). If the current message string equals the last message string, and collapsing is enabled, then instead of logging the message, a count is incremented. If the current message is not equal, then the stored message is logged with a tag indicating the number of repeats (i18n?) and then the next submitted message is logged.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years