Monday, 2015-03-23

*** GitHub188 <GitHub188!~GitHub188@192.30.252.41> has joined #immutant00:08
GitHub188[wunderboss] jcrossley3 pushed 1 new commit to master: http://git.io/hQhr00:08
GitHub188wunderboss/master 9ce817f Jim Crossley: More post WF9a1 updates, mostly jgroups related00:08
*** GitHub188 <GitHub188!~GitHub188@192.30.252.41> has left #immutant00:08
jbossbotTitle: More post WF9a1 updates, mostly jgroups related · projectodd/wunderboss@9ce817f · GitHub00:08
projectodd-ciProject wunderboss-incremental build #208: SUCCESS in 10 min: https://projectodd.ci.cloudbees.com/job/wunderboss-incremental/208/00:19
projectodd-ciJim Crossley: More post WF9a1 updates, mostly jgroups related00:19
*** deadghost <deadghost!~deadghost@49.230.125.36> has quit IRC (Ping timeout: 255 seconds)00:35
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant00:48
jbossbotgit [immutant] push thedeuce a1a51a8.. Jim Crossley Pick up fixes for clustering tests on post-WF9a100:58
jbossbotgit [immutant] push thedeuce URL: http://github.com/immutant/immutant/commit/a1a51a85000:58
*** tcrawley-away is now known as tcrawley01:04
*** tcrawley is now known as tcrawley-away01:05
projectodd-ciProject immutant2-incremental build #520: SUCCESS in 13 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/520/01:12
projectodd-ciJim Crossley: Pick up fixes for clustering tests on post-WF9a101:12
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 252 seconds)01:21
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has joined #immutant01:26
jcrossley3tcrawley-away: i think we may have an opportunity/bug in our clustered singleton thingy. we should pair on it tomorrow.01:38
*** marianoguerra <marianoguerra!~marianogu@245-123-17-190.fibertel.com.ar> has joined #immutant02:12
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has joined #immutant02:12
projectodd-ciProject immutant2-incremental-integs build #12: SUCCESS in 1 hr 2 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/12/02:14
projectodd-ciJim Crossley: Pick up fixes for clustering tests on post-WF9a102:14
*** eric_normand <eric_normand!~eric@ip72-211-99-52.no.no.cox.net> has quit IRC (Quit: eric_normand)02:21
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has joined #immutant02:27
*** Jesterman81 <Jesterman81!~adam@174-124-3-72.dyn.centurytel.net> has joined #immutant03:39
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)03:40
*** Jesterman81 <Jesterman81!~adam@174-124-3-72.dyn.centurytel.net> has left #immutant03:41
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has joined #immutant03:46
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)03:57
*** statonjr <statonjr!~statonjr@cpe-174-108-074-226.carolina.res.rr.com> has quit IRC (Quit: statonjr)04:04
*** jcrossley3 is now known as jcrossley3-away04:06
*** eric_normand <eric_normand!~eric@ip72-211-99-52.no.no.cox.net> has joined #immutant04:29
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has quit IRC (Remote host closed the connection)04:31
*** eric_normand <eric_normand!~eric@ip72-211-99-52.no.no.cox.net> has quit IRC (Quit: eric_normand)05:03
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has quit IRC (Quit: leaving)05:40
*** fivebats <fivebats!~fivebats@c-24-20-216-46.hsd1.or.comcast.net> has quit IRC (Remote host closed the connection)05:43
*** fivebats <fivebats!~fivebats@c-24-20-216-46.hsd1.or.comcast.net> has joined #immutant05:43
*** fivebats <fivebats!~fivebats@c-24-20-216-46.hsd1.or.comcast.net> has quit IRC (Client Quit)05:43
*** rboyd <rboyd!uid40503@gateway/web/irccloud.com/x-mkclismqzcbvnflo> has quit IRC (Quit: Connection closed for inactivity)06:17
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant06:28
*** MadcapJake <MadcapJake!~MadcapJak@66-188-235-160.dhcp.eucl.wi.charter.com> has quit IRC (Ping timeout: 244 seconds)06:42
*** mgoldmann|away is now known as mgoldmann06:50
*** MadcapJake <MadcapJake!~MadcapJak@66-188-235-160.dhcp.eucl.wi.charter.com> has joined #immutant07:20
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has joined #immutant07:30
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant07:44
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)08:38
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant08:45
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Remote host closed the connection)08:45
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant08:46
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Client Quit)08:49
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant08:49
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Remote host closed the connection)09:16
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant09:16
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 245 seconds)09:20
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)09:22
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)09:38
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant09:39
*** deadghost <deadghost!~deadghost@49.230.125.36> has joined #immutant09:45
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)09:48
*** dm3 <dm3!~dm3@pub158181119172.dh-hfc.datazug.ch> has joined #immutant09:55
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant09:56
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)10:05
*** deadghost <deadghost!~deadghost@49.230.125.36> has quit IRC (Ping timeout: 265 seconds)10:08
*** qwerty_nor <qwerty_nor!~Thunderbi@5.248.107.224> has joined #immutant10:33
*** deadghost <deadghost!~deadghost@49.230.71.59> has joined #immutant10:36
*** statonjr <statonjr!~statonjr@cpe-174-108-074-226.carolina.res.rr.com> has joined #immutant10:50
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has joined #immutant11:06
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)11:20
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant11:36
*** bobmcw <bobmcw!bobmcw@nat/redhat/x-hrngvnjxngrvocvy> has joined #immutant11:47
*** bobmcw <bobmcw!bobmcw@nat/redhat/x-hrngvnjxngrvocvy> has quit IRC (Changing host)11:47
*** bobmcw <bobmcw!bobmcw@redhat/jboss/bobmcw> has joined #immutant11:47
*** bobmcw <bobmcw!bobmcw@redhat/jboss/bobmcw> has quit IRC (Remote host closed the connection)11:48
*** bobmcw <bobmcw!bobmcw@redhat/jboss/bobmcw> has joined #immutant11:56
*** bobmcw <bobmcw!bobmcw@redhat/jboss/bobmcw> has quit IRC (Read error: Connection reset by peer)11:57
*** bobmcw <bobmcw!bobmcw@nat/redhat/x-ztyapijgarienuvw> has joined #immutant11:57
*** bobmcw <bobmcw!bobmcw@nat/redhat/x-ztyapijgarienuvw> has quit IRC (Changing host)11:57
*** bobmcw <bobmcw!bobmcw@redhat/jboss/bobmcw> has joined #immutant11:57
*** cnb_ <cnb_!~cnb@pc-25-8-74-200.cm.vtr.net> has joined #immutant12:04
*** jcrossley3-away is now known as jcrossley312:09
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has joined #immutant12:12
*** tcrawley-away is now known as tcrawley12:12
* tcrawley loves opportunity bugs!12:15
*** irsol <irsol!~irsol@unaffiliated/contempt> has quit IRC (Remote host closed the connection)12:22
jcrossley3tcrawley: when you get a chance, can you build WF HEAD locally and test the +cluster integs with it?12:22
tcrawleysure!12:22
jcrossley3they take 5-10 minutes to run for me, but i think most of that time is spent by jgroups waiting to timeout12:24
*** irsol <irsol!~irsol@unaffiliated/contempt> has joined #immutant12:31
jcrossley3tcrawley: sometimes it completes in <3 minutes12:36
jcrossley3i'm trying to figure out why12:36
jcrossley3i thought it might have to do with the jgroups "discarded" warnings first discovered back in december by jwm: http://transcripts.jboss.org/channel/irc.freenode.org/%23immutant/2014/%23immutant.2014-12-09.log.html#t2014-12-09T17:12:1912:37
jbossbotTitle: Tuesday, 2014-12-0912:37
jcrossley3that's pretty much the only reference to those warnings on the internet12:37
jcrossley3and the existence of that "ee" channel got into the config post-WF9a112:38
*** bbrowning <bbrowning!~bbrowning@redhat/jboss/bbrowning> has joined #immutant12:41
*** marianoguerra <marianoguerra!~marianogu@245-123-17-190.fibertel.com.ar> has joined #immutant12:44
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has joined #immutant12:44
*** galderz <galderz!~galder@155.157.63.188.dynamic.wline.res.cust.swisscom.ch> has joined #immutant12:48
*** galderz <galderz!~galder@155.157.63.188.dynamic.wline.res.cust.swisscom.ch> has quit IRC (Changing host)12:48
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant12:48
tcrawleyjcrossley3: sorry, my src tree is currently a mess from trying to get stomp working on friday. lemme clean that up and I'll run the tests12:52
jcrossley3kk!12:58
jcrossley3hmmm. i'm unable to replicate what i was consistently seeing last night.13:05
jcrossley3i think the "discarded" messages only occur when a node is going down, which probably makes sense13:06
tcrawleyare you still seeing slowness?13:16
jcrossley3not today :(13:17
jcrossley3well, unless they run a lot faster than 3-4 minutes for you13:17
*** bbrowning is now known as bbrowning_away13:27
tcrawleyjcrossley3: the cluster integs just ran in 2m 58s for me13:33
tcrawleyrunning again13:33
tcrawleythen I'll run against 9a1 to compare13:33
jcrossley3tcrawley: ok, i have a theory13:44
jcrossley3i can get the delay to occur with 8.2, too13:44
jcrossley3but i get a different error message13:44
jcrossley32015-03-23 09:43:54,173 WARN  [org.jgroups.protocols.TP$ProtocolAdapter] (INT-1,shared=udp) JGRP000031: master:server-two/default: dropping unicast message to wrong destination eaaa32b5-4b35-c9d3-c27c-f52b41e6edbe13:44
jcrossley3i believe that's a known WF bug13:45
jcrossley3but i think if i keep running the test, i can get the delay with WF9a2, too13:45
tcrawley9a2s just took 8+ minutes for me13:46
jcrossley3good!13:46
jcrossley3so you're seeing it too!13:46
tcrawleylooks like13:46
jcrossley3I'M NOT INSANE!13:47
tcrawleylet me check the logs13:47
*** deadghost <deadghost!~deadghost@49.230.71.59> has quit IRC (Ping timeout: 244 seconds)13:47
tcrawleywell...13:47
jcrossley3the big sucky thing about this is the resolution of that known bug13:47
jcrossley3"This is no longer an issue as of 9.0.0.Alpha2-SNAPSHOT (future 9.0.0.CR1). There are numerous changes since Alpha1 (FORK, component upgrades, etc) one of which fixed the problem."13:48
jcrossley3WFLY-263213:49
jbossbotjira [WFLY-2632] JGroups drops unicast messages after shutdown/restart (dropping unicast message to wrong destination) [Resolved (Done) Bug, Major, Radoslav Husar] https://issues.jboss.org/browse/WFLY-263213:49
jcrossley3they have nfi what fixed it13:49
tcrawleysweet13:49
jcrossley3so i think the potential for delays is still there, though it manifests differently is all13:50
jcrossley3i wrapped each test in START/FINISH marks:13:51
jcrossley309:42:54,808 START #<cluster_test$publish_here_receive_there integs.cluster_test$publish_here_receive_there@362b6302>13:51
jcrossley309:47:54,841 FINISH13:51
jcrossley313:51
jcrossley3pretty obvious the timeout is exactly 5 minutes13:52
jcrossley3that's with 8.213:52
tcrawleyI wonder if we're not shutting something down properly in singleton?13:54
jcrossley3could be13:54
tcrawleyI wonder if we're grabbing a lock and not releasing it?14:02
jcrossley3could be14:03
jcrossley3i'm consistently timing out waiting for publish-here-receive-there to complete now14:03
jcrossley3i wonder if there's some persistent state somewhere14:04
jcrossley3somewhere *not* in isolated-wildfly14:04
jcrossley3which i'm blowing away each time14:04
tcrawleyjcrossley3: make sure there are no hung WF processes. I've had them hang around before14:04
tcrawleyfrom a prior run, that is14:05
jcrossley3i would think that'd cause other issues14:05
jcrossley3but i'll confirm14:05
tcrawleyI can't recall what issues I had, but recall that they were puzzling and non-intuitive14:05
jbossbotgit [immutant] push thedeuce 89c51b1.. Jim Crossley Debug cluster test hangs14:07
jbossbotgit [immutant] push thedeuce URL: http://github.com/immutant/immutant/commit/89c51b12914:07
*** deadghost <deadghost!~deadghost@49.230.71.59> has joined #immutant14:13
*** Jesterman81 <Jesterman81!~adam@174-124-3-72.dyn.centurytel.net> has joined #immutant14:14
projectodd-ciProject immutant2-incremental build #521: SUCCESS in 13 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/521/14:22
projectodd-ciJim Crossley: Debug cluster test hangs14:22
jcrossley3tcrawley: confirmed jboss processes get cleaned up by the fntest fixtures14:23
jcrossley3and my hang remained over several runs until i ultimately refreshed by jboss-home14:24
*** bbrowning_away is now known as bbrowning14:24
*** Jesterman81 <Jesterman81!~adam@174-124-3-72.dyn.centurytel.net> has left #immutant14:25
tcrawleyweird14:25
jcrossley3trying to isolate the persistent state now14:26
jcrossley3perhaps it's a waste of time to diagnose clustering issues with 8.214:30
tcrawleyyeah, I'd focus on 914:30
jcrossley3tcrawley: are you looking into whether we're not closing something we should?14:31
tcrawleyyes, I'm trying to see if we're either holding a jgroups lock or continuing to try to use jgroups after shutdown is initiated14:32
jcrossley3kk!14:32
tcrawleymarktest is handy, thanks!14:32
jcrossley3coolio14:33
*** deadghost <deadghost!~deadghost@49.230.71.59> has quit IRC (Read error: Connection timed out)14:36
*** deadghost <deadghost!~deadghost@49.230.71.59> has joined #immutant14:37
tcrawleyjcrossley3: is it always the same test that takes the extr 5m? I just did my first run with marktest, and the offending test was publish-here-receive-there14:40
jcrossley3tcrawley: it seems to be that one, yes14:41
jcrossley3though i also occasionally see a failure on line 71, too14:41
jcrossley3that might be racism, though14:41
jcrossley3tcrawley: and that's with 9a2?14:42
tcrawleyyes14:42
jcrossley3i've yet to see the hang with 9a214:43
jcrossley3brb14:43
*** jcrossley3 <jcrossley3!~user@redhat/jboss/jc3> has quit IRC (Quit: ERC Version 5.3 (IRC client for Emacs))14:43
*** jcrossley3 <jcrossley3!~user@redhat/jboss/jc3> has joined #immutant14:44
tcrawleyjcrossley3: do you mean the 5 minute pause, or the full hang you were seeing with receive?14:46
jcrossley3tcrawley: the former. i'm not sure i recall the latter.14:47
jcrossley3i'm just now seeing the 5 minute pause with 9a214:48
tcrawleyah, I meant the timing out issue on pub-here-rcv-there. carry on14:48
jcrossley3with occasional discarded message warnings during the 5 minutes14:48
jcrossley3which i didn't see with 8.2, fwiw14:48
jcrossley3i would see the "wrong destination" warning and then nothing at all for 5 minutes14:49
jcrossley3not sure that's relevant14:49
tcrawleywe're not doing anything with jgroups during that 5m - we're not holding locks or trying to assess singeleton state14:49
jcrossley3well, any mention of ROOT.war is us14:50
jcrossley3something about those two channels is wrong14:50
jcrossley3ee being the other one14:50
jcrossley3none of the versions pre-9a2 have that ee channel configured. that's new.14:50
jcrossley3tcrawley: have you determined whether it's the publish or receive that's hanging?14:52
jcrossley3now i consistently get the hang. maybe it's just me, but i feel like once i start getting it, i get it from then on.14:56
tcrawleynow I don't get it :)14:56
tcrawleyso I don't know if it's pub or rcv that's hanging14:57
tcrawleyadding some more debug and trying again14:57
jcrossley3i wonder if each rcv is timing out after 30s15:03
tcrawleyjcrossley3: I found where it's happening. each rcv takes 30s15:04
jcrossley3that's what i'm seeing15:04
tcrawleyships!15:04
jcrossley3ships!15:04
tcrawleyships!15:04
tcrawleybut is getting a value15:04
jcrossley3yeah15:04
jcrossley3weird15:04
tcrawleyI'm going to lower the timeout for that rcv and see if it still gets a value15:06
jcrossley3is 30s our default timeout?15:07
tcrawleyI thought it was, but it's actually 10s15:07
tcrawleyremember the comment in messaging_test.clj? it's this issue15:08
tcrawley;; This works sometimes, but sometimes a remote receive takes 30s to15:08
tcrawley;; timeout, no matter the :timeout setting. I think we're doing it15:08
tcrawley;; right, and it's an HQ issue, so I'm disabling this test.15:08
tcrawley15:08
jcrossley3huh15:09
jcrossley3is it an HQ issue?15:10
tcrawleynot that I could find15:10
tcrawleybut I couldn't find how we'd be causing it either, so I blamed them15:10
tcrawleyso really I have no idea15:10
jcrossley3natch15:10
jcrossley3it doesn't happen every time15:11
projectodd-ciProject immutant2-incremental-integs build #13: SUCCESS in 50 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/13/15:12
projectodd-ciJim Crossley: Debug cluster test hangs15:12
jcrossley3so maybe the jgroups warnings are harmless15:14
tcrawleyhere's a mention of 30 seconds and hornetq clients: https://docs.jboss.org/hornetq/2.2.5.Final/user-manual/en/html/connection-ttl.html#d0e369915:14
jbossbotTitle: Chapter 17. Detecting Dead Connections15:15
tcrawleybut I'm not sure if it's related15:15
jcrossley3our client isn't dead15:17
jcrossley3nor the server it's connected to15:17
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)15:17
tcrawleyindeed15:17
jcrossley3so... NOTABUG?15:18
*** lanceball is now known as lance|afk15:18
*** lance|afk is now known as lanceball15:18
tcrawleythere's an undocumented connection-factory.call-timeout setting that defaults to 30s15:20
tcrawleyno idea what it does15:21
jcrossley3worth asking in #hornetq?15:21
tcrawleyyeah, maybe so15:21
tcrawleylet me take a look at how we're constructing the ConnectionFactory and Connection15:21
jcrossley3kk!15:21
*** deadghost <deadghost!~deadghost@49.230.71.59> has quit IRC (Ping timeout: 264 seconds)15:35
jcrossley3tcrawley: i think the occasional failure on line 71 is also due to the 30s timeout15:47
jcrossley3or related somehow15:47
jcrossley3need more debug15:47
*** deadghost <deadghost!~deadghost@49.230.71.59> has joined #immutant15:48
*** deadghost <deadghost!~deadghost@49.230.71.59> has quit IRC (Ping timeout: 245 seconds)15:52
jcrossley3we gotta be doing something wrong, else google would be more help15:57
tcrawleyif I jstack the test process, I can see exactly where we're waiting inside the HQ client15:57
jcrossley3and?15:58
tcrawleyI'm going to stop there in the debugger and see what the current state is15:58
jcrossley3coolio15:58
* jcrossley3 scoots to the edge of his seat15:58
*** statonjr <statonjr!~statonjr@cpe-174-108-074-226.carolina.res.rr.com> has quit IRC (Quit: statonjr)15:59
*** deadghost <deadghost!~deadghost@49.230.71.59> has joined #immutant16:05
jcrossley3tcrawley: if :every is the only thing in my schedule spec, the job will be run immediately, correct?16:05
tcrawleyI believe so, yes. the start time should be set to 'now'16:06
jcrossley3kk!16:08
jcrossley3ah, https://gist.github.com/c07b8d8d48b7f56ea91416:08
*** deadghost <deadghost!~deadghost@49.230.71.59> has quit IRC (Ping timeout: 245 seconds)16:09
tcrawleyyeppers16:10
*** deadghost <deadghost!~deadghost@49.230.71.59> has joined #immutant16:23
*** jcrossle_ <jcrossle_!~user@71-90-202-246.dhcp.stls.mo.charter.com> has joined #immutant16:36
*** jcrossley3 <jcrossley3!~user@redhat/jboss/jc3> has quit IRC (Ping timeout: 256 seconds)16:39
*** jcrossle_ is now known as jcrossley316:44
*** Jesterman81 <Jesterman81!~adam@75-121-155-30.dyn.centurytel.net> has joined #immutant16:49
*** bbrowning is now known as bbrowning_away16:51
*** Jesterman81 <Jesterman81!~adam@75-121-155-30.dyn.centurytel.net> has left #immutant16:53
tcrawleyjcrossley3: asking in #hornetq now17:03
jcrossley3i saw, yeah17:03
* jcrossley3 watches you17:03
jcrossley3looks like you may have found a bug17:05
tcrawleyyeah17:05
tcrawleywell, I've started that conversation. I'm going to move on to other things and wait to see if we get a response17:07
tcrawleyif not, I'll file a bug17:07
jcrossley3cool17:07
*** cap10morgan <cap10morgan!~cap10morg@c-50-134-198-253.hsd1.co.comcast.net> has joined #immutant17:07
jcrossley3i think i found my racism17:07
tcrawleyyay!17:07
jcrossley3easily "solved" with a sleep, of course17:08
jcrossley3tcrawley: you're probably going to have to repost a gist of that when clebert and/or andytaylor are in the channel :(17:09
tcrawleyyeah17:11
jcrossley3tcrawley: i could refactor those tests to use http instead of remote jms, and they'd complete a lot faster.17:27
tcrawleythat sounds good to me17:27
jcrossley3we should still fix it, obviously, but we don't need remote messaging to verify those particular tests. web would work.17:28
tcrawleyyeah, I agree. once I file an issue with HQ, we can track that17:31
tcrawleyI suspect there are two bugs in the client we are seeing - one around MAX_VALUE timeouts, the other around how incoming messages notify() the waiting thread17:31
*** bbrowning_away is now known as bbrowning17:33
jcrossley3interesting17:34
jcrossley3i wonder what they'll break by fixing those ;)17:35
*** statonjr <statonjr!~statonjr@cpe-174-108-074-226.carolina.res.rr.com> has joined #immutant18:06
*** dm3_ <dm3_!~dm3@pub158181119172.dh-hfc.datazug.ch> has joined #immutant18:21
*** GitHub137 <GitHub137!~GitHub137@192.30.252.41> has joined #immutant18:23
GitHub137[lein-immutant] tobias pushed 2 new commits to 2x-dev: http://git.io/hbHi18:23
GitHub137lein-immutant/2x-dev 9052108 Toby Crawley: Honor :main's that are functions [fixes #107]18:23
GitHub137lein-immutant/2x-dev ef4c542 Toby Crawley: Activate the test profiles when running the `immutant test` task [fixes #108]18:23
*** GitHub137 <GitHub137!~GitHub137@192.30.252.41> has left #immutant18:23
jbossbotTitle: Comparing bb736baeeab6...ef4c5422c19e · immutant/lein-immutant · GitHub18:23
*** dm3 <dm3!~dm3@pub158181119172.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 250 seconds)18:24
*** dm3_ <dm3_!~dm3@pub158181119172.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 272 seconds)18:26
*** _kardan <_kardan!~daniel_ka@c-31-209-39-157.cust.bredband2.com> has joined #immutant18:42
*** jcrossle_ <jcrossle_!~user@71-90-202-246.dhcp.stls.mo.charter.com> has joined #immutant18:47
*** jcrossle_ is now known as jcrossley3-away18:48
*** jcrossley3 <jcrossley3!~user@71-90-202-246.dhcp.stls.mo.charter.com> has quit IRC (Ping timeout: 250 seconds)18:51
*** egli <egli!~user@alouette.sbs.ch> has quit IRC (*.net *.split)19:04
*** kungi <kungi!kungi@hell.kungi.org> has quit IRC (*.net *.split)19:04
*** mgoldmann <mgoldmann!~mgoldmann@redhat/jboss/mgoldmann> has quit IRC (*.net *.split)19:04
*** mgoldmann <mgoldmann!~mgoldmann@redhat/jboss/mgoldmann> has joined #immutant19:04
*** egli <egli!~user@alouette.sbs.ch> has joined #immutant19:04
*** kungi <kungi!kungi@hell.kungi.org> has joined #immutant19:04
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant19:05
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: Leaving)19:14
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 256 seconds)19:33
*** lanceball is now known as lance|afk19:35
*** lance|afk is now known as lanceball19:57
*** jcrossley3-away is now known as jcrossley320:01
tcrawleyjcrossley3: https://gist.github.com/e7063731d32809b9829220:02
jcrossley3i saw that, yeah20:03
jcrossley3i say fuck a java repro20:03
jcrossley3all they need is lein and git and JBOSS_HOME. turn up the trace, and go to town.20:04
tcrawleyah, I thought you were gone, but I see jcrossle_ was there20:04
jcrossley3the reason i say that is because so many of their issues are closed with a comment saying "we need a repro".20:05
tcrawleysweet20:05
jcrossley3if your bar is that high, then you shouldn't care what lang the repro is written in20:05
jcrossley3especially when they can easily attach some debugger to that jboss process20:06
tcrawleytrue20:06
jcrossley3they can easily see our stack20:06
jcrossley3and what parts are there'n20:06
jcrossley3their'n?20:06
tcrawleyhey, so I STOMP working. the two issues are:20:07
tcrawleywell three:20:07
jcrossley3yeah, fuck verbs20:07
tcrawleywell, four:20:07
tcrawleys/I S/I got S/20:08
tcrawleybetter?20:08
jcrossley3:)20:08
jcrossley3i'm just pissed cuz my pants stink20:08
tcrawleybecause you pissed?20:08
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has joined #immutant20:08
tcrawley1) you have to provide an xml file to enable STOMP (this is embedded)20:08
jcrossley3i swear something about this material just reeks of bo after a leisurely stroll20:08
tcrawley2) your app needs to bring in the hornetq-stomp jar20:09
jcrossley3wait, my daughter might've farted20:09
tcrawley3) you have to set your listener to :decode? false, and manually extract the body of the underlying jms message20:10
tcrawley4) you need a :text codec to respond, since :none creates an ObjectMessage, which stomp doesn't know how to send down the wire20:10
jcrossley3all i heard was "you have to provide an xml file blah, blah, blah"20:10
tcrawley1) you have to configure HornetQ to enable STOMP (this is embedded)20:11
tcrawleybetter?20:11
jcrossley3i guess. i can't tell whether this is too high a price to pay for STOMP, cuz i wouldn't use STOMP20:12
tcrawleysay you had a python app you wanted to connect to HQ. how would you do that?20:12
jcrossley3websocket?20:13
jcrossley3web?20:13
tcrawleyso you'd roll your own messaging?20:13
jcrossley3i'm not all that smart20:13
jcrossley3four instructions might justify some sort of immutant-stomp lib20:13
tcrawleyyeah, that's my plan20:14
tcrawleystep 4 makes me want to bring a :text encoding back in immutant-core :)20:14
jcrossley3we don't have one?20:14
jcrossley3isn't it just a string?20:14
tcrawleyno, we dropped it for :none20:15
tcrawleywhich is an ObjectMessage underneath instead of a TextMessage20:15
jcrossley3i don't care if you bring it back if it clarifies your code20:15
tcrawleyright now, I'm registering one inside the stomp test app20:16
jcrossley3tcrawley: do we have an IMMUTANT issue tracking the 30s remote receive bug?20:27
tcrawleyno, not yet. at least I don't think we do20:27
tcrawleyI'll look20:27
jcrossley3no20:27
jcrossley3i'll do it20:27
jcrossley3i thought you may have created one20:28
tcrawleythanks!20:28
jcrossley3IMMUTANT-54220:34
jbossbotjira [IMMUTANT-542] Remote receive calls can sometimes take 30 seconds to complete [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-54220:34
tcrawleydonkey20:36
*** bobmcw <bobmcw!bobmcw@redhat/jboss/bobmcw> has quit IRC (Remote host closed the connection)20:39
jcrossley3tcrawley: kinda sucks to not be able to call web/run from a daemon20:57
tcrawleyyeah21:05
*** bbrowning is now known as bbrowning_away21:05
*** mgoldmann is now known as mgoldmann|away21:10
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has quit IRC (Ping timeout: 252 seconds)21:14
jbossbotgit [immutant] push thedeuce f2a3c4e.. Jim Crossley Some debug21:21
jbossbotgit [immutant] push thedeuce d537ce1.. Jim Crossley Embrace the HQ 30s-receive bug & avoid singleton racism21:21
jbossbotgit [immutant] push thedeuce f7c5201.. Jim Crossley A little faster failover test to mitigate IMMUTANT-542...21:21
jbossbotgit [immutant] push thedeuce URL: http://github.com/immutant/immutant/compare/89c51b1...f7c520121:21
jbossbotjira [IMMUTANT-542] Remote receive calls can sometimes take 30 seconds to complete [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-54221:21
*** lanceball is now known as lance|afk21:23
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Remote host closed the connection)21:33
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant21:34
projectodd-ciProject immutant2-incremental build #522: SUCCESS in 13 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/522/21:35
projectodd-ci* Jim Crossley: Some debug21:35
projectodd-ci* Jim Crossley: Embrace the HQ 30s-receive bug & avoid singleton racism21:35
projectodd-ci* Jim Crossley: A little faster failover test to mitigate IMMUTANT-54221:35
jbossbotjira [IMMUTANT-542] Remote receive calls can sometimes take 30 seconds to complete [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-54221:35
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 256 seconds)21:38
*** qwerty_nor <qwerty_nor!~Thunderbi@5.248.107.224> has quit IRC (Ping timeout: 250 seconds)21:43
*** _kardan <_kardan!~daniel_ka@c-31-209-39-157.cust.bredband2.com> has quit IRC (Quit: Computer has gone to sleep.)21:44
*** tcrawley is now known as tcrawley-away21:49
projectodd-ciProject immutant2-incremental-integs build #14: SUCCESS in 53 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/14/22:29
projectodd-ci* Jim Crossley: Some debug22:29
projectodd-ci* Jim Crossley: Embrace the HQ 30s-receive bug & avoid singleton racism22:29
projectodd-ci* Jim Crossley: A little faster failover test to mitigate IMMUTANT-54222:29
jbossbotjira [IMMUTANT-542] Remote receive calls can sometimes take 30 seconds to complete [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-54222:29
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant22:33
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)22:42
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 245 seconds)22:51
*** Guest9000 <Guest9000!~textual@97-97-226-79.res.bhn.net> has joined #immutant23:15
*** jcrossley3 is now known as jcrossley3-away23:38
*** marianoguerra <marianoguerra!~marianogu@245-123-17-190.fibertel.com.ar> has joined #immutant23:45
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has joined #immutant23:45

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!