[jboss-jira] [JBoss JIRA] (JBRULES-3576) Drools-camel-Server - Guvnor URL referenced by <drools:resource> is not started yet.

Nicholas DiPiazza (JIRA) jira-events at lists.jboss.org
Tue Jul 10 20:23:12 EDT 2012


     [ https://issues.jboss.org/browse/JBRULES-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicholas DiPiazza updated JBRULES-3576:
---------------------------------------

    Description: 
When Drools-camel-server has a knowledge session with <drools:resource source="http://remoteurl.com/drools/resource">, but the URL is not available... then instead of gracefully timing out... it will freeze Tomcat never to be unfrozen.

This makes it so Guvnor and Drools execution sever can't be tested on the same Tomcat. 

Steps to reproduce: 


1)	Get droolsjbpm-integration-distribution-5.3.0.Final\binaries\drools-camel-server-5.3.0.Final.war and Extract to $catalina_home/webapps/drools-server
2)	Get droolsjbpm-integration-distribution-5.3.0.Final\binaries\drools-camel-server-5.3.0.Final.war and Extract to $catalina_home/webapps/guvnor
3)	Create two Tomcats (do not put drools-server that is connected to guvnor as an endpoint or the server won’t startup), changing the ports so they can run simultaneously on the same box. 
4)	Deploy drools-camel-server and Guvnor on the same tomcat 6 server. Give it 512m permgen and 1000m max heap.
5)	Created a test Rule on guvnor called test. Binary PKG should be: http://localhost:8080/guvnor/rest/packages/test 
6)     Stop Tomcat
7)     Edit drools-server/WEB-INF/classes/camel-client.xml

change 

       <from uri="direct://kservice"/>

to 

       <from uri="direct://kservice/rest"/>

8) Edit knowledge-services.xml:

Replace kbase with this one:

  <drools:kbase id="kbase1" node="node1">
      <drools:resources>
            <drools:resource  type="PKG" source="http://localhost:8080/guvnor/rest/packages/test/binary"/>
    </drools:resources>
  </drools:kbase>

9) Restart

Because Guvnor is not started yet when Drools-camel-server is starting, Drools-camel-server sits and freezes up. Never unfreezes.

Expected result: should try again after N ms for a maximum of M tries. 

  was:
When Drools-camel-server has a knowledge session with <drools:resource source="a url that is not available yet", then instead of gracefully timing out... it will freeze Tomcat never to be unfrozen.

Steps to reproduce: 


1)	Get droolsjbpm-integration-distribution-5.3.0.Final\binaries\drools-camel-server-5.3.0.Final.war and Extract to $catalina_home/webapps/drools-server
2)	Get droolsjbpm-integration-distribution-5.3.0.Final\binaries\drools-camel-server-5.3.0.Final.war and Extract to $catalina_home/webapps/guvnor
3)	Create two Tomcats (do not put drools-server that is connected to guvnor as an endpoint or the server won’t startup), changing the ports so they can run simultaneously on the same box. 
4)	Deploy drools-camel-server and Guvnor on the same tomcat 6 server. Give it 512m permgen and 1000m max heap.
5)	Created a test Rule on guvnor called test. Binary PKG should be: http://localhost:8080/guvnor/rest/packages/test 
6)     Stop Tomcat
7)     Edit drools-server/WEB-INF/classes/camel-client.xml

change 

       <from uri="direct://kservice"/>

to 

       <from uri="direct://kservice/rest"/>

8) Edit knowledge-services.xml:

Replace kbase with this one:

  <drools:kbase id="kbase1" node="node1">
      <drools:resources>
            <drools:resource  type="PKG" source="http://localhost:8080/guvnor/rest/packages/test/binary"/>
    </drools:resources>
  </drools:kbase>

9) Restart

Because Guvnor is not started yet when Drools-camel-server is starting, Drools-camel-server sits and freezes up. Never unfreezes.

Expected result: should try again after N ms for a maximum of M tries. 


    
> Drools-camel-Server - Guvnor URL referenced by <drools:resource> is not started yet.
> ------------------------------------------------------------------------------------
>
>                 Key: JBRULES-3576
>                 URL: https://issues.jboss.org/browse/JBRULES-3576
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-camel
>    Affects Versions: 5.3.0.Final
>            Reporter: Nicholas DiPiazza
>            Assignee: Mark Proctor
>
> When Drools-camel-server has a knowledge session with <drools:resource source="http://remoteurl.com/drools/resource">, but the URL is not available... then instead of gracefully timing out... it will freeze Tomcat never to be unfrozen.
> This makes it so Guvnor and Drools execution sever can't be tested on the same Tomcat. 
> Steps to reproduce: 
> 1)	Get droolsjbpm-integration-distribution-5.3.0.Final\binaries\drools-camel-server-5.3.0.Final.war and Extract to $catalina_home/webapps/drools-server
> 2)	Get droolsjbpm-integration-distribution-5.3.0.Final\binaries\drools-camel-server-5.3.0.Final.war and Extract to $catalina_home/webapps/guvnor
> 3)	Create two Tomcats (do not put drools-server that is connected to guvnor as an endpoint or the server won’t startup), changing the ports so they can run simultaneously on the same box. 
> 4)	Deploy drools-camel-server and Guvnor on the same tomcat 6 server. Give it 512m permgen and 1000m max heap.
> 5)	Created a test Rule on guvnor called test. Binary PKG should be: http://localhost:8080/guvnor/rest/packages/test 
> 6)     Stop Tomcat
> 7)     Edit drools-server/WEB-INF/classes/camel-client.xml
> change 
>        <from uri="direct://kservice"/>
> to 
>        <from uri="direct://kservice/rest"/>
> 8) Edit knowledge-services.xml:
> Replace kbase with this one:
>   <drools:kbase id="kbase1" node="node1">
>       <drools:resources>
>             <drools:resource  type="PKG" source="http://localhost:8080/guvnor/rest/packages/test/binary"/>
>     </drools:resources>
>   </drools:kbase>
> 9) Restart
> Because Guvnor is not started yet when Drools-camel-server is starting, Drools-camel-server sits and freezes up. Never unfreezes.
> Expected result: should try again after N ms for a maximum of M tries. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the jboss-jira mailing list