You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Holger Caesar (JIRA)" <ji...@apache.org> on 2012/08/14 10:49:38 UTC
[jira] [Closed] (QPID-4224) SetClientID does not have an effect
[ https://issues.apache.org/jira/browse/QPID-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Holger Caesar closed QPID-4224.
-------------------------------
Resolution: Fixed
The described workaround works fine. I would however appreciate in future versions if I could just call setClientId() (before connection start, but after creation).
> SetClientID does not have an effect
> -----------------------------------
>
> Key: QPID-4224
> URL: https://issues.apache.org/jira/browse/QPID-4224
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.16
> Environment: Windows 7 64-bit, Java 1.6
> Reporter: Holger Caesar
> Priority: Critical
> Labels: AMQP, ClientID, JMS, QPID
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Hi everyone,
> I am currently evaluating QPID and AMQP in general. I have a JMS test application that works perfectly on a JMS compliant broker (non AMQP) and now I am trying to port it to QPID using only JMS features. Unfortunately I am having problems changing the client ID. I am aware that I can specify it in the AMQ://... string on startup, but since I want to read that string from a single .properties file, that is not a nice solution for 200 clients in parallel. Instead I tried using the setClientID method and setting the ignore_setClientID flag. The only effect this had was to ignore the error that is normally thrown.
> Below you can see the source code that basically does nothing other than reporting the requested ID change. Is there any workaround or solution to this problem??
> Thank you very much for your support,
> Holger
> public void setClientID(String clientID) throws JMSException
> {
> checkNotClosed();
> // in AMQP it is not possible to change the client ID. If one is not specified
> // upon connection construction, an id is generated automatically. Therefore
> // we can always throw an exception.
> if (!Boolean.getBoolean(ClientProperties.IGNORE_SET_CLIENTID_PROP_NAME))
> {
> throw new IllegalStateException("Client name cannot be changed after being set");
> }
> else
> {
> _logger.info("Operation setClientID is ignored using ID: " + getClientID());
> }
> }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org