Tuesday, 2015-05-12

*** bbrowning_away is now known as bbrowning00:12
*** jcrossley3 is now known as jcrossley3-away00:33
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant00:52
*** tcrawley-away is now known as tcrawley00:55
*** tcrawley is now known as tcrawley-away00:59
*** deadghost <deadghost!~deadghost@49.230.116.51> has quit IRC (Ping timeout: 272 seconds)01:01
*** bbrowning is now known as bbrowning_away01:12
*** tcrawley-away is now known as tcrawley01:50
*** tcrawley is now known as tcrawley-away01:52
*** [1]cnb <[1]cnb!~cnb@pc-74-8-74-200.cm.vtr.net> has quit IRC (Quit: Want to be different? Try HydraIRC -> http://www.hydrairc.com <-)02:20
*** deadghost <deadghost!~deadghost@49.230.116.51> has joined #immutant02:22
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has joined #immutant02:38
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has quit IRC (Quit: bobby_)03:31
*** bostonaholic <bostonaholic!~textual@c-50-134-212-204.hsd1.co.comcast.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)04:06
*** deadghost <deadghost!~deadghost@49.230.116.51> has quit IRC (Ping timeout: 255 seconds)05:12
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 240 seconds)05:17
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant06:18
*** mgoldmann|away is now known as mgoldmann06:22
*** jbossbot <jbossbot!~JBossBot@redhat/jbossbot> has quit IRC (Ping timeout: 256 seconds)06:47
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant07:07
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)07:26
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has joined #immutant07:26
*** jbossbot <jbossbot!~JBossBot@redhat/jbossbot> has joined #immutant07:38
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant07:40
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has quit IRC (Ping timeout: 256 seconds)07:47
*** qwerty_nor <qwerty_nor!~Thunderbi@5.248.107.224> has joined #immutant08:12
*** deadghost <deadghost!~deadghost@49.230.116.51> has joined #immutant08:23
*** qwerty_nor <qwerty_nor!~Thunderbi@5.248.107.224> has quit IRC (Ping timeout: 264 seconds)08:36
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has joined #immutant08:42
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Remote host closed the connection)08:45
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant08:46
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 246 seconds)08:50
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has quit IRC (Ping timeout: 272 seconds)09:18
*** dm3 <dm3!~dm3@pub158181119172.dh-hfc.datazug.ch> has joined #immutant09:22
*** marianoguerra <marianoguerra!~marianogu@195.245.197.229> has joined #immutant09:28
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has joined #immutant09:28
*** qwerty_nor <qwerty_nor!~Thunderbi@5.248.107.224> has joined #immutant10:18
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)11:14
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant11:15
*** deadghost <deadghost!~deadghost@49.230.116.51> has quit IRC (Ping timeout: 272 seconds)11:18
*** deadghost <deadghost!~deadghost@49.230.116.51> has joined #immutant11:57
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has quit IRC (Ping timeout: 264 seconds)11:59
*** lance|afk is now known as lanceball12:02
*** agarman <agarman!~agarman@169.130.108.20> has quit IRC (Quit: Leaving.)12:06
*** agarman <agarman!~agarman@169.130.108.20> has joined #immutant12:06
*** tcrawley-away is now known as tcrawley12:10
*** jcrossley3-away is now known as jcrossley312:16
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has joined #immutant12:17
*** bbrowning_away is now known as bbrowning12:27
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant12:48
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has joined #immutant13:17
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 256 seconds)13:20
*** bostonaholic <bostonaholic!~textual@c-50-134-212-204.hsd1.co.comcast.net> has joined #immutant13:38
*** bostonaholic <bostonaholic!~textual@c-50-134-212-204.hsd1.co.comcast.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)13:52
*** agarman1 <agarman1!~agarman@169.130.108.37> has joined #immutant14:02
*** agarman <agarman!~agarman@169.130.108.20> has quit IRC (Ping timeout: 244 seconds)14:06
*** bostonaholic <bostonaholic!~textual@c-50-134-212-204.hsd1.co.comcast.net> has joined #immutant14:11
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has joined #immutant14:31
bobby_jcrossley3 tcrawley: I’m running into a snag using immutant.messaging when subscribing to pre-defined topics on a remote context.  immutant.messaging/subscribe is throwing an NPE.  What’s the best way to communicate the issue to you?  At this point I suspect it’s an issue in wunderboss, but it’s entirely possible that it’s user error :-)14:34
jcrossley3bobby_: @jira is preferred14:34
proddbotWe'd be happy as birds that sing on a tree if you would file an issue at https://issues.jboss.org/browse/IMMUTANT14:34
jcrossley3or you can describe it here14:35
jcrossley3any kind of small test app demonstrating the issue would be most appreciated14:35
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)14:36
bobby_jcrossley3: I’ll put together a gist and drop it here to screen if I’ve done something obviously dumb, and if not, I’ll add to jira14:36
bobby_thanks!14:36
jcrossley3bobby_: sure thing!14:36
tcrawleybobby_: can you share a gist of the NPE now? that may give us an immediate clue. and what version of Immutant is this?14:48
bobby_tcrawley: https://gist.github.com/bobby/cf472afba67e5cd60e6e14:50
bobby_Running hornetq 2.4.0.Final standalone, non-clustered14:51
tcrawleycool, thanks. can you share the stack of the NPE?14:51
bobby_tcrawley: it appears that the client connects to the topic prior to NPE, because an attempted re-connect complains of an existing ClientID=“foo”14:51
bobby_whoops, yes, I’ll add to gist14:52
bobby_tcrawley: https://gist.github.com/bobby/cf472afba67e5cd60e6e updated14:53
bobby_my suspicion was that I was running afoul of some JNDI naming/path convention baked into wunderboss, but I’ve tried several permutations of -jmx.xml configs with various entries that matched the convention in https://github.com/projectodd/wunderboss/blob/master/modules/messaging/src/main/java/org/projectodd/wunderboss/messaging/hornetq/HQDestination.java#L19814:54
jcrossley3bobby_: i assume you saw this? http://immutant.org/documentation/2.0.0/apidoc/guide-messaging.html#h533414:56
jbossbotTitle: Immutant 2.0.0 API documentation14:56
bobby_jcrossley3: yes, read all the docs, but that one pertains specifically to running within Wildfly, vs. my case of running against hornetq standalone14:57
jcrossley3hmmm14:57
jcrossley3i thought the config was the same14:57
bobby_somewhat similar.  There are two styles of config: JMS and Hornet/Core.  The style in the gist is the latter, but tried with identical results using *-jms.xml style config14:58
bobby_i’ll test again and update the xml config in the gist14:58
tcrawleyI think the NPE is caused by the JMS server's registry being null15:00
tcrawleyor the server itself being null15:00
tcrawleythe latter would be true if you are only talking to remote HQ15:00
tcrawleyit shouldn't be asking the local server about a remote topic at all15:01
tcrawleybut it appears to be doing so, so that's a bug15:01
jcrossley3huh15:02
jcrossley3would a possible workaround be to start a random queue? or just invoke the wboss impl?15:03
tcrawleythat may work as a workaround, yes. (msg/queue "something") will start the local HQ, even though it won't be used15:03
tcrawleyother than trying to look up the non-existent topic15:04
tcrawleythough it's unclear to me how it actually gets reference to the remote topic15:05
jcrossley3bobby_: can you verify that works? ^15:06
bobby_tcrawley jcrossley3: that was another suspicion that I had, but didn’t know enough to make heads or tails15:07
bobby_trying work-around now15:07
jcrossley3might be cheaper to just call (immutant.messaging.internal/broker nil)15:08
tcrawleyI think I see the bug, and I don't think that workaround will work :(15:09
jcrossley3:(15:09
tcrawleyI think https://github.com/projectodd/wunderboss/blob/master/modules/messaging/src/main/java/org/projectodd/wunderboss/messaging/hornetq/HQTopic.java#L106 shouldn't override its parent15:12
jcrossley3interesting15:14
bobby_tcrawley: workaround doesn’t work, updated: https://gist.github.com/bobby/cf472afba67e5cd60e6e15:16
jcrossley3tcrawley: that was part of a pretty big change15:16
bobby_jcrossley3 tcrawley: how should I proceed?  Create issue in JIRA15:23
jcrossley3bobby_: yes, please15:24
bobby_jcrossley3 tcrawley: https://issues.jboss.org/browse/IMMUTANT-56015:36
jbossbotjira [IMMUTANT-560] Subscribing to pre-existing topic with remote context throws NPE [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-56015:36
*** agarman <agarman!~agarman@169.130.108.20> has joined #immutant15:38
*** agarman1 <agarman1!~agarman@169.130.108.37> has quit IRC (Ping timeout: 265 seconds)15:40
jcrossley3bobby_: thanks!15:42
*** dark4eg <dark4eg!~dark4eg@188.168.34.194> has quit IRC (Read error: Connection reset by peer)15:53
*** deadghost <deadghost!~deadghost@49.230.116.51> has quit IRC (Ping timeout: 264 seconds)15:58
*** deadghost <deadghost!~deadghost@49.230.116.51> has joined #immutant15:58
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant16:25
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has quit IRC (Quit: bobby_)16:26
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has quit IRC (Ping timeout: 264 seconds)16:45
*** bbrowning is now known as bbrowning_away16:48
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has quit IRC (Ping timeout: 252 seconds)16:48
*** dm3_ <dm3_!~dm3@pub158181119172.dh-hfc.datazug.ch> has joined #immutant16:55
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has joined #immutant16:56
*** dm3 <dm3!~dm3@pub158181119172.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 256 seconds)16:58
*** dm3_ <dm3_!~dm3@pub158181119172.dh-hfc.datazug.ch> has quit IRC (Ping timeout: 240 seconds)16:59
*** bbrowning_away is now known as bbrowning17:09
*** galderz <galderz!~galder@redhat/jboss/galderz> has joined #immutant17:18
*** lanceball is now known as lance|afk17:48
*** marianoguerra <marianoguerra!~marianogu@a95-93-242-245.cpe.netcabo.pt> has joined #immutant17:48
*** marianoguerra <marianoguerra!~marianogu@a95-93-242-245.cpe.netcabo.pt> has quit IRC (Changing host)17:48
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has joined #immutant17:48
*** bbrowning is now known as bbrowning_away17:56
*** jcrossley3 is now known as jcrossley3-away18:04
*** bostonaholic <bostonaholic!~textual@c-50-134-212-204.hsd1.co.comcast.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)18:12
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has quit IRC (Ping timeout: 272 seconds)18:12
*** bostonaholic <bostonaholic!~textual@c-50-134-212-204.hsd1.co.comcast.net> has joined #immutant18:13
*** galderz <galderz!~galder@redhat/jboss/galderz> has quit IRC (Quit: This computer has gone to sleep)18:18
*** bobby_ <bobby_!~bobby@wsip-98-190-221-98.dc.dc.cox.net> has quit IRC (Quit: bobby_)18:19
*** cap10morgan <cap10morgan!~cap10morg@75-148-43-81-Colorado.hfc.comcastbusiness.net> has joined #immutant18:20
*** bostonaholic <bostonaholic!~textual@c-50-134-212-204.hsd1.co.comcast.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)18:22
*** lance|afk is now known as lanceball18:32
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has joined #immutant18:47
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has joined #immutant18:56
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has quit IRC (Quit: bobby_)19:07
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has joined #immutant19:10
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has quit IRC (Client Quit)19:12
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has joined #immutant19:12
*** jcrossley3-away is now known as jcrossley319:21
*** conan_ <conan_!~conan@mdproctor.plus.com> has quit IRC (Read error: Connection reset by peer)19:22
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has quit IRC (Quit: bobby_)19:23
*** jcrossley3 <jcrossley3!~user@71-90-202-246.dhcp.stls.mo.charter.com> has quit IRC (Quit: ERC Version 5.3 (IRC client for Emacs))19:35
*** jcrossley3 <jcrossley3!~user@redhat/jboss/jc3> has joined #immutant19:35
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has joined #immutant19:37
*** qwerty_nor <qwerty_nor!~Thunderbi@5.248.107.224> has quit IRC (Ping timeout: 256 seconds)19:47
*** bobmcw <bobmcw!~bobmcw@redhat/jboss/bobmcw> has quit IRC (Remote host closed the connection)19:55
*** GitHub69 <GitHub69!~GitHub69@192.30.252.45> has joined #immutant19:58
GitHub69[wunderboss] tobias pushed 1 new commit to master: http://git.io/vUVH919:58
GitHub69wunderboss/master 1123a66 Toby Crawley: Don't lookup JMS topic via JNDI [IMMUTANT-560]...19:58
*** GitHub69 <GitHub69!~GitHub69@192.30.252.45> has left #immutant19:58
jbossbotTitle: Don't lookup JMS topic via JNDI [IMMUTANT-560] · projectodd/wunderboss@1123a66 · GitHub19:58
jbossbotjira [IMMUTANT-560] Subscribing to pre-existing topic on remote context throws NPE [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-56019:58
*** bbrowning_away is now known as bbrowning20:01
projectodd-ciProject wunderboss-incremental build #236: SUCCESS in 3 min 41 sec: https://projectodd.ci.cloudbees.com/job/wunderboss-incremental/236/20:03
projectodd-ciToby Crawley: Don't lookup JMS topic via JNDI [IMMUTANT-560]20:03
jbossbotjira [IMMUTANT-560] Subscribing to pre-existing topic on remote context throws NPE [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-56020:03
*** bostonaholic <bostonaholic!~textual@c-50-134-212-204.hsd1.co.comcast.net> has joined #immutant20:06
jbossbotgit [immutant] push thedeuce cf24895.. Toby Crawley Use newer WunderBoss that uses the correct Topic ref when remote [IMMUTANT-560]20:10
jbossbotgit [immutant] push thedeuce URL: http://github.com/immutant/immutant/commit/cf24895a920:10
jbossbotjira [IMMUTANT-560] Subscribing to pre-existing topic on remote context throws NPE [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-56020:10
*** cemerick <cemerick!~cemerick@c-24-34-140-98.hsd1.ma.comcast.net> has joined #immutant20:10
tcrawleybobby_: once ^ builds, I'll have an incremental build for you to test20:10
tcrawleyit fixed the issue for me locally20:10
bobby_tcrawley: wow, that was really fast!  I’ll be happy to test the build, as it would unstick me!20:10
tcrawleycool, once it finishes, I'll link to it from the jira20:11
tcrawleyyou also mentioned seeing "InvalidClientIDRuntimeException: clientID=foo was already set into another connection", I got that too when testing, and realized that you may see that error often when you have reconnection enabled, since if there is a network issue that breaks the connection but the context wasn't properly closed, HornetQ will still see it as open20:13
tcrawleywhen the context reconnects20:13
tcrawleyand there may not be anything we can do about that20:14
tcrawleyunless we lower HQ's timeout for giving up on those connections20:14
tcrawleylet us know if you do indeed see that issue in the future20:14
projectodd-ciProject immutant2-incremental build #569: SUCCESS in 3 min 50 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/569/20:14
projectodd-ciToby Crawley: Use newer WunderBoss that uses the correct Topic ref when remote [IMMUTANT-560]20:14
jbossbotjira [IMMUTANT-560] Subscribing to pre-existing topic on remote context throws NPE [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-56020:14
tcrawleybobby_: ^ there you go20:14
tcrawleysee http://immutant.org/builds/2x/ if you need help setting up an incremental build20:15
jbossbotTitle: Immutant | 2.x Incremental Builds20:15
jcrossley3bobby_: just to be clear, you don't need to build it, just reference its repo in your project.clj20:17
projectodd-ciProject immutant2-incremental-integs build #56: STILL FAILING in 3 min 0 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/56/20:17
projectodd-ciToby Crawley: Use newer WunderBoss that uses the correct Topic ref when remote [IMMUTANT-560]20:17
jbossbotjira [IMMUTANT-560] Subscribing to pre-existing topic on remote context throws NPE [Open (Unresolved) Bug, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-56020:17
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant20:18
jbossbotgit [immutant] push thedeuce 9132937.. Toby Crawley Have integs look at the correct build version, and update the integ...20:20
jbossbotgit [immutant] push thedeuce URL: http://github.com/immutant/immutant/commit/9132937da20:20
tcrawleyjcrossley3: I think ^ is the right thing to do?20:20
jcrossley3tcrawley: good call20:22
tcrawleyfor integs/project.clj, org.immutant/immutant is versioned _. will that pick up the version of the project itself in that case?20:22
jcrossley3tcrawley: it actually comes from here: https://github.com/immutant/immutant/tree/thedeuce/project.clj#L9720:24
tcrawleyhmm, the integs were looking for org.immutant/immutant "2.0.0-SNAPSHOT" instead of "2.1.0-SNAPSHOT" for some reason20:24
tcrawleyare you sure it's using the parent version there?20:25
jcrossley3hmm20:25
jcrossley3it's possible :version resolves to the child20:25
jcrossley3that would make more sense actually20:25
projectodd-ciProject immutant2-incremental build #570: SUCCESS in 4 min 27 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/570/20:25
projectodd-ciToby Crawley: Have integs look at the correct build version, and update the integ20:25
jcrossley3it is using the key i linked to (in the parent), but the value of :version would be from the child20:26
tcrawleygotcha20:27
jcrossley3tcrawley: i'd like to remove those "set" calls prior to releasing 2.0.1 if that's ok with you20:27
tcrawleywhat would set the versions?20:28
jcrossley3that way, we can stop manually doing it20:28
jcrossley3the release task20:28
tcrawleywhy are we calling set now then?20:29
jcrossley3it can handle X.Y.Z, but not X.Y.Z-somethingQ20:29
tcrawleyah20:29
tcrawleywait, what about the child projects?20:29
jcrossley3idu20:29
projectodd-ciProject immutant2-incremental-integs build #57: STILL FAILING in 3 min 7 sec: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/57/20:29
projectodd-ciToby Crawley: Have integs look at the correct build version, and update the integ20:29
tcrawleyright now, we call "modules change version set ..." - the release task won't invoke the modules mw, will it?20:30
jcrossley3tcrawley: https://github.com/jcrossley3/lein-modules#release-management20:31
jcrossley3we won't call set20:31
jcrossley3we'll call bump-version20:31
tcrawleyah, gotcha20:32
jcrossley3thus eliminating the hard-coded versions20:32
tcrawleycool. do it up, homie20:32
jcrossley3when do you want to release 2.0.1?20:32
tcrawleyI'd like to take a look at IMMUTANT-559 first20:34
jbossbotjira [IMMUTANT-559] Consider timing out the :main call [Open (Unresolved) Feature Request, Major, Unassigned] https://issues.jboss.org/browse/IMMUTANT-55920:34
tcrawleymaybe I can get to that tamari, and release on Thursday?20:34
jcrossley3coolio20:35
tcrawleybobby_: I noticed from your gist that you're using boot. do use Immutant with WildFly at all? if so, we now have a boot-immutant task20:35
tcrawleyit's a little rough, but I hope to test it and get a non-SNAPSHOT out soonish20:35
jcrossley3tcrawley: i don't think his issue occurs in wildfly :)20:35
jcrossley3so i'm guessing no20:35
bobby_tcrawley: no, not using with WildFly, but rather from docker container20:35
tcrawleyjcrossley3: right, I know the issue wasn't in WF, but I was seeing if he used it otherwise20:36
tcrawleybobby_: thanks20:36
jcrossley3tcrawley: i actually pledged to myself that i wouldn't be an asshole this week, so sorry.20:36
bobby_tcrawley jcrossley3: also, in case you couldn’t hear over the sound of my bug-whining earlier, I’ve really liked working with Immutant!20:36
jcrossley3bobby_: awesome! thanks for helping us make it better!20:37
tcrawleybobby_: thanks! that's great to hear :)20:37
tcrawleywith the way jcrossley3 treats me, I can use all the kind words I can get20:37
jcrossley3dammit!20:37
bobby_I’m running a bunch of small services, each in its own docker container, using immutant.messaging to communicate among them, and Sente+immutant.web for server=>client comms20:38
tcrawleynice!20:38
jcrossley3fancy!20:38
tcrawleynice + fancy = nancy20:38
tcrawleynincy?20:38
jcrossley3bobby_: you should blog about the tradeoffs you made along the way at some point.20:39
bobby_yes, that would be good20:39
bobby_project is actually in an interesting state, currently decomposing a single-JVM app that used core.async channels for inter-component comms into the architecture I described above, so immutant.messaging has become very important, as is the suite-of-libraries approach you took in Immutant 2.  It’s been interesting to deploy this way vs. traditional J2EE/container arch.20:41
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Remote host closed the connection)20:41
bobby_jcrossley3 tcrawley: so kudos to Immutant and the decisions you made in v2!20:42
jcrossley3bobby_: music to our ears, my friend :)20:43
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has joined #immutant20:50
*** conan <conan!~conan@mdproctor.plus.com> has joined #immutant21:03
*** dm3 <dm3!~dm3@pub151248158012.dh-hfc.datazug.ch> has quit IRC (Remote host closed the connection)21:03
bobby_tcrawley jcrossley3: the NPE has gone away as of 569.  I’m currently running into hornetq authorization issues, but I’ll let you know when I’ve hit smooth waters.21:23
tcrawleycool, thanks!21:24
bobby_tcrawley jcrossley3: looking good on latest incremental, i’m through the authz issue and humming right along21:37
bobby_thanks again!21:37
jcrossley3yay!21:37
tcrawleygood deal! we hope to release a 2.0.1 for you by the end of the week or early next21:37
*** tcrawley is now known as tcrawley-away21:43
*** bbrowning is now known as bbrowning_away21:44
jcrossley3tcrawley-away: still around?21:45
*** astoon <astoon!~astoon@91.202.45.54> has joined #immutant21:48
*** lanceball is now known as lance|afk21:51
*** jcrossley3 <jcrossley3!~user@redhat/jboss/jc3> has quit IRC (Quit: ERC Version 5.3 (IRC client for Emacs))21:59
*** jcrossley3 <jcrossley3!~user@redhat/jboss/jc3> has joined #immutant21:59
*** bobby_ <bobby_!~bobby@pool-70-106-220-21.clppva.fios.verizon.net> has quit IRC (Quit: bobby_)22:05
jbossbotgit [immutant] push thedeuce 94f5766.. Jim Crossley Un-hardcode next release version and reset next to 2.0.122:31
jbossbotgit [immutant] push thedeuce URL: http://github.com/immutant/immutant/commit/94f57666f22:31
*** cap10morgan <cap10morgan!~cap10morg@75-148-43-81-Colorado.hfc.comcastbusiness.net> has quit IRC (Quit: (null))22:36
projectodd-ciProject immutant2-incremental build #571: SUCCESS in 13 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental/571/22:45
projectodd-ciJim Crossley: Un-hardcode next release version and reset next to 2.0.122:45
projectodd-ciProject immutant2-incremental-integs build #58: STILL FAILING in 11 min: https://projectodd.ci.cloudbees.com/job/immutant2-incremental-integs/58/22:57
projectodd-ciJim Crossley: Un-hardcode next release version and reset next to 2.0.122:57
*** bostonaholic <bostonaholic!~textual@c-50-134-212-204.hsd1.co.comcast.net> has quit IRC (Quit: My Mac has gone to sleep. ZZZzzz…)23:09
*** bostonaholic <bostonaholic!~textual@c-50-134-212-204.hsd1.co.comcast.net> has joined #immutant23:19
*** marianoguerra <marianoguerra!~marianogu@emesene/grandpa/marianoguerra> has quit IRC (Ping timeout: 276 seconds)23:31

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