[ 
https://issues.apache.org/jira/browse/ARTEMIS-2626?focusedWorklogId=390132&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-390132
 ]

ASF GitHub Bot logged work on ARTEMIS-2626:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Feb/20 18:18
            Start Date: 20/Feb/20 18:18
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on issue #2987: 
[ARTEMIS-2626]: Postgresql Journal implementation requires the jdbc driver to 
be in the same classloader
URL: https://github.com/apache/activemq-artemis/pull/2987#issuecomment-589235625
 
 
   Nice !!!   I thought about something simple. You went beyond complete now.  
Thanks a lot. 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 390132)
    Time Spent: 50m  (was: 40m)

> Postgresql Journal implementation requires the jdbc driver to be in the same 
> classloader
> ----------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-2626
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2626
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.11.0
>            Reporter: Emmanuel Hugonnet
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The postrelsq journal implementation makes direct use of Postgresql classes 
> which requires them to be directly accessible from the implementation 
> classloader.
> Also it doesn't take into account the fact that the PGConnection may have 
> been wrapped (for example if it comes from a pool).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to