[jboss-jira] [JBoss JIRA] Closed: (JBAS-4169) Fix a typo in docs\examples\jms\derby-jdbc2-service.xml

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4169?page=all ]

Adrian Brock closed JBAS-4169.
------------------------------

    Fix Version/s:     (was: JBossAS-4.2.0.GA)
       Resolution: Duplicate Issue
         Assignee:     (was: Dimitris Andreadis)

Duplicate of JBAS-3785

Please use search.

> Fix a typo in docs\examples\jms\derby-jdbc2-service.xml
> -------------------------------------------------------
>
>                 Key: JBAS-4169
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4169
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JCA service
>    Affects Versions: JBossAS-4.0.5.GA
>         Environment: WindowsXP with JDK 6, although irrelevant for the issue at hand.
>            Reporter: Panagiotis Astithas
>
> There is a typo in JBOSS_HOME\docs\examples\jms\derby-jdbc2-service.xml that generates errors when using it to configure Derby as the default data source for the JMS system. The typo is in the PersistenceManager mbean definition:
> <mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager" name="jboss.mq:service=PersistenceManager">
> Specifically in line 66 (in my editor at least) there is the string "EXITS" instead of the correct "EXISTS". Without this small change an SQL error is displayed in the server log:
> 14:34:02,233 WARN  [ServiceController] Problem starting service jboss.mq:service=PersistenceManager org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions.  Message recovery may not be accurate; - nested throwable: (java.sql.SQLSyntaxErrorException: Syntax error: Encountered "SELECT" at line 1, column 39.)
>         at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:492)
>         at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1809)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
>         at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
>         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
>         at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
>         at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
>         at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
>         at $Proxy0.start(Unknown Source)
>         at org.jboss.system.ServiceController.start(ServiceController.java:417)
>         at org.jboss.system.ServiceController.start(ServiceController.java:435)
>         at org.jboss.system.ServiceController.start(ServiceController.java:435)
>         at org.jboss.system.ServiceController.start(ServiceController.java:435)
>         at org.jboss.system.ServiceController.start(ServiceController.java:435)
>         at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> [...]

-- 
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