[JBoss JIRA] (WFCORE-1974) Inconsistency in resource description
by Radim Hatlapatka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1974?page=com.atlassian.jira.plugi... ]
Radim Hatlapatka updated WFCORE-1974:
-------------------------------------
Priority: Trivial (was: Minor)
> Inconsistency in resource description
> --------------------------------------
>
> Key: WFCORE-1974
> URL: https://issues.jboss.org/browse/WFCORE-1974
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Radim Hatlapatka
> Assignee: Brian Stansberry
> Priority: Trivial
> Labels: user_experience
>
> The description format is inconsistent in relation to starting with camel case and in relation to ending with full stop. This should be ideally consistent.
> There are some inconsistencies noted with Undertow subsystem that I've noted, still the issue is general:
> # Start with uppercase/lowercase >>"description" => "*_+enables+_* x-for ... "<< {noformat}"proxy-address-forwarding" => {
> "type" => BOOLEAN,
> "description" => "enables x-forwarded-host and similar headers and set a remote ip address and hostname",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => false,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> {noformat} vs {noformat}"url-charset" => {
> "type" => STRING,
> "description" => "URL charset",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => "UTF-8",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat}
> # End with dot/no dot {noformat}"url-charset" => {
> "type" => STRING,
> "description" => "URL charset",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => "UTF-8",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat} vs {noformat}"receive-buffer" => {
> "type" => INT,
> "description" => "The receive buffer size, in bytes.",
> "expressions-allowed" => true,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat}
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1974) Inconsistency in resource description
by Radim Hatlapatka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1974?page=com.atlassian.jira.plugi... ]
Radim Hatlapatka updated WFCORE-1974:
-------------------------------------
Description:
The description format is inconsistent in relation to starting with camel case and in relation to ending with full stop. This should be ideally consistent.
There are some inconsistencies noted with Undertow subsystem that I've noted, still the issue is general:
# Start with uppercase/lowercase >>"description" => "*_+enables+_* x-for ... "<< {noformat}"proxy-address-forwarding" => {
"type" => BOOLEAN,
"description" => "enables x-forwarded-host and similar headers and set a remote ip address and hostname",
"expressions-allowed" => true,
"nillable" => true,
"default" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
{noformat} vs {noformat}"url-charset" => {
"type" => STRING,
"description" => "URL charset",
"expressions-allowed" => true,
"nillable" => true,
"default" => "UTF-8",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"{noformat}
# End with dot/no dot {noformat}"url-charset" => {
"type" => STRING,
"description" => "URL charset",
"expressions-allowed" => true,
"nillable" => true,
"default" => "UTF-8",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"{noformat} vs {noformat}"receive-buffer" => {
"type" => INT,
"description" => "The receive buffer size, in bytes.",
"expressions-allowed" => true,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"{noformat}
was:
There are 2 inconsistencies that I've noted.
# Start with uppercase/lowercase >>"description" => "*_+enables+_* x-for ... "<< {noformat}"proxy-address-forwarding" => {
"type" => BOOLEAN,
"description" => "enables x-forwarded-host and similar headers and set a remote ip address and hostname",
"expressions-allowed" => true,
"nillable" => true,
"default" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
{noformat} vs {noformat}"url-charset" => {
"type" => STRING,
"description" => "URL charset",
"expressions-allowed" => true,
"nillable" => true,
"default" => "UTF-8",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"{noformat}
# End with dot/no dot {noformat}"url-charset" => {
"type" => STRING,
"description" => "URL charset",
"expressions-allowed" => true,
"nillable" => true,
"default" => "UTF-8",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"{noformat} vs {noformat}"receive-buffer" => {
"type" => INT,
"description" => "The receive buffer size, in bytes.",
"expressions-allowed" => true,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"{noformat}
> Inconsistency in resource description
> --------------------------------------
>
> Key: WFCORE-1974
> URL: https://issues.jboss.org/browse/WFCORE-1974
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Radim Hatlapatka
> Priority: Minor
> Labels: user_experience
>
> The description format is inconsistent in relation to starting with camel case and in relation to ending with full stop. This should be ideally consistent.
> There are some inconsistencies noted with Undertow subsystem that I've noted, still the issue is general:
> # Start with uppercase/lowercase >>"description" => "*_+enables+_* x-for ... "<< {noformat}"proxy-address-forwarding" => {
> "type" => BOOLEAN,
> "description" => "enables x-forwarded-host and similar headers and set a remote ip address and hostname",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => false,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> {noformat} vs {noformat}"url-charset" => {
> "type" => STRING,
> "description" => "URL charset",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => "UTF-8",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat}
> # End with dot/no dot {noformat}"url-charset" => {
> "type" => STRING,
> "description" => "URL charset",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => "UTF-8",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat} vs {noformat}"receive-buffer" => {
> "type" => INT,
> "description" => "The receive buffer size, in bytes.",
> "expressions-allowed" => true,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat}
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1974) Inconsistency in resource description
by Radim Hatlapatka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1974?page=com.atlassian.jira.plugi... ]
Radim Hatlapatka reassigned WFCORE-1974:
----------------------------------------
Assignee: Brian Stansberry
> Inconsistency in resource description
> --------------------------------------
>
> Key: WFCORE-1974
> URL: https://issues.jboss.org/browse/WFCORE-1974
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Radim Hatlapatka
> Assignee: Brian Stansberry
> Priority: Minor
> Labels: user_experience
>
> The description format is inconsistent in relation to starting with camel case and in relation to ending with full stop. This should be ideally consistent.
> There are some inconsistencies noted with Undertow subsystem that I've noted, still the issue is general:
> # Start with uppercase/lowercase >>"description" => "*_+enables+_* x-for ... "<< {noformat}"proxy-address-forwarding" => {
> "type" => BOOLEAN,
> "description" => "enables x-forwarded-host and similar headers and set a remote ip address and hostname",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => false,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> {noformat} vs {noformat}"url-charset" => {
> "type" => STRING,
> "description" => "URL charset",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => "UTF-8",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat}
> # End with dot/no dot {noformat}"url-charset" => {
> "type" => STRING,
> "description" => "URL charset",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => "UTF-8",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat} vs {noformat}"receive-buffer" => {
> "type" => INT,
> "description" => "The receive buffer size, in bytes.",
> "expressions-allowed" => true,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat}
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1974) Inconsistency in resource description
by Radim Hatlapatka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1974?page=com.atlassian.jira.plugi... ]
Radim Hatlapatka updated WFCORE-1974:
-------------------------------------
Labels: user_experience (was: )
> Inconsistency in resource description
> --------------------------------------
>
> Key: WFCORE-1974
> URL: https://issues.jboss.org/browse/WFCORE-1974
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Radim Hatlapatka
> Priority: Minor
> Labels: user_experience
>
> There are 2 inconsistencies that I've noted.
> # Start with uppercase/lowercase >>"description" => "*_+enables+_* x-for ... "<< {noformat}"proxy-address-forwarding" => {
> "type" => BOOLEAN,
> "description" => "enables x-forwarded-host and similar headers and set a remote ip address and hostname",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => false,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> {noformat} vs {noformat}"url-charset" => {
> "type" => STRING,
> "description" => "URL charset",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => "UTF-8",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat}
> # End with dot/no dot {noformat}"url-charset" => {
> "type" => STRING,
> "description" => "URL charset",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => "UTF-8",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat} vs {noformat}"receive-buffer" => {
> "type" => INT,
> "description" => "The receive buffer size, in bytes.",
> "expressions-allowed" => true,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat}
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1974) Inconsistency in resource description
by Radim Hatlapatka (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1974?page=com.atlassian.jira.plugi... ]
Radim Hatlapatka updated WFCORE-1974:
-------------------------------------
Component/s: Domain Management
> Inconsistency in resource description
> --------------------------------------
>
> Key: WFCORE-1974
> URL: https://issues.jboss.org/browse/WFCORE-1974
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Radim Hatlapatka
> Priority: Minor
> Labels: user_experience
>
> There are 2 inconsistencies that I've noted.
> # Start with uppercase/lowercase >>"description" => "*_+enables+_* x-for ... "<< {noformat}"proxy-address-forwarding" => {
> "type" => BOOLEAN,
> "description" => "enables x-forwarded-host and similar headers and set a remote ip address and hostname",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => false,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "resource-services"
> {noformat} vs {noformat}"url-charset" => {
> "type" => STRING,
> "description" => "URL charset",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => "UTF-8",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat}
> # End with dot/no dot {noformat}"url-charset" => {
> "type" => STRING,
> "description" => "URL charset",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => "UTF-8",
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat} vs {noformat}"receive-buffer" => {
> "type" => INT,
> "description" => "The receive buffer size, in bytes.",
> "expressions-allowed" => true,
> "nillable" => true,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"{noformat}
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFCORE-1974) Inconsistency in resource description
by Radim Hatlapatka (JIRA)
Radim Hatlapatka created WFCORE-1974:
----------------------------------------
Summary: Inconsistency in resource description
Key: WFCORE-1974
URL: https://issues.jboss.org/browse/WFCORE-1974
Project: WildFly Core
Issue Type: Bug
Reporter: Radim Hatlapatka
Priority: Minor
There are 2 inconsistencies that I've noted.
# Start with uppercase/lowercase >>"description" => "*_+enables+_* x-for ... "<< {noformat}"proxy-address-forwarding" => {
"type" => BOOLEAN,
"description" => "enables x-forwarded-host and similar headers and set a remote ip address and hostname",
"expressions-allowed" => true,
"nillable" => true,
"default" => false,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "resource-services"
{noformat} vs {noformat}"url-charset" => {
"type" => STRING,
"description" => "URL charset",
"expressions-allowed" => true,
"nillable" => true,
"default" => "UTF-8",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"{noformat}
# End with dot/no dot {noformat}"url-charset" => {
"type" => STRING,
"description" => "URL charset",
"expressions-allowed" => true,
"nillable" => true,
"default" => "UTF-8",
"min-length" => 1L,
"max-length" => 2147483647L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"{noformat} vs {noformat}"receive-buffer" => {
"type" => INT,
"description" => "The receive buffer size, in bytes.",
"expressions-allowed" => true,
"nillable" => true,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "no-services"{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (DROOLS-1250) Drools Sample.drl is broken
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1250?page=com.atlassian.jira.plugi... ]
Tomas David commented on DROOLS-1250:
-------------------------------------
I checked that this issue is fixed in Drools plugin 6.5.0.Final.
Tested environment:
* Fedora 24 and Windows 10
* Eclipse neon 4.6
* Drools plugin 6.5.0.Final
* Drools runtime 6.5.0.Final
> Drools Sample.drl is broken
> ---------------------------
>
> Key: DROOLS-1250
> URL: https://issues.jboss.org/browse/DROOLS-1250
> Project: Drools
> Issue Type: Feature Request
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Reporter: Tianwei Chen
> Assignee: Robert (Bob) Brodt
> Fix For: 6.5.0.Final
>
>
> Hello, I use drools plugin (6.4.0.Final) in Eclipse Neon. I followed the wizard to create a drools project with some example files. After the step were done, Eclipse highlighted errors at the two rules in the Sample.drl file. Here is one of the errors:
> Multiple markers at this line
> - com.sample.DroolsTest.Message cannot be resolved to a type
> - org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> - Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> - org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> - KnowledgeHelper cannot be resolved to a type
> - Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> - Message.GOODBYE cannot be resolved to a type
> - org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> - java.lang.Exception cannot be resolved to a type
> When I ran DroolsTest.java, I got the following error:
> java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=Sample.drl, line=15, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type], Message [id=2, level=ERROR, path=Sample.drl, line=5, column=0
> text=Rule Compilation error Only a type can be imported. com.sample.DroolsTest.Message resolves to a package
> Only a type can be imported. org.drools.core.spi.KnowledgeHelper resolves to a package
> KnowledgeHelper cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> org.kie.api.runtime.rule.FactHandle cannot be resolved to a type
> java.lang.Exception cannot be resolved to a type
> org.kie.api.runtime.rule.RuleContext cannot be resolved to a type
> Message.GOODBYE cannot be resolved to a type
> org.drools.core.util.bitmask.AllSetBitMask cannot be resolved to a type
> com.sample.DroolsTest.Message cannot be resolved to a type]]
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieContainerImpl.java:450)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:604)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(KieContainerImpl.java:575)
> It seems like an library path issue. Please help!
> Thank you very much!
> Tianwei Chen
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months
[JBoss JIRA] (WFLY-7457) UT005013 causes OutOfMemoryError
by Steve Vater (JIRA)
[ https://issues.jboss.org/browse/WFLY-7457?page=com.atlassian.jira.plugin.... ]
Steve Vater commented on WFLY-7457:
-----------------------------------
Unfortunately not at this point, no.
Our customer finally follows the RFC-recommendation to send a "close_notify". Since then, there's no OutOfMemoryError anymore.
> UT005013 causes OutOfMemoryError
> --------------------------------
>
> Key: WFLY-7457
> URL: https://issues.jboss.org/browse/WFLY-7457
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.1.0.Final
> Reporter: Steve Vater
> Assignee: Stuart Douglas
> Labels: new_and_noteworthy
>
> There's some F5 WAF within the network where our WildFly is running. The WAF sends multiple Keep Alive-Requests to our WAF via TCP, but without sending "close_notify" after the communication has ended.
> Undertow throws UT005013, which is correct, but this causes the JVM to run out of Memory. The keepalive is sent 12 times per minute (every 5 seconds) to our WildFly.
> We already installed an update of Undertow (1.4.3); This didn't help.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 8 months