[JBoss JIRA] (TEIID-5266) Docker Issue
by Arvind Gopinath (JIRA)
[ https://issues.jboss.org/browse/TEIID-5266?page=com.atlassian.jira.plugin... ]
Arvind Gopinath commented on TEIID-5266:
----------------------------------------
[~rareddy] All good now.
I added "_Djava.net.preferIPv4Stack=true" and it works without any issue.
CMD ["java", "-Djava.net.preferIPv4Stack=true", "-jar", "tpl-teiid-docker-1.0.0-swarm.jar", "-S", "local"]
> Docker Issue
> -------------
>
> Key: TEIID-5266
> URL: https://issues.jboss.org/browse/TEIID-5266
> Project: Teiid
> Issue Type: Bug
> Reporter: Arvind Gopinath
> Assignee: Steven Hawkins
> Priority: Minor
> Attachments: Dockerfile, VDB-Teiid-RDBMS-ErrorLogs-Docker.txt
>
>
> For the below example - when I create the docker file (attached for reference) and run through docker, I am getting below error message -
> https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/rdbms-a...
> docker run -p 31000:31000 -p 8080:8080 teiid/vdb-rdbms-swarm:1.0
> Error logs (attached)
> 2018-02-27 11:30:33,947 ERROR [stderr] (main) java.lang.RuntimeException: org.jboss.msc.service.StartException in service jboss.teiid.transport.jdbc: Failed to start serv
> ice
> 2018-02-27 11:30:33,949 ERROR [stderr] (main) at org.wildfly.swarm.spi.api.ClassLoading.withTCCL(ClassLoading.java:45)
> 2018-02-27 11:30:33,949 ERROR [stderr] (main) at org.wildfly.swarm.container.runtime.ServerBootstrapImpl.bootstrap(ServerBootstrapImpl.java:113)
> 2018-02-27 11:30:33,950 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.start(Swarm.java:398)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5266) Docker Issue
by Arvind Gopinath (JIRA)
[ https://issues.jboss.org/browse/TEIID-5266?page=com.atlassian.jira.plugin... ]
Arvind Gopinath resolved TEIID-5266.
------------------------------------
Resolution: Done
> Docker Issue
> -------------
>
> Key: TEIID-5266
> URL: https://issues.jboss.org/browse/TEIID-5266
> Project: Teiid
> Issue Type: Bug
> Reporter: Arvind Gopinath
> Assignee: Steven Hawkins
> Priority: Minor
> Attachments: Dockerfile, VDB-Teiid-RDBMS-ErrorLogs-Docker.txt
>
>
> For the below example - when I create the docker file (attached for reference) and run through docker, I am getting below error message -
> https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/rdbms-a...
> docker run -p 31000:31000 -p 8080:8080 teiid/vdb-rdbms-swarm:1.0
> Error logs (attached)
> 2018-02-27 11:30:33,947 ERROR [stderr] (main) java.lang.RuntimeException: org.jboss.msc.service.StartException in service jboss.teiid.transport.jdbc: Failed to start serv
> ice
> 2018-02-27 11:30:33,949 ERROR [stderr] (main) at org.wildfly.swarm.spi.api.ClassLoading.withTCCL(ClassLoading.java:45)
> 2018-02-27 11:30:33,949 ERROR [stderr] (main) at org.wildfly.swarm.container.runtime.ServerBootstrapImpl.bootstrap(ServerBootstrapImpl.java:113)
> 2018-02-27 11:30:33,950 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.start(Swarm.java:398)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5266) Docker Issue
by Arvind Gopinath (JIRA)
[ https://issues.jboss.org/browse/TEIID-5266?page=com.atlassian.jira.plugin... ]
Arvind Gopinath closed TEIID-5266.
----------------------------------
> Docker Issue
> -------------
>
> Key: TEIID-5266
> URL: https://issues.jboss.org/browse/TEIID-5266
> Project: Teiid
> Issue Type: Bug
> Reporter: Arvind Gopinath
> Assignee: Steven Hawkins
> Priority: Minor
> Attachments: Dockerfile, VDB-Teiid-RDBMS-ErrorLogs-Docker.txt
>
>
> For the below example - when I create the docker file (attached for reference) and run through docker, I am getting below error message -
> https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/rdbms-a...
> docker run -p 31000:31000 -p 8080:8080 teiid/vdb-rdbms-swarm:1.0
> Error logs (attached)
> 2018-02-27 11:30:33,947 ERROR [stderr] (main) java.lang.RuntimeException: org.jboss.msc.service.StartException in service jboss.teiid.transport.jdbc: Failed to start serv
> ice
> 2018-02-27 11:30:33,949 ERROR [stderr] (main) at org.wildfly.swarm.spi.api.ClassLoading.withTCCL(ClassLoading.java:45)
> 2018-02-27 11:30:33,949 ERROR [stderr] (main) at org.wildfly.swarm.container.runtime.ServerBootstrapImpl.bootstrap(ServerBootstrapImpl.java:113)
> 2018-02-27 11:30:33,950 ERROR [stderr] (main) at org.wildfly.swarm.Swarm.start(Swarm.java:398)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5268) Anonymous bind login doesn't work for ldap connector
by Yuming Zhu (JIRA)
[ https://issues.jboss.org/browse/TEIID-5268?page=com.atlassian.jira.plugin... ]
Yuming Zhu updated TEIID-5268:
------------------------------
Summary: Anonymous bind login doesn't work for ldap connector (was: Anonymous bind login doesn't work)
> Anonymous bind login doesn't work for ldap connector
> ----------------------------------------------------
>
> Key: TEIID-5268
> URL: https://issues.jboss.org/browse/TEIID-5268
> Project: Teiid
> Issue Type: Bug
> Components: LDAP Connector
> Affects Versions: 8.8, 8.12.5
> Reporter: Yuming Zhu
> Assignee: Steven Hawkins
>
> I configured an anonymous to connect to LDAP server via ldaps://... according to https://docs.jboss.org/author/display/teiid812final/LDAP+Data+Sources
> like:
> {code:xml}
> <resource-adapter id="ldap">
> <module slot="main" id="org.jboss.teiid.resource-adapter.ldap"/>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory" jndi-name="java:/ldapDS" enabled="true" use-java-context="true" pool-name="ldapDS">
> <config-property name="LdapUrl">
> ldaps://ldap.corp.redhat.com:636
> </config-property>
> <config-property name="LdapAdminUserDN">
> </config-property>
> <config-property name="LdapAdminUserPassword">
> </config-property>
> <config-property name="LdapTxnTimeoutInMillis">
> -1
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
> {code}
> when I test the connection by jboss-cli, error occurs:
> command:
> {code}
> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=ldap/connection-definitions=ldapDS:test-connection-in-pool
> {code}
> error:
> {code}
> 13:02:17,263 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) ldapDS running as FIFO
> 13:02:17,263 DEBUG [org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover] (management-handler-thread - 3) Register pool: SemaphoreArrayListManagedConnectionPool@13f30b23[pool=ldapDS] (interval=1800000)
> 13:02:17,264 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) ldapDS: getConnection(null, null) [0/20]
> 13:02:17,802 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Initializing LDAP directory context failed. Please check LDAP connection properties, including username and password: [LDAP: error code 49 - Invalid Credentials]
> at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.initializeLDAPContext(LDAPConnectionImpl.java:151)
> at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.<init>(LDAPConnectionImpl.java:75)
> at org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory$1.getConnection(LDAPManagedConnectionFactory.java:49)
> at org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory$1.getConnection(LDAPManagedConnectionFactory.java:43)
> at org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:71)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:858) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:413) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:725) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.strategy.OnePool.testConnection(OnePool.java:89) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
> at org.jboss.as.connector.subsystems.common.pool.PoolOperations$TestConnectionInPool.invokeCommandOn(PoolOperations.java:143) [jboss-as-connector-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:82) [jboss-as-connector-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:702) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:537) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1144) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:331) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:201) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:135) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_112]
> at javax.security.auth.Subject.doAs(Subject.java:422) [rt.jar:1.8.0_112]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298)
> at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:537)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_112]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_112]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_112]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
> Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
> at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3136) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3082) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2883) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2797) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) [rt.jar:1.8.0_112]
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) [rt.jar:1.8.0_112]
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:122) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:107) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) [rt.jar:1.8.0_112]
> at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:98) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.8.0_112]
> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) [rt.jar:1.8.0_112]
> at javax.naming.InitialContext.init(InitialContext.java:244) [rt.jar:1.8.0_112]
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) [rt.jar:1.8.0_112]
> at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.initializeLDAPContext(LDAPConnectionImpl.java:148)
> ... 31 more
> 13:02:17,808 DEBUG [org.jboss.as.controller.management-operation] (management-handler-thread - 3) JBAS014616: Operation ("test-connection-in-pool") failed - address: ([
> ("subsystem" => "resource-adapters"),
> ("resource-adapter" => "ldap"),
> ("connection-definitions" => "ldapDS")
> ]) - failure description: "JBAS010440: failed to invoke operation: JBAS010447: Connection is not valid"
> {code}
> It looks username isn't set as expected
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5268) Anonymous bind login doesn't work
by Yuming Zhu (JIRA)
Yuming Zhu created TEIID-5268:
---------------------------------
Summary: Anonymous bind login doesn't work
Key: TEIID-5268
URL: https://issues.jboss.org/browse/TEIID-5268
Project: Teiid
Issue Type: Bug
Components: LDAP Connector
Affects Versions: 8.12.5, 8.8
Reporter: Yuming Zhu
Assignee: Steven Hawkins
I configured an anonymous to connect to LDAP server via ldaps://... according to https://docs.jboss.org/author/display/teiid812final/LDAP+Data+Sources
like:
{code:xml}
<resource-adapter id="ldap">
<module slot="main" id="org.jboss.teiid.resource-adapter.ldap"/>
<connection-definitions>
<connection-definition class-name="org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory" jndi-name="java:/ldapDS" enabled="true" use-java-context="true" pool-name="ldapDS">
<config-property name="LdapUrl">
ldaps://ldap.corp.redhat.com:636
</config-property>
<config-property name="LdapAdminUserDN">
</config-property>
<config-property name="LdapAdminUserPassword">
</config-property>
<config-property name="LdapTxnTimeoutInMillis">
-1
</config-property>
</connection-definition>
</connection-definitions>
</resource-adapter>
{code}
when I test the connection by jboss-cli, error occurs:
command:
{code}
[standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=ldap/connection-definitions=ldapDS:test-connection-in-pool
{code}
error:
{code}
13:02:17,263 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) ldapDS running as FIFO
13:02:17,263 DEBUG [org.jboss.jca.core.connectionmanager.pool.idle.IdleRemover] (management-handler-thread - 3) Register pool: SemaphoreArrayListManagedConnectionPool@13f30b23[pool=ldapDS] (interval=1800000)
13:02:17,264 DEBUG [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) ldapDS: getConnection(null, null) [0/20]
13:02:17,802 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Initializing LDAP directory context failed. Please check LDAP connection properties, including username and password: [LDAP: error code 49 - Invalid Credentials]
at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.initializeLDAPContext(LDAPConnectionImpl.java:151)
at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.<init>(LDAPConnectionImpl.java:75)
at org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory$1.getConnection(LDAPManagedConnectionFactory.java:49)
at org.teiid.resource.adapter.ldap.LDAPManagedConnectionFactory$1.getConnection(LDAPManagedConnectionFactory.java:43)
at org.teiid.resource.spi.BasicManagedConnectionFactory.createManagedConnection(BasicManagedConnectionFactory.java:71)
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:858) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:413) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:725) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
at org.jboss.jca.core.connectionmanager.pool.strategy.OnePool.testConnection(OnePool.java:89) [ironjacamar-core-impl-1.0.37.Final-redhat-1.jar:1.0.37.Final-redhat-1]
at org.jboss.as.connector.subsystems.common.pool.PoolOperations$TestConnectionInPool.invokeCommandOn(PoolOperations.java:143) [jboss-as-connector-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:82) [jboss-as-connector-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:702) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:537) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:338) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:314) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1144) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:331) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:201) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:135) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.8.0_112]
at javax.security.auth.Subject.doAs(Subject.java:422) [rt.jar:1.8.0_112]
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) [jboss-as-controller-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:298)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:537)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_112]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_112]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_112]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.2.Final-redhat-1.jar:2.1.2.Final-redhat-1]
Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3136) [rt.jar:1.8.0_112]
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3082) [rt.jar:1.8.0_112]
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2883) [rt.jar:1.8.0_112]
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2797) [rt.jar:1.8.0_112]
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) [rt.jar:1.8.0_112]
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) [rt.jar:1.8.0_112]
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) [rt.jar:1.8.0_112]
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) [rt.jar:1.8.0_112]
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) [rt.jar:1.8.0_112]
at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:122) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.naming.InitialContext.init(InitialContext.java:107) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) [rt.jar:1.8.0_112]
at org.jboss.as.naming.InitialContext.<init>(InitialContext.java:98) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:44) [jboss-as-naming-7.5.9.Final-redhat-2.jar:7.5.9.Final-redhat-2]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) [rt.jar:1.8.0_112]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) [rt.jar:1.8.0_112]
at javax.naming.InitialContext.init(InitialContext.java:244) [rt.jar:1.8.0_112]
at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) [rt.jar:1.8.0_112]
at org.teiid.resource.adapter.ldap.LDAPConnectionImpl.initializeLDAPContext(LDAPConnectionImpl.java:148)
... 31 more
13:02:17,808 DEBUG [org.jboss.as.controller.management-operation] (management-handler-thread - 3) JBAS014616: Operation ("test-connection-in-pool") failed - address: ([
("subsystem" => "resource-adapters"),
("resource-adapter" => "ldap"),
("connection-definitions" => "ldapDS")
]) - failure description: "JBAS010440: failed to invoke operation: JBAS010447: Connection is not valid"
{code}
It looks username isn't set as expected
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5248) Upgrade to v4 api for google spreadsheets
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5248?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5248.
-----------------------------------
Resolution: Done
Added the v4 gdata connectivity, but in a hybrid design. Even if you select to use v4, v3 is still required for update/delete. The resource adapter properties were also updated to remove the legacy AuthMethod, and to use SpreadsheetId rather than the Key property.
> Upgrade to v4 api for google spreadsheets
> -----------------------------------------
>
> Key: TEIID-5248
> URL: https://issues.jboss.org/browse/TEIID-5248
> Project: Teiid
> Issue Type: Quality Risk
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.2
>
>
> Our integration is based upon the v3 api, which will soon be deprecated. This will be a large change given the api differences. We can also look to include TEIID-5040
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5267) Foreign misspelled in several places
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5267:
-------------------------------------
Summary: Foreign misspelled in several places
Key: TEIID-5267
URL: https://issues.jboss.org/browse/TEIID-5267
Project: Teiid
Issue Type: Quality Risk
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.2
In several places, including public api methods, foreign is misspelled. This should be corrected with appropriate deprecations added.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-5265) AssertionError: Batch not found in storage
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5265?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5265:
---------------------------------------
I am not yet able to reproduce this to where it would cause an issue with batch retrieval. I have added a commit to account for some potential issues and to clean up logging. If possible can you test with master to see if this addresses your scenario or if we can get a better root exception?
> AssertionError: Batch not found in storage
> ------------------------------------------
>
> Key: TEIID-5265
> URL: https://issues.jboss.org/browse/TEIID-5265
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 10.1
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
>
> While executing the following query:
> {code:sql}
> insert into rep149_cci(PatientID,age,Orig,Upd,agepointsO,agepointsU,AMI,CHF,PVD,CVD,DEM,CPD,PUD,MLD,SLD,DNC,DWC,HEM,RED,MAL,MST,HIV)
> select cci.patientid as patientid,cci.age as age,cci.orig as orig,cci.upd as upd,cci.agepointso as agepointso,cci.agepointsu as agepointsu,
> cci.charlson_ami as ami,cci.charlson_chf as chf,cci.charlson_pvd as pvd,cci.charlson_cvd as cvd,cci.charlson_dem as dem,cci.charlson_cpd as cpd,cci.charlson_pud as pud,
> cci.charlson_mld as mld,cci.charlson_sld as sld,cci.charlson_dnc as dnc,cci.charlson_dwc as dwc,cci.charlson_hem as hem,cci.charlson_red as red,cci.charlson_mal as mal,
> cci.charlson_mst as mst,cci.charlson_hiv as hiv
> from rep149_cohort gd
> join izisviews.pr_calculate_cci cci on
> cci.patientid_in = gd.patientid;
> {code}
> rep149_cci is defined as
> {code:sql}
> create foreign temporary table rep149_cci(
> PatientID integer not null,
> age bigdecimal,
> Orig long,
> Upd long,
> agepointsO integer,
> agepointsU integer,
> AMI integer,
> CHF integer,
> PVD integer,
> CVD integer,
> DEM integer,
> CPD integer,
> PUD integer,
> MLD integer,
> SLD integer,
> DNC integer,
> DWC integer,
> HEM integer,
> RED integer,
> MAL integer,
> MST integer,
> HIV integer,
> primary key(patientid)
> )OPTIONS (UPDATABLE true) on tmptables;
> {code}
> pr_calculate_cci is a virtual procedure. (I can't however share this code for confidentiality reasons).
> {code:sql}
> CREATE VIRTUAL PROCEDURE pr_calculate_cci(patientid_in integer)
> RETURNS (
> PatientID integer,
> age bigdecimal,
> Orig long,
> Upd long,
> agepointsO integer,
> agepointsU integer,
> AMI integer,
> CHF integer,
> PherVascDis integer,
> CerebVascDis integer,
> Dement integer,
> ChrPulmDis integer,
> PeptUlcer integer,
> MildLivDis integer,
> SevLivDis integer,
> DiabetesNoCompl integer,
> DiabetesWithCompl integer,
> HemiPara integer,
> RenalDis integer,
> Malign integer,
> Metastase integer,
> HIV_AIDS integer
> )
> AS
> BEGIN
> ...
> END
> {code}
> There are a few error reports like this one:
> 2018-02-23 08:33:05,478 ERROR [org.teiid.BUFFER_MGR] (Worker291_QueryProcessorQueue571476) mh0bsTIbs7qY TEIID30001 Max block number exceeded by object 1,366,497 from group 5,068,016. It is a Batch of 1797 rows of [Ljava.lang.String;@10953478. The estimated size was 172,528, but the actual size was 14,410. Increase the maxStorageObjectSize to support larger storage objects. Alternatively you could make the processor batch size smaller.
> The final stack trace is:
> 2018-02-23 08:33:05,539 ERROR [org.teiid.PROCESSOR] (Worker291_QueryProcessorQueue571476) mh0bsTIbs7qY TEIID30019 Unexpected exception for request mh0bsTIbs7qY.90: java.lang.AssertionError: Batch not found in storage 5067771
> at org.teiid.common.buffer.impl.BufferManagerImpl$BatchManagerImpl.getBatch(BufferManagerImpl.java:382)
> at org.teiid.common.buffer.SPage.getValues(SPage.java:234)
> at org.teiid.common.buffer.SPage.search(SPage.java:135)
> at org.teiid.common.buffer.STree.find(STree.java:247)
> at org.teiid.common.buffer.STree.insert(STree.java:295)
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.saveValues(WindowFunctionProjectNode.java:419)
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.buildResults(WindowFunctionProjectNode.java:380)
> at org.teiid.query.processor.relational.WindowFunctionProjectNode.nextBatchDirect(WindowFunctionProjectNode.java:229)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirectInternal(UnionAllNode.java:165)
> at org.teiid.query.processor.relational.UnionAllNode.nextBatchDirect(UnionAllNode.java:138)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.SelectNode.nextBatchDirect(SelectNode.java:100)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160)
> at org.teiid.query.processor.relational.SourceState.prefetch(SourceState.java:207)
> at org.teiid.query.processor.relational.SourceState.rowCountLE(SourceState.java:154)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (TEIID-4652) SybaseIQ translator: DAYOFYEAR function not pushed correctly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-4652?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-4652:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1549210
Bugzilla Update: Perform
> SybaseIQ translator: DAYOFYEAR function not pushed correctly
> ------------------------------------------------------------
>
> Key: TEIID-4652
> URL: https://issues.jboss.org/browse/TEIID-4652
> Project: Teiid
> Issue Type: Sub-task
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Fix For: 9.3, 9.2.1
>
>
> DAYOFYEAR function is being pushed into SAP IQ datasource causing an error. The function doesn't seem to be supported directly in SAP IQ according to [SAP IQ docs|http://help.sap.com/saphelp_iq1611_iqrefbb/helpdata/en/a5/2b07be84f2...]
> Query used:
> {code:sql}
> SELECT IntKey, datevalue, DAYOFYEAR(datevalue) AS DayFromDate FROM BQT1.SmallA ORDER BY IntKey
> {code}
> Source query pushed:
> {code:sql}
> [SELECT g_0."intkey" AS c_0, g_0."datevalue" AS c_1, {fn dayofyear(g_0."datevalue")} AS c_2 FROM "bqt-server"."dvqe"."SmallA" AS g_0 ORDER BY c_0]
> {code}
> Causing an error coming from SAP IQ:
> {code}
> 09:08:30,130 WARN [org.teiid.CONNECTOR] (Worker11_QueryProcessorQueue58) Connector worker process failed for atomic-request=PYp5BTTPF3pK.20.0.12: org.teiid.translator.jdbc.JDBCExecutionException: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."intkey" AS c_0, g_0."datevalue" AS c_1, {fn dayofyear(g_0."datevalue")} AS c_2 FROM "bqt-server"."dvqe"."SmallA" AS g_0 ORDER BY c_0]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:131) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:366)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_71]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_71]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_71]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_71]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211)
> at com.sun.proxy.$Proxy80.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_71]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_71]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_71]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_71]
> Caused by: java.sql.SQLException: JZ0SI: A static function escape dayofyear was used which is not supported by this server.
> at com.sybase.jdbc4.jdbc.ErrorMessage.raiseError(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybStatement.processEscapes(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybStatement.doEscapeProcessing(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybPreparedStatement.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.a(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(Unknown Source)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:744)
> at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:730)
> at org.jboss.jca.adapters.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:405)
> at org.teiid.translator.jdbc.JDBCBaseExecution.getPreparedStatement(JDBCBaseExecution.java:196) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:121) [translator-jdbc-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> ... 18 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months