Hi David,

Even though it took us a while, I'm happy to report that this issue is now
fixed:
https://github.com/restlet/restlet-framework-java/issues/437

Best regards,
Jerome
--
http://www.restlet.com
http://twitter.com/#!/jlouvel


-----Message d'origine-----
De : Crogdor [mailto:da...@davidfuchs.ca] 
Envoyé : mardi 17 mai 2011 13:54
À : discuss@restlet.tigris.org
Objet : RestletFrameworkServlet - HTTP 500 on first request.

Hello - I'm running Restlet 2.1-M4 (JEE edition) with the Spring extensions
on Tomcat 7/JRE6.  I'm using Spring 3.0.5-RELEASE.  I've also reproduced
these results with Restlet 2.0.7 and Spring 3.0.1-RELEASE.

I'm receiving an HTTP 500 error error the first time I call my Restlet. 
Subsequent calls succeed, however, as do calls after a server restart - it
only happens with a newly deployed WAR for some reason.

The server log shows one of the following two errors - it's pretty
arbitrary, but I definitely see the first one more often:

17-May-2011 1:27:01 PM org.restlet.engine.CompositeHelper handle
SEVERE: The org.restlet.Application class has no Restlet defined to process
calls. Maybe it wasn't properly started.

17-May-2011 1:48:34 PM org.restlet.routing.Filter doHandle
WARNING: The filter org.restlet.engine.application.StatusFilter@16f8789 was
executed without a next Restlet attached to it.

I believe my servlet are router are defined correctly, as subsequent calls
succeed:

<servlet>
    <servlet-name>MyRestlet</servlet-name>
   
<servlet-class>org.restlet.ext.spring.RestletFrameworkServlet</servlet-class
>
    <load-on-startup>1</load-on-startup>
</servlet>

<bean id="root" class="org.restlet.ext.spring.SpringRouter">
    <property name="attachments">
        <map>
            <entry key="/item">
                <bean class="org.restlet.ext.spring.SpringFinder">
                    <lookup-method name="create" bean="itemResource"/>
                </bean>
            </entry>
        </map>
    </property>
</bean>

It's interesting that it only occurs for a new deployment - perhaps
something is resolving the issue behind the scenes and caching the results.

Has anyone else experienced this, or know of a solution?

Thanks!

--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/RestletFrameworkServlet-HTTP-50
0-on-first-request-tp6375129p6375129.html
Sent from the Restlet Discuss mailing list archive at Nabble.com.

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=27394
57

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2972107

Reply via email to