NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 1101 - Error message appears: Warning: Could not get charToByteConverterClass!
Error message appears: Warning: Could not get charToByteConverterClass!
Status: NEEDSINFO
Product: Fiji
Classification: Unclassified
Component: Plugins
unspecified
PC Windows
: P4 normal
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2015-06-29 08:40 CDT by Monika Pawlowska
Modified: 2015-06-30 10:49 CDT
3 users (show)

See Also:

Description Monika Pawlowska 2015-06-29 08:40:29 CDT
The following warning appears at differen times, for example directly after completing acquisition of a stack.

Information about your version of Java:

  os.arch => amd64
  os.name => Windows 7
  os.version => 6.1
  java.version => 1.8.0_45
  java.vendor => Oracle Corporation
  java.runtime.name => Java(TM) SE Runtime Environment
  java.runtime.version => 1.8.0_45-b14
  java.vm.name => Java HotSpot(TM) 64-Bit Server VM
  java.vm.version => 25.45-b02
  java.vm.vendor => Oracle Corporation
  java.vm.info => mixed mode
  java.awt.graphicsenv => sun.awt.Win32GraphicsEnvironment
  java.specification.name => Java Platform API Specification
  java.specification.version => 1.8
  sun.cpu.endian => little
  sun.desktop => windows
  file.separator => \

The up-to-date check says: REMIND_LATER

Information relevant to JAVA_HOME related problems:

  JAVA_HOME is set to: C:\Program Files\Java\jdk1.8.0_45/jre
  imagej.dir => C:\OPENSP~1\OpenSPIM.app

Information about the version of each plugin:

Activated update sites:
ImageJ: http://update.imagej.net/ (last check:20150624045330)
Fiji: http://fiji.sc/update/ (last check:20150625112927)
OpenSPIM: http://openspim.org/update/ (last check:20150512160259)
Micro-Manager-dev: http://sites.imagej.net/Micro-Manager-dev/ (last check:20150629082658)

Files not up-to-date:
  87de8fb9 (OBSOLETE_MODIFIED) 20150624110837 mm/win32/OlympusIX3Control/OlympusIX3Control.old.exe
  33e7bef9 (OBSOLETE_MODIFIED) 20150624110838 mm/win64/OlympusIX3Control/OlympusIX3Control.old.exe
  3cea8b06 (MODIFIED) 20141223094152 mm/win64/PiUsb.dll
Comment 1 Monika Pawlowska 2015-06-29 08:41:23 CDT
(by "appears" I mean in the java console window)
Comment 2 Curtis Rueden 2015-06-29 14:21:47 CDT
Could you please copy and paste the entire error message, including any stack trace?

See also:
http://imagej.net/Bug_reporting_best_practices

Thanks!
Comment 3 Monika Pawlowska 2015-06-30 04:14:07 CDT
(In reply to Curtis Rueden from comment #2)
> Could you please copy and paste the entire error message, including any
> stack trace?
> 
> See also:
> http://imagej.net/Bug_reporting_best_practices
> 
> Thanks!

Hi,
the entire error message I see in the console is: "Warning: Could not get charToByteConverterClass!", in red. Sometimes it already pops up when fiji is started, before I do anything. Is there a more detailed log file somewhere? I was looking for it, but I couldn't find any.
Comment 4 Mark Hiner 2015-06-30 10:36:24 CDT
Looks like something is using deprecated pre-java 7 API. See: http://stackoverflow.com/questions/10444129/java-class-chartobyteconverter-type-deprecated

I believe this class has been removed in Java 8, which is why it can't be found.

As a short-term workaround you can try launching with Java 7: http://imagej.net/FAQ#On_Windows

The long-term resolution is to identify the location(s) where this class is referenced and update them to use java.nio.charset, to be Java 8-compatible.
Comment 5 Curtis Rueden 2015-06-30 10:49:52 CDT
From a web search (https://www.google.com/search?q=Warning%3A+Could+not+get+charToByteConverterClass&oq=Warning%3A+Could+not+get+charToByteConverterClass&aqs=chrome..69i57j69i58j69i61l2.709j0j7&sourceid=chrome&es_sm=91&ie=UTF-8#q=%22Warning:+Could+not+get+charToByteConverterClass%22) it appears related to construction or parsing of XML using standard Java APIs.

Could you post a specific workflow that reliably produces the message? Is this an OpenSPIM-specific problem? I.e.: do you see this error in a "regular" Fiji installation without the OpenSPIM or Micro-Manager update sites enabled?