<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException in VMware Aria Automation Orchestrator Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186672#M17825</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just make sure you use a 5.5.1 client&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 Mar 2014 18:07:22 GMT</pubDate>
    <dc:creator>cdecanini_</dc:creator>
    <dc:date>2014-03-19T18:07:22Z</dc:date>
    <item>
      <title>Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186667#M17820</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone encountered this error before? Screen shot is below. Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Untitled.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/50702iFE4F7F60FA710C5B/image-size/large?v=v2&amp;amp;px=999" role="button" title="Untitled.png" alt="Untitled.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 17:50:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186667#M17820</guid>
      <dc:creator>FSvcoe</dc:creator>
      <dc:date>2014-03-19T17:50:53Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186668#M17821</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This appears when you are attempting to connect the vCO client through a Load Balancer - this is NOT supported. Web services Are supported through a LB, but not the client.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 17:52:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186668#M17821</guid>
      <dc:creator>Burke-</dc:creator>
      <dc:date>2014-03-19T17:52:42Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186669#M17822</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Burke, but no load balancer, or firewall for that matter. These are all on the same local network segment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 17:55:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186669#M17822</guid>
      <dc:creator>FSvcoe</dc:creator>
      <dc:date>2014-03-19T17:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186670#M17823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hmm... It looks like you changed the port to 443 in that screenshot - is that the correct port for the vCO Server? Default is :8281 ... If you changed other ports that may be contributing to the issue here... Never seen this issue when there is nothing between the vCO client and server.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 18:00:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186670#M17823</guid>
      <dc:creator>Burke-</dc:creator>
      <dc:date>2014-03-19T18:00:33Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186671#M17824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, that is the correct port. We modify our configs to use it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I should point out this is an existing server, and has worked just fine with the 5.5.0 versions. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 18:04:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186671#M17824</guid>
      <dc:creator>FSvcoe</dc:creator>
      <dc:date>2014-03-19T18:04:29Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186672#M17825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just make sure you use a 5.5.1 client&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 18:07:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186672#M17825</guid>
      <dc:creator>cdecanini_</dc:creator>
      <dc:date>2014-03-19T18:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186673#M17826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks. I've checked that, and tried using the web client-it reports a slightly different issue-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anywhere in the logs I should be checking?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Untitled2.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/50703iE520331671616A3A/image-size/large?v=v2&amp;amp;px=999" role="button" title="Untitled2.png" alt="Untitled2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 18:24:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186673#M17826</guid>
      <dc:creator>FSvcoe</dc:creator>
      <dc:date>2014-03-19T18:24:25Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186674#M17827</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can always check the server.log but not sure if it will give you a clue.&lt;/P&gt;&lt;P&gt;Maybe you need to check your IP / port settings and the http proxy file in the appliance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 20:02:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186674#M17827</guid>
      <dc:creator>cdecanini_</dc:creator>
      <dc:date>2014-03-19T20:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186675#M17828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check this :&lt;/P&gt;&lt;P&gt;/opt/vco-proxy/vco-proxy.conf&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you change it restart it with :&lt;/P&gt;&lt;P&gt;/etc/init.d/vco-proxy restart&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Mar 2014 20:03:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186675#M17828</guid>
      <dc:creator>cdecanini_</dc:creator>
      <dc:date>2014-03-19T20:03:21Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186676#M17829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm encountering the exact same issue. Fresh deployment of the new appliance with a restore of the 5.5.0 appliance's configuration file. Using the default network port, no load balancer. Connecting via the Java web-client.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2014 19:53:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186676#M17829</guid>
      <dc:creator>stevenbright</dc:creator>
      <dc:date>2014-03-20T19:53:07Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186677#M17830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had this issue as well, I had forgotten to update my client to 5.5.1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Mar 2014 17:35:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186677#M17830</guid>
      <dc:creator>mwpreston</dc:creator>
      <dc:date>2014-03-25T17:35:51Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186678#M17831</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Could you provide the exact version of vCO client you are using and vCO server which you are trying to connect (including the build numbers?).&lt;/P&gt;&lt;P&gt;Is this behavior also observed when using java Web Start client (.jnlp)&lt;/P&gt;&lt;P&gt;Could you check if vCO server is accessible (&lt;A href="https://10.23.164.147:8281/vco/api/" title="https://10.23.164.147:8281/vco/api/"&gt;https://10.23.164.147:8281/vco/api/&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note that unfortunately vCO client need to be exactly the same version as vCO server (including the build number).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Mar 2014 12:39:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186678#M17831</guid>
      <dc:creator>igaydajiev</dc:creator>
      <dc:date>2014-03-26T12:39:34Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186679#M17832</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are also seeing this issue with the latest vCO appliance (&lt;SPAN style="color: #000000; font-family: Arial, Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold;"&gt;5.5.1.0 Build 1617225&lt;/SPAN&gt;). It happens when using the downloadable client as well as the web-based client (JNLP). We are using all of the default ports with SSO authentication to vCenter and all of the firewall rules look correct. Here's the Java console output I get when using the JNLP client:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:36.665-0400 INFO&amp;nbsp; [CertTrackerMain] Can not find keystore C:\Program Files (x86)\Java\jre7\lib\security\jssecacerts&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:36.717-0400 INFO&amp;nbsp; [Application] Loading properties at : C:\Users\shane\Downloads\.\vmo.properties ...&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:36.718-0400 INFO&amp;nbsp; [Application] No properties found !&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:36.718-0400 INFO&amp;nbsp; [Application] Loading ...&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:36.856-0400 INFO&amp;nbsp; [Application] Starting...&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:36.858-0400 DEBUG [Preferences] Loading preferences from C:\Users\shane\.vmware\vmware-vmo.cfg ...&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:36.859-0400 INFO&amp;nbsp; [Preferences] Loaded preferences file: C:\Users\shane\.vmware\vmware-vmo.cfg&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:43.329-0400 DEBUG [VSOFactoryClient] Start connection to VMO server : chopin.esx.gatech.edu:8281&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:43.330-0400 DEBUG [VSOFactoryClient] Create Session&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:45.189-0400 DEBUG [TypeConverter] Convertor Re registration of type : Array&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:45.216-0400 DEBUG [VSOFactoryClient] Session created&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:55.447-0400 ERROR [VSOFactoryClient] javax.jms.JMSException: Failed to create session factory&lt;/P&gt;&lt;P&gt;2014-04-04 19:21:55.452-0400 DEBUG [VSOFactoryClient] javax.jms.JMSException: Failed to create session factory&lt;/P&gt;&lt;P&gt;ch.dunes.util.DunesServerException: javax.jms.JMSException: Failed to create session factory&lt;/P&gt;&lt;P&gt;&amp;nbsp; at ch.dunes.model.client.InVMJmsClient.createConnection(InVMJmsClient.java:118)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at ch.dunes.model.client.VCOHornetQJMSClient.connectTopics(VCOHornetQJMSClient.java:79)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:314)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at ch.dunes.model.client.VSOFactoryClient.connect(VSOFactoryClient.java:272)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at ch.dunes.vso.app.VSOClientAuthService.login(VSOClientAuthService.java:45)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at ch.dunes.vso.app.VSOClientAuthService.login(VSOClientAuthService.java:60)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at ch.dunes.vso.app.VSOLoginDialog._doLogin(VSOLoginDialog.java:486)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at ch.dunes.vso.app.VSOLoginDialog.access$400(VSOLoginDialog.java:52)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at ch.dunes.vso.app.VSOLoginDialog$10.run(VSOLoginDialog.java:464)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at java.lang.Thread.run(Unknown Source)&lt;/P&gt;&lt;P&gt;Caused by: javax.jms.JMSException: Failed to create session factory&lt;/P&gt;&lt;P&gt;&amp;nbsp; at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:615)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:145)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at ch.dunes.model.client.InVMJmsClient.createConnection(InVMJmsClient.java:110)&lt;/P&gt;&lt;P&gt;&amp;nbsp; ... 9 more&lt;/P&gt;&lt;P&gt;Caused by: HornetQException[errorCode=2 message=Cannot connect to server(s). Tried with all available servers.]&lt;/P&gt;&lt;P&gt;&amp;nbsp; at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:619)&lt;/P&gt;&lt;P&gt;&amp;nbsp; at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:611)&lt;/P&gt;&lt;P&gt;&amp;nbsp; ... 11 more&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Apr 2014 15:40:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186679#M17832</guid>
      <dc:creator>MarkAtGT</dc:creator>
      <dc:date>2014-04-07T15:40:04Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186680#M17833</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I figured out my issue... cranked up Wireshark and it turns out that it's using a port that wasn't listed in the vCO documentation (8287/tcp). Check and see if you can access your vCO appliance via 8287/tcp.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Apr 2014 16:16:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186680#M17833</guid>
      <dc:creator>MarkAtGT</dc:creator>
      <dc:date>2014-04-07T16:16:42Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186681#M17834</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I will make sure that the documentation is updated.&lt;/P&gt;&lt;P&gt;Just to confirm that in vCO 5.5.1 ports 8286 and 8287 must be accessible also.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Apr 2014 09:28:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186681#M17834</guid>
      <dc:creator>igaydajiev</dc:creator>
      <dc:date>2014-04-08T09:28:17Z</dc:date>
    </item>
    <item>
      <title>Re: Can't connect to VCO 5.5.1 via client-Java timeout-java.jms.JMSException</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186682#M17835</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for the Information.&lt;/P&gt;&lt;P&gt;I had the same issue and with those two ports it is fixed now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Beside that:&lt;/P&gt;&lt;P&gt;We installed on Dec 2013 a fresh vCenter 5.5 with Orchestrator on a Win2k12R2 Server (german language).&lt;/P&gt;&lt;P&gt;After the update we did today to 5.5.1 i found the Orchestrator Firewallrules twice in our Windows Firewall Settings.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2014 16:55:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Can-t-connect-to-VCO-5-5-1-via-client-Java-timeout-java-jms/m-p/2186682#M17835</guid>
      <dc:creator>Kagome</dc:creator>
      <dc:date>2014-06-05T16:55:55Z</dc:date>
    </item>
  </channel>
</rss>

