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

ASF GitHub Bot commented on TINKERPOP-1352:
-------------------------------------------

Github user ramzioueslati commented on the issue:

    https://github.com/apache/tinkerpop/pull/352
  
    Will do right away.
    
    For the record here is the stacktrace:
    ```
    Running 
org.apache.tinkerpop.gremlin.server.GremlinServerAuthOldIntegrateTest
    [WARN] org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator - Using 
{} configuration option which is deprecated - prefer including the location of 
the credentials graph data in the TinkerGraph config file.
    [WARN] org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator - Using 
{} configuration option which is deprecated - prefer including the location of 
the credentials graph data in the TinkerGraph config file.
    [WARN] org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator - Using 
{} configuration option which is deprecated - prefer including the location of 
the credentials graph data in the TinkerGraph config file.
    [WARN] org.apache.tinkerpop.gremlin.server.AbstractChannelizer - Enabling 
SSL with self-signed certificate (NOT SUITABLE FOR PRODUCTION)
    [WARN] org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator - Using 
{} configuration option which is deprecated - prefer including the location of 
the credentials graph data in the TinkerGraph config file.
    [WARN] org.apache.tinkerpop.gremlin.driver.Cluster - SSL configured without 
a trustCertChainFile and thus trusts all certificates without verification (not 
suitable for production)
    [WARN] org.apache.tinkerpop.gremlin.driver.Cluster - SSL configured without 
a trustCertChainFile and thus trusts all certificates without verification (not 
suitable for production)
    [WARN] org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator - Using 
{} configuration option which is deprecated - prefer including the location of 
the credentials graph data in the TinkerGraph config file.
    [WARN] org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator - Using 
{} configuration option which is deprecated - prefer including the location of 
the credentials graph data in the TinkerGraph config file.
    [ERROR] org.apache.tinkerpop.gremlin.driver.Handler$GremlinResponseHandler 
- Could not process the response
    javax.security.sasl.SaslException: GSS initiate failed [Caused by 
GSSException: No valid credentials provided (Mechanism level: Failed to find 
any Kerberos tgt)]
            at 
com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:211)
            at 
org.apache.tinkerpop.gremlin.driver.Handler$GremlinSaslAuthenticationHandler.evaluateChallenge(Handler.java:123)
            at 
org.apache.tinkerpop.gremlin.driver.Handler$GremlinSaslAuthenticationHandler.channelRead0(Handler.java:93)
            at 
org.apache.tinkerpop.gremlin.driver.Handler$GremlinSaslAuthenticationHandler.channelRead0(Handler.java:66)
            at 
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
            at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:307)
            at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:293)
            at 
io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:103)
            at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:307)
            at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:293)
            at 
org.apache.tinkerpop.gremlin.driver.handler.WebSocketClientHandler.channelRead0(WebSocketClientHandler.java:90)
            at 
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
            at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:307)
            at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:293)
            at 
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:276)
            at 
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:263)
            at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:307)
            at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:293)
            at 
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:840)
            at 
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:131)
            at 
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
            at 
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
            at 
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
            at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
            at 
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
            at java.lang.Thread.run(Thread.java:745)
    Caused by: GSSException: No valid credentials provided (Mechanism level: 
Failed to find any Kerberos tgt)
            at 
sun.security.jgss.krb5.Krb5InitCredential.getInstance(Krb5InitCredential.java:147)
            at 
sun.security.jgss.krb5.Krb5MechFactory.getCredentialElement(Krb5MechFactory.java:122)
            at 
sun.security.jgss.krb5.Krb5MechFactory.getMechanismContext(Krb5MechFactory.java:187)
            at 
sun.security.jgss.GSSManagerImpl.getMechanismContext(GSSManagerImpl.java:224)
            at 
sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:212)
            at 
sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:179)
            at 
com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:192)
            ... 25 more
    [WARN] org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator - Using 
{} configuration option which is deprecated - prefer including the location of 
the credentials graph data in the TinkerGraph config file.
    [WARN] org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator - Using 
{} configuration option which is deprecated - prefer including the location of 
the credentials graph data in the TinkerGraph config file.
    [WARN] org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator - Using 
{} configuration option which is deprecated - prefer including the location of 
the credentials graph data in the TinkerGraph config file.
    [WARN] org.apache.tinkerpop.gremlin.server.AbstractChannelizer - Enabling 
SSL with self-signed certificate (NOT SUITABLE FOR PRODUCTION)
    [WARN] org.apache.tinkerpop.gremlin.server.auth.SimpleAuthenticator - Using 
{} configuration option which is deprecated - prefer including the location of 
the credentials graph data in the TinkerGraph config file.
    Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 62.071 sec 
<<< FAILURE! - in 
org.apache.tinkerpop.gremlin.server.GremlinServerAuthOldIntegrateTest
    
shouldFailAuthenticateWithPlainTextNoCredentials(org.apache.tinkerpop.gremlin.server.GremlinServerAuthOldIntegrateTest)
  Time elapsed: 4.58 sec  <<< FAILURE!
    java.lang.AssertionError:
    Expected: a string starting with "Invalid name provided"
         but: was "No valid credentials provided (Mechanism level: Failed to 
find any Kerberos tgt)"
            at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
            at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8)
            at 
org.apache.tinkerpop.gremlin.server.GremlinServerAuthOldIntegrateTest.shouldFailAuthenticateWithPlainTextNoCredentials(GremlinServerAuthOldIntegrateTest.java:135)
    ```


> Connection Pool doesn't always grow 
> ------------------------------------
>
>                 Key: TINKERPOP-1352
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1352
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: driver
>    Affects Versions: 3.1.2-incubating
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Critical
>             Fix For: 3.1.3, 3.2.1
>
>
> With certain configurations (that aren't terribly intuitive) of the driver, 
> the connection pool won't grow properly - this includes the default 
> configuration. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to