Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-5319

JMS "sybase-persistence-service.xml" does not work with Sybase.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • EAP_EWP 5.1.1
    • EAP_EWP 5.1.0
    • Messaging
    • None

    • SOA 5.1.0 ER3 (based on EAP 5.1.0 GA)

    • Hide

      Use a default value for "CLIENTID":

      CREATE_USER_TABLE=CREATE TABLE JBM_USER (USER_ID VARCHAR(32) NOT NULL, PASSWD VARCHAR(32) NOT NULL, CLIENTID VARCHAR(128) DEFAULT '', PRIMARY KEY(USER_ID))

      Other options are to allow "NULL" for "CLIENTID", or to specify the "CLIENTID" on all the lines

      POPULATE.TABLES.n = INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ...

      Show
      Use a default value for "CLIENTID": CREATE_USER_TABLE=CREATE TABLE JBM_USER (USER_ID VARCHAR(32) NOT NULL, PASSWD VARCHAR(32) NOT NULL, CLIENTID VARCHAR(128) DEFAULT '', PRIMARY KEY(USER_ID)) Other options are to allow "NULL" for "CLIENTID", or to specify the "CLIENTID" on all the lines POPULATE.TABLES.n = INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ...
    • Not Required

    Description

      Using the JMS persistence service from:

      jboss-eap-5.1/jboss-as/docs/examples/jms/sybase-persistence-service.xml

      with Sybase 15 causes errors of the form:

      2010-10-26 13:15:13,460 DEBUG [org.jboss.jms.server.plugin.JDBCJMSUserManager] (main) Failed to execute INSERT INTO JBM_USER (USER_ID, PASSWD) VALUES ('guest', 'guest')
      com.sybase.jdbc4.jdbc.SybSQLException: The column CLIENTID in table JBM_USER does not allow null values.

      and the entries in the "JBM_USER" table that have no "CLIENTID" defined are not inserted into the database.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-5349 Issue in JBoss Messaging sybase-persistence-service.xml example file

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              mnovak1@redhat.com Miroslav Novak
              rhn-engineering-jcoleman Julian Coleman
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: