Startup Error

When I start the FactoryPMI Designer I get this error.

java.lang.ArrayIndexOutOfBoundsException: No such child: 2
at java.awt.Container.getComponent(Unknown Source)
at com.jidesoft.swing.JideSplitPane.setDividersVisible(Unknown Source)
at com.jidesoft.swing.JideSplitPane.componentHidden(Unknown Source)
at java.awt.Component.processComponentEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
FactoryPMI v3.3.2 (build 2754)
Java: Sun Microsystems Inc. 1.6.0_14

Is there a way to resolve this problem?

I’m having a similar error… not sure if they’re related. Mine is:

FailedDownloadException: Unable to load resource: 127.0.0.1:8080/gateway/designer/designer.jnlp

java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at java.io.FilterInputStream.read(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at com.sun.deploy.net.HttpDownloadHelper.download(Unknown Source)
at com.sun.deploy.cache.Cache.downloadResourceToTempFile(Unknown Source)
at com.sun.deploy.cache.Cache.downloadResourceToCache(Unknown Source)
at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getResource(Unknown Source)
at com.sun.deploy.net.DownloadEngine.getResource(Unknown Source)
at com.sun.javaws.LaunchDownload.getUpdatedLaunchDesc(Unknown Source)
at com.sun.javaws.Launcher.updateFinalLaunchDesc(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.launch(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Okay, lets see here. The first error:

java.lang.ArrayIndexOutOfBoundsException: No such child: 2

is a known issue with recent versions of Java 6 (update 12 and up, iirc). It is totally harmless and will be fixed in the next major release.

The secoind issue:

FailedDownloadException: Unable to load resource: http://127.0.0.1:8080/gateway/designer/designer.jnlp java.net.SocketException: Connection reset

is not similar to the first. I don’t know what would give you that impression. Anyhow, this seems like a networking error. Check the FactoryPMI logs (usually in C:\Program Files\Inductive Automation\FactoryPMI\logs) to look for anything unusual.

Hope this helps,

Regarding the first error (no such child), by major release do you mean some 3.x version, or the next version that is now in the beta state (v4.x?)? I know it’s harmless, but the IT guys I’m training don’t like to see it. But if it’s a Java problem, I’ll just tell as much and that FPMI is catching it.

No, I meant v4. I know its a bit embarassing, sorry. It’s caused by the docking framework used in version 3, combined with later releases of Java 6.