buildbot failure in on juddi-trunk-win7-openjpa
The Buildbot has detected a new failure on builder juddi-trunk-win7-openjpa while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-win7-openjpa/builds/104 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb-win10 Build Reason: The SingleBranchScheduler scheduler named 'on-juddi-hibernate-commit' triggered this build Build Source Stamp: [branch master] 044d97ff22f51bca8f58496bac20aea25c5e68d6 Blamelist: Alex O'Ree BUILD FAILED: failed compile_1 Sincerely, -The Buildbot
buildbot success in on juddi-trunk-win7-hibernate
The Buildbot has detected a restored build on builder juddi-trunk-win7-hibernate while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-win7-hibernate/builds/105 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb-win10 Build Reason: The SingleBranchScheduler scheduler named 'on-juddi-hibernate-commit' triggered this build Build Source Stamp: [branch master] bec02735c517deb20c54f1b2804add40216f3055 Blamelist: Alex O'Ree Build succeeded! Sincerely, -The Buildbot
[jira] [Commented] (JUDDI-949) Make JUDDI compatible with WebLogic and Oracle database
[ https://issues.apache.org/jira/browse/JUDDI-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995938#comment-16995938 ] Alex O'Ree commented on JUDDI-949: -- is this still an issue? also, where was your repo with these changes? > Make JUDDI compatible with WebLogic and Oracle database > --- > > Key: JUDDI-949 > URL: https://issues.apache.org/jira/browse/JUDDI-949 > Project: jUDDI > Issue Type: Improvement > Components: juddi-tomcat >Affects Versions: 3.3.2 >Reporter: Matthieu Ghilain >Priority: Minor > > At the moment JUDDI is not compatible with Oracle database and WebLogic. > The following things are probably necessary: > - Creation of a weblogic.xml file > - Creation of a specific orm.xml file to make it compatible with Oracle > - Custom web.xml > - *Adjustment to code (problem with JAXB)* > - *Fix in some jsp* > - Custom persistence.xml > - Creation of a custom build profile in pom.xml > The things in bold might have an impact on other deployment environment. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (JUDDI-854) update cloud instance
[ https://issues.apache.org/jira/browse/JUDDI-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree resolved JUDDI-854. -- Resolution: Fixed > update cloud instance > - > > Key: JUDDI-854 > URL: https://issues.apache.org/jira/browse/JUDDI-854 > Project: jUDDI > Issue Type: Task > Components: cloud >Reporter: Kurt T Stam >Assignee: Kurt Stam >Priority: Minor > > - add a banner to tell people how to get a publisher account. > - update the seed data to reflect the nature of this node -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree resolved JUDDI-991. -- Resolution: Fixed this should be resolved. hopefully there won't be any unanticipated side effects > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995928#comment-16995928 ] ASF subversion and git services commented on JUDDI-991: --- Commit 044d97ff22f51bca8f58496bac20aea25c5e68d6 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=044d97f ] JUDDI-991 cxf update > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995925#comment-16995925 ] ASF subversion and git services commented on JUDDI-991: --- Commit e4112296a261249fc41663341933f3a931f5f07c in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=e411229 ] JUDDI-991 progress with cxf upgrade > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995926#comment-16995926 ] ASF subversion and git services commented on JUDDI-991: --- Commit 8016bf340db08da87391129cfec23a59b1473691 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=8016bf3 ] Merge branch 'master' into feature/JUDDI-991 > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995927#comment-16995927 ] ASF subversion and git services commented on JUDDI-991: --- Commit 4522d6fb5bf61408aa8a4f20e47f2ee2813b48ff in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=4522d6f ] Merge branch 'master' into feature/JUDDI-991 > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995924#comment-16995924 ] ASF subversion and git services commented on JUDDI-991: --- Commit 044d97ff22f51bca8f58496bac20aea25c5e68d6 in juddi's branch refs/heads/feature/JUDDI-991 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=044d97f ] JUDDI-991 cxf update > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995923#comment-16995923 ] ASF subversion and git services commented on JUDDI-991: --- Commit 4522d6fb5bf61408aa8a4f20e47f2ee2813b48ff in juddi's branch refs/heads/feature/JUDDI-991 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=4522d6f ] Merge branch 'master' into feature/JUDDI-991 > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995921#comment-16995921 ] ASF subversion and git services commented on JUDDI-991: --- Commit e4112296a261249fc41663341933f3a931f5f07c in juddi's branch refs/heads/feature/JUDDI-991 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=e411229 ] JUDDI-991 progress with cxf upgrade > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
buildbot success in on juddi-trunk-win7-openjpa
The Buildbot has detected a restored build on builder juddi-trunk-win7-openjpa while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-win7-openjpa/builds/103 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb-win10 Build Reason: The SingleBranchScheduler scheduler named 'on-juddi-hibernate-commit' triggered this build Build Source Stamp: [branch master] 854d5708bed7f025613916c182db9bbc879ba6cb Blamelist: Alex O'Ree Build succeeded! Sincerely, -The Buildbot
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995922#comment-16995922 ] ASF subversion and git services commented on JUDDI-991: --- Commit 8016bf340db08da87391129cfec23a59b1473691 in juddi's branch refs/heads/feature/JUDDI-991 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=8016bf3 ] Merge branch 'master' into feature/JUDDI-991 > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
buildbot failure in on juddi-trunk-hibernate
The Buildbot has detected a new failure on builder juddi-trunk-hibernate while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-hibernate/builds/103 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: asf947_ubuntu Build Reason: The SingleBranchScheduler scheduler named 'on-juddi-hibernate-commit' triggered this build Build Source Stamp: [branch master] 854d5708bed7f025613916c182db9bbc879ba6cb Blamelist: Alex O'Ree BUILD FAILED: failed compile_1 Sincerely, -The Buildbot
[jira] [Resolved] (JUDDI-995) Add automated generation of sha512 hashes during the build
[ https://issues.apache.org/jira/browse/JUDDI-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree resolved JUDDI-995. -- Resolution: Fixed > Add automated generation of sha512 hashes during the build > -- > > Key: JUDDI-995 > URL: https://issues.apache.org/jira/browse/JUDDI-995 > Project: jUDDI > Issue Type: Improvement > Components: build >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > Fix For: 3.3.7 > > > the asf release guys want us to use a strong hash mechanism. found a plugin > that will auto generate it -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JUDDI-995) Add automated generation of sha512 hashes during the build
[ https://issues.apache.org/jira/browse/JUDDI-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree updated JUDDI-995: - Fix Version/s: 3.3.7 > Add automated generation of sha512 hashes during the build > -- > > Key: JUDDI-995 > URL: https://issues.apache.org/jira/browse/JUDDI-995 > Project: jUDDI > Issue Type: Improvement > Components: build >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > Fix For: 3.3.7 > > > the asf release guys want us to use a strong hash mechanism. found a plugin > that will auto generate it -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-1000) Update embedded tomcat to the latest version available
[ https://issues.apache.org/jira/browse/JUDDI-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995883#comment-16995883 ] ASF subversion and git services commented on JUDDI-1000: Commit bec02735c517deb20c54f1b2804add40216f3055 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=bec0273 ] JUDDI-1000 resolved > Update embedded tomcat to the latest version available > -- > > Key: JUDDI-1000 > URL: https://issues.apache.org/jira/browse/JUDDI-1000 > Project: jUDDI > Issue Type: Improvement > Components: juddi-tomcat >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > Fix For: 3.3.7 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (JUDDI-1000) Update embedded tomcat to the latest version available
[ https://issues.apache.org/jira/browse/JUDDI-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree resolved JUDDI-1000. --- Resolution: Fixed > Update embedded tomcat to the latest version available > -- > > Key: JUDDI-1000 > URL: https://issues.apache.org/jira/browse/JUDDI-1000 > Project: jUDDI > Issue Type: Improvement > Components: juddi-tomcat >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > Fix For: 3.3.7 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (JUDDI-995) Add automated generation of sha512 hashes during the build
[ https://issues.apache.org/jira/browse/JUDDI-995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree reassigned JUDDI-995: Assignee: Alex O'Ree > Add automated generation of sha512 hashes during the build > -- > > Key: JUDDI-995 > URL: https://issues.apache.org/jira/browse/JUDDI-995 > Project: jUDDI > Issue Type: Improvement > Components: build >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > > the asf release guys want us to use a strong hash mechanism. found a plugin > that will auto generate it -- This message was sent by Atlassian Jira (v8.3.4#803005)
buildbot failure in on juddi-trunk-win7-hibernate
The Buildbot has detected a new failure on builder juddi-trunk-win7-hibernate while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-win7-hibernate/builds/104 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb-win10 Build Reason: The SingleBranchScheduler scheduler named 'on-juddi-hibernate-commit' triggered this build Build Source Stamp: [branch master] 854d5708bed7f025613916c182db9bbc879ba6cb Blamelist: Alex O'Ree BUILD FAILED: failed compile Sincerely, -The Buildbot
buildbot failure in on juddi-trunk-openjpa
The Buildbot has detected a new failure on builder juddi-trunk-openjpa while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-openjpa/builds/103 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: asf947_ubuntu Build Reason: The SingleBranchScheduler scheduler named 'on-juddi-hibernate-commit' triggered this build Build Source Stamp: [branch master] 854d5708bed7f025613916c182db9bbc879ba6cb Blamelist: Alex O'Ree BUILD FAILED: failed compile_1 Sincerely, -The Buildbot
[jira] [Updated] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK
[ https://issues.apache.org/jira/browse/JUDDI-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree updated JUDDI-998: - Fix Version/s: (was: 3.3.7) > when using the gui, create, new business name is incorrectly stored as OK > - > > Key: JUDDI-998 > URL: https://issues.apache.org/jira/browse/JUDDI-998 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Affects Versions: 3.3.6 >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK
[ https://issues.apache.org/jira/browse/JUDDI-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree resolved JUDDI-998. -- Resolution: Cannot Reproduce > when using the gui, create, new business name is incorrectly stored as OK > - > > Key: JUDDI-998 > URL: https://issues.apache.org/jira/browse/JUDDI-998 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Affects Versions: 3.3.6 >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.7 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK
[ https://issues.apache.org/jira/browse/JUDDI-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995862#comment-16995862 ] Alex O'Ree commented on JUDDI-998: -- turns out to not be an issue. may have only been present on a test branch > when using the gui, create, new business name is incorrectly stored as OK > - > > Key: JUDDI-998 > URL: https://issues.apache.org/jira/browse/JUDDI-998 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Affects Versions: 3.3.6 >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.7 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work started] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK
[ https://issues.apache.org/jira/browse/JUDDI-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JUDDI-998 started by Alex O'Ree. > when using the gui, create, new business name is incorrectly stored as OK > - > > Key: JUDDI-998 > URL: https://issues.apache.org/jira/browse/JUDDI-998 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Affects Versions: 3.3.6 >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.7 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000)
[
https://issues.apache.org/jira/browse/JUDDI-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex O'Ree resolved JUDDI-999.
--
Resolution: Fixed
> Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000)
> ---
>
> Key: JUDDI-999
> URL: https://issues.apache.org/jira/browse/JUDDI-999
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6
>Reporter: Rahul S
>Assignee: Alex O'Ree
>Priority: Major
> Labels: jUDDI, juddi
> Fix For: 3.3.7
>
> Attachments: juddi-core-3.3.7-SNAPSHOT.jar,
> juddi-core-openjpa-3.3.7-SNAPSHOT.jar
>
>
> We were using SQLServer with JUDDI 3.0.4. It is working fine so far.
> Now, we are trying to move to JUDDI version 3.3.6. We are encountering
> following issue on start-up.
> {code:java}
> Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002]Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131, state=S0002]
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559) at
> org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455) at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
> at
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
> at
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:155)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:226)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:153)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:59)
> at
> org.apache.juddi.config.PersistenceManager.getEntityManager(PersistenceManager.java:48)
> at
> org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:174)
> at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:160)
> at org.apache.juddi.config.AppConfig.(AppConfig.java:82) at
> org.apache.juddi.config.AppConfig.getInstance(AppConfig.java:272) at
> org.apache.juddi.config.AppConfig.getConfiguration(AppConfig.java:298) at
> org.apache.juddi.api.impl.AuthenticatedService.(AuthenticatedService.java:75)
> at org.apache.juddi.api.impl.UDDIInquiryImpl.(UDDIInquiryImpl.java:88)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at
> java.lang.reflect.Constructor.newInstance(Unknown Source) at
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142) ...
> 36 moreCaused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: The size
> (8192) given to the column 'instance_parms' exceeds the maximum allowed for
> any data type (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info
> (id BIGINT NOT NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255)
> NOT NULL, entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002] at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:59)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConnectionDecorator.java:914)
> at
> org.apache.openjpa.lib.jdbc.DelegatingStatement.exec
[jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000)
[
https://issues.apache.org/jira/browse/JUDDI-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995854#comment-16995854
]
ASF subversion and git services commented on JUDDI-999:
---
Commit 854d5708bed7f025613916c182db9bbc879ba6cb in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=854d570 ]
JUDDI-999 merging
> Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000)
> ---
>
> Key: JUDDI-999
> URL: https://issues.apache.org/jira/browse/JUDDI-999
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6
>Reporter: Rahul S
>Assignee: Alex O'Ree
>Priority: Major
> Labels: jUDDI, juddi
> Fix For: 3.3.7
>
> Attachments: juddi-core-3.3.7-SNAPSHOT.jar,
> juddi-core-openjpa-3.3.7-SNAPSHOT.jar
>
>
> We were using SQLServer with JUDDI 3.0.4. It is working fine so far.
> Now, we are trying to move to JUDDI version 3.3.6. We are encountering
> following issue on start-up.
> {code:java}
> Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002]Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131, state=S0002]
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559) at
> org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455) at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
> at
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
> at
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:155)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:226)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:153)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:59)
> at
> org.apache.juddi.config.PersistenceManager.getEntityManager(PersistenceManager.java:48)
> at
> org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:174)
> at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:160)
> at org.apache.juddi.config.AppConfig.(AppConfig.java:82) at
> org.apache.juddi.config.AppConfig.getInstance(AppConfig.java:272) at
> org.apache.juddi.config.AppConfig.getConfiguration(AppConfig.java:298) at
> org.apache.juddi.api.impl.AuthenticatedService.(AuthenticatedService.java:75)
> at org.apache.juddi.api.impl.UDDIInquiryImpl.(UDDIInquiryImpl.java:88)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at
> java.lang.reflect.Constructor.newInstance(Unknown Source) at
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142) ...
> 36 moreCaused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: The size
> (8192) given to the column 'instance_parms' exceeds the maximum allowed for
> any data type (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info
> (id BIGINT NOT NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255)
> NOT NULL, entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002] at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator
[jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000)
[
https://issues.apache.org/jira/browse/JUDDI-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995850#comment-16995850
]
ASF subversion and git services commented on JUDDI-999:
---
Commit 539b31b8d2d7e7e6db13814943eec80cef3f3c4c in juddi's branch
refs/heads/bug/JUDDI-999 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=539b31b ]
JUDDI-999 fix for mssql issue with tmodelinstanceinfo varchar being too big
> Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000)
> ---
>
> Key: JUDDI-999
> URL: https://issues.apache.org/jira/browse/JUDDI-999
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6
>Reporter: Rahul S
>Assignee: Alex O'Ree
>Priority: Major
> Labels: jUDDI, juddi
> Fix For: 3.3.7
>
> Attachments: juddi-core-3.3.7-SNAPSHOT.jar,
> juddi-core-openjpa-3.3.7-SNAPSHOT.jar
>
>
> We were using SQLServer with JUDDI 3.0.4. It is working fine so far.
> Now, we are trying to move to JUDDI version 3.3.6. We are encountering
> following issue on start-up.
> {code:java}
> Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002]Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131, state=S0002]
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559) at
> org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455) at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
> at
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
> at
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:155)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:226)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:153)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:59)
> at
> org.apache.juddi.config.PersistenceManager.getEntityManager(PersistenceManager.java:48)
> at
> org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:174)
> at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:160)
> at org.apache.juddi.config.AppConfig.(AppConfig.java:82) at
> org.apache.juddi.config.AppConfig.getInstance(AppConfig.java:272) at
> org.apache.juddi.config.AppConfig.getConfiguration(AppConfig.java:298) at
> org.apache.juddi.api.impl.AuthenticatedService.(AuthenticatedService.java:75)
> at org.apache.juddi.api.impl.UDDIInquiryImpl.(UDDIInquiryImpl.java:88)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at
> java.lang.reflect.Constructor.newInstance(Unknown Source) at
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142) ...
> 36 moreCaused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: The size
> (8192) given to the column 'instance_parms' exceeds the maximum allowed for
> any data type (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info
> (id BIGINT NOT NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255)
> NOT NULL, entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002] at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203
[jira] [Updated] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK
[ https://issues.apache.org/jira/browse/JUDDI-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree updated JUDDI-998: - Summary: when using the gui, create, new business name is incorrectly stored as OK (was: when using the gui, create, new busimess name is incorrectly stored as OK) > when using the gui, create, new business name is incorrectly stored as OK > - > > Key: JUDDI-998 > URL: https://issues.apache.org/jira/browse/JUDDI-998 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (JUDDI-1000) Update embedded tomcat to the latest version available
Alex O'Ree created JUDDI-1000: - Summary: Update embedded tomcat to the latest version available Key: JUDDI-1000 URL: https://issues.apache.org/jira/browse/JUDDI-1000 Project: jUDDI Issue Type: Improvement Components: juddi-tomcat Reporter: Alex O'Ree Assignee: Alex O'Ree Fix For: 3.3.7 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK
[ https://issues.apache.org/jira/browse/JUDDI-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree updated JUDDI-998: - Fix Version/s: 3.3.7 > when using the gui, create, new business name is incorrectly stored as OK > - > > Key: JUDDI-998 > URL: https://issues.apache.org/jira/browse/JUDDI-998 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Affects Versions: 3.3.6 >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.7 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK
[ https://issues.apache.org/jira/browse/JUDDI-998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree updated JUDDI-998: - Affects Version/s: 3.3.6 > when using the gui, create, new business name is incorrectly stored as OK > - > > Key: JUDDI-998 > URL: https://issues.apache.org/jira/browse/JUDDI-998 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Affects Versions: 3.3.6 >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000)
[
https://issues.apache.org/jira/browse/JUDDI-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex O'Ree updated JUDDI-999:
-
Fix Version/s: 3.3.7
> Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000)
> ---
>
> Key: JUDDI-999
> URL: https://issues.apache.org/jira/browse/JUDDI-999
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6
>Reporter: Rahul S
>Assignee: Alex O'Ree
>Priority: Major
> Labels: jUDDI, juddi
> Fix For: 3.3.7
>
> Attachments: juddi-core-3.3.7-SNAPSHOT.jar,
> juddi-core-openjpa-3.3.7-SNAPSHOT.jar
>
>
> We were using SQLServer with JUDDI 3.0.4. It is working fine so far.
> Now, we are trying to move to JUDDI version 3.3.6. We are encountering
> following issue on start-up.
> {code:java}
> Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002]Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131, state=S0002]
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559) at
> org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455) at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
> at
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
> at
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:155)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:226)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:153)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:59)
> at
> org.apache.juddi.config.PersistenceManager.getEntityManager(PersistenceManager.java:48)
> at
> org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:174)
> at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:160)
> at org.apache.juddi.config.AppConfig.(AppConfig.java:82) at
> org.apache.juddi.config.AppConfig.getInstance(AppConfig.java:272) at
> org.apache.juddi.config.AppConfig.getConfiguration(AppConfig.java:298) at
> org.apache.juddi.api.impl.AuthenticatedService.(AuthenticatedService.java:75)
> at org.apache.juddi.api.impl.UDDIInquiryImpl.(UDDIInquiryImpl.java:88)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at
> java.lang.reflect.Constructor.newInstance(Unknown Source) at
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142) ...
> 36 moreCaused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: The size
> (8192) given to the column 'instance_parms' exceeds the maximum allowed for
> any data type (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info
> (id BIGINT NOT NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255)
> NOT NULL, entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002] at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:59)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConnectionDecorator.java:914)
> at
> org.apache.openjpa.lib.jdbc.DelegatingStatement.exe
[jira] [Assigned] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000)
[
https://issues.apache.org/jira/browse/JUDDI-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex O'Ree reassigned JUDDI-999:
Assignee: Alex O'Ree
> Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000)
> ---
>
> Key: JUDDI-999
> URL: https://issues.apache.org/jira/browse/JUDDI-999
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6
>Reporter: Rahul S
>Assignee: Alex O'Ree
>Priority: Major
> Labels: jUDDI, juddi
> Attachments: juddi-core-3.3.7-SNAPSHOT.jar,
> juddi-core-openjpa-3.3.7-SNAPSHOT.jar
>
>
> We were using SQLServer with JUDDI 3.0.4. It is working fine so far.
> Now, we are trying to move to JUDDI version 3.3.6. We are encountering
> following issue on start-up.
> {code:java}
> Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002]Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131, state=S0002]
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559) at
> org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455) at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
> at
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
> at
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:155)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:226)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:153)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:59)
> at
> org.apache.juddi.config.PersistenceManager.getEntityManager(PersistenceManager.java:48)
> at
> org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:174)
> at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:160)
> at org.apache.juddi.config.AppConfig.(AppConfig.java:82) at
> org.apache.juddi.config.AppConfig.getInstance(AppConfig.java:272) at
> org.apache.juddi.config.AppConfig.getConfiguration(AppConfig.java:298) at
> org.apache.juddi.api.impl.AuthenticatedService.(AuthenticatedService.java:75)
> at org.apache.juddi.api.impl.UDDIInquiryImpl.(UDDIInquiryImpl.java:88)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at
> java.lang.reflect.Constructor.newInstance(Unknown Source) at
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142) ...
> 36 moreCaused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: The size
> (8192) given to the column 'instance_parms' exceeds the maximum allowed for
> any data type (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info
> (id BIGINT NOT NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255)
> NOT NULL, entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002] at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:59)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConnectionDecorator.java:914)
> at
> org.apache.openjpa.lib.jdbc.DelegatingStatement.executeUpdate(DelegatingSta
