[JBoss JIRA] (JGRP-2167) Highest seqno is not resent nor recorded on receivers
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/JGRP-2167?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on JGRP-2167:
-----------------------------------
Then I suggest adding another counter (hs = highest sent?) that will keep this information, and test this in {{LastSeqnoResender}}.
> I suggest this as a workaround for now
I've already sent a PR with this workaround to Infinispan, but since you've closed this as 'Won't fix', do you intend to ignore this issue completely? Have you considered setting the default value for {{resend_last_seqno_max_times}} to a very high value? A situation like this is non-trivial to detect & analyze, and user can end up with blocked application for no obvious reason.
> Highest seqno is not resent nor recorded on receivers
> -----------------------------------------------------
>
> Key: JGRP-2167
> URL: https://issues.jboss.org/browse/JGRP-2167
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.1
> Reporter: Radim Vansa
> Assignee: Bela Ban
> Fix For: 4.0.2
>
>
> I am investigating an issue in a stress test which leads me to a situation where in a TCP-based configuration a {{GMS[VIEW]}} is broadcast to all nodes, but it is not received by some of them. Soon after that there's a {{NAKACK2.HIGHEST_SEQNO}} that causes the node that is missing the last seqno to resend it, but the retransmit is not received either. There are no further retries, and generally no NAKACK2 activity until about 30 seconds later (when another node leaves after some timeout in the test).
> The receiver does not keep asking for retransmissions until it gets them, but it seems that {{NAKACK2.handleHighestSeqno}} doesn't update {{Table.hr}} (not sure if having highest received set to non-received msg would be legal, though).
> The sender uses default value {{NAKACK2.resend_last_seqno_max_times=1}}, and as there are no further mcast messages, the highest sent seqno does not change on sender.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8593) Wildfly should log bound ports
by Jason Tedor (JIRA)
[ https://issues.jboss.org/browse/WFLY-8593?page=com.atlassian.jira.plugin.... ]
Jason Tedor updated WFLY-8593:
------------------------------
Git Pull Request: https://issues.jboss.org/browse/WFLY-8593
> Wildfly should log bound ports
> ------------------------------
>
> Key: WFLY-8593
> URL: https://issues.jboss.org/browse/WFLY-8593
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (Undertow)
> Reporter: Jason Tedor
> Assignee: Stuart Douglas
>
> When binding Wildfly to an ephemeral port (i.e., by specifying port 0), Wildfly does not log the port that it actually binds to, but instead logs the port as 0.
> {{09:11:18,955 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:0}}
> Instead, Wildfly should log the ephemeral port that it actually bound to:
> {{09:11:58,769 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:52928}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8593) Wildfly should log bound ports
by Jason Tedor (JIRA)
[ https://issues.jboss.org/browse/WFLY-8593?page=com.atlassian.jira.plugin.... ]
Jason Tedor commented on WFLY-8593:
-----------------------------------
I opened https://github.com/wildfly/wildfly/pull/9943 for this.
> Wildfly should log bound ports
> ------------------------------
>
> Key: WFLY-8593
> URL: https://issues.jboss.org/browse/WFLY-8593
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (Undertow)
> Reporter: Jason Tedor
> Assignee: Stuart Douglas
>
> When binding Wildfly to an ephemeral port (i.e., by specifying port 0), Wildfly does not log the port that it actually binds to, but instead logs the port as 0.
> {{09:11:18,955 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:0}}
> Instead, Wildfly should log the ephemeral port that it actually bound to:
> {{09:11:58,769 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:52928}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8593) Wildfly should log bound ports
by Jason Tedor (JIRA)
Jason Tedor created WFLY-8593:
---------------------------------
Summary: Wildfly should log bound ports
Key: WFLY-8593
URL: https://issues.jboss.org/browse/WFLY-8593
Project: WildFly
Issue Type: Enhancement
Components: Web (Undertow)
Reporter: Jason Tedor
Assignee: Stuart Douglas
When binding Wildfly to an ephemeral port (i.e., by specifying port 0), Wildfly does not log the port that it actually binds to, but instead logs the port as 0.
{{09:11:18,955 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:0}}
Instead, Wildfly should log the ephemeral port that it actually bound to:
{{09:11:58,769 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:52928}}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2684) IO extension doesn't initialise outbound bind addresses
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-2684:
--------------------------------------------
Summary: IO extension doesn't initialise outbound bind addresses
Key: WFCORE-2684
URL: https://issues.jboss.org/browse/WFCORE-2684
Project: WildFly Core
Issue Type: Bug
Components: IO
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
WorkerService.start and OutboundBindAddressAddHandler execute in //. The add handler is executed first, so the table is still null.
The Builder table must be returned by the Service.
Furthermore the OutboundBindAddressRemoveHandler uses the operation ModelNode instead of the model, so there is no way to remove an OutboundBind address.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8592) Add xts dependency for war created by maven in wsat-simple quickstart
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8592?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-8592:
------------------------------
Description:
Creating {{war}} package in {{wsat-simple}} quickstart give a user way to check the functionality of the WS-AT on his own. He can take the war and deploy it on two containers and then invoked the servlet at {{http://localhost:8180/WSATSimpleServletClient}}. But currently, the war fails to be deployed as there is missing {{xts}} dependency in the deployment.
The Arquillian test passes as there is such dependency added by Shrinkwrap in the test, see
https://github.com/wildfly/quickstart/blob/11.x/wsat-simple/src/test/java...
{{pom.xml}} should configure the war to contain the {{XTS}} dependency.
was:
Creating {{war}} package in {{wsat-simple}} quickstart give a user way to check the functionality of the WS-AT on his own. He can take the war and deploy it on two containers and then invoked the servlet at {{http://localhost:8180/WSATSimpleServletClient}}. But currently, the war fails to be deployed as there is missing {{xts}} dependency in the deployment.
The Arquillian test passes as there is such dependency added by Shrinkwrap in the test, see
https://github.com/jbossas/eap-quickstarts/blob/7.x/wsat-simple/src/test/...
{{pom.xml}} should configure the war to contain the {{XTS}} dependency.
> Add xts dependency for war created by maven in wsat-simple quickstart
> ---------------------------------------------------------------------
>
> Key: WFLY-8592
> URL: https://issues.jboss.org/browse/WFLY-8592
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Minor
>
> Creating {{war}} package in {{wsat-simple}} quickstart give a user way to check the functionality of the WS-AT on his own. He can take the war and deploy it on two containers and then invoked the servlet at {{http://localhost:8180/WSATSimpleServletClient}}. But currently, the war fails to be deployed as there is missing {{xts}} dependency in the deployment.
> The Arquillian test passes as there is such dependency added by Shrinkwrap in the test, see
> https://github.com/wildfly/quickstart/blob/11.x/wsat-simple/src/test/java...
> {{pom.xml}} should configure the war to contain the {{XTS}} dependency.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ELY-1086) CS tool, Command without any option must show help rather then error message about required options.
by Hynek Švábek (JIRA)
Hynek Švábek created ELY-1086:
---------------------------------
Summary: CS tool, Command without any option must show help rather then error message about required options.
Key: ELY-1086
URL: https://issues.jboss.org/browse/ELY-1086
Project: WildFly Elytron
Issue Type: Bug
Reporter: Hynek Švábek
Assignee: Darran Lofthouse
Command without any option must show help rather then error message about required options.
*How to reproduce:*
{code}
java -jar wildfly-elytron-tool.jar credential-store
Exception encountered executing the command:
org.apache.commons.cli.MissingOptionException: Missing required option: [-a Add new alias to the credential store, -r Remove alias from the credential store, -e Check if alias exists within the credential store, -v Display all aliases, -h Get help with usage of this command]
at org.apache.commons.cli.DefaultParser.checkRequiredOptions(DefaultParser.java:199)
at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:130)
at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:81)
at org.wildfly.security.tool.CredentialStoreCommand.execute(CredentialStoreCommand.java:120)
at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:74)
{code}
*Same for mask command*
{code}
java -jar wildfly-elytron-tool.jar mask
Exception encountered executing the command:
org.apache.commons.cli.MissingOptionException: Missing required option: [-x Secret to be encrypted, -h Get help with usage of this command]
at org.apache.commons.cli.DefaultParser.checkRequiredOptions(DefaultParser.java:199)
at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:130)
at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:81)
at org.wildfly.security.tool.MaskCommand.execute(MaskCommand.java:72)
at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:74)
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (ELY-1086) CS tool, Command without any option must show help rather then error message about required options.
by Hynek Švábek (JIRA)
[ https://issues.jboss.org/browse/ELY-1086?page=com.atlassian.jira.plugin.s... ]
Hynek Švábek updated ELY-1086:
------------------------------
Component/s: Credential Store
> CS tool, Command without any option must show help rather then error message about required options.
> ----------------------------------------------------------------------------------------------------
>
> Key: ELY-1086
> URL: https://issues.jboss.org/browse/ELY-1086
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credential Store
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
>
> Command without any option must show help rather then error message about required options.
> *How to reproduce:*
> {code}
> java -jar wildfly-elytron-tool.jar credential-store
> Exception encountered executing the command:
> org.apache.commons.cli.MissingOptionException: Missing required option: [-a Add new alias to the credential store, -r Remove alias from the credential store, -e Check if alias exists within the credential store, -v Display all aliases, -h Get help with usage of this command]
> at org.apache.commons.cli.DefaultParser.checkRequiredOptions(DefaultParser.java:199)
> at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:130)
> at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:81)
> at org.wildfly.security.tool.CredentialStoreCommand.execute(CredentialStoreCommand.java:120)
> at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:74)
> {code}
> *Same for mask command*
> {code}
> java -jar wildfly-elytron-tool.jar mask
> Exception encountered executing the command:
> org.apache.commons.cli.MissingOptionException: Missing required option: [-x Secret to be encrypted, -h Get help with usage of this command]
> at org.apache.commons.cli.DefaultParser.checkRequiredOptions(DefaultParser.java:199)
> at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:130)
> at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:81)
> at org.wildfly.security.tool.MaskCommand.execute(MaskCommand.java:72)
> at org.wildfly.security.tool.ElytronTool.main(ElytronTool.java:74)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFLY-8592) Add xts dependency for war created by maven in wsat-simple quickstart
by Ondra Chaloupka (JIRA)
Ondra Chaloupka created WFLY-8592:
-------------------------------------
Summary: Add xts dependency for war created by maven in wsat-simple quickstart
Key: WFLY-8592
URL: https://issues.jboss.org/browse/WFLY-8592
Project: WildFly
Issue Type: Bug
Components: Quickstarts
Reporter: Ondra Chaloupka
Assignee: Tomaz Cerar
Priority: Minor
Creating {{war}} package in {{wsat-simple}} quickstart give a user way to check the functionality of the WS-AT on his own. He can take the war and deploy it on two containers and then invoked the servlet at {{http://localhost:8180/WSATSimpleServletClient}}. But currently, the war fails to be deployed as there is missing {{xts}} dependency in the deployment.
The Arquillian test passes as there is such dependency added by Shrinkwrap in the test, see
https://github.com/jbossas/eap-quickstarts/blob/7.x/wsat-simple/src/test/...
{{pom.xml}} should configure the war to contain the {{XTS}} dependency.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years