[JBoss JIRA] Closed: (JBAS-2113) Tables creation problem on Oracle
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2113?page=all ]
Dimitris Andreadis closed JBAS-2113.
------------------------------------
Fix Version/s: JBossAS-4.2.0.GA
JBossAS-5.0.0.Beta3
JBossAS-4.0.5.SP1
Resolution: Done
This problem can now be avoided with the option to rename the timers table and/or specify a particular schema name, see JBAS-4042.
> Tables creation problem on Oracle
> ---------------------------------
>
> Key: JBAS-2113
> URL: http://jira.jboss.com/jira/browse/JBAS-2113
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Scheduling/Timers
> Affects Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.3RC1
> Environment: WindowsXp, Oracle 9i
> Reporter: Martin Cerba
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3, JBossAS-4.0.5.SP1
>
>
> When Jboss is configured to use Oracle 9i DB for tables TIMERS table is not created when user for logging is changed.
> I found problem in org.jboss.ejb.plugins.cmp.jdbc.SQLUtil class in function
> public static boolean tableExists(String tableName, DataSource dataSource)
> This function use JDBC3 functionality getTables(catalog, schema, tableName, null) to check for table existence where schema parameter is set to null.
> On Oracle this function check all schemas (users) for table existence (user had DBA privilegies set) and may find TIMERS table under different user.
> Then jboss assume TIMERS as existing.
> I put username to schema parameter and it repairs problem on oracle but then it not works under hypersonic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Assigned: (JBAS-2113) Tables creation problem on Oracle
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2113?page=all ]
Dimitris Andreadis reassigned JBAS-2113:
----------------------------------------
Assignee: Dimitris Andreadis
> Tables creation problem on Oracle
> ---------------------------------
>
> Key: JBAS-2113
> URL: http://jira.jboss.com/jira/browse/JBAS-2113
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Scheduling/Timers
> Affects Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.3RC1
> Environment: WindowsXp, Oracle 9i
> Reporter: Martin Cerba
> Assigned To: Dimitris Andreadis
>
> When Jboss is configured to use Oracle 9i DB for tables TIMERS table is not created when user for logging is changed.
> I found problem in org.jboss.ejb.plugins.cmp.jdbc.SQLUtil class in function
> public static boolean tableExists(String tableName, DataSource dataSource)
> This function use JDBC3 functionality getTables(catalog, schema, tableName, null) to check for table existence where schema parameter is set to null.
> On Oracle this function check all schemas (users) for table existence (user had DBA privilegies set) and may find TIMERS table under different user.
> Then jboss assume TIMERS as existing.
> I put username to schema parameter and it repairs problem on oracle but then it not works under hypersonic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBAS-4042) Timer service fails to create TIMERS table is table exists in other schema
by Darran Lofthouse (JIRA)
Timer service fails to create TIMERS table is table exists in other schema
--------------------------------------------------------------------------
Key: JBAS-4042
URL: http://jira.jboss.com/jira/browse/JBAS-4042
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.0.4.GA
Environment: Reported against Oracle 9i
Reporter: Darran Lofthouse
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.1.CR1
The TIMER service does not allow the name of the table to be used by the timer service to be overriden.
To check is the table already exists the following is called: -
rs = dmd.getTables(catalog, schema, tableName, null);
return rs.next();
For the timer service no schema is specified so this returns the TIMER tables for all schemas so we do not create the table for the current schema even though it is not available.
If the table name is specified as SCHEMA_NAME.TABLE_NAME then the search will be restricted to the schema so will prevent tables from other schemas being picked up.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Created: (JBAS-3953) OracleDatabasePersistencePlugin does not override selectTimers(ObjectName containerId) - selecting persisted timers fails at startup
by Gunnar von der Beck (JIRA)
OracleDatabasePersistencePlugin does not override selectTimers(ObjectName containerId) - selecting persisted timers fails at startup
------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-3953
URL: http://jira.jboss.com/jira/browse/JBAS-3953
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA
Environment: Oracle Database instead of HSQL-DB
Reporter: Gunnar von der Beck
Precondition:
-------------------
Configure the use of the OracleDatabasePersistencePlugin for EJBTimers:
<!-- A persistence policy that persistes timers to a database -->
<mbean code="org.jboss.ejb.txtimer.DatabasePersistencePolicy" name="jboss.ejb:service=EJBTimerService,persistencePolicy=database">
<!-- DataSource JNDI name -->
<depends optional-attribute-name="DataSource">jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>
<!-- The plugin that handles database persistence -->
<attribute name="DatabasePersistencePlugin">org.jboss.ejb.txtimer.OracleDatabasePersistencePlugin</attribute>
</mbean>
Error:
--------
The org.jboss.ejb.txtimer.OracleDatabasePersistencePlugin extends GeneralPurposeDatabasePersistencePlugin and implements a method
public List selectTimers() throws SQLException;
In order to override the behavior of the GeneralPurposeDatabasePersistencePlugin the correct signature must be
public List selectTimers(ObjectName containerId) throws SQLException;
Hence the following exception occurs when restoring persisted timers at server startup:
2006-12-19 13:27:33,789 ERROR [org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin] Cannot deserialize
java.io.StreamCorruptedException: invalid stream header
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:764)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277)
at org.jboss.invocation.MarshalledValueInputStream.<init>(MarshalledValueInputStream.java:74)
at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.deserialize(GeneralPurposeDatabasePersistencePlugin.java:386)
at org.jboss.ejb.txtimer.GeneralPurposeDatabasePersistencePlugin.selectTimers(GeneralPurposeDatabasePersistencePlugin.java:228)
at org.jboss.ejb.txtimer.DatabasePersistencePolicy.listTimerHandles(DatabasePersistencePolicy.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy16.listTimerHandles(Unknown Source)
at org.jboss.ejb.txtimer.EJBTimerServiceImpl.restoreTimers(EJBTimerServiceImpl.java:408)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months
[JBoss JIRA] Closed: (JBAS-1306) Can't create timer because TARGETID column is too small
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1306?page=all ]
Dimitris Andreadis closed JBAS-1306.
------------------------------------
Resolution: Done
> Can't create timer because TARGETID column is too small
> -------------------------------------------------------
>
> Key: JBAS-1306
> URL: http://jira.jboss.com/jira/browse/JBAS-1306
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Scheduling/Timers
> Affects Versions: JBossAS-4.0.1 Final
> Environment: JBoss 4.0.1, Oracle 9
> Reporter: Tim McCune
> Assigned To: Dimitris Andreadis
> Priority: Minor
> Fix For: JBossAS-5.0.0.Beta1, JBossAS-4.0.4RC1
>
>
> I tried using the timer service in JBoss 4 for the first time today and the timer creation failed because the TARGETID column is defined as VARCHAR(80), and the code is trying to insert a value that is 88 chars long:
> target=jboss.j2ee:jndiName=com/hmsonline/harvester/control/client/Scheduler,service=EJB
> Can you just increase the column size to something like 255 chars by default?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 3 months