[
https://issues.apache.org/jira/browse/IGNITE-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198796#comment-16198796
]
ASF GitHub Bot commented on IGNITE-5790:
----------------------------------------
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/2460
> Xml config can not be used in jdbs and user code simultaneously
> ---------------------------------------------------------------
>
> Key: IGNITE-5790
> URL: https://issues.apache.org/jira/browse/IGNITE-5790
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.1
> Reporter: Mikhail Cherkasov
> Assignee: Ilya Kasnacheev
> Fix For: 2.3
>
>
> when user uses the same xml config for jdbc driver and for his own ignite
> instance there can be :
> java.sql.SQLException: Failed to start Ignite node.
> Caused by: class org.apache.ignite.IgniteCheckedException: Ignite instance
> with this name has already been started: CustomeIgniteName
> because JDBC creates separate ignite instance, while user already has one
> with the same name.
> Of course that can be easily workarounded, user can support two configs or
> create jdbc connect first and then use Ignition.getOrStart().
> However it's inconvenient for user and should be treated as usability issue.
> I see 2 solutions:
> 1) jdbc driver should use Ignition.getOrStart()
> 2) jdbc driver should connection string as ignite name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
