8 Replies Latest reply on Apr 26, 2004 8:04 AM by Jon Barnett

    Help with an X11 problem - I'm running out of ideas?

    seagull Newbie

      Can anyone shed some light on the following problems?

      I've had an application running successfully for a few months using Linux and jboss-3.0.3_tomcat-4.0.5 and jdk1.3.1_08 but for some reason it now fails when trying to load a dynamic web page with the following error:

      Xlib: connection to "localhost:0.0" refused by server
      Xlib: No protocol specified

      08:56:04,677 ERROR [Engine] ApplicationDispatcher[/weatherContext] Servlet.service() for servlet jsp threw exception
      javax.servlet.ServletException: Can't connect to X11 window server using 'localhost:0.0' as the value of the DISPLAY variable.

      Similar problems reported on other threads suggest running in headless mode but for that I need java 1.4. I loaded on j2sdk1.4.2_04 but with that JBoss won't start-up - it falls over with the error:

      Error occurred during initialization of VM
      java/lang/NoClassDefFoundError: java/lang/Object.

      My next line of attack was to load a later version of Jboss - 3.2.3.
      With that, my application doesn't deploy properly. The following errors are displayed at start up;

      2004-04-23 09:27:46,486 INFO [org.jboss.system.ServiceConfigurator] Problem configuring service jboss.jca:service=LocalTxDS,name=MSSQLD
      S
      org.jboss.deployment.DeploymentException: No Attribute found with name: JndiName
      ...
      ...
      2004-04-23 09:28:11,885 ERROR [org.jboss.ejb.EjbModule] Initialization failed
      org.jboss.deployment.DeploymentException: Failed to find InvokerProxyBindingMetaData for: 'entity-rmi-invoker'. Check the invoker-proxy-
      binding-name to invoker-proxy-binding/name mappings in jboss.xml

      My jboss.xml files are unchanged from jboss3.0.3.

      It seems that everything I try results in different problems!

      If anyone can shed some light on any of the problems, I'd really appreciate it.

      Many thanks,
      Dave Baker.

        • 1. Re: Help with an X11 problem - I'm running out of ideas?
          Jon Barnett Master

          You are probably using the old datasource definition files from 3.0.x in 3.2.x. This won't work as the configuration has been simplified in JBoss 3.2.x and are of a different format. Get the appropriate datasource example file for your database from JBOSS_HOME/docs/examples/jca of the JBoss 3.2.x distribution. Copy that into the deploy directory for JBoss - probably JBOSS_HOME/server/default/deploy. Modify the file for your database login. You can name the file anything you like as long as it ends with -ds.xml so JBoss knows this is a datasource configuration file. That should get rid of your datasource configuration problem.

          • 2. Re: Help with an X11 problem - I'm running out of ideas?
            Richard Barrington Newbie

            I think the first question is why is trying to get a graphics context? I'm guessing you're doing some rendering, and if so, running in headless mode should fix that though (-Djava.awt.headless=true). If you've added X libs recently, maybe the class problem is as simple as running an ldconfig?

            • 3. Re: Help with an X11 problem - I'm running out of ideas?
              Jon Barnett Master

              Rendering is a little more difficult with JDK 1.3.x on Linux/Unix - you need an operating X server, or have JPA or xvfb. Getting running on JBoss 3.2.x with JDK 1.4.x should allow you to move forward without these contortions. Sure you still need the X11 libraries.

              MHO.

              • 4. Re: Help with an X11 problem - I'm running out of ideas?
                seagull Newbie

                Thanks for all your ideas.

                I decided to try and get my application working with Jboss 3.2.2 and Java 1.4.2 on Windows - but still haven't had much luck. There must be some change I need to make to my fully working Jboss3.0.3 version to get it going with Jboss 3.2.2 - I just don't know what it is yet!

                I modified a copy of the mssql_ds.xml file but still get the following error when trying to access my mssql database:

                2004-04-26 09:13:00,973 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException in method: public abstract com.iplbath.I999162.ejb.currentdata.LocalCurrentData com.iplbath.I999162.ejb.currentdata.LocalCurrentDataHome.findByPrimaryKey(java.lang.Integer) throws javax.ejb.FinderException, causedBy:
                javax.ejb.EJBException: ejbFindByPrimaryKey: Unable to connect to database. Could not dereference object

                I must admit, I'm not too sure how the mssql_ds file works - there seems to be a lot less information than in the old mssql-service.xml file.

                I've included them here just in case anyone can help me out in my ignorance!

                Here's the mssql-service file:

                <?xml version="1.0" encoding="UTF-8"?>

                <!-- ===================================================================== -->
                <!-- -->
                <!-- JBoss Server Configuration -->
                <!-- -->
                <!-- ===================================================================== -->



                <!-- ======================================================================-->
                <!-- New ConnectionManager setup for Microsoft SQL Server 2000 driver -->
                <!-- You may download the latest Microsoft JDBC driver from *Microsoft* -->
                <!-- http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/MSDN-FILES/027/001/779/msdncompositedoc.xml&frame=true -->
                <!-- Build jmx-api (build/build.sh all) and view for config documentation -->
                <!-- ===================================================================== -->



                <!-- Include a login module configuration named MSSQLDbRealm.
                Update your login-conf.xml, here is an example for a
                ConfiguredIdentityLoginModule:

                <application-policy name = "MSSQLDbRealm">

                <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
                <module-option name = "principal">sa</module-option>
                <module-option name = "userName">sa</module-option>
                <module-option name = "password">sa</module-option>
                <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=MSSQLDS</module-option>
                </login-module>

                </application-policy>

                NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
                module-option name = "managedConnectionFactoryName"
                must match the object name of the ConnectionManager you are configuring here.
                -->
                <!--uncomment out this line if you are using the MSSQLDbRealm above
                -->
                MSSQLDbRealm

                <depends optional-attribute-name="ManagedConnectionFactoryName">
                <!--embedded mbean-->


                WeatherDB



                <config-property name="ConnectionURL" type="java.lang.String">jdbc:microsoft:sqlserver://PRIS:1433;DatabaseName=MSDE2</config-property>
                <config-property name="DriverClass" type="java.lang.String">com.microsoft.jdbc.sqlserver.SQLServerDriver</config-property>
                <!--set these only if you want only default logins, not through JAAS-->
                <config-property name="UserName" type="java.lang.String"></config-property>
                <config-property name="Password" type="java.lang.String"></config-property>



                <!--Below here are advanced properties -->
                <!--hack-->
                <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper



                <depends optional-attribute-name="ManagedConnectionPool">
                <!--embedded mbean-->


                0
                50
                5000
                15
                <!--criteria indicates if Subject (from security domain) or app supplied
                parameters (such as from getConnection(user, pw)) are used to distinguish
                connections in the pool. Choices are
                ByContainerAndApplication (use both),
                ByContainer (use Subject),
                ByApplication (use app supplied params only),
                ByNothing (all connections are equivalent, usually if adapter supports
                reauthentication)-->
                ByContainer



                <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager

                <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager

                java:/TransactionManager
                <!--make the rar deploy! hack till better deployment-->
                jboss.jca:service=RARDeployer







                ... and here's the mssql_ds file:

                <?xml version="1.0" encoding="UTF-8"?>

                <!-- ===================================================================== -->
                <!-- -->
                <!-- JBoss Server Configuration -->
                <!-- -->
                <!-- ===================================================================== -->

                <!-- $Id: mssql-ds.xml,v 1.1.2.1 2003/09/05 16:38:24 patriot1burke Exp $ -->

                <!-- ======================================================================-->
                <!-- New ConnectionManager setup for Microsoft SQL Server 2000 driver -->
                <!-- You may download the latest Microsoft JDBC driver from *Microsoft* -->
                <!-- http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/MSDN-FILES/027/001/779/msdncompositedoc.xml&frame=true -->
                <!-- ===================================================================== -->


                <local-tx-datasource>
                <jndi-name>MSSQLDS</jndi-name>
                <connection-url>jdbc:microsoft:sqlserver://PRIS:1433;DatabaseName=MSDE2</connection-url>
                <driver-class>com.microsoft.jdbc.sqlserver.SQLServerDriver</driver-class>
                <user-name>"UserName"</user-name>
                "Password"
                <!-- sql to call when connection is created -->
                <new-connection-sql>select * from currentData</new-connection-sql>
                <!-- -->

                <!-- sql to call on an existing pooled connection when it is obtained from pool
                <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
                -->

                </local-tx-datasource>




                The one thing that struck me was that in the mssql-service file there was a line that gived the Jndi name of my database ' WeatherDB' but the mssql_ds didn't appear to have anywhere for that. I tried changing

                <jndi-name>MSSQLDS</jndi-name>
                to
                <jndi-name>WeatherDB</jndi-name>

                but still couldn't get a connection.

                Are there any other files that need changing?


                Any more help would be appreciated.

                Thanks,
                Dave.

                • 5. Re: Help with an X11 problem - I'm running out of ideas?
                  Kabir Khan Master

                  Here's a copy of my mssql-ds.xml, it uses the inet-opta driver (I notice that you have quotes around your username/password)

                  <local-tx-datasource>
                   <jndi-name>JBossJms</jndi-name>
                   <connection-url>jdbc:inetdae7:localhost:1433?database=JBossDefaultDs</connection-url>
                   <driver-class>com.inet.tds.XDataSource</driver-class>
                   <user-name>emuser</user-name>
                   <password>empwd</password>
                   </local-tx-datasource>
                  


                  If you do do a search for "No Attribute found with name: JndiName", a few things you could try come up.

                  One of them is that you might have both the -service.xml and -ds.xml in your deploy folder, if you do delete the -service.xml file.

                  It's hard to say without seeing more of the stack trace, but this error sounds related to a -service.xml file (I ran into this error a while back and that was related to the structure of the -service.xml file also having changed between the versions). So get rid of your -serivce.xml file if it is there and use only the -ds.xml file.

                  • 6. Re: Help with an X11 problem - I'm running out of ideas?
                    seagull Newbie

                    Hi,
                    Thanks for your reply. It was interesting following your suggested thread but I'm still having problems. I checked that there is no mssql-service.xml file in the deploy directory and have tried various settings in the username and password attributes but without success.


                    What I'm puzzled about is that when using jboss3.0.3 I didn't have to specify a username/password - which makes me wonder how I was connecting to the database. Any valid username/password combination I try in Jboss3.2.2 just fails. Is there some new file that Jboss3.2.3 requires?

                    I'll try getting the latest versions of the MS jar files to see if that makes any difference.

                    The latest state of my *_ds.xml file is as follows;


                    <local-tx-datasource>
                    <jndi-name>WeatherDB</jndi-name>
                    <connection-url>jdbc:microsoft:sqlserver://PRIS:1433;DatabaseName=MSDE2</connection-url>
                    <driver-class>com.microsoft.jdbc.sqlserver.SQLServerDriver</driver-class>
                    <user-name>sa</user-name>
                    sa
                    <!-- sql to call when connection is created -->
                    <new-connection-sql>select * from currentData</new-connection-sql>
                    <!-- -->

                    <!-- sql to call on an existing pooled connection when it is obtained from pool
                    <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
                    -->

                    </local-tx-datasource>




                    The error I get is as follows;

                    2004-04-26 12:23:58,311 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection:
                    org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Login failed for user 'sa'.)
                    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:160)
                    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:451)
                    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:212)
                    at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:496)
                    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:425)
                    at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:318)
                    at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:477)
                    at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:814)
                    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:102)
                    at com.iplbath.I999162.ejb.currentdata.CurrentDataBean.makeConnection(CurrentDataBean.java:217)
                    at com.iplbath.I999162.ejb.currentdata.CurrentDataBean.selectByPrimaryKey(CurrentDataBean.java:253)
                    at com.iplbath.I999162.ejb.currentdata.CurrentDataBean.ejbFindByPrimaryKey(CurrentDataBean.java:101)
                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:324)
                    at org.jboss.ejb.plugins.BMPPersistenceManager.callFinderMethod(BMPPersistenceManager.java:585)
                    at org.jboss.ejb.plugins.BMPPersistenceManager.findEntity(BMPPersistenceManager.java:306)
                    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntity(CachedConnectionInterceptor.java:300)
                    at org.jboss.ejb.EntityContainer.findLocal(EntityContainer.java:636)
                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:324)
                    at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1042)
                    at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:197)
                    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:214)
                    at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:88)
                    at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:89)
                    at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61)
                    at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28)
                    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:88)
                    at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:267)
                    at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:98)
                    at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:92)
                    at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:120)
                    at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93)
                    at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:484)
                    at org.jboss.ejb.Container.invoke(Container.java:720)
                    at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invokeHome(BaseLocalProxyFactory.java:293)
                    at org.jboss.ejb.plugins.local.LocalHomeProxy.invoke(LocalHomeProxy.java:110)
                    at $Proxy54.findByPrimaryKey(Unknown Source)
                    at com.iplbath.I999162.ejb.controller.ControllerBean.getCurrentData(ControllerBean.java:261)
                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:324)
                    at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:683)
                    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:185)
                    at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:72)
                    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84)
                    at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:267)
                    at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:128)
                    at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:118)
                    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191)
                    at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
                    at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:331)
                    at org.jboss.ejb.Container.invoke(Container.java:700)
                    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                    at java.lang.reflect.Method.invoke(Method.java:324)
                    at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
                    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
                    at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101)
                    at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:90)
                    at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46)
                    at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:45)
                    at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:100)
                    at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85)
                    at $Proxy61.getCurrentData(Unknown Source)
                    at CurrentBean.populate(CurrentBean.java:55)
                    at Dispatcher.doGet(Dispatcher.java:110)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
                    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
                    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
                    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
                    at HitCounterFilter.doFilter(HitCounterFilter.java:103)
                    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:213)
                    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
                    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
                    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
                    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
                    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
                    at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.invoke(JBossSecurityMgrRealm.java:220)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
                    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:494)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
                    at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
                    at org.jboss.web.tomcat.tc4.statistics.ContainerStatsValve.invoke(ContainerStatsValve.java:76)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
                    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
                    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
                    at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416)
                    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
                    at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
                    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
                    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:65)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
                    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:577)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
                    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
                    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
                    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
                    at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
                    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
                    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
                    at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
                    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601)
                    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
                    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
                    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
                    at java.lang.Thread.run(Thread.java:534)
                    Caused by: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Login failed for user 'sa'.
                    at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
                    at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
                    at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
                    at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
                    at com.microsoft.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
                    at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
                    at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
                    at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
                    at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
                    at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
                    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:150)
                    ... 118 more


                    Many thanks in advance for any more help.

                    • 7. Re: Help with an X11 problem - I'm running out of ideas?
                      Kabir Khan Master

                      Hmm,

                      I'm afraid I can only state the obvious. You're getting further, you were previously getting exceptions at the deploy stage. The datasource now deploys and you're getting problems connecting to the database when trying to use the connection.

                      I'm sure you've done this already, but have you double checked using Query Analyzer that you can log in to the database in question with the given username/password? Is the database name correct etc.

                      • 8. Re: Help with an X11 problem - I'm running out of ideas?
                        Jon Barnett Master

                        It must be mysql-ds.xml not mysql_ds.xml. JBoss identifies a datasource configuration only by the -ds.xml and not any other variation. MHO.