Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 347891 - RepositoryNotFoundException: Repository not found: null
Summary: RepositoryNotFoundException: Repository not found: null
Status: CLOSED WORKSFORME
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.ui (show other bugs)
Version: 4.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-01 04:54 EDT by Michal Tkacz CLA
Modified: 2012-09-21 06:51 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Tkacz CLA 2011-06-01 04:54:28 EDT 
I installed Eclipse Modeling Tools package 3.7 RC2 and when I try to open a session to a CDO repository from the UI I get

org.eclipse.emf.cdo.server.RepositoryNotFoundException: Repository not found: null
	at org.eclipse.emf.cdo.server.internal.net4j.protocol.OpenSessionIndication.responding(OpenSessionIndication.java:96)
	at org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServerIndication.responding(CDOServerIndication.java:133)
	at org.eclipse.net4j.signal.IndicationWithResponse.doExtendedOutput(IndicationWithResponse.java:96)
	at org.eclipse.net4j.signal.Signal.doOutput(Signal.java:296)
	at org.eclipse.net4j.signal.IndicationWithResponse.execute(IndicationWithResponse.java:65)
	at org.eclipse.net4j.signal.Signal.runSync(Signal.java:251)
	at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)

even though I enter the name of the repository in the dialog box ("default"). It used to work with some earlier 4.0 milestones.
Comment 1 Michal Tkacz CLA 2011-06-01 10:33:46 EDT 
Actually the CDO used to run the server was a bit older than the one on the client side (probably from around February) so this may be some kind of incompatibility between these two versions. So far I haven't tried it with the server running on top of the latest version of CDO, because I have some problems with JDBC driver (I posted on the newsgroup so I might be able to continue soon).
Comment 2 Eike Stepper CLA 2011-09-19 03:15:14 EDT 
Hi Michal, sorry, this report is a bit older. Does the problem still occur?

I'm closing this a WORKSFORME, but please feel free to reopen!
Comment 3 Eike Stepper CLA 2012-09-21 06:51:58 EDT 
Closing.