Menu
▾
▴
#173 epidoc schema timeout in Oxygen
Currently we receive an error message when validating against the epidoc-schema:
I/O error reported by XML parser processing http://www.stoa.org/epidoc/schema/9.0/tei-epidoc.rng: Read timed out (http://www.stoa.org/epidoc/schema/9.0/tei-epidoc.rng)
Maybe the server is down and/or should be restarted?
Related
Hi Thomas, I nudged UKY and the Stoa seems to be back online. Is the problem fixed for you now? (If so, please close the ticket. Thanks!)
Dear Gabby,
thanks for the quick fix. Max and I will give a very short introduction to EpiDoc in Graz next week and now we know that we can present the benefits of validation to our public.
Closing is difficult couldn’t find any button (some of my younger colleagues which better eyes and brighter minds looked too) … reason could be that I forget to declare me owner when creating the ticket?
Any advice?
bye
Thomas
Ah, that may be some Sourceforge weirdness about having to be a ticket admin to close a ticket. I'll close it, and look into the background in the meantime.
Re presenting: I would suggest you keep a local copy of the schema handy, just in case the online version goes down again. It's also much faster validating to a local copy, at least in Oxygen, in my experience…
Cheers,
Gabby
==
Dr Gabriel BODARD
Reader in Digital Classics
Institute of Classical Studies
University of London
Senate House
Malet Street
London WC1E 7HU
E: Gabriel.bodard@sas.ac.uk
T: +44 (0)20 78628752
http://digitalclassicist.org/
From: Thomas Kollatz thomaskollatz@users.sourceforge.net
Sent: 04 July 2018 15:00
To: [epidoc:bugs]
Subject: [epidoc:bugs] #173 epidoc schema timeout in Oxygen
Dear Gabby,
thanks for the quick fix. Max and I will give a very short introduction to EpiDoc in Graz next week and now we know that we can present the benefits of validation to our public.
Closing is difficult couldn’t find any button (some of my younger colleagues which better eyes and brighter minds looked too) … reason could be that I forget to declare me owner when creating the ticket?
Any advice?
bye
Thomas
** [bugs:#173] epidoc schema timeout in Oxygen**
Status: unread
Group: 9.1
Created: Wed Jul 04, 2018 12:09 PM UTC by Thomas Kollatz
Last Updated: Wed Jul 04, 2018 01:47 PM UTC
Owner: nobody
Currently we receive an error message when validating against the epidoc-schema:
I/O error reported by XML parser processing http://www.stoa.org/epidoc/schema/9.0/tei-epidoc.rng: Read timed out (http://www.stoa.org/epidoc/schema/9.0/tei-epidoc.rng)
Maybe the server is down and/or should be restarted?
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/epidoc/bugs/173/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
Report Bugs:
#173Down again
ro.sync.basic.net.http.HttpException: Connect to www.stoa.org:80 [www.stoa.org/128.163.188.101] failed: connect timed out (http://www.stoa.org/epidoc/schema/9.0/tei-epidoc.rng)
at ro.sync.net.protocol.http.b.d.h(Unknown Source)
at ro.sync.net.protocol.http.abstraction.n.p(Unknown Source)
at ro.sync.net.protocol.http.abstraction.n.d(Unknown Source)
at ro.sync.net.protocol.http.WebdavHttpURLConnection.g(Unknown Source)
at ro.sync.net.protocol.http.WebdavHttpURLConnection.getInputStream(Unknown Source)
at ro.sync.net.protocol.http.WebdavHttpURLConnection.s(Unknown Source)
at ro.sync.net.protocol.http.WebdavHttpURLConnection.getHeaderField(Unknown Source)
at ro.sync.exml.editor.yb.l(Unknown Source)
at ro.sync.exml.editor.yd.sgk(Unknown Source)
at ro.sync.exml.editor.yd.open(Unknown Source)
at ro.sync.exml.k.u.c(Unknown Source)
at ro.sync.exml.k.u.d(Unknown Source)
at ro.sync.exml.k.u.e(Unknown Source)
at ro.sync.exml.k.d.ljl(Unknown Source)
at ro.sync.exml.k.d$2.actionPerformed(Unknown Source)
at ro.sync.ui.application.action.x$_b$1.cud(Unknown Source)
at ro.sync.ui.application.nb.run(Unknown Source)
Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to www.stoa.org:80 [www.stoa.org/128.163.188.101] failed: connect timed out
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:143)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
... 17 more
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:386)
at java.net.Socket.connect(Socket.java:589)
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
... 25 more