Re: [dspace-tech] google analytics and connection pool error

2017-03-21 Thread Jose Blanco 
A few months ago we went from http to https and I did not update the
GA site.  I just did that and I a have not seen any db connections
exhausted error.  I'm also working on GoogleRecorderEventListener.java
to see if I can put in a timeout to the request.  I can share that
code once I test it a bit.

-Jose

On Tue, Mar 21, 2017 at 2:41 PM, Jose Blanco  wrote:
> I'm reposting this.  I've turned off GA, but would like to turn it on
> again.  Is there any way to do that without having the instance go
> down.
>
> On Mon, Mar 20, 2017 at 5:03 PM, Jose Blanco  wrote:
>> I spoke to our sys admin person, and he does not think there were any
>> network connectivity issues yesterday.  Today, I tried to re-enable GA
>> and it failed at some point, but not soon after restarting tomcat.  In
>> contrast, what I was seeing yesterday was very predictable.  I would
>> start tomcat and within a few minutes all the connections were taken.
>> It was as if every connection taken got locked.  I did this quite a
>> few times ( starting and stopping tomcat, and always with the same
>> result ).  Is this what you typically see and is there any workaround?
>>
>> Thank you for your replies!
>> -Jose
>>
>> On Mon, Mar 20, 2017 at 4:35 AM, Claudia Jürgen
>>  wrote:
>>> Hi Jose,
>>>
>>> see https://jira.duraspace.org/browse/DS-2904
>>> there is a default configuration which will be used:
>>> https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-services/src/main/resources/config/dspace-defaults.cfg#L23
>>>
>>> Hope this helps
>>>
>>> Claudia Jürgen
>>>
>>>
>>>
>>> Am 20.03.2017 um 00:58 schrieb Jose Blanco:

 We were seeing something strange in our production site this Sunday.
 It seemed like calls to google analytics were locking db connections
 and eventually taking all of them.  I tried to comment this line:

 #xmlui.google.analytics.key=UA-12656561-1

 But this did not change anything.  I eventually change it to this

 xmlui.google.analytics.key=

 and then the db connection error ended.

 I would have thought that commenting it out would have been the way to
 do it.  Well in any case, the connection pool is now not being
 exhausted.  But I wonder why it happened this Sunday, and when I can
 re-enable it to get stats.  Perhaps there was a problem with Google
 Anyalitics this Sunday?

 Thanks,
 Jose

>>>
>>> --
>>> Claudia Juergen
>>> Eldorado
>>>
>>> Technische Universität Dortmund
>>> Universitätsbibliothek
>>> Vogelpothsweg 76
>>> 44227 Dortmund
>>>
>>> Tel.: +49 231-755 40 43
>>> Fax: +49 231-755 40 32
>>> claudia.juer...@tu-dortmund.de
>>> www.ub.tu-dortmund.de
>>>
>>> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist
>>> ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese
>>> E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und
>>> vernichten Sie diese Mail. Vielen Dank.
>>> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
>>> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
>>> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines
>>> solchen Schriftstücks per Telefax erfolgen.
>>>
>>> Important note: The information included in this e-mail is confidential. It
>>> is solely intended for the recipient. If you are not the intended recipient
>>> of this e-mail please contact the sender and delete this message. Thank you.
>>> Without prejudice of e-mail correspondence, our statements are only legally
>>> binding when they are made in the conventional written form (with personal
>>> signature) or when such documents are sent by fax.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "DSpace Technical Support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to dspace-tech+unsubscr...@googlegroups.com.
>>> To post to this group, send email to dspace-tech@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] google analytics and connection pool error

2017-03-21 Thread Jose Blanco 
I'm reposting this.  I've turned off GA, but would like to turn it on
again.  Is there any way to do that without having the instance go
down.

On Mon, Mar 20, 2017 at 5:03 PM, Jose Blanco  wrote:
> I spoke to our sys admin person, and he does not think there were any
> network connectivity issues yesterday.  Today, I tried to re-enable GA
> and it failed at some point, but not soon after restarting tomcat.  In
> contrast, what I was seeing yesterday was very predictable.  I would
> start tomcat and within a few minutes all the connections were taken.
> It was as if every connection taken got locked.  I did this quite a
> few times ( starting and stopping tomcat, and always with the same
> result ).  Is this what you typically see and is there any workaround?
>
> Thank you for your replies!
> -Jose
>
> On Mon, Mar 20, 2017 at 4:35 AM, Claudia Jürgen
>  wrote:
>> Hi Jose,
>>
>> see https://jira.duraspace.org/browse/DS-2904
>> there is a default configuration which will be used:
>> https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-services/src/main/resources/config/dspace-defaults.cfg#L23
>>
>> Hope this helps
>>
>> Claudia Jürgen
>>
>>
>>
>> Am 20.03.2017 um 00:58 schrieb Jose Blanco:
>>>
>>> We were seeing something strange in our production site this Sunday.
>>> It seemed like calls to google analytics were locking db connections
>>> and eventually taking all of them.  I tried to comment this line:
>>>
>>> #xmlui.google.analytics.key=UA-12656561-1
>>>
>>> But this did not change anything.  I eventually change it to this
>>>
>>> xmlui.google.analytics.key=
>>>
>>> and then the db connection error ended.
>>>
>>> I would have thought that commenting it out would have been the way to
>>> do it.  Well in any case, the connection pool is now not being
>>> exhausted.  But I wonder why it happened this Sunday, and when I can
>>> re-enable it to get stats.  Perhaps there was a problem with Google
>>> Anyalitics this Sunday?
>>>
>>> Thanks,
>>> Jose
>>>
>>
>> --
>> Claudia Juergen
>> Eldorado
>>
>> Technische Universität Dortmund
>> Universitätsbibliothek
>> Vogelpothsweg 76
>> 44227 Dortmund
>>
>> Tel.: +49 231-755 40 43
>> Fax: +49 231-755 40 32
>> claudia.juer...@tu-dortmund.de
>> www.ub.tu-dortmund.de
>>
>> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist
>> ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese
>> E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und
>> vernichten Sie diese Mail. Vielen Dank.
>> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
>> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
>> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines
>> solchen Schriftstücks per Telefax erfolgen.
>>
>> Important note: The information included in this e-mail is confidential. It
>> is solely intended for the recipient. If you are not the intended recipient
>> of this e-mail please contact the sender and delete this message. Thank you.
>> Without prejudice of e-mail correspondence, our statements are only legally
>> binding when they are made in the conventional written form (with personal
>> signature) or when such documents are sent by fax.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-tech+unsubscr...@googlegroups.com.
>> To post to this group, send email to dspace-tech@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] DSpace 6.0 error with Community List

2017-03-21 Thread George Kozak 
Hardy:
Just an update on my problem.  I did the tests you mentioned and they
didn't show any errors, but when I did the actual mvn build and ant update,
I ran into the same problem.  I stripped out all of my local modifications
(except for local.cfg) and recompiled again, and still the same problem
with the community-list command (everything else seems to work) and in the
"vanilla" version, the list of communities shows up OK on the home page, so
I know that there isn't a SQL problem.
I'm really stumped.  Could some setting in the local.cfg be causing this?
George Kozak
Cornell University

On Sat, Mar 18, 2017 at 11:20 AM, Hardy Pottinger  wrote:

> Hi, George, I went back to one of your earlier e-mails, and will include
> your info re: the Cocoon log here:
>
> > I did find the following error in the cocoon log:
> >
> > 2017-02-17 09:07:22,465 ERROR cocoon.handled  - Could not read resource
> cocoon://DRI/8/community-list
> >  at  - 
> > resource://aspects/Discovery/sitemap.xmap:223:40
>
> > at  - resource://aspects/Discovery/s
> itemap.xmap:79:47
> > at  - resource://aspects/Discovery/sitemap.xmap:67:28
>
> > at  - resource://aspects/Administrat
> ive/sitemap.xmap:1077:31
> > at  - 
> > resource://aspects/Administrative/sitemap.xmap:299:38
>
> > at  -
> resource://aspects/Administrative/sitemap.xmap:298:44
> > at  - resource://aspects/Administrat
> ive/sitemap.xmap:296:19
> > (continues)
>
> I've seen this behavior on occasion, I suspect that you may have a small
> error in one of your XML or XSLT theme files. You can either validate them
> each by hand:
>
> xmllint --noout name-of-file.xml
>
> works well. However, there is a built-in test in DSpace that will do this
> for you. Just run the tests [1]:
>
> mvn test -Dmaven.test.skip=false
>
> If there is an error in any of your XML or XSLT, the tests will find it.
>
> Hope that helps!
>
> --Hardy
>
> [1] https://wiki.duraspace.org/display/DSPACE/DSpace+Testing
>
> On Fri, Mar 17, 2017 at 6:04 PM, George Kozak  wrote:
>
>> Hi...
>> My Third Try is getting an answer :-)
>> So, I'm stuck.  I can't upgrade from DSpace 5.5 to DSpace 6.0 because
>> after doing the upgrade the command: http://my.dspace.url/community-list 
>> causes
>> an error.
>> I am using a modified Mirage2 theme, but the problem occurs in JSPUI and
>> even vanilla code and in any other theme.
>> Does anyone have any ideas for me?  I have tried 5 times to upgrade
>> (blowing away the upgrade and reverting back to 5.5 each time), and each
>> time no matter what I do, I get the same error after the upgrade (PS: the
>> community-list command works fine in 5.5).
>>
>> I guess if I don't hear from anyone, I will assume that this problem is
>> unique to Cornell's installation, and we can't upgrade.
>>
>> My previous emails contained the java stack traces, but here is a
>> snippet, if it helps anyone:
>> Cocoon error:
>> ERROR cocoon.handled  - Could not read resource
>> cocoon://DRI/8/community-list
>> at  - resource://aspects/Discovery/s
>> itemap.xmap:223:40
>>
>> Java error:
>>
>> Java stacktrace: java.lang.NullPointerException
>>  at 
>> org.dspace.content.DSpaceObjectServiceImpl.match(DSpaceObjectServiceImpl.java:427)
>>  at 
>> org.dspace.content.DSpaceObjectServiceImpl.getMetadata(DSpaceObjectServiceImpl.java:131)
>>  at 
>> org.dspace.content.DSpaceObjectServiceImpl.getMetadataFirstValue(DSpaceObjectServiceImpl.java:380)
>>  at 
>> org.dspace.content.CollectionServiceImpl.getMetadata(CollectionServiceImpl.java:395)
>>  at 
>> org.dspace.content.CollectionServiceImpl.getMetadata(CollectionServiceImpl.java:43)
>>  at 
>> org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:271)
>>  at 
>> org.dspace.app.xmlui.aspect.artifactbrowser.CommunityBrowser.getValidity(CommunityBrowser.java:160)
>>
>> --
>> ***
>> George Kozak
>> Digital Library Specialist
>> Cornell University Library - IT
>> 218 Olin Library
>> Cornell University
>> Ithaca, NY 14853
>> 607-255-8924 <(607)%20255-8924>
>> g...@cornell.edu
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-tech+unsubscr...@googlegroups.com.
>> To post to this group, send email to dspace-tech@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>


-- 
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
g...@cornell.edu

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To