[JBoss JIRA] (WFCORE-1703) It is not possible to set jboss.modules.system.pkgs per server in domain mode
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1703?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-1703:
----------------------------------------
Component/s: Domain Management
Assignee: (was: Jason Greene)
> It is not possible to set jboss.modules.system.pkgs per server in domain mode
> -----------------------------------------------------------------------------
>
> Key: WFCORE-1703
> URL: https://issues.jboss.org/browse/WFCORE-1703
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.2.0.Final
> Reporter: Bogdan Ilchyshyn
> Priority: Minor
>
> It is not possible to set {{jboss.modules.system.pkgs}} property per server / server group in domain configuration. Even when the following configuration is added to {{host.xml}}:
> {code:xml}
> <server name="server-one" group="main-server-group">
> <jvm name="default">
> <jvm-options>
> <option value="-Djboss.modules.system.pkgs=my.package"/>
> ...
> {code}
> It is overridden by configuration in {{domain.conf}}:
> {noformat}
> JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
> {noformat}
> This is an issue for configuring third-party java agents per-server. A problem described in WFLY-895 adds to this. One should either add a whole bunch of things to _all_ jvms in domain in order to make agent work, or remove config from {{domain.conf}} to avoid overrides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1703) It is not possible to set jboss.modules.system.pkgs per server in domain mode
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1703?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved WFLY-6929 to WFCORE-1703:
------------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-1703 (was: WFLY-6929)
Affects Version/s: 2.2.0.Final
(was: 10.0.0.Final)
> It is not possible to set jboss.modules.system.pkgs per server in domain mode
> -----------------------------------------------------------------------------
>
> Key: WFCORE-1703
> URL: https://issues.jboss.org/browse/WFCORE-1703
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 2.2.0.Final
> Reporter: Bogdan Ilchyshyn
> Assignee: Jason Greene
> Priority: Minor
>
> It is not possible to set {{jboss.modules.system.pkgs}} property per server / server group in domain configuration. Even when the following configuration is added to {{host.xml}}:
> {code:xml}
> <server name="server-one" group="main-server-group">
> <jvm name="default">
> <jvm-options>
> <option value="-Djboss.modules.system.pkgs=my.package"/>
> ...
> {code}
> It is overridden by configuration in {{domain.conf}}:
> {noformat}
> JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
> {noformat}
> This is an issue for configuring third-party java agents per-server. A problem described in WFLY-895 adds to this. One should either add a whole bunch of things to _all_ jvms in domain in order to make agent work, or remove config from {{domain.conf}} to avoid overrides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-1175) Accumulates: sum(Long), sum(BigDecimal), sum(Integer) and sum(BigInteger)
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1175?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet commented on DROOLS-1175:
------------------------------------------
I ran benchmarks on this, and these are the percentage gains I am seeing:
||Example||new||old||gain||
|Cloud Balancing |104327 |95582 |9.15%|
|Machine Reassignment |169405 |168904 |0.30%|
|Course Scheduling |10319 |10753 |-4.04%|
|Examination |12649 |12957 |-2.38%|
|Nurse Rostering |6552 |6437 |1.79%|
|TravelingTournament |2262 |2243 |0.85%|
> Accumulates: sum(Long), sum(BigDecimal), sum(Integer) and sum(BigInteger)
> -------------------------------------------------------------------------
>
> Key: DROOLS-1175
> URL: https://issues.jboss.org/browse/DROOLS-1175
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 6.4.0.Final
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
> Fix For: 7.0.0.Beta2
>
>
> Currently, when summing longs in an accumulate, we get something like this:
> {code}
> when ...
> $t : Number(...) from accumulate(...,
> sum($p.getLongWeight()))
> then scoreHolder.addHard($t.longValue());
> {code}
> This has 3 problems:
> - *Loss of precision*: the long sum `1881617265586265321L` will incorrectly return `1.88161726558626534E18`, so `13` too much! The BigDecimal sum of `0.09` and `0.01` will also be incorrect.
> - *Loss of performance*: Summing with a Double total is significantly slower than summing with a Long total or an Integer total.
> - Example complexity (minor, not all of us agree on this argument): the use of `Number` is an abstraction that doesn't bring any value to the use case. It's worthless complexity.
> Solution proposal A) for 7.0 as discussed with Mario:
> Based on the argument type to the sum function, the compiler selects a different sum function implementation. This is similar to java overloading mechanism, where `System.out.println(1)` selects a different method implementation than `System.out.println(2.0)`.
> Support sum(Long):
> {code}
> when ...
> $t : Long(...) from accumulate(...,
> sum($p.getLongWeight()))
> then scoreHolder.addHard($t);
> {code}
> and sum(BigDecimal):
> {code}
> when ...
> $t : BigDecimal(...) from accumulate(...,
> sum($p.getBigDecimalWeight()))
> then scoreHolder.addHard($t);
> {code}
> and also support sum(Integer) and sum(BigInteger).
> If this works well, we can consider it for other functions as well in a different jira issue.
> Special case 1: sum(Number) should default to sum(Double) for backwards compatibility.
> {code}
> when ...
> $t : Number(...) from accumulate(...,
> sum($p.getNumberWeight()))
> then scoreHolder.addHard($t.doubleValue());
> {code}
> Not-so-special case 2: to sum integers into a long total, the user should just use:
> {code}
> $t : Long(...) from accumulate(...,
> sum((long) $p.getIntWeight()))
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1702) WF Core StringBytesLengthValidator should not use error message considering characters
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1702?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-1702:
------------------------------------------
The fix for this is just a new error message method that say 'bytes' instead of 'characters'.
> WF Core StringBytesLengthValidator should not use error message considering characters
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-1702
> URL: https://issues.jboss.org/browse/WFCORE-1702
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Ondra Chaloupka
> Priority: Minor
> Fix For: 3.0.0.CR1
>
>
> Current implementation of class {{StringBytesLengthValidator}} which is used by {{TransactionSubsystemRootResourceDefinition}} for validation of {{node-identifier}} element prints error message in format
> {code}
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[356,13]
> Message: "WFLYCTL0112: '' is an invalid value for parameter node-identifier. Values must have a maximum length of 23 characters"
> {code}
> but the validator does not count characters of the string but bytes of the string. Then could occur if some none-ascii character are part of the {{node id}} that the string has length smaller than {{23}} but the message says that it's bigger.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1702) WF Core StringBytesLengthValidator should not use error message considering characters
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1702?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-1702:
----------------------------------------
Assignee: (was: Brian Stansberry)
> WF Core StringBytesLengthValidator should not use error message considering characters
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-1702
> URL: https://issues.jboss.org/browse/WFCORE-1702
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Ondra Chaloupka
> Priority: Minor
> Fix For: 3.0.0.CR1
>
>
> Current implementation of class {{StringBytesLengthValidator}} which is used by {{TransactionSubsystemRootResourceDefinition}} for validation of {{node-identifier}} element prints error message in format
> {code}
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[356,13]
> Message: "WFLYCTL0112: '' is an invalid value for parameter node-identifier. Values must have a maximum length of 23 characters"
> {code}
> but the validator does not count characters of the string but bytes of the string. Then could occur if some none-ascii character are part of the {{node id}} that the string has length smaller than {{23}} but the message says that it's bigger.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1702) WF Core StringBytesLengthValidator should not use error message considering characters
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1702?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1702:
-------------------------------------
Fix Version/s: 3.0.0.CR1
> WF Core StringBytesLengthValidator should not use error message considering characters
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-1702
> URL: https://issues.jboss.org/browse/WFCORE-1702
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Ondra Chaloupka
> Priority: Minor
> Fix For: 3.0.0.CR1
>
>
> Current implementation of class {{StringBytesLengthValidator}} which is used by {{TransactionSubsystemRootResourceDefinition}} for validation of {{node-identifier}} element prints error message in format
> {code}
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[356,13]
> Message: "WFLYCTL0112: '' is an invalid value for parameter node-identifier. Values must have a maximum length of 23 characters"
> {code}
> but the validator does not count characters of the string but bytes of the string. Then could occur if some none-ascii character are part of the {{node id}} that the string has length smaller than {{23}} but the message says that it's bigger.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFCORE-1702) WF Core StringBytesLengthValidator should not use error message considering characters
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1702?page=com.atlassian.jira.plugi... ]
Brian Stansberry moved JBEAP-5589 to WFCORE-1702:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1702 (was: JBEAP-5589)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
(was: Transactions)
Affects Version/s: (was: 7.1.0.DR2)
> WF Core StringBytesLengthValidator should not use error message considering characters
> --------------------------------------------------------------------------------------
>
> Key: WFCORE-1702
> URL: https://issues.jboss.org/browse/WFCORE-1702
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Ondra Chaloupka
> Assignee: Brian Stansberry
> Priority: Minor
>
> Current implementation of class {{StringBytesLengthValidator}} which is used by {{TransactionSubsystemRootResourceDefinition}} for validation of {{node-identifier}} element prints error message in format
> {code}
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[356,13]
> Message: "WFLYCTL0112: '' is an invalid value for parameter node-identifier. Values must have a maximum length of 23 characters"
> {code}
> but the validator does not count characters of the string but bytes of the string. Then could occur if some none-ascii character are part of the {{node id}} that the string has length smaller than {{23}} but the message says that it's bigger.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (DROOLS-1235) MBean naming rework
by Matteo Mortari (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1235?page=com.atlassian.jira.plugi... ]
Matteo Mortari edited comment on DROOLS-1235 at 8/9/16 10:03 AM:
-----------------------------------------------------------------
To recap:
h6. droolsjbpm-knowledge
* Perform necessary Public KIE API changes for allowing API users to
specify an optional, unique, container ID.
h6. drools
* give KieContainer an optional user defined name
* KieContainer MBean and various refactorings.
* jargon: containerId
* jargon: configuredReleaseId, resolvedReleaseId
* unit testing
* assuming the containerId can be "recycled" on dispose.
* introducing test for KieServices API with containerId.
* fixing other tests.
* avoid using lock and leverage ConcurrentMap without java8
* fixing objectname conventions
h6. droolsjbpm-integration
* KieServer cascade containerId while creating via KieServices
h6. kie-docs
* Including an entry for this on the release notes, as requested.
h6. kie-wb-common
* reflecting internal api / implementation of KieContainerImpl constructor change, requiring a container Id (normally a new KieContainerImpl is called via KieServices so transparently, but in this case is explicitly required manual management).
was (Author: tari_manga):
To recap:
h6. droolsjbpm-knowledge
* Perform necessary Public KIE API changes for allowing API users to
specify an optional, unique, container ID.
h6. drools
* give KieContainer an optional user defined name
* KieContainer MBean and various refactorings.
* jargon: containerId
* jargon: configuredReleaseId, resolvedReleaseId
* unit testing
* assuming the containerId can be "recycled" on dispose.
* introducing test for KieServices API with containerId.
* fixing other tests.
* avoid using lock and leverage ConcurrentMap without java8
* fixing objectname conventions
h6. droolsjbpm-integration
* KieServer cascade containerId while creating via KieServices
h6. kie-docs
* Including an entry for this on the release notes, as requested.
> MBean naming rework
> -------------------
>
> Key: DROOLS-1235
> URL: https://issues.jboss.org/browse/DROOLS-1235
> Project: Drools
> Issue Type: Sub-task
> Components: core engine, kie server
> Affects Versions: 6.4.0.Final
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
> Fix For: 6.5.0.Final, 7.0.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (WFLY-4316) InvalidBytecodeException when an EJB local interface declares static method
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4316?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-4316:
-----------------------------------------------
Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1346242|https://bugzilla.redhat.com/show_bug.cgi?id=1346242] from ON_QA to VERIFIED
> InvalidBytecodeException when an EJB local interface declares static method
> ---------------------------------------------------------------------------
>
> Key: WFLY-4316
> URL: https://issues.jboss.org/browse/WFLY-4316
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 9.0.0.Alpha1
> Reporter: Jozef Hartinger
> Assignee: Jozef Hartinger
> Fix For: 9.0.0.Beta1
>
>
> {noformat}
> Caused by: org.jboss.classfilewriter.InvalidBytecodeException: Cannot load variable at 1. Local Variables: Local Variables: [StackEntry [descriptor=Ljava/lang/String;, type=OBJECT]]
> at org.jboss.classfilewriter.code.CodeAttribute.aload(CodeAttribute.java:185)
> at org.jboss.invocation.proxy.ProxyFactory$ProxyMethodBodyCreator.overrideMethod(ProxyFactory.java:150)
> at org.jboss.invocation.proxy.AbstractSubclassFactory.overrideMethod(AbstractSubclassFactory.java:106)
> at org.jboss.invocation.proxy.AbstractSubclassFactory.addInterface(AbstractSubclassFactory.java:363)
> at org.jboss.invocation.proxy.ProxyFactory.generateClass(ProxyFactory.java:286)
> at org.jboss.invocation.proxy.AbstractClassFactory.buildClassDefinition(AbstractClassFactory.java:207)
> at org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:160)
> at org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:150)
> at org.jboss.as.ejb3.component.stateless.StatelessComponentDescription$3.configure(StatelessComponentDescription.java:150)
> at org.jboss.as.ee.component.DefaultComponentViewConfigurator.configure(DefaultComponentViewConfigurator.java:68)
> at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)
> ... 6 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months