Bug 894323 - Juddi unit tests are failing with DB2 97, column key_data_value in table j3_key_data_value is too short
Summary: Juddi unit tests are failing with DB2 97, column key_data_value in table j3_k...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA
Version: 5.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER4
: 5.3.1
Assignee: Nobody
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-11 12:26 UTC by Jiri Sedlacek
Modified: 2025-02-10 03:27 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
DB2-97, all JDKs, all OSs
Last Closed: 2025-02-10 03:27:15 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
test log resulting from unit tests (4.35 MB, text/x-log)
2013-01-11 12:26 UTC, Jiri Sedlacek 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBESB-3895 0 Major Closed Need to increase the size of j3_key_data_value.key_data_value to 2048 2013-01-29 14:37:23 UTC

Description Jiri Sedlacek 2013-01-11 12:26:01 UTC 
Created attachment 676838 [details]
test log resulting from unit tests

Description of problem:

Some unit tests for juddi 3.1.4 are failing:

    [junit] Running org.apache.juddi.api.impl.API_010_PublisherTest
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 32,25 sec
    [junit] Running org.apache.juddi.api.impl.API_020_TmodelTest
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 55,68 sec
    [junit] Running org.apache.juddi.api.impl.API_030_BusinessEntityTest
    [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 125,03 sec
    [junit] TEST org.apache.juddi.api.impl.API_030_BusinessEntityTest FAILED
    [junit] Running org.apache.juddi.api.impl.API_040_BusinessServiceTest
    [junit] Tests run: 5, Failures: 5, Errors: 0, Time elapsed: 260,38 sec
    [junit] TEST org.apache.juddi.api.impl.API_040_BusinessServiceTest FAILED
    [junit] Running org.apache.juddi.api.impl.API_050_BindingTemplateTest
    [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 102,32 sec
    [junit] TEST org.apache.juddi.api.impl.API_050_BindingTemplateTest FAILED
    [junit] Running org.apache.juddi.api.impl.API_060_PublisherAssertionTest
    [junit] Tests run: 3, Failures: 3, Errors: 0, Time elapsed: 224,45 sec
    [junit] TEST org.apache.juddi.api.impl.API_060_PublisherAssertionTest FAILED
    [junit] Running org.apache.juddi.api.impl.API_070_FindEntityTest
    [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 57,02 sec
    [junit] TEST org.apache.juddi.api.impl.API_070_FindEntityTest FAILED
    [junit] Running org.apache.juddi.api.impl.API_080_SubscriptionTest
    [junit] Tests run: 4, Failures: 1, Errors: 0, Time elapsed: 660,94 sec
    [junit] TEST org.apache.juddi.api.impl.API_080_SubscriptionTest FAILED
    [junit] Running org.apache.juddi.api.impl.API_090_SubscriptionListenerIntegrationTest
    [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 59,24 sec
    [junit] TEST org.apache.juddi.api.impl.API_090_SubscriptionListenerIntegrationTest FAILED
    [junit] Running org.apache.juddi.api.impl.API_091_RMISubscriptionListenerIntegrationTest
    [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 57,12 sec
    [junit] TEST org.apache.juddi.api.impl.API_091_RMISubscriptionListenerIntegrationTest FAILED
    [junit] Running org.apache.juddi.api.impl.API_100_ClientSubscriptionInfoTest
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 25,99 sec
    [junit] Running org.apache.juddi.auth.AuthenticatorTest
    [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 18,85 sec
    [junit] Running org.apache.juddi.config.ApplicationConfigurationTest
    [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,01 sec
    [junit] Running org.apache.juddi.keygen.KeyGeneratorTest
    [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0,01 sec
    [junit] Running org.apache.juddi.rmi.JNDIRegistrationTest
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0,11 sec
    [junit] Running org.apache.juddi.subscription.SubscriptionNotifierTest
    [junit] Tests run: 0, Failures: 2, Errors: 0, Time elapsed: 62,99 sec
    [junit] TEST org.apache.juddi.subscription.SubscriptionNotifierTest FAILED
    [junit] Running org.apache.juddi.subscription.notify.NotifierTest
    [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,27 sec
    [junit] Tests FAILED


How reproducible:
Configure juddi unit tests to use db2 97 db and then run unit tests.



In some cases when saving data to j3_key_data_value table, exception is thrown.
Full log is attached, DEBUG and TRACE output was set for org.hibernate.SQL and org.hibernate.type

If I changed column to use blob(2048), tests passed, I could see that problem row has data of size larger than 700 bytes.
Comment 1 Julian Coleman 2013-01-21 12:31:44 UTC 
Revision 11674 of:

  soa-p/src/main/resources/soa-p/add-juddi-tables.db2.txt

Commit log:

  BZ-894323
  Increase size of key_data_value in the j3_key_data_value table to 2048
  in the DB2 upgrade script.  Mirrors change in the ESB create table script.
Comment 2 Jiri Sedlacek 2013-01-29 14:40:58 UTC 
verified in soa-p-5.3.1.ER4
Comment 10 Red Hat Bugzilla 2025-02-10 03:27:15 UTC 
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.
Note You need to log in before you can comment on or make changes to this bug.