[teiid-issues] [JBoss JIRA] Resolved: (TEIID-639) DQP Identity issues

[Steven Hawkins (JIRA)]

     [ https://jira.jboss.org/jira/browse/TEIID-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-639.
----------------------------------

    Resolution: Done


We have no way to enforce TEIID-66 if multiple classloaders are used for the client jar, which was happening in DTP.  For now I have changed the identity logic to increment the identity for each instance created.

> DQP Identity issues
> -------------------
>
>                 Key: TEIID-639
>                 URL: https://jira.jboss.org/jira/browse/TEIID-639
>             Project: Teiid
>          Issue Type: Bug
>          Components: Embedded
>    Affects Versions: 6.0.0
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Critical
>             Fix For: 6.1.0
>
>
> Currently we key off of a system property to determine dqp identity.  This does not work in environments that load multiple instances of teiid in the same vm - it's also cumbersome even with multiple vms sharing the same deployment location.
> We should determine a unique value for the user based upon the instances in use.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira