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/07 16:16:13 UTC

[jira] [Commented] (JUDDI-562) CI build integration failures

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

Kurt T Stam commented on JUDDI-562:
-----------------------------------

ad 1. Removing the ./m2/repository/repository.xml fixed the issue for me. I'm not sure why this file was corrupted. This file has nothing to do with the actual build, but does is used by the maven-bundle plugin.

ad 2. I moved setting the properties in a different place in the hibernate/openjpa profiles. 

ad 3. Hibernate seems to pick 255 as the default size. I'm now explicitly setting it to 65636.
                
> CI build integration failures
> -----------------------------
>
>                 Key: JUDDI-562
>                 URL: https://issues.apache.org/jira/browse/JUDDI-562
>             Project: jUDDI
>          Issue Type: Bug
>            Reporter: Kurt T Stam
>            Assignee: Kurt T Stam
>             Fix For: 3.1.5
>
>
> 1. [INFO] --- maven-bundle-plugin:2.0.0:install (default-install) @ uddi-ws ---
> [INFO] Parsing file:/.m2/repository/repository.xml
> [Fatal Error] repository.xml:3:1: Premature end of file.
> 2. Caused by: javax.persistence.PersistenceException: No Persistence provider for EntityManager named juddiDatabase
> 3. Hibernate build only:
> SEVERE: A truncation error was encountered trying to shrink BLOB '(Binary data value not displayed)' to length 255.
> Mar 7, 2013 9:35:56 AM org.hibernate.event.def.AbstractFlushingEventListener performExecutions
> SEVERE: Could not synchronize database state with session
> org.hibernate.exception.DataException: could not insert: [org.apache.juddi.model.KeyDataValue]

--
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