[JBoss JIRA] (TEIIDDES-1803) Error generating JBossWS-CXF war
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1803?page=com.atlassian.jira.plu... ]
Paul Richardson reassigned TEIIDDES-1803:
-----------------------------------------
Assignee: Van Halbert (was: Paul Richardson)
> Error generating JBossWS-CXF war
> --------------------------------
>
> Key: TEIIDDES-1803
> URL: https://issues.jboss.org/browse/TEIIDDES-1803
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Van Halbert
> Fix For: 8.2
>
>
> Attached is the Sample.vdb that was used to try to generate the JBossWS-CXF war. The following error occurred:
> java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>".
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718)
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1803) Error generating JBossWS-CXF war
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1803?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1803:
-------------------------------------------
Hey Van,
I cannot reproduce this with the financials demo. Can you attach the Sample.vdb (not currently attached) that created this exception?
Thanks
Paul
> Error generating JBossWS-CXF war
> --------------------------------
>
> Key: TEIIDDES-1803
> URL: https://issues.jboss.org/browse/TEIIDDES-1803
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> Attached is the Sample.vdb that was used to try to generate the JBossWS-CXF war. The following error occurred:
> java.lang.RuntimeException: org.xml.sax.SAXParseException: The element type "meta" must be terminated by the matching end-tag "</meta>".
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718)
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:476)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1502) Failure to access Oracle data source with column names enclosed in double quotes
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1502?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1502.
-------------------------------------
Resolution: Done
> Failure to access Oracle data source with column names enclosed in double quotes
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-1502
> URL: https://issues.jboss.org/browse/TEIIDDES-1502
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.7
> Reporter: Hisanobu Okuda
> Assignee: Mark Drilling
> Priority: Minor
> Fix For: 8.2
>
>
> EDS is throwing an error when accessing Oracle data source with column names enclosed in double quotes. I am able to import the metadata, test through Datasource explorer but when I run the query against VDB, it is not interpreting correctly to send double-quotes to the column name in this case, causing below error.
> {code}
> java.sql.SQLSyntaxErrorException: ORA-00922: missing or invalid option
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
> at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
> at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
> at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
> at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
> at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
> at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1033)
> at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1329)
> at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1909)
> at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1871)
> at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:318)
> at org.jboss.resource.adapter.jdbc.CheckValidConnectionSQL.isValidConnection(CheckValidConnectionSQL.java:58)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:560)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:364)
> at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:402)
> at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:225)
> at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:689)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
> at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:424)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
> at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:228)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:56)
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:184)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:207)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:354)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:143)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:140)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:240)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:122)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:292)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> {code}
> JDBC Importer should be identify this scenario and automatically enclose in double quotes, instead of we manually add double-quotes for these type of scenarios.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1502) Failure to access Oracle data source with column names enclosed in double quotes
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1502?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-1502:
-----------------------------------------
The map creation should remain as originally intended (first attempt to use NIS, then fallback on column name), since this map key is being compared directly against the JDBC source names. It just required some rework since the quote string is now being used where necessary. I've modified the method and also a couple points where key matching is done to use the names consistently.
pull request : https://github.com/Teiid-Designer/teiid-designer/pull/217
> Failure to access Oracle data source with column names enclosed in double quotes
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-1502
> URL: https://issues.jboss.org/browse/TEIIDDES-1502
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.7
> Reporter: Hisanobu Okuda
> Assignee: Mark Drilling
> Priority: Minor
> Fix For: 8.2
>
>
> EDS is throwing an error when accessing Oracle data source with column names enclosed in double quotes. I am able to import the metadata, test through Datasource explorer but when I run the query against VDB, it is not interpreting correctly to send double-quotes to the column name in this case, causing below error.
> {code}
> java.sql.SQLSyntaxErrorException: ORA-00922: missing or invalid option
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
> at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
> at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
> at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
> at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
> at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
> at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1033)
> at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1329)
> at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1909)
> at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1871)
> at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:318)
> at org.jboss.resource.adapter.jdbc.CheckValidConnectionSQL.isValidConnection(CheckValidConnectionSQL.java:58)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:560)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:364)
> at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:402)
> at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:225)
> at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:689)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
> at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:424)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
> at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:228)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:56)
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:184)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:207)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:354)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:143)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:140)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:240)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:122)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:292)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> {code}
> JDBC Importer should be identify this scenario and automatically enclose in double quotes, instead of we manually add double-quotes for these type of scenarios.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1814) Need to remove Teiid specific server creation dialog for Designer 8.x
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1814?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1814:
----------------------------------------
I understand, but a duplicate is source of confusion. You can possibly hide it for Teiid 8.x servers and show it for the Teiid 7.x. That include the tool bar button on the servers view
> Need to remove Teiid specific server creation dialog for Designer 8.x
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-1814
> URL: https://issues.jboss.org/browse/TEIIDDES-1814
> Project: Teiid Designer
> Issue Type: Quality Risk
> Reporter: Ramesh Reddy
>
> Currently Teiid Designer has its own server instance creation dialog box and let's user create new server instance with it. This causes confusion as to how to configure server. There should be only one way to create a server instance.
> In AS 7.x with Teiid 8.x, this dialog or option should NOT exist, as Teiid is just subsystem in JBoss AS, and it does own the Admin section as it did in Teiid 7.x series. It should operate solely by the server instance created by "Servers" view provided by the JBoss Tools.
> The Teiid's JDBC port can also be automatically read from the configuration, and JDBC user name/password can be moved to "preferences" section and default to "user/user". Do not hard code these names in code.
> Since JBoss Tools gives an option to create multiple running servers, the default selection of the server view can still exist; or contribute the default selection of server to the JBoss Tools and remove that option from Teiid Designer.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1814) Need to remove Teiid specific server creation dialog for Designer 8.x
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1814?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1814:
-------------------------------------------
> Currently Teiid Designer has its own server instance creation dialog box and let's user
> create new server instance with it. This causes confusion as to how to configure server.
> There should be only one way to create a server instance.
These dialog is merely a wrapper around the JBoss Server creation dialog box and simply allows the user to modify the JDBC user/password and Teiid display name. Otherwise, the server instance created is exactly the same as that created using the Servers view hyperlink. It was added as a convenience but if it causes that much confusion it can easily be removed.
> In AS 7.x with Teiid 8.x, this dialog or option should NOT exist, as Teiid is just
> subsystem in JBoss AS, and it does own the Admin section as it did in Teiid 7.x series.
This may be true but you forget that Designer 8.2 also allows connection to Teiid 7.7.x servers. The primary purpose of allowing the up-front connection was addressing this possibility.
> It should operate solely by the server instance created by "Servers" view provided by
> the JBoss Tools.
It does.
> The Teiid's JDBC port can also be automatically read from the configuration, and JDBC
> user name/password can be moved to "preferences" section and default to "user/user". Do
> not hard code these names in code.
The JDBC port IS read from the server configuration but as you might imagine, that is only when the parent JBoss server has been started. Values are saved at the end of the session and restored at the beginning of the session. Hard-coded defaults remain to address corner cases, such as when a server is first created and not started.
> Since JBoss Tools gives an option to create multiple running servers, the default
> selection of the server view can still exist; or contribute the default selection of
> server to the JBoss Tools and remove that option from Teiid Designer.
The default selection is important for Teiid Designer not JBoss Tools. For example, the models created by Designer are dependent upon a specific server version. Thus, targeting a specific Teiid Server version is vital for the development of valid models and their correct deployment. Thus, the default option must remain.
> Need to remove Teiid specific server creation dialog for Designer 8.x
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-1814
> URL: https://issues.jboss.org/browse/TEIIDDES-1814
> Project: Teiid Designer
> Issue Type: Quality Risk
> Reporter: Ramesh Reddy
>
> Currently Teiid Designer has its own server instance creation dialog box and let's user create new server instance with it. This causes confusion as to how to configure server. There should be only one way to create a server instance.
> In AS 7.x with Teiid 8.x, this dialog or option should NOT exist, as Teiid is just subsystem in JBoss AS, and it does own the Admin section as it did in Teiid 7.x series. It should operate solely by the server instance created by "Servers" view provided by the JBoss Tools.
> The Teiid's JDBC port can also be automatically read from the configuration, and JDBC user name/password can be moved to "preferences" section and default to "user/user". Do not hard code these names in code.
> Since JBoss Tools gives an option to create multiple running servers, the default selection of the server view can still exist; or contribute the default selection of server to the JBoss Tools and remove that option from Teiid Designer.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1814) Need to remove Teiid specific server creation dialog for Designer 8.x
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-1814:
--------------------------------------
Summary: Need to remove Teiid specific server creation dialog for Designer 8.x
Key: TEIIDDES-1814
URL: https://issues.jboss.org/browse/TEIIDDES-1814
Project: Teiid Designer
Issue Type: Quality Risk
Reporter: Ramesh Reddy
Currently Teiid Designer has its own server instance creation dialog box and let's user create new server instance with it. This causes confusion as to how to configure server. There should be only one way to create a server instance.
In AS 7.x with Teiid 8.x, this dialog or option should NOT exist, as Teiid is just subsystem in JBoss AS, and it does own the Admin section as it did in Teiid 7.x series. It should operate solely by the server instance created by "Servers" view provided by the JBoss Tools.
The Teiid's JDBC port can also be automatically read from the configuration, and JDBC user name/password can be moved to "preferences" section and default to "user/user". Do not hard code these names in code.
Since JBoss Tools gives an option to create multiple running servers, the default selection of the server view can still exist; or contribute the default selection of server to the JBoss Tools and remove that option from Teiid Designer.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1813) Restart of Designer and JBoss Server does not always reconnect to Teiid Server
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1813?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1813:
-------------------------------------------
Identified race condition between the DqpPlugin bundle starting and the org.eclipse.wst.server.core ResourceManager.
On startup, the ServerCore class is responsible for initialising the JBoss servers listed in the Servers view. It hands-off to its ResourceManager which calls its init() method. However, this method is not protected in any way so that if subsequent calls are made to it, while it is initialising then it simply returns. Thus, calls to ServerCore.getServers() returns empty while ServerCore is being initialised.
The DqpPlugin adds the TeiidParentServerListener instance to each JBoss server on startup. However, if the ResourceManager is in the middle of initialising, it actually adds the listener to nothing since the servers collection returned from ServerCore is empty.
Likewise, any part of the UI (such as the ServerStatusPanel in the Model Explorer) that requires the TeiidServerManager will fail to initialise correctly. Since the TeiidServerManager is initialised and restored on startup, it requires ServerCore's servers to set as parents on the saved TeiidServers. If there are no parent servers then the TeiidServers are orphaned and never added to the manager's own server collection. Thus, no TeiidServers are available even though the JBoss Servers are initialised correctly in the Servers view.
Thus, it is necessary to delay anything involving ServerCore's servers until its ResourceManager has correctly initialised its server collection.
> Restart of Designer and JBoss Server does not always reconnect to Teiid Server
> ------------------------------------------------------------------------------
>
> Key: TEIIDDES-1813
> URL: https://issues.jboss.org/browse/TEIIDDES-1813
> Project: Teiid Designer
> Issue Type: Bug
> Components: Usability
> Affects Versions: 8.2
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> Cases where restarting Designer and the configured JBoss Server, fails to reconnect to the Teiid Server. This leaves the user with the expectation that everything is fine, until an operation is conducted, eg. preview, where the server is necessary, resulting in 'no running server messages'.
> Further details and use-case [here|https://community.jboss.org/message/830573#830573].
--
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
10 years, 9 months