[JBoss JIRA] (TEIID-2352) START USER COMMAND and END USER COMMAND are not shown with loglevel=DEBUG
by Hisanobu Okuda (JIRA)
[ https://issues.jboss.org/browse/TEIID-2352?page=com.atlassian.jira.plugin... ]
Hisanobu Okuda commented on TEIID-2352:
---------------------------------------
org.teiid.dqp.internal.process.DQPCore#logMMCommand() should be:-
{code}
[hokuda@localhost process]$ diff -u DQPCore.java.org DQPCore.java.fix1
--- DQPCore.java.org 2012-07-18 19:31:12.000000000 +0900
+++ DQPCore.java.fix1 2013-01-17 16:21:39.202972307 +0900
@@ -691,7 +691,7 @@
void logMMCommand(RequestWorkItem workItem, Event status, Integer rowCount) {
if ((status != Event.PLAN && !LogManager.isMessageToBeRecorded(LogConstants.CTX_COMMANDLOGGING, Mess
ageLevel.DETAIL))
- || !LogManager.isMessageToBeRecorded(LogConstants.CTX_COMMANDLOGGING, MessageLevel.T
RACE)) {
+ ) {
return;
}
[hokuda@localhost process]$
{code}
> START USER COMMAND and END USER COMMAND are not shown with loglevel=DEBUG
> -------------------------------------------------------------------------
>
> Key: TEIID-2352
> URL: https://issues.jboss.org/browse/TEIID-2352
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 7.7.1
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
>
> With loglevel=DEBUG, START USER COMMAND and END USER COMMAND log messages are not shown.
> With loglevel=TRACE, they are shown:-
> {code}
> 2013-01-17 13:45:58,205 DEBUG [org.teiid.COMMAND_LOG] (New I/O server worker #1-1:) START USER COMMAND:startTime=2013-01-17 13:45:58.205 requestID=GQ2RlqzuDfet.0 txID=null sessionID=GQ2RlqzuDfet applicationName=JDBC principal=user@teiid-security vdbName=PREVIEW_31af68bd-5f4d-4e77-b13c-94823d02dcf8_test_project vdbVersion=1 sql=select * from "v2"."data2View"
> ...
> 2013-01-17 13:50:23,968 DEBUG [org.teiid.COMMAND_LOG] (Worker2_QueryProcessorQueue9:) END USER COMMAND: endTime=2013-01-17 13:50:23.968 requestID=GQ2RlqzuDfet.0 txID=null sessionID=GQ2RlqzuDfet principal=user@teiid-security vdbName=PREVIEW_31af68bd-5f4d-4e77-b13c-94823d02dcf8_test_project vdbV
> ersion=1 finalRowCount=2
> {code}
> But shown as "DEBUG".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2352) START USER COMMAND and END USER COMMAND are not shown with loglevel=DEBUG
by Hisanobu Okuda (JIRA)
[ https://issues.jboss.org/browse/TEIID-2352?page=com.atlassian.jira.plugin... ]
Hisanobu Okuda updated TEIID-2352:
----------------------------------
Comment: was deleted
(was: org.teiid.dqp.internal.process.DQPCore#logMMCommand() should be:-
{code}
[hokuda@localhost process]$ diff -u DQPCore.java.org DQPCore.java.fix1
--- DQPCore.java.org 2012-07-18 19:31:12.000000000 +0900
+++ DQPCore.java.fix1 2013-01-17 14:43:52.224319386 +0900
@@ -690,7 +690,7 @@
}
void logMMCommand(RequestWorkItem workItem, Event status, Integer rowCount) {
- if ((status != Event.PLAN && !LogManager.isMessageToBeRecorded(LogConstants.CTX_COMMANDLOGGING, Mess
ageLevel.DETAIL))
+ if ((status != Event.PLAN && status != Event.NEW && !LogManager.isMessageToBeRecorded(LogConstants.C
TX_COMMANDLOGGING, MessageLevel.DETAIL))
|| !LogManager.isMessageToBeRecorded(LogConstants.CTX_COMMANDLOGGING, MessageLevel.T
RACE)) {
return;
}
[hokuda@localhost process]$
{code})
> START USER COMMAND and END USER COMMAND are not shown with loglevel=DEBUG
> -------------------------------------------------------------------------
>
> Key: TEIID-2352
> URL: https://issues.jboss.org/browse/TEIID-2352
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 7.7.1
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
>
> With loglevel=DEBUG, START USER COMMAND and END USER COMMAND log messages are not shown.
> With loglevel=TRACE, they are shown:-
> {code}
> 2013-01-17 13:45:58,205 DEBUG [org.teiid.COMMAND_LOG] (New I/O server worker #1-1:) START USER COMMAND:startTime=2013-01-17 13:45:58.205 requestID=GQ2RlqzuDfet.0 txID=null sessionID=GQ2RlqzuDfet applicationName=JDBC principal=user@teiid-security vdbName=PREVIEW_31af68bd-5f4d-4e77-b13c-94823d02dcf8_test_project vdbVersion=1 sql=select * from "v2"."data2View"
> ...
> 2013-01-17 13:50:23,968 DEBUG [org.teiid.COMMAND_LOG] (Worker2_QueryProcessorQueue9:) END USER COMMAND: endTime=2013-01-17 13:50:23.968 requestID=GQ2RlqzuDfet.0 txID=null sessionID=GQ2RlqzuDfet principal=user@teiid-security vdbName=PREVIEW_31af68bd-5f4d-4e77-b13c-94823d02dcf8_test_project vdbV
> ersion=1 finalRowCount=2
> {code}
> But shown as "DEBUG".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2352) START USER COMMAND and END USER COMMAND are not shown with loglevel=DEBUG
by Hisanobu Okuda (JIRA)
[ https://issues.jboss.org/browse/TEIID-2352?page=com.atlassian.jira.plugin... ]
Hisanobu Okuda commented on TEIID-2352:
---------------------------------------
org.teiid.dqp.internal.process.DQPCore#logMMCommand() should be:-
{code}
[hokuda@localhost process]$ diff -u DQPCore.java.org DQPCore.java.fix1
--- DQPCore.java.org 2012-07-18 19:31:12.000000000 +0900
+++ DQPCore.java.fix1 2013-01-17 14:43:52.224319386 +0900
@@ -690,7 +690,7 @@
}
void logMMCommand(RequestWorkItem workItem, Event status, Integer rowCount) {
- if ((status != Event.PLAN && !LogManager.isMessageToBeRecorded(LogConstants.CTX_COMMANDLOGGING, Mess
ageLevel.DETAIL))
+ if ((status != Event.PLAN && status != Event.NEW && !LogManager.isMessageToBeRecorded(LogConstants.C
TX_COMMANDLOGGING, MessageLevel.DETAIL))
|| !LogManager.isMessageToBeRecorded(LogConstants.CTX_COMMANDLOGGING, MessageLevel.T
RACE)) {
return;
}
[hokuda@localhost process]$
{code}
> START USER COMMAND and END USER COMMAND are not shown with loglevel=DEBUG
> -------------------------------------------------------------------------
>
> Key: TEIID-2352
> URL: https://issues.jboss.org/browse/TEIID-2352
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 7.7.1
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
>
> With loglevel=DEBUG, START USER COMMAND and END USER COMMAND log messages are not shown.
> With loglevel=TRACE, they are shown:-
> {code}
> 2013-01-17 13:45:58,205 DEBUG [org.teiid.COMMAND_LOG] (New I/O server worker #1-1:) START USER COMMAND:startTime=2013-01-17 13:45:58.205 requestID=GQ2RlqzuDfet.0 txID=null sessionID=GQ2RlqzuDfet applicationName=JDBC principal=user@teiid-security vdbName=PREVIEW_31af68bd-5f4d-4e77-b13c-94823d02dcf8_test_project vdbVersion=1 sql=select * from "v2"."data2View"
> ...
> 2013-01-17 13:50:23,968 DEBUG [org.teiid.COMMAND_LOG] (Worker2_QueryProcessorQueue9:) END USER COMMAND: endTime=2013-01-17 13:50:23.968 requestID=GQ2RlqzuDfet.0 txID=null sessionID=GQ2RlqzuDfet principal=user@teiid-security vdbName=PREVIEW_31af68bd-5f4d-4e77-b13c-94823d02dcf8_test_project vdbV
> ersion=1 finalRowCount=2
> {code}
> But shown as "DEBUG".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2352) START USER COMMAND and END USER COMMAND are not shown with loglevel=DEBUG
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created TEIID-2352:
-------------------------------------
Summary: START USER COMMAND and END USER COMMAND are not shown with loglevel=DEBUG
Key: TEIID-2352
URL: https://issues.jboss.org/browse/TEIID-2352
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 7.7.1
Reporter: Hisanobu Okuda
Assignee: Steven Hawkins
With loglevel=DEBUG, START USER COMMAND and END USER COMMAND log messages are not shown.
With loglevel=TRACE, they are shown:-
{code}
2013-01-17 13:45:58,205 DEBUG [org.teiid.COMMAND_LOG] (New I/O server worker #1-1:) START USER COMMAND:startTime=2013-01-17 13:45:58.205 requestID=GQ2RlqzuDfet.0 txID=null sessionID=GQ2RlqzuDfet applicationName=JDBC principal=user@teiid-security vdbName=PREVIEW_31af68bd-5f4d-4e77-b13c-94823d02dcf8_test_project vdbVersion=1 sql=select * from "v2"."data2View"
...
2013-01-17 13:50:23,968 DEBUG [org.teiid.COMMAND_LOG] (Worker2_QueryProcessorQueue9:) END USER COMMAND: endTime=2013-01-17 13:50:23.968 requestID=GQ2RlqzuDfet.0 txID=null sessionID=GQ2RlqzuDfet principal=user@teiid-security vdbName=PREVIEW_31af68bd-5f4d-4e77-b13c-94823d02dcf8_test_project vdbV
ersion=1 finalRowCount=2
{code}
But shown as "DEBUG".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2182) Mechanism to hook up event listener into Teiid runtime
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2182?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2182.
---------------------------------
Resolution: Done
I changed the interface to
{code}
public interface EventListener {
/**
* Invoked when VDB is deployed
* @param vdbName
* @param vdbVersion
*/
void vdbDeployed(String vdbName, int vdbVersion);
/**
* Invoked when VDB undeployed
* @param vdbName
* @param vdbVersion
*/
void vdbUndeployed(String vdbName, int vdbVersion);
/**
* VDB and all its metadata has been loaded and in ACTIVE state.
* @param vdb
*/
void vdbLoaded(VDB vdb);
/**
* VDB failed to load and in FAILED state; Note this can be called
* multiple times for given VDB
* @param vdb
*/
void vdbLoadFailed(VDB vdb);
}
{code}
Please let me know if you think we need to modifications to this.
> Mechanism to hook up event listener into Teiid runtime
> ------------------------------------------------------
>
> Key: TEIID-2182
> URL: https://issues.jboss.org/browse/TEIID-2182
> Project: Teiid
> Issue Type: Feature Request
> Components: AdminApi, Server
> Affects Versions: 8.1
> Environment: Windows 7 64 bit
> Reporter: Anil Allewar
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> It would be to useful allow the installation of custom listeners since we don't have a global vdb table that could have customizable triggers. This could cover for example custom strategies for external materialization initialization.
> This would also help in where an application wants to listen to when a VDB was added, made active, destroyed so that it can handle those events as required by the application.
> Please see the thread below for the context & details
> https://community.jboss.org/message/756060
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2350) NPE during call generated REST service from browser
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2350?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-2350:
--------------------------------
Fix Version/s: 8.3
Assignee: Ramesh Reddy (was: Steven Hawkins)
Complexity: Low
Component/s: Server
> NPE during call generated REST service from browser
> ---------------------------------------------------
>
> Key: TEIID-2350
> URL: https://issues.jboss.org/browse/TEIID-2350
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.2
> Environment: Windows 7, JBoss AS 7.1.1 Final
> Reporter: Vadim Melnikov
> Assignee: Ramesh Reddy
> Fix For: 8.3
>
>
> See also discussion at https://community.jboss.org/thread/219690
> Teiid 8.2
> Example from https://docs.jboss.org/author/display/teiid82final/REST+Service+Through+VDB
>
> {code:xml}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="sample" version="1">
>
> <property name="UseConnectorMetadata" value="true" />
> <property name="{http://teiid.org/rest}auto-generate" value="true"/>
> <property name="{http://teiid.org/rest}security-type" value="HttpBasic"/>
> <property name="{http://teiid.org/rest}security-domain" value="teiid-security"/>
> <property name="{http://teiid.org/rest}security-role" value="example-role"/>
> <property name="{http://teiid.org/rest}passthrough-auth" value="true"/>
>
> <model name="PM1">
> <source name="text-connector" translator-name="loopback" />
> <metadata type="DDL"><![CDATA[
> CREATE FOREIGN TABLE G1 (e1 string, e2 integer);
> CREATE FOREIGN TABLE G2 (e1 string, e2 integer);
> ]]> </metadata>
> </model>
> <model name="View" type ="VIRTUAL">
> <metadata type="DDL"><![CDATA[
> SET NAMESPACE 'http://teiid.org/rest' AS REST;
> CREATE VIRTUAL PROCEDURE g1Table(IN p1 integer) RETURNS TABLE (xml_out xml) OPTIONS (UPDATECOUNT 0, "REST:METHOD" 'GET', "REST:URI" 'g1/{p1}')
> AS
> BEGIN
> SELECT XMLELEMENT(NAME "rows", XMLATTRIBUTES (g1Table.p1 as p1), XMLAGG(XMLELEMENT(NAME "row", XMLFOREST(e1, e2)))) AS xml_out FROM PM1.G1;
> END
> ]]> </metadata>
> </model>
>
> </vdb>
> {code}
>
> Open URL: http://localhost:8080/sample_1/view/g1/1
> Error log was generated:
>
> org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException
> org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:340)
> org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:214)
> org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:190)
> org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:540)
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> root cause
> java.lang.NullPointerException
> org.teiid.jboss.rest.TeiidRSProvider.execute(TeiidRSProvider.java:64)
> org.teiid.jboss.rest.View.g1Tableapplication_xml(Unknown Source)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> java.lang.reflect.Method.invoke(Method.java:597)
> org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:155)
> org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:257)
> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222)
> org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211)
> org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:525)
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)
> org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
> org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
> org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2350) NPE during call generated REST service from browser
by Vadim Melnikov (JIRA)
Vadim Melnikov created TEIID-2350:
-------------------------------------
Summary: NPE during call generated REST service from browser
Key: TEIID-2350
URL: https://issues.jboss.org/browse/TEIID-2350
Project: Teiid
Issue Type: Bug
Affects Versions: 8.2
Environment: Windows 7, JBoss AS 7.1.1 Final
Reporter: Vadim Melnikov
Assignee: Steven Hawkins
See also discussion at https://community.jboss.org/thread/219690
Teiid 8.2
Example from https://docs.jboss.org/author/display/teiid82final/REST+Service+Through+VDB
{code:xml}
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<vdb name="sample" version="1">
<property name="UseConnectorMetadata" value="true" />
<property name="{http://teiid.org/rest}auto-generate" value="true"/>
<property name="{http://teiid.org/rest}security-type" value="HttpBasic"/>
<property name="{http://teiid.org/rest}security-domain" value="teiid-security"/>
<property name="{http://teiid.org/rest}security-role" value="example-role"/>
<property name="{http://teiid.org/rest}passthrough-auth" value="true"/>
<model name="PM1">
<source name="text-connector" translator-name="loopback" />
<metadata type="DDL"><![CDATA[
CREATE FOREIGN TABLE G1 (e1 string, e2 integer);
CREATE FOREIGN TABLE G2 (e1 string, e2 integer);
]]> </metadata>
</model>
<model name="View" type ="VIRTUAL">
<metadata type="DDL"><![CDATA[
SET NAMESPACE 'http://teiid.org/rest' AS REST;
CREATE VIRTUAL PROCEDURE g1Table(IN p1 integer) RETURNS TABLE (xml_out xml) OPTIONS (UPDATECOUNT 0, "REST:METHOD" 'GET', "REST:URI" 'g1/{p1}')
AS
BEGIN
SELECT XMLELEMENT(NAME "rows", XMLATTRIBUTES (g1Table.p1 as p1), XMLAGG(XMLELEMENT(NAME "row", XMLFOREST(e1, e2)))) AS xml_out FROM PM1.G1;
END
]]> </metadata>
</model>
</vdb>
{code}
Open URL: http://localhost:8080/sample_1/view/g1/1
Error log was generated:
org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException
org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:340)
org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:214)
org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:190)
org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:540)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
root cause
java.lang.NullPointerException
org.teiid.jboss.rest.TeiidRSProvider.execute(TeiidRSProvider.java:64)
org.teiid.jboss.rest.View.g1Tableapplication_xml(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:155)
org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:257)
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:222)
org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:211)
org.jboss.resteasy.core.SynchronousDispatcher.getResponse(SynchronousDispatcher.java:525)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:502)
org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:119)
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:208)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:55)
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:50)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months
[JBoss JIRA] (TEIID-2349) Cannot execute Two-Phase Commit using Multi-Source Model Dynamic VDB
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2349?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2349:
------------------------------------------------
Eiichi Nagai <enagai(a)redhat.com> made a comment on [bug 895304|https://bugzilla.redhat.com/show_bug.cgi?id=895304]
Hi Van,
Thank you for your update.
> But until then, can you get them to try one of the below options to confirm there is a work around for this issue?
I tried setAutoCommit(false). Yes, Explicit transaction is working. They become the workaround.
> Cannot execute Two-Phase Commit using Multi-Source Model Dynamic VDB
> --------------------------------------------------------------------
>
> Key: TEIID-2349
> URL: https://issues.jboss.org/browse/TEIID-2349
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 7.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.1, 7.7.4
>
>
> Description of problem:
> 2nd connection to Multi-Source Model Dynamic VDB is not Two-Phase Commit.
> How reproducible:
> Always
> Steps to Reproduce:
> Execute a update query via Multi-Source Model Dynamic VDB.
> ex)
> vdb - maseter-vdb.xml
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <vdb name="MASTER-VDB" version="1">
> <description>A Dynamic VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <model visible="true" type="PHYSICAL" name="VDB1">
> <property name="supports-multi-source-bindings" value="true" />
> <source name="db02" translator-name="postgresql" connection-jndi-name="java:/PostgresXADS02" />
> <source name="db01" translator-name="postgresql" connection-jndi-name="java:/PostgresXADS01" />
> </model>
> </vdb>
>
> Additional info:
> Set the multisourceUpdate flag as first query plan creating.
> org.teiid.dqp.internal.process.multisource.MultiSourcePlanToProcessConverter.java
> 90: @Override
> 91: public synchronized RelationalPlan convert(PlanNode planNode)
> 92: throws QueryPlannerException, TeiidComponentException {
> 93: RelationalPlan result = null;
> 94: try {
> 95: result = super.convert(planNode);
> 96: return result;
> 97: } finally {
> 98: if (result != null && update && multiSource) {
> -> 99: result.setMultisourceUpdate(true);
> 100: }
> 101: update = false;
> 102: multiSource = false;
> 103: }
> 104: }
> If multisourceUpdate is true, transactionService is started by teiid engine. But, second connects does not set the multisourceUpdate flag. Therefore, teiid engine does not start transactionService.
> org.teiid.dqp.internal.process.Request.java
> 338: private void createProcessor() throws TeiidComponentException {
> --- snip ---
> 349: if(RequestMessage.TXN_WRAP_ON.equals(requestMsg.getTxnAutoWrapMode())){
> 350: startAutoWrapTxn = true;
> 351: } else if (RequestMessage.TXN_WRAP_DETECT.equals(requestMsg.getTxnAutoWrapMode())){
> 352: boolean transactionalRead = requestMsg.getTransactionIsolation() == Connection.TRANSACTION_REPEATABLE_READ
> 353: || requestMsg.getTransactionIsolation() == Connection.TRANSACTION_SERIALIZABLE;
> -> 354: startAutoWrapTxn = processPlan.requiresTransaction(transactionalRead);
> 355: }
> 356:
> 357: if (startAutoWrapTxn) {
> 358: try {
> -> 359: transactionService.begin(tc);
> 360: } catch (XATransactionException err) {
> 361: throw new TeiidComponentException(err);
> 362: }
> 363: }
> 364: }
> org.teiid.query.processor.relational.RelationalPlan.java
> 254: @Override
> 255: public boolean requiresTransaction(boolean transactionalReads) {
> 256: if (multisourceUpdate) {
> -> 257: return true;
> 258: }
> 259: if (this.with != null) {
> 260: if (transactionalReads) {
> 261: return true;
> 262: }
> 263: for (WithQueryCommand withCommand : this.with) {
> 264: if (withCommand.getCommand().getProcessorPlan().requiresTransaction(transactionalReads)) {
> 265: return true;
> 266: }
> 267: }
> 268: }
> 279: return requiresTransaction(transactionalReads, root);
> 270: }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 11 months