[ 
https://issues.apache.org/jira/browse/DRILL-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16058393#comment-16058393
 ] 

N Campbell edited comment on DRILL-5256 at 6/22/17 1:39 PM:
------------------------------------------------------------

Is anyone looking at this issue?

Drill 1.10. 1.9 or latest MAPR JDBC drivers hit similar error

SQL Squirrel executed using  current (1.8 SR4 FP6) and prior IBM JRE 1.8 builds 
(i.e. SR3 FP22 and SR3 FP10 and SR2). 

But runs with ORACLE JRE.

*Apache driver*
Caused by: java.lang.ExceptionInInitializerError
        at java.lang.J9VMInternals.ensureError(J9VMInternals.java:141)
        at 
java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:130)
        at 
oadd.org.apache.drill.exec.memory.BaseAllocator.<clinit>(BaseAllocator.java:44)
        at 
oadd.org.apache.drill.exec.memory.RootAllocatorFactory.newRoot(RootAllocatorFactory.java:38)
        at 
org.apache.drill.jdbc.impl.DrillConnectionImpl.<init>(DrillConnectionImpl.java:145)
        at 
org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:70)
        at 
org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:69)
        at 
oadd.org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:143)
        at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
        at 
net.sourceforge.squirrel_sql.fw.sql.SQLDriverManager.getConnection(SQLDriverManager.java:133)
        at 
net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.executeConnect(OpenConnectionCommand.java:167)

*MAPR driver*

Caused by: java.lang.NoClassDefFoundError: 
org.apache.drill.exec.memory.RootAllocator (initialization failure)
        at 
java.lang.J9VMInternals.initializationAlreadyFailed(J9VMInternals.java:91)
        at 
org.apache.drill.exec.memory.RootAllocatorFactory.newRoot(RootAllocatorFactory.java:38)
        at com.mapr.drill.client.DRJDBCClient.openSession(Unknown Source)
        at com.mapr.drill.client.DRJDBCClient.<init>(Unknown Source)
        at com.mapr.drill.core.DRJDBCConnection.connect(Unknown Source)
        at com.mapr.jdbc.common.BaseConnectionFactory.doConnect(Unknown Source)
        at com.mapr.jdbc.common.AbstractDriver.connect(Unknown Source)
        at 
net.sourceforge.squirrel_sql.fw.sql.SQLDriverManager.getConnection(SQLDriverManager.java:133)




was (Author: the6campbells):
Is anyone looking at this issue?

Drill 1.10. 1.9 or latest MAPR JDBC drivers hit similar error

SQL Squirrel executed using  current (1.8 SR4 FP6) and prior IBM JRE 1.8 builds 
(i.e. SR3 FP22 and SR3 FP10 and SR2). 

But runs with ORACLE JRE.

Caused by: java.lang.NullPointerException
        at 
oadd.io.netty.buffer.PooledByteBufAllocatorL$InnerAllocator.<init>(PooledByteBufAllocatorL.java:93)
        at 
oadd.io.netty.buffer.PooledByteBufAllocatorL.<init>(PooledByteBufAllocatorL.java:56)
        at 
oadd.org.apache.drill.exec.memory.AllocationManager.<clinit>(AllocationManager.java:60)
        ... 16 more


> Exception in thread "main" java.lang.ExceptionInInitializerError
> ----------------------------------------------------------------
>
>                 Key: DRILL-5256
>                 URL: https://issues.apache.org/jira/browse/DRILL-5256
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>    Affects Versions: 1.7.0, 1.8.0
>         Environment: Windows 7, IBM SDK 1.6 and IBM SDK 1.7
>            Reporter: Vasu
>              Labels: jvm
>
> Below error while connecting to Drill Server 
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.J9VMInternals.initialize(J9VMInternals.java:257)
> at 
> oadd.org.apache.drill.exec.memory.BaseAllocator.<clinit>(BaseAllocator.java:44)
> at java.lang.J9VMInternals.initializeImpl(Native Method)
> at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
> at java.lang.J9VMInternals.initialize(J9VMInternals.java:202)
> at 
> oadd.org.apache.drill.exec.memory.RootAllocatorFactory.newRoot(RootAllocatorFactory.java:38)
> at 
> org.apache.drill.jdbc.impl.DrillConnectionImpl.<init>(DrillConnectionImpl.java:143)
> at 
> org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:64)
> at org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:69)
> at 
> oadd.net.hydromatic.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:126)
> at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
> at java.sql.DriverManager.getConnection(DriverManager.java:583)
> at java.sql.DriverManager.getConnection(DriverManager.java:245)
> at com.trianz.drill.ApacheDrillDemo.main(ApacheDrillDemo.java:13)
> Caused by: java.lang.NullPointerException
> at 
> oadd.io.netty.buffer.PooledByteBufAllocatorL$InnerAllocator.<init>(PooledByteBufAllocatorL.java:93)
> at 
> oadd.io.netty.buffer.PooledByteBufAllocatorL.<init>(PooledByteBufAllocatorL.java:56)
> at 
> oadd.org.apache.drill.exec.memory.AllocationManager.<clinit>(AllocationManager.java:60)
> at java.lang.J9VMInternals.initializeImpl(Native Method)
> at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
> ... 13 more
> When I tried to debug in to source code, following is the place where we are 
> getting NULL POINTER EXCEPTION
>  
> drill/exec/memory/base/src/main/java/io/netty/buffer/PooledByteBufAllocatorL.java
>  
> Line: 93: this.chunkSize = directArenas[0].chunkSize;
> Below is the code snapshot.
>  public InnerAllocator() {
>       super(true);
>       try {
>         Field f = 
> PooledByteBufAllocator.class.getDeclaredField("directArenas");
>         f.setAccessible(true);
>         this.directArenas = (PoolArena<ByteBuffer>[]) f.get(this);
>       } catch (Exception e) {
>         throw new RuntimeException("Failure while initializing allocator.  
> Unable to retrieve direct arenas field.", e);
>       }
>       this.chunkSize = directArenas[0].chunkSize;
> if (memoryLogger.isTraceEnabled()) {
> Can anyone please help on this? Thanks in advance.
> Thanks,
> Vasu T



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to