Bug 1195150 - Java 8 error message during DV installation and starting
Summary: Java 8 error message during DV installation and starting
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Compatibility
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: David Le Sage
QA Contact:
URL:
Whiteboard:
Depends On: 1194705
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-23 09:23 UTC by Jan Stastny
Modified: 2015-03-23 14:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
When you run Red Hat JBoss Data Virtualization on RHEL with JDK 1.8, an error message is recorded in the log for each VDB that is deployed. The message states that JDK 1.8 javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found. This bug does not impact on the deployment of the VDBs. The error message can safely be ignored.
Clone Of:
Environment:
Last Closed: 2015-03-16 01:00:07 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3991 0 Major Resolved JDK 1.8 javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found 2017-09-29 05:46:26 UTC

Description Jan Stastny 2015-02-23 09:23:12 UTC 
Description of problem:
When DV 6.1.0 is installed or started on a machine with Java 8 an error message appears in console log:

ERROR [stderr] (MSC service thread 1-5) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found

It seems that it does not have an influence on the functionality of the product.

How reproducible:
Each start


Actual results:
Error message which seems to have no influence on the functionality of the product.

Expected results:
No error message in console

Additional info:
Note You need to log in before you can comment on or make changes to this bug.