| Summary: | jUDDI v3 cannot be certified with SQl Server 2005 and db2 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jiri Pechanec <jpechane> | ||||||
| Component: | jUDDI - within SOA | Assignee: | Kurt Stam <kurt.stam> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 5.0.0 ER5 | ||||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 5.1.0 GA | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-1704 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: |
ER5
|
|||||||
| Last Closed: | 2011-02-11 06:53:45 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Jiri Pechanec
2009-12-11 04:49:03 UTC
Jiri, 1. was the persistence.xml changed to mssql-dialect or db2-dialect? 2. what are the errors? 3. can I get my hands on a myssql and db2 database so I can reproduce? --Kurt I have attached persistence.xml file for db2. Unfortunately there are no more information generated by tests related to errors. You can get an instance of db2 database putting this URL to browser http://jawa05.englab.brq.redhat.com/Allocator/AllocatorServlet?operation=alloc&label=db2-97&requestee=KurtStam&expiry=120 - this will reserve a database instance for 120 minutes for your use. The connection details are displayed in the page Attachment: Added: persistence.xml Jiri, which are the specific tests that are failing? thx --Kurt org.apache.juddi.api.impl.API_080_SubscriptionTest.joePublisher org.apache.juddi.api.impl.API_080_SubscriptionTest.samSyndicator org.apache.juddi.api.impl.API_080_SubscriptionTest.samSyndicatorWithChunkingOnFind org.apache.juddi.api.impl.API_080_SubscriptionTest.samSyndicatorWithChunkingOnGet org.apache.juddi.subscription.SubscriptionNotifierTest.org.apache.juddi.subscription.SubscriptionNotifierTest Does the persistence.xml contain something like <provider>org.hibernate.ejb.HibernatePersistence</provider> Yes, see attached file. BTW I am sory I have posted too generic URL - this one is better http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-juddi3-db-jdk16-maven/DATABASE=mssql2005,jdk=java16_default,label=RHEL_any/7/ Test results with ER7 http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-juddi3-db-jdk16-maven/15/DATABASE=mssql2005,jdk=java16_default,label=RHEL_any/ http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-juddi3-db-jdk16-maven/15/DATABASE=db2-97,jdk=java16_default,label=RHEL_any/ Files server.log and test.log are created with DEBUG level Both dbs have issues with: the query: select distinct ss from Subscription ss where (ss.authorizedName = ?) "The text data type cannot be selected as DISTINCT because it is not comparable." I think it does a distinct over all the fields rather then just the PK, and one of the fields on subscription is "text", which is causing an issue. http://issues.apache.org/jira/browse/JUDDI-341 ER8 contains jUDDI 3.0.1 but the problem is still there - see http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-juddi3-db-jdk16-maven/17/DATABASE=db2-97,jdk=java16_default,label=RHEL_any/ http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-juddi3-db-jdk16-maven/17/DATABASE=mssql2005,jdk=java16_default,label=RHEL_any/ it was still doing a distinct over all the columns. Should be fixed now. Jiri, let me attach a new jar so you can verify. Attachment: Added: juddi-core-3.0.2-SNAPSHOT.jar I have tried the attached jar and the result is - all blue. The problem is solved and there is no impact on the other databases http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-juddi3-db-jdk16-maven/20/ Jar fixes the problem but we will have to wait for juddi 3.0.2 to get the fix This needs to be fixed in SOA 5.1.0 Both releases jUDDI-3.0.2 and 3.0.3 are available: http://ws.apache.org/juddi/releases.html We are already using 3.0.3, alt was just doing some housekeeping after triage. I don't think there is anything else that needs to be done apart from verify whether it works or not (QE). Writer: Added: dlesage Verified in ER6 Temporarily reopening to update release note info. Release Notes Docs Status: Added: Not Required |