We Keep Coding

Orientdb Errors : can't load log handler "java.util.logging.FileHandler" etc

I'm a total novice to graph database and I've giving Orientdb 2.2.34 a go. I'm using a Windows 10 machine with Java 10.0.1 JRE and JDK. When I run the server.bat file I get the following errors displayed and I don't know where to start to solve them:
Can't load log handler "java.util.logging.FileHandler"
java.nio.file.AccessDeniedException: ..\log\orient-server.log.0.lck
java.nio.file.AccessDeniedException: ..\log\orient-server.log.0.lck
at java.base/sun.nio.fs.WindowsException.translateToIOException(Unknown
Source)
at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(Unknown
Source)
at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(Unknown
Source)
at java.base/sun.nio.fs.WindowsFileSystemProvider.newFileChannel(Unknown
Source)
at java.base/java.nio.channels.FileChannel.open(Unknown Source)
at java.base/java.nio.channels.FileChannel.open(Unknown Source)
at java.logging/java.util.logging.FileHandler.openFiles(Unknown Source)
at java.logging/java.util.logging.FileHandler.(Unknown Source)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
Source)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Source)
at java.base/java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.base/java.lang.Class.newInstance(Unknown Source)
at java.logging/java.util.logging.LogManager.createLoggerHandlers(Unknown
Source)
at java.logging/java.util.logging.LogManager.access$1000(Unknown Source)
at java.logging/java.util.logging.LogManager$4.run(Unknown Source)
at java.logging/java.util.logging.LogManager$4.run(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.logging/java.util.logging.LogManager.loadLoggerHandlers(Unknown
Source)
at java.logging/java.util.logging.LogManager.initializeGlobalHandlers(Unknown
Source)
at java.logging/java.util.logging.LogManager.access$1800(Unknown Source)
at java.logging/java.util.logging.LogManager$RootLogger.accessCheckedHandlers(Unknown
Source)
at java.logging/java.util.logging.Logger.getHandlers(Unknown Source)
at com.orientechnologies.common.log.OLogManager.installCustomFormatter(OLogManager.java:84)
at com.orientechnologies.orient.server.OServer.(OServer.java:135)
at com.orientechnologies.orient.server.OServer.(OServer.java:118)
at com.orientechnologies.orient.server.OServerMain.create(OServerMain.java:28)
at com.orientechnologies.orient.server.OServerMain$1.run(OServerMain.java:47)
2018-05-01 21:47:35:110 INFO Loading configuration from: C:/Program
Files/Orientdb-2.2.34/config/orientdb-server-config.xml...WARNING: An
illegal reflective access operation has occurred WARNING: Illegal
reflective access by
com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1
(file:/C:/Program%20Files/Orientdb-2.2.34/lib/jaxb-impl-2.2.3.jar) to
method
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of
com.sun.xml.bind.v2.runtime.reflect.opt.Injector$1 WARNING: Use
--illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be
denied in a future release
2018-05-01 21:47:35:371 INFO OrientDB Server v2.2.34 (build
f340442755a31eabc91b87cb3ef99eda5cee6ebd, branch 2.2.x) is starting
up... 2018-05-01 21:47:35:377 INFO Databases directory: C:\Program
Files\Orientdb-2.2.34\databases 2018-05-01 21:47:35:413 INFO
Configuration of usage of soft references inside of containers of
results of SQL execution 2018-05-01 21:47:35:426 INFO Initial and
maximum values of heap memory usage are equal, containers of results
of SQL executors will use soft references by default 2018-05-01
21:47:35:427 INFO Auto configuration of disk cache size. 2018-05-01
21:47:35:483 INFO 8449830912 B/8058 MB/7 GB of physical memory were
detected on machine 2018-05-01 21:47:35:483 INFO Detected memory
limit for current process is 8449830912 B/8058 MB/7 GB 2018-05-01
21:47:35:486 INFO OrientDB auto-config DISKCACHE=3,962MB
(heap=2,048MB direct=524,288MB os=8,058MB) 2018-05-01 21:47:35:599
INFO {db=OSystem} Creating the system database 'OSystem' for current
serverException 1E7ECDE6 in storage plocal:C:/Program
Files/Orientdb-2.2.34/databases/OSystem: 2.2.34 (build
f340442755a31eabc91b87cb3ef99eda5cee6ebd, branch 2.2.x)
com.orientechnologies.orient.core.exception.OStorageException: Cannot
create folders in storage with path C:/Program
Files/Orientdb-2.2.34/databases/OSystem
DB name="OSystem"
at com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage.create(OLocalPaginatedStorage.java:127)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.create(ODatabaseDocumentTx.java:438)
at com.orientechnologies.orient.server.OSystemDatabase.init(OSystemDatabase.java:160)
at com.orientechnologies.orient.server.OSystemDatabase.(OSystemDatabase.java:44)
at com.orientechnologies.orient.server.OServer.initSystemDatabase(OServer.java:1309)
at com.orientechnologies.orient.server.OServer.activate
(OServer.java:367)
at com.orientechnologies.orient.server.OServerMain$1.run(OServerMain.java:48)
Error during server execution
com.orientechnologies.orient.core.exception.ODatabaseException: Cannot create database 'OSystem'
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.create(ODatabaseDocumentTx.java:506)
at com.orientechnologies.orient.server.OSystemDatabase.init(OSystemDatabase.java:160)
at com.orientechnologies.orient.server.OSystemDatabase.<init>(OSystemDatabase.java:44)
at com.orientechnologies.orient.server.OServer.initSystemDatabase(OServer.java:1309)
at com.orientechnologies.orient.server.OServer.activate(OServer.java:367)
at com.orientechnologies.orient.server.OServerMain$1.run(OServerMain.java:48)
Caused by: com.orientechnologies.orient.core.exception.OStorageException: Cannot
create folders in storage with path C:/Program
Files/Orientdb-2.2.34/databases/OSystem
DB name="OSystem"
at com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage.create(OLocalPaginatedStorage.java:127)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.create(ODatabaseDocumentTx.java:438)
... 5
more

Looks like you need to edit your java.util.logging.FileHandler.pattern in orientdb-server-log-properties to an absolute path instead of a relative.
e.g. C:\Program Files\Orientdb-2.2.34\log

If you are running this on Windows with Server.BAT, then that BAT requires its working directory is set to there. You can edit the orientdb-server-log-properties and that's a correct answer.
Alternately, you can just change the working directory to where the bin is and start the server from there without a need to change the config file and that's what I opted to do.
I have a small orientStart.ps1 file that I can run from anywhere that look like this.
The environment ORIENTDB_HOME is always required.
Push-Location
$env:ORIENTDB_HOME="C:\orientdb-3.1.1"
Set-Location $env:ORIENTDB_HOME\bin
$SERVER ="server.bat"
cmd /c $SERVER
Pop-Location

Start OrientDB's server.bat from within a Windows CLI that has been started with Admin privileges.

Java-FX failed to load resource exception

I am running my Java-FX application via webstart by tomcat server.
After signing and versioning of jars I having this problem when am accessing it through web browser.
I am using jnlp and version protocol to start the application through tomcat server.
ExitException[ 3]com.sun.deploy.net.FailedDownloadException: Unable to load resource:
(httP://127.0.0.1:8080/gyms/lib/commons-collections-3.2.1.jar?version-id=1.0.1, 1.0.1)
at sun.plugin2.applet.JNLP2Manager.downloadResources(Unknown Source)
at sun.plugin2.applet.JNLP2Manager.prepareLaunchFile(Unknown Source)
at sun.plugin2.applet.JNLP2Manager.loadJarFiles(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

It seems you are using a jnlp-file with a line like this:
<jar href="commons-collections-3.2.1.jar" version="1.0.1" />
So you are using the version-based download protocol. This will result in the server looking for a file called commons-collections-3.2.1__V1.0.1.jar which apparently is not there.
Bottom line: do not specify two conflicting version-numbers in your jnlp. Decide wether you want to use versioned download and omit the version-number in the href-attribute or use simple download and omit the version-attribute.

Problem is solved because I am using Java 1.7.51 update and also i am usin third api which is not supported in java 8 which is also installed in my desktop.
The program(x86) should not have any version of java greater than java 7 as the application is taking java/bin from x86 only.
that is why that failed download exception is coming at run time.

Google Cloud appcfg.cmd can't deploy because can't find appengine-web.xml

I'm just trying to get the basic hello world project built and deployed by following the instructions on https://console.developers.google.com/start/appengine. I got through all the steps but the last one, Step 6, where I got this error:
D:\google-app-engine\appengine-try-java>appcfg.cmd -A aqueous-flames-561 update
target\appengine-try-java
Reading application configuration data...
Apr 24, 2014 4:27:39 PM com.google.apphosting.utils.config.AppEngineWebXmlReader
readAppEngineWebXml
SEVERE: Received exception processing target/appengine-try-java\WEB-INF/appengin
e-web.xml
com.google.apphosting.utils.config.AppEngineConfigException: Could not locate D:
\google-app-engine\appengine-try-java\target\appengine-try-java\WEB-INF\appengin
e-web.xml
at com.google.apphosting.utils.config.AppEngineWebXmlReader.getInputStre
am(AppEngineWebXmlReader.java:140)
at com.google.apphosting.utils.config.AppEngineWebXmlReader.readAppEngin
eWebXml(AppEngineWebXmlReader.java:75)
at com.google.appengine.tools.admin.Application.<init>(Application.java:
185)
at com.google.appengine.tools.admin.Application.readApplication(Applicat
ion.java:322)
at com.google.appengine.tools.admin.AppCfg.readWar(AppCfg.java:280)
at com.google.appengine.tools.admin.AppCfg.readApplication(AppCfg.java:2
71)
at com.google.appengine.tools.admin.AppCfg.<init>(AppCfg.java:209)
at com.google.appengine.tools.admin.AppCfg.<init>(AppCfg.java:121)
at com.google.appengine.tools.admin.AppCfg.main(AppCfg.java:117)
Caused by: java.io.FileNotFoundException: target\appengine-try-java\WEB-INF\appe
ngine-web.xml (The system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(Unknown Source)
at java.io.FileInputStream.<init>(Unknown Source)
at com.google.apphosting.utils.config.AppEngineWebXmlReader.getInputStre
am(AppEngineWebXmlReader.java:137)
... 8 more
Bad configuration: Could not locate D:\google-app-engine\appengine-try-java\targ
et\appengine-try-java\WEB-INF\appengine-web.xml
Caused by: target\appengine-try-java\WEB-INF\appengine-web.xml (The system can
not find the file specified)
Please see the logs [C:\Users\MICHAE~1\AppData\Local\Temp\appcfg7867248686279117
668.log] for further information.
D:\google-app-engine\appengine-try-java>
I was able to successfully complete Step 5, Run Your App Locally (https://console.developers.google.com/start/appengine). So I’m not sure how I can run locally if I indeed am missing an appengine-web.xml file.

Jordan Fish of Google Cloud Platform Support said that Step 6 of https://console.developers.google.com/start/appengine contains a mistake which he said will be fixed at some point. The correct command is as follows (note the ending which has -1.0):
appcfg.cmd -A aqueous-flames-561 update target\appengine-try-java-1.0

AMTU (Amazon Transport Utility) crashing and service not running

Having a problem running AMTU on a windows 7 Pro Machine.
It runs fine when it opens but it crashes after running a few days.
Here is the Crash Report.
2013-09-14 09:48:19,482 [pool-3-thread-3] com.amazon.merchants.services.RetrieverService - Unable to retrieve unacknowledged report information - MWS Request ID unknown
2013-09-14 09:48:19,482 [pool-3-thread-3] com.amazon.merchants.services.RetrieverService - MWS responded with an error: Internal Error
com.amazonaws.mws.MarketplaceWebServiceException: Internal Error
at com.amazonaws.mws.MarketplaceWebServiceClient.processErrors(MarketplaceWebServiceClient.java:2342)
at com.amazonaws.mws.MarketplaceWebServiceClient.invoke(MarketplaceWebServiceClient.java:2231)
at com.amazonaws.mws.MarketplaceWebServiceClient.invoke(MarketplaceWebServiceClient.java:2011)
at com.amazonaws.mws.MarketplaceWebServiceClient.getReportList(MarketplaceWebServiceClient.java:1206)
at com.amazon.merchants.services.RetrieverService.processReportCheck(RetrieverService.java:94)
at com.amazon.merchants.services.RetrieverService.run(RetrieverService.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
I also cannot start the Windows Service called AMTU. Get the following Error:
The AMTU service on local computer has started and then stopped
I am suspecting its a Java version issue.
In the AMTU documentation it says "requires Java version 1.6.0 or later (listed as JDK/JRE - 6)" and links to http://www.oracle.com/technetwork/java/archive-139210.html. The link has many download links, but nothing listed "JDK/JRE - 6".
AMTU documentation: https://d28hcfptedr5ia.cloudfront.net/ug/AMTU_2.2_UserGuide.pdf
Any Ideas?
Thanks in advance.

The way I read this crash report, AMTU got an unexpected result from the MWS servers:
MWS responded with an error: Internal Error
It seems the error handling in AMTU is not good enough to gracefully handle a HTTP status 500, and there is not a lot you can do about this. You could put a HTTP proxy in between and catch a HTTP 500 on the line before it gets to the AMTU, replacing it with something that AMTU handles more gracefully (e.g. an empty XML result or a time out). It would be preferrable though that Amazon doesn't send those errors back, after all, a 500 is an error on their side of things.
I seriously doubt the Java version has anything to do with this, but just in case: You can still download JRE6 even though it is end-of-life:
Java 6 downloads
Please note that the true name of JRE6 is "Java SE runtime environment" and JDK6 is called "Java SE development kit". At the time of writing, the most current version is "update 45". You may need to uninstall Java 7 to make sure the AMTU actually uses the version you want it to. Please also note that since AMTU is a 32bit process, you will need the 32bit JRE even if it is run on a 64bit windows.

Java applet fails to reload on Internet Explorer

I have an applet that has a logout"button. The button ends the session by calling a CGI script and then kills Java VM by calling System.exit(). The problem is when a user tries to log in again in the same browser window - the applet fails to load with ClassNotFoundException:
load: class lucent/fm/parts/BlankPage.class not found.
java.lang.ClassNotFoundException: lucent.fm.parts.BlankPage.class
at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: open HTTP connection failed:http://example.com/html/lucent/fm/parts/BlankPage/class.class
at sun.plugin2.applet.Applet2ClassLoader.getBytes(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader.access$000(Unknown Source)
at sun.plugin2.applet.Applet2ClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
... 7 more
Exception: java.lang.ClassNotFoundException: lucent.fm.parts.BlankPage.class
It appears only on Internet Explorer, not in Firefox. Java Plugin is:
Java Plug-in 1.6.0_20
Using JRE version 1.6.0_20-b02 Java HotSpot(TM) Client VM
The direct scenario is the following:
1. Log in to the system (load the applet).
2. Log out (it closes the applet, but the browser window persists).
3. Click on the address bar and press Enter.
4. The applet fails to load and the ClassNotFoundException can be seen in Java Console.
5. Refresh the page - the server redirects to the login page; after logging in, the applet again does not load and throws the exception.
Looking at the Apache access log proved that in the step 4 that the browser (or plugin) tries to load jar files and gets a HTTP error. It is OK because the session has expired. The strange thing happens in the 5th point - there is no request for jars! It seems that the browser or plugin remembers failed attempts and does not even try to load jar files. It only tries to load a raw .class file, which is not present on the server.
Is my conclusion correct? How can I deal with such an error? Is it possible to force Java plugin to load jar files?
I checked that enabling caching in Java Control Panel does not help. Setting the codebase_lookup parameter to "false" is not helpful, too. It only prevents from trying to load the "class" file directly.
Thanks in advance for any suggestions.

I have an applet that has a "logout" button. The button ends the session by calling a CGI script and then kills Java VM by calling System.exit().
An applet calling System.exit(anyNumber) is crudely equivalent to a guest burning down the house of their host. Applets (even trusted applets) should never try to end the VM. The VM will be ended by the browser when all applets in a page that share the VM have finished their destroy() methods and a subsequent period of time as chosen by the browser.
BTW - I recall one version of Mozilla/FF where calling System.exit(int) not just ended the VM, but also crashed the browser!

If your html with applets is not static (cgi, php, etc), then after logging out, you can try to force different URL pointing to the jar file (i.e. instead of "my.jar" use "my.jar?random=1235232").
Also, you can try to play with cache HTTP headers.
Another potential workaround will be to reconfigure apache to serve the jars always - even when session has been closed (if that's acceptable).