import.sql taking too long (create-drop) - Timing out

[tony.herstell1]

I get this:

21:01:13,003 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "scrams.war" was rolled back with failure message Operation cancelled

21:01:13,003 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [60 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.

21:02:31,403 INFO  [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-10) HHH000230: Schema export complete

Is there a way to extend the timeout??

<persistence-unit name="scramsadministratorDatasource">

                    <provider>org.hibernate.ejb.HibernatePersistence</provider>

                    <jta-data-source>java:/datasources/scramsadministratorDatasource</jta-data-source>

                    <properties>

                              <property name="hibernate.dialect" value="org.hibernate.dialect.MySQL5InnoDBDialect" />

                              <property name="hibernate.hbm2ddl.auto" value="create-drop" /> <!-- create-drop update -->

                              <property name="hibernate.show_sql" value="true" />

                              <property name="hibernate.format_sql" value="true" />

                              <!-- These are the default for JBoss EJB3, but not for HEM: -->

                              <property name="hibernate.cache.provider_class" value="org.hibernate.cache.HashtableCacheProvider" />

                              <property name="hibernate.transaction.manager_lookup_class"

                                        value="org.hibernate.transaction.JBossTransactionManagerLookup" />

                              <property name="jboss.entity.manager.factory.jndi.name"

                                        value="java:/scramsadministratorEntityManagerFactories" />

                    </properties>

          </persistence-unit>

[nickarls]

Yes, there is an attribute for it in the deployment-scanner subsystem (deployment-timeout="300" for example)

[tony.herstell1]

With import.sql

21:22:58,280 ERROR [org.jboss.as] (MSC service thread 1-11) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 132390ms

Vs

Without import.sql

21:25:52,077 ERROR [org.jboss.as] (MSC service thread 1-7) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 13926ms

Something is odd as import.sql not THAT big (4402 lines); works fine on another PC.

After clearing Windows Temp got it down to 121524ms

21:43:47,164 ERROR [org.jboss.as] (MSC service thread 1-3) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 121524ms - Started 491 of 586 services (1 services failed or missing dependencies, 89 services are passive or on-demand)

Must have a slow HDD.

Thx.

[nickarls]

Yes, talk to your boss about that new quadcore beast with 16G mem and a fast SDD. A new 26" monitor might also increase the performance ;-)