[JBoss JIRA] (JGRP-1880) UDP.ip_ttl is ignored and is always 1
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1880?page=com.atlassian.jira.plugin.... ]
Bela Ban edited comment on JGRP-1880 at 11/26/14 6:18 AM:
----------------------------------------------------------
There's a problem on Windows where setting the TTL throws a 'not implemented' exception. This is caused by not using the right stack, forcing IPv4 with {{-Djava.net.preferIPv4Stack=true}} fixes this. Details at https://github.com/belaban/JGroups/wiki/FAQ
was (Author: belaban):
There's a problem on Windows where setting the TTL throws a 'not implemented' exception. This is caused by not using the right stack, forcing IPv4 with {{-Djava.net.preferIPv4Stack=true}} fixes this.
> UDP.ip_ttl is ignored and is always 1
> -------------------------------------
>
> Key: JGRP-1880
> URL: https://issues.jboss.org/browse/JGRP-1880
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5.1, 3.6
>
>
> Since we switched from using a {{MulticastSocket}} for sending of multicast packets to a {{DatagramSocket}}, the time-to-live (TTL) of a packet is always {{1}}. The reason is that method {{setTimeToLive()}} only exists in {{MulticastSocket}}, but not in {{DatagramSocket}}.
> We cannot revert the code and use a {{MulticastSocket}} to send multicasts, as this won't reveal the real IP address of the sender, but only the multicast address, and the real address is needed to drop packets at the _transport level_.
> Investigate whether we could use reflection to get the {{DatagramSocketImpl}} and call {{setTimeToLive()}}.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (JGRP-1880) UDP.ip_ttl is ignored and is always 1
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1880?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1880:
--------------------------------
There's a problem on Windows where setting the TTL throws a 'not implemented' exception. This is caused by not using the right stack, forcing IPv4 with {{-Djava.net.preferIPv4Stack=true}} fixes this.
> UDP.ip_ttl is ignored and is always 1
> -------------------------------------
>
> Key: JGRP-1880
> URL: https://issues.jboss.org/browse/JGRP-1880
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5.1, 3.6
>
>
> Since we switched from using a {{MulticastSocket}} for sending of multicast packets to a {{DatagramSocket}}, the time-to-live (TTL) of a packet is always {{1}}. The reason is that method {{setTimeToLive()}} only exists in {{MulticastSocket}}, but not in {{DatagramSocket}}.
> We cannot revert the code and use a {{MulticastSocket}} to send multicasts, as this won't reveal the real IP address of the sender, but only the multicast address, and the real address is needed to drop packets at the _transport level_.
> Investigate whether we could use reflection to get the {{DatagramSocketImpl}} and call {{setTimeToLive()}}.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (WFCORE-242) the deployment content is deleted if first undeploy and then deploy the same application using CLI batch
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-242?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-242:
------------------------------------------------
Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 1162444|https://bugzilla.redhat.com/show_bug.cgi?id=1162444] from POST to ASSIGNED
> the deployment content is deleted if first undeploy and then deploy the same application using CLI batch
> --------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-242
> URL: https://issues.jboss.org/browse/WFCORE-242
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management
> Reporter: Jay Kumar SenSharma
> Assignee: Emmanuel Hugonnet
> Priority: Minor
>
> - If deploy and undeploy CLI commands executed in a batch mode then it causes missing deployment inside the "data/content" directory which leads to the following error:
> {code}
> [Host Controller] 10:33:42,387 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "example.war")]) - failure description: "WFLYDC0058: No deployment content with hash d85f1e3106bc8a49838a0dccae9e80819c25e02c is available in the deployment content repository for deployment 'example.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart."
> [Host Controller] 10:33:42,390 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (DROOLS-655) Debug: Line after "THEN" ignored
by Marc Dzaebel (JIRA)
[ https://issues.jboss.org/browse/DROOLS-655?page=com.atlassian.jira.plugin... ]
Marc Dzaebel updated DROOLS-655:
--------------------------------
Description:
If "THEN" is directly followed by code, the Eclipse debugger doesn't see the code, e.g. variables are not displayed in the "variables" debug view.
{code}
rule ""
when
then int i=1;
System.out.println( i); // breakpoint set here
end
{code}
Additionally, it's impossible to set breakpoints at the line of "THEN". So the indentation style is forced to always have a new line after THEN. Even smallest rules need to take unnecessary number of lines. However, the above rule works.
was:
If "THEN" is directly followed by code, the Eclipse debugger doesn't see the code, e.g. variables are not displayed in the "variables" debug view.
{code}
rule ""
when
then int i=1;
System.out.println( i); // breakpoint set here
end
{code}
Additionally, it's impossible to set breakpoints at the line of "THEN". So the indentation style is forced to always have a line for then. Even smallest rules need to take unnecessary number of lines. However, the above rule works.
> Debug: Line after "THEN" ignored
> --------------------------------
>
> Key: DROOLS-655
> URL: https://issues.jboss.org/browse/DROOLS-655
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.2.0.CR2
> Environment: All (Eclipse Debug)
> Reporter: Marc Dzaebel
> Assignee: Mark Proctor
> Priority: Minor
>
> If "THEN" is directly followed by code, the Eclipse debugger doesn't see the code, e.g. variables are not displayed in the "variables" debug view.
> {code}
> rule ""
> when
> then int i=1;
> System.out.println( i); // breakpoint set here
> end
> {code}
> Additionally, it's impossible to set breakpoints at the line of "THEN". So the indentation style is forced to always have a new line after THEN. Even smallest rules need to take unnecessary number of lines. However, the above rule works.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month