[
https://issues.apache.org/jira/browse/TIKA-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393184#comment-14393184
]
Tyler Palsulich commented on TIKA-1592:
---------------------------------------
Thanks for reporting this, [~michaelcouck]! Just to be clear, you're building
Tika 1.7 from source?
Which test case causes this? After a quick {{grep}}, I don't see any gconf or
dbus references (don't know why there would be any, off the top of my head...).
When you say the logging is a a gig, is that what is sent to stdout when doing
{{mvn install}}? Or something else?
> It seems dbus and x11 server are invoked, and fails for some reason too
> -----------------------------------------------------------------------
>
> Key: TIKA-1592
> URL: https://issues.apache.org/jira/browse/TIKA-1592
> Project: Tika
> Issue Type: Bug
> Affects Versions: 1.7
> Environment: CentOs 6.6, Java 1.7
> Reporter: Michael Couck
>
> Exception running unit tests:
> GConf Error: Failed to contact configuration server; some possible causes are
> that you need to enable TCP/IP networking for ORBit, or you have stale NFS
> locks due to a system crash. See http://projects.gnome.org/gconf/ for
> information. (Details - 1: Not running within active session)
> Is Tika trying to start an x11 server using dbus? Why? This breaks the unit
> tests, the logging is a gig for each run, and even a 64 core server is 100%
> cpu during the failure. I am completely confounded. Any ideas?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
