[JBoss Tools (users)] - Re: continuos redeployment of seam with birt
by netdrag
I hope this works
| 009-08-18 01:44:57,227 INFO [org.hibernate.impl.SessionFactoryObjectFactory] (HDScanner) Factory name: persistence.unit:unitName=#xeric
| 2009-08-18 01:44:57,231 INFO [org.hibernate.util.NamingHelper] (HDScanner) JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2009-08-18 01:44:57,240 INFO [org.hibernate.impl.SessionFactoryObjectFactory] (HDScanner) Bound factory to JNDI name: persistence.unit:unitName=#xeric
| 2009-08-18 01:44:57,241 WARN [org.hibernate.impl.SessionFactoryObjectFactory] (HDScanner) InitialContext did not implement EventContext
| 2009-08-18 01:44:57,266 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (HDScanner) Running hbm2ddl schema update
| 2009-08-18 01:44:57,267 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (HDScanner) fetching database metadata
| 2009-08-18 01:44:57,272 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (HDScanner) updating schema
| 2009-08-18 01:44:57,277 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (HDScanner) schema update complete
| 2009-08-18 01:44:57,281 INFO [org.hibernate.util.NamingHelper] (HDScanner) JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2009-08-18 01:44:57,340 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) deploy, ctxPath=/xeric
| 2009-08-18 01:44:57,522 INFO [javax.enterprise.resource.webcontainer.jsf.config] (HDScanner) Initializing Mojarra (1.2_12-b01-FCS) for context '/xeric'
| 2009-08-18 01:45:02,210 INFO [javax.servlet.ServletContextListener] (HDScanner) Welcome to Seam 2.0.2.SP1
| 2009-08-18 01:45:06,088 INFO [org.hibernate.cfg.search.HibernateSearchEventListenerRegister] (HDScanner) Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled.
| 2009-08-18 01:45:06,090 INFO [org.hibernate.util.NamingHelper] (HDScanner) JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2009-08-18 01:45:06,090 INFO [org.hibernate.connection.DatasourceConnectionProvider] (HDScanner) Using datasource: java:/xericDatasource
| 2009-08-18 01:45:06,091 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) RDBMS: PostgreSQL, version: 8.4.0
| 2009-08-18 01:45:06,091 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) JDBC driver: PostgreSQL Native Driver, version: PostgreSQL 8.3 JDBC4 with SSL (build 604)
| 2009-08-18 01:45:06,091 INFO [org.hibernate.dialect.Dialect] (HDScanner) Using dialect: org.hibernate.dialect.PostgreSQLDialect
| 2009-08-18 01:45:06,092 INFO [org.hibernate.transaction.TransactionFactoryFactory] (HDScanner) Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory
| 2009-08-18 01:45:06,092 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] (HDScanner) instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup
| 2009-08-18 01:45:06,093 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] (HDScanner) instantiated TransactionManagerLookup
| 2009-08-18 01:45:06,093 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Automatic flush during beforeCompletion(): disabled
| 2009-08-18 01:45:06,093 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Automatic session close at end of transaction: disabled
| 2009-08-18 01:45:06,094 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) JDBC batch size: 15
| 2009-08-18 01:45:06,094 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) JDBC batch updates for versioned data: disabled
| 2009-08-18 01:45:06,094 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Scrollable result sets: enabled
| 2009-08-18 01:45:06,094 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) JDBC3 getGeneratedKeys(): disabled
| 2009-08-18 01:45:06,094 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Connection release mode: auto
| 2009-08-18 01:45:06,094 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Default batch fetch size: 1
| 2009-08-18 01:45:06,094 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Generate SQL with comments: disabled
| 2009-08-18 01:45:06,094 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Order SQL updates by primary key: disabled
| 2009-08-18 01:45:06,094 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Order SQL inserts for batching: disabled
| 2009-08-18 01:45:06,094 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
| 2009-08-18 01:45:06,095 INFO [org.hibernate.hql.ast.ASTQueryTranslatorFactory] (HDScanner) Using ASTQueryTranslatorFactory
| 2009-08-18 01:45:06,095 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Query language substitutions: {}
| 2009-08-18 01:45:06,095 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) JPA-QL strict compliance: enabled
| 2009-08-18 01:45:06,095 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Second-level cache: enabled
| 2009-08-18 01:45:06,095 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Query cache: disabled
| 2009-08-18 01:45:06,096 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Cache region factory : org.hibernate.cache.impl.NoCachingRegionFactory
| 2009-08-18 01:45:06,097 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Optimize cache for minimal puts: disabled
| 2009-08-18 01:45:06,097 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Structured second-level cache entries: disabled
| 009-08-18 01:45:06,097 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Echoing all SQL to stdout
| 2009-08-18 01:45:06,097 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Statistics: disabled
| 2009-08-18 01:45:06,097 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Deleted entity synthetic identifier rollback: disabled
| 2009-08-18 01:45:06,097 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Default entity-mode: pojo
| 2009-08-18 01:45:06,098 INFO [org.hibernate.cfg.SettingsFactory] (HDScanner) Named query checking : enabled
| 2009-08-18 01:45:06,106 INFO [org.hibernate.impl.SessionFactoryImpl] (HDScanner) building session factory
| 2009-08-18 01:45:06,106 INFO [org.hibernate.impl.SessionFactoryObjectFactory] (HDScanner) Not binding factory to JNDI, no JNDI name configured
| 2009-08-18 01:45:06,107 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (HDScanner) Running hbm2ddl schema update
| 2009-08-18 01:45:06,107 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (HDScanner) fetching database metadata
| 2009-08-18 01:45:06,108 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (HDScanner) updating schema
| 2009-08-18 01:45:06,109 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (HDScanner) schema update complete
| 2009-08-18 01:45:06,109 INFO [org.hibernate.util.NamingHelper] (HDScanner) JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2009-08-18 01:45:17,881 WARN [org.jboss.virtual.plugins.context.AbstractVirtualFileHandler] (HDScanner) No such existing handler, falling back to old root + path: vfsfile:/home/er/J2EE/workspace/eric/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server/deploy/xeric.war/documents
| 2009-08-18 01:45:26,435 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/xeric
| 2009-08-18 01:45:26,440 INFO [org.hibernate.impl.SessionFactoryImpl] (HDScanner) closing
| 2009-08-18 01:45:31,804 INFO [org.jboss.jpa.deployment.PersistenceUnitDeployment] (HDScanner) Stopping persistence unit persistence.unit:unitName=#xeric
| 2009-08-18 01:45:31,804 INFO [org.hibernate.impl.SessionFactoryImpl] (HDScanner) closing
| 2009-08-18 01:45:31,804 INFO [org.hibernate.impl.SessionFactoryObjectFactory] (HDScanner) Unbinding factory from JNDI name: persistence.unit:unitName=#xeric
| 2009-08-18 01:45:31,805 INFO [org.hibernate.util.NamingHelper] (HDScanner) JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
| 2009-08-18 01:45:31,805 INFO [org.hibernate.impl.SessionFactoryObjectFactory] (HDScanner) Unbound factory from JNDI name: persistence.unit:unitName=#xeric
| 2009-08-18 01:45:39,300 INFO [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (HDScanner) Encountered deployment AbstractVFSDeploymentContext@25934841{vfsfile:/home/er/J2EE/workspace/eric/.metadata/.plugins/org.jboss.ide.eclipse.as.c
| ore/JBoss_5.1_Runtime_Server/deploy/xeric.war/}
| 2009-08-18 01:45:39,301 INFO [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (HDScanner) Encountered deployment AbstractVFSDeploymentContext@25934841{vfsfile:/home/er/J2EE/workspace/eric/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server/deploy/xeric.war/}
| 2009-08-18 01:45:39,301 INFO [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer] (HDScanner) Encountered deployment AbstractVFSDeploymentContext@25934841{vfsfile:/home/er/J2EE/workspace/eric/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_Server/deploy/xeric.war/}
| 2009-08-18 01:45:39,315 INFO [org.jboss.jpa.deployment.PersistenceUnitDeployment] (HDScanner) Starting persistence unit persistence.unit:unitName=#xeric
| 2009-08-18 01:45:39,318 INFO [org.hibernate.ejb.Ejb3Configuration] (HDScanner) Processing PersistenceUnitInfo [
| name: xeric
| ...]
| 2009-08-18 01:45:39,319 WARN [org.hibernate.ejb.Ejb3Configuration] (HDScanner) Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null.
| 2009-08-18 01:45:39,337 INFO [org.hibernate.cfg.search.HibernateSearchEventListenerRegister] (HDScanner) Unable to find org.hibernate.search.event.FullTextIndexEventListener on the classpath. Hibernate Search is not enabled.
| 2009-08-18 01:45:39,338 INFO [org.hibernate.connection.ConnectionProviderFactory] (HDScanner) Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
| 2009-08-18 01:45:39,339 INFO [org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider] (HDScanner) Using provided datasource
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250106#4250106
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250106
16 years, 10 months
[Persistence, JBoss/CMP, Hibernate, Database] - JBoss does not reconnect after mysql-server restart
by wasu
Hello,
I am using JBoss 4.2.2, mysql-connector-java-5.1.5 and mysql-server 5.1.
I sometimes have to restart my mysql-server (/etc/init.d/mysql restart). However, when I do this, JBoss does not reconnect. I get com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure.
My question: How can I configure JBoss to automatically reconnect when I manually restart my mysql-server?
Here is my mysql-ds.xml configuration:
| <local-tx-datasource>
| <jndi-name>meetings</jndi-name>
| <connection-url>jdbc:mysql://localhost:3306/meetings</connection-url>
| <driver-class>com.mysql.jdbc.Driver</driver-class>
| <user-name>userame</user-name>
| <password>password</password>
| <valid-connection-checker-classname>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-classname>
| <metadata>
| <type-mapping>mySQL</type-mapping>
| </metadata>
| </local-tx-datasource>
|
I have also tried to use the reconnect property in mysql-ds.xml, however with no success
<connection-property name="autoReconnect">true</connection-property>
Besides, In the documentation I have read not to use this.
Please help. I need the database-connection to be reconnected after the mysql-server restart.
Regards,
Walter
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250094#4250094
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250094
16 years, 10 months
[Microcontainer] - Re: Class loading conflict
by objectiser
Hi Ales
Using the same domains in the riftsaw.esb and sar worked fine, but introduced another problem when I deployed some ESB examples that depended upon the action I had defined in the riftsaw.esb, and I don't think it would be a good idea for me to set the domain inside the ESB example to be based on riftsaw, as an ESB service in reality maybe using a number of other thirdparty custom ESB actions - and I assume it cannot be part of multiple domains?
So I thought it best to outline the overall scenario, to see whether there is a good overall solution, rather than presenting the side effects of each individual change as I have currently being doing.
1) The riftsaw.sar, which had the original jar conflict, is not dependent upon JbossESB. It does however have some interfaces that need to be used externally.
2) If the JBossESB integration is being used, then currently there is a single BPEL invoke action that needs to access the interface from the riftsaw.sar
3) Other ESB services - that may need to use the BPELInvoke action. Currently ESB services don't need to do anything specific in their configuration to pick up ESB actions defined in other .esb modules - so either this approach needs to continue, or an approach needs to be used that would enable the ESB example to reference multiple ESB actions potentially defined in different isolation domains.
Hope this gives a clearer outline of the dependencies and what we are wanting to achieve.
Regards
Gary
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250085#4250085
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250085
16 years, 10 months