Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335802 - [ZooDiscovery] ArrayIndexOutOfBoundsException when starting Discovery View
Summary: [ZooDiscovery] ArrayIndexOutOfBoundsException when starting Discovery View
Status: RESOLVED FIXED
Alias: None
Product: ECF
Classification: RT
Component: ecf.discovery (show other bugs)
Version: 3.4.1   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: ecf.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-30 21:32 EST by Wim Jongman CLA
Modified: 2011-03-09 05:27 EST (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 Wim Jongman CLA 2011-01-30 21:32:34 EST 
When starting the discovery view, this exception is seen. The parameter value of the propAsString parameter at this time is

org.eclipse.ecf.provider.discovery.CompositeDiscoveryContainer

which is not a key value pair that this method is assuming.

Can anybody imagine that this is caused by something they have been working on? I can make the exception go away but I don't know why the method is so convinced that it receives a key=value pair?


java.lang.ArrayIndexOutOfBoundsException: 1
	at org.eclipse.ecf.provider.zookeeper.core.internal.Configuration.<init>(Configuration.java:63)
	at org.eclipse.ecf.provider.zookeeper.core.internal.Configuration.<init>(Configuration.java:55)
	at org.eclipse.ecf.provider.zookeeper.core.internal.Configurator.createConfig(Configurator.java:41)
	at org.eclipse.ecf.provider.zookeeper.core.ZooDiscoveryContainer.init(ZooDiscoveryContainer.java:122)
	at org.eclipse.ecf.provider.zookeeper.core.ZooDiscoveryContainer.connect(ZooDiscoveryContainer.java:327)
	at org.eclipse.ecf.provider.discovery.CompositeDiscoveryContainer.connect(CompositeDiscoveryContainer.java:150)
	at org.eclipse.ecf.provider.discovery.SingletonDiscoveryContainer.connect(SingletonDiscoveryContainer.java:46)
	at org.eclipse.ecf.discovery.ui.model.resource.ServiceResource$ServiceDiscoveryListener.connect(ServiceResource.java:63)
	at org.eclipse.ecf.discovery.ui.model.resource.ServiceResource$1.run(ServiceResource.java:455)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Markus Kuppe CLA 2011-01-31 03:08:21 EST 
Hi Wim,

this seems related to bug #332848.
Comment 2 Wim Jongman CLA 2011-03-09 05:27:39 EST 
Hi Markus, thanks, yes it was. I did not notice that this was the case. Fix released to master. All systems are go!