[jira] Commented: (DERBY-3541) quit; on ij with authentication enabled does not shutdown the derby modules that are loaded

[ https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729545#action_12729545 ] V.Narayanan commented on DERBY-3541: Oystein says: "2. Somehow fix the

[jira] Commented: (DERBY-3541) quit; on ij with authentication enabled does not shutdown the derby modules that are loaded

[ https://issues.apache.org/jira/browse/DERBY-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729072#action_12729072 ] V.Narayanan commented on DERBY-3541: Thank you for trying out the reproducible.

[jira] Closed: (DERBY-3417) slave side stop in a client server mode results in SQLState printed without proper error message

[ https://issues.apache.org/jira/browse/DERBY-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan closed DERBY-3417. -- Thank you for the backport Dag! Closing Issue! > slave side stop in a client server mode results

[jira] Commented: (DERBY-3896) Assert failure in LogicalUndoOperation.doMe() when starting slave with uncommitted transactions on the master

[ https://issues.apache.org/jira/browse/DERBY-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698680#action_12698680 ] V.Narayanan commented on DERBY-3896: The decision on when to log ship, is t

[jira] Commented: (DERBY-3896) Assert failure in LogicalUndoOperation.doMe() when starting slave with uncommitted transactions on the master

[ https://issues.apache.org/jira/browse/DERBY-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698330#action_12698330 ] V.Narayanan commented on DERBY-3896: Knut said: "I think the problem is th

[jira] Commented: (DERBY-646) In-memory backend storage support

[ https://issues.apache.org/jira/browse/DERBY-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676561#action_12676561 ] V.Narayanan commented on DERBY-646: --- can u please assign the issue to your name? Also

[jira] Closed: (DERBY-2345) truncate on a Blob does not work when the Blob is in memory

[ https://issues.apache.org/jira/browse/DERBY-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan closed DERBY-2345. -- The final patch has been committed for this issue. Thanks to Anurag and kristian for the good work

[jira] Commented: (DERBY-2017) Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length

[ https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611949#action_12611949 ] V.Narayanan commented on DERBY-2017: One of the solutions proposed in the discuss

[jira] Commented: (DERBY-1903) Convert largedata/LobLimits.java to junit

[ https://issues.apache.org/jira/browse/DERBY-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608393#action_12608393 ] V.Narayanan commented on DERBY-1903: Thank you for assigning this to yourself Er

[jira] Commented: (DERBY-3709) Exception printed by replication test: Could not perform operation because the database is not in replication master mode.

[ https://issues.apache.org/jira/browse/DERBY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604200#action_12604200 ] V.Narayanan commented on DERBY-3709: merged with 10.4. The tests in my environ

[jira] Issue Comment Edited: (DERBY-3709) Exception printed by replication test: Could not perform operation because the database is not in replication master mode.

[ https://issues.apache.org/jira/browse/DERBY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603802#action_12603802 ] narayanan edited comment on DERBY-3709 at 6/10/08 1:32 AM: - Tha

[jira] Commented: (DERBY-3709) Exception printed by replication test: Could not perform operation because the database is not in replication master mode.

[ https://issues.apache.org/jira/browse/DERBY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603802#action_12603802 ] V.Narayanan commented on DERBY-3709: Thank you for the patch Ole I had two unrel

[jira] Issue Comment Edited: (DERBY-3709) Exception printed by replication test: Could not perform operation because the database is not in replication master mode.

[ https://issues.apache.org/jira/browse/DERBY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603554#action_12603554 ] narayanan edited comment on DERBY-3709 at 6/9/08 5:02 AM: Thank

[jira] Commented: (DERBY-3709) Exception printed by replication test: Could not perform operation because the database is not in replication master mode.

[ https://issues.apache.org/jira/browse/DERBY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603554#action_12603554 ] V.Narayanan commented on DERBY-3709: Thank you for the patch Ole! Shall run tests

[jira] Assigned: (DERBY-3709) Exception printed by replication test: Could not perform operation because the database is not in replication master mode.

[ https://issues.apache.org/jira/browse/DERBY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan reassigned DERBY-3709: -- Assignee: Ole Solberg > Exception printed by replication test: Could not perform operat

[jira] Commented: (DERBY-3632) Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.

[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603551#action_12603551 ] V.Narayanan commented on DERBY-3632: Committed to 10.4 branch also, ran t

[jira] Commented: (DERBY-3632) Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.

[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603485#action_12603485 ] V.Narayanan commented on DERBY-3632: Thank you for the diagnosis on the issue and

[jira] Commented: (DERBY-3632) Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.

[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603483#action_12603483 ] V.Narayanan commented on DERBY-3632: In addition to the 7 failures in tinderbox, I

[jira] Commented: (DERBY-3632) Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.

[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603463#action_12603463 ] V.Narayanan commented on DERBY-3632: I ran tests on this patch and noticed mult

[jira] Commented: (DERBY-3709) Exception printed by replication test: Could not perform operation because the database is not in replication master mode.

[ https://issues.apache.org/jira/browse/DERBY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603419#action_12603419 ] V.Narayanan commented on DERBY-3709: 1) Can't we just leave the 'else&

[jira] Issue Comment Edited: (DERBY-3632) Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.

[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603415#action_12603415 ] narayanan edited comment on DERBY-3632 at 6/8/08 10:53 AM: - The

[jira] Commented: (DERBY-3632) Replication tests must ensure stable replication state has been reached before attempting further connection or new replication commands.

[ https://issues.apache.org/jira/browse/DERBY-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603415#action_12603415 ] V.Narayanan commented on DERBY-3632: The issue seems straightforward to me,

[jira] Commented: (DERBY-3709) Exception printed by replication test: Could not perform operation because the database is not in replication master mode.

[ https://issues.apache.org/jira/browse/DERBY-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602613#action_12602613 ] V.Narayanan commented on DERBY-3709: I remember while working on 3617 thinking

[jira] Issue Comment Edited: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601022#action_12601022 ] narayanan edited comment on DERBY-2514 at 5/29/08 11:14 PM: -- I

[jira] Commented: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601022#action_12601022 ] V.Narayanan commented on DERBY-2514: Sending java/testing/org/ap

[jira] Commented: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600744#action_12600744 ] V.Narayanan commented on DERBY-2514: starting tests, shall commit as soon as compl

[jira] Commented: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600463#action_12600463 ] V.Narayanan commented on DERBY-2514: I think Knut has some very valid points, s

[jira] Updated: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-2514: --- Attachment: Derby2514_3.diff The patch looks very good. I ran the the mentioned test alone and it

[jira] Issue Comment Edited: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600419#action_12600419 ] narayanan edited comment on DERBY-2514 at 5/28/08 2:48 AM: - Not

[jira] Commented: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600419#action_12600419 ] V.Narayanan commented on DERBY-2514: Not removing lang/closed.java is OK, No pro

[jira] Assigned: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan reassigned DERBY-2514: -- Assignee: Svein Erik Løvland Taking the liberty of assigning this issue to Svien Erik since he

[jira] Commented: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600404#action_12600404 ] V.Narayanan commented on DERBY-2514: A few comments at first look * new file

[jira] Commented: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600402#action_12600402 ] V.Narayanan commented on DERBY-2514: Sorry for the late reply. Thank you for the p

[jira] Commented: (DERBY-2514) convert lang/closed.java to junit

[ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598656#action_12598656 ] V.Narayanan commented on DERBY-2514: This link gives tips on converting tests to j

[jira] Commented: (DERBY-3638) java/testing/Readme.htm location of derbyTesting.jar

[ https://issues.apache.org/jira/browse/DERBY-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591571#action_12591571 ] V.Narayanan commented on DERBY-3638: I was trying to assign this issue to Svein

[jira] Commented: (DERBY-3617) failover on slave hangs after stopmaster on master.

[ https://issues.apache.org/jira/browse/DERBY-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589529#action_12589529 ] V.Narayanan commented on DERBY-3617: Thanks a ton for the clarification Ole. Thank

[jira] Commented: (DERBY-3617) failover on slave hangs after stopmaster on master.

[ https://issues.apache.org/jira/browse/DERBY-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589499#action_12589499 ] V.Narayanan commented on DERBY-3617: Hi Ole, would it be possible for you to

[jira] Commented: (DERBY-3617) failover on slave hangs after stopmaster on master.

[ https://issues.apache.org/jira/browse/DERBY-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589437#action_12589437 ] V.Narayanan commented on DERBY-3617: I tried a simple run without authentica

[jira] Commented: (DERBY-3616) TableFunctionTest fails under Ubuntu 7.10

[ https://issues.apache.org/jira/browse/DERBY-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588553#action_12588553 ] V.Narayanan commented on DERBY-3616: I see these failures as well in ubuntu

[jira] Assigned: (DERBY-3617) failover on slave hangs after stopmaster on master.

[ https://issues.apache.org/jira/browse/DERBY-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan reassigned DERBY-3617: -- Assignee: V.Narayanan > failover on slave hangs after stopmaster on mas

[jira] Commented: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586667#action_12586667 ] V.Narayanan commented on DERBY-3574: while working on Derby-694 I understood that

[jira] Commented: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586395#action_12586395 ] V.Narayanan commented on DERBY-3574: >What if instead of setting lengthObtai

[jira] Commented: (DERBY-3574) With client, attempting to get the lob length after commit or connection close if there was a call to length() before commit does not throw an exception

[ https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586388#action_12586388 ] V.Narayanan commented on DERBY-3574: I have suggested a possible workaround for

[jira] Commented: (DERBY-3469) Clob.length() doesn't detect a closed underlying connection in a consistent way

[ https://issues.apache.org/jira/browse/DERBY-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586387#action_12586387 ] V.Narayanan commented on DERBY-3469: This issue will have unexpected ramifications

[jira] Commented: (DERBY-2954) Add commands to NetworkServerControl for interacting with the replication functionality

[ https://issues.apache.org/jira/browse/DERBY-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586301#action_12586301 ] V.Narayanan commented on DERBY-2954: This JIRA issues has caused changes to

[jira] Resolved: (DERBY-3455) Move replication methods from org.apache.derby.database.Database to org.apache.derby.iapi.db.Database

[ https://issues.apache.org/jira/browse/DERBY-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan resolved DERBY-3455. Resolution: Fixed Fix Version/s: 10.4.0.0 I have raised Derby-3600 to address the follow-up

[jira] Created: (DERBY-3600) Change replication methods in org.apache.derby.iapi.db.Database to throw StandardException instead of SQLException

://issues.apache.org/jira/browse/DERBY-3600 Project: Derby Issue Type: Bug Components: Replication Affects Versions: 10.5.0.0 Reporter: V.Narayanan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to

[jira] Assigned: (DERBY-3600) Change replication methods in org.apache.derby.iapi.db.Database to throw StandardException instead of SQLException

[ https://issues.apache.org/jira/browse/DERBY-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan reassigned DERBY-3600: -- Assignee: V.Narayanan > Change replication methods in org.apache.derby.iapi.db.Database

[jira] Assigned: (DERBY-3553) Write tests for unlogged operations when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan reassigned DERBY-3553: -- Assignee: V.Narayanan > Write tests for unlogged operations when replication is enab

[jira] Updated: (DERBY-3533) Replication fails when unlogged operations are used

[ https://issues.apache.org/jira/browse/DERBY-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3533: --- Affects Version/s: 10.5.0.0 Derby-3551 and Derby-3552 which are sub-tasks of this issue have been

[jira] Updated: (DERBY-3553) Write tests for unlogged operations when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3553: --- Affects Version/s: (was: 10.4.0.0) The fix for logging of unlogged operations during replication

[jira] Resolved: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan resolved DERBY-3552. Resolution: Fixed Fix Version/s: 10.4.0.0 Necessary analysis for this issue has been done

[jira] Assigned: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan reassigned DERBY-3552: -- Assignee: V.Narayanan > Handle jar files that are installed when replication is enab

[jira] Resolved: (DERBY-3454) 'java.lang.NullPointerException' is thrown when starting a master db before a slave one

[ https://issues.apache.org/jira/browse/DERBY-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan resolved DERBY-3454. Resolution: Fixed Fix Version/s: 10.4.0.0 All relevant patches have been submitted and

[jira] Resolved: (DERBY-2954) Add commands to NetworkServerControl for interacting with the replication functionality

[ https://issues.apache.org/jira/browse/DERBY-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan resolved DERBY-2954. Resolution: Fixed Fix Version/s: 10.4.0.0 "NetworkServerControlImpl will not su

[jira] Commented: (DERBY-3554) Change Collation test to run DatabaseMetaDataTest, BatchUpdateTest,GroupByExpressionTest, and UpdateableResultSetTest for only one locale

[ https://issues.apache.org/jira/browse/DERBY-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586282#action_12586282 ] V.Narayanan commented on DERBY-3554: I think a commit message for this issue

[jira] Resolved: (DERBY-3358) After an incorrect(unsuccesfull) startMaster comand, further correct startMaster attempts also fail.

[ https://issues.apache.org/jira/browse/DERBY-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan resolved DERBY-3358. Resolution: Fixed Fix Version/s: 10.4.0.0 All relevant patches have been submitted and

[jira] Commented: (DERBY-3489) Error message XRE04 does not include the right port number.

[ https://issues.apache.org/jira/browse/DERBY-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585581#action_12585581 ] V.Narayanan commented on DERBY-3489: The replication suite of tests passed

[jira] Updated: (DERBY-3489) Error message XRE04 does not include the right port number.

[ https://issues.apache.org/jira/browse/DERBY-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3489: --- Attachment: Derby3489_4.stat Derby3489_4.diff * Moved logging back to the

[jira] Updated: (DERBY-3489) Error message XRE04 does not include the right port number.

[ https://issues.apache.org/jira/browse/DERBY-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3489: --- Attachment: Derby3489_3.stat Derby3489_3.diff Thank you for the comments/reviews

[jira] Commented: (DERBY-3169) Add documentation for replication

[ https://issues.apache.org/jira/browse/DERBY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584993#action_12584993 ] V.Narayanan commented on DERBY-3169: >I agree that something should probably

[jira] Commented: (DERBY-3169) Add documentation for replication

[ https://issues.apache.org/jira/browse/DERBY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584642#action_12584642 ] V.Narayanan commented on DERBY-3169: In mentioning "Unlogged operations

[jira] Commented: (DERBY-3169) Add documentation for replication

[ https://issues.apache.org/jira/browse/DERBY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584625#action_12584625 ] V.Narayanan commented on DERBY-3169: Thank you for the follow-up on 3551 and 3552

[jira] Commented: (DERBY-3567) AsynchronousLogShipper#forceFlush should time out

[ https://issues.apache.org/jira/browse/DERBY-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584591#action_12584591 ] V.Narayanan commented on DERBY-3567: what happens if network goes down in flushBu

[jira] Assigned: (DERBY-3567) AsynchronousLogShipper#forceFlush should time out

[ https://issues.apache.org/jira/browse/DERBY-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan reassigned DERBY-3567: -- Assignee: Jørgen Løland The patch attached by Jorgen to this issue looks good to me. Jorgen

[jira] Commented: (DERBY-3567) AsynchronousLogShipper#forceFlush should time out

[ https://issues.apache.org/jira/browse/DERBY-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584502#action_12584502 ] V.Narayanan commented on DERBY-3567: The patch looks complete and very good, Work

[jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584425#action_12584425 ] V.Narayanan commented on DERBY-3552: >I guess the jar installation is recorded

[jira] Updated: (DERBY-3509) The replication log shipper is not notified when a new replication transmitter is instantiated in MC#handleException.

[ https://issues.apache.org/jira/browse/DERBY-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3509: --- Attachment: Derby3509_1.stat Derby3509_1.diff I have modified the handleException

[jira] Updated: (DERBY-3509) The replication log shipper is not notified when a new replication transmitter is instantiated in MC#handleException.

[ https://issues.apache.org/jira/browse/DERBY-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3509: --- Derby Info: [Patch Available] > The replication log shipper is not notified when a new replicat

[jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584021#action_12584021 ] V.Narayanan commented on DERBY-3552: Below is the trial of trying to install on

[jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584011#action_12584011 ] V.Narayanan commented on DERBY-3552: Kim says >Why would you need to do a repl

[jira] Assigned: (DERBY-3509) The replication log shipper is not notified when a new replication transmitter is instantiated in MC#handleException.

[ https://issues.apache.org/jira/browse/DERBY-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan reassigned DERBY-3509: -- Assignee: V.Narayanan > The replication log shipper is not notified when a new replicat

[jira] Issue Comment Edited: (DERBY-3489) Error message XRE04 does not include the right port number.

Bug > Components: Replication >Affects Versions: 10.4.0.0 >Reporter: Øystein Grøvlen >Assignee: V.Narayanan > Attachments: Derby3489_1.diff, Derby3489_1.stat, Derby3489_2.diff, > Derby3489_2.stat > > > If the master is not a

[jira] Updated: (DERBY-3489) Error message XRE04 does not include the right port number.

[ https://issues.apache.org/jira/browse/DERBY-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3489: --- Attachment: Derby3489_2.stat Derby3489_2.diff Prints a message in

[jira] Commented: (DERBY-3489) Error message XRE04 does not include the right port number.

[ https://issues.apache.org/jira/browse/DERBY-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583623#action_12583623 ] V.Narayanan commented on DERBY-3489: > Does this mean that the slave will never

[jira] Updated: (DERBY-3489) Error message XRE04 does not include the right port number.

[ https://issues.apache.org/jira/browse/DERBY-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3489: --- Derby Info: [Patch Available] > Error message XRE04 does not include the right port num

[jira] Updated: (DERBY-3489) Error message XRE04 does not include the right port number.

[ https://issues.apache.org/jira/browse/DERBY-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3489: --- Attachment: Derby3489_1.stat Derby3489_1.diff * java/engine/org/apache/derby/impl

[jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583577#action_12583577 ] V.Narayanan commented on DERBY-3552: Documentation related observa

[jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583521#action_12583521 ] V.Narayanan commented on DERBY-3552: Thank you for looking at this issue Ki

[jira] Updated: (DERBY-3526) AsynchronousLogShipper#workToDo is blocked while the log shipper sends a log chunk

[ https://issues.apache.org/jira/browse/DERBY-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3526: --- Attachment: Derby3526_1.stat Derby3526_1.diff Thanks for looking at the issue

[jira] Updated: (DERBY-3447) Shutdown on a database without stopping replication hangs

[ https://issues.apache.org/jira/browse/DERBY-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3447: --- Attachment: Derby3447_v5.stat Derby3447_v5.diff Thank you for taking a look at the

[jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582251#action_12582251 ] V.Narayanan commented on DERBY-3552: I have been experimenting with this and I do

[jira] Updated: (DERBY-3526) AsynchronousLogShipper#workToDo is blocked while the log shipper sends a log chunk

[ https://issues.apache.org/jira/browse/DERBY-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3526: --- Derby Info: [Patch Available] > AsynchronousLogShipper#workToDo is blocked while the log ship

[jira] Commented: (DERBY-3526) AsynchronousLogShipper#workToDo is blocked while the log shipper sends a log chunk

[ https://issues.apache.org/jira/browse/DERBY-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582146#action_12582146 ] V.Narayanan commented on DERBY-3526: Would it be OK to commit the attached patch

[jira] Commented: (DERBY-3447) Shutdown on a database without stopping replication hangs

[ https://issues.apache.org/jira/browse/DERBY-3447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582118#action_12582118 ] V.Narayanan commented on DERBY-3447: v4 applies cleanly to a freshworkspace. I

[jira] Commented: (DERBY-3551) Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

[ https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582000#action_12582000 ] V.Narayanan commented on DERBY-3551: Thank you for watching this issue Kim. I dec

[jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581403#action_12581403 ] V.Narayanan commented on DERBY-3552: If a complete path to the location of the

[jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581389#action_12581389 ] V.Narayanan commented on DERBY-3552: I have the following comments on what needs t

[jira] Commented: (DERBY-3552) Handle jar files that are installed when replication is enabled

[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581388#action_12581388 ] V.Narayanan commented on DERBY-3552: I have been experimenting with running jars

[jira] Issue Comment Edited: (DERBY-3552) Handle jar files that are installed when replication is enabled

ask > Components: Replication >Affects Versions: 10.4.0.0, 10.5.0.0 >Reporter: V.Narayanan > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.

[jira] Updated: (DERBY-3551) Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

[ https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3551: --- Attachment: Derby3551_3.stat Derby3551_3.diff > Since I guess unlogged operati

[jira] Commented: (DERBY-3551) Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

[ https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581141#action_12581141 ] V.Narayanan commented on DERBY-3551: I had also earlier tested this patch for a si

[jira] Updated: (DERBY-3551) Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

[ https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3551: --- Attachment: runscript_import.sql I tested the patch Derby3551_2 with imports and it worked fine

[jira] Updated: (DERBY-3551) Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

[ https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3551: --- Attachment: Derby3551_2.stat Derby3551_2.diff I have modified Derby3551_1.diff to

[jira] Commented: (DERBY-3562) Number of log files (and log dir size) on the slave increases continuously

[ https://issues.apache.org/jira/browse/DERBY-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581024#action_12581024 ] V.Narayanan commented on DERBY-3562: Not sure if the analysis here points at the

[jira] Commented: (DERBY-3551) Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

[ https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581020#action_12581020 ] V.Narayanan commented on DERBY-3551: >"Check if any unlogged operations a

[jira] Commented: (DERBY-3551) Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

[ https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581015#action_12581015 ] V.Narayanan commented on DERBY-3551: I feel that the stored procedure will no

[jira] Commented: (DERBY-3169) Add documentation for replication

[ https://issues.apache.org/jira/browse/DERBY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580430#action_12580430 ] V.Narayanan commented on DERBY-3169: Thank you for the excellent work you have

[jira] Commented: (DERBY-3551) Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

[ https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580338#action_12580338 ] V.Narayanan commented on DERBY-3551: Please note that Derby3551_1 is not for a co

[jira] Updated: (DERBY-3551) Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

[ https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] V.Narayanan updated DERBY-3551: --- Attachment: Derby3551_1.stat Derby3551_1.diff In trying to search for a way to

  1   2   3   4   5   6   7   8   9   10   >