Internal Website Search

1-9 of 9 results


	General Settings and Logging . The supported logging levels are: " fatal " "error" "warning" "info" "trace" "debug"
	UTF Error .objectdb.o.SHN.x(SHN.java:157) at com.objectdb.o.HND.run(HND.java:134) ... 1 more FATAL : JSF1073 ... string FATAL : /person/List.xhtml @25,35 value="#{personController.items}": javax.ejb.EJBException
	Possible cause for "Enhancement of type ... is old and cannot be used" /issue/1924#item-5 . The initial error (with inevitable fatal side-effects) is similar
	Failed to commit transaction: Attempt to commit a rollback only transaction Anyone know what this means?? Suddenly cropped up. Failed to commit transaction: Attempt to commit a rollback only transaction (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:271) at javax.jdo.Transaction$commit.call(Unknown Source) dmoshal David Moshal Some fatal exceptions mark
	Query fails with failed to read ;(logger "store.file", level fatal , so probably no need for any configuration change if fatal logging
	Unexpected exception (Error 990) com.objectdb.o.InternalException it's really interesting: If we change the loggingLevel from " fatal " to "warning
	Querying error - java.lang.ClassCastException: com.objectdb.o.STV :*: fatal ] java.lang.ClassCastException: com.objectdb.o.STV at com.objectdb.o.PBI.p(PBI.java:91) at com
	database corrupt system is shared). Accessing ObjectDB in embedded mode directly from two processes is fatal . Regarding
	javax.jdo.JDOFatalException JDO Exception JDOFatalException java.lang.Object ∟ java.lang.Throwable ∟ java.lang.Exception ∟ java.lang.RuntimeException ∟ javax.jdo.JDOException ∟ javax.jdo.JDOFatalException This class represents exceptions that are fatal ; that is, the condition that caused