You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt T Stam (JIRA)" <ju...@ws.apache.org> on 2013/03/19 22:55:17 UTC

[jira] [Comment Edited] (JUDDI-568) If publication of the root publisher fails, juddi goes into an infinite loop

    [ https://issues.apache.org/jira/browse/JUDDI-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606887#comment-13606887 ] 

Kurt T Stam edited comment on JUDDI-568 at 3/19/13 9:55 PM:
------------------------------------------------------------

Hi Alex, I just looked at the code and it should be throwing a ConfigurationException; all the way into the RegistryServlet which then logs the error. Did you check the juddi.log?

try {
			Registry.start();
		} catch (ConfigurationException e) {
			logger.error("jUDDI registry could not be started."
					+ e.getMessage(), e);
		}

I now also throw a ServletException so that the container knows the initialization of jUDDI went bust. Do you have an easy way of validating that this change does the the trick?

--Kurt
                
      was (Author: kurtstam):
    Hi Alex, I just looked at the code and it should be throwing a ConfigurationException; all the way into the RegistryServlet which then logs the error. Did you check the juddi.log?

try {
			Registry.start();
		} catch (ConfigurationException e) {
			logger.error("jUDDI registry could not be started."
					+ e.getMessage(), e);
		}

I now also through a ServletException so that the container knows the initialization of jUDDI went bust. Do you have an easy way of validating that this change does the the trick?

--Kurt
                  
> If publication of the root publisher fails, juddi goes into an infinite loop
> ----------------------------------------------------------------------------
>
>                 Key: JUDDI-568
>                 URL: https://issues.apache.org/jira/browse/JUDDI-568
>             Project: jUDDI
>          Issue Type: Bug
>    Affects Versions: 3.1.4
>            Reporter: Alex O'Ree
>            Assignee: Kurt T Stam
>            Priority: Minor
>             Fix For: 3.1.5
>
>
> If the initial seed data from trunk/juddi-core-openjpa/target/classes/juddi_install_data/ is bad or is rejected somewhere due to a validation error, no error messages are displayed to the log or stdout. Furthermore, the Install class gets stuck in an infinite loop. Suggest some kind of counter or exist cause to prevent the loop,

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira