Hibernate example source code file (appendix-Troubleshooting.xml)

This example Hibernate source code file (appendix-Troubleshooting.xml) is included in the DevDaily.com "Java Source Code Warehouse" project. The intent of this project is to help you "Learn Java by Example" ^TM.

Java - Hibernate tags/keywords

a, book_entities, book_entities, certain, doctype, hibernate, hibernate, jvm, jvms, jvms, oasis//dtd, system, the, xml

The Hibernate appendix-Troubleshooting.xml source code

<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "Hibernate_Development_Guide.ent">
%BOOK_ENTITIES;
]>
<appendix id="appendix-Troubleshooting">
    <title>Troubleshooting

    <section>
        <title>Log messages
        <para>
            This section discusses certain log messages you might see from Hibernate and the "meaning" of those
            messages.  Specifically, it will discuss certain messages having a "message id", which for Hibernate
            is always the code <literal>HHH followed by a numeric code.  The table below is ordered
            by this code.
        </para>
        <table>
            <title>Explanation of identified log messages
            <tgroup cols="2">
                <thead>
                    <row>
                        <entry>Key
                        <entry>Explanation
                    </row>
                </thead>
                <tbody>
                    <row>
                        <entry>HHH000002
                        <entry>
                            <para>
                                Indicates that a session was left associated with the
                                <classname>org.hibernate.context.internal.ThreadLocalSessionContext that is used
                                to implement thread-based current session management.  Internally that class uses a
                                ThreadLocal, and in environments where Threads are pooled this could represent a
                                potential "bleed through" situation.  Consider using a different
                                <interfacename>org.hibernate.context.spi.CurrentSessionContext
                                implementation.  Otherwise, make sure the sessions always get unbound properly.
                            </para>
                        </entry>
                    </row>
                    <row>
                        <entry>HHH000408
                        <entry>
                            <para>
                                Using workaround for JVM bug in <classname>java.sql.Timestamp.  Certain
                                JVMs are known to have a bug in the implementation of
                                <classname>java.sql.Timestamp that causes the following condition to
                                evaluate to <literal>false: new Timestamp(x).getTime() != x.
                                A huge concern here is to make sure you are not using temporal based optimistic
                                locking on such JVMs.
                            </para>
                        </entry>
                    </row>
                </tbody>
            </tgroup>
        </table>
    </section>

</appendix>