[
https://issues.jboss.org/browse/WFLY-5501?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on WFLY-5501:
-------------------------------------
Definitely works for me .
With the right password:
{quote}
10:20:33,237 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.4.Final
10:20:33,471 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
10:20:33,518 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Core
2.0.0.CR8 "Kenny" starting
10:20:34,284 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating
http management service using socket-binding (management-http)
10:20:34,299 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.2.Final
10:20:34,315 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version
3.3.2.Final
10:20:34,330 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node
identifier property is set to the default value. Please make sure it is unique.
10:20:34,330 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38)
WFLYCLINF0001: Activating Infinispan subsystem.
10:20:34,330 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001:
Activating Naming Subsystem
10:20:34,346 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002:
Activating Security Subsystem
10:20:34,346 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007:
Activated the following JSF Implementations: [main]
10:20:34,346 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56)
WFLYWS0002: Activating WebServices Extension
10:20:34,346 INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current
PicketBox version=4.9.3.Final
10:20:34,346 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001:
Worker 'default' has auto-configured to 16 core threads with 128 task threads
based on your 8 available processors
10:20:34,377 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003:
Undertow 1.3.3.Final starting
10:20:34,393 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version
4.0.14.Final
10:20:34,377 INFO [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Starting
JCA Subsystem (WildFly/IronJacamar 1.3.1.Final)
10:20:34,377 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55)
WFLYUT0003: Undertow 1.3.3.Final starting
10:20:34,471 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread
Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version
1.3)
10:20:34,487 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4)
WFLYJCA0018: Started Driver service with driver-name = h2
10:20:34,518 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting
Naming Service
10:20:34,518 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001:
Bound mail session [java:jboss/mail/Default]
10:20:34,518 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread
Pool -- 33) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.mariadb.jdbc.Driver
(version 1.2)
10:20:34,518 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1)
WFLYJCA0018: Started Driver service with driver-name = module_mariadb.jar
10:20:34,596 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55)
WFLYUT0014: Creating file handler for path
'C:\Users\tom\projects\jbosstm\narayana\jboss-as\build\target\wildfly-10.0.0.CR4/welcome-content'
with options [directory-listing: 'false', follow-symlink: 'false',
case-sensitive: 'true', safe-symlink-paths: '[]']
10:20:34,596 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012:
Started server default-server.
10:20:34,612 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018:
Host default-host starting
10:20:34,674 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread
1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/jdbc-store]
10:20:34,674 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool
slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived
from thread worker pool sizing.
10:20:34,690 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0482: Strict pool
mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from
the number of CPUs on this host.
10:20:34,705 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006:
Undertow HTTP listener default listening on 127.0.0.1:8080
10:20:34,784 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1)
WFLYDS0013: Started FileSystemDeploymentService for directory
C:\Users\tom\projects\jbosstm\narayana\jboss-as\build\target\wildfly-10.0.0.CR4\standalone\deployments
10:20:34,862 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread
1-8) ISPN000128: Infinispan version: Infinispan 'Infinite Darkness' 8.0.1.Final
10:20:34,862 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread
1-6) ISPN000128: Infinispan version: Infinispan 'Infinite Darkness' 8.0.1.Final
10:20:34,862 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread
1-4) ISPN000128: Infinispan version: Infinispan 'Infinite Darkness' 8.0.1.Final
10:20:34,862 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread
1-7) ISPN000128: Infinispan version: Infinispan 'Infinite Darkness' 8.0.1.Final
10:20:34,893 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052:
Starting JBoss Web Services - Stack CXF Server 5.1.0.Final
10:20:39,190 WARN [org.mariadb.jdbc.internal.mysql.MySQLProtocol] (MSC service thread
1-5) Could not execute query CREATE TABLE JBossTSTxTable (StateType INTEGER NOT NULL,
Hidden INTEGER NOT NULL, TypeName VARCHAR(255) NOT NULL, UidString VARCHAR(255) NOT NULL,
ObjectState BLOB, PRIMARY KEY(UidString, TypeName, StateType)): Table
'JBossTSTxTable' already exists
10:20:40,049 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread
1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
10:20:40,145 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management
interface listening on
http://127.0.0.1:9990/management
10:20:40,145 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console
listening on
http://127.0.0.1:9990
10:20:40,145 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Core
2.0.0.CR8 "Kenny" started in 7111ms - Started 266 of 496 services (315 services
are lazy, passive or on-demand)
{quote}
In particular I see this line that indicates the config is taking effect:
{quote}
10:20:39,190 WARN [org.mariadb.jdbc.internal.mysql.MySQLProtocol] (MSC service thread
1-5) Could not execute query CREATE TABLE JBossTSTxTable (StateType INTEGER NOT NULL,
Hidden INTEGER NOT NULL, TypeName VARCHAR(255) NOT NULL, UidString VARCHAR(255) NOT NULL,
ObjectState BLOB, PRIMARY KEY(UidString, TypeName, StateType)): Table
'JBossTSTxTable' already exists
{quote}
JDBC Object Store problem with Mariadb55
----------------------------------------
Key: WFLY-5501
URL:
https://issues.jboss.org/browse/WFLY-5501
Project: WildFly
Issue Type: Bug
Components: Transactions
Reporter: Hayk Hovsepyan
Assignee: Tom Jenkinson
Fix For: 10.0.0.CR4
Attachments: mariadb_jar.zip, server.log, standalone.xml
When configuring transactions to use Mariadb55 Datasource as a JDBC Object store, server
fails to start with error:
{code}
13:56:51,485 ERROR [org.jboss.as.controller.management-operation] (Controller Boot
Thread) WFLYCTL0013: Operation ("add") failed - address:
([("subsystem" => "transactions")]) - failure description:
{"WFLYCTL0080: Failed services" =>
{"jboss.txn.ArjunaRecoveryManager" =>
"org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager:
WFLYTX0005: Recovery manager create failed
Caused by: java.lang.NullPointerException"}}
{code}
Steps to reproduce:
1. Create Mariadb55 JDBC driver module. Module archived directory is attached.
2. Add driver into configuration xml.
3. Create Datasource pointing to Mariadb55 database and using driver configured a a
module.
4. Configure transactions to use jdbc-store the added Datasource. standalone.xml is
attached.
5. Server fails to start. server.log is attached.
config xml file part:
{code}
<subsystem xmlns="urn:jboss:domain:datasources:4.0">
<datasources>
<datasource jndi-name="java:jboss/datasources/ExampleDS"
pool-name="ExampleDS" enabled="true"
use-java-context="true">
<connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url>
<driver>h2</driver>
<security>
<user-name>sa</user-name>
<password>sa</password>
</security>
</datasource>
<datasource jta="false"
jndi-name="java:jboss/datasources/jdbc-store"
pool-name="JDBCObjectStore" enabled="true"
use-java-context="true">
<connection-url>jdbc:mariadb://db22.mw.lab.eng.bos.redhat.com:3306/dballo17</connection-url>
<driver>module_mariadb.jar</driver>
<security>
<user-name>dballo17</user-name>
<password>dballo17</password>
</security>
</datasource>
<drivers>
<driver name="h2"
module="com.h2database.h2">
<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
<driver name="module_mariadb.jar"
module="mariadb_jar"/>
</drivers>
</datasources>
</subsystem>
<subsystem xmlns="urn:jboss:domain:transactions:3.0">
<core-environment>
<process-id>
<uuid/>
</process-id>
</core-environment>
<recovery-environment socket-binding="txn-recovery-environment"
status-socket-binding="txn-status-manager"/>
<coordinator-environment enable-tsm-status="true"/>
<jdbc-store
datasource-jndi-name="java:jboss/datasources/jdbc-store"/>
</subsystem>
{code}
Attached necessary info:
1. server.log
2. Module zip to extract in $JBOSS_HOME/modules/system/layers/base
3. standalone.xml
Notes:
The same steps works for other databases.
When step 4. is not executed server starts successfully, so module is recognized.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)