[JBoss JIRA] (WFLY-5048) CLI escapes anpersand in double-quoted strings
by Roman Syroeshko (JIRA)
[ https://issues.jboss.org/browse/WFLY-5048?page=com.atlassian.jira.plugin.... ]
Roman Syroeshko updated WFLY-5048:
----------------------------------
Description:
I use Qpid JCA to work with AMQP message broker via JMS API. Qpid JCA is configured through Jboss CLI. Queues in Qpid are addressed using [Binding URL|https://qpid.apache.org/releases/qpid-0.32/jms-client-0-8/book/JMS-Cl...]. The format uses ampersands to separate additional options.
For example,
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
But when I run cli-command like that:
{code}
./admin-objects=AnotherQueue:add(class-name=org.apache.qpid.ra.admin.QpidQueueImpl,jndi-name=java:/comp/env/jms/AnotherQueue)
./admin-objects=AnotherQueue/config-properties=DestinationAddress:add(value="BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'")
{code}
I get
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
instead of
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
It seemed to me that CLI shouldn't escape double-quoted values. Am I missing something?
Thanks.
was:
I use Qpid JCA to work with AMQP message broker via JMS API. Qpid JCA is configured through Jboss CLI. Queues in Qpid are addressed using [Binding URL|https://qpid.apache.org/releases/qpid-0.32/jms-client-0-8/book/JMS-Cl...]. The format uses ampersands to separate additional options.
For example,
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
But when I run cli-command like that:
{code}
./admin-objects=AnotherQueue:add(class-name=org.apache.qpid.ra.admin.QpidQueueImpl,jndi-name=java:/comp/env/jms/AnotherQueue)
./admin-objects=AnotherQueue/config-properties=DestinationAddress:add(value="BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'")
{code}
I get
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
instead of
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
It seemed to me that CLI shouldn't escape double-quoted values. Am I missing something?
Thanks.
> CLI escapes anpersand in double-quoted strings
> ----------------------------------------------
>
> Key: WFLY-5048
> URL: https://issues.jboss.org/browse/WFLY-5048
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 8.2.0.Final
> Environment: Windows 8.1 x64, WildFly 8.2.0, JDK 1.8.0.45.
> Reporter: Roman Syroeshko
> Assignee: Alexey Loubyansky
> Priority: Blocker
> Labels: escaping
>
> I use Qpid JCA to work with AMQP message broker via JMS API. Qpid JCA is configured through Jboss CLI. Queues in Qpid are addressed using [Binding URL|https://qpid.apache.org/releases/qpid-0.32/jms-client-0-8/book/JMS-Cl...]. The format uses ampersands to separate additional options.
> For example,
> BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
> But when I run cli-command like that:
> {code}
> ./admin-objects=AnotherQueue:add(class-name=org.apache.qpid.ra.admin.QpidQueueImpl,jndi-name=java:/comp/env/jms/AnotherQueue)
> ./admin-objects=AnotherQueue/config-properties=DestinationAddress:add(value="BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'")
> {code}
> I get
> {code:xml}
> <admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
> <config-property name="DestinationAddress">
> BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
> </config-property>
> </admin-object>
> {code}
> instead of
> {code:xml}
> <admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
> <config-property name="DestinationAddress">
> BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
> </config-property>
> </admin-object>
> {code}
> It seemed to me that CLI shouldn't escape double-quoted values. Am I missing something?
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFLY-5048) CLI escapes anpersand in double-quoted strings
by Roman Syroeshko (JIRA)
[ https://issues.jboss.org/browse/WFLY-5048?page=com.atlassian.jira.plugin.... ]
Roman Syroeshko updated WFLY-5048:
----------------------------------
Description:
I use Qpid JCA to work with AMQP message broker via JMS API. Qpid JCA is configured through Jboss CLI. Queues in Qpid are addressed using [Binding URL|https://qpid.apache.org/releases/qpid-0.32/jms-client-0-8/book/JMS-Cl...]. The format uses ampersands to separate additional options.
For example,
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
But when I run cli-command like that:
{code}
./admin-objects=AnotherQueue:add(class-name=org.apache.qpid.ra.admin.QpidQueueImpl,jndi-name=java:/comp/env/jms/AnotherQueue)
./admin-objects=AnotherQueue/config-properties=DestinationAddress:add(value="BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'")
{code}
I get
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
instead of
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
It seemed to me that CLI shouldn't escape double-quoted values. Am I missing something?
Thanks.
was:
I use Qpid JCA to work with AMQP message broker via JMS API. Qpid JCA is configured through Jboss CLI. Queues in Qpid are addressed using [Binding URL|https://qpid.apache.org/releases/qpid-0.32/jms-client-0-8/book/JMS-Cl...]. The format uses ampersands to separate additional options.
For example,
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
But when I run cli-command like that:
{code}
./admin-objects=AnotherQueue:add(class-name=org.apache.qpid.ra.admin.QpidQueueImpl,jndi-name=java:/comp/env/jms/AnotherQueue)
./admin-objects=AnotherQueue/config-properties=DestinationAddress:add(value="BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'")
{code}
I get
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
instead of
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
It seemed to me that CLI shouldn't escape double-quoted values. Am I missing something?
Thanks.
> CLI escapes anpersand in double-quoted strings
> ----------------------------------------------
>
> Key: WFLY-5048
> URL: https://issues.jboss.org/browse/WFLY-5048
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 8.2.0.Final
> Environment: Windows 8.1 x64, WildFly 8.2.0, JDK 1.8.0.45.
> Reporter: Roman Syroeshko
> Assignee: Alexey Loubyansky
> Priority: Blocker
> Labels: escaping
>
> I use Qpid JCA to work with AMQP message broker via JMS API. Qpid JCA is configured through Jboss CLI. Queues in Qpid are addressed using [Binding URL|https://qpid.apache.org/releases/qpid-0.32/jms-client-0-8/book/JMS-Cl...]. The format uses ampersands to separate additional options.
> For example,
> BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
> But when I run cli-command like that:
> {code}
> ./admin-objects=AnotherQueue:add(class-name=org.apache.qpid.ra.admin.QpidQueueImpl,jndi-name=java:/comp/env/jms/AnotherQueue)
> ./admin-objects=AnotherQueue/config-properties=DestinationAddress:add(value="BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'")
> {code}
> I get
> {code:xml}
> <admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
> <config-property name="DestinationAddress">
> BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
> </config-property>
> </admin-object>
> {code}
> instead of
> {code:xml}
> <admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
> <config-property name="DestinationAddress">
> BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
> </config-property>
> </admin-object>
> {code}
> It seemed to me that CLI shouldn't escape double-quoted values. Am I missing something?
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFLY-5048) CLI escapes anpersand in double-quoted strings
by Roman Syroeshko (JIRA)
[ https://issues.jboss.org/browse/WFLY-5048?page=com.atlassian.jira.plugin.... ]
Roman Syroeshko updated WFLY-5048:
----------------------------------
Description:
I use Qpid JCA to work with AMQP message broker via JMS API. Qpid JCA is configured through Jboss CLI. Queues in Qpid are addressed using [Binding URL|https://qpid.apache.org/releases/qpid-0.32/jms-client-0-8/book/JMS-Cl...]. The format uses ampersands to separate additional options.
For example,
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
But when I run cli-command like that:
{code}
./admin-objects=AnotherQueue:add(class-name=org.apache.qpid.ra.admin.QpidQueueImpl,jndi-name=java:/comp/env/jms/AnotherQueue)
./admin-objects=AnotherQueue/config-properties=DestinationAddress:add(value="BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'")
{code}
I get
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
instead of
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
It seemed to me that CLI shouldn't escape double-quoted values. Am I missing something?
Thanks.
was:
I use Qpid JCA to work with AMQP message broker via JMS API. Qpid JCA is configured through Jboss CLI. Queues in Qpid are addressed using [Binding URL|https://qpid.apache.org/releases/qpid-0.32/jms-client-0-8/book/JMS-Cl...]. The format uses ampersands to separate additional options.
For example,
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
But when I run cli-command like that:
{code}
./admin-objects=AnotherQueue:add(class-name=org.apache.qpid.ra.admin.QpidQueueImpl,jndi-name=java:/comp/env/jms/AnotherQueue)
./admin-objects=AnotherQueue/config-properties=DestinationAddress:add(value="BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'")
{code}
I get
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
instead of
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
It seemed to me that CLI shouldn't escape double-quoted values. Am I missing something?
Thanks.
> CLI escapes anpersand in double-quoted strings
> ----------------------------------------------
>
> Key: WFLY-5048
> URL: https://issues.jboss.org/browse/WFLY-5048
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 8.2.0.Final
> Environment: Windows 8.1 x64, WildFly 8.2.0, JDK 1.8.0.45.
> Reporter: Roman Syroeshko
> Assignee: Alexey Loubyansky
> Priority: Blocker
> Labels: escaping
>
> I use Qpid JCA to work with AMQP message broker via JMS API. Qpid JCA is configured through Jboss CLI. Queues in Qpid are addressed using [Binding URL|https://qpid.apache.org/releases/qpid-0.32/jms-client-0-8/book/JMS-Cl...]. The format uses ampersands to separate additional options.
> For example,
> BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
> But when I run cli-command like that:
> {code}
> ./admin-objects=AnotherQueue:add(class-name=org.apache.qpid.ra.admin.QpidQueueImpl,jndi-name=java:/comp/env/jms/AnotherQueue)
> ./admin-objects=AnotherQueue/config-properties=DestinationAddress:add(value="BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'")
> {code}
> I get
> {code:xml}
> <admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
> <config-property name="DestinationAddress">
> BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
> </config-property>
> </admin-object>
> {code}
> instead of
> {code:xml}
> <admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
> <config-property name="DestinationAddress">
> BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
> </config-property>
> </admin-object>
> {code}
> It seemed to me that CLI shouldn't escape double-quoted values. Am I missing something?
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFLY-5048) CLI escapes anpersand in double-quoted strings
by Roman Syroeshko (JIRA)
Roman Syroeshko created WFLY-5048:
-------------------------------------
Summary: CLI escapes anpersand in double-quoted strings
Key: WFLY-5048
URL: https://issues.jboss.org/browse/WFLY-5048
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: 8.2.0.Final
Environment: Windows 8.1 x64, WildFly 8.2.0, JDK 1.8.0.45.
Reporter: Roman Syroeshko
Assignee: Alexey Loubyansky
Priority: Blocker
I use Qpid JCA to work with AMQP message broker via JMS API. Qpid JCA is configured through Jboss CLI. Queues in Qpid are addressed using [Binding URL|https://qpid.apache.org/releases/qpid-0.32/jms-client-0-8/book/JMS-Cl...]. The format uses ampersands to separate additional options.
For example,
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
But when I run cli-command like that:
{code}
./admin-objects=AnotherQueue:add(class-name=org.apache.qpid.ra.admin.QpidQueueImpl,jndi-name=java:/comp/env/jms/AnotherQueue)
./admin-objects=AnotherQueue/config-properties=DestinationAddress:add(value="BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'")
{code}
I get
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
instead of
{code:xml}
<admin-object class-name="org.apache.qpid.ra.admin.QpidQueueImpl" jndi-name="java:/comp/env/jms/AnotherQueue" pool-name="AnotherQueue">
<config-property name="DestinationAddress">
BURL:direct://AnotherExchange//AnotherQueue?routingkey='AnotherQueue'&durable='true'&autodelete='false'&exchangedurable='true'&exchangeautodelete='false'
</config-property>
</admin-object>
{code}
It seemed to me that CLI shouldn't escape double-quoted values. Am I missing something?
Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JGRP-1944) jgroups does not recover properly when using UDP after ifdown / ifup
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1944?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1944:
--------------------------------
I tried this on 2 VirtualBox instances running Fedora 14 (ifconfig eth2 down - up), and it worked.
I'll now look at your VirtualBox image...
> jgroups does not recover properly when using UDP after ifdown / ifup
> --------------------------------------------------------------------
>
> Key: JGRP-1944
> URL: https://issues.jboss.org/browse/JGRP-1944
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.4
> Environment: Linux Ubutun 14.04 where the network cards are configured as bridges:
> auto bridge0
> iface bridge0 inet dhcp
> bridge_ports eth1
> bridge_stp off
> bridge_fd 0
> Reporter: Bram Klein Gunnewiek
> Assignee: Bela Ban
> Fix For: 3.6.5
>
> Attachments: AutoRecoverMulticast.java
>
>
> When we bring the interface down and back up in a complete (udp.xml) configuration everything *seems* to be fine, however multicast traffic from the node that had the interface brought down is not received by other nodes. The node also doesn't receive any data from the other nodes. No exceptions are logged. I don't think the previous test was done correctly by me ... sorry .
> When we use TCP + MPING we see the stacktraces we had previously with UDP:
> 12:13:51.624 50644 [Timer-3,debug,shockvm-tn3-42192] ERROR unknown.jul.logger - failed sending discovery request
> java.io.IOException: Invalid argument
> at java.net.PlainDatagramSocketImpl.send(Native Method) ~[na:1.7.0_79]
> at java.net.DatagramSocket.send(DatagramSocket.java:697) ~[na:1.7.0_79]
> at org.jgroups.protocols.MPING.sendMcastDiscoveryRequest(MPING.java:295) ~[jar:rsrc:jgroups-3.6.4.Final.jar!/:na]
> at org.jgroups.protocols.PING.sendDiscoveryRequest(PING.java:61) [jar:rsrc:jgroups-3.6.4.Final.jar!/:na]
> at org.jgroups.protocols.PING.findMembers(PING.java:31) [jar:rsrc:jgroups-3.6.4.Final.jar!/:na]
> at org.jgroups.protocols.Discovery.findMembers(Discovery.java:244) [jar:rsrc:jgroups-3.6.4.Final.jar!/:na]
> at org.jgroups.protocols.Discovery.down(Discovery.java:387) [jar:rsrc:jgroups-3.6.4.Final.jar!/:na]
> at org.jgroups.protocols.MERGE3$InfoSender.run(MERGE3.java:382) [jar:rsrc:jgroups-3.6.4.Final.jar!/:na]
> at org.jgroups.util.TimeScheduler3$Task.run(TimeScheduler3.java:287) [jar:rsrc:jgroups-3.6.4.Final.jar!/:na]
> at org.jgroups.util.TimeScheduler3$RecurringTask.run(TimeScheduler3.java:321) [jar:rsrc:jgroups-3.6.4.Final.jar!/:na]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_79]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_79]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79]
> (The exact message differs whether or not the -Djava.net.preferIPv4Stack=true argument is configured)
> A configuration that uses MPING also doesn't recover from ifdown/ifup.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JGRP-1939) UDP Max Bundling size setting is treated as max allowable packet size
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1939?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-1939.
----------------------------
Resolution: Done
> UDP Max Bundling size setting is treated as max allowable packet size
> ---------------------------------------------------------------------
>
> Key: JGRP-1939
> URL: https://issues.jboss.org/browse/JGRP-1939
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.5
> Reporter: Jim Thomas
> Assignee: Bela Ban
> Fix For: 3.6.5
>
>
> When the maximum bundle size is exceeded by a non-bundled message an error is generated and the message is not set. When bundling is configured to small sizes this is very problematic because it is impossible to avoid without serious performance consequences.
> JGRP000029: node1: failed sending message to node2 (1413 bytes): java.lang.Exception: message size (1413) is greater than max bundling size (1400). Set the fragmentation/bundle size in FRAG/FRAG2 and TP correctly, headers: FRAG: [id=999, frag_id=1, num_frags=3], UDP: [cluster_name=MainCluster]
> Recommendation: Let bundling size limit be just that -- the maximum size that bundles will be built to. If a maximum UDP packet size restriction is desired then add that as a separate option. However I don't recommend this because this error is pretty much fatal if the wrong kind of message is exceeding the limit. Once the packet has made it past the frag protocols it is going to be the size it wants to be. Refusing to put it on the network only has bad outcomes because there is no recovery.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (WFCORE-861) Wrong installation date in product info report
by Marek Kopecký (JIRA)
[ https://issues.jboss.org/browse/WFCORE-861?page=com.atlassian.jira.plugin... ]
Marek Kopecký updated WFCORE-861:
---------------------------------
Description:
*Description of problem:*
Product info report shows wrong installation date in wildfly. Reported installation date is date of wildfly building.
*How reproducible:*
Always on EAP from zip installation
*Steps to Reproduce:*
# get fresh wildfly from git
# build wildfly
# ./standalone.sh
# ./jboss-cli.sh -c
# :product-info
*Actual results:*
installation-date is a date of wildfly building
*Expected results:*
If Product Install Date is not available, wildfly do not report it.
*Additional info:*
Installation date is reported correctly, when installer is used.
was:
*Description of problem:*
Product info report shows wrong installation date in EAP from zip installation. Reported installation date is date of EAP building.
*How reproducible:*
Always on EAP from zip installation
*Steps to Reproduce:*
# get fresh EAP from zip
# ./standalone.sh
# ./jboss-cli.sh -c
# :product-info
*Actual results:*
installation-date is a date of EAP building
*Expected results:*
If Product Install Date is not available in zip installation, EAP do not report it.
*Additional info:*
Installation date is reported correctly, when installer is used.
> Wrong installation date in product info report
> ----------------------------------------------
>
> Key: WFCORE-861
> URL: https://issues.jboss.org/browse/WFCORE-861
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.0.0.Alpha11
> Reporter: Marek Kopecký
> Assignee: ehsavoie Hugonnet
>
> *Description of problem:*
> Product info report shows wrong installation date in wildfly. Reported installation date is date of wildfly building.
> *How reproducible:*
> Always on EAP from zip installation
> *Steps to Reproduce:*
> # get fresh wildfly from git
> # build wildfly
> # ./standalone.sh
> # ./jboss-cli.sh -c
> # :product-info
> *Actual results:*
> installation-date is a date of wildfly building
> *Expected results:*
> If Product Install Date is not available, wildfly do not report it.
> *Additional info:*
> Installation date is reported correctly, when installer is used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JGRP-1939) UDP Max Bundling size setting is treated as max allowable packet size
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1939?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1939:
--------------------------------
Makes sense, fixed this in 3.6.5. Running the test suite now.
> UDP Max Bundling size setting is treated as max allowable packet size
> ---------------------------------------------------------------------
>
> Key: JGRP-1939
> URL: https://issues.jboss.org/browse/JGRP-1939
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.5
> Reporter: Jim Thomas
> Assignee: Bela Ban
> Fix For: 3.6.5
>
>
> When the maximum bundle size is exceeded by a non-bundled message an error is generated and the message is not set. When bundling is configured to small sizes this is very problematic because it is impossible to avoid without serious performance consequences.
> JGRP000029: node1: failed sending message to node2 (1413 bytes): java.lang.Exception: message size (1413) is greater than max bundling size (1400). Set the fragmentation/bundle size in FRAG/FRAG2 and TP correctly, headers: FRAG: [id=999, frag_id=1, num_frags=3], UDP: [cluster_name=MainCluster]
> Recommendation: Let bundling size limit be just that -- the maximum size that bundles will be built to. If a maximum UDP packet size restriction is desired then add that as a separate option. However I don't recommend this because this error is pretty much fatal if the wrong kind of message is exceeding the limit. Once the packet has made it past the frag protocols it is going to be the size it wants to be. Refusing to put it on the network only has bad outcomes because there is no recovery.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months