Thank you for your answer, The second attempt to install the connectionmanager was a 
test of mine to see if jboss would reach the database, have removed this now.

I Temporarily disabled the log4j.xml file so I have normal logging.

The 3.2.x. database config was also added as a test.. but removed this as well, from 
boot.log I now receive this error still :

11:00:00,966 INFO  [Scheduler] Starting
11:00:00,976 DEBUG [Scheduler] Start Scheduler on start up time
11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::static - BEGIN
11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::initialize - BEGIN
11:00:01,036 DEBUG [ConnectionManager] ConnectionManager:: JNDI name : java:/MySQLDS
11:00:01,036 ERROR [ConnectionManager] NamingException looking up Database DS
11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::static - END
11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::getConnection - BEGIN
11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::initialize - BEGIN
11:00:01,036 DEBUG [ConnectionManager] ConnectionManager:: JNDI name : java:/MySQLDS
11:00:01,036 ERROR [ConnectionManager] javax.naming.NameNotFoundException: MySQLDS not 
bound
11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::getConnection - END
11:00:01,046 WARN  [QueueScheduler] Start-up failed: Database not ready!

Which was my original error I started with, just with more information.

My jboss-service.xml file looks like this internally :


  <!-- ==================================================================== -->
  <!-- XXX JMS Queues                                                       -->
  <!-- ==================================================================== -->
  
    <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
  

  
    <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
  

  
    <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
  

  
         <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
  

  
    <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
  

  
    <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
  

  
    <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
  

  
    <depends 
optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager
     

    <!-- MMX Requeue Scheduler
             Description: Starts a scheduler to check for messages that needs to be 
requeued
             Time interval between tasks: 60 * 1000 (60000) msec
    -->
    
        
        true
        nl.mobileminds.mmx.addon.queueing.QueueScheduler   
        0
        60000
        -1
    

    <!-- MMX QuizMaster Requeue Scheduler
             Description: Starts a scheduler to check for messages that needs to be 
requeued
             Time interval between tasks: 60 * 1000 (60000) msec
    

        true
        nl.mobileminds.application.quizmaster.queueing.QueueScheduler
        0
        30000
        -1
    

    -->
    <!-- MMX Quiz Game Scheduler
             Description: Starts a scheduler to check for messages that needs to be 
requeued
             Time interval between tasks: 60 * 1000 (60000) msec
    

        true
        nl.mobileminds.application.quizmaster.queueing.GameScheduler
        0
        30000
        -1
    

    -->
    <!-- MMX Quiz Cycle Scheduler
             Description: Starts a scheduler to check for messages that needs to be 
requeued
             Time interval between tasks: 60 * 1000 (60000) msec
    

        true
        nl.mobileminds.application.quizmaster.queueing.CycleScheduler
        0
        60000
        -1
    

    -->

  <!-- ==================================================================== -->
  <!-- ConnectionManager setup for MySQL DBMS                               -->
  <!-- ==================================================================== -->

    

        <depends optional-attribute-name="ManagedConnectionFactoryName">

            <!--embedded mbean-->
            

                MySQLDS
                
                    
                        <config-property 
                                name="ConnectionURL"
                                type="java.lang.String">jdbc:mysql://localhost:3306/mmx
                        </config-property>
                        <config-property 
                                name="DriverClass" 
                                type="java.lang.String">com.mysql.jdbc.Driver
                        </config-property>
                        <!--set these only if you want only default logins, not 
through JAAS -->
                        <config-property name="UserName" 
type="java.lang.String">xxx</config-property>
                        <config-property name="Password" 
type="java.lang.String">xxx</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
                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

    



The server is still started with the same property file and it states :
database.jndi.name=java:/MySqlDS 

I Have tried switching the IP inside the DB part around to see if I had my privileges 
right for MySQL, but I had them right, for [EMAIL PROTECTED] may connect, using other 
parts there results in Query and DB connect errors.

It seems as tho the database is being connected to, I can see 2 tables being opened, 
yet somewhere the connectionmanager can not bound to the databases. I checked the code 
of the connectionmanager and it seems to be correct (checked it against information of 
how to do it correct).

Relevant parts of the connectionmanager :

public class ConnectionManager
{
    private static DataSource dataSource = null;
    private static Log logger = LogFactory.getLog(ConnectionManager.class);

    static {
        logger.debug("ConnectionManager::static - BEGIN");

        try {
            initialize();
        } catch (NamingException ne) {
            logger.error("NamingException looking up Database DS");
        }

        logger.debug("ConnectionManager::static - END");
    }


    private static void initialize() throws NamingException {
        logger.debug("ConnectionManager::initialize - BEGIN");

        Context iniCtx = new InitialContext();
        String  dsJndiName = System.getProperty("database.jndi.name.mmx").trim();
        logger.debug("ConnectionManager:: JNDI name : " + dsJndiName);
        if (dsJndiName == null)
            throw new NamingException("Datasource JNDI name not configured.");
        dataSource = (DataSource) iniCtx.lookup(dsJndiName);
        logger.debug("ConnectionManager::initialize - END");
    }

    public static Connection getConnection() throws SQLException
    {
        logger.debug("ConnectionManager::getConnection - BEGIN");
        Connection conn = null;

        try {
            if (dataSource == null) initialize();
            conn = dataSource.getConnection();
        } catch (NamingException ne) {logger.error(ne);}
        logger.debug("ConnectionManager::getConnection - END");
        return conn;
    }

}

Does anyone have any ideas ? If correct this set-up and code should have worked and 
not result in any errors..

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3829927#3829927

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3829927


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to