You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Timothy A. Bish (Jira)" <ji...@apache.org> on 2022/08/10 23:41:00 UTC

[jira] [Commented] (QPIDJMS-574) java.lang.IllegalArgumentException "unused parameters" after upgrade from 0.6 to 1.6

    [ https://issues.apache.org/jira/browse/QPIDJMS-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578185#comment-17578185 ] 

Timothy A. Bish commented on QPIDJMS-574:
-----------------------------------------

There appears to be a typo in your URI (missing &) :
{code:java}
&amqp.vhost=localhostamqp.saslLayer=true&{code}
I've tried the URI with corrections with main and with a build from the 1.6.0 tag and didn't experience any issues connecting to Artemis broker.

> java.lang.IllegalArgumentException "unused parameters" after upgrade from 0.6 to 1.6
> ------------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-574
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-574
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 1.6.0
>         Environment: OpenJDK 11
>            Reporter: Sebastian T
>            Priority: Major
>
> I am trying to migrate from qpid-jms-client from 0.6.1 to 1.6.0 but with the new release I get the following error:
> {noformat}
> Exception in thread "main" java.lang.IllegalArgumentException: Not all jms options could be set on the ConnectionFactory. Check the options are spelled correctly. Unused parameters=[
> {redeliveryPolicy.maxRedeliveries=0, redeliveryPolicy.outcome=REJECTED, presettlePolicy.presettleAll=false}
> ]. This connection factory cannot be started.
> at org.apache.qpid.jms.JmsConnectionFactory.setRemoteURI(JmsConnectionFactory.java:420)
> at org.apache.qpid.jms.JmsConnectionFactory.<init>(JmsConnectionFactory.java:128)
> {noformat}
> The connection string looks something like this:
> {noformat}
> failover:(amqps://localhost:5671?transport.useOpenSSL=true&amqp.vhost=localhostamqp.saslLayer=true&amqp.saslMechanisms=EXTERNAL)?failover.maxReconnectAttempts=-1&failover.startupMaxReconnectAttempts=3&failover.warnAfterReconnectAttempts=1&failover.nested.transport.contextProtocol=TLSv1.2&jms.populateJMSXUserID=true&jms.localMessageExpiry=true&jms.requestTimeout=60000&jms.sendTimeout=60000&jms.receiveNoWaitLocalOnly=true&jms.validatePropertyNames=false&jms.redeliveryPolicy.maxRedeliveries=0&jms.redeliveryPolicy.outcome=REJECTED&jms.presettlePolicy.presettleAll=false
> {noformat}
> Looking at the documentation at [https://qpid.apache.org/releases/qpid-jms-1.6.0/docs/index.html] the parameters {*}jms.redeliveryPolicy.maxRedeliveries{*}, *jms.redeliveryPolicy.outcome* and *jms.presettlePolicy.presettleAll* still exist, so I don't really understand why this fails now.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org