fmonclar | 10 Sep 19:59 2015
Picon

[jgroups-users] Activate logs on GossipRouter

Hi, 

I'm running GossiRouter like that :

java.exe -Dlog4j.configurationFile=log4j2.xml
-Djava.net.preferIPv4Stack=true 
 -cp lib/jgroups-3.6.3.Final.jar:lib org.jgroups.stack.GossipRouter -port
12001 -bind_addr CANOPP01

and my log4j2.xml is very light :
-----------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN" monitorInterval="30">
	<Properties>
		<Property name="user">${sys:user.name}</Property>
		<Property name="filename">router.log</Property>
	</Properties>

	<Appenders>		
		<RollingFile name="RollingFile" fileName="logs/${user}/${filename}"
filePattern="logs/${user}/${filename}-%d{yyyy-MM-dd}-%i.log" bufferedIO="
true " immediateFlush="true">			
			<PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level [%logger{36}][%M]
%msg%n%throwable"/>
			<Policies>
				<OnStartupTriggeringPolicy />
				<SizeBasedTriggeringPolicy size="20 MB" />
				<TimeBasedTriggeringPolicy />
			</Policies>
			<DefaultRolloverStrategy max="10" />
(Continue reading)

Thomas Cunningham | 10 Sep 19:38 2015
Picon
Gravatar

[jgroups-users] Version 3.2.14.Final

Hi,

I noticed that there's a JGroups-3.2.14.Final tag, and I believe it's been picked up by other projects, but
there does not seem to be a community release in maven for 3.2.14.Final and it is causing some build
problems for me.   Any chance of one the artifact being released?  

Thanks,

Tom

------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
Bela Ban | 9 Sep 18:01 2015
Picon
Gravatar

[jgroups-users] 3.6.6.Final

http://belaban.blogspot.ch/2015/09/jgroups-366final-released.html

--

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)

------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
fmonclar | 9 Sep 16:47 2015
Picon

[jgroups-users] Use of GossiRouter on different sub-networks


Hello,

I have one server "CANOPP01" (10.149.135.6) with :

 - one GossipRouter started like that : jre1.8.0_25-x64\bin\java.exe
-Dlog4j.configurationFile=log4j2.xml -Djava.net.preferIPv4Stack=true -cp
lib/jgroups-3.6.3.Final.jar;lib org.jgroups.stack.GossipRouter -port 12001
-bind_addr CANOPP01

 - one java application (SERVICE_CANOPP01)
2015/09/09 15:33:51.065 [Timer-2,Cluster,SERVICE_CANOPP01] TRACE
org.jgroups.protocols.TCPGOSSIP - Pinging
RouterStub[localsocket=/10.149.135.6:57746,router_host=CANOPP01::12001,connected=true]
2015/09/09 15:33:51.065 [Timer-2,Cluster,SERVICE_CANOPP01] TRACE
org.jgroups.protocols.TCPGOSSIP - Pinged
RouterStub[localsocket=/10.149.135.6:57746,router_host=CANOPP01::12001,connected=true]

 - another one java application (ADMIN_CANOPP01 / 10.149.135.6:7800)
2015/09/09 15:44:01.967 [Timer-3,Cluster,ADMIN_CANOPP01] TRACE
org.jgroups.protocols.TCPGOSSIP - Pinging
RouterStub[localsocket=/10.149.135.6:57877,router_host=CANOPP01::12001,connected=true]
2015/09/09 15:44:01.967 [Timer-3,Cluster,ADMIN_CANOPP01] TRACE
org.jgroups.protocols.TCPGOSSIP - Pinged
RouterStub[localsocket=/10.149.135.6:57877,router_host=CANOPP01::12001,connected=true]

And, in another hand, several PCs which are on another sub network I have
for exemple (but they could be more than 2) :

 - one java application (HCI_PC208594 / 172.18.91.142:7800)
(Continue reading)

Bela Ban | 5 Sep 18:26 2015
Picon
Gravatar

[jgroups-users] Don't use TCP_NIO2 in 3.6.5 just yet

FYI:

Messages sent with a message bundler may get corrupted if TCP_NIO2 is 
used as transport. See [1] for details. I hope to release a fix shortly.

[1] https://issues.jboss.org/browse/JGRP-1961

--

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)

------------------------------------------------------------------------------
Bela Ban | 3 Sep 09:03 2015
Picon
Gravatar

[jgroups-users] JGroups 3.6.5 released

http://belaban.blogspot.ch/2015/09/jgroups-365-released.html

--

-- 
Bela Ban, JGroups lead (http://www.jgroups.org)

------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
pooja | 2 Sep 04:35 2015
Picon

[jgroups-users] Behavior of TCPPING protocol ?

Hi Bela,

I use TCPPING for Discovery, timeout is 6 seconds, Timer.min_threads =1 and socket_connect_timeout=3 seconds.

I set my initial_hosts list intentionally to a list of Ipaddress which I know are online and let the trail be list of offline nodes. 
I assumed that JGroups timer thread will pick up 1st IP and then 2nd and so on. But it is being picked up randomly from the list. Is this expected behavior?

Below is an example:

Following is initial_hosts list on Node 71. Only 70 is alive so I set it first in the list with the assumption that JGroups timer thread will pick that up first to query.

initial_hosts=[70:9802, 27:9802, 26:9802, 5:9802, 172:9802, 58:9802, 45:9802, 12:9802, 13:9802, 6:9802, 52:9802, 19:9802, 20:9802, 46:9802, 71:9802],


But the discovery request picks up second IP in the list. 

2015-09-01T18:24:24.804-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 14:replZ9i3accm2-1217(): sending discovery request to 27:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 15:replZ9i3accm2-1217(): sending discovery request to 26:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 16:replZ9i3accm2-1217(): sending discovery request to 172:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 17:replZ9i3accm2-1217(): sending discovery request to 5:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 18:replZ9i3accm2-1217(): sending discovery request to 70:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 19:replZ9i3accm2-1217(): sending discovery request to 58:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 20:replZ9i3accm2-1217(): sending discovery request to 45:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 21:replZ9i3accm2-1217(): sending discovery request to 12:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 22:replZ9i3accm2-1217(): sending discovery request to 13:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 23:replZ9i3accm2-1217(): sending discovery request to 6:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 24:replZ9i3accm2-1217(): sending discovery request to 52:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 25:replZ9i3accm2-1217(): sending discovery request to 19:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 26:replZ9i3accm2-1217(): sending discovery request to 20:9802
2015-09-01T18:24:24.805-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 27:replZ9i3accm2-1217(): sending discovery request to 46:9802


Thread-79 picks dead Node and stays here till sock_conn_timeout

2015-09-01T18:24:24.808-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[79]: JgroupsLogger 28:replZ9i3accm2-1217(): sending msg to 27:9802, src=replZ9i3accm2-1217(), headers are TCPPING: [PING: type=GET_MBRS_REQ, cluster=cluster_A, arg=replZ9i3accm2-1217(), view_id=, is_server=false, is_coord=false, logical_name=replZ9i3accm2-1217, physical_addrs=71:9802], TCP: [channel_name=cluster_A]
2015-09-01T18:24:24.825-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[79]: JgroupsLogger 30:71:9802: connecting to 27:9802
2015-09-01T18:24:27.834-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[79]: JgroupsLogger 31:71:9802: failed connecting to 27:9802: java.net.SocketTimeoutException: connect timed out

//Same thread-79 picking up next IP in list.
2015-09-01T18:24:27.835-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[79]: JgroupsLogger 32:replZ9i3accm2-1217(): sending msg to 26:9802, src=replZ9i3accm2-1217(), headers are TCPPING: [PING: type=GET_MBRS_REQ, cluster=cluster_A, arg=replZ9i3accm2-1217(), view_id=, is_server=false, is_coord=false, logical_name=replZ9i3accm2-1217, physical_addrs=71:9802], TCP: [channel_name=cluster_A]
2015-09-01T18:24:27.835-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[79]: JgroupsLogger 34:71:9802: connecting to 26:9802
 


It never reaches the online Node and hence ends up being co-ordinator instead of joining Node 70. 

2015-09-01T18:24:30.808-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 35:replZ9i3accm2-1217(): discovery took 6012 ms: responses: 0 total (0 servers (0 coord), 0 clients)
2015-09-01T18:24:30.808-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[25]: JgroupsLogger 36:replZ9i3accm2-1217(): no initial members discovered: creating group as first member
2015-09-01T18:24:30.836-04:00 [user] [debug] replZ9i3accm2.i.com RepDSGrp jgroups[79]: JgroupsLogger 41:71:9802: failed connecting to 26:9802: java.net.SocketTimeoutException: connect timed out
 



Have I understood this behavior correctly ? 


View this message in context: Behavior of TCPPING protocol ?
Sent from the JGroups - General mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
javagroups-users mailing list
javagroups-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/javagroups-users
Mark Bobick, CTO | 28 Aug 17:53 2015

[jgroups-users] jgroups consulting...

Where is the best place to locate/engage expert jgroups consultants with great reputations and proven skills?

 

Regards,

 

-mark bobick            LinkedIn

 

CTO, Correlation Concepts

www.correlationconcepts.com

2880 David Walker Dr. #407

Eustis, Florida  32726

702.882.5664

 

"We will find a way, or we will make one." - Hannibal

 

------------------------------------------------------------------------------
_______________________________________________
javagroups-users mailing list
javagroups-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/javagroups-users
Debajit Adhikary | 26 Aug 04:26 2015

[jgroups-users] How do I avoid storing passwords in JGroups channel XML file?

Hi

I have set up a JGroups cluster using S3_PING.

The XML configuration file contains a line like the following with the actual username and password:

    <S3_PING location="s3-bucket-name" timeout="2000" secret_access_key="ACTUAL_PASSWORD" access_key="ACTUAL_USERNAME" />

I do not want to check in my actual password to source control.

How can I fix this? Does JGroups offer any solution to this problem?

Any pointers are welcome.


Thanks in advance.
—Debajit
------------------------------------------------------------------------------
_______________________________________________
javagroups-users mailing list
javagroups-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/javagroups-users
Debajit Adhikary | 26 Aug 04:24 2015

[jgroups-users] How do I avoid storing passwords in my JGroups channel XML file?

Hi

I have set up a JGroups cluster using S3_PING.

The XML configuration file contains a line like the following with the actual username and password:

    <S3_PING location="s3-bucket-name" timeout="2000" secret_access_key="ACTUAL_PASSWORD" access_key="ACTUAL_USERNAME"/>

I do not want to check in my actual password to source control.

How can I fix this? Does JGroups offer any solution to this problem?

Any pointers are welcome.


Thanks in advance.
—Debajit
------------------------------------------------------------------------------
_______________________________________________
javagroups-users mailing list
javagroups-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/javagroups-users
Tomek | 18 Aug 15:35 2015

[jgroups-users] Retransmit requests to self


Hi experts,
I'm trying to figure out a problem for which I can't find a logical 
cause. Most probably because of my lack of clue as to the inner workings 
of jgroups. It seems like one node is requesting retransmissions for 
messages originating from itself and fails. What can cause such 
behaviour? We're running on Linux and using udp transport over OpenVPN 
with a TAP adapter in case this has anything to do with it.

2015-08-18 15:11:48,911 TRACE  org.jgroups.protocols.pbcast.NAKACK - 
10.8.0.12:17291: sending XMIT_REQ ([0, 37]) to 10.8.0.12:17291
2015-08-18 15:11:48,911 TRACE  org.jgroups.protocols.pbcast.NAKACK - 
10.8.0.12:17291: received xmit request from 10.8.0.12:17291 for 
10.8.0.12:17291 [0 - 37]
2015-08-18 15:11:48,911 ERROR  org.jgroups.protocols.pbcast.NAKACK - 
(requester=10.8.0.12:17291, local_addr=10.8.0.12:17291) message 
10.8.0.12:17291::0 not found in sent msgs.
2015-08-18 15:11:48,911 ERROR  org.jgroups.protocols.pbcast.NAKACK - 
(requester=10.8.0.12:17291, local_addr=10.8.0.12:17291) message 
10.8.0.12:17291::1 not found in sent msgs.
(...)
2015-08-18 15:11:48,912 ERROR  org.jgroups.protocols.pbcast.NAKACK - 
(requester=10.8.0.12:17291, local_addr=10.8.0.12:17291) message 
10.8.0.12:17291::37 not found in sent msgs.

Kind regards,
Tomek

------------------------------------------------------------------------------

Gmane