68 words

Issue #250 - Enhancer: non-zero exit code at exceptions

Feature RequestVersion: Priority: HighStatus: FixedReplies: 2
#1
2015-03-23 08:13

Hello,

we have found that the enhancer returned an non-zero exit code on errors.

You can change this so that the error of the enhancers can be detected.

btc_es
btc_es's picture
Joined on 2014-10-20
User Post #36
#2
2015-03-30 08:42

Thank you for this report. Starting build 2.6.1_04 the Enhancer exits with non zero code on errors.

Note that System.exit is now invoked (on errors) so calling Enhancer.main from a running program may terminate the JVM.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support
support's picture
Joined on 2010-05-03
User Post #2,178
#3
2015-04-01 11:11

Thank you. It works.

btc_es
btc_es's picture
Joined on 2014-10-20
User Post #40

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.
Attachments:
Maximum file size: 32 MB
Cancel