<?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: db connect issues after upgrade in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/db-connect-issues-after-upgrade/m-p/167840#M98195</link>
    <description>&lt;P&gt;This is a known issue that persists through DB Connect version 1.1.2.  See: &lt;A href="http://docs.splunk.com/Documentation/DBX/1.1.2/DeployDBX/Releasenotes"&gt;http://docs.splunk.com/Documentation/DBX/1.1.2/DeployDBX/Releasenotes&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;See workaround here: &lt;A href="http://answers.splunk.com/answers/109920/splunk6-db-connect-111-no-handlers-could-be-found-for-logger-sppjava"&gt;http://answers.splunk.com/answers/109920/splunk6-db-connect-111-no-handlers-could-be-found-for-logger-sppjava&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 03 Feb 2014 21:20:29 GMT</pubDate>
    <dc:creator>sroback_splunk</dc:creator>
    <dc:date>2014-02-03T21:20:29Z</dc:date>
    <item>
      <title>db connect issues after upgrade</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/db-connect-issues-after-upgrade/m-p/167838#M98193</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I just upgraded to the latest db connect, and now my java bridge is in a constant "loading" state. I noticed the following in the splunkd.log:&lt;/P&gt;

&lt;P&gt;12-05-2013 09:51:59.292 -0500 ERROR ExecProcessor - message from "python /elfaqa1A/misc/splunk1a/splunk/etc/apps/dbx/bin/jbridge_server.py" No handlers could be found for logger "spp.java"&lt;/P&gt;

&lt;P&gt;Has anyone run into this?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Dec 2013 14:57:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/db-connect-issues-after-upgrade/m-p/167838#M98193</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2013-12-05T14:57:04Z</dc:date>
    </item>
    <item>
      <title>Re: db connect issues after upgrade</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/db-connect-issues-after-upgrade/m-p/167839#M98194</link>
      <description>&lt;P&gt;Yes, a number of people have.&lt;BR /&gt;
After the install you have to open and save the DB Connect &amp;gt; Settings page.&lt;/P&gt;

&lt;P&gt;See this post:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/answers/102729/db-connect-error-in-upgrading-to-110-version"&gt;http://answers.splunk.com/answers/102729/db-connect-error-in-upgrading-to-110-version&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Dec 2013 15:19:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/db-connect-issues-after-upgrade/m-p/167839#M98194</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2013-12-05T15:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: db connect issues after upgrade</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/db-connect-issues-after-upgrade/m-p/167840#M98195</link>
      <description>&lt;P&gt;This is a known issue that persists through DB Connect version 1.1.2.  See: &lt;A href="http://docs.splunk.com/Documentation/DBX/1.1.2/DeployDBX/Releasenotes"&gt;http://docs.splunk.com/Documentation/DBX/1.1.2/DeployDBX/Releasenotes&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;See workaround here: &lt;A href="http://answers.splunk.com/answers/109920/splunk6-db-connect-111-no-handlers-could-be-found-for-logger-sppjava"&gt;http://answers.splunk.com/answers/109920/splunk6-db-connect-111-no-handlers-could-be-found-for-logger-sppjava&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2014 21:20:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/db-connect-issues-after-upgrade/m-p/167840#M98195</guid>
      <dc:creator>sroback_splunk</dc:creator>
      <dc:date>2014-02-03T21:20:29Z</dc:date>
    </item>
  </channel>
</rss>

