[JBoss JIRA] (TEIID-5514) Move release notes to root
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5514:
-------------------------------------
Summary: Move release notes to root
Key: TEIID-5514
URL: https://issues.jboss.org/browse/TEIID-5514
Project: Teiid
Issue Type: Task
Components: Build/Kits
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 12.0
Just a quick task to put the release notes at the top level, rather than deeply nested.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5513) Fully automate release
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5513:
-------------------------------------
Summary: Fully automate release
Key: TEIID-5513
URL: https://issues.jboss.org/browse/TEIID-5513
Project: Teiid
Issue Type: Task
Components: Build/Kits
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 12.0
We should add a fully automated release on the creation of a tag.
One outstanding task is to clean up the javacc doc generation and link that with the doc release as well.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4251:
---------------------------------------
Moving the remaining work to 12.0 as there is still more discussion needed on the interplay of an alternative materialization implementation.
> Built in support for Postgres DB as materialization target
> ----------------------------------------------------------
>
> Key: TEIID-4251
> URL: https://issues.jboss.org/browse/TEIID-4251
> Project: Teiid
> Issue Type: Sub-task
> Components: Server
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.0
>
>
> If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like
> - Creation of a common STATUS table
> - Creation of the materilization targets (create views on dbms)
> - On load, on undeploy and load scripts for all the materialization views
> We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4251:
----------------------------------
Fix Version/s: 12.0
(was: 11.2)
> Built in support for Postgres DB as materialization target
> ----------------------------------------------------------
>
> Key: TEIID-4251
> URL: https://issues.jboss.org/browse/TEIID-4251
> Project: Teiid
> Issue Type: Sub-task
> Components: Server
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.0
>
>
> If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like
> - Creation of a common STATUS table
> - Creation of the materilization targets (create views on dbms)
> - On load, on undeploy and load scripts for all the materialization views
> We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5512) No transaction associated with the current thread
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5512?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5512:
---------------------------------------
Is there any log, at least of the transaction service of this scenario that can be provided?
Are you doing any explicit control of the transaction boundaries - xa client or using an explicit local transaction or this all inferred from the auto commit txn setting?
> No transaction associated with the current thread
> -------------------------------------------------
>
> Key: TEIID-5512
> URL: https://issues.jboss.org/browse/TEIID-5512
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 10.3.4
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Priority: Major
>
> I'm facing this problem but I'm not sure where or when it occurs. It seems to be randomly. The virtual procedure that is run while this problem occurs, copies data from one xa-datasource to a temp table and then inserts it into a non-xa datasource.
> 2018-10-22 09:50:28,361 WARN [org.teiid.PROCESSOR] (Worker25_QueryProcessorQueue73179) F274YMAVci29 TEIID31200 Lower level transaction Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffffac130002:-2cc3b1fb:5bcd8cc9:f717 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider) not properly ended, rolling back.
> 2018-10-22 09:50:28,361 WARN [org.teiid.PROCESSOR] (Worker25_QueryProcessorQueue73179) F274YMAVci29 TEIID30028 Failed to properly rollback autowrap transaction properly: org.teiid.client.xa.XATransactionException: TEIID30535 java.lang.IllegalStateException: No transaction associated with the current thread
> at org.teiid.dqp.internal.process.TransactionServerImpl.rollbackDirect(TransactionServerImpl.java:432)
> at org.teiid.dqp.internal.process.TransactionServerImpl.rollback(TransactionServerImpl.java:551)
> at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:117)
> at com.sun.proxy.$Proxy25.rollback(Unknown Source)
> at org.teiid.dqp.internal.process.RequestWorkItem.close(RequestWorkItem.java:574)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:375)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:47)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:277)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalStateException: No transaction associated with the current thread
> at org.wildfly.transaction.client.ContextTransactionManager.rollback(ContextTransactionManager.java:81)
> at org.teiid.dqp.internal.process.TransactionServerImpl.rollbackDirect(TransactionServerImpl.java:426)
> ... 16 more
> 2018-10-22 09:50:28,389 WARN [org.teiid.PROCESSOR] (Worker22_QueryProcessorQueue73181) F274YMAVci29 TEIID30020 Processing exception for request F274YMAVci29.39 'TEIID30538 java.lang.IllegalStateException: WFTXN0007: A transaction is already associated with the current thread'. Originally XATransactionException ContextTransactionManager.java:140. Enable more detailed logging to see the entire stacktrace.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5512) No transaction associated with the current thread
by Bram Gadeyne (Jira)
Bram Gadeyne created TEIID-5512:
-----------------------------------
Summary: No transaction associated with the current thread
Key: TEIID-5512
URL: https://issues.jboss.org/browse/TEIID-5512
Project: Teiid
Issue Type: Bug
Affects Versions: 10.3.4
Reporter: Bram Gadeyne
Assignee: Steven Hawkins
I'm facing this problem but I'm not sure where or when it occurs. It seems to be randomly. The virtual procedure that is run while this problem occurs, copies data from one xa-datasource to a temp table and then inserts it into a non-xa datasource.
2018-10-22 09:50:28,361 WARN [org.teiid.PROCESSOR] (Worker25_QueryProcessorQueue73179) F274YMAVci29 TEIID31200 Lower level transaction Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffffac130002:-2cc3b1fb:5bcd8cc9:f717 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider) not properly ended, rolling back.
2018-10-22 09:50:28,361 WARN [org.teiid.PROCESSOR] (Worker25_QueryProcessorQueue73179) F274YMAVci29 TEIID30028 Failed to properly rollback autowrap transaction properly: org.teiid.client.xa.XATransactionException: TEIID30535 java.lang.IllegalStateException: No transaction associated with the current thread
at org.teiid.dqp.internal.process.TransactionServerImpl.rollbackDirect(TransactionServerImpl.java:432)
at org.teiid.dqp.internal.process.TransactionServerImpl.rollback(TransactionServerImpl.java:551)
at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.teiid.logging.LogManager$LoggingProxy.invoke(LogManager.java:117)
at com.sun.proxy.$Proxy25.rollback(Unknown Source)
at org.teiid.dqp.internal.process.RequestWorkItem.close(RequestWorkItem.java:574)
at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:375)
at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:47)
at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:276)
at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:277)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115)
at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: No transaction associated with the current thread
at org.wildfly.transaction.client.ContextTransactionManager.rollback(ContextTransactionManager.java:81)
at org.teiid.dqp.internal.process.TransactionServerImpl.rollbackDirect(TransactionServerImpl.java:426)
... 16 more
2018-10-22 09:50:28,389 WARN [org.teiid.PROCESSOR] (Worker22_QueryProcessorQueue73181) F274YMAVci29 TEIID30020 Processing exception for request F274YMAVci29.39 'TEIID30538 java.lang.IllegalStateException: WFTXN0007: A transaction is already associated with the current thread'. Originally XATransactionException ContextTransactionManager.java:140. Enable more detailed logging to see the entire stacktrace.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5511) Update groovy to common version
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5511?page=com.atlassian.jira.plugin... ]
Steven Hawkins reassigned TEIID-5511:
-------------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
Ramesh, I'm kicking this over to you to see if you want to handle the removal of adminshell.
> Update groovy to common version
> -------------------------------
>
> Key: TEIID-5511
> URL: https://issues.jboss.org/browse/TEIID-5511
> Project: Teiid
> Issue Type: Sub-task
> Components: AdminApi
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 12.0
>
>
> At the common 2.4.7 version the adminshell has quite a few compilation issues. We should evaluate updating to the latest version, or even removal entirely.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months
[JBoss JIRA] (TEIID-5511) Update groovy to common version
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5511:
-------------------------------------
Summary: Update groovy to common version
Key: TEIID-5511
URL: https://issues.jboss.org/browse/TEIID-5511
Project: Teiid
Issue Type: Sub-task
Components: AdminApi
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 12.0
At the common 2.4.7 version the adminshell has quite a few compilation issues. We should evaluate updating to the latest version, or even removal entirely.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 7 months