The handle you requested --
*10718.test/3075*
-- cannot be found.
--
Carolyn Brown Ray
Web Architect
Office of Information Technology
Muhlenberg College
484-664-3646
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code
2641
> dsdfsdf
> Ncat: Connection refused.
>
> So the comms to your server are not working. Do you have a firewall
> blocking them? Port 2641 must be open on both TCP and UDP.
>
> Kind Regards.
>
> Shaun.
> On 2019/10/28 18:52, Carolyn Brown wrote:
>
> Tot
Move the files to the new server and change the asset store value in local.cfg
and you should be set.
Sent from my iPhone
> On Nov 25, 2019, at 7:01 AM, Joelton Silva R. Correia
> wrote:
>
>
> Thanks everyone, but I found doing research would be using the "assetstore"
> folder.
>
> Em se
from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/5b196f92-d3fb-4e97-bae0-c31411abbd87%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/5b196f92-d3fb-4e97-bae0-c3
l.java:689)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.util.NoSuchElementException: Timeout waiting for idle object
at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:958)
at
org.apache.commons.dbcp.PoolingDataSource.getCon
ted), but this used to lock up my databases as well
> as it did not release the pool connections and did not re-use them.
>
> Kind Regards.
>
> Shaun.
> On 2019/12/11 20:38, Carolyn Brown wrote:
>
> All of a sudden we are constantly getting this connection error, and the
>
?
Regards,
--
Carolyn Brown Ray
Web Architect
Office of Information Technology
Muhlenberg College
484-664-3646
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are
ote:
> Hi,
>
> Verify the out Dspace log in [dspace]/log/dspace.log
>
> Em qui., 20 de fev. de 2020 às 14:35, Carolyn Brown <
> carolynbr...@muhlenberg.edu> escreveu:
>
>> ANY IDEAS?
>>
>> *Steps taken:*
>> Upgrade from DSpace 3.3 to 6.3.
>> Dat
t; would be logged later on in the dspace.log file.
>
> If somehow there are no errors in the dspace.log file, also check your Tomcat
> & database logs to see if any errors are appearing there.
>
> Tim
>
> From: dspace-tech@googlegroups.com on behalf
> of Carolyn B
eve/d1c10669-f93f-416c-bdfb-bc183ca09fdd HTTP/1.1" 200
42311
192.104.181.41 - - [05/Mar/2020:12:14:30 -0500] "POST /solr/search/select
HTTP/1.1" 500 5774
192.104.181.41 - - [05/Mar/2020:12:14:30 -0500] "POST /solr/search/select
HTTP/1.1" 500 5774
192.104.181.41 - - [05/Mar
;utm_campaign=braml>
> - Custom DSpace Services
> <https://www.atmire.com/custom-dspace&utm_source=emailfooter&utm_medium=email&utm_campaign=braml>
>
>
> On Thu, 5 Mar 2020 at 22:12, Carolyn Brown
> wrote:
>
>> Had to turn my attention to another pro
11 matches
Mail list logo
