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

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

                Author: ASF GitHub Bot
            Created on: 07/Apr/22 13:46
            Start Date: 07/Apr/22 13:46
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on code in PR #4009:
URL: https://github.com/apache/activemq-artemis/pull/4009#discussion_r845156155


##########
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/jms/SimpleJNDIClientTest.java:
##########
@@ -111,22 +115,26 @@ public void testEmptyConnectionFactoryString() throws 
NamingException, JMSExcept
 
       //IIB v10 assumes this property is mandatory and sets it to an empty 
string when not specified
       props.put("java.naming.provider.url", "");
-      new InitialContext(props);//Must not throw an exception
-
+      Context ctx = new InitialContext(props);//Must not throw an exception
+      ctx.close();
    }
 
    @Test
    public void testConnectionFactoryStringWithInvalidParameter() throws 
Exception {
+      Level initialLevel = 
LogManager.getLogManager().getLogger("org.apache.activemq.artemis.core.client").getLevel();

Review Comment:
   lets just remove this test?





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

    Worklog Id:     (was: 754085)
    Time Spent: 40m  (was: 0.5h)

> Connectors extra parameters are not passed throught the URI
> -----------------------------------------------------------
>
>                 Key: ARTEMIS-3756
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3756
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.21.0
>            Reporter: Emmanuel Hugonnet
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Since the connectors extra parameters are not passed through the URI when 
> obtaining a  ConnectionFactory by JNDI it won't be using them. This may be an 
> issue for any SPI on the client side since it doesn't get the configuration 
> defined on the server side.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to