[esb-issues] [JBoss JIRA] Created: (JBESB-2978) Juddi v3 errors running on Oracle

Fri Nov 13 06:15:05 EST 2009

Juddi v3 errors running on Oracle
---------------------------------

                 Key: JBESB-2978
                 URL: https://jira.jboss.org/jira/browse/JBESB-2978
             Project: JBoss ESB
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Registry and Repository
    Affects Versions: 4.6
            Reporter: Kevin Conner
            Assignee: Kevin Conner
             Fix For: 4.7

Tom Cunningham investigate this and provided the following comment

"Earlier today, Julian found an issue during ESB startup with Oracle and jUDDI :

(10:09:42 AM) jdc: 2009-11-12 15:01:41,758 ERROR [org.hibernate.util.JDBCExceptionReporter] (pool-8-thread-6) ORA-01400: cannot insert NULL into ("SOA"."J3_ADDRESS_LINE"."LINE")

This also happens on one other table - J3_BINDING_DESCR on the DESCR column later in the startup.    

>From what I can see, the issue here is that Oracle treats empty strings as NULLs, and if a column has a NULL constraint on it and you try and insert an empty string, it treats it as a null and throws an error.      We didn't see this in our jUDDI testing because it requires the combination of ESB and jUDDIV3 on Oracle (we used MySQL and Postgres during testing).      Other databases treat empty strings as empty strings, so we didn't see this until now in our testing.

Fixing these two issues would require a change to JAXRRegistryImpl.java in the ESB project and a change to Scout.     I've aspectized the Scout change in the ESB project and I'm sending Kevin/Julian/Trevor the diffs.

This issue can also be easily worked around for testing with a small manual change.      If you let the server startup and fail, the tables will be created.       Then stop the server, and go in and modify the J3_ADDRESS_LINE.LINE column and the J3_BINDING_DESCR.DESCR columns to be NULLABLE.     Then startup again and everything will succeed."

I have his changes and am going to apply the workarounds to our codebase.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira