<?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 The Java Bridge server seems not to be running... in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/The-Java-Bridge-server-seems-not-to-be-running/m-p/199728#M2692</link>
    <description>&lt;P&gt;We found Java Bridge server seems not to be running&lt;/P&gt;

&lt;P&gt;Please advise!&lt;/P&gt;

&lt;P&gt;jbridge.log&lt;BR /&gt;
2014-06-18 09:41:51,931 INFO Checking for obsolete java libraries in /opt/splunk/etc/apps/dbx/bin/lib&lt;BR /&gt;
2014-06-18 09:41:51,934 INFO Started JavaBridgeServer PID=5094&lt;/P&gt;

&lt;P&gt;splunkd.log&lt;BR /&gt;
06-18-2014 09:53:10.627 +0800 WARN  HttpListener - Socket error from 127.0.0.1 while idling: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher&lt;BR /&gt;
dbx.log&lt;BR /&gt;
2014-06-18 09:44:52.439 main:INFO:SplunkContext - Splunk Context initialized: SplunkContext{env=SplunkEnvi&lt;BR /&gt;
ronment{SPLUNK_HOME=/opt/splunk,SPLUNK_DB=/opt/splunk/var/lib/splunk}}&lt;BR /&gt;
2014-06-18 09:44:58.145 main:INFO:Splunkd - Initialized Splunkd REST service service=127.0.0.1:8089 sessio&lt;BR /&gt;
nKey=Rf^lkc54OI0hWjhqMhVbLtreEjjeW7F4Cp^8PQDBAPiO8P55LtqCHmLKlHi3F1aQXJLeI0qcEzysf3LUu_MeSfV^Tx2ptI_gLmWq8&lt;BR /&gt;
t2s&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 16:52:51 GMT</pubDate>
    <dc:creator>edwardman88</dc:creator>
    <dc:date>2020-09-28T16:52:51Z</dc:date>
    <item>
      <title>The Java Bridge server seems not to be running...</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/The-Java-Bridge-server-seems-not-to-be-running/m-p/199728#M2692</link>
      <description>&lt;P&gt;We found Java Bridge server seems not to be running&lt;/P&gt;

&lt;P&gt;Please advise!&lt;/P&gt;

&lt;P&gt;jbridge.log&lt;BR /&gt;
2014-06-18 09:41:51,931 INFO Checking for obsolete java libraries in /opt/splunk/etc/apps/dbx/bin/lib&lt;BR /&gt;
2014-06-18 09:41:51,934 INFO Started JavaBridgeServer PID=5094&lt;/P&gt;

&lt;P&gt;splunkd.log&lt;BR /&gt;
06-18-2014 09:53:10.627 +0800 WARN  HttpListener - Socket error from 127.0.0.1 while idling: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher&lt;BR /&gt;
dbx.log&lt;BR /&gt;
2014-06-18 09:44:52.439 main:INFO:SplunkContext - Splunk Context initialized: SplunkContext{env=SplunkEnvi&lt;BR /&gt;
ronment{SPLUNK_HOME=/opt/splunk,SPLUNK_DB=/opt/splunk/var/lib/splunk}}&lt;BR /&gt;
2014-06-18 09:44:58.145 main:INFO:Splunkd - Initialized Splunkd REST service service=127.0.0.1:8089 sessio&lt;BR /&gt;
nKey=Rf^lkc54OI0hWjhqMhVbLtreEjjeW7F4Cp^8PQDBAPiO8P55LtqCHmLKlHi3F1aQXJLeI0qcEzysf3LUu_MeSfV^Tx2ptI_gLmWq8&lt;BR /&gt;
t2s&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 16:52:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/The-Java-Bridge-server-seems-not-to-be-running/m-p/199728#M2692</guid>
      <dc:creator>edwardman88</dc:creator>
      <dc:date>2020-09-28T16:52:51Z</dc:date>
    </item>
    <item>
      <title>Re: The Java Bridge server seems not to be running...</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/The-Java-Bridge-server-seems-not-to-be-running/m-p/199729#M2693</link>
      <description>&lt;P&gt;This might be relevant to the second error you reference.&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/296893/how-can-i-force-a-specific-ecdhe-cipher-to-communi.html"&gt;https://answers.splunk.com/answers/296893/how-can-i-force-a-specific-ecdhe-cipher-to-communi.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 14:10:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/The-Java-Bridge-server-seems-not-to-be-running/m-p/199729#M2693</guid>
      <dc:creator>bohanlon_splunk</dc:creator>
      <dc:date>2016-01-26T14:10:34Z</dc:date>
    </item>
  </channel>
</rss>

