5:49 a.m.
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer bit
not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:07 a.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
jaikiran pai resolved EJBTHREE-2152.
------------------------------------
Component Fix Version(s): timerservice-mk2:1.0.0-alpha-8
Fix Version/s: depchain-1.0.0
Resolution: Done
Done
http://github.com/jbossejb3/jboss-ejb3-timerservice/commit/56494a6cdc539a...
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:57 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
Frank Cornelis commented on EJBTHREE-2152:
------------------------------------------
I still receive the following error:
16:28:41,330 ERROR [SchemaUpdate] Unsuccessful: create table timer (id varchar(255) not
null, info longblob, initialDate datetime, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
16:28:41,330 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
Seems like "interval" is a reserved word in MySQL. Could someone fix this and
push out a 1.0.0-alpha-8 ? I'm kind of stuck on this one.
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:59 a.m.
New subject: [JBoss JIRA] Reopened: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
jaikiran pai reopened EJBTHREE-2152:
------------------------------------
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:09 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
jaikiran pai commented on EJBTHREE-2152:
----------------------------------------
I have fixed that column name. But I haven't checked if other column(s) in the
"Calendar_timer" table have similar issues. I'll have to install MySQL first
to test it thoroughly, which I'll do later this week. As of now, you can try using
this snapshot to *replace* the
JBOSS_HOME/server/<servername>/deploy/jboss-ejb3-timerservice-mk2.jar with this one
https://repository.jboss.org/nexus/content/repositories/snapshots//org/jb...
By the way, after replacing that jar, remember to delete the
JBOSS_HOME/server/<servername>/data folder before restarting the server.
I'll leave this issue open and mark it fixed once I have tested this.
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:34 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
Frank Cornelis commented on EJBTHREE-2152:
------------------------------------------
I'm using Maven2 to create a JBoss distribution, thus I would also need the following
artifact:
org.jboss.ejb3.timerservice:jboss-ejb3-timerservice-parent
[INFO] Failed to create assembly: Unable to create managed-version map for all assembly
activities: Unable to get dependency information: Unable to read the metadata file for
artifact 'org.jboss.ejb3.timerservice:jboss-ejb3-timerservice-mk2:jar': Cannot
find parent: org.jboss.ejb3.timerservice:jboss-ejb3-timerservice-parent for project:
org.jboss.ejb3.timerservice:jboss-ejb3-timerservice-mk2:jar:null for project
org.jboss.ejb3.timerservice:jboss-ejb3-timerservice-mk2:jar:null
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:45 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
jaikiran pai commented on EJBTHREE-2152:
----------------------------------------
1.0.0-alpha-8 of timerservice-mk2 has been released and available in Maven repo. I have
run the testsuite locally against a MySQL instance and have the tests passing. Feel free
to give it a try and see if it resolves your issues.
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:45 a.m.
New subject: [JBoss JIRA] Resolved: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
jaikiran pai resolved EJBTHREE-2152.
------------------------------------
Resolution: Done
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:33 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
Frank Cornelis commented on EJBTHREE-2152:
------------------------------------------
The timers work as expected on MySQL 5.1 with 1.0.0-alpha-8. Thanks for your work on
this!
http://code.google.com/p/eid-applet/source/detail?r=423
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:46 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
Frank Cornelis commented on EJBTHREE-2152:
------------------------------------------
Another issue with the persistence of timers, this time on PostgreSQL:
15:40:42,418 ERROR [org.hibernate.util.JDBCExceptionReporter] Batch entry 0 insert into
timer (info, initialDate, nextDate, previousRun, repeatInterval, timedObjectId,
timerState, id) values ('<stream of 31 bytes>', '2010-08-20
18:00:00.000000 +02:00:00', '2010-08-20 18:00:00.000000 +02:00:00', NULL,
'0',
'jboss.j2ee:ear=eid-trust-service-deploy-1.0.0-SNAPSHOT.ear,jar=eid-trust-service-model-1.0.0-SNAPSHOT.jar,name=SchedulingServiceBean,service=EJB3',
'0', 'a8f6ae38-5d4d-4117-9ddc-5b6c60b43398') was aborted. Call
getNextException to see the cause.
15:40:42,418 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Error: 0, SQLState:
42804
15:40:42,418 ERROR [org.hibernate.util.JDBCExceptionReporter] ERROR: column
"info" is of type oid but expression is of type bytea
Hint: You will need to rewrite or cast the expression.
You probably need to add @Type(type =
"org.hibernate.type.PrimitiveByteArrayBlobType") to the info field on
TimerEntity.java for PostgreSQL to like it.
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:51 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
jaikiran pai commented on EJBTHREE-2152:
----------------------------------------
I believe that's something the JPA provider should take into account transparently.
Let me investigate a bit more on that one, I remember some version of PostgreSQL is more
stricter in type conversion.
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
jaikiran pai commented on EJBTHREE-2152:
----------------------------------------
Just for reference http://in.relation.to/Bloggers/PostgreSQLAndBLOBs
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:55 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://jira.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plugi...
]
Frank Cornelis commented on EJBTHREE-2152:
------------------------------------------
In JBoss AS 6.0.0.M5 I've tried several options in
common/deploy/jboss-ejb3-timerservice-mk2.jar/META-INF/persistence.xml. For example:
<property name="hibernate.dialect"
value="org.hibernate.dialect.PostgreSQLDialect" />
<property name="hibernate.jdbc.use_streams_for_binary" value="true"
/>
and
<property name="hibernate.jdbc.use_streams_for_binary"
value="false" />
I still receive the following error:
15:53:27,833 ERROR [org.hibernate.util.JDBCExceptionReporter] ERROR: column
"info" is of type oid but expression is of type bytea
when trying to create an EJB3 timer. I'm using PostgreSQL 8.4.4 and JDBC driver
8.4-701.jdbc4. Anyone knows how to make JBoss AS 6.0 work on PostgreSQL?
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://jira.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0-alpha-2
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:15 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://issues.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plu...
]
jaikiran pai commented on EJBTHREE-2152:
----------------------------------------
Frank, I just added a fix for the PostgreSQL DB issue. Is there any chance you can give it
a try and see if it works? I don't have ready access to PostgreSQL setup. I have
tested the change against the (default) HSQLDB that JBoss AS uses. If you are able to test
this against PostgreSQL and able to report by tomorrow, then the chances of this fix
making it to 6.0 Final are very high. I know, it's a bit too much to ask during a
weekend, but sorry about that - I haven't had a chance to work on this given the other
priorities.
Here's what you have to do to test this:
1) Download the latest JBoss AS from here (or you can even use JBoss AS 6.0 CR1)
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x/lastSuc....
2) Download the fixed timerservice jar from here
https://repository.jboss.org/nexus/content/repositories/releases/org/jbos...
3) Remove (back it up first) the jboss-ejb3-timerservice-mk2.jar from
JBOSS_HOME/common/deploy
4) Place the newly downloaded jboss-ejb3-timerservice-mk2.jar (that exactly how it should
be named) into JBOSS_HOME/common/deploy.
5) Start the server and test your timerservice application against PostgreSQL.
Let us know how it goes.
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://issues.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0-alpha-2
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:06 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://issues.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plu...
]
Frank Cornelis commented on EJBTHREE-2152:
------------------------------------------
Version 1.0.0-alpha-12 fixes the issue on PostgreSQL. The timers are created as it should
be, and they fire as expected. What exactly did you change to fix this issue on
PostgreSQL?
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://issues.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0-alpha-2
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:25 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-2152) Timer table creation fails on MySQL 5
[
https://issues.jboss.org/browse/EJBTHREE-2152?page=com.atlassian.jira.plu...
]
jaikiran pai commented on EJBTHREE-2152:
----------------------------------------
Frank, thanks for testing this fix.
> What exactly did you change to fix this issue on PostgreSQL?
I followed this thread on stackoverflow
http://stackoverflow.com/questions/3677380/proper-hibernate-annotation-fo... which
suggested removing the @Lob annotation altogether so that it can be handled as a Basic
type.
The commit is here
https://github.com/jbossejb3/jboss-ejb3-timerservice/commit/f7f495109a836...
Timer table creation fails on MySQL 5
-------------------------------------
Key: EJBTHREE-2152
URL: https://issues.jboss.org/browse/EJBTHREE-2152
Project: EJB 3.0
Issue Type: Bug
Components: timerservice-mk2
Environment: JBoss AS 6.0.0.M4, bom-as6:0.2.0-alpha-10
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0-alpha-2
Timer table creation fails during AS 6.0.0.M4 startup against MySQL5 DB. Please see the
referenced forum thread for complete details. Here's the relevant logs:
12:34:30,492 INFO [SessionFactoryObjectFactory] Bound factory to JNDI name:
persistence.unit:unitName=#timerdb
12:34:30,492 WARN [SessionFactoryObjectFactory] InitialContext did not implement
EventContext
12:34:30,509 INFO [SchemaUpdate] Running hbm2ddl schema update
12:34:30,509 INFO [SchemaUpdate] fetching database metadata
12:34:30,510 INFO [SchemaUpdate] updating schema
12:34:30,513 INFO [DefaultTraversableResolver] Instantiated an instance of
org.hibernate.validator.engine.resolver.JPATraversableResolver.
12:34:30,519 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,546 INFO [TableMetadata] table found: trust.TimeoutMethod_methodParams
12:34:30,546 INFO [TableMetadata] columns: [methodparams, timeoutmethod_id]
12:34:30,547 INFO [TableMetadata] foreign keys: []
12:34:30,547 INFO [TableMetadata] indexes: [fkf294c964b7de2d8a]
12:34:30,551 INFO [TableMetadata] table found: trust.Timeout_Method
12:34:30,551 INFO [TableMetadata] columns: [id, methodname, cachedtostring,
declaringclass]
12:34:30,551 INFO [TableMetadata] foreign keys: []
12:34:30,551 INFO [TableMetadata] indexes: [primary]
12:34:30,552 INFO [DatabaseMetadata] table not found: timer
12:34:30,553 INFO [DatabaseMetadata] table not found: Calendar_Timer
12:34:30,554 INFO [DatabaseMetadata] table not found: timer
12:34:30,575 ERROR [SchemaUpdate] Unsuccessful: create table Calendar_Timer (autoTimer
bit not null, dayOfMonth varchar(255), dayOfWeek varchar(255), endDate datetime, hour
varchar(255), minute varchar(255), month varchar(255), second varchar(255), startDate
datetime, timezone varchar(255), year varchar(255), id tinyblob not null, timeoutMethod_id
bigint, primary key (id))
12:34:30,576 ERROR [SchemaUpdate] BLOB/TEXT column 'id' used in key specification
without a key length
12:34:30,576 ERROR [SchemaUpdate] Unsuccessful: create table timer (id tinyblob not null,
info longblob, initialDate datetime not null, interval bigint not null, nextDate datetime,
previousRun datetime, timedObjectId varchar(255) not null, timerState integer, primary key
(id))
12:34:30,576 ERROR [SchemaUpdate] You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to use near
'interval bigint not null, nextDate datetime, previousRun datetime, timedObjectId'
at line 1
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04E6E6EF93 (id), add constraint FKEDED5B04E6E6EF93 foreign key (id) references
timer (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,577 ERROR [SchemaUpdate] Unsuccessful: alter table Calendar_Timer add index
FKEDED5B04B7DE2D8A (timeoutMethod_id), add constraint FKEDED5B04B7DE2D8A foreign key
(timeoutMethod_id) references Timeout_Method (id)
12:34:30,577 ERROR [SchemaUpdate] Table 'trust.Calendar_Timer' doesn't exist
12:34:30,578 INFO [SchemaUpdate] schema update complete
I think using a BLOB field for primary key, in itself is probably a bad idea.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5694
days inactive
5818
days old
15 comments
2 participants
participants (2)
-
Frank Cornelis (JIRA) -
jaikiran pai (JIRA)