Timestamps are in GMT/BST.
[3:26] * lyncode (~DSpace@bl23-57-40.dsl.telepac.pt) has joined #duraspace
[3:26] * lyncode (~DSpace@bl23-57-40.dsl.telepac.pt) Quit (Client Quit)
[6:40] -wolfe.freenode.net- *** Looking up your hostname...
[6:40] -wolfe.freenode.net- *** Checking Ident
[6:40] -wolfe.freenode.net- *** Found your hostname
[6:40] -wolfe.freenode.net- *** No Ident response
[6:40] [frigg VERSION]
[6:40] * DuraLogBot (~PircBot@atlas.duraspace.org) has joined #duraspace
[6:40] * Topic is '[Welcome to DuraSpace - This channel is logged - http://irclogs.duraspace.org/]'
[6:40] * Set by cwilper!ad579d86@gateway/web/freenode/ip.173.87.157.134 on Fri Oct 22 01:19:41 UTC 2010
[12:17] * mhwood (mwood@mhw.ulib.iupui.edu) has joined #duraspace
[12:52] * tdonohue (~tdonohue@c-67-177-108-221.hsd1.il.comcast.net) has joined #duraspace
[13:17] * mhwood (mwood@mhw.ulib.iupui.edu) Quit (Quit: Leaving.)
[13:18] * mhwood (mwood@mhw.ulib.iupui.edu) has joined #duraspace
[13:28] * scottatm (~scottatm@adhcp218.evans.tamu.edu) has joined #duraspace
[14:20] * tdonohue (~tdonohue@c-67-177-108-221.hsd1.il.comcast.net) Quit (Read error: Connection reset by peer)
[14:51] * tdonohue (~tdonohue@c-67-177-108-221.hsd1.il.comcast.net) has joined #duraspace
[16:20] * grahamtriggs (~Graham@host213-123-239-134.in-addr.btopenworld.com) has joined #duraspace
[16:20] * grahamtriggs (~Graham@host213-123-239-134.in-addr.btopenworld.com) has left #duraspace
[19:07] * ryscher (98033b4c@gateway/web/freenode/ip.152.3.59.76) has joined #duraspace
[19:32] * helix84 (a@195.113.97.174) has joined #duraspace
[19:34] * ChanServ (ChanServ@services.) Quit (shutting down)
[19:35] * ChanServ (ChanServ@services.) has joined #duraspace
[19:50] * hpottinger (~hpottinge@mu-162198.dhcp.missouri.edu) has joined #duraspace
[19:53] * kstamatis (b03adf91@gateway/web/freenode/ip.176.58.223.145) has joined #duraspace
[19:56] * KevinVdV (~KevinVdV@d54C154B1.access.telenet.be) has joined #duraspace
[19:58] * PeterDietz (~peterdiet@128.146.173.112) has joined #duraspace
[20:00] <tdonohue> Hi all, welcome. The DSpace Developers Mtg starts now. Agenda for today: https://wiki.duraspace.org/display/DSPACE/DevMtg+2012-10-10
[20:00] <kompewter> [ DevMtg 2012-10-10 - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DevMtg+2012-10-10
[20:01] <tdonohue> Essentially, as we've done recently, today is going to concentrate on 3.0 Release & Testathon (which was just officially announced an hour or so ago)
[20:02] <tdonohue> First off though, thanks to the 3.0 Release Team & all the contributors for helping us get to 3.0 Release Candidate #1!
[20:03] <tdonohue> But, obviously, we're not done yet...we could still use plenty of help in the next 10 days to test 3.0-rc1 & see what we can find that needs fixing before the final 3.0
[20:03] <mhwood> I have my own 3.0-rc1 running and have begun kicking the tires.
[20:03] <helix84> especially we haven't budged with the long list of bugs scheduled in Jira for 3.0
[20:04] <tdonohue> Testathon runs until end-of-day Fri, Oct 19 -- though the http://demo.dspace.org server will continue to be available all the way up until the final 3.0 release. So, whenever you can test, please feel free! If you have time to help fix bugs too, we'd appreciate it as well.
[20:04] <kompewter> [ DSpace 3.0 Demonstration Repository ] - http://demo.dspace.org
[20:05] <tdonohue> Ok, so, the topics today are actually a bit "general". First and foremost, I just wanted to ask to see if there's anything else to be done for Testathon or anything related to Testathon anyone wants to talk about?
[20:07] <helix84> well, the Release Notes page still contains the old list of proposed features. I haven't gotten around to updating it.
[20:08] <tdonohue> helix84 -- I just updated that with a very basic list of features (about an hour ago): https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.0+Notes
[20:08] <kompewter> [ DSpace Release 3.0 Notes - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.0+Notes
[20:08] <helix84> tdonohue: i see, thanks
[20:08] <tdonohue> direct link: https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.0+Notes#DSpaceRelease3.0Notes-NewfeaturesinDSpace3.0
[20:08] <kompewter> [ DSpace Release 3.0 Notes - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.0+Notes#DSpaceRelease3.0Notes-NewfeaturesinDSpace3.0
[20:08] <tdonohue> Although, it would be good if *everyone* reviewed that list. It's very possible I forgot to list a major feature that should make it on that list.
[20:09] <helix84> secondly, although bug fixing isn't glorious work, we should start looking at the reported bugs, see the bottom of this list:
[20:09] <helix84> https://wiki.duraspace.org/display/DSPACE/DSpace+3.0+Tasks
[20:09] <kompewter> [ DSpace 3.0 Tasks - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/DSpace+3.0+Tasks
[20:09] <helix84> some of them have been reported for quite some time
[20:09] * aschweer (~schweer@schweer.its.waikato.ac.nz) has joined #duraspace
[20:09] <helix84> IIRC, some even have patches
[20:10] <tdonohue> I wonder if we should just look at the JIRA list? This 3.0 Tasks page is now outdated, and it's a bit hard to look at with the giant list of everything.... here's what is still open in JIRA & scheduled for 3.0: https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+DS+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+%223.0%22+ORDER+BY+priority+DESC
[20:10] <kompewter> [ Issue Navigator - DuraSpace JIRA ] - https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+DS+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+%223.0%22+ORDER+BY+priority+DESC
[20:11] * sands (~sandsfish@18.189.25.238) has joined #duraspace
[20:12] <tdonohue> (The main reason I'd like to get us off the "3.0 Tasks" page is that as new bugs get reported, it's easier to have them auto-appear via a JIRA query than remember to add them to that Wiki page
[20:12] <tdonohue> But, I fully agree that we need to start assigning/tackling the 3.0 bugs that we already know of.
[20:13] <helix84> tdonohue: you're right about the Tasks page, it has been kept manually and it got a bit outdated while I was away
[20:13] <mhwood> I just Resolved one that has actually been pulled. (ds-1182, was waiting for comment on whether it worked elsewhere.)
[20:13] <kompewter> [ https://jira.duraspace.org/browse/ds-1182 ] - [#DS-1182] Javamail: Getting Session object with getDefaultInstace - DuraSpace JIRA
[20:13] <helix84> does anyone see any mouth-watering bugs they would like to take?
[20:14] <helix84> mhwood: I just updated its status
[20:14] <tdonohue> One that sticks out here is DS-1081 -- we need help verifying whether or not DSpace works on Java 7 (both Oracle & OpenJDK)
[20:14] <kompewter> [ https://jira.duraspace.org/browse/DS-1081 ] - [#DS-1081] Ensure that DSpace can run on java 7 - DuraSpace JIRA
[20:14] <helix84> mhwood: regarding that bug, see my last comment
[20:15] <sands> Flag here on the release. I could not get mvn release:prepare to work with Java 7 on OS/X
[20:15] <helix84> tdonohue: I noticed demo.d.o has been running on OpenJDK 7
[20:15] <sands> not exactly the same thing as DSpace running on it, but relevant perhaps.
[20:15] * lyncode (~Utilizado@bl23-57-40.dsl.telepac.pt) has joined #duraspace
[20:15] <tdonohue> demo.dspace.org is running OpenJDK 7. Which helps us test it, yes. But, there are issues noted in the comments of Ds-1081 around XMLWorkflow
[20:16] * mdiggory (~mdiggory@rrcs-74-87-47-118.west.biz.rr.com) has joined #duraspace
[20:16] <helix84> are there any users of XMLWorkflow among us?
[20:16] <helix84> speak of the devil :)
[20:17] <mdiggory> Hey!...
[20:17] <tdonohue> I'm wondering if someone from @mire (mdiggory or KevinVdV) has looked into the Java 7 issues reported with XMLWorkflow in comments of DS-1081
[20:17] <kompewter> [ https://jira.duraspace.org/browse/DS-1081 ] - [#DS-1081] Ensure that DSpace can run on java 7 - DuraSpace JIRA
[20:18] <tdonohue> I personally consider Java 7 support to be a *high priority* in this release, as Java 6 is coming very soon (Feb 2013, IIRC)
[20:18] <tdonohue> s/Java 6/Java 6 EOL/
[20:18] <kompewter> tdonohue meant to say: I personally consider Java 7 support to be a *high priority* in this release, as Java 6 EOL is coming very soon (Feb 2013, IIRC)
[20:18] <mdiggory> looking at ticket
[20:19] <mdiggory> we really should be trying to upgrade to the latest version of Spring as well
[20:20] <tdonohue> mdiggory: sounds good to me assuming we test things on latest Spring, put it in a ticket ;)
[20:20] <mhwood> Anybody run the version-check mojo recently?
[20:20] <mdiggory> latest is 3.1.2.RELEASE
[20:21] <tdonohue> version-check mojo? How do you run that? (I honestly don't know)
[20:21] * hpottinger was wondering the same thing, and thinking it must be something to do with Maven...
[20:21] <tdonohue> (but it sounds like something that should get into our docs somewhere -- we need a list of such things for Release Team)
[20:21] <mhwood> Trying to remember which Maven plugin it's in.
[20:22] <mdiggory> https://jira.duraspace.org/browse/DS-1280
[20:22] <kompewter> [ [#DS-1280] Upgrade Spring to latest release possible - DuraSpace JIRA ] - https://jira.duraspace.org/browse/DS-1280
[20:22] <kompewter> [ https://jira.duraspace.org/browse/DS-1280 ] - [#DS-1280] Upgrade Spring to latest release possible - DuraSpace JIRA
[20:23] <ryscher> http://demo.dspace.org just crashed -- yay testathon!
[20:23] <kompewter> [ DSpace 3.0 Demonstration Repository ] - http://demo.dspace.org
[20:23] <ryscher> (xmlui, that is)
[20:23] * scottatm (~scottatm@adhcp218.evans.tamu.edu) Quit (Quit: scottatm)
[20:23] <mdiggory> http://mojo.codehaus.org/versions-maven-plugin/examples/display-dependency-updates.html
[20:23] <kompewter> [ Checking for new dependency updates ] - http://mojo.codehaus.org/versions-maven-plugin/examples/display-dependency-updates.html
[20:23] <mhwood> Might be thinking of http://mojo.codehaus.org/versions-maven-plugin/
[20:23] <kompewter> [ Introduction ] - http://mojo.codehaus.org/versions-maven-plugin/
[20:24] <hpottinger> woah, litterally mojo...
[20:24] <aschweer> yup I just ran mvn versions:display-dependency-updates on a local project and it came up with useful things
[20:24] <tdonohue> yep...looks like 3.0-RC1 XMLUI crashed on demo site (thanks ryscher)
[20:24] <helix84> Caused by: java.lang.OutOfMemoryError: PermGen space
[20:25] <mdiggory> Well isn't that special
[20:25] <hpottinger> oh, well, then the whole container won't work...
[20:25] <tdonohue> Oh yea...demo.dspace.org XMLUI says "OutOfMemoryError : PermGen space"
[20:25] <mdiggory> our favorite kinda exception
[20:25] <hpottinger> more power!
[20:26] <mhwood> Hmmm, versions wants us to upgrade Spring from 3.0.5-RELEASE to 2.5.6.
[20:27] <mdiggory> the groupid changed I think....
[20:27] <helix84> just asking so that we don't tread on each other's toes: should I just restart it or will someone (Tim?) increase memory?
[20:28] <tdonohue> Hmm...guess our old recommendations for PermGen Memory = 128MB is not enough anymore?
[20:28] <helix84> tdonohue: must be the huge number of items we have on demo...
[20:28] <tdonohue> helix84 : I'm on demo.dspace.org -- just trying to determine how much PermGen DSpace needs now...and why the heck 128MB is no longer enough.
[20:28] * qwebirc8422 (126518da@gateway/web/freenode/ip.18.101.24.218) has joined #duraspace
[20:29] <sands> Does Discovery incur a larger footprint?
[20:29] <tdonohue> helix84: huge number? demo.dspace.org has something like <50 items,last I checked
[20:29] <mdiggory> 128MB?
[20:29] <mdiggory> thats never enough ;-)
[20:29] * helix84 has to remember to use the <sarcasm> tag
[20:29] <tdonohue> why not, mdiggory? It worked before on demo.dspace.org. Just wondering why we need to bump...but, I guess we do
[20:30] <helix84> 640 Kb should be enough for everybody. Now get off my lawn!
[20:30] <hpottinger> here's what we're running (engaging cut/paste device...)
[20:30] <hpottinger> JAVA_OPTS="-Xmx1024M -Xms768M"
[20:30] <hpottinger> JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=128M"
[20:30] <hpottinger> JAVA_OPTS="$JAVA_OPTS -XX:PermSize=32M"
[20:31] * robint (52292725@gateway/web/freenode/ip.82.41.39.37) has joined #duraspace
[20:31] <helix84> seriously, when I first started using Discovery, it did increase the memory requirements significantly. But after some leaks were fixed, at least it stopped increasing in time.
[20:31] <robint> hi all, sorry I'm late
[20:31] <tdonohue> Rebooted Tomcat on demo.dspace.org -- It's now running CATALINA_OPTS=-Xms1024M -Xmx1024M -XX:MaxPermSize=256M -Dfile.encoding=UTF-8
[20:31] <mdiggory> tdonohue: does the platform reload webapps without restarting tomcat?
[20:31] <tdonohue> Having "XX:MaxPermSize=128M" wasn't enough it seems
[20:31] <mdiggory> we'll see...
[20:31] <mhwood> I have one production instance starting PermGen at 64MB, limit 128, running in 67. It's not a high-volume site, though.
[20:31] <hpottinger> JAVA_OPTS="$JAVA_OPTS -XX:+UseParallelGC"
[20:32] <mdiggory> mhwood: is that using xmlui?
[20:32] <helix84> tdonohue: just curious, does this change automatically and dynamically? cat /proc/meminfo | grep MemTotal MemTotal: 1692604 kB
[20:32] <tdonohue> not sure what you are asking helix84
[20:32] <mhwood> Yes. Getting the version....
[20:33] <helix84> tdonohue: how does one increase the physical memory of the VM demo runs on?
[20:34] <tdonohue> oh, the VM we are using only has 1.7 GB of memory...we need to use a different VM altogether to increase that. We've always been fine on demo.dspace.org with just 1.7GB of memory in past
[20:34] <tdonohue> so, increasing memory = not easy
[20:34] <tdonohue> demo site is back
[20:35] <mdiggory> tdonohue: you using any swap space on that?
[20:35] <mhwood> That instance is running 1.7.2. (Time to upgrade.)
[20:35] <hpottinger> last time I did any reading on this was a few years back, but I do remember reading that using a different GC model helps with PermGen memory...
[20:36] <mhwood> ??? PermGen is supposed to be permanent.
[20:36] <helix84> mhwood: I'm glad to see I'm not the only one confused by that
[20:37] <hpottinger> man, my brain ain't what it used to be :-\
[20:37] <tdonohue> mdiggory -- you have access to demo server ;) Swap is the default for the Amazon server of this type (it's a "small" sized instance)... 'top' reports swap = 900MB
[20:37] <mhwood> Is demo running 32-bit or 64? Java 32-bit won't use more than 2GB anyway.
[20:37] * robint (52292725@gateway/web/freenode/ip.82.41.39.37) Quit (Ping timeout: 245 seconds)
[20:37] <helix84> 64
[20:38] <tdonohue> Ok, either folks are really testing things heavily, or we got ourselves a memory leak. We're about to hit another OOM
[20:38] <mdiggory> thanks tdonohue.. I've not logged onto it in about 2 years I think..
[20:38] * robint (52292725@gateway/web/freenode/ip.82.41.39.37) has joined #duraspace
[20:39] <hpottinger> aha, I blame this article for poisoning my brain: http://mark.koli.ch/2009/01/understanding-javas-perm-gen-maxpermsize-heap-space-etc.html
[20:39] * tdonohue is watching some logs.. hey, ryscher just logged in!
[20:40] * helix84 is just reminding that we should discuss the release today. I'll keep one eye on demo, I'm sure Tim will, too.
[20:41] <tdonohue> We may need to do some memory analysis on 3.0... There is not much activity right now in the logs, and we're using lots o' memory.
[20:41] * ryscher trying to verify that people can actually submit content on this thing
[20:42] * tdonohue is embarrassed that we hit an OOM error with a whole 11 items in the demo site.
[20:42] <mdiggory> I would like to chat about what happened with https://github.com/DSpace/DSpace/pull/91
[20:42] <kompewter> [ [DS-1272] Setting discovery to be the default search/browse engine by KevinVdV · Pull Request #91 · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pull/91
[20:42] <helix84> just one slightly relevant quote I thought I'd share: "Alpha does not mean 'finished'. Alpha does not even mean 'nearly finished'. Alpha means 'here's this thing that will probably eat your babies and burn down your house, we want you to tell us exactly where the teeth marks were on the babies and what the fire smelled like'."
[20:43] <mdiggory> that is such pleasant imagery
[20:44] <mdiggory> I was enjoying my lunch
[20:44] <tdonohue> So, we do have a free open source license for YourKit (Java profiler), if anyone would like a copy to help do some analysis of 3.0 with.
[20:44] * helix84 struggles to hold back even more sinister comments
[20:44] <mhwood> Got another Tomcat here running in about 433 MB PermGen out of 512, but it has two dozen DSpaces (various versions) and several other things in it.
[20:45] <mdiggory> we tried to release a beta a couple years ago, it confused everyone
[20:45] <tdonohue> I'd also be interested to hear what others see locally when you play around with 3.0 in terms of memory and PermGen esp.
[20:46] <hpottinger> YourKit is on my list of things to play with at some point...
[20:46] <mdiggory> Per https://github.com/DSpace/DSpace/pull/91
[20:46] <kompewter> [ [DS-1272] Setting discovery to be the default search/browse engine by KevinVdV · Pull Request #91 · DSpace/DSpace · GitHub ] - https://github.com/DSpace/DSpace/pull/91
[20:46] <helix84> haven't run into any problems on my testing server with 20k items and JAVA_OPTS="-Djava.awt.headless=true -Xmx768M -Xms768M -XX:MaxPermSize=128m"
[20:46] <mdiggory> we need some way to setup different configurations for test enviornment and production
[20:47] <helix84> helix84: that is with XMLUI, Discovery enabled
[20:47] <robint> mdiggory: any properties in particular ?
[20:47] <mdiggory> more specifically, we need a means to start Solr Embedded in discovery / statistics for the dspace-api testing.
[20:47] <tdonohue> helix84 -- huh, interesting. Wonder why we hit issues so quickly on demo then. would be worth looking at differences
[20:48] * tdonohue is gonna listen to mdiggory now
[20:48] <helix84> tdonohue: well i'm usually the only user at my testing server, that's the biggest difference I can think of
[20:48] <mdiggory> This means that we need to setup two different spring configurations for discovery / statistics
[20:49] <mdiggory> and write some changes to support Solr in different modes.
[20:49] <helix84> mdiggory: solr modes?
[20:49] <mdiggory> http://wiki.apache.org/solr/EmbeddedSolr
[20:49] <kompewter> [ EmbeddedSolr - Solr Wiki ] - http://wiki.apache.org/solr/EmbeddedSolr
[20:50] <mhwood> Sounds like integration testing. Will Failsafe give us any help?
[20:50] <robint> Embedded Solr = Lucene ? :)
[20:50] <mdiggory> sounds like you mean http://maven.apache.org/plugins/maven-failsafe-plugin/
[20:50] <kompewter> [ Introduction ] - http://maven.apache.org/plugins/maven-failsafe-plugin/
[20:51] <mdiggory> robint: haha.... yes in a way it does
[20:51] <mdiggory> think of it as solr without http transport
[20:52] <mdiggory> mhwood: may not need failsafe, this should be possible with JUnit
[20:52] * aschweer (~schweer@schweer.its.waikato.ac.nz) Quit (Quit: leaving)
[20:53] <mdiggory> the goal would be to alter Discovery and Statistics to have the Solrj configuration they use be injected
[20:53] <mhwood> Ok, sounds like we have options. If we need something fixed up for testing/unfixed after, we can use the pre-/post-integration-test phases.
[20:53] <mdiggory> in the case that we are in JUnit testing the spring config for solrj would be under src/test/resources
[20:54] <mdiggory> and in production it would reside in src/main/resources
[20:57] <mhwood> Sounds good. Anything else?
[20:57] <sands> Have to bow out a little early today. See you all. Next week I'd like to chat about the performance tests in the build failing. ;)
[20:57] <mdiggory> not really, it will need testing
[20:57] * ryscher (98033b4c@gateway/web/freenode/ip.152.3.59.76) Quit (Quit: Page closed)
[20:57] * sands (~sandsfish@18.189.25.238) Quit (Quit: sands)
[20:58] <hpottinger> so, is anyone currently profiling demo?
[20:59] <tdonohue> hpottinger -- no, not now. We do have YourKit installed on demo though
[21:00] <helix84> No, i wouldn't know how. But I notice that someone plays around with xmlworkflow and gets NPE
[21:00] <tdonohue> I'm watching the logs of demo.dspace.org...just noticed this fun error with the XMLWorkflow: https://jira.duraspace.org/browse/DS-1281
[21:00] <kompewter> [ [#DS-1281] XMLWorkflow throws NullPointerException on "Assign Roles" when not enabled - DuraSpace JIRA ] - https://jira.duraspace.org/browse/DS-1281
[21:00] <kompewter> [ https://jira.duraspace.org/browse/DS-1281 ] - [#DS-1281] XMLWorkflow throws NullPointerException on "Assign Roles" when not enabled - DuraSpace JIRA
[21:00] <tdonohue> (NOTE that XMLWorkflow is throwing that NPE when it's *disabled*)
[21:01] * qwebirc8422 (126518da@gateway/web/freenode/ip.18.101.24.218) Quit (Quit: Page closed)
[21:01] <tdonohue> How to do Profiling (via YourKit) with demo.dspace.org. It's documented here: https://wiki.duraspace.org/display/DSPACE/demo.dspace.org+Notes#demo.dspace.orgNotes-JavaProfilingusingYourKit
[21:01] <kompewter> [ demo.dspace.org Notes - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/demo.dspace.org+Notes#demo.dspace.orgNotes-JavaProfilingusingYourKit
[21:02] <KevinVdV> *will look into this*
[21:02] <KevinVdV> This == workflow bug
[21:03] <hpottinger> I am going to set up YourKit, how does one locate the key?
[21:03] <robint> hpottinger: Its in a recent email to the commit list
[21:04] <tdonohue> hpottinger -- one just needs to look for a msg sent to dspace-committers from robint dated Sept 21, 2012
[21:04] <helix84> on Sept 21
[21:04] <KevinVdV> Needs to run until next week !
[21:04] * KevinVdV (~KevinVdV@d54C154B1.access.telenet.be) Quit (Quit: Leaving)
[21:04] <hpottinger> found it, thx
[21:05] <tdonohue> (if a non-committer would like to help do 3.0 profiling via YourKit, honestly let us know. We can share our YourKit key assuming it is used to benefit DSpace open source development)
[21:06] <robint> Go to go, cheers all
[21:06] * robint (52292725@gateway/web/freenode/ip.82.41.39.37) Quit (Quit: Page closed)
[21:06] <tdonohue> Sorry that this meeting went a bit "off track" today. Didn't mean to spend so much time looking at demo site ;)
[21:07] <lyncode> i could help
[21:07] <tdonohue> Honestly though, I think we'd all make 3.0 better if we could each find a few hours here or there to do some testing & report results. Plus, volunteer to squash a few bugs, if you are able https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+DS+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+%223.0%22+ORDER+BY+priority+DESC
[21:07] <kompewter> [ Issue Navigator - DuraSpace JIRA ] - https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+DS+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+%223.0%22+ORDER+BY+priority+DESC
[21:08] <tdonohue> Next week we'll work to assign bugs that don't have a volunteer yet.
[21:08] <mhwood> About a dozen of those.
[21:08] <helix84> tdonohue: are you sure it's port 80? doesn't want to connect. Or maybe YourKit isn't running on demo site?
[21:09] <hpottinger> have installed YourKit, pointed it at port 80... YourKit complains there's nothing running on port 80
[21:09] <tdonohue> helix84 -- may want to first check that yourkit is running...it *should* be, but admittedly the last time I used it was the last release
[21:09] <tdonohue> lyncode -- are you volunteering to help profiling? or help in general?
[21:09] <helix84> tdonohue: just noting that our instructions don't say how to start yourkit
[21:09] <lyncode> i have some experience with profiling
[21:09] <helix84> +1 to lyncode
[21:10] <helix84> happy bug hunting
[21:11] <mhwood> Quick Q: do we want to document db.jndi for 3.0? (See discussion in dspace-devel)
[21:11] <tdonohue> lyncode. Ok, will send you our YourKit key shortly. hpottinger & helix84 -- give me a sec on yourkit -- will check if it's running
[21:11] <lyncode> ok
[21:12] <helix84> tdonohue: not that i'm too stupid to run yjp.sh, it just seems weird to me that it would listen on port 80. IOW, I wouldn't know how to check if it's already running.
[21:12] <tdonohue> helix84: it's possible that I had a typo there on the port... I'm not 100% trusting of my docs right now. looking into it
[21:13] <lyncode> by the way, i'll start using my own name = joao melo
[21:14] <helix84> lyncode: maybe it would be best to post a short email to the lists explaining what is lyncode and what the connection is
[21:14] <tdonohue> lyncode/joao - yep, I just sent it to your new email (jmelo) you've been using.
[21:14] <helix84> i know that some people didn't connect my name and my nick
[21:14] * lyncode is now known as joaomelo
[21:15] <tdonohue> yea...we were all like "who is this helix84 guy?" ;)
[21:15] <mdiggory> very mysterious
[21:15] <helix84> that was the intention. now the mafia knows!
[21:15] <hpottinger> I think it's interesting that we all still address you by your handle
[21:16] <joaomelo> ok
[21:16] <hpottinger> I've signed in to demo, and I can see that there's *something* running on port 80, but I can't find a PID for it
[21:17] <hpottinger> probably because I'm not root...
[21:21] <helix84> hpottinger: you're right about root. but that's apache on 80, obviously. I'm not sure how YourKit gets there, it probably somehow injects the JVM.
[21:21] <tdonohue> no -- it's Tomcat on port 80. No apache server is being used
[21:21] <joaomelo> by the way, translations? i've sent an email to sands but he didn't anwser me. I could provide 3 updated translations.
[21:21] <mhwood> I looked around a bit to see if there's a way to specify YourKit port, but nothing yet.
[21:22] <tdonohue> Yourkit gets into Tomcat via the CATALINA_OPTS
[21:22] <tdonohue> and it looks to be installed & running in Tomcat. I see the YourKit options when I look at the Tomcat process
[21:22] <joaomelo> s/anwser/answer/
[21:22] <kompewter> joaomelo meant to say: by the way, translations? i've sent an email to sands but he didn't answer me. I could provide 3 updated translations.
[21:22] <mhwood> Ah.
[21:23] <mhwood> Should we document db.jndi for 3.0?
[21:24] <helix84> joaomelo: about translations - you can just send them to me
[21:24] <helix84> helix84: actually, Jira would be best
[21:25] <tdonohue> mhwood: I honestly don't know what has changed there? But, I'd say "yes" since so few of us seem to understand it.
[21:25] <helix84> joaomelo: Claudia Jurgen dealt with them in the past and knows the tools to check if all necessary strings for a particular version are present
[21:26] <joaomelo> ok i'll also contact her
[21:26] <helix84> joaomelo: really, just send it to Jira, she'll notice
[21:27] <joaomelo> ok, need to go, see you all
[21:27] * joaomelo (~Utilizado@bl23-57-40.dsl.telepac.pt) Quit (Quit: Saindo)
[21:28] * tdonohue is waiting on yourkit to download. Need to reinstall on my local machine and see if I can get it connected to demo.dspace.org
[21:28] <hpottinger> there is supposed to be a log file created in ~/.yjp/log/PID.log
[21:29] <hpottinger> I'm assuming PID should equal the same PID as the running tomcat
[21:29] <mhwood> db.jndi: okay, I will write it up. If there are objections, it can be taken out again. There's not much to say.
[21:31] <hpottinger> ps aux | grep jsvc
[21:31] <hpottinger> I see two jsvc processes...
[21:32] <mhwood> or jps -v
[21:32] <tdonohue> hpottinger -- one of those jsvc process is the parent of the other... it gets started via 'root' but then switches to running as the 'dspace' user
[21:33] <mhwood> Got to run, thanks all.
[21:33] * mhwood (mwood@mhw.ulib.iupui.edu) has left #duraspace
[21:35] * hpottinger is learning...
[21:36] <helix84> hpottinger is updating instructions on https://wiki.duraspace.org/display/DSPACE/demo.dspace.org+Notes#demo.dspace.orgNotes-JavaProfilingusingYourKit
[21:36] <kompewter> [ demo.dspace.org Notes - DSpace - DuraSpace Wiki ] - https://wiki.duraspace.org/display/DSPACE/demo.dspace.org+Notes#demo.dspace.orgNotes-JavaProfilingusingYourKit
[21:36] <helix84> ;)
[21:37] <hpottinger> Confluence lies!
[21:37] * scottatm (~scottatm@adhcp218.evans.tamu.edu) has joined #duraspace
[21:37] <hpottinger> I've closed the page
[21:39] <hpottinger> OK, so, looking at the ~/.yjp/log/PID.log file, I see "11.0.8 - 1.211: Profiler agent is listening on port 10001"
[21:39] <helix84> noooo! we're damned to live our lives in ignorance! share your knowledge with us, oh, almighty wizard!
[21:40] <tdonohue> I was just looking at what ports are in use on demo.dspace.org, and I noticed *something* is using port 10001
[21:40] <tdonohue> Sounds like a Firewall needs opening...give me a sec
[21:41] <tdonohue> Why don't I see a ~/.yjp/log/PID.log file?
[21:41] <hpottinger> ${PID}
[21:41] <helix84> replace PID with a PID :)
[21:41] <tdonohue> oh..doh
[21:42] <helix84> kinda sucks if you don't know the PID, but there are always file dates
[21:42] <hpottinger> mhwood's suggestion of jps -v will get you the PID if you need it
[21:42] <tdonohue> yea, that is a bit of a pain. I thought it was literally named "PID.log" :)
[21:43] <hpottinger> nah, figured I'd leave the actual PID out of the chat logs
[21:43] <helix84> security through obscurity! heretic!
[21:43] <hpottinger> old habits
[21:44] <helix84> i'm knocking and knocking and noone is opening
[21:45] <hpottinger> "hello? demo.dspace.org? anyone home?"
[21:45] <tdonohue> argh...supposedly (according to Amazon), port 10001 is now open. But Yourkit still not working yet
[21:46] <hpottinger> any number of firewalls may be in the way...
[21:46] <tdonohue> yea...exactly. Try and find them all
[21:46] <helix84> tdonohue: what's the output of netstat -tulpn | grep 100001 ?
[21:46] <helix84> +- one zero
[21:47] <tdonohue> grep 10001 (three zeros) returns something
[21:47] <tdonohue> tcp6 0 0 :::10001 :::* LISTEN -
[21:47] <tdonohue> that's where I saw something is listening on 10001
[21:47] <helix84> tdonohue: sudo make me a sandwich
[21:47] <tdonohue> sudo do it yourself
[21:47] <helix84> ehm... sudo netstat -tulpn | grep 10001
[21:48] <helix84> but anyway, we progressed from "connection refused" to "connection timed out"
[21:49] <tdonohue> Oh yea...duh, this server has iptables too
[21:49] <tdonohue> So, I think we are through one firewall and hitting a second
[21:49] <helix84> multilayered security FTW!
[21:49] <helix84> are we black-hat or white-hat?
[21:51] <tdonohue> SUCCESS!
[21:52] <tdonohue> port 10001 now open for business
[21:52] <hpottinger> sweet!
[21:53] <helix84> okey dokey. what am I looking at?
[21:53] <tdonohue> ok..I gotta head out now. But, if someone could change that wiki page to say 10001, it'd be appreciated.
[21:53] <helix84> yessir
[21:54] <tdonohue> I can help more with YourKit stuff tomorrow perhaps (though admittedly I'm not the foremost expert either on it)
[21:54] * tdonohue (~tdonohue@c-67-177-108-221.hsd1.il.comcast.net) Quit (Read error: Connection reset by peer)
[21:55] <hpottinger> I totally need to set this up on my dev and production boxes
[21:56] <helix84> it's nice. I've been using Psi probe. Just deploy a webapp, set up username/password and head over to the web interface. No need to install anything.
[21:58] <helix84> just saying because this isn't open source :)
[21:58] <hpottinger> been using Psi probe (and formerly Lambda probe) for years, very helpful... I just like that this seems a lot closer to what we need to do actual profiling
[22:00] <helix84> yeah. should I switch CPU profiling to Tracing? maybe we'll see the call stack
[22:00] <helix84> and crash demo in the process ;)
[22:00] <hpottinger> I'm looking at memory right now
[22:00] <hpottinger> grabbing a snapshot for later
[22:01] <helix84> I'm wondering if it will show actual objects with their sizes
[22:01] <helix84> or class instances or whatever you call them in Java :)
[22:03] <helix84> should we make it interesting by running an index update or something?
[22:04] <helix84> I found the class list. You have to restrict display to one memory pool.
[22:05] <helix84> that's a lot of char[]s
[22:06] <hpottinger> looks like PermGen is using 113MB
[22:06] <hpottinger> rock solid
[22:08] <hpottinger> OK, will play with this some more tonight, gotta run, bye!
[22:08] <helix84> good night
[22:08] * hpottinger (~hpottinge@mu-162198.dhcp.missouri.edu) has left #duraspace
[22:08] * helix84 (a@195.113.97.174) has left #duraspace
[23:40] * scottatm (~scottatm@adhcp218.evans.tamu.edu) Quit (Quit: scottatm)
These logs were automatically created by DuraLogBot on irc.freenode.net using the Java IRC LogBot.