ObjectDB Database Search

feedback. Reported also to Zeroturnaround for JRebel. When using JRebel I am getting copious server log ... it cause any further issues? You may suppress these warnings by reducing logging level

for. I would like to log (in the console or in a separate log file) what it's actually executing

\nbproject\build-impl.xml:1050: The module has not been deployed. See the server log for details ... Priya Please follow the instructions in the error message and check the server log for details

. Second: LOG . log (Level.INFO, "Created client {0}", c.getId()); Here is when the error happens, when c

we want to run several embedded systems on one server. In principle this is working but there are endless logs generated reporting about a double used port. Ist there a possibility to configure ... the ObjectDB configuration: support Support we switched off the embedded server, but still have logs

Eugen Please post the complete stack trace including nested exceptions (check the ObjectDB log file ... . With logging I know, that error take place on this line: em.getTransaction().commit(); As

04:56:02,075 INFO [org.jboss.as. logging ] JBAS011502: Removing bootstrap log handlers 04:56:02,078

of your application. support Support Hi, we only use one entity class version.  Attached second log file ... the log “08:44:09,440 ERROR [stderr] (http--10.10.10.60-8080-3) Failed to write the value of field field

if there is a way to know what settings ODB is using when it starts up? Would be useful to log the location ... . So, would be useful to log , at startup, current config file location and contents

the logs were not opening but recentely we have faced a strange issue , we have used a new build machine ... after installing the application on user pc we are able to open the logs without any issue

, Browser, etc.). In addition, check if there are exceptions in the console or in the server log . support ... get no execptions in server log and sometimes yes like here: Launching GlassFish on Felix platform

previous versions). Could you please post a stack trace of the error (from the log file) or provide ... the stack trace in the log of the database explorer. The interface CodeArchitectureExt is a private

you find this stack trace, in the log file? on the server, client or both? If you get the stack trace ... We are getting the log only on client-side. You're right  setDefaultUncaughtExceptionHandler works

.remoting] JBoss Remoting version 3.2.3.GA 08:17:22,243 INFO [org.jboss.as. logging ] JBAS011502: Removing bootstrap log handlers 08:17:22,246 INFO [org.jboss.as.configadmin] (ServerService Thread Pool

the log file. support Support In the log file there are these lines: [2012-12-18 09:04:35 #1 server

Please check for a longer stack trace (including nested stack traces) in the log file. support Support

the change log since version 2.8.3, there is always a chance that an issue happens only in specific versions

is unclear, even after reviewing the bug report and the log files. The schema evolution rules

://localhost:6136/technolink.odb;user=admin;password=admin exception in the Karaf log . I have deployed

the exception and output a log message like "Java 8 weaving currently not supported." instead

about that, this shouldn't happen. Pre 2.3.7 activation codes should work with 2.3.7. But in the logs I

, including nested exceptions, in the log file. support Support Hi support, Yes, stack trace shows

my server, and there are no errors logged for this. FastModel Ben Schreiber The problem

after we installed an update and I was the only logged in user. So it beeing another Thread closing

During import big logs we are observed some memory leaks inside of ObjectDb, so, could you explain what we did incorrectly or investigate how to fix it ASAP. Source code which causing memory leaks: m_EntityMgrFactory = Persistence.createEntityManagerFactory( "objectdb:" + aFilename ); m

Hi, We have a memory leak in our application which seems to be related with ObjectDB. Basically, we use single instance of EntityManager, which is opened on aplication initialization and closed when the user logs out, as well as EntityManagerFactory. We use em.clear() after every commit

for this example, but if you look at logs : Store: 4, size: 10 Offer: Offer for product: 94, store: 4

just the one type.  The log file shows the same stack trace and nothing else of note. Crispy

) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at com.sun.common.util. logging

has no permission to create files at that path. Please check also the ObjectDB log file on the server

. When the project runs it logs creation of objects. Please note that there are 2 Project objects, and note ... both in my logged output and by examining the result in the Explorer (which it seems is not

as per the previous issue I logged , I haven't added or removed any entities but I try and query ... ) and the below errors in the logs . I can query the object fine by non-indexed fields and by the @Id.  

an unexpected index state during a query update. You should see some log lines starting at "Attempt to remove a non existing index entry" in the ObjectDB server log file. Could you please post

a query hint ( see issue #2379 ). Added logging when the number of allowed entity classes is exceeded ( feature request #2412 ). Added logging to diagnose unexpected duplicate index entry ( issue

get the following error (you can also see the log message containing the String parameter ... you can see from the log /stacktrace, the query parameter is 'default'). This have been working for quite some

these in the log : [2020-07-24 10:56:45 #50 store]  SectionClassifier: SectionClassifier{'bd127e47 ... of the log : [2020-07-13 17:10:29 #7 store] RetrievalTask.reportSecondaryResult: page#55027945, reader

Improved processing of some sorts of queries. Added support for using ObjectDB with JPA 1 jar in the classpath. Changed server start avoiding new process creation. Added logging for class loading ... a bug in the new log based (recording) recovery from failure mechanism. Fixed a bug in finding

the full log in case it helps (sorry I should have attached it from the start). The following is an extract from a production log which is also showing the error (nothing else of interest in the file

cannot correctly write back into the database file, is it possible that the db log file remains in the file ... log so that the repaired database has not any data lost? btc_es BTC EmbeddedSystems If recovery

expression. Added the ability to disable hollow objects . Added TRACE level logging of query execution ... and closing. Improved connecting and disconnecting performance when logging is disabled. Improved closing

works without problems. Objectdb logs does not contains any problem logs in this time

After running without issue, uninterrupted for seven months, our instance stopped silently.  The contents of the log are as follows: Object DB log : ObjectDB Server started on port 6138. ObjectDB Server stopped. ObjectDB Server started on port 6138. ObjectDB Server stopped. ObjectDB Server

Added support of editing enum values in the Explorer. Added logging of type registration . Added error message when using mapped by (inverse) collections and maps of invalid types. Changed JOIN FETCH to act as LEFT JOIN in path expressions. Updated the PDF manual. Fixed a possible deadlock

Hello, we have found another exception in objectdb. log : java.lang.ClassCastException: com.objectdb.o.SLV cannot be cast to com.objectdb.o.RSV at com.objectdb.o.RSV.compareTo(RSV.java:158) at com.objectdb.o.INV.compareTo(INV.java:215) at com.objectdb.o.INV.J(INV.java:315) at com.objectdb.o.PAG

. We are monitoring the log closely and noticed your attempts to edit your post. Editing should work now

") private java.util.Map z_regulatedSchemes = new java.util.HashMap ();   I have attached the log

(which should be found in the log file) can help in understanding the context. If you are using client-server mode

it. The Glassfish3.01 log stacktrace is: WARNING: StandardWrapperValve[Faces Servlet]: PWC1406: Servlet.service

. We can release a new build with writing relevant information to the log when it happens in order

see that the exception is written to the log with a WARING level. It would be changed to TRACE in the next build (2.3.3_01).  support Support