[JBoss JIRA] (TEIID-3241) Audit/Command Logging handler names do not match web console handler names
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3241?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3241.
---------------------------------
> Audit/Command Logging handler names do not match web console handler names
> --------------------------------------------------------------------------
>
> Key: TEIID-3241
> URL: https://issues.jboss.org/browse/TEIID-3241
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 8.7.1
>
>
> When changing configuration of Audit and Command logging via Web Management, an exception is thrown in specific usecase, see the steps to reproduce below.
> Then even after server restart logging doesn't work. No changes noticed in standalone.xml during the configuration.
> Version-Release number of selected component (if applicable):
> DV 6.1.0 ER4
> How reproducible:
> Once after installation (further on the logging simply doesn't work)
> Steps to Reproduce:
> 1.Install DV with audit/command logging enabled
> 2.Start DV with bin/standalone.sh, check that logging works
> 3.Access http://localhost:9990/console/App.html#teiid-audit and unselect selected options
> 4.Apply
> 5.Select the previously deselected options again
> 6.Apply
> 7.See the server log in console
> 8.When there is server reload between unselecting and reselecting the options, then the exception is not raised, but the logging doesn't work afterwards.
> Actual results:
> java.lang.IllegalArgumentException: Handler "TEIID_AUDIT_LOG" is not found
> or
> java.lang.IllegalArgumentException: Handler "TEIID_COMMAND_LOG" is not found
> Expected results:
> Logging configured again
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3245) Database Logging: Problems with Microsoft
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3245?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3245.
---------------------------------
> Database Logging: Problems with Microsoft
> ------------------------------------------
>
> Key: TEIID-3245
> URL: https://issues.jboss.org/browse/TEIID-3245
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Fix For: 8.7.1
>
>
> Still getting error with mssql driver and sql server 2012.
> The error messages look similar, but one:
> [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 55) Incorrect syntax near the keyword 'rowcount'.
> is present.
> While the prior issue
> 14:46:56,858 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool – 57) Incorrect syntax near the keyword 'plan'.
> was solved.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3238) Cassandra: Access to Cassandra fails with CNF "sun/misc/Unsafe"
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3238?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3238.
---------------------------------
> Cassandra: Access to Cassandra fails with CNF "sun/misc/Unsafe"
> ---------------------------------------------------------------
>
> Key: TEIID-3238
> URL: https://issues.jboss.org/browse/TEIID-3238
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Labels: alpha2
> Fix For: 8.10
>
>
> new connection: null: java.lang.NoClassDefFoundError: sun/misc/Unsafe
> at com.codahale.metrics.Striped64.getUnsafe(Striped64.java:330) [metrics-core-3.0.2.jar:3.0.2]
> at com.codahale.metrics.Striped64.<clinit>(Striped64.java:311) [metrics-core-3.0.2.jar:3.0.2]
> at com.codahale.metrics.Counter.<init>(Counter.java:10) [metrics-core-3.0.2.jar:3.0.2]
> at com.codahale.metrics.MetricRegistry$MetricBuilder$1.newMetric(MetricRegistry.java:402) [metrics-core-3.0.2.jar:3.0.2]
> at com.codahale.metrics.MetricRegistry$MetricBuilder$1.newMetric(MetricRegistry.java:399) [metrics-core-3.0.2.jar:3.0.2]
> at com.codahale.metrics.MetricRegistry.getOrAdd(MetricRegistry.java:313) [metrics-core-3.0.2.jar:3.0.2]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3215?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3215.
---------------------------------
> External Materialization ON_VDB_START_SCRIPT invocation issues
> --------------------------------------------------------------
>
> Key: TEIID-3215
> URL: https://issues.jboss.org/browse/TEIID-3215
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
> Labels: Final
> Fix For: 8.7.1, 8.9
>
> Attachments: mat-views-vdb.xml
>
>
> With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.)
> Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does.
> A - 1. Copy the vdbname-vdb.xml into deployments folder
> 2. Start the server
> B - 1. Start the server
> 2. Copy the vdbname-vdb.xml into deployments folder
> That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table,...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months