Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
On 07/06/2011 07:28 PM, Eric Kreiser wrote:
> So I am attempting to get the servers working in "clustered" mode...
>
> it is not working... and if I turn logging up... I am getting all kinds
> of ClassNotFoundException's... it is looking for a number of Hessian
> classes that are not in any of the jars released with the resin download...
>
level="all" isn't generally useful because it includes normal exceptions
like that one. The most you'd normally want to run at is "finer".
-- Scott
> 07-06 21:41:56.823 HmtpWriter[null] query AuthQuery[,SignedCredentials]
> {id: 1, to:null, from:baa.app-tier.admin.resin}
> 07-06 21:41:56.853 java.lang.ClassNotFoundException:
> com.caucho.hmtp.AuthQueryHessianSerializer
> at
> java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at
> java.security.AccessController.doPrivileged(Native Method)
> at
> java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at
> java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at
> sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at
> java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:247)
> at
> com.caucho.hessian.io.ContextSerializerFactory.getCustomSerializer(ContextSerializerFactory.java:190)
> at
> com.caucho.hessian.io.SerializerFactory.loadSerializer(SerializerFactory.java:266)
> at
> com.caucho.hessian.io.SerializerFactory.getSerializer(SerializerFactory.java:224)
> at
> com.caucho.hessian.io.SerializerFactory.getObjectSerializer(SerializerFactory.java:197)
> at
> com.caucho.hessian.io.Hessian2Output.writeObject(Hessian2Output.java:437)
> at
> com.caucho.hmtp.HmtpWriter.query(HmtpWriter.java:194)
> at
> com.caucho.hmtp.HmtpWebSocketWriter.query(HmtpWebSocketWriter.java:152)
> at
> com.caucho.cloud.bam.HmtpStream.authenticate(HmtpStream.java:167)
> at
> com.caucho.cloud.bam.HmtpStream.init(HmtpStream.java:137)
> at
> com.caucho.cloud.bam.HmtpStream.(HmtpStream.java:78)
> at
> com.caucho.cloud.heartbeat.HeartbeatActor.openStream(HeartbeatActor.java:335)
> at
> com.caucho.cloud.heartbeat.HeartbeatActor.sendMessage(HeartbeatActor.java:288)
> at
> com.caucho.cloud.heartbeat.HeartbeatActor.sendHeartbeatMessage(HeartbeatActor.java:270)
> at
> com.caucho.cloud.heartbeat.HeartbeatActor.sendHeartbeat(HeartbeatActor.java:195)
> at
> com.caucho.cloud.heartbeat.HeartbeatActor.access$000(HeartbeatActor.java:62)
> at
> com.caucho.cloud.heartbeat.HeartbeatActor$HeartBeatSender.run(HeartbeatActor.java:417)
> at
> com.caucho.env.thread.ResinThread.runTasks(ResinThread.java:164)
> at
> com.caucho.env.thread.ResinThread.run(ResinThread.java:130)
>
> On 07/05/2011 09:44 AM, Eric Kreiser wrote:
>> I've attached a stripped down resin.conf
>>
>> you wrote "But the cluster store doesn't use jdbc." - BUT earlier in
>> the thread you wrote "The jdbc store in Resin 4.0 acts as a backup to
>> the normal cluster store."
>>
>> which is it?
>>
>> how can things like persistent sessions work in a load balanced scenario
>> if all servers are not pointing to the same DB?
>>
>> like I stated earlier in the thread - I haven't been using Resin's
>> clustering setup... I have been relying on db persisted sessions to
>> "tie" the server together... is this approach no longer valid with 4.0?
>>
>> Does Caucho intend to support Oracle? or do I need to stay on a earlier
>> version until I can figure out what I am going to do?
>>
>>
>>
>>
>>
>> On 07/01/2011 11:41 AM, Scott Ferguson wrote:
>>> On 07/01/2011 07:57 AM, Eric Kreiser wrote:
I changed my persistent-store type to be "cluster" instead of "jdbc"...
but it still doesn't start because it still needs the "new" resin
database tables... (which fail on create connecting to Oracle)
>>> But the cluster store doesn't use jdbc. It wouldn't even know about the
>>> Oracle database.
>>>
>>> What does that section of the resin.xml look like?
>>>
>>> -- Scott
>>>
thoughts?
Eric Kreiser
On 06/27/2011 02:24 PM, Eric Kreiser wrote:
> the problem(I think) is that I don't use Resin's clustering... and rely
> on the db persistent sessions to handle bouncing between servers.
>
>
> On 06/27/2011 01:50 PM, Scott Ferguson wrote:
>> On 06/27/2011 10:39 AM, Eric Kreiser wrote:
>>> I am trying to upgrade from 4.0.15 to
Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
So I am attempting to get the servers working in "clustered" mode...
it is not working... and if I turn logging up... I am getting all kinds
of ClassNotFoundException's... it is looking for a number of Hessian
classes that are not in any of the jars released with the resin download...
07-06 21:41:56.823 HmtpWriter[null] query AuthQuery[,SignedCredentials]
{id: 1, to:null, from:baa.app-tier.admin.resin}
07-06 21:41:56.853 java.lang.ClassNotFoundException:
com.caucho.hmtp.AuthQueryHessianSerializer
at
java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at
java.security.AccessController.doPrivileged(Native Method)
at
java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at
com.caucho.hessian.io.ContextSerializerFactory.getCustomSerializer(ContextSerializerFactory.java:190)
at
com.caucho.hessian.io.SerializerFactory.loadSerializer(SerializerFactory.java:266)
at
com.caucho.hessian.io.SerializerFactory.getSerializer(SerializerFactory.java:224)
at
com.caucho.hessian.io.SerializerFactory.getObjectSerializer(SerializerFactory.java:197)
at
com.caucho.hessian.io.Hessian2Output.writeObject(Hessian2Output.java:437)
at
com.caucho.hmtp.HmtpWriter.query(HmtpWriter.java:194)
at
com.caucho.hmtp.HmtpWebSocketWriter.query(HmtpWebSocketWriter.java:152)
at
com.caucho.cloud.bam.HmtpStream.authenticate(HmtpStream.java:167)
at
com.caucho.cloud.bam.HmtpStream.init(HmtpStream.java:137)
at
com.caucho.cloud.bam.HmtpStream.(HmtpStream.java:78)
at
com.caucho.cloud.heartbeat.HeartbeatActor.openStream(HeartbeatActor.java:335)
at
com.caucho.cloud.heartbeat.HeartbeatActor.sendMessage(HeartbeatActor.java:288)
at
com.caucho.cloud.heartbeat.HeartbeatActor.sendHeartbeatMessage(HeartbeatActor.java:270)
at
com.caucho.cloud.heartbeat.HeartbeatActor.sendHeartbeat(HeartbeatActor.java:195)
at
com.caucho.cloud.heartbeat.HeartbeatActor.access$000(HeartbeatActor.java:62)
at
com.caucho.cloud.heartbeat.HeartbeatActor$HeartBeatSender.run(HeartbeatActor.java:417)
at
com.caucho.env.thread.ResinThread.runTasks(ResinThread.java:164)
at
com.caucho.env.thread.ResinThread.run(ResinThread.java:130)
On 07/05/2011 09:44 AM, Eric Kreiser wrote:
> I've attached a stripped down resin.conf
>
> you wrote "But the cluster store doesn't use jdbc." - BUT earlier in
> the thread you wrote "The jdbc store in Resin 4.0 acts as a backup to
> the normal cluster store."
>
> which is it?
>
> how can things like persistent sessions work in a load balanced scenario
> if all servers are not pointing to the same DB?
>
> like I stated earlier in the thread - I haven't been using Resin's
> clustering setup... I have been relying on db persisted sessions to
> "tie" the server together... is this approach no longer valid with 4.0?
>
> Does Caucho intend to support Oracle? or do I need to stay on a earlier
> version until I can figure out what I am going to do?
>
>
>
>
>
> On 07/01/2011 11:41 AM, Scott Ferguson wrote:
>> On 07/01/2011 07:57 AM, Eric Kreiser wrote:
>>> I changed my persistent-store type to be "cluster" instead of "jdbc"...
>>> but it still doesn't start because it still needs the "new" resin
>>> database tables... (which fail on create connecting to Oracle)
>> But the cluster store doesn't use jdbc. It wouldn't even know about the
>> Oracle database.
>>
>> What does that section of the resin.xml look like?
>>
>> -- Scott
>>
>>> thoughts?
>>> Eric Kreiser
>>>
>>>
>>> On 06/27/2011 02:24 PM, Eric Kreiser wrote:
the problem(I think) is that I don't use Resin's clustering... and rely
on the db persistent sessions to handle bouncing between servers.
On 06/27/2011 01:50 PM, Scott Ferguson wrote:
> On 06/27/2011 10:39 AM, Eric Kreiser wrote:
>> I am trying to upgrade from 4.0.15 to 4.0.19.
>>
>> The server fails to start.
> For now, just set the persistent-store type="cluster" instead of "jdbc".
>
> The jdbc store in Resin 4.0 acts as a backup to the normal cluster store.
>
> -- Scott
>
>> The problem is that it is trying to create the "resin_data" and
>> "resin_mnode" database tables ... but the
Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
On 07/05/2011 10:58 AM, Eric Kreiser wrote: > ok... so basically what I am hearing is that I can't deploy my app on > 4.0.19 as it stands now. > > In resin 3.1, I was able to deploy my app... using db persistent > sessions... NOT configure the resin.conf to be clustered... but still > be able to load balance(using other products) and have the users not > loose state as they bounce between servers. > > Is this scenario supported with 4? or with 4, am I forced to tell > resin about each one of its peer servers in the resin.conf? Correct. If you want the clustering capabilities like distributed sessions, you need to configure a cluster. -- Scott > > > I am not trying to beat a dead horse here... but trying to understand > if it is an intended change in design/functionality between 3.1 and 4. > > > > On 07/05/2011 11:27 AM, Scott Ferguson wrote: >> On 07/05/2011 06:44 AM, Eric Kreiser wrote: >>> I've attached a stripped down resin.conf >> You need to remove the from the to >> disable the jdbc backup. >>> you wrote "But the cluster store doesn't use jdbc." - BUT earlier in >>> the thread you wrote "The jdbc store in Resin 4.0 acts as a backup to >>> the normal cluster store." >>> >>> which is it? >> It is a backup store. Because it's a backup, it's not strictly needed >> for normal operation. >> >>> how can things like persistent sessions work in a load balanced >>> scenario if all servers are not pointing to the same DB? >> I don't understand the question. The servers in a cluster know about >> each other through the configuration. >> >>> like I stated earlier in the thread - I haven't been using Resin's >>> clustering setup... I have been relying on db persisted sessions to >>> "tie" the server together... is this approach no longer valid with 4.0? >> If you're not configuring Resin in a cluster, then cluster capabilities >> like the persistent store aren't available. >> >>> Does Caucho intend to support Oracle? >> I filed a bug report. >> >> -- Scott >> >>> or do I need to stay on a earlier version until I can figure out what >>> I am going to do? >> >>> >>> >>> >>> >>> On 07/01/2011 11:41 AM, Scott Ferguson wrote: On 07/01/2011 07:57 AM, Eric Kreiser wrote: > I changed my persistent-store type to be "cluster" instead of > "jdbc"... > but it still doesn't start because it still needs the "new" resin > database tables... (which fail on create connecting to Oracle) But the cluster store doesn't use jdbc. It wouldn't even know about the Oracle database. What does that section of the resin.xml look like? -- Scott > thoughts? > Eric Kreiser > > > On 06/27/2011 02:24 PM, Eric Kreiser wrote: >> the problem(I think) is that I don't use Resin's clustering... and >> rely >> on the db persistent sessions to handle bouncing between servers. >> >> >> On 06/27/2011 01:50 PM, Scott Ferguson wrote: >>> On 06/27/2011 10:39 AM, Eric Kreiser wrote: I am trying to upgrade from 4.0.15 to 4.0.19. The server fails to start. >>> For now, just set the persistent-store type="cluster" instead of >>> "jdbc". >>> >>> The jdbc store in Resin 4.0 acts as a backup to the normal cluster >>> store. >>> >>> -- Scott >>> The problem is that it is trying to create the "resin_data" and "resin_mnode" database tables ... but the "create table" syntax is not valid for Oracle. -- 06-27 12:38:29.146 JdbcMnodeStore[server] java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist 06-27 12:38:29.146 CREATE TABLE resin_mnode ( id CHAR(64) PRIMARY KEY, value CHAR(64), cache_id CHAR(64), expire_timeout BIGINT, idle_timeout BIGINT, lease_timeout BIGINT, local_read_timeout BIGINT, update_time BIGINT, item_version BIGINT, flags INTEGER, server_version INTEGER) 06-27 12:38:29.149 [3ms] jdbc/versioncloud.d0.0.0:exn-executeUpdate(CREATE TABLE resin_mnode ( id CHAR(64) PRIMARY KEY, value CHAR(64), cache_id CHAR(64), expire_timeout BIGINT, idle_timeout BIGINT, lease_timeout BIGINT,
Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
ok... so basically what I am hearing is that I can't deploy my app on 4.0.19 as it stands now. In resin 3.1, I was able to deploy my app... using db persistent sessions... NOT configure the resin.conf to be clustered... but still be able to load balance(using other products) and have the users not loose state as they bounce between servers. Is this scenario supported with 4? or with 4, am I forced to tell resin about each one of its peer servers in the resin.conf? I am not trying to beat a dead horse here... but trying to understand if it is an intended change in design/functionality between 3.1 and 4. On 07/05/2011 11:27 AM, Scott Ferguson wrote: > On 07/05/2011 06:44 AM, Eric Kreiser wrote: >> I've attached a stripped down resin.conf > You need to remove the from the to > disable the jdbc backup. >> you wrote "But the cluster store doesn't use jdbc." - BUT earlier in >> the thread you wrote "The jdbc store in Resin 4.0 acts as a backup to >> the normal cluster store." >> >> which is it? > It is a backup store. Because it's a backup, it's not strictly needed > for normal operation. > >> how can things like persistent sessions work in a load balanced >> scenario if all servers are not pointing to the same DB? > I don't understand the question. The servers in a cluster know about > each other through the configuration. > >> like I stated earlier in the thread - I haven't been using Resin's >> clustering setup... I have been relying on db persisted sessions to >> "tie" the server together... is this approach no longer valid with 4.0? > If you're not configuring Resin in a cluster, then cluster capabilities > like the persistent store aren't available. > >> Does Caucho intend to support Oracle? > I filed a bug report. > > -- Scott > >> or do I need to stay on a earlier version until I can figure out what >> I am going to do? > >> >> >> >> >> On 07/01/2011 11:41 AM, Scott Ferguson wrote: >>> On 07/01/2011 07:57 AM, Eric Kreiser wrote: I changed my persistent-store type to be "cluster" instead of "jdbc"... but it still doesn't start because it still needs the "new" resin database tables... (which fail on create connecting to Oracle) >>> But the cluster store doesn't use jdbc. It wouldn't even know about the >>> Oracle database. >>> >>> What does that section of the resin.xml look like? >>> >>> -- Scott >>> thoughts? Eric Kreiser On 06/27/2011 02:24 PM, Eric Kreiser wrote: > the problem(I think) is that I don't use Resin's clustering... and > rely > on the db persistent sessions to handle bouncing between servers. > > > On 06/27/2011 01:50 PM, Scott Ferguson wrote: >> On 06/27/2011 10:39 AM, Eric Kreiser wrote: >>> I am trying to upgrade from 4.0.15 to 4.0.19. >>> >>> The server fails to start. >> For now, just set the persistent-store type="cluster" instead of >> "jdbc". >> >> The jdbc store in Resin 4.0 acts as a backup to the normal cluster >> store. >> >> -- Scott >> >>> The problem is that it is trying to create the "resin_data" and >>> "resin_mnode" database tables ... but the "create table" syntax >>> is not >>> valid for Oracle. >>> >>> -- >>> >>> 06-27 12:38:29.146 JdbcMnodeStore[server] >>> java.sql.SQLSyntaxErrorException: ORA-00942: table or view does >>> not exist >>> >>> 06-27 12:38:29.146 CREATE TABLE resin_mnode ( >>> id CHAR(64) PRIMARY KEY, >>> value CHAR(64), >>> cache_id CHAR(64), >>> expire_timeout BIGINT, >>> idle_timeout BIGINT, >>> lease_timeout BIGINT, >>> local_read_timeout BIGINT, >>> update_time BIGINT, >>> item_version BIGINT, >>> flags INTEGER, >>> server_version INTEGER) >>> 06-27 12:38:29.149 [3ms] >>> jdbc/versioncloud.d0.0.0:exn-executeUpdate(CREATE TABLE >>> resin_mnode ( >>> id CHAR(64) PRIMARY KEY, >>> value CHAR(64), >>> cache_id CHAR(64), >>> expire_timeout BIGINT, >>> idle_timeout BIGINT, >>> lease_timeout BIGINT, >>> local_read_timeout BIGINT, >>> update_time BIGINT, >>> item_version BIGINT, >>> flags INTEGER, >>> server_version INTEGER)) -> >>> java.sql.SQLSyntaxErrorException: ORA-00902: invalid
Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
On 07/05/2011 06:44 AM, Eric Kreiser wrote: > I've attached a stripped down resin.conf You need to remove the from the to disable the jdbc backup. > > you wrote "But the cluster store doesn't use jdbc." - BUT earlier in > the thread you wrote "The jdbc store in Resin 4.0 acts as a backup to > the normal cluster store." > > which is it? It is a backup store. Because it's a backup, it's not strictly needed for normal operation. > > how can things like persistent sessions work in a load balanced > scenario if all servers are not pointing to the same DB? I don't understand the question. The servers in a cluster know about each other through the configuration. > > like I stated earlier in the thread - I haven't been using Resin's > clustering setup... I have been relying on db persisted sessions to > "tie" the server together... is this approach no longer valid with 4.0? If you're not configuring Resin in a cluster, then cluster capabilities like the persistent store aren't available. > > Does Caucho intend to support Oracle? I filed a bug report. -- Scott > or do I need to stay on a earlier version until I can figure out what > I am going to do? > > > > > > On 07/01/2011 11:41 AM, Scott Ferguson wrote: >> On 07/01/2011 07:57 AM, Eric Kreiser wrote: >>> I changed my persistent-store type to be "cluster" instead of "jdbc"... >>> but it still doesn't start because it still needs the "new" resin >>> database tables... (which fail on create connecting to Oracle) >> But the cluster store doesn't use jdbc. It wouldn't even know about the >> Oracle database. >> >> What does that section of the resin.xml look like? >> >> -- Scott >> >>> thoughts? >>> Eric Kreiser >>> >>> >>> On 06/27/2011 02:24 PM, Eric Kreiser wrote: the problem(I think) is that I don't use Resin's clustering... and rely on the db persistent sessions to handle bouncing between servers. On 06/27/2011 01:50 PM, Scott Ferguson wrote: > On 06/27/2011 10:39 AM, Eric Kreiser wrote: >> I am trying to upgrade from 4.0.15 to 4.0.19. >> >> The server fails to start. > For now, just set the persistent-store type="cluster" instead of > "jdbc". > > The jdbc store in Resin 4.0 acts as a backup to the normal cluster > store. > > -- Scott > >> The problem is that it is trying to create the "resin_data" and >> "resin_mnode" database tables ... but the "create table" syntax >> is not >> valid for Oracle. >> >> -- >> >> >> 06-27 12:38:29.146 JdbcMnodeStore[server] >> java.sql.SQLSyntaxErrorException: ORA-00942: table or view does >> not exist >> >> 06-27 12:38:29.146 CREATE TABLE resin_mnode ( >>id CHAR(64) PRIMARY KEY, >>value CHAR(64), >>cache_id CHAR(64), >>expire_timeout BIGINT, >>idle_timeout BIGINT, >>lease_timeout BIGINT, >>local_read_timeout BIGINT, >>update_time BIGINT, >>item_version BIGINT, >>flags INTEGER, >>server_version INTEGER) >> 06-27 12:38:29.149 [3ms] >> jdbc/versioncloud.d0.0.0:exn-executeUpdate(CREATE TABLE >> resin_mnode ( >>id CHAR(64) PRIMARY KEY, >>value CHAR(64), >>cache_id CHAR(64), >>expire_timeout BIGINT, >>idle_timeout BIGINT, >>lease_timeout BIGINT, >>local_read_timeout BIGINT, >>update_time BIGINT, >>item_version BIGINT, >>flags INTEGER, >>server_version INTEGER)) -> >> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype >> >> 06-27 12:38:29.149 [0ms] jdbc/versioncloud.d0.0.0:close() >> 06-27 12:38:29.149 idle >> ManagedPoolItem[jdbc/versioncloud,0,ManagedConnectionImpl] >> 06-27 12:38:29.149 jdbc/versioncloud.d0.0:clearWarnings() >> 06-27 12:38:29.149 java.lang.RuntimeException: >> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype >> >> at >> com.caucho.distcache.cluster.ClusterDataBacking.(ClusterDataBacking.java:89) >> >> >> at >> com.caucho.distcache.cluster.ClusterCacheManagerImpl.createDataBacking(ClusterCacheManagerImpl.java:81) >> >> >> at >> com.caucho.server.distcache.AbstractCacheManag
Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
I've attached a stripped down resin.conf you wrote "But the cluster store doesn't use jdbc." - BUT earlier in the thread you wrote "The jdbc store in Resin 4.0 acts as a backup to the normal cluster store." which is it? how can things like persistent sessions work in a load balanced scenario if all servers are not pointing to the same DB? like I stated earlier in the thread - I haven't been using Resin's clustering setup... I have been relying on db persisted sessions to "tie" the server together... is this approach no longer valid with 4.0? Does Caucho intend to support Oracle? or do I need to stay on a earlier version until I can figure out what I am going to do? On 07/01/2011 11:41 AM, Scott Ferguson wrote: On 07/01/2011 07:57 AM, Eric Kreiser wrote: I changed my persistent-store type to be "cluster" instead of "jdbc"... but it still doesn't start because it still needs the "new" resin database tables... (which fail on create connecting to Oracle) But the cluster store doesn't use jdbc. It wouldn't even know about the Oracle database. What does that section of the resin.xml look like? -- Scott thoughts? Eric Kreiser On 06/27/2011 02:24 PM, Eric Kreiser wrote: the problem(I think) is that I don't use Resin's clustering... and rely on the db persistent sessions to handle bouncing between servers. On 06/27/2011 01:50 PM, Scott Ferguson wrote: On 06/27/2011 10:39 AM, Eric Kreiser wrote: I am trying to upgrade from 4.0.15 to 4.0.19. The server fails to start. For now, just set the persistent-store type="cluster" instead of "jdbc". The jdbc store in Resin 4.0 acts as a backup to the normal cluster store. -- Scott The problem is that it is trying to create the "resin_data" and "resin_mnode" database tables ... but the "create table" syntax is not valid for Oracle. -- 06-27 12:38:29.146 JdbcMnodeStore[server] java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist 06-27 12:38:29.146 CREATE TABLE resin_mnode ( id CHAR(64) PRIMARY KEY, value CHAR(64), cache_id CHAR(64), expire_timeout BIGINT, idle_timeout BIGINT, lease_timeout BIGINT, local_read_timeout BIGINT, update_time BIGINT, item_version BIGINT, flags INTEGER, server_version INTEGER) 06-27 12:38:29.149 [3ms] jdbc/versioncloud.d0.0.0:exn-executeUpdate(CREATE TABLE resin_mnode ( id CHAR(64) PRIMARY KEY, value CHAR(64), cache_id CHAR(64), expire_timeout BIGINT, idle_timeout BIGINT, lease_timeout BIGINT, local_read_timeout BIGINT, update_time BIGINT, item_version BIGINT, flags INTEGER, server_version INTEGER)) -> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype 06-27 12:38:29.149 [0ms] jdbc/versioncloud.d0.0.0:close() 06-27 12:38:29.149 idle ManagedPoolItem[jdbc/versioncloud,0,ManagedConnectionImpl] 06-27 12:38:29.149 jdbc/versioncloud.d0.0:clearWarnings() 06-27 12:38:29.149 java.lang.RuntimeException: java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype at com.caucho.distcache.cluster.ClusterDataBacking.(ClusterDataBacking.java:89) at com.caucho.distcache.cluster.ClusterCacheManagerImpl.createDataBacking(ClusterCacheManagerImpl.java:81) at com.caucho.server.distcache.AbstractCacheManager.start(AbstractCacheManager.java:1133) at com.caucho.distcache.cluster.ClusterCacheManagerImpl.start(ClusterCacheManagerImpl.java:90) at com.caucho.env.distcache.DistCacheSystem.start(DistCacheSystem.java:110) at com.caucho.env.service.ResinSystem.startServices(ResinSystem.java:513) at com.caucho.env.service.ResinSystem.start(ResinSystem.java:481) at com.caucho.server.resin.Resin.start(Resin.java:999) at com.caucho.server.resin.Resin.initMain(Resin.java:1127) at com.caucho.server.resin.Resin.main(Resin.java:1426) Caused by: java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) at oracl
Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
On 07/01/2011 07:57 AM, Eric Kreiser wrote: > I changed my persistent-store type to be "cluster" instead of "jdbc"... > but it still doesn't start because it still needs the "new" resin > database tables... (which fail on create connecting to Oracle) But the cluster store doesn't use jdbc. It wouldn't even know about the Oracle database. What does that section of the resin.xml look like? -- Scott > thoughts? > Eric Kreiser > > > On 06/27/2011 02:24 PM, Eric Kreiser wrote: >> the problem(I think) is that I don't use Resin's clustering... and rely >> on the db persistent sessions to handle bouncing between servers. >> >> >> On 06/27/2011 01:50 PM, Scott Ferguson wrote: >>> On 06/27/2011 10:39 AM, Eric Kreiser wrote: I am trying to upgrade from 4.0.15 to 4.0.19. The server fails to start. >>> For now, just set the persistent-store type="cluster" instead of "jdbc". >>> >>> The jdbc store in Resin 4.0 acts as a backup to the normal cluster store. >>> >>> -- Scott >>> The problem is that it is trying to create the "resin_data" and "resin_mnode" database tables ... but the "create table" syntax is not valid for Oracle. -- 06-27 12:38:29.146 JdbcMnodeStore[server] java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist 06-27 12:38:29.146 CREATE TABLE resin_mnode ( id CHAR(64) PRIMARY KEY, value CHAR(64), cache_id CHAR(64), expire_timeout BIGINT, idle_timeout BIGINT, lease_timeout BIGINT, local_read_timeout BIGINT, update_time BIGINT, item_version BIGINT, flags INTEGER, server_version INTEGER) 06-27 12:38:29.149 [3ms] jdbc/versioncloud.d0.0.0:exn-executeUpdate(CREATE TABLE resin_mnode ( id CHAR(64) PRIMARY KEY, value CHAR(64), cache_id CHAR(64), expire_timeout BIGINT, idle_timeout BIGINT, lease_timeout BIGINT, local_read_timeout BIGINT, update_time BIGINT, item_version BIGINT, flags INTEGER, server_version INTEGER)) -> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype 06-27 12:38:29.149 [0ms] jdbc/versioncloud.d0.0.0:close() 06-27 12:38:29.149 idle ManagedPoolItem[jdbc/versioncloud,0,ManagedConnectionImpl] 06-27 12:38:29.149 jdbc/versioncloud.d0.0:clearWarnings() 06-27 12:38:29.149 java.lang.RuntimeException: java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype at com.caucho.distcache.cluster.ClusterDataBacking.(ClusterDataBacking.java:89) at com.caucho.distcache.cluster.ClusterCacheManagerImpl.createDataBacking(ClusterCacheManagerImpl.java:81) at com.caucho.server.distcache.AbstractCacheManager.start(AbstractCacheManager.java:1133) at com.caucho.distcache.cluster.ClusterCacheManagerImpl.start(ClusterCacheManagerImpl.java:90) at com.caucho.env.distcache.DistCacheSystem.start(DistCacheSystem.java:110) at com.caucho.env.service.ResinSystem.startServices(ResinSystem.java:513) at com.caucho.env.service.ResinSystem.start(ResinSystem.java:481) at com.caucho.server.resin.Resin.start(Resin.java:999) at com.caucho.server.resin.Resin.initMain(Resin.java:1127) at com.caucho.server.resin.Resin.main(Resin.java:1426) Caused by: java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
I changed my persistent-store type to be "cluster" instead of "jdbc"... but it still doesn't start because it still needs the "new" resin database tables... (which fail on create connecting to Oracle) thoughts? Eric Kreiser On 06/27/2011 02:24 PM, Eric Kreiser wrote: > the problem(I think) is that I don't use Resin's clustering... and rely > on the db persistent sessions to handle bouncing between servers. > > > On 06/27/2011 01:50 PM, Scott Ferguson wrote: >> On 06/27/2011 10:39 AM, Eric Kreiser wrote: >>> I am trying to upgrade from 4.0.15 to 4.0.19. >>> >>> The server fails to start. >> For now, just set the persistent-store type="cluster" instead of "jdbc". >> >> The jdbc store in Resin 4.0 acts as a backup to the normal cluster store. >> >> -- Scott >> >>> The problem is that it is trying to create the "resin_data" and >>> "resin_mnode" database tables ... but the "create table" syntax is not >>> valid for Oracle. >>> >>> -- >>> 06-27 12:38:29.146 JdbcMnodeStore[server] >>> java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist >>> >>> 06-27 12:38:29.146 CREATE TABLE resin_mnode ( >>> id CHAR(64) PRIMARY KEY, >>> value CHAR(64), >>> cache_id CHAR(64), >>> expire_timeout BIGINT, >>> idle_timeout BIGINT, >>> lease_timeout BIGINT, >>> local_read_timeout BIGINT, >>> update_time BIGINT, >>> item_version BIGINT, >>> flags INTEGER, >>> server_version INTEGER) >>> 06-27 12:38:29.149 [3ms] >>> jdbc/versioncloud.d0.0.0:exn-executeUpdate(CREATE TABLE resin_mnode ( >>> id CHAR(64) PRIMARY KEY, >>> value CHAR(64), >>> cache_id CHAR(64), >>> expire_timeout BIGINT, >>> idle_timeout BIGINT, >>> lease_timeout BIGINT, >>> local_read_timeout BIGINT, >>> update_time BIGINT, >>> item_version BIGINT, >>> flags INTEGER, >>> server_version INTEGER)) -> >>> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype >>> >>> 06-27 12:38:29.149 [0ms] jdbc/versioncloud.d0.0.0:close() >>> 06-27 12:38:29.149 idle >>> ManagedPoolItem[jdbc/versioncloud,0,ManagedConnectionImpl] >>> 06-27 12:38:29.149 jdbc/versioncloud.d0.0:clearWarnings() >>> 06-27 12:38:29.149 java.lang.RuntimeException: >>> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype >>> >>>at >>> com.caucho.distcache.cluster.ClusterDataBacking.(ClusterDataBacking.java:89) >>>at >>> com.caucho.distcache.cluster.ClusterCacheManagerImpl.createDataBacking(ClusterCacheManagerImpl.java:81) >>>at >>> com.caucho.server.distcache.AbstractCacheManager.start(AbstractCacheManager.java:1133) >>>at >>> com.caucho.distcache.cluster.ClusterCacheManagerImpl.start(ClusterCacheManagerImpl.java:90) >>>at >>> com.caucho.env.distcache.DistCacheSystem.start(DistCacheSystem.java:110) >>>at >>> com.caucho.env.service.ResinSystem.startServices(ResinSystem.java:513) >>>at >>> com.caucho.env.service.ResinSystem.start(ResinSystem.java:481) >>>at >>> com.caucho.server.resin.Resin.start(Resin.java:999) >>>at >>> com.caucho.server.resin.Resin.initMain(Resin.java:1127) >>>at >>> com.caucho.server.resin.Resin.main(Resin.java:1426) >>>Caused by: java.sql.SQLSyntaxErrorException: >>> ORA-00902: invalid datatype >>> >>>at >>> oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) >>>at >>> oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) >>>at >>> oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802) >>>at >>> oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436) >>>at >>> oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) >>>at >>> oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521) >>>at >>> oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194) >>>at >>> oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1000) >>>at >>> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307) >>>at >
Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
On 06/27/2011 11:24 AM, Eric Kreiser wrote: > the problem(I think) is that I don't use Resin's clustering... and > rely on the db persistent sessions to handle bouncing between servers. The db persistent sessions in Resin 4.0 is a backup to Resin's clustering. If you're using db persistent sessions, you're also using Resin's clustered sessions. It's not a replacement, it's an additional level of reliability. -- Scott > > > On 06/27/2011 01:50 PM, Scott Ferguson wrote: >> On 06/27/2011 10:39 AM, Eric Kreiser wrote: >>> I am trying to upgrade from 4.0.15 to 4.0.19. >>> >>> The server fails to start. >> For now, just set the persistent-store type="cluster" instead of "jdbc". >> >> The jdbc store in Resin 4.0 acts as a backup to the normal cluster >> store. >> >> -- Scott >> >>> The problem is that it is trying to create the "resin_data" and >>> "resin_mnode" database tables ... but the "create table" syntax is not >>> valid for Oracle. >>> >>> -- >>> >>> >>> 06-27 12:38:29.146 JdbcMnodeStore[server] >>> java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not >>> exist >>> >>> 06-27 12:38:29.146 CREATE TABLE resin_mnode ( >>> id CHAR(64) PRIMARY KEY, >>> value CHAR(64), >>> cache_id CHAR(64), >>> expire_timeout BIGINT, >>> idle_timeout BIGINT, >>> lease_timeout BIGINT, >>> local_read_timeout BIGINT, >>> update_time BIGINT, >>> item_version BIGINT, >>> flags INTEGER, >>> server_version INTEGER) >>> 06-27 12:38:29.149 [3ms] >>> jdbc/versioncloud.d0.0.0:exn-executeUpdate(CREATE TABLE resin_mnode ( >>> id CHAR(64) PRIMARY KEY, >>> value CHAR(64), >>> cache_id CHAR(64), >>> expire_timeout BIGINT, >>> idle_timeout BIGINT, >>> lease_timeout BIGINT, >>> local_read_timeout BIGINT, >>> update_time BIGINT, >>> item_version BIGINT, >>> flags INTEGER, >>> server_version INTEGER)) -> >>> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype >>> >>> 06-27 12:38:29.149 [0ms] jdbc/versioncloud.d0.0.0:close() >>> 06-27 12:38:29.149 idle >>> ManagedPoolItem[jdbc/versioncloud,0,ManagedConnectionImpl] >>> 06-27 12:38:29.149 jdbc/versioncloud.d0.0:clearWarnings() >>> 06-27 12:38:29.149 java.lang.RuntimeException: >>> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype >>> >>> at >>> com.caucho.distcache.cluster.ClusterDataBacking.(ClusterDataBacking.java:89) >>> >>> >>> at >>> com.caucho.distcache.cluster.ClusterCacheManagerImpl.createDataBacking(ClusterCacheManagerImpl.java:81) >>> >>> >>> at >>> com.caucho.server.distcache.AbstractCacheManager.start(AbstractCacheManager.java:1133) >>> >>> >>> at >>> com.caucho.distcache.cluster.ClusterCacheManagerImpl.start(ClusterCacheManagerImpl.java:90) >>> >>> >>> at >>> com.caucho.env.distcache.DistCacheSystem.start(DistCacheSystem.java:110) >>> >>> at >>> com.caucho.env.service.ResinSystem.startServices(ResinSystem.java:513) >>> at >>> com.caucho.env.service.ResinSystem.start(ResinSystem.java:481) >>> at >>> com.caucho.server.resin.Resin.start(Resin.java:999) >>> at >>> com.caucho.server.resin.Resin.initMain(Resin.java:1127) >>> at >>> com.caucho.server.resin.Resin.main(Resin.java:1426) >>> Caused by: java.sql.SQLSyntaxErrorException: >>> ORA-00902: invalid datatype >>> >>> at >>> oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) >>> at >>> oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) >>> at >>> oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802) >>> at >>> oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436) >>> at >>> oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) >>> at >>> oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521) >>> at >>> oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194) >>> at >>> oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1000) >>> at >>> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307)
Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
the problem(I think) is that I don't use Resin's clustering... and rely on the db persistent sessions to handle bouncing between servers. On 06/27/2011 01:50 PM, Scott Ferguson wrote: > On 06/27/2011 10:39 AM, Eric Kreiser wrote: >> I am trying to upgrade from 4.0.15 to 4.0.19. >> >> The server fails to start. > For now, just set the persistent-store type="cluster" instead of "jdbc". > > The jdbc store in Resin 4.0 acts as a backup to the normal cluster store. > > -- Scott > >> The problem is that it is trying to create the "resin_data" and >> "resin_mnode" database tables ... but the "create table" syntax is not >> valid for Oracle. >> >> -- >> 06-27 12:38:29.146 JdbcMnodeStore[server] >> java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist >> >> 06-27 12:38:29.146 CREATE TABLE resin_mnode ( >> id CHAR(64) PRIMARY KEY, >> value CHAR(64), >> cache_id CHAR(64), >> expire_timeout BIGINT, >> idle_timeout BIGINT, >> lease_timeout BIGINT, >> local_read_timeout BIGINT, >> update_time BIGINT, >> item_version BIGINT, >> flags INTEGER, >> server_version INTEGER) >> 06-27 12:38:29.149 [3ms] >> jdbc/versioncloud.d0.0.0:exn-executeUpdate(CREATE TABLE resin_mnode ( >> id CHAR(64) PRIMARY KEY, >> value CHAR(64), >> cache_id CHAR(64), >> expire_timeout BIGINT, >> idle_timeout BIGINT, >> lease_timeout BIGINT, >> local_read_timeout BIGINT, >> update_time BIGINT, >> item_version BIGINT, >> flags INTEGER, >> server_version INTEGER)) -> >> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype >> >> 06-27 12:38:29.149 [0ms] jdbc/versioncloud.d0.0.0:close() >> 06-27 12:38:29.149 idle >> ManagedPoolItem[jdbc/versioncloud,0,ManagedConnectionImpl] >> 06-27 12:38:29.149 jdbc/versioncloud.d0.0:clearWarnings() >> 06-27 12:38:29.149 java.lang.RuntimeException: >> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype >> >> at >> com.caucho.distcache.cluster.ClusterDataBacking.(ClusterDataBacking.java:89) >> at >> com.caucho.distcache.cluster.ClusterCacheManagerImpl.createDataBacking(ClusterCacheManagerImpl.java:81) >> at >> com.caucho.server.distcache.AbstractCacheManager.start(AbstractCacheManager.java:1133) >> at >> com.caucho.distcache.cluster.ClusterCacheManagerImpl.start(ClusterCacheManagerImpl.java:90) >> at >> com.caucho.env.distcache.DistCacheSystem.start(DistCacheSystem.java:110) >> at >> com.caucho.env.service.ResinSystem.startServices(ResinSystem.java:513) >> at >> com.caucho.env.service.ResinSystem.start(ResinSystem.java:481) >> at >> com.caucho.server.resin.Resin.start(Resin.java:999) >> at >> com.caucho.server.resin.Resin.initMain(Resin.java:1127) >> at >> com.caucho.server.resin.Resin.main(Resin.java:1426) >> Caused by: java.sql.SQLSyntaxErrorException: >> ORA-00902: invalid datatype >> >> at >> oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) >> at >> oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) >> at >> oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802) >> at >> oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436) >> at >> oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) >> at >> oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521) >> at >> oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194) >> at >> oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1000) >> at >> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307) >> at >> oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1814) >> at >> oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1779) >> at >> oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:277) >> at >> com.caucho.sql.spy.SpyStatement.executeUpdate(SpyStatement.ja
Re: [Resin-interest] ResinPro 4.0.19 - Oracle support???
On 06/27/2011 10:39 AM, Eric Kreiser wrote: > I am trying to upgrade from 4.0.15 to 4.0.19. > > The server fails to start. For now, just set the persistent-store type="cluster" instead of "jdbc". The jdbc store in Resin 4.0 acts as a backup to the normal cluster store. -- Scott > The problem is that it is trying to create the "resin_data" and > "resin_mnode" database tables ... but the "create table" syntax is not > valid for Oracle. > > -- > 06-27 12:38:29.146 JdbcMnodeStore[server] > java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist > > 06-27 12:38:29.146 CREATE TABLE resin_mnode ( >id CHAR(64) PRIMARY KEY, >value CHAR(64), >cache_id CHAR(64), >expire_timeout BIGINT, >idle_timeout BIGINT, >lease_timeout BIGINT, >local_read_timeout BIGINT, >update_time BIGINT, >item_version BIGINT, >flags INTEGER, >server_version INTEGER) > 06-27 12:38:29.149 [3ms] > jdbc/versioncloud.d0.0.0:exn-executeUpdate(CREATE TABLE resin_mnode ( >id CHAR(64) PRIMARY KEY, >value CHAR(64), >cache_id CHAR(64), >expire_timeout BIGINT, >idle_timeout BIGINT, >lease_timeout BIGINT, >local_read_timeout BIGINT, >update_time BIGINT, >item_version BIGINT, >flags INTEGER, >server_version INTEGER)) -> > java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype > > 06-27 12:38:29.149 [0ms] jdbc/versioncloud.d0.0.0:close() > 06-27 12:38:29.149 idle > ManagedPoolItem[jdbc/versioncloud,0,ManagedConnectionImpl] > 06-27 12:38:29.149 jdbc/versioncloud.d0.0:clearWarnings() > 06-27 12:38:29.149 java.lang.RuntimeException: > java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype > > at > com.caucho.distcache.cluster.ClusterDataBacking.(ClusterDataBacking.java:89) > at > com.caucho.distcache.cluster.ClusterCacheManagerImpl.createDataBacking(ClusterCacheManagerImpl.java:81) > at > com.caucho.server.distcache.AbstractCacheManager.start(AbstractCacheManager.java:1133) > at > com.caucho.distcache.cluster.ClusterCacheManagerImpl.start(ClusterCacheManagerImpl.java:90) > at > com.caucho.env.distcache.DistCacheSystem.start(DistCacheSystem.java:110) > at > com.caucho.env.service.ResinSystem.startServices(ResinSystem.java:513) > at > com.caucho.env.service.ResinSystem.start(ResinSystem.java:481) > at > com.caucho.server.resin.Resin.start(Resin.java:999) > at > com.caucho.server.resin.Resin.initMain(Resin.java:1127) > at > com.caucho.server.resin.Resin.main(Resin.java:1426) > Caused by: java.sql.SQLSyntaxErrorException: > ORA-00902: invalid datatype > > at > oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) > at > oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) > at > oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802) > at > oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436) > at > oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) > at > oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521) > at > oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194) > at > oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1000) > at > oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307) > at > oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1814) > at > oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1779) > at > oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:277) > at > com.caucho.sql.spy.SpyStatement.executeUpdate(SpyStatement.java:225) > at > com.caucho.sql.UserStatement.executeUpdate(UserStatement.java:230) > at > com.caucho.distcache.jdbc.JdbcMnodeStore.initDatabase(JdbcMnodeStore.java:256) > at > com.caucho.distcache.jdbc.JdbcMnodeStore.init(JdbcMnodeStore.java:196) >
[Resin-interest] ResinPro 4.0.19 - Oracle support???
I am trying to upgrade from 4.0.15 to 4.0.19. The server fails to start. The problem is that it is trying to create the "resin_data" and "resin_mnode" database tables ... but the "create table" syntax is not valid for Oracle. -- 06-27 12:38:29.146 JdbcMnodeStore[server] java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist 06-27 12:38:29.146 CREATE TABLE resin_mnode ( id CHAR(64) PRIMARY KEY, value CHAR(64), cache_id CHAR(64), expire_timeout BIGINT, idle_timeout BIGINT, lease_timeout BIGINT, local_read_timeout BIGINT, update_time BIGINT, item_version BIGINT, flags INTEGER, server_version INTEGER) 06-27 12:38:29.149 [3ms] jdbc/versioncloud.d0.0.0:exn-executeUpdate(CREATE TABLE resin_mnode ( id CHAR(64) PRIMARY KEY, value CHAR(64), cache_id CHAR(64), expire_timeout BIGINT, idle_timeout BIGINT, lease_timeout BIGINT, local_read_timeout BIGINT, update_time BIGINT, item_version BIGINT, flags INTEGER, server_version INTEGER)) -> java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype 06-27 12:38:29.149 [0ms] jdbc/versioncloud.d0.0.0:close() 06-27 12:38:29.149 idle ManagedPoolItem[jdbc/versioncloud,0,ManagedConnectionImpl] 06-27 12:38:29.149 jdbc/versioncloud.d0.0:clearWarnings() 06-27 12:38:29.149 java.lang.RuntimeException: java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype at com.caucho.distcache.cluster.ClusterDataBacking.(ClusterDataBacking.java:89) at com.caucho.distcache.cluster.ClusterCacheManagerImpl.createDataBacking(ClusterCacheManagerImpl.java:81) at com.caucho.server.distcache.AbstractCacheManager.start(AbstractCacheManager.java:1133) at com.caucho.distcache.cluster.ClusterCacheManagerImpl.start(ClusterCacheManagerImpl.java:90) at com.caucho.env.distcache.DistCacheSystem.start(DistCacheSystem.java:110) at com.caucho.env.service.ResinSystem.startServices(ResinSystem.java:513) at com.caucho.env.service.ResinSystem.start(ResinSystem.java:481) at com.caucho.server.resin.Resin.start(Resin.java:999) at com.caucho.server.resin.Resin.initMain(Resin.java:1127) at com.caucho.server.resin.Resin.main(Resin.java:1426) Caused by: java.sql.SQLSyntaxErrorException: ORA-00902: invalid datatype at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521) at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:194) at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1000) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307) at oracle.jdbc.driver.OracleStatement.executeUpdateInternal(OracleStatement.java:1814) at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java:1779) at oracle.jdbc.driver.OracleStatementWrapper.executeUpdate(OracleStatementWrapper.java:277) at com.caucho.sql.spy.SpyStatement.executeUpdate(SpyStatement.java:225) at com.caucho.sql.UserStatement.executeUpdate(UserStatement.java:230) at com.caucho.distcache.jdbc.JdbcMnodeStore.initDatabase(JdbcMnodeStore.java:256) at com.caucho.distcache.jdbc.JdbcMnodeStore.init(JdbcMnodeStore.java:196) at com.caucho.distcache.cluster.ClusterDataBacking.(ClusterDataBacking.java:80) ... 9 more -- If I manually add the tables... the server starts... but I get errors. -- 06-27 12:07:31.8
