[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-915) Sybase Persistence Problem - CLUSTERED is a keyword

Tim Fox (JIRA) jira-events at lists.jboss.org
Wed Apr 11 06:17:58 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBMESSAGING-915?page=all ]

Tim Fox updated JBMESSAGING-915:
--------------------------------

    Fix Version/s: 1.2.0.SP2
                       (was: Unscheduled)
         Assignee: Tim Fox  (was: Ovidiu Feodorov)

> Sybase Persistence Problem - CLUSTERED is a keyword
> ---------------------------------------------------
>
>                 Key: JBMESSAGING-915
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-915
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: Messaging Core Persistence
>    Affects Versions: 1.2.0.GA
>         Environment: Windows XP/Linux gentoo (dev); Adaptive Server Enterprise/12.5.3/EBF 13339 ESD#7/P/x86_64/Enterprise Linux/ase1253/1951/64-bit/OPT/Fri Mar 24 00:39:11 2006; Java 5 Update 11
>            Reporter: Radim Marek
>         Assigned To: Tim Fox
>             Fix For: 1.2.0.SP2
>
>
> examples/config sybase-persistence-service.xml is used using CLUSTERD as column name and it's keyword in Sybase.
> --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
> ObjectName: jboss.messaging:service=PostOffice
>   State: FAILED
>   Reason: com.sybase.jdbc3.jdbc.SybSQLException: Incorrect syntax near the keyword 'CLUSTERED'.
>   I Depend On:
>     jboss.messaging:service=ServerPeer
>     jboss.jca:service=DataSourceBinding,name=DefaultDS
>     jboss:service=TransactionManager
>   Depends On Me:
>     jboss.messaging.connectionfactory:service=ConnectionFactory
>     jboss.messaging.connectionfactory:service=NonClusteredConnectionFactory
>     jboss.messaging.destination:service=Queue,name=DLQ
>     jboss.messaging.destination:service=Queue,name=ExpiryQueue
>     jboss.messaging.destination:service=Topic,name=testTopic
>     jboss.messaging.destination:service=Topic,name=securedTopic
>     jboss.messaging.destination:service=Topic,name=testDurableTopic
>     jboss.messaging.destination:service=Queue,name=testQueue
>     jboss.messaging.destination:service=Queue,name=A
>     jboss.messaging.destination:service=Queue,name=B
>     jboss.messaging.destination:service=Queue,name=C
>     jboss.messaging.destination:service=Queue,name=D
>     jboss.messaging.destination:service=Queue,name=ex
>     jboss.messaging.destination:service=Queue,name=PrivateDLQ
>     jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue
>     jboss.messaging.destination:service=Queue,name=QueueWithOwnDLQAndExpiryQueue
>     jboss.messaging.destination:service=Topic,name=TopicWithOwnDLQAndExpiryQueue
>     jboss.messaging.destination:service=Queue,name=QueueWithOwnRedeliveryDelay
>     jboss.messaging.destination:service=Topic,name=TopicWithOwnRedeliveryDelay
>     jboss.messaging.destination:service=Queue,name=testDistributedQueue
>     jboss.messaging.destination:service=Topic,name=testDistributedTopic

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

        



More information about the jboss-jira mailing list