Hi Robert,
Thank you for your update.
Here is my requested scenario
The database scheme
--------------------------------
+-----------+-------------+------+-----+---------------------+----------------+
| Field | Type | Null | Key | Default |
Extra |
+-----------+-------------+------+-----+---------------------+----------------+
| cid | int(11) | NO | PRI | NULL |
auto_increment |
| cname | varchar(20) | NO | | NULL
| |
| cemail | varchar(50) | NO | | NULL
| |
| csubject | varchar(30) | NO | | NULL
| |
| cmessage | text | NO | | NULL
| |
| lastlogin | datetime | YES | | 0000-00-00 00:00:00
| |
| age | tinyint(4) | YES | | 1
| |
| age2 | tinyint(4) | YES | | 1
| |
+-----------+-------------+------+-----+---------------------+----------------+
Here is my write sql query
------------------------------------
insert into contact(cname,cemail,csubject,cmessage)
values('abcdeabcdeabcdeabcdee','lggg','jjjj','hhh')
Please note the field "cname" is defined the width of 20. However 21 chars
have been passed from the application leads to the below error. I am using
sequoia version 2.10.9 and appia as group communication.
Here i am using only one controller.
Thanks in Advance for your any help.
Regards
George Elefter
Backend iviews - BackendWorkerThread for backend 'backend2' with RAIDb
level:1 failed (Data truncation: Data too long for column 'cname' at row 1)
Backend iviews - BackendWorkerThread for backend 'backend1' with RAIDb
level:1 failed (Data truncation: Data too long for column 'cname' at row 1)
16:42:25,516 WARN controller.RequestManager.iviews SQLException while
executing distributed write request write request 5 failed:
Backend iviews - BackendWorkerThread for backend 'backend2' with RAIDb
level:1 failed (Data truncation: Data too long for column 'cname' at row 1)
Backend iviews - BackendWorkerThread for backend 'backend1' with RAIDb
level:1 failed (Data truncation: Data too long for column 'cname' at row 1)
java.sql.SQLException: write request 5 failed:
Backend iviews - BackendWorkerThread for backend 'backend2' with RAIDb
level:1 failed (Data truncation: Data too long for column 'cname' at row 1)
Backend iviews - BackendWorkerThread for backend 'backend1' with RAIDb
level:1 failed (Data truncation: Data too long for column 'cname' at row 1)
at
org.continuent.sequoia.common.exceptions.SQLExceptionFactory.getSQLException
(SQLExceptionFactory.java:88)
at
org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.checkTaskCompletion
(RAIDb1.java:939)
at
org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.execWriteRequest
(RAIDb1.java:343)
at
org.continuent.sequoia.controller.loadbalancer.raidb1.RAIDb1.statementExecuteUpdate
(RAIDb1.java:249)
at
org.continuent.sequoia.controller.requestmanager.RequestManager.loadBalanceStatementExecuteUpdate
(RequestManager.java:925)
at
org.continuent.sequoia.controller.virtualdatabase.protocol.DistributedStatementExecuteUpdate.executeScheduledRequest
(DistributedStatementExecuteUpdate.java:87)
at
org.continuent.sequoia.controller.virtualdatabase.protocol.DistributedRequest.handleMessageMultiThreaded
(DistributedRequest.java:157)
at
org.continuent.sequoia.controller.virtualdatabase.DistributedVirtualDatabase.handleMessageMultiThreaded
(DistributedVirtualDatabase.java:364)
at org.continuent.hedera.adapters.MulticastRequestAdapterThread.run(
MulticastRequestAdapterThread.java:102)
16:42:25,529 ERROR continuent.hedera.adapters PullPushAdapter: Error while
reading from channel
org.continuent.appia.core.message.MessageException: Trying to read an
unknown object from message.
at org.continuent.appia.core.message.Message.popObject(Message.java
:1254)
at org.continuent.hedera.channel.AppiaReliableGroupChannel.receive(
AppiaReliableGroupChannel.java:292)
at org.continuent.hedera.adapters.PullPushAdapter.run(
PullPushAdapter.java:166)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException:
com.mysql.jdbc.MysqlDataTruncation
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java
:574)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java
:1538)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java
:1460)
at java.io.ObjectInputStream.readOrdinaryObject(
ObjectInputStream.java:1693)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java
:1299)
at java.io.ObjectInputStream.defaultReadFields(
ObjectInputStream.java:1912)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java
:1836)
at java.io.ObjectInputStream.readOrdinaryObject(
ObjectInputStream.java:1713)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java
:1299)
at java.io.ObjectInputStream.defaultReadFields(
ObjectInputStream.java:1912)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java
:1836)
at java.io.ObjectInputStream.readOrdinaryObject(
ObjectInputStream.java:1713)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java
:1299)
at java.io.ObjectInputStream.defaultReadFields(
ObjectInputStream.java:1912)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java
:1836)
at java.io.ObjectInputStream.readOrdinaryObject(
ObjectInputStream.java:1713)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java
:1299)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
at org.continuent.appia.core.message.Message.popObject(Message.java
:1250)
... 3 more
On Jan 2, 2008 9:25 PM, Robert Hodges <[EMAIL PROTECTED]> wrote:
> Hi George and Pierre,
>
> I'm updating the JGroups release in Sequoia today to 2.6.1 and will post a
> beta Sequoia build as quickly as I can. However, the Appia problem is
> different. Do you have reproducible test cases for both of these? We may
> need to check in with Nuno on Appia.
>
> Happy new year,
>
> Robert
>
>
> On 1/2/08 5:22 AM, "George Elefter" <[EMAIL PROTECTED]> wrote:
>
> Hi Pierre,
>
> Thanks for the update. We are using appia for group communications. Hence
> it looks like the issue is little different here. Because of a wrong sql
> query passed from the application a pending request is placed in the queue.
> Correcting this at the application level is not feasible now. We want to go
> with the next db write ignoring the pending one. Means that the sql error
> query execution should be terminated by the sequoia level and not keep it
> pending write and blocking the successive request. Is this one handled in
> any of the Sequoia version including beta. We are using 2.10.9.
>
> Regards
>
> George Elefter.
>
> On 1/2/08, *BESSON-DEBLON,Pier re (SOGETI HIGH TECH)* <
> [EMAIL PROTECTED]> wrote:
>
> I experienced pending write requests using jgroups : there is a bug in
> sequencer which can eliminate group requests.
> This bug is fixed by jgroups-JIRA-607, there is a related JIRA entry in
> sequoia but it is not fixed.
>
>
> -----Message d'origine-----
> *De :* [EMAIL PROTECTED] [
> mailto:[EMAIL PROTECTED]<[EMAIL PROTECTED]>
> *De la part de* George Elefter
> *Envoyé :* 27 December 2007 17:49
> *À :* [email protected]
> *Objet :* [Sequoia] Sequoia Pending Write Request
>
> Hello,
>
> When a "pending write request" is placed in the queue, sequoia waits
> forthis statement to finish, but it NEVER finishes the same and as a result
> the table will never be released and no more write operation happens in
> that table. This is a potential trouble in the production system.Thisproblem
> is with Sequoia
> 2.10.9. Is this resolved in the later versions ? It would be help if you
> provide an workaround for this.
>
> Thanks & Regards
>
> George Elefter
>
> This mail has originated outside your organization, either from an
> external partner or the Global Internet.
> Keep this in mind if you answer this message.
>
>
> This e-mail is intended only for the above addressee. It may contain
> privileged information.
> If you are not the addressee you must not copy, distribute, disclose or
> use any of the information in it.
> If you have received it in error please delete it and immediately notify
> the sender.
>
> Security Notice: all e-mail, sent to or from this address, may be accessed
> by someone other than the recipient, for system management and security
> reasons. This access is controlled under Regulation of security reasons.
>
> This access is controlled under Regulation of Investigatory Powers Act
> 2000, Lawful Business Practises.
>
>
> _______________________________________________
> Sequoia mailing list
> [email protected]
> <mailto:[email protected]><[email protected]>
> https://forge.continuent.org/mailman/listinfo/sequoia
>
>
> ------------------------------
> _______________________________________________
> Sequoia mailing list
> [email protected]
> https://forge.continuent.org/mailman/listinfo/sequoia
>
>
>
> --
> Robert Hodges, CTO, Continuent, Inc.
> Email: [EMAIL PROTECTED]
> Mobile: +1-510-501-3728 Skype: hodgesrm
>
> _______________________________________________
> Sequoia mailing list
> [email protected]
> https://forge.continuent.org/mailman/listinfo/sequoia
>
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
