[
https://issues.apache.org/jira/browse/JUDDI-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt T Stam resolved JUDDI-568.
-------------------------------
Resolution: Not A Problem
Turns out it was during juddi deploy, but a problem with the unittests. Each
test has a setup phase which loads the initial UDDI data. If something is
corrupt like the publisher, then pretty much all tests will fail the same way
looking like it is looping..
> 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: Alex O'Ree
> 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
