[ https://forge.continuent.org/jira/browse/SEQUOIA-832?page=all ]
Emmanuel Cecchet resolved SEQUOIA-832:
--------------------------------------
Assign To: Mathieu Peltier (was: Emmanuel Cecchet)
Resolution: Fixed
Fix available in 2.10 branch
> Using persistent connections with a single controller without a recovery log
> causes NPE
> ---------------------------------------------------------------------------------------
>
> Key: SEQUOIA-832
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-832
> Project: Sequoia
> Type: Bug
> Components: Core
> Versions: Sequoia 2.10.2
> Reporter: Emmanuel Cecchet
> Assignee: Mathieu Peltier
> Priority: Critical
> Fix For: Sequoia 2.10.3
>
>
> When using persistent connections with a single controller (no Distribution
> element) without a recovery log definition causes:
> java.lang.NullPointerException
> at
> org.continuent.sequoia.controller.requestmanager.RequestManager.openPersistentConnection(RequestManager.java:482)
> at
> org.continuent.sequoia.controller.virtualdatabase.VirtualDatabase.openPersistentConnection(VirtualDatabase.java:1043)
> at
> org.continuent.sequoia.controller.virtualdatabase.VirtualDatabaseWorkerThread.run(VirtualDatabaseWorkerThread.java:336)
> This does not affect Sequoia 3.0 where recovery log is mandatory.
> Workaround is to define a recovery log when using persistent connections.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
