437 words


2017-01-31 10:30

Good morning,

OS: Windows Server 2008 R2 64 bit

Java: Java Server JRE 8u121 for Windows x64

ObjectDB: version 2.6.9 build 5

Problem description:

ObjectDB server will start and function normally (?) but an exception is logged:

"java.lang.NoClassDefFoundError: com/sun/tools/attach/AttachNotSupportedException" (see attachment to this thread).

I also added C:\Java\jdk8\lib\tools.jar to the classpath, but that did not make any difference.

What am I doing wrong?

Best regards,


RuiRosado's picture
Joined on 2014-09-23
User Post #1
2017-01-31 18:28

Enhancement requires the availiability of classes that are referenced from enhanced classes, and probably AttachNotSupportedException is referenced from an enhanced class.

Usually the ObjectDB server doesn't need any external class. It uses enhancement internally to prepare classes based on the object model that is stored in the database.

Do you get the same error when you open the database in the Explorer?

Can you post a sample database that demonstrates the problem?

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support's picture
Joined on 2010-05-03
User Post #2,689
2017-02-02 11:36

Thank you for your assistance.

We are experiencing this error when opening any database. Also when we open a database from Explorer.

An example db is in the attachment to this post.

Could this have anything to do with the fact that we are running on windows 2008 server x64 OS with java 1.8 x64?

We were using the same databases before (= last week :) on a windows10 x64 OS with java 1.7 x32 and had no problem at all.


  • we included the path to \objectdb\bin in the CLASSPATH environment variable
  • we are using 'server-b.exe' and also 'explorer-b.exe' instead of 'server.exe' and 'explorer.exe', because starting the last two exe's will fail with an error: 'Error starting Java VM'.
RuiRosado's picture
Joined on 2014-09-23
User Post #2
2017-02-04 15:45

We 'solved' the problem:

  • this error disappeared after we uninstalled java 1.8 from the server at our datacenter. After reinstalling and resetting the classpath this message did not appear again.
  • we had a subsequent problem: objectdb was trying to enhance quite some (about 183) classes in the lib folder of Apache TomEE. That was caused because we had '-javaagent:c:\objectdb\bin\objectdb.jar' as default VM argument for the JRE in Eclipse. After removing the javaagent, everything works fine.
  • FYI: Eclipse Neon, Java JDK 1.8, Apache TomEE 7.0.2-plume. We start ObjectDB by calling server-b.exe and we use explorer-b.exe (server.exe and explorer.exe will not start with JDK 1.8: 'Failed to find Java VM').

Now we can start all our web applications on the remote server.



RuiRosado's picture
Joined on 2014-09-23
User Post #3
2017-02-05 08:28

Thank you for the update. We can comfirm that the sample database in #3 above has no errors, and we could open it with no issues using Java 8 on Windows 10.

Apparently this error message is related to issues with the Java installation rather than with ObjectDB, as understood from some threads on the Internet and from your new report.

server-b.exe and explorer-b.exe are provided because server.exe and explorer.exe fail to work on some systems. Unfortunately on other systems server-b.exe and explorer-b.exe fail. So currently both of these pairs are provided.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support's picture
Joined on 2010-05-03
User Post #2,691

Post Reply

Please read carefully the posting instructions - before posting to the ObjectDB website.

  • You may have to disable pop up blocking in order to use the toolbar (e.g. in Chrome).
  • Use ctrl + right click to open the browser context menu in the editing area (e.g. for using a browser spell checker).
  • To insert formatted lines (e.g. Java code, stack trace) - select a style in the toolbar and then insert the text in the new created block.
  • Avoid overflow of published source code examples by breaking long lines.
  • You may mark in paragraph code words (e.g. class names) with the code style (can be applied by ctrl + D).
  • Long stack traces (> 50 lines) and complex source examples (> 100 lines) should be posted as attachments.
Maximum file size: 32 MB