Thursday, 2015-11-05

*** jcrossley3 is now known as jcrossley3-away00:06
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant01:20
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)01:31
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has joined #immutant01:52
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 240 seconds)01:55
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)02:07
*** bobmcw <bobmcw!~bobmcw@ip-64-134-100-76.public.wayport.net> has joined #immutant02:08
*** bobmcw <bobmcw!~bobmcw@ip-64-134-100-76.public.wayport.net> has quit IRC (Changing host)02:08
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has joined #immutant02:08
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has joined #immutant02:47
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)04:10
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has quit IRC (Remote host closed the connection)05:48
*** dm3 <dm3!~dm3@pub082136109248.dh-hfc.datazug.ch> has joined #immutant06:23
*** rboyd <rboyd!uid40503@gateway/web/irccloud.com/x-taundnpeilhvjpgt> has quit IRC (Quit: Connection closed for inactivity)06:47
*** mgoldmann|away is now known as mgoldmann07:36
*** dm3 <dm3!~dm3@pub082136109248.dh-hfc.datazug.ch> has quit IRC (Remote host closed the connection)09:07
*** dm3 <dm3!~dm3@pub082136109248.dh-hfc.datazug.ch> has joined #immutant09:08
*** dm3 <dm3!~dm3@pub082136109248.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 268 seconds)09:13
*** dm3 <dm3!~dm3@pub082136076233.dh-hfc.datazug.ch> has joined #immutant09:22
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant09:51
*** qwerty_nor <qwerty_nor!~Thunderbi@37.229.49.175> has joined #immutant10:26
*** qwerty_nor <qwerty_nor!~Thunderbi@37.229.49.175> has quit IRC (Read error: Connection reset by peer)10:27
*** qwerty_nor <qwerty_nor!~Thunderbi@37.229.49.175> has joined #immutant10:28
*** bbrowning_away is now known as bbrowning11:17
*** bbrowning is now known as bbrowning_away11:43
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 250 seconds)12:13
*** bbrowning_away <bbrowning_away!~bbrowning@redhat/jboss/bbrowning> has quit IRC (Ping timeout: 250 seconds)12:30
*** bbrowning <bbrowning!~bbrowning@redhat/jboss/bbrowning> has joined #immutant12:39
*** xcv <xcv!~xcv@108.61.68.140> has joined #immutant12:58
*** xcv <xcv!~xcv@108.61.68.140> has quit IRC (Ping timeout: 240 seconds)13:02
*** deadghost <deadghost!~deadghost@122.167.219.181> has joined #immutant13:06
*** tcrawley-away is now known as tcrawley13:21
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant13:24
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 260 seconds)13:29
*** rboyd <rboyd!uid40503@gateway/web/irccloud.com/x-rrffdjlkyplaefla> has joined #immutant13:31
tcrawleyjcrossley3-away: let's chat about the integ failures this morning, I need help debugging those13:33
*** jcrossley3-away is now known as jcrossley313:49
jcrossley3tcrawley: i haven't been paying attn. was attributing them to the normal raciness. something else?13:50
* jcrossley3 looks13:50
tcrawleywe seem to have a lot more failures - the latest with -integs is newish, and might be due to a clustered server not restarting in time, maybe because of the cache lock errors in https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/180/artifact/integration-tests/target/isolated-wildfly/domain/servers/server-two/log/server.log13:52
jcrossley3tcrawley: can you repro locally?13:53
tcrawleyno13:53
tcrawleywait, hmm13:54
* jcrossley3 tries13:54
tcrawleyI may not have ran the clustered tests locally in a while13:54
tcrawleyand I did upgrade us to test against 8.2.1, 9.0.2, 10.0.0.CR4 recently13:54
jcrossley3the errors appear *only* on clustered tests, right?13:54
tcrawleyfor -integs, yes13:54
jcrossley3are there other errors?13:54
tcrawleythere are occasional -integs-eap failures, but that might be the regular ones we see13:55
jcrossley3what did you upgrade from?13:55
tcrawleyah, yeah, the old: CompilerException java.lang.NoSuchMethodError: org.hornetq.core.buffers.impl.ChannelBufferWrapper.<init>(Lorg/jboss/netty/buffer/ChannelBuffer;)V, compiling:(transactions_test.clj:29:11), which is intermittent, oddly13:55
tcrawley8.2.0->8.2.1, 9.0.1->9.0.2, 10.0.0.CR2->CR413:56
jcrossley3are we consistently seeing the error in any particular version?13:56
tcrawleylet me look13:56
tcrawleyno, 177 failed on 8.2.1, 176 made it past 8.2.1, but failed on 9.0.2 with the same error13:59
*** deadghost <deadghost!~deadghost@122.167.219.181> has quit IRC (Ping timeout: 244 seconds)13:59
tcrawleyso that makes me think it's environmental13:59
*** agarman <agarman!~agarman@169.130.108.20> has joined #immutant14:02
jcrossley3tcrawley: i can't get past this locally: "org.jboss.as.server.deployment.DeploymentUnitProcessingException: org.jboss.msc.service.DuplicateServiceException: Service jboss.deployment.unit.\"ROOT.war\".wunderboss is already registered"14:05
jcrossley3that's with 9.0.114:06
tcrawleywhat version? I just ran +cluster with 9.0.214:06
jcrossley3it's worked before14:06
jcrossley3i think14:06
tcrawleyweird. can you gist the full log?14:06
tcrawleywait, do you have leftover deployments in standalone.xml?14:06
tcrawleyor whatever the proper .xml is for domain mode?14:07
jcrossley3https://gist.github.com/a1c2a2828221fb1a5dba14:07
jcrossley3tcrawley: no, virgin install14:07
tcrawleywhat command are you running to run the tests?14:09
jcrossley3lein with-profile +cluster all14:09
tcrawleyit looks like it is reading two ROOT.war's, given the duplicate private module warnings14:10
tcrawleythat's weird14:10
jcrossley3i thought that, but then noticed the .wunderboss extension14:10
jcrossley3tcrawley: might i have the wrong plugin version or something?14:11
tcrawleyhmm, maybe. do you have a plugin set in ~/.lein/profiles.clj?14:12
tcrawleyif so, can you try 2.1.0-SNAPSHOT there?14:12
jcrossley3oh wait!14:12
jcrossley3we depend on fntest 2.0.8-SNAPSHOT now?14:13
jcrossley3that's not good14:13
tcrawleywhy?14:13
jcrossley3that change has your name on it, my friend :)14:13
tcrawleysure, I remember making that change, but why is it bad?14:13
jcrossley3er...14:14
jcrossley3i might have the wrong one locally?14:14
tcrawleywhich would be older than the remote one, so a new one would get pulled14:14
jcrossley3hmm14:14
tcrawleyunless /me forgot to publish14:14
tcrawleybut if I did forget, ci would fail14:15
jcrossley3like it's doing :)14:15
tcrawleyis it failing with your same error?14:15
jcrossley3no14:15
jcrossley3you win14:15
jcrossley3i lose14:15
jcrossley3again14:15
tcrawley:)14:15
tcrawleyI hope to get us off of the snapshots today, and release fntest, deploy-tools, lein-immutant14:16
tcrawleycan you gist the TOC of the jar that fntest builds for the cluster tests?14:16
jcrossley3let's see14:17
jcrossley3tcrawley: https://gist.github.com/79836e648ca8e065f3e314:18
jcrossley3tcrawley: where does that .wunderboss extension come from?14:20
jcrossley3for the service14:20
tcrawleythat's from https://github.com/projectodd/wunderboss/tree/master/wildfly/core/src/main/java/org/projectodd/wunderboss/as/CoreServiceActivator.java#L5014:21
tcrawleyhttps://github.com/projectodd/wunderboss/tree/master/wildfly/core/src/main/java/org/projectodd/wunderboss/as/WunderBossService.java#L3914:21
tcrawleyso it would mean that something is activating CoreServiceActivator twice14:22
tcrawleyI see the duplicated "private module" warnings as well, so I think that's a red herring14:23
jcrossley3hmm14:23
jcrossley3tcrawley: i get a different error when i use 8.2.014:24
tcrawleywhat error?14:24
jcrossley3wait, n/m14:24
jcrossley3i was confusing a weld error14:24
jcrossley3it's the same14:25
jcrossley3let me rebuild everything14:25
tcrawleyImma rm ~/.m2/repository/org/immutant locally and see if I can recreate. maybe I do have a local -SNAPSHOT of something that is newer than what's on clojars14:25
tcrawleyhmm, no, that didn't make a difference14:28
tcrawleywait, I didn't remove lein-immutant14:28
tcrawleybut the cluster tests don't use it, they only use deploy-tools and fntest14:29
tcrawleyyeah, no dif14:30
tcrawleywhat version of java are you using?14:30
* tcrawley is just trying to look for any differences14:30
tcrawleyjcrossley3: ^14:30
jcrossley3java version "1.8.0_60"14:31
jcrossley3tcrawley: rebuild seems to have helped :(14:33
jcrossley38.2.0 worked but i got the same NPE from Numbers.ops that CI did on 9.0.114:39
*** agarman <agarman!~agarman@169.130.108.20> has quit IRC (Read error: Connection reset by peer)14:39
*** agarman <agarman!~agarman@169.130.108.20> has joined #immutant14:40
*** projectodd-ci <projectodd-ci!~PircBotx@ec2-54-235-41-52.compute-1.amazonaws.com> has quit IRC (Ping timeout: 250 seconds)14:43
jcrossley3tcrawley: that stack trace indicates a problem with memoizing the port var in management.clj. maybe that's a bad idea?14:44
tcrawleyhey, success then!14:54
tcrawleyor is the failure pre-memoization? the stack on CI looks like it happens in api.clj14:55
*** projectodd-ci <projectodd-ci!~PircBotx@ec2-54-235-41-52.compute-1.amazonaws.com> has joined #immutant14:58
jcrossley3i dunno, tbh. but i'm not opposed to un-memoizing it if you're publishing snapshots anyway14:59
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has joined #immutant14:59
jcrossley3tcrawley: my next run passed, fwiw15:00
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has quit IRC (Client Quit)15:01
*** xcv <xcv!~xcv@37.120.119.22> has joined #immutant15:02
*** xcv <xcv!~xcv@37.120.119.22> has joined #immutant15:02
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has joined #immutant15:14
*** deadghost <deadghost!~deadghost@122.167.219.181> has joined #immutant15:27
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant15:40
jbossbotgit [immutant] push master 4e1461b.. Toby Crawley Use SNAPSHOT of jboss-as-management with debug output...15:49
jbossbotgit [immutant] push master URL: http://github.com/immutant/immutant/commit/4e1461be115:49
tcrawleyjcrossley3: that uses a jboss-as-management with https://gist.github.com/65fca9298208f5788a1a15:49
jcrossley3kk!15:51
projectodd-ciProject immutant2-incremental build #679: SUCCESS in 5 min 54 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/679/15:55
*** jcrossley3 is now known as jcrossley3-away16:15
*** kbaribeau <kbaribeau!~Adium@207-47-240-132.sktn.hsdb.sasknet.sk.ca> has left #immutant16:24
projectodd-ciYippee, build fixed!16:35
projectodd-ciProject immutant2-incremental-integs-eap build #226: FIXED in 20 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs-eap/226/16:35
projectodd-ciToby Crawley: Use SNAPSHOT of jboss-as-management with debug output16:35
projectodd-ciYippee, build fixed!16:37
projectodd-ciProject immutant2-incremental-integs build #182: FIXED in 41 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/182/16:37
projectodd-ciToby Crawley: Use SNAPSHOT of jboss-as-management with debug output16:37
*** dm3_ <dm3_!~dm3@pub082136076233.dh-hfc.datazug.ch> has joined #immutant16:40
*** dm3 <dm3!~dm3@pub082136076233.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 252 seconds)16:43
tcrawleydammit16:44
tcrawleytriggering another -integs build16:44
*** dm3_ <dm3_!~dm3@pub082136076233.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 255 seconds)16:45
*** lanceball is now known as lance|afk16:47
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 244 seconds)17:13
projectodd-ciProject immutant2-incremental-integs build #183: SUCCESS in 32 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/183/17:17
*** mgoldmann is now known as mgoldmann|away17:28
*** GitHub53 <GitHub53!~GitHub53@192.30.252.40> has joined #immutant17:28
GitHub53[deploy-tools] tobias pushed 1 new commit to master: http://git.io/v8Uxm17:28
GitHub53deploy-tools/master 0107b5e Toby Crawley: Maintain backwards compatibility with prior immutant versions...17:28
*** GitHub53 <GitHub53!~GitHub53@192.30.252.40> has left #immutant17:28
jbossbotTitle: Maintain backwards compatibility with prior immutant versions · immutant/deploy-tools@0107b5e · GitHub17:28
*** travis-ci <travis-ci!~travis-ci@ec2-54-83-102-241.compute-1.amazonaws.com> has joined #immutant17:29
travis-ciimmutant/deploy-tools#59 (master - 0107b5e : Toby Crawley): The build passed.17:29
travis-ciChange view : https://github.com/immutant/deploy-tools/compare/703d2ab06ed4...0107b5efc07117:29
travis-ciBuild details : https://travis-ci.org/immutant/deploy-tools/builds/8948430417:29
*** travis-ci <travis-ci!~travis-ci@ec2-54-83-102-241.compute-1.amazonaws.com> has left #immutant17:29
*** GitHub122 <GitHub122!~GitHub122@192.30.252.40> has joined #immutant17:30
GitHub122[deploy-tools] tobias pushed 2 new commits to master: http://git.io/v8UxD17:30
GitHub122deploy-tools/master 96ad926 Toby Crawley: Version 2.1.017:30
GitHub122deploy-tools/master e466e42 Toby Crawley: Version 2.1.1-SNAPSHOT17:30
*** GitHub122 <GitHub122!~GitHub122@192.30.252.40> has left #immutant17:30
jbossbotTitle: Comparing 0107b5efc071...e466e426c7a7 · immutant/deploy-tools · GitHub17:30
*** GitHub155 <GitHub155!~GitHub155@192.30.252.45> has joined #immutant17:30
GitHub155[deploy-tools] tobias tagged 2.1.0 at 0c8dcff: http://git.io/v8UxQ17:30
*** GitHub155 <GitHub155!~GitHub155@192.30.252.45> has left #immutant17:30
jbossbotTitle: Commits · immutant/deploy-tools · GitHub17:30
*** GitHub44 <GitHub44!~GitHub44@192.30.252.46> has joined #immutant17:31
GitHub44[fntest] tobias pushed 1 new commit to master: http://git.io/v8UpZ17:31
GitHub44fntest/master ebedcaa Toby Crawley: Use non-SNAPSHOT deploy-tools.17:31
*** GitHub44 <GitHub44!~GitHub44@192.30.252.46> has left #immutant17:31
jbossbotTitle: Use non-SNAPSHOT deploy-tools. · immutant/fntest@ebedcaa · GitHub17:31
*** travis-ci <travis-ci!~travis-ci@ec2-54-144-55-225.compute-1.amazonaws.com> has joined #immutant17:31
travis-ciimmutant/deploy-tools#60 (master - e466e42 : Toby Crawley): The build passed.17:31
travis-ciChange view : https://github.com/immutant/deploy-tools/compare/0107b5efc071...e466e426c7a717:31
travis-ciBuild details : https://travis-ci.org/immutant/deploy-tools/builds/8948469617:31
*** travis-ci <travis-ci!~travis-ci@ec2-54-144-55-225.compute-1.amazonaws.com> has left #immutant17:31
*** travis-ci <travis-ci!~travis-ci@ec2-54-92-236-71.compute-1.amazonaws.com> has joined #immutant17:31
travis-ciimmutant/deploy-tools#61 (2.1.0 - 96ad926 : Toby Crawley): The build passed.17:31
travis-ciChange view : https://github.com/immutant/deploy-tools/compare/2.1.017:31
travis-ciBuild details : https://travis-ci.org/immutant/deploy-tools/builds/8948471717:31
*** travis-ci <travis-ci!~travis-ci@ec2-54-92-236-71.compute-1.amazonaws.com> has left #immutant17:31
*** GitHub18 <GitHub18!~GitHub18@192.30.252.46> has joined #immutant17:32
GitHub18[fntest] tobias pushed 2 new commits to master: http://git.io/v8UpM17:32
GitHub18fntest/master 0e5ea5a Toby Crawley: Version 2.0.817:32
GitHub18fntest/master 0f1f9c0 Toby Crawley: Version 2.0.9-SNAPSHOT17:32
*** GitHub18 <GitHub18!~GitHub18@192.30.252.46> has left #immutant17:32
jbossbotTitle: Comparing ebedcaab09a4...0f1f9c0ed40a · immutant/fntest · GitHub17:32
*** GitHub103 <GitHub103!~GitHub103@192.30.252.34> has joined #immutant17:32
GitHub103[fntest] tobias tagged 2.0.8 at 17d666d: http://git.io/v8UpS17:32
*** GitHub103 <GitHub103!~GitHub103@192.30.252.34> has left #immutant17:32
jbossbotTitle: Commits · immutant/fntest · GitHub17:32
*** GitHub113 <GitHub113!~GitHub113@192.30.252.45> has joined #immutant17:35
GitHub113[lein-immutant] tobias pushed 1 new commit to master: http://git.io/v8UjJ17:35
GitHub113lein-immutant/master afa6d0d Toby Crawley: Use releases of fntest & deploy-tools17:35
*** GitHub113 <GitHub113!~GitHub113@192.30.252.45> has left #immutant17:35
jbossbotTitle: Use releases of fntest & deploy-tools · immutant/lein-immutant@afa6d0d · GitHub17:35
jbossbotgit [immutant] push master 4854e92.. Toby Crawley Use released fntest.17:35
jbossbotgit [immutant] push master URL: http://github.com/immutant/immutant/commit/4854e924117:35
projectodd-ciProject immutant2-incremental build #680: SUCCESS in 7 min 51 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/680/17:44
*** xcv <xcv!~xcv@37.120.119.22> has quit IRC (Remote host closed the connection)17:48
projectodd-ciProject immutant2-incremental-integs-eap build #227: FAILURE in 1 min 21 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs-eap/227/17:48
projectodd-ciToby Crawley: Use released fntest.17:48
*** lance|afk is now known as lanceball18:29
projectodd-ciProject immutant2-incremental-integs build #184: FAILURE in 55 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/184/18:39
projectodd-ciToby Crawley: Use released fntest.18:39
*** jbossbot <jbossbot!~JBossBot@redhat/jbossbot> has quit IRC (Ping timeout: 272 seconds)18:44
*** projectodd-ci <projectodd-ci!~PircBotx@ec2-54-235-41-52.compute-1.amazonaws.com> has quit IRC (Ping timeout: 272 seconds)18:45
*** projectodd-ci <projectodd-ci!~PircBotx@ec2-54-235-41-52.compute-1.amazonaws.com> has joined #immutant18:45
*** jbossbot <jbossbot!~JBossBot@redhat/jbossbot> has joined #immutant18:46
*** jcrossley3-away is now known as jcrossley318:48
*** xcv <xcv!~xcv@2a02:2450:102b:5b:d4ab:737d:e177:c122> has joined #immutant18:48
*** xcv <xcv!~xcv@2a02:2450:102b:5b:d4ab:737d:e177:c122> has quit IRC (Ping timeout: 252 seconds)18:54
jbossbotgit [immutant] push master 3f45354.. Toby Crawley Avoid reflection when logging.18:55
jbossbotgit [immutant] push master URL: http://github.com/immutant/immutant/commit/3f45354f818:55
jcrossley3tcrawley: any failure feedback?18:57
tcrawleynot yet, no18:57
tcrawleythe only -integs failure was one of the common ones (failure to get a cached value from one of the servers)18:57
projectodd-ciProject immutant2-incremental-integs build #185: STILL FAILING in 14 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/185/18:57
tcrawleywell, let's see what that one was18:57
jcrossley3ah18:58
jcrossley3i like your TC prefix :)18:59
tcrawleyheh18:59
jcrossley3so the memoize error is there19:00
jcrossley3but i'm not sure how to map that to your debug19:01
tcrawleyyep, looking at the log19:01
tcrawleyso, we do an api request to get the port, and the result of that request is nil19:01
tcrawleythe last api request made before the error should be the one that didn't get a port19:01
projectodd-ciProject immutant2-incremental build #681: SUCCESS in 5 min 15 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/681/19:02
tcrawleyactually, it's the request before that - the last request gets system-properties19:03
projectodd-ciProject immutant2-incremental-integs-eap build #228: STILL FAILING in 1 min 9 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs-eap/228/19:06
projectodd-ciToby Crawley: Avoid reflection when logging.19:06
jcrossley3huh, the line numbers in api.clj are wrong for me. should HEAD be correct?19:08
tcrawleyno, because I didn't push my debug changes19:08
tcrawleyI'll do that19:08
tcrawleyit looks like it is looking for the :http port offset, I think19:09
tcrawleywhich is https://gist.github.com/1d1c2e280b3d9ee70b80 in the response19:09
tcrawleyI pushed, btw19:10
jcrossley3yeah, looks like the :socket-binding-group is nil for some reason19:11
tcrawleyah, yeah, it is. I was looking at the wrong request. would the :s-b-g be nil if the server was restarting?19:13
tcrawleyshould we backoff-retry the request?19:13
jcrossley3maybe, but i wouldn't expect it to attempt the call if it wasn't up19:14
tcrawleypb19:14
jcrossley3i'm cool with backoff-retry'ing19:14
*** dm3 <dm3!~dm3@pub082136109248.dh-hfc.datazug.ch> has joined #immutant19:16
jcrossley3tcrawley: actually, maybe it's expected to be nil for :child-type "host"19:18
projectodd-ciProject immutant2-incremental-integs build #186: STILL FAILING in 15 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/186/19:19
projectodd-ciToby Crawley: Avoid reflection when logging.19:19
tcrawleyhmm, the request is for :operation "read-children-resources" :child-type "socket-binding-group", so I don't think that "host" request is the correct one19:19
tcrawleywhich I think should be this full response: https://gist.github.com/291079aaf2fddc134ee719:22
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant19:24
tcrawleyunless it's really the offset lookup that is nil, not the port19:24
jcrossley3if i'm reading the code correctly, the order of requests should be: 1) host 2) socket-binding-group 3) system-properties19:27
jcrossley3but the log appears to show 2 1 319:27
jcrossley3idu that19:27
tcrawleyagreed!19:28
tcrawleythat is confusing19:28
jcrossley3do you think the (if ...) is being expanded prior to (offset...)?19:28
tcrawleyfor the :host call, the port offsets are there. it looks for [:server-config server-name :socket-binding-port-offset], which would be there: https://gist.github.com/96bf3d2627d486cdad1319:29
tcrawleyunless we're asking for a non-existent server name19:29
tcrawleymaybe? but that would be weird19:29
jcrossley3this error isn't consistent19:30
tcrawleymeaning it doesn't happen consistently?19:31
jcrossley3correct19:33
tcrawleyright19:33
tcrawleyit's intermittent19:33
tcrawleywhich makes me think timing19:33
jcrossley3yeah19:35
jcrossley3but where?19:35
tcrawleyare we even memoizing the port? it seems like we look it up a lot in the log19:36
jcrossley3i think so19:39
tcrawleywhere?19:39
jcrossley3https://github.com/immutant/jboss-as-management/blob/master/src/jboss_as/management.clj#L5019:40
jcrossley3er...19:41
jcrossley3i'm not sure what's calling that, though :)19:41
jcrossley3fntest?19:41
tcrawleyah, yeah, fntest.core: https://github.com/immutant/fntest/tree/master/src/fntest/core.clj#L5619:43
jcrossley3but that's the wrong port19:43
jcrossley3there's management/port and api/port19:43
jcrossley3i'm not sure why both exist19:43
tcrawleyin fntest.core, confusingly: [jboss-as.management :as api]19:43
jcrossley3but it doesn't seem like anything's calling mgmt/port, which is the memoized one19:43
jcrossley3ah!19:44
jcrossley3yeah, confusing19:44
tcrawleyso it should call the memo version19:44
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 260 seconds)19:44
tcrawleymaybe it is, and this is the first call for the requested server19:44
jcrossley3that's what i was thinking19:44
jcrossley3but you said "a lot" :)19:45
tcrawleywell, there are a ton of :child-type host calls, htf knows what they are really for?19:45
jcrossley3yeah, that's the host-controller. that could probably benefit from memoization, too.19:45
tcrawleyI need a snack, bbiab19:46
jcrossley3of course you do19:47
xeqinom nom19:47
jcrossley3xeqi: don't encourage him19:49
* tcrawley is all snacked up20:12
tcrawleyjcrossley3: did you figure it out in my absence?20:12
jcrossley3tcrawley: no20:13
* jcrossley3 played his guitar20:13
*** audaxion <audaxion!~siksia@unaffiliated/siksia> has quit IRC (Quit: BYE)20:17
*** agarman_ <agarman_!~agarman@169.130.108.37> has joined #immutant20:55
*** agarman <agarman!~agarman@169.130.108.20> has quit IRC (Ping timeout: 260 seconds)20:59
*** agarman_ <agarman_!~agarman@169.130.108.37> has quit IRC (Ping timeout: 264 seconds)20:59
*** deadghost <deadghost!~deadghost@122.167.219.181> has quit IRC (Ping timeout: 264 seconds)21:00
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant21:04
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)21:05
*** xcv <xcv!~xcv@2a02:2450:102b:5b:d4ab:737d:e177:c122> has joined #immutant21:21
*** xcv <xcv!~xcv@2a02:2450:102b:5b:d4ab:737d:e177:c122> has quit IRC (Ping timeout: 252 seconds)21:25
*** lnostdal <lnostdal!~lnostdal@2001:8a0:4937:f801:2c0:caff:fe58:5c47> has quit IRC (Ping timeout: 240 seconds)21:32
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 250 seconds)21:36
*** dm3 <dm3!~dm3@pub082136109248.dh-hfc.datazug.ch> has quit IRC (Remote host closed the connection)21:42
*** lnostdal <lnostdal!~lnostdal@2001:8a0:491c:2601:2c0:caff:fe58:5c47> has joined #immutant21:45
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has joined #immutant22:00
*** bbrowning is now known as bbrowning_away22:12
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant22:15
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 250 seconds)22:30
*** lanceball is now known as lance|afk22:47
*** qwerty_nor <qwerty_nor!~Thunderbi@37.229.49.175> has quit IRC (Ping timeout: 272 seconds)22:48
*** xcv <xcv!~xcv@2a02:2450:102b:5b:d4ab:737d:e177:c122> has joined #immutant23:21
*** GitHub115 <GitHub115!~GitHub115@192.30.252.34> has joined #immutant23:24
GitHub115[wunderboss] tobias pushed 1 new commit to master: http://git.io/v8I9P23:24
GitHub115wunderboss/master 0e6f802 Toby Crawley: Invoke the WS init handler before the socket is connected...23:24
*** GitHub115 <GitHub115!~GitHub115@192.30.252.34> has left #immutant23:24
jbossbotTitle: Invoke the WS init handler before the socket is connected · projectodd/wunderboss@0e6f802 · GitHub23:24
*** xcv <xcv!~xcv@2a02:2450:102b:5b:d4ab:737d:e177:c122> has quit IRC (Ping timeout: 252 seconds)23:26
projectodd-ciProject wunderboss-incremental build #297: SUCCESS in 3 min 7 sec: https://projectodd.ci.cloudbees.com/job/wunderboss-incremental/297/23:27
projectodd-ciToby Crawley: Invoke the WS init handler before the socket is connected23:27
jbossbotgit [immutant] push master be8e100.. Toby Crawley Allow setting headers from a websocket handshake [IMMUTANT-580]23:29
jbossbotgit [immutant] push master URL: http://github.com/immutant/immutant/commit/be8e1009f23:29
jbossbotjira [IMMUTANT-580] Support for setting HTTP response headers in the WebSocket handshake [Open (Unresolved) Enhancement, Minor, Toby Crawley] https://issues.jboss.org/browse/IMMUTANT-58023:29
*** tcrawley is now known as tcrawley-away23:31
projectodd-ciProject immutant2-incremental build #682: SUCCESS in 4 min 57 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/682/23:35
*** xcv <xcv!~xcv@37.120.30.253> has joined #immutant23:49
projectodd-ciYippee, build fixed!23:54
projectodd-ciProject immutant2-incremental-integs build #187: FIXED in 18 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/187/23:54
projectodd-ciToby Crawley: Allow setting headers from a websocket handshake [IMMUTANT-580]23:54
jbossbotjira [IMMUTANT-580] Support for setting HTTP response headers in the WebSocket handshake [Open (Unresolved) Enhancement, Minor, Toby Crawley] https://issues.jboss.org/browse/IMMUTANT-58023:54
projectodd-ciProject immutant2-incremental-integs-eap build #229: STILL FAILING in 51 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs-eap/229/23:55
projectodd-ciToby Crawley: Allow setting headers from a websocket handshake [IMMUTANT-580]23:55
jbossbotjira [IMMUTANT-580] Support for setting HTTP response headers in the WebSocket handshake [Open (Unresolved) Enhancement, Minor, Toby Crawley] https://issues.jboss.org/browse/IMMUTANT-58023:55
*** xcv <xcv!~xcv@37.120.30.253> has quit IRC (Ping timeout: 265 seconds)23:55
*** bostonaholic <bostonaholic!~textual@97-122-166-12.hlrn.qwest.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)23:58

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