10 Replies Latest reply on Aug 8, 2008 12:25 PM by Jeremy Thornton

    No more console messages after first deployment - jboss work

    null null Newbie

      Hi everybody,

      a simple question: After deploying a simple ejb component, consisting of a session and an entity bean, i get no more deployment messages on my console window. I can see the "deploying xyz" and thats all. I use XP and have tried several jboss versions with the same jar - same results. Console quick edit mode is off an the appserver works! I can redeploy the application, and test it, but there are simply no messages on the console visible. The beans are quite simple and work too. They dont use log4j at all. The server profile doesnt make a difference. Where do I have to search for my problem?

      Regards,
      oliver.

        • 1. Re: No more console messages after first deployment - jboss
          null null Newbie

          No suggestions anyone? This is driving me mad. I cannot imagine that I am the fist to face this. Am I off-topic?

          Greets,
          oliver

          • 2. Re: No more console messages after first deployment - jboss
            jaikiran pai Master

            Which version of JBoss are you using? What other logs do you expect on the console? What does the server.log file unser %JBOSS_HOME%/server/xxx/logs show? Did you try accesing the bean from your application?

            • 3. Re: No more console messages after first deployment - jboss
              null null Newbie

              I am using 4.2.1.GA, but the problem is the same with other versions. I expect deployment- or redeployment-messages or sysouts to the console coming from my beans. Yes i did try to access the beans - as i wrote - the server works and the beans can be called too. I see nothing suspicious in the log files. Shall I post the whole file (800k)? Here you can see the log entries in server.xml for the first time I deploy. This deployment is also being logged to the console. All following un- or redeployments do work too (ejb-changes can be tested by my client), but on the server console you dont see anything. The server.xml has also no information about the un- or redeployment. It seems that the whole logging stops at some point.

              2008-02-07 15:25:59,586 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 44s:984ms
              2008-02-07 15:26:09,150 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass <Do, 7 Feb 2008 15:26:09>
              2008-02-07 15:26:09,150 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] AtomicActionRecoveryModule: Second pass
              2008-02-07 15:26:09,150 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] - TORecoveryModule - second pass
              2008-02-07 15:26:09,150 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - second pass
              2008-02-07 15:28:09,143 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - first pass <Do, 7 Feb 2008 15:28:09>
              2008-02-07 15:28:09,143 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] StatusModule: first pass
              2008-02-07 15:28:09,143 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - first pass
              2008-02-07 15:28:09,143 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass
              2008-02-07 15:28:19,147 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass <Do, 7 Feb 2008 15:28:19>
              2008-02-07 15:28:19,147 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] AtomicActionRecoveryModule: Second pass
              2008-02-07 15:28:19,147 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] - TORecoveryModule - second pass
              2008-02-07 15:28:19,147 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - second pass
              2008-02-07 15:29:59,661 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar
              2008-02-07 15:29:59,661 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar
              2008-02-07 15:29:59,661 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar -> C:\ide\jboss-4.2.1.GA\server\all\tmp\deploy\tmp59349beans.jar
              2008-02-07 15:29:59,671 DEBUG [org.jboss.deployment.MainDeployer] using deployer MBeanProxyExt[jboss.ejb:service=EJBDeployer]
              2008-02-07 15:29:59,671 DEBUG [org.jboss.ejb.EJBDeployer] init, beans.jar
              2008-02-07 15:29:59,702 DEBUG [org.jboss.ejb.EJBDeployer] looking for nested deployments in : file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar
              2008-02-07 15:29:59,702 DEBUG [org.jboss.deployment.DeploymentInfo] createLoaderRepository from config: LoaderRepositoryConfig(repositoryName: JMImplementation:service=LoaderRepository,name=Default, repositoryClassName: null, configParserClassName: null, repositoryConfig: null)
              2008-02-07 15:29:59,702 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@27e353, cl=org.jboss.mx.loading.UnifiedClassLoader3@1bd8993{ url=file:/C:/ide/jboss-4.2.1.GA/server/all/tmp/deploy/tmp59349beans.jar ,addedOrder=0}
              2008-02-07 15:29:59,702 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.UnifiedLoaderRepository3@27e353, cl=org.jboss.mx.loading.UnifiedClassLoader3@1bd8993{ url=file:/C:/ide/jboss-4.2.1.GA/server/all/tmp/deploy/tmp59349beans.jar ,addedOrder=0}
              2008-02-07 15:29:59,702 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] Adding org.jboss.mx.loading.UnifiedClassLoader3@1bd8993{ url=file:/C:/ide/jboss-4.2.1.GA/server/all/tmp/deploy/tmp59349beans.jar ,addedOrder=0}
              2008-02-07 15:29:59,702 DEBUG [org.jboss.deployment.MainDeployer] found 0 subpackages of file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar
              2008-02-07 15:29:59,702 DEBUG [org.jboss.deployment.MainDeployer] Watching new file: file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar
              2008-02-07 15:29:59,702 DEBUG [org.jboss.deployment.MainDeployer] create step for deployment file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar
              2008-02-07 15:29:59,702 DEBUG [org.jboss.ejb.EJBDeployer] create, beans.jar
              2008-02-07 15:30:00,252 DEBUG [org.jboss.ejb.EJBDeployer] Verifying file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar
              2008-02-07 15:30:00,292 DEBUG [org.jboss.ejb.EJBDeployer.verifier] Bean checked: BankAccount: Verified.
              2008-02-07 15:30:00,292 DEBUG [org.jboss.ejb.EJBDeployer.verifier] Bean checked: BruttoNettoBean: Verified.
              2008-02-07 15:30:00,322 DEBUG [org.jboss.ejb.EJBDeployer] Deploying: file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar
              2008-02-07 15:30:00,322 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:service=EjbModule,module=beans.jar
              2008-02-07 15:30:00,322 DEBUG [org.jboss.ejb.EjbModule] Creating jboss.j2ee:service=EjbModule,module=beans.jar
              2008-02-07 15:30:00,322 DEBUG [org.jboss.ejb.EjbModule] createService, begin
              2008-02-07 15:30:00,322 INFO [org.jboss.ejb.EjbModule] Deploying BankAccount
              2008-02-07 15:30:00,352 DEBUG [org.jboss.ejb.EjbModule] Creating WebClassLoader of class org.jboss.web.WebClassLoader
              2008-02-07 15:30:00,393 DEBUG [org.jboss.ejb.EjbModule] creating binding for BankAccountEntityBeanJNDI:entity-unified-invoker
              2008-02-07 15:30:00,423 DEBUG [org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy] Cache policy timer started, tasksTimer=java.util.Timer@1823918
              2008-02-07 15:30:00,443 INFO [org.jboss.ejb.EjbModule] Deploying BruttoNettoBean
              2008-02-07 15:30:00,463 DEBUG [org.jboss.ejb.EjbModule] Creating WebClassLoader of class org.jboss.web.WebClassLoader
              2008-02-07 15:30:00,483 DEBUG [org.jboss.ejb.EjbModule] creating binding for BruttoNettoBeanJNDI:stateful-unified-invoker
              2008-02-07 15:30:00,493 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:jndiName=BankAccountEntityBeanJNDI,service=EJB
              2008-02-07 15:30:00,493 DEBUG [org.jboss.system.ServiceController] adding depends in ServiceController.register: []
              2008-02-07 15:30:00,493 DEBUG [org.jboss.ejb.EntityContainer] Creating jboss.j2ee:jndiName=BankAccountEntityBeanJNDI,service=EJB
              2008-02-07 15:30:00,513 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:service=EJB,plugin=pool,jndiName=BankAccountEntityBeanJNDI
              2008-02-07 15:30:00,513 DEBUG [org.jboss.ejb.plugins.EntityInstancePool] Creating jboss.j2ee:service=EJB,plugin=pool,jndiName=BankAccountEntityBeanJNDI
              2008-02-07 15:30:00,513 DEBUG [org.jboss.ejb.plugins.EntityInstancePool] Created jboss.j2ee:service=EJB,plugin=pool,jndiName=BankAccountEntityBeanJNDI
              2008-02-07 15:30:00,513 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.j2ee:service=EJB,plugin=pool,jndiName=BankAccountEntityBeanJNDI dependents are: []
              2008-02-07 15:30:01,084 DEBUG [org.jboss.proxy.ejb.ProxyFactory] Proxy Factory for BankAccountEntityBeanJNDI initialized
              2008-02-07 15:30:01,094 DEBUG [org.jboss.ejb.EntityContainer] Created jboss.j2ee:jndiName=BankAccountEntityBeanJNDI,service=EJB
              2008-02-07 15:30:01,094 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.j2ee:jndiName=BankAccountEntityBeanJNDI,service=EJB dependents are: []
              2008-02-07 15:30:01,094 DEBUG [org.jboss.ejb.EjbModule] Bound jmxName=jboss.j2ee:jndiName=BankAccountEntityBeanJNDI,service=EJB, hash=-1033608632into Registry
              2008-02-07 15:30:01,094 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:jndiName=BruttoNettoBeanJNDI,service=EJB
              2008-02-07 15:30:01,094 DEBUG [org.jboss.system.ServiceController] adding depends in ServiceController.register: []
              2008-02-07 15:30:01,094 DEBUG [org.jboss.ejb.StatefulSessionContainer] Creating jboss.j2ee:jndiName=BruttoNettoBeanJNDI,service=EJB
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.StatefulSessionContainer] Mapped info HASH -177545549to public java.util.Properties ejb.bruttonetto.BruttoNettoBean.info()
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.StatefulSessionContainer] Mapped getNetto HASH -2122264257to public double ejb.bruttonetto.BruttoNettoBean.getNetto(double)
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.StatefulSessionContainer] Mapped getBrutto HASH -409681219to public double ejb.bruttonetto.BruttoNettoBean.getBrutto(double)
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.StatefulSessionContainer] Mapped Container method remove HASH -1842617161
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.StatefulSessionContainer] Mapped Container method isIdentical HASH 285457048
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.StatefulSessionContainer] Mapped Container method getHandle HASH 1182305581
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.StatefulSessionContainer] Mapped Container method getEJBHome HASH -993218923
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.StatefulSessionContainer] Mapped Container method getPrimaryKey HASH -131865408
              2008-02-07 15:30:01,104 DEBUG [org.jboss.proxy.ejb.ProxyFactory] Proxy Factory for BruttoNettoBeanJNDI initialized
              2008-02-07 15:30:01,104 DEBUG [org.jboss.system.ServiceController] Creating service jboss.j2ee:service=EJB,plugin=pool,jndiName=BruttoNettoBeanJNDI
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.plugins.StatefulSessionInstancePool] Creating jboss.j2ee:service=EJB,plugin=pool,jndiName=BruttoNettoBeanJNDI
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.plugins.StatefulSessionInstancePool] Created jboss.j2ee:service=EJB,plugin=pool,jndiName=BruttoNettoBeanJNDI
              2008-02-07 15:30:01,104 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.j2ee:service=EJB,plugin=pool,jndiName=BruttoNettoBeanJNDI dependents are: []
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Creating StatefulSessionFilePersistenceManager
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Storing sessions for 'BruttoNettoBean' in: C:\ide\jboss-4.2.1.GA\server\all\tmp\sessions\BruttoNettoBean-fcdep7yo-7
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Purging all session data in: C:\ide\jboss-4.2.1.GA\server\all\tmp\sessions\BruttoNettoBean-fcdep7yo-7
              2008-02-07 15:30:01,104 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Created StatefulSessionFilePersistenceManager
              2008-02-07 15:30:01,124 DEBUG [org.jboss.ejb.StatefulSessionContainer] Created jboss.j2ee:jndiName=BruttoNettoBeanJNDI,service=EJB
              2008-02-07 15:30:01,124 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.j2ee:jndiName=BruttoNettoBeanJNDI,service=EJB dependents are: []
              2008-02-07 15:30:01,124 DEBUG [org.jboss.ejb.EjbModule] Bound jmxName=jboss.j2ee:jndiName=BruttoNettoBeanJNDI,service=EJB, hash=1554929794into Registry
              2008-02-07 15:30:01,124 DEBUG [org.jboss.ejb.EjbModule] Created jboss.j2ee:service=EjbModule,module=beans.jar
              2008-02-07 15:30:01,124 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.j2ee:service=EjbModule,module=beans.jar dependents are: []
              2008-02-07 15:30:01,124 DEBUG [org.jboss.deployment.MainDeployer] Done with create step of deploying beans.jar
              2008-02-07 15:30:01,124 DEBUG [org.jboss.deployment.MainDeployer] Begin deployment start file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar
              2008-02-07 15:30:01,124 DEBUG [org.jboss.ejb.EJBDeployer] start application, deploymentInfo: org.jboss.deployment.DeploymentInfo@3ccb22bf { url=file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar }
              deployer: MBeanProxyExt[jboss.ejb:service=EJBDeployer]
              status: Starting
              state: START_DEPLOYER
              watch: file:/C:/ide/jboss-4.2.1.GA/server/all/deploy/beans.jar
              altDD: null
              lastDeployed: 1202394599702
              lastModified: 1202394599661
              mbeans:
              jboss.j2ee:jndiName=BankAccountEntityBeanJNDI,service=EJB state: Created
              jboss.j2ee:jndiName=BruttoNettoBeanJNDI,service=EJB state: Created
              , short name: beans.jar, parent short name: null
              2008-02-07 15:30:01,124 DEBUG [org.jboss.system.ServiceController] starting service jboss.j2ee:service=EjbModule,module=beans.jar
              2008-02-07 15:30:01,124 DEBUG [org.jboss.ejb.EjbModule] Starting jboss.j2ee:service=EjbModule,module=beans.jar
              2008-02-07 15:30:01,124 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.BankAccount] Initializing CMP plugin for BankAccount
              2008-02-07 15:30:01,144 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.BankAccount] Loading standardjbosscmp-jdbc.xml : file:/C:/ide/jboss-4.2.1.GA/server/all/conf/standardjbosscmp-jdbc.xml
              2008-02-07 15:30:01,684 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.BankAccount] jar:file:/C:/ide/jboss-4.2.1.GA/server/all/tmp/deploy/tmp59349beans.jar!/META-INF/jbosscmp-jdbc.xml found. Overriding defaults
              2008-02-07 15:30:01,795 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool: registering pool with interval 900000 old interval: 9223372036854775807
              2008-02-07 15:30:01,795 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool: about to notify thread: old next: 1202395051795, new next: 1202395051795


              • 4. Re: No more console messages after first deployment - jboss
                jaikiran pai Master

                I just gave this a try on my local setup. Going by your logs, it appears that you have placed beans.jar in the deploy folder and the beans.jar contains EJB2 beans. I used a similar application named myapp_ejb2.jar and placed it in deploy folder. Started JBoss. Here's what i see on the console:

                20:39:39,739 INFO [EjbModule] Deploying HelloWorldBean
                20:39:39,989 INFO [ProxyFactory] Bound EJB Home 'HelloWorldBean' to jndi 'HelloWorld'
                20:39:39,989 INFO [EJBDeployer] Deployed: file:/D:/JBoss-4.2.2/jboss-4.2.2.GA/server/jaikiran/deploy/myapp_ejb2.jar/

                Then i 'touched' the ejb-jar.xml to redeploy this application. Here's the logs that i see:
                20:40:05,646 INFO [EJBDeployer] Undeploying: file:/D:/JBoss-4.2.2/jboss-4.2.2.GA/server/jaikiran/deploy/myapp_ejb2.jar/
                20:40:05,661 INFO [ProxyFactory] Unbind EJB Home 'HelloWorldBean' from jndi 'HelloWorld'
                20:40:05,661 INFO [EjbModule] Undeployed HelloWorldBean
                20:40:05,849 INFO [EjbModule] Deploying HelloWorldBean
                20:40:06,021 INFO [ProxyFactory] Bound EJB Home 'HelloWorldBean' to jndi 'HelloWorld'
                20:40:06,021 INFO [EJBDeployer] Deployed: file:/D:/JBoss-4.2.2/jboss-4.2.2.GA/server/jaikiran/deploy/myapp_ejb2.jar/


                Looks fine for me. Can you search for the string [EJBDeployer] Deployed: in your server.log?

                • 5. Re: No more console messages after first deployment - jboss
                  null null Newbie

                  After the first deployment the only thing i can see is:

                  15:25:59,586 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 44s:984ms
                  15:30:00,322 INFO [EjbModule] Deploying BankAccount
                  15:30:00,443 INFO [EjbModule] Deploying BruttoNettoBean

                  Nothing further, even on redeployment. I cant find an "[EJBDeployer] deployed" in my server.log . Only the logs I posted in my message before. I get the impression, that something in the logging engine crashes. It must have to do with my archive, otherwise this would not happen on other jboss versions... But what causes the log engine to crash and doesnt affect the functionality of the ejbs?

                  • 6. Re: No more console messages after first deployment - jboss
                    jaikiran pai Master

                    I wouldn't say, the logging engine is crashing. Have you done any changes in the jboss-log4j.xml file which is present in C:\ide\jboss-4.2.1.GA\server\all\conf folder? Or do you have any log4j.properties or log4j.xml file packaged in your application?

                    • 7. Re: No more console messages after first deployment - jboss
                      null null Newbie

                      I'm getting nearer to our solution. No there are no logging changes - the server was extracted brand new. BUT! I changed the bean archive and removed my entity bean. Now I'm getting exactly the log messages you posted and the console stays "alive". Deployments and undeployments are logged! Everything works, when I delete those two sections

                      In the ejb-jar.xml:


                      <ejb-name>BankAccount</ejb-name>
                      ejb.bankaccount.BankAccountHome
                      ejb.bankaccount.BankAccount
                      <ejb-class>ejb.bankaccount.BankAccountBean</ejb-class>
                      <persistence-type>Container</persistence-type>
                      <prim-key-class>java.lang.String</prim-key-class>
                      False
                      <cmp-version>2.x</cmp-version>
                      <abstract-schema-name>AccountBeanAPS</abstract-schema-name>
                      <cmp-field>
                      Die Kontonummer
                      <field-name>accountNumber</field-name>
                      </cmp-field>
                      <cmp-field>
                      Die Kontobeschreibung
                      <field-name>accountDescription</field-name>
                      </cmp-field>
                      <cmp-field>
                      Der Kontostand
                      <field-name>accountBalance</field-name>
                      </cmp-field>
                      <primkey-field>accountNumber</primkey-field>


                      in jboss.xml:


                      <ejb-name>BankAccount</ejb-name>
                      <jndi-name>BankAccountEntityBeanJNDI</jndi-name>


                      This is crazy! The entity bean works fine, when I reintegrate the passages. But no more console messages! What the hell could be wrong? Eventually the jbosscmp-jdbc.xml?

                      <?xml version="1.0" encoding="iso-8859-1" ?>
                      <!DOCTYPE jbosscmp-jdbc PUBLIC "-//JBoss//DTD JBOSSCMP-JDBC 4.0//EN" "http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_4_0.dtd">
                      <!-- Beschreibung der persistenzabhängigen Deploymentdaten -->
                      <jbosscmp-jdbc>
                      <!-- Globale Einstellungen, können in den Bean-Einstellungen
                      überschrieben werden. -->

                      <!-- Beschreibung des Herstellernamens für die Datenquelle -->
                      java:/EjbDataSource
                      <!-- Beschreibung der Datentypangleichungen für die Datenquelle -->
                      <datasource-mapping>mySQL</datasource-mapping>
                      <!-- Soll die Tabelle beim Deployment erzeugt werden? -->
                      <create-table>true</create-table>
                      <!-- Soll die Tabelle beim Undeployment gelöscht werden? -->
                      <remove-table>true</remove-table>
                      <!-- Wichtig! Sonst funktioniert die Bean nicht! -->
                      <read-only>false</read-only>


                      <!-- Beziehungen zwischen den Bean-Attributen und der Datenquelle -->
                      <enterprise-beans>
                      <!-- Beschreibung einer Bean aus dem JAR-File -->

                      <!-- Anweisungen zur Vorinitialisierung -->

                      <!-- Name der Bean -->
                      <ejb-name>BankAccount</ejb-name>

                      <post-table-create>
                      <sql-statement>insert into Account values ( "0001", "Oliver Schell", 1578.28 )</sql-statement>
                      <sql-statement>insert into Account values ( "0004", "Kroesus", 12578.37 )</sql-statement>
                      <sql-statement>insert into Account values ( "0005", "Armer Mann", 10.82 )</sql-statement>
                      </post-table-create>

                      <!-- Zieltabelle -->
                      <table-name>Account</table-name>
                      <!-- Zusammenhänge zwischen den persistenten Attributen
                      und den Tabellenspalten. -->
                      <cmp-field>
                      <field-name>accountNumber</field-name>
                      <column-name>acno</column-name>
                      </cmp-field>
                      <cmp-field>
                      <field-name>accountDescription</field-name>
                      <column-name>acdesc</column-name>
                      </cmp-field>
                      <cmp-field>
                      <field-name>accountBalance</field-name>
                      <column-name>acbal</column-name>
                      </cmp-field>


                      </enterprise-beans>
                      </jbosscmp-jdbc>

                      No idea...

                      • 8. Re: No more console messages after first deployment - jboss
                        jaikiran pai Master

                        In my case, i did not have entity beans (i have never used them before). So yes, maybe if entity beans are deployed, there might be no logging. But this does not mean that something has gone wrong. Maybe the implementation for deploying entity beans doesn't log any messages about deployment completion.

                        • 9. Re: No more console messages after first deployment - jboss
                          null null Newbie

                          Ok, but i hope you understood me well: Once I have deployed the entity, I'm getting no more logs at all. Even if I undeploy something or force an exception by deploying a crapped bean - the log hangs at the first deployment of this entity. No stacktraces, no infos, no System.outs. This cannot be intended.

                          • 10. Re: No more console messages after first deployment - jboss
                            Jeremy Thornton Newbie

                            I am having the same problem as the OP. Was there ever a resolution to this?