Mysql and InnoDB tables
thepriz May 15, 2006 9:10 AMHere is what I am using:
JBossAS 4.0.3SP1
JPortal 2.2.1
MySQL 5.0.21
JConnector 3.1.12
It starts up and creates the tables as InnoDB tables then it gives the following errors:
2006-05-15 06:07:53,193 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/C:/Program Files/jboss-4.0.3SP1/server/default/deploy/jmx-console.war/ -> file:/C:/Program Files/jboss-4.0.3SP1/server/default/deploy/jmx-console.war/WEB-INF/web.xml 2006-05-15 06:07:53,193 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: portal:policy=PortalPolicyConfigStore,type=Component State: FAILED Reason: java.lang.IllegalArgumentException: No transaction manager provided I Depend On: portal:policy=JaccPortalPolicyConfigurator portal:service=TreeCacheProvider,type=transient portal:policy=PortalPolicyConfigService Depends On Me: portal:deploymentFactory=PortletApp ObjectName: portal:deploymentFactory=PortletApp State: CONFIGURED I Depend On: portal:deployer=PortalWebApp portal:service=WebAppRegistry portal:service=ServerConfig portal:policy=PortalPolicyConfigStore,type=Component Depends On Me: portal:deployer=Adapter ObjectName: portal:deployer=Adapter State: CONFIGURED I Depend On: portal:deploymentFactory=Object portal:deploymentFactory=PortletApp portal:deploymentFactory=Layout portal:deploymentFactory=LayoutFeatures portal:deploymentFactory=Theme portal:service=Module,type=User portal:service=Module,type=Role portal:service=Module,type=Mail portal:deployer=PortalWebApp jboss.web:service=WebServer --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: portal:policy=PortalPolicyConfigStore,type=Component State: FAILED Reason: java.lang.IllegalArgumentException: No transaction manager provided I Depend On: portal:policy=JaccPortalPolicyConfigurator portal:service=TreeCacheProvider,type=transient portal:policy=PortalPolicyConfigService Depends On Me: portal:deploymentFactory=PortletApp 2006-05-15 06:07:53,193 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified that enabled: true 2006-05-15 06:07:53,193 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Started jboss.deployment:type=DeploymentScanner,flavor=URL 2006-05-15 06:07:53,193 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.deployment:type=DeploymentScanner,flavor=URL dependent components: [] 2006-05-15 06:07:53,208 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-service.xml 2006-05-15 06:07:53,208 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Program Files/jboss-4.0.3SP1/server/default/conf/jboss-service.xml 2006-05-15 06:07:53,208 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Saw org.jboss.system.server.started notification, starting connectors 2006-05-15 06:07:53,224 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 2006-05-15 06:07:53,271 DEBUG [org.jboss.cache.eviction.LRUAlgorithm] processing the node events in region: Regions--- fqn: /_default_/ maxNodes 1000000 TimeToIdleSeconds 300current eviction queue size is 0 2006-05-15 06:07:53,271 DEBUG [org.jboss.cache.eviction.LRUAlgorithm] processed 0 node events 2006-05-15 06:07:53,302 INFO [org.apache.jk.common.ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009 2006-05-15 06:07:53,302 INFO [org.apache.jk.server.JkMain] Jk running ID=0 time=0/31 config=null 2006-05-15 06:07:53,302 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1 date=200510231751)] Started in 27s:969ms 2006-05-15 06:07:54,271 DEBUG [org.jboss.cache.eviction.LRUAlgorithm] processing the node events in region: Regions--- fqn: /_default_/ maxNodes 1000000 TimeToIdleSeconds 300current eviction queue size is 0
I believe this has something to do with the fact that it creates innoDB tables, but I am not positive. Any suggestions?