[
https://issues.jboss.org/browse/TEIIDDES-1699?page=com.atlassian.jira.plu...
]
Paul Richardson commented on TEIIDDES-1699:
-------------------------------------------
The TeiidServerManager class governs the live registry of TeiidServers. However, it simply
is an arraylist so would support duplicates.
However, the internalAdd and internalRemove methods are governed by the
isRegistered(TeiidServer) method which checks the server based on URL and username.
Likewise, the TeiidServerAdapterFactory which determines the display of Teiid servers in
the server view, iterates through the registry and find the server which has the JBoss
Server as a parent. This is an instance equality check so I don't think this would be
the problem.
My gut feeling is that all your 8.3 servers have the same URL and same user, ie. all
localhost and all admin, all using port 9999. As such it is unsurprising that they start
confusing each other when a JBoss instance is started. The use case of having more than
one server on a single host is impossible to satisfy since there is no way to identify
uniquely the distinct servers.
You can try debugging the TeiidServerManager to conclude if this is the case.
Issue with ServerView leads to Out of Memory condition
------------------------------------------------------
Key: TEIIDDES-1699
URL:
https://issues.jboss.org/browse/TEIIDDES-1699
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 8.1
Reporter: Mark Drilling
Assignee: Paul Richardson
Fix For: 8.2
I'm running into out of memory with Designer in certain situations defining Teiid
Servers in the Servers view. It is related to having different instances of the same
server type in the view.
In my situation, I have
1) JBoss AS5.1 / Teiid 7.7 server
2) JBoss AS7.1 / Teiid 8.3 servers
The AS7.1/Teiid 8.3 servers point to different installations that I have locally. If I
start one of the Teiid8.3 servers, the view seems to go into a loop and eventually run out
of memory and the designer crashes.
I suspect this has something to do with the registered servers not having unique
identifier because the view looks like it is confusing the 8.3 servers. But I have not
been able to pinpoint what is happening yet.
Also, I'm confused regarding the criteria for a server to be added to the registry.
On Designer shutdown, I'm looking at the registry.xml and not all of the defined
servers are included. Does a server need to be started in order for it to be added?
--
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