Skip to content

version command sometimes fails with 500 #192

@boris-horner

Description

@boris-horner

In a server (Linux / mono) based rendering scenario, the version command sometimes fails with error 500. This is reproducible with the specific PDF data, most other data always works.

Versioning the same file using the Windows client works without a problem (which internally calls exactly the same version command with the same low-level client-server-library on the client, and the same timeout settings that are by far long enough).

I have no idea what's wrong here. To track this, it would be good to have more detailed logging in the version command (before and after every "dangerous" step - perhaps this is a tika issue?)

Or if such logging already exists, how can I swith it on?

These are the current log settings:

  <root level="DEBUG">
    <appender-ref ref="SIFT" />
    <appender-ref ref="FILE" />
  </root>

 <logger name="org.hibernate" level="WARN"/>
 <logger name="org.hhibernate.cfg" level="WARN"/>
 <logger name="org.hibernate.cfg.annotations.EntityBinder" level="WARN"/>
 <logger name="org.hibernate.loader.entity.EntityLoader" level="WARN"/>
 <logger name="server.index" level="DEBUG"/>
 <logger name="server.index.IndexItem" level="DEBUG"/>
 <logger name="server.helpers" level="INFO"/>
 <logger name="server.data" level="INFO"/>
 <logger name="server.trigger" level="INFO"/>
 <logger name="server.CmdInterpreter" level="DEBUG"/>
 <logger name="server.CmnServer" level="DEBUG"/>
 <logger name="utils.HibernateSession" level="INFO"/>
 <logger name="server.dao.UserDAOHibernate" level="INFO"/>

 <logger name="server.Session" level="INFO"/>
 <logger name="server.User" level="INFO"/>
 <logger name="server.data.ObjectSystemData" level="DEBUG"/>
 <logger name="server.lifecycle.LifeCycleState" level="INFO"/>

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions