Announcement Announcement Module
No announcement yet.
Context initialization hangs on Burlap proxy Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Context initialization hangs on Burlap proxy


    I have met a strange (as for me) behavior (Spring 2.0.3).

    I have following context
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN 2.0//EN" "">
        Application context for the remote service client.
        Defines various proxies proxies to acess the same service by various protocols 
        (for demo purposes only, in reality one protocol is usually suffcient).
        <!-- Resolves ${...} placeholders from -->
        <bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
            <property name="location" value="WEB-INF/"/>
        <!-- Proxy for the Hessian-exported OrderService -->
        <!-- Hessian is a slim binary HTTP remoting protocol -->
        <bean id="hessianProxy" class="org.springframework.remoting.caucho.HessianProxyFactoryBean">
            <property name="serviceUrl"
                value="http://${serverName}:${httpPort}${contextPath}/remoting/XYService-hessian" />
            <property name="serviceInterface" value="${serviceInterface}" />
        <!-- Proxy for the Burlap-exported OrderService -->
        <!-- Burlap is a slim XML-based HTTP remoting protocol -->
        <bean id="burlapProxy" class="org.springframework.remoting.caucho.BurlapProxyFactoryBean">
            <property name="serviceUrl"
                value="http://${serverName}:${httpPort}${contextPath}/remoting/XYService-burlap" />
            <property name="serviceInterface" value="${serviceInterface}" />
        <!-- Proxy for the HTTP-invoker-exported XYService -->
        <!-- Spring's HTTP invoker uses Java serialization via HTTP  -->
        <!--  Note that HTTP Invoker is a preferred method for Java-to-Java communication -->
        <bean id="httpInvokerProxy" class="org.springframework.remoting.httpinvoker.HttpInvokerProxyFactoryBean">
            <property name="serviceUrl"
                value="http://${serverName}:${httpPort}${contextPath}/remoting/XYService-httpinvoker" />
            <property name="serviceInterface" value="${serviceInterface}" />
            Comment the following in to use Apache Commons HttpClient instead of the JDK's
            standard HttpURLConnection (as used by the default SimpleHttpInvokerRequestExecutor).
            <property name="httpInvokerRequestExecutor">
                    <bean class="org.springframework.remoting.httpinvoker.CommonsHttpInvokerRequestExecutor"/>
    It was copied (with absolutely minor modifications) from JPetStore cleintContext.XML.

    When I start Tomcat all hangs on initialization of burlapProxy bean - see failure.txt in the attached zip (too big to include it directly into the post)

    If definition of this bean is commented out all loads and works Ok.

    But now even more fascinating part - if I deploy application to the running Tomcat it loads and works nicely (see success.txt in the attached zip) - till next Tomcat restart, when it hangs.

    Any ideas?

    Regards, Oleksandr