Bug 1219036 - Problems with starting DV server from Teiid Designer 9.0.2.Beta1
Summary: Problems with starting DV server from Teiid Designer 9.0.2.Beta1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Tooling
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Barry LaFond
QA Contact: Matus Makovy
URL:
Whiteboard:
: 1278191 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-06 13:01 UTC by Matus Makovy
Modified: 2015-11-17 18:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Users can encounter exceptions if they attempt to launch the Data Virtualization server from within JBoss Developer Studio.
Clone Of:
Environment:
Last Closed: 2015-11-17 18:06:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIIDDES-2512 0 Minor Closed Problems with starting DV server from Teiid Designer 9.0.2.Beta1 2017-05-02 15:06:46 UTC

Description Matus Makovy 2015-05-06 13:01:41 UTC
When I try to start DV server from JBDS it starts normaly, but following exception occures (screenshot in JIRA) :

org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-children-names" for undefined. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available".
	at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:342)
	at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171)
	at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
	at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66)
	at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192)
	at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181)
	at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82)
	at org.teiid.designer.runtime.TeiidParentServerListener$1.tryConnecting(TeiidParentServerListener.java:208)
	at org.teiid.designer.runtime.TeiidParentServerListener$1.run(TeiidParentServerListener.java:177)
	at java.lang.Thread.run(Thread.java:744)
Caused by: org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: Could not execute "read-children-names" for undefined. Failure was "JBAS013493: System boot is in process; execution of remote management operations is not currently available".
	at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:333)
	... 9 more

Comment 1 Barry LaFond 2015-05-21 12:49:16 UTC
Will take a bit to track down what changed on serverside-vs-UI side. Push to 9.0.3

Comment 2 Barry LaFond 2015-07-27 19:00:27 UTC
Per Paul R.
    Is the regular and repeatable or happens only occasionally?
    I notice you are using a mac, does this happen on linux as well?
    Are the security credentials entered when creating the server correct?

Comment 3 Matus Makovy 2015-07-29 07:12:34 UTC
I don't see an option to enter credentials, during the creation of the server. I tried to change the credentials, after the server is created and it did not help. It happened 2 out of 3 times on Mac when I tried to start the server and after the change of credentials. I have seen it on Linux (Fedora 20) also, but I was not able to reproduce it today.

Comment 4 JBoss JIRA Server 2015-09-16 18:53:30 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-2512 to Resolved

Comment 5 JBoss JIRA Server 2015-09-18 09:56:52 UTC
Matus Makovy <mmakovy> updated the status of jira TEIIDDES-2512 to Closed

Comment 6 Matus Makovy 2015-11-05 08:18:50 UTC
*** Bug 1278191 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.