Clover graph failing with Error

villumanati

• June 27, 2013 00:00

• Answered

Follow

I am receiving the following error and have no idea why. Any help is greatly appreciated.

----------------
WARN [main] - SecurityException while DriverManager.deregisterDriver() message:DriverManager: calling class not authorized to deregister JDBC driver
WARN [main] - SecurityException while DriverManager.deregisterDriver() message:DriverManager: calling class not authorized to deregister JDBC driver
WARN [main] - SecurityException while DriverManager.deregisterDriver() message:DriverManager: calling class not authorized to deregister JDBC driver
WARN [main] - SecurityException while DriverManager.deregisterDriver() message:DriverManager: calling class not authorized to deregister JDBC driver
ERROR [main] - Execution of graph failed !
-------------

• 

  admin

  • June 28, 2013 11:40

  0

  Comment actions Permalink

  Hi villumanati,
  
  It seems to me that you are trying to run CloverETL Engine with Apache Harmony. Right? I am afraid that for Engine is required (http://doc.cloveretl.com/documentation/ ... igner.html) Oracle Java 6+. We know that some users use OpenJDK but suffers at least by performance issues. I have never heard of user using Apache Harmony.
  
  You may try to find root cause of problem with Apache Harmony (Engine is available as source codes) and prepare patch. Then I can ask developers to accept it into mainstream repository.
• 

  villumanati

  • June 28, 2013 12:50

  0

  Comment actions Permalink

  I am running CloverETL that is distributed with the IBM Initiate Master Data service product. How do I determine if I am they use Harmony or the default JDK?
  
  Also I had a copy of this graph v9(my graph name) that has a dbjoin component with a query in it. I did a save as and renamed it to (v11). I changed the dbjoin sql in v11 to better accomadate my needs.
  
  The graph runs PERFECT in my v9 graph. It only has an issue with v11. At first i thought it was the sql but both queries execute fine by themselves on sql server.
  
  Is it possible that v9 registered the driver to the database and hence this is the reason that v11 can't use the same connection properties or deregister the jdbc driver?
  
  I have been doing a little dig and this is my hypothesis but i don't know how to fix it. Please advise.
  
  
  http://www.tutorialspoint.com/jdbc/jdbc ... ctions.htm
  http://docs.oracle.com/javase/6/docs/ap ... nager.html
• 

  imriskal

  • July 01, 2013 13:57

  0

  Comment actions Permalink

  Hi, villumanati,
  
  Please, contact your IBM support. IBM does this bundle with CloverETL by itself so their support department will definitely have deeper knowledge of their product than us. Thank you for your understanding.
  
  Best regards,

Please sign in to leave a comment.