Page 2 of 4

Posted: Thu Mar 29, 2007 7:53 am
by melearp
Spoke too soon. The 404's are back this morning as at 07:53.

Posted: Thu Mar 29, 2007 10:18 am
by Bawbagg
Alan,

Do you still have a contact at RadioTimes?? I used to swap mail with Spencer, but he left sometime last year - I found out by an Auto Reply.

I did try mailing the contact on his Auto Reply, but I didn't get an answer.

This might be a good time to try to contact them to understand if they have any plans to support the xmltv service.

Cheers,

BB

Posted: Thu Mar 29, 2007 11:46 am
by alanbirtles
i just tried spencer and got the auto reply, i will contact those listed there

Posted: Thu Mar 29, 2007 12:03 pm
by Bawbagg
I already sent a mail to Chris this morning - he's out the office until tomorrow. Let's hope he's kicking ass at the web developers ;-)).

Here's what I sent:

Hello Chris,

I've seen that Radiotimes.com has come live again after a site revision.

However, you may know that a number of PVR users (primarily SageTV, MythTV, Windows MCE and Topfield 5800) have been using the feeds provided by Radiotimes.com at http://xmltv.radiotimes.com/xmltv/*.*

Since the site update, these feeds are no longer accessible.

Can you let me know if there are any plans to either start the free feeds again, or to switch to a subscription service??

Many thanks,

Posted: Thu Mar 29, 2007 12:06 pm
by rickgillyon
http://xmltv.radiotimes.com/ just shows a completely empty folder. I even tried logging in (the site now asks for a username/password) but still can't see any xmltv data.

Posted: Thu Mar 29, 2007 12:13 pm
by Bawbagg
I saw the empty folder there too..... but I guess it doesn't mean much.

Posted: Thu Mar 29, 2007 12:18 pm
by rickgillyon
Certainly doesn't help much! :)

Posted: Thu Mar 29, 2007 5:38 pm
by alanbirtles
Hi Alan,

Thanks for your email - we appreciate your concern. As you are no doubt aware, we are having a few issues related to the new-look site, and these are our top priority at present. We will look at restoring the XMLTV service as soon as we can, and will keep you updated.

Thanks,

Simon

Posted: Thu Mar 29, 2007 5:45 pm
by rickgillyon
Aaaagh! Great news, looks like it will be restored, but we need some ideas on the scale of "as soon as we can". Will it be within the 10 days we have left in our EPGs, or will it be 3 months?

I realise we don't want to bug them too much though...

Posted: Thu Mar 29, 2007 6:13 pm
by melearp
Well I just ran a grab and success. It looks pretty well back to normal.

Posted: Thu Mar 29, 2007 6:28 pm
by rickgillyon
Yay! :lol:

Posted: Thu Mar 29, 2007 6:48 pm
by 7andY
I've just tried, and no go still...


<EDIT> and tried again, and got it!

Posted: Thu Mar 29, 2007 6:57 pm
by rickgillyon
I wouldn't expect reliability for a while...

Posted: Thu Mar 29, 2007 8:08 pm
by rickgillyon
Alan, if you do have any email dialogue with them, can you ask where the episode numbers have gone? I liked them... Thanks!

Posted: Sat Mar 31, 2007 10:03 am
by melearp
RT are still in a right old mess. I just tried to look at the main web site and got this:

Code: Select all

500 
Could not invoke Java compiler, please make sure jikesw is in /usr/local/jrun4/bin or put a JDK bin directory in your path.


jrunx.compiler.JavaCompiler$NoCompilerFoundException: Could not invoke Java compiler, please make sure jikesw is in /usr/local/jrun4/bin or put a JDK bin directory in your path.
	at jrunx.compiler.JavaCompiler.outProcessCompile(JavaCompiler.java:467)
	at jrunx.compiler.JavaCompiler.compile(JavaCompiler.java:132)
	at jrunx.compiler.JavaCompiler.compile(JavaCompiler.java:100)
	at jrun.jsp.Translator.compilePage(Translator.java:176)
	at jrun.jsp.Translator.translate(Translator.java:254)
	at jrun.jsp.Translator.translate(Translator.java:101)
	at jrun.jsp.JSPEngine.translateJSP(JSPEngine.java:693)
	at jrun.jsp.JSPServlet.translate(JSPServlet.java:125)
	at jrun.jsp.JSPServlet.service(JSPServlet.java:113)
	at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
	at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
	at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:259)
	at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541)
	at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:204)
	at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
	at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
	at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
	at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

At least the grab worked OK last night.