[dspace-tech] Shibboleth Setup Trouble

2018-02-22 Thread librarysystems . test
I'm trying to get Shibboleth to work with a new DSpace 6 installation on 
Centos 7 running Apache 2.4.  I have both password and Shibboleth 
authentication enabled.  This gives me the opportunity to hover over the 
Shibboleth login link.  The link shows this URL:

https://rc.library.ourschool.edu/Shibboleth.sso/Login?target=https%3A%2F%2Frc.library.ourschool.edu%3A8080%2F%2Futa-ir%2Fshibboleth-login

or, with all the placeholders exchanged:

https://rc.library.ourschool.edu/Shibboleth.sso/Login?target=https://rc.library.ourschool.edu:8080//ourschool-ir/shibboleth-login

When I click the link, our standard Shibboleth login box appears.  I enter 
credentials and then I get the error message:

"*No peer endpoint available to which to send SAML response*" 

The fellow who maintains the Identity Provider says it logs the 
AssertionConsumerServiceURL as:

*https://rc.library.ourschool.edu:8080/Shibboleth.sso/SAML2/POST* 


Putting two and two together, it seems the IdP can't contact the SP because 
it's trying to hit port 8080.  Since I have Apache doing reverse proxy, the 
IdP needs to hit the base URL, but I can't find a way to change it.  Here 
are the relevant lines from the Apache main config:

# Send requests for / to /ourschool-ir
RedirectMatch ^/$ /ourschool-ir
# Redirect http to https
Redirect permanent /ourschool-ir 
https://rc.library.ourschool.edu/ourschool-ir


And from the Apache virtual server config:


   # Configure Shibboleth for "lazy" authentication
AuthType shibboleth
ShibUseHeaders on
Require shibboleth


# Suggested by DSpace docs
 ProxyPass !
 SetHandler shib

ProxyPass /ourschool-ir 
http://rc.library.ourschool.edu:8080/ourschool-ir
ProxyPassReverse /ourschool-ir 
http://rc.library.ourschool.edu:8080/ourschool-ir



Any clues greatly appreciated.

Glenn

-- 
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.


[dspace-tech] DSpace Shibboleth Setup Trouble

2018-02-22 Thread librarysystems . test
I'm trying to get Shibboleth to work with a new DSpace 6 installation on 
Centos 7 running Apache 2.4.  I have both password and Shibboleth 
authentication enabled.  This gives me the opportunity to hover over the 
Shibboleth login link.  The link shows this URL:

https://rc.library.ourschool.edu/Shibboleth.sso/Login?target=https%3A%2F%2Frc.library.ourschool.edu%3A8080%2F%2Futa-ir%2Fshibboleth-login

or, with all the placeholders exchanged:

https://rc.library.ourschool.edu/Shibboleth.sso/Login?target=https://rc.library.ourschool.edu:8080//ourschool-ir/shibboleth-login

When I click the link, our standard Shibboleth login box appears.  I enter 
credentials and then I get the error message:

"*No peer endpoint available to which to send SAML response*" 

The fellow who maintains the Identity Provider says it logs the 
AssertionConsumerServiceURL as:

*https://rc.library.ourschool.edu:8080/Shibboleth.sso/SAML2/POST* 


Putting two and two together, it seems the IdP can't contact the SP because 
it's trying to hit port 8080.  Since I have Apache doing reverse proxy, the 
IdP needs to hit the base URL, but I can't find a way to change it.  Here 
are the relevant lines from the Apache main config:

# Send requests for / to /ourschool-ir
RedirectMatch ^/$ /ourschool-ir
# Redirect http to https
Redirect permanent /ourschool-ir https://rc.library.ourschool.edu/uta-ir


And from the Apache virtual server config:


   # Configure Shibboleth for "lazy" authentication
AuthType shibboleth
ShibUseHeaders on
Require shibboleth


# Suggested by DSpace docs
 ProxyPass !
 SetHandler shib

ProxyPass /ourschool-ir 
http://rc.library.ourschool.edu:8080/ourschool-ir
ProxyPassReverse /ourschool-ir 
http://rc.library.ourschool.edu:8080/ourschool-ir



Any clues greatly appreciated.

Glenn

-- 
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.


[dspace-tech] Re: DSpace 6.2 with collection home page too slow to load if items have lots of bitsteams

2018-02-22 Thread Bill T
Here is my hibernate log for /community-list (page takes about 90 seconds 
to load);  We have about 200 communities, 1200 collections, and 64,000 
items.  Unlike Ying, we essentially have one original bitstream per item, 
primarily pdf files.  Redhat 7, Java 8, Tomcat 8.5, Postgresql 9.6.2;  32G 
Ram, 8 CPU  This setup worked well with previous versions up to and 
including 5.8

I'm not trying to pile on, but hopefully some additional info will be 
helpful!


2018-02-22 13:52:05,871 INFO 
 org.hibernate.engine.internal.StatisticalLoggingSessionEventListener @ 
Session Metrics {
372441 nanoseconds spent acquiring 1 JDBC connections;
0 nanoseconds spent releasing 0 JDBC connections;
233248 nanoseconds spent preparing 3 JDBC statements;
482887 nanoseconds spent executing 1 JDBC statements;
1985778 nanoseconds spent executing 2 JDBC batches;
3867293 nanoseconds spent performing 3 L2C puts;
0 nanoseconds spent performing 0 L2C hits;
0 nanoseconds spent performing 0 L2C misses;
29762475 nanoseconds spent executing 2 flushes (flushing a total of 2 
entities and 0 collections);
0 nanoseconds spent executing 0 partial-flushes (flushing a total of 0 
entities and 0 collections)
}

2018-02-22 13:52:05,873 INFO 
 org.hibernate.engine.internal.StatisticalLoggingSessionEventListener @ 
Session Metrics {
0 nanoseconds spent acquiring 0 JDBC connections;
0 nanoseconds spent releasing 0 JDBC connections;
0 nanoseconds spent preparing 0 JDBC statements;
0 nanoseconds spent executing 0 JDBC statements;
0 nanoseconds spent executing 0 JDBC batches;
0 nanoseconds spent performing 0 L2C puts;
0 nanoseconds spent performing 0 L2C hits;
0 nanoseconds spent performing 0 L2C misses;
0 nanoseconds spent executing 0 flushes (flushing a total of 0 entities 
and 0 collections);
0 nanoseconds spent executing 0 partial-flushes (flushing a total of 0 
entities and 0 collections)
}

2018-02-22 13:52:16,450 INFO 
 org.hibernate.engine.internal.StatisticalLoggingSessionEventListener @ 
Session Metrics {
440048 nanoseconds spent acquiring 1 JDBC connections;
0 nanoseconds spent releasing 0 JDBC connections;
273468 nanoseconds spent preparing 3 JDBC statements;
547508 nanoseconds spent executing 1 JDBC statements;
1702327 nanoseconds spent executing 2 JDBC batches;
3683682 nanoseconds spent performing 3 L2C puts;
0 nanoseconds spent performing 0 L2C hits;
0 nanoseconds spent performing 0 L2C misses;
27298233 nanoseconds spent executing 2 flushes (flushing a total of 2 
entities and 0 collections);
0 nanoseconds spent executing 0 partial-flushes (flushing a total of 0 
entities and 0 collections)
}

2018-02-22 13:52:16,452 INFO 
 org.hibernate.engine.internal.StatisticalLoggingSessionEventListener @ 
Session Metrics {
0 nanoseconds spent acquiring 0 JDBC connections;
0 nanoseconds spent releasing 0 JDBC connections;
0 nanoseconds spent preparing 0 JDBC statements;
0 nanoseconds spent executing 0 JDBC statements;
0 nanoseconds spent executing 0 JDBC batches;
0 nanoseconds spent performing 0 L2C puts;
0 nanoseconds spent performing 0 L2C hits;
0 nanoseconds spent performing 0 L2C misses;
0 nanoseconds spent executing 0 flushes (flushing a total of 0 entities 
and 0 collections);
0 nanoseconds spent executing 0 partial-flushes (flushing a total of 0 
entities and 0 collections)
}

2018-02-22 13:52:27,121 INFO 
 org.hibernate.engine.internal.StatisticalLoggingSessionEventListener @ 
Session Metrics {
429299 nanoseconds spent acquiring 1 JDBC connections;
0 nanoseconds spent releasing 0 JDBC connections;
236026 nanoseconds spent preparing 3 JDBC statements;
561023 nanoseconds spent executing 1 JDBC statements;
1029554 nanoseconds spent executing 2 JDBC batches;
3446462 nanoseconds spent performing 3 L2C puts;
0 nanoseconds spent performing 0 L2C hits;
0 nanoseconds spent performing 0 L2C misses;
23575938 nanoseconds spent executing 2 flushes (flushing a total of 2 
entities and 0 collections);
0 nanoseconds spent executing 0 partial-flushes (flushing a total of 0 
entities and 0 collections)
}

2018-02-22 13:52:27,123 INFO 
 org.hibernate.engine.internal.StatisticalLoggingSessionEventListener @ 
Session Metrics {
0 nanoseconds spent acquiring 0 JDBC connections;
0 nanoseconds spent releasing 0 JDBC connections;
0 nanoseconds spent preparing 0 JDBC statements;
0 nanoseconds spent executing 0 JDBC statements;
0 nanoseconds spent executing 0 JDBC batches;
0 nanoseconds spent performing 0 L2C puts;
0 nanoseconds spent performing 0 L2C hits;
0 nanoseconds spent performing 0 L2C misses;
0 nanoseconds spent executing 0 flushes (flushing a total of 0 entities 
and 0 collections);
0 nanoseconds spent executing 0 partial-flushes (flushing a total of 0 
entities and 0 collections)
}

2018-02-22 13:52:37,220 INFO 
 

Re: [dspace-tech] Icon next to authorities names

2018-02-22 Thread Alan Orth
Hello, Hugo.

This is just simple configuration of the Mirage 2 XMLUI theme using XSLT.
The metadata stored in dc.contributor.author includes a piece of text like
"[UNIFESP]" so you can use an XSL test like "if" or "choose" and apply
certain HTML to the the theme conditionally. Pretty easy!

Cheers,

On Mon, Feb 19, 2018 at 10:09 PM Bollini Andrea 
wrote:

> Hi Hugo,
> this looks like a local customisation. A similar feature that is likely
> what you have seen widely is available out of box in dspace-cris
> https://wiki.duraspace.org/display/DSPACECRIS/DSpace-CRIS+Home
> as example here
> http://ira.lib.polyu.edu.hk
>
> You can set eventually different icons (or no icon) for
> - current researchers (blue in the above example)
> - former researchers (gray above)
> - external researchers (no icon)
> it can be easily extended to different categories for instance role based
> (phd students, associate professors, etc.)
>
> Hope this help,
> Andrea
>
>
>
>
> Inviato da smartphone Samsung Galaxy.
>  Messaggio originale 
> Da: Hugo Carlos 
> Data: 19/02/18 19:24 (GMT+01:00)
> A: DSpace Technical Support 
> Oggetto: [dspace-tech] Icon next to authorities names
>
> Hello! Guys, I have seen that some repositories have an icon of the
> researcher's institution next to their name in the DSpace.
>
> How to achieve this? I saw several repositories have this interesting
> visual resource that facilitates identification of which author belongs to
> the institution, according to the example below. However, unfortunately I
> do not even know the name of this feature to search google correctly. Could
> anyone help?
>
> Example:
>
>
> 
>
>
>
>
>
>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> == in portuguese:
> 
> Olá! Pessoal, tenho visto que alguns repositórios possuem um ícone da
> instituição do pesquisador ao lado do seu nome no Dspace.
>
> Como conseguir isso? Vi vários repositórios terem esse interessante
> recurso visual que facilita identificação de qual o autor pertencente a
> instituição, conforme exemplo abaixo. Porem, infelizmente não sei nem ao
> menos o nome desse recurso para buscar no google corretamente. Alguém
> poderia ajudar?
>
> --
> 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
> 
> .
>
>
> --
> Questo messaggio e' stato analizzato con Libra ESVA ed e' risultato non
> infetto.
> Clicca qui per segnalarlo come spam.
> 
>
> --
> This message has been checked by Libra ESVA and is believed to be clean.
>
> --
> 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.
>
-- 

Alan Orth
alan.o...@gmail.com
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch

-- 
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.


[dspace-tech] Re: DSpace 6.2 with collection home page too slow to load if items have lots of bitsteams

2018-02-22 Thread Bill T
Thanks! -- I missed a couple of these.  Yes, really verbose output!  No 
problem, because I have yet to move this to production.
--Bill

On Thursday, February 22, 2018 at 12:50:33 PM UTC-6, Ying Jin wrote:
>
> Hi Bill,
>
> I put some extra lines in log4j.properties
>
> First, change this to DEBUG
>
> loglevel.other=DEBUG
>
> And add following:
>
> log4j.logger.org.hibernate=INFO, hb
>
> log4j.logger.org.hibernate.SQL=DEBUG
>
> log4j.logger.org.hibernate.type=TRACE
>
> log4j.logger.org.hibernate.hql.ast.AST=info
>
> log4j.logger.org.hibernate.tool.hbm2ddl=warn
>
> log4j.logger.org.hibernate.hql=debug
>
> log4j.logger.org.hibernate.cache=info
>
> log4j.logger.org.hibernate.jdbc=debug
>
> log4j.logger.org.hibernate.stat=debug
>
> Also, I added extra lines to hibernate.cfg.xml file:
>
> true
>
> debug
>
> true
>
> true
>
> true
>
> It generates huge log files, so be careful with using it. I only use this 
> on our development server and when I am not debugging, I turn them off.
>
> Hope this helps!
>
> Best,
> Ying
>
> On Thursday, February 22, 2018 at 10:40:09 AM UTC-6, Bill T wrote:
>>
>> Ying
>>
>> As you've noticed I'm having the same difficulties with DSpace 6x...  How 
>> did you get this log info?  I have show_sql = true in hibernate.cfg, but 
>> I'm not seeing the same info...
>> --Bill
>>
>> On Wednesday, February 21, 2018 at 4:02:06 PM UTC-6, Ying Jin wrote:
>>>
>>> Dear All,
>>>
>>> We are experiencing a performance issue with DSpace 6.2. Some of our 
>>> collections will time out/take several minutes to load. They are not big 
>>> collections, one of them only have 20 items, but each item contains 100+ 
>>> bitstreams (one PDF in Original bundle and 100+ of JP2 files in customized 
>>> MASTER bundle which are hidden from end users). The postgresql left so many 
>>> "idle in transaction" processes that will slow down the overall site. The 
>>> tomcat begin to take most of the CPU time too.
>>>
>>> We used to use 16G of memory for tomcat under v5.x, and the performance 
>>> has been ok. Now, even I increased to 64G(half of our server memory) under 
>>> 6.2, the performance didn't improve. 
>>>
>>> We are using Tomcat 8.0.13, Java 1.8, Redhat Linux 6.7, and XMLUI. We 
>>> have about 80+ communities, 280+ collections, 60,000+ items and 490,000 
>>> bitstreams. 
>>>
>>> To determine the cause of the slowness, I duplicate the same collection 
>>> with two copies. In one collection, I removed all MASTER files and leave 
>>> PDF only. The other collection, I zipped all MASTER files as one zip file 
>>> and uploaded with PDF. It turns out they all have no performance issues. 
>>> Seems like the number of bitstreams will affect the performance.
>>>
>>> After turning on the debugging, I got following information. It is too 
>>> big to upload the whole log so I just put hibernate stat here. 
>>>
>>> ==
>>> The collection has 100+ bitstreams in it
>>> ==
>>>
>>> 2018-02-07 00:43:17,724 DEBUG 
>>> org.hibernate.stat.internal.ConcurrentStatisticsImpl @ HHH000117: HQL: 
>>> null, time: 1ms, rows: 1
>>>
>>> 2018-02-07 00:43:17,882 INFO  
>>> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
>>> @ Session Metrics {
>>>
>>> 237746 nanoseconds spent acquiring 1 JDBC connections;
>>>
>>> 0 nanoseconds spent releasing 0 JDBC connections;
>>>
>>> 552698751 nanoseconds spent preparing 48017 JDBC statements;
>>>
>>> 12590561333 nanoseconds spent executing 48017 JDBC statements;
>>>
>>> 0 nanoseconds spent executing 0 JDBC batches;
>>>
>>> 929992 nanoseconds spent performing 52 L2C puts;
>>>
>>> 188492 nanoseconds spent performing 10 L2C hits;
>>>
>>> 1935100 nanoseconds spent performing 42 L2C misses;
>>>
>>> 133422494 nanoseconds spent executing 2 flushes (flushing a total 
>>> of 43868 entities and 58348 collections);
>>>
>>> 562373235433 nanoseconds spent executing 20136 partial-flushes 
>>> (flushing a total of 235915143 entities and 235915143 collections)
>>>
>>> }
>>>
>>> 2018-02-07 00:43:17,884 INFO  
>>> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
>>> @ Session Metrics {
>>>
>>> 0 nanoseconds spent acquiring 0 JDBC connections;
>>>
>>> 0 nanoseconds spent releasing 0 JDBC connections;
>>>
>>> 0 nanoseconds spent preparing 0 JDBC statements;
>>>
>>> 0 nanoseconds spent executing 0 JDBC statements;
>>>
>>> 0 nanoseconds spent executing 0 JDBC batches;
>>>
>>> 0 nanoseconds spent performing 0 L2C puts;
>>>
>>> 0 nanoseconds spent performing 0 L2C hits;
>>>
>>> 0 nanoseconds spent performing 0 L2C misses;
>>>
>>> 0 nanoseconds spent executing 0 flushes (flushing a total of 0 
>>> entities and 0 collections);
>>>
>>> 0 nanoseconds spent executing 0 partial-flushes (flushing a total 
>>> of 0 entities and 0 collections)
>>>
>>> }
>>>
>>> =
>>>
>>> The collection has PDF only
>>> =
>>>
>>> 2018-02-17 20:30:27,534 INFO  
>>> 

[dspace-tech] Re: DSpace 6.2 with collection home page too slow to load if items have lots of bitsteams

2018-02-22 Thread Ying Jin
Hi Bill,

I put some extra lines in log4j.properties

First, change this to DEBUG

loglevel.other=DEBUG

And add following:

log4j.logger.org.hibernate=INFO, hb

log4j.logger.org.hibernate.SQL=DEBUG

log4j.logger.org.hibernate.type=TRACE

log4j.logger.org.hibernate.hql.ast.AST=info

log4j.logger.org.hibernate.tool.hbm2ddl=warn

log4j.logger.org.hibernate.hql=debug

log4j.logger.org.hibernate.cache=info

log4j.logger.org.hibernate.jdbc=debug

log4j.logger.org.hibernate.stat=debug

Also, I added extra lines to hibernate.cfg.xml file:

true

debug

true

true

true

It generates huge log files, so be careful with using it. I only use this 
on our development server and when I am not debugging, I turn them off.

Hope this helps!

Best,
Ying

On Thursday, February 22, 2018 at 10:40:09 AM UTC-6, Bill T wrote:
>
> Ying
>
> As you've noticed I'm having the same difficulties with DSpace 6x...  How 
> did you get this log info?  I have show_sql = true in hibernate.cfg, but 
> I'm not seeing the same info...
> --Bill
>
> On Wednesday, February 21, 2018 at 4:02:06 PM UTC-6, Ying Jin wrote:
>>
>> Dear All,
>>
>> We are experiencing a performance issue with DSpace 6.2. Some of our 
>> collections will time out/take several minutes to load. They are not big 
>> collections, one of them only have 20 items, but each item contains 100+ 
>> bitstreams (one PDF in Original bundle and 100+ of JP2 files in customized 
>> MASTER bundle which are hidden from end users). The postgresql left so many 
>> "idle in transaction" processes that will slow down the overall site. The 
>> tomcat begin to take most of the CPU time too.
>>
>> We used to use 16G of memory for tomcat under v5.x, and the performance 
>> has been ok. Now, even I increased to 64G(half of our server memory) under 
>> 6.2, the performance didn't improve. 
>>
>> We are using Tomcat 8.0.13, Java 1.8, Redhat Linux 6.7, and XMLUI. We 
>> have about 80+ communities, 280+ collections, 60,000+ items and 490,000 
>> bitstreams. 
>>
>> To determine the cause of the slowness, I duplicate the same collection 
>> with two copies. In one collection, I removed all MASTER files and leave 
>> PDF only. The other collection, I zipped all MASTER files as one zip file 
>> and uploaded with PDF. It turns out they all have no performance issues. 
>> Seems like the number of bitstreams will affect the performance.
>>
>> After turning on the debugging, I got following information. It is too 
>> big to upload the whole log so I just put hibernate stat here. 
>>
>> ==
>> The collection has 100+ bitstreams in it
>> ==
>>
>> 2018-02-07 00:43:17,724 DEBUG 
>> org.hibernate.stat.internal.ConcurrentStatisticsImpl @ HHH000117: HQL: 
>> null, time: 1ms, rows: 1
>>
>> 2018-02-07 00:43:17,882 INFO  
>> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
>> @ Session Metrics {
>>
>> 237746 nanoseconds spent acquiring 1 JDBC connections;
>>
>> 0 nanoseconds spent releasing 0 JDBC connections;
>>
>> 552698751 nanoseconds spent preparing 48017 JDBC statements;
>>
>> 12590561333 nanoseconds spent executing 48017 JDBC statements;
>>
>> 0 nanoseconds spent executing 0 JDBC batches;
>>
>> 929992 nanoseconds spent performing 52 L2C puts;
>>
>> 188492 nanoseconds spent performing 10 L2C hits;
>>
>> 1935100 nanoseconds spent performing 42 L2C misses;
>>
>> 133422494 nanoseconds spent executing 2 flushes (flushing a total of 
>> 43868 entities and 58348 collections);
>>
>> 562373235433 nanoseconds spent executing 20136 partial-flushes 
>> (flushing a total of 235915143 entities and 235915143 collections)
>>
>> }
>>
>> 2018-02-07 00:43:17,884 INFO  
>> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
>> @ Session Metrics {
>>
>> 0 nanoseconds spent acquiring 0 JDBC connections;
>>
>> 0 nanoseconds spent releasing 0 JDBC connections;
>>
>> 0 nanoseconds spent preparing 0 JDBC statements;
>>
>> 0 nanoseconds spent executing 0 JDBC statements;
>>
>> 0 nanoseconds spent executing 0 JDBC batches;
>>
>> 0 nanoseconds spent performing 0 L2C puts;
>>
>> 0 nanoseconds spent performing 0 L2C hits;
>>
>> 0 nanoseconds spent performing 0 L2C misses;
>>
>> 0 nanoseconds spent executing 0 flushes (flushing a total of 0 
>> entities and 0 collections);
>>
>> 0 nanoseconds spent executing 0 partial-flushes (flushing a total of 
>> 0 entities and 0 collections)
>>
>> }
>>
>> =
>>
>> The collection has PDF only
>> =
>>
>> 2018-02-17 20:30:27,534 INFO  
>> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
>> @ Session Metrics {
>>
>> 341778 nanoseconds spent acquiring 1 JDBC connections;
>>
>> 0 nanoseconds spent releasing 0 JDBC connections;
>>
>> 15974134 nanoseconds spent preparing 1189 JDBC statements;
>>
>> 271327429 nanoseconds spent executing 1189 JDBC statements;
>>
>> 0 nanoseconds spent executing 0 JDBC batches;
>>

[dspace-tech] Re: DSpace 6.2 with collection home page too slow to load if items have lots of bitsteams

2018-02-22 Thread Bill T
Ying

As you've noticed I'm having the same difficulties with DSpace 6x...  How 
did you get this log info?  I have show_sql = true in hibernate.cfg, but 
I'm not seeing the same info...
--Bill

On Wednesday, February 21, 2018 at 4:02:06 PM UTC-6, Ying Jin wrote:
>
> Dear All,
>
> We are experiencing a performance issue with DSpace 6.2. Some of our 
> collections will time out/take several minutes to load. They are not big 
> collections, one of them only have 20 items, but each item contains 100+ 
> bitstreams (one PDF in Original bundle and 100+ of JP2 files in customized 
> MASTER bundle which are hidden from end users). The postgresql left so many 
> "idle in transaction" processes that will slow down the overall site. The 
> tomcat begin to take most of the CPU time too.
>
> We used to use 16G of memory for tomcat under v5.x, and the performance 
> has been ok. Now, even I increased to 64G(half of our server memory) under 
> 6.2, the performance didn't improve. 
>
> We are using Tomcat 8.0.13, Java 1.8, Redhat Linux 6.7, and XMLUI. We have 
> about 80+ communities, 280+ collections, 60,000+ items and 490,000 
> bitstreams. 
>
> To determine the cause of the slowness, I duplicate the same collection 
> with two copies. In one collection, I removed all MASTER files and leave 
> PDF only. The other collection, I zipped all MASTER files as one zip file 
> and uploaded with PDF. It turns out they all have no performance issues. 
> Seems like the number of bitstreams will affect the performance.
>
> After turning on the debugging, I got following information. It is too big 
> to upload the whole log so I just put hibernate stat here. 
>
> ==
> The collection has 100+ bitstreams in it
> ==
>
> 2018-02-07 00:43:17,724 DEBUG 
> org.hibernate.stat.internal.ConcurrentStatisticsImpl @ HHH000117: HQL: 
> null, time: 1ms, rows: 1
>
> 2018-02-07 00:43:17,882 INFO  
> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
> @ Session Metrics {
>
> 237746 nanoseconds spent acquiring 1 JDBC connections;
>
> 0 nanoseconds spent releasing 0 JDBC connections;
>
> 552698751 nanoseconds spent preparing 48017 JDBC statements;
>
> 12590561333 nanoseconds spent executing 48017 JDBC statements;
>
> 0 nanoseconds spent executing 0 JDBC batches;
>
> 929992 nanoseconds spent performing 52 L2C puts;
>
> 188492 nanoseconds spent performing 10 L2C hits;
>
> 1935100 nanoseconds spent performing 42 L2C misses;
>
> 133422494 nanoseconds spent executing 2 flushes (flushing a total of 
> 43868 entities and 58348 collections);
>
> 562373235433 nanoseconds spent executing 20136 partial-flushes 
> (flushing a total of 235915143 entities and 235915143 collections)
>
> }
>
> 2018-02-07 00:43:17,884 INFO  
> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
> @ Session Metrics {
>
> 0 nanoseconds spent acquiring 0 JDBC connections;
>
> 0 nanoseconds spent releasing 0 JDBC connections;
>
> 0 nanoseconds spent preparing 0 JDBC statements;
>
> 0 nanoseconds spent executing 0 JDBC statements;
>
> 0 nanoseconds spent executing 0 JDBC batches;
>
> 0 nanoseconds spent performing 0 L2C puts;
>
> 0 nanoseconds spent performing 0 L2C hits;
>
> 0 nanoseconds spent performing 0 L2C misses;
>
> 0 nanoseconds spent executing 0 flushes (flushing a total of 0 
> entities and 0 collections);
>
> 0 nanoseconds spent executing 0 partial-flushes (flushing a total of 
> 0 entities and 0 collections)
>
> }
>
> =
>
> The collection has PDF only
> =
>
> 2018-02-17 20:30:27,534 INFO  
> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
> @ Session Metrics {
>
> 341778 nanoseconds spent acquiring 1 JDBC connections;
>
> 0 nanoseconds spent releasing 0 JDBC connections;
>
> 15974134 nanoseconds spent preparing 1189 JDBC statements;
>
> 271327429 nanoseconds spent executing 1189 JDBC statements;
>
> 0 nanoseconds spent executing 0 JDBC batches;
>
> 717412 nanoseconds spent performing 45 L2C puts;
>
> 3906724 nanoseconds spent performing 247 L2C hits;
>
> 2081066 nanoseconds spent performing 855 L2C misses;
>
> 6829028 nanoseconds spent executing 2 flushes (flushing a total of 
> 3916 entities and 5072 collections);
>
> 578786157 nanoseconds spent executing 261 partial-flushes (flushing a 
> total of 345641 entities and 345641 collections)
>
> }
>
> .
>
>
> 2018-02-17 20:30:27,536 INFO  
> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
> @ Session Metrics {
>
> 120941 nanoseconds spent acquiring 1 JDBC connections;
>
> 0 nanoseconds spent releasing 0 JDBC connections;
>
> 19210 nanoseconds spent preparing 1 JDBC statements;
>
> 190340 nanoseconds spent executing 1 JDBC statements;
>
> 0 nanoseconds spent executing 0 JDBC batches;
>
> 0 nanoseconds spent performing 0 L2C puts;
>
> 0 nanoseconds spent performing 0 L2C hits;
>
> 

[dspace-tech] Re: DSpace 6.2 with collection home page too slow to load if items have lots of bitsteams

2018-02-22 Thread Ying Jin
Hi Kim,

We are using XMLUI and the trigger is trying to open the collection home 
page. I think search will suffer too but I didn't test on it. Opening the 
individual item with lots of bitstreams(100+) is kind of slow too, but not 
as bad (it might because we display 20 recent submission items x 100+/item 
= 2000+ bitstreams to load a collection?).

Please let me know if you need any test collections or the full log that I 
may share through google drive. Thanks so much for working on it!

Best,
Ying

On Wednesday, February 21, 2018 at 4:22:47 PM UTC-6, Kim Shepherd wrote:
>
> Hi Ying,
>
> Just to help properly reproduce your conditions, could you confirm what 
> "load the collection" refers to and which UI you're using? Which specific 
> page(s) will trigger the load times? Is it the collection home page, a 
> search/browse of (or scoped to) the collection, etc? Administrative pages? 
> Do you also see slow load times on item pages of the items with many 
> bitstreams
>
> Cheers
>
> Kim
>
> On Thursday, February 22, 2018 at 11:02:06 AM UTC+13, Ying Jin wrote:
>>
>> Dear All,
>>
>> We are experiencing a performance issue with DSpace 6.2. Some of our 
>> collections will time out/take several minutes to load. They are not big 
>> collections, one of them only have 20 items, but each item contains 100+ 
>> bitstreams (one PDF in Original bundle and 100+ of JP2 files in customized 
>> MASTER bundle which are hidden from end users). The postgresql left so many 
>> "idle in transaction" processes that will slow down the overall site. The 
>> tomcat begin to take most of the CPU time too.
>>
>> We used to use 16G of memory for tomcat under v5.x, and the performance 
>> has been ok. Now, even I increased to 64G(half of our server memory) under 
>> 6.2, the performance didn't improve. 
>>
>> We are using Tomcat 8.0.13, Java 1.8, Redhat Linux 6.7, and XMLUI. We 
>> have about 80+ communities, 280+ collections, 60,000+ items and 490,000 
>> bitstreams. 
>>
>> To determine the cause of the slowness, I duplicate the same collection 
>> with two copies. In one collection, I removed all MASTER files and leave 
>> PDF only. The other collection, I zipped all MASTER files as one zip file 
>> and uploaded with PDF. It turns out they all have no performance issues. 
>> Seems like the number of bitstreams will affect the performance.
>>
>> After turning on the debugging, I got following information. It is too 
>> big to upload the whole log so I just put hibernate stat here. 
>>
>> ==
>> The collection has 100+ bitstreams in it
>> ==
>>
>> 2018-02-07 00:43:17,724 DEBUG 
>> org.hibernate.stat.internal.ConcurrentStatisticsImpl @ HHH000117: HQL: 
>> null, time: 1ms, rows: 1
>>
>> 2018-02-07 00:43:17,882 INFO  
>> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
>> @ Session Metrics {
>>
>> 237746 nanoseconds spent acquiring 1 JDBC connections;
>>
>> 0 nanoseconds spent releasing 0 JDBC connections;
>>
>> 552698751 nanoseconds spent preparing 48017 JDBC statements;
>>
>> 12590561333 nanoseconds spent executing 48017 JDBC statements;
>>
>> 0 nanoseconds spent executing 0 JDBC batches;
>>
>> 929992 nanoseconds spent performing 52 L2C puts;
>>
>> 188492 nanoseconds spent performing 10 L2C hits;
>>
>> 1935100 nanoseconds spent performing 42 L2C misses;
>>
>> 133422494 nanoseconds spent executing 2 flushes (flushing a total of 
>> 43868 entities and 58348 collections);
>>
>> 562373235433 nanoseconds spent executing 20136 partial-flushes 
>> (flushing a total of 235915143 entities and 235915143 collections)
>>
>> }
>>
>> 2018-02-07 00:43:17,884 INFO  
>> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
>> @ Session Metrics {
>>
>> 0 nanoseconds spent acquiring 0 JDBC connections;
>>
>> 0 nanoseconds spent releasing 0 JDBC connections;
>>
>> 0 nanoseconds spent preparing 0 JDBC statements;
>>
>> 0 nanoseconds spent executing 0 JDBC statements;
>>
>> 0 nanoseconds spent executing 0 JDBC batches;
>>
>> 0 nanoseconds spent performing 0 L2C puts;
>>
>> 0 nanoseconds spent performing 0 L2C hits;
>>
>> 0 nanoseconds spent performing 0 L2C misses;
>>
>> 0 nanoseconds spent executing 0 flushes (flushing a total of 0 
>> entities and 0 collections);
>>
>> 0 nanoseconds spent executing 0 partial-flushes (flushing a total of 
>> 0 entities and 0 collections)
>>
>> }
>>
>> =
>>
>> The collection has PDF only
>> =
>>
>> 2018-02-17 20:30:27,534 INFO  
>> org.hibernate.engine.internal.StatisticalLoggingSessionEventListener 
>> @ Session Metrics {
>>
>> 341778 nanoseconds spent acquiring 1 JDBC connections;
>>
>> 0 nanoseconds spent releasing 0 JDBC connections;
>>
>> 15974134 nanoseconds spent preparing 1189 JDBC statements;
>>
>> 271327429 nanoseconds spent executing 1189 JDBC statements;
>>
>> 0 nanoseconds spent executing 0 JDBC batches;
>>
>> 717412 nanoseconds spent performing 45 L2C 

[dspace-tech] Error OAI result ListSets

2018-02-22 Thread Pedro Pineda
Hi, i have problem in OAI, when I try to access OAI -> Default Context -> 
List Sets its shows me NullPointerException, to which this could be due? 
someone could help me with this error.

-- 
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.


[dspace-tech] Handle Setup

2018-02-22 Thread Iltifat Ibrahimov
Hello Everyone,

I've configured handle server recently and updated existing prefixes. All
items' prefixes have changed but when click on URI:
http://hdl.handle.net/20.500.12181/22 causes following Tomcat error. Have
you ever experienced such kind of error?

HTTP Status 404 - /handle/20.500.12181/22

*type* Status report

*message* */handle/20.500.12181/22*

*description* *The requested resource is not available.*
--
Apache Tomcat/8.0.36

Thanks in advance,
Iltifat

-- 
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.