Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » DTP » "Unsupported" folder/profiles, NullPointerException connecting ...
"Unsupported" folder/profiles, NullPointerException connecting ... [message #38962] Tue, 20 November 2007 05:24 Go to next message
Eclipse UserFriend
Originally posted by: paul.n.woods.gmail.com

Hope this is the correct place to post this - sorry if not.

Two days ago I'm using the Database Development perspective with Eclipse
3.3 quite happily with HSQLDB, shut it down, and the next day come back
to work. Upon loading the Database Perspective, a see a new folder in
the Data Source Explorer window, titled "Unsupported". The connection I
was previously using is listed there, and unusable.

I create a new profile and connection, everything the same, and go to
work. Eventually, the "unsupported" profile suddenly appears underneath
the "Databases" folder with the new one - now working.

Today, I have the same issue, except that now I cannot do anything to get
a valid connection. Trying to ping or open the old one in the unsupported
folder gives me a NullPointerException.

Eclipse 3.3.2
Data Tools Platform 1.5.1.200709261
Java 1.6.0_03 on the latest Ubuntu


These are from my log file (the top one is from Eclipse startup I
believe ...):

!ENTRY org.eclipse.datatools.connectivity 4 10001 2007-11-20 04:54:00.025
!MESSAGE assertion failed: Parsing error: invalid attribute
( org.eclipse.core.internal.registry.ConfigurationElementHandl e @23db)
!STACK 0
org.eclipse.core.runtime.AssertionFailedException: assertion failed:
Parsing error: invalid attribute
( org.eclipse.core.internal.registry.ConfigurationElementHandl e @23db)
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:109)
at
org.eclipse.datatools.connectivity.internal.ConnectionProfil eManager.processExtensions
(ConnectionProfileManager.java:171)
at
org.eclipse.datatools.connectivity.internal.ConnectionProfil eManager.getProviders
(ConnectionProfileManager.java:91)
at
org.eclipse.datatools.connectivity.internal.ConnectionProfil eManager.getProvider
(ConnectionProfileManager.java:96)
at
org.eclipse.datatools.connectivity.internal.ConnectionProfil e. <init>
(ConnectionProfile.java:102)
at
org.eclipse.datatools.connectivity.internal.ConnectionProfil eMgmt.readCPsFromXML1_0
(ConnectionProfileMgmt.java:527)
at
org.eclipse.datatools.connectivity.internal.ConnectionProfil eMgmt.loadCPs
(ConnectionProfileMgmt.java:690)
at
org.eclipse.datatools.connectivity.internal.ConnectionProfil eMgmt.loadCPs
(ConnectionProfileMgmt.java:474)
at
org.eclipse.datatools.connectivity.internal.InternalProfileM anager.loadProfiles
(InternalProfileManager.java:785)
at
org.eclipse.datatools.connectivity.internal.InternalProfileM anager.getProfiles
(InternalProfileManager.java:117)
at
org.eclipse.datatools.connectivity.internal.InternalProfileM anager.getProfileByName
(InternalProfileManager.java:192)
at
org.eclipse.datatools.connectivity.ProfileManager.getProfile ByName
(ProfileManager.java:92)
at
org.eclipse.datatools.sqltools.core.profile.ProfileUtil.getP rofile
(ProfileUtil.java:225)
at
org.eclipse.datatools.sqltools.core.profile.ProfileUtil.getD atabaseVendorDefinitionId
(ProfileUtil.java:275)
at
org.eclipse.datatools.sqltools.core.profile.ProfileUtil.getD atabaseVendorDefinitionId
(ProfileUtil.java:263)
at
org.eclipse.datatools.sqltools.sqleditor.SQLEditorConnection Info. <init>
(SQLEditorConnectionInfo.java:85)
at
org.eclipse.datatools.sqltools.sqleditor.SQLEditorConnection Info.decode
(SQLEditorConnectionInfo.java:200)
at
org.eclipse.datatools.sqltools.internal.sqlscrapbook.util.SQ LFileUtil.getConnectionInfo
(SQLFileUtil.java:35)
at
org.eclipse.datatools.sqltools.internal.sqlscrapbook.editor. SQLScrapbookEditorInput. <init>
(SQLScrapbookEditorInput.java:49)
at
org.eclipse.datatools.sqltools.internal.sqlscrapbook.editor. SQLScrapbookEditorInputFactory.createElement
(SQLScrapbookEditorInputFactory.java:61)
at org.eclipse.ui.internal.EditorReference.getRestoredInput
(EditorReference.java:361)
at org.eclipse.ui.internal.EditorReference.getEditorInput
(EditorReference.java:324)
at org.eclipse.jst.jsf.designtime.internal.jsp.StartupHandler
$JSPEditorListener.getIFile(StartupHandler.java:192)
at org.eclipse.jst.jsf.designtime.internal.jsp.StartupHandler
$JSPEditorListener.isValidJSPEditor(StartupHandler.java:152)
at org.eclipse.jst.jsf.designtime.internal.jsp.StartupHandler
$1.run(StartupHandler.java:62)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages
(Synchronizer.java:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages
(Display.java:3296)
at org.eclipse.swt.widgets.Display.readAndDispatch
(Display.java:2974)
at org.eclipse.ui.internal.Workbench.runEventLoop
(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 19)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault
(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench
(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench
(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start
(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run
(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication
(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start
(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:176)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework
(Main.java:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)

!ENTRY org.eclipse.core.jobs 4 2 2007-11-20 05:01:21.432
!MESSAGE An internal error occurred during: "Ping server job".
!STACK 0
java.lang.NullPointerException
at
org.eclipse.datatools.connectivity.internal.ConnectionProfil e.createConnection
(ConnectionProfile.java:354)
at org.eclipse.datatools.connectivity.ui.PingJob.run
(PingJob.java:57)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY org.eclipse.core.jobs 4 2 2007-11-20 05:03:42.886
!MESSAGE An internal error occurred during: "Ping server job".
!STACK 0
java.lang.NullPointerException
at
org.eclipse.datatools.connectivity.internal.ConnectionProfil e.createConnection
(ConnectionProfile.java:354)
at org.eclipse.datatools.connectivity.ui.PingJob.run
(PingJob.java:57)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)



Any and all ideas appreciated, thanks.

Paul
Re: "Unsupported" folder/profiles, NullPointerException connecting ... [message #39276 is a reply to message #38962] Wed, 28 November 2007 19:51 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: john.graham.sybase.com

Paul,

In this case one or more extensions for database support is not being
parsed by the platform. This would explain why you had HSQLDB support at
one time, and then later not. Now, why this is happening is not
immediately clear to me. Based on the log entries, it appears that the
extension declaration in the HSQLDB support plug-in is somehow corrupted
(or believed to be corrupted by the platform extension loader)...

Some questions/observations:
1. Eclipse 3.3.2? Is this a nightly build of the 3.3.2 stream? DTP 1.5.1
was built on Eclipse 3.3.1.1. Not sure that this will make a difference.
If possible, switch to Eclipse 3.3.1.1 instead.

2. Our primary VM level is 1.5, though we've done some testing on 1.6.
We've also tested with Ubuntu along the way, but neither Ubuntu nor 1.6 VM
are our primary test environment. If possible, try using a 1.5 VM and see
if that makes any difference.

It would be also useful if you could file a bug report for this issue, so
we can try to track it further.

HTH,
John Graham
Eclipse Data Tools Platform PMC Chair

Paul wrote:

> Hope this is the correct place to post this - sorry if not.

> Two days ago I'm using the Database Development perspective with Eclipse
> 3.3 quite happily with HSQLDB, shut it down, and the next day come back
> to work. Upon loading the Database Perspective, a see a new folder in
> the Data Source Explorer window, titled "Unsupported". The connection I
> was previously using is listed there, and unusable.

> I create a new profile and connection, everything the same, and go to
> work. Eventually, the "unsupported" profile suddenly appears underneath
> the "Databases" folder with the new one - now working.

> Today, I have the same issue, except that now I cannot do anything to get
> a valid connection. Trying to ping or open the old one in the unsupported
> folder gives me a NullPointerException.

> Eclipse 3.3.2
> Data Tools Platform 1.5.1.200709261
> Java 1.6.0_03 on the latest Ubuntu


> These are from my log file (the top one is from Eclipse startup I
> believe ...):

> !ENTRY org.eclipse.datatools.connectivity 4 10001 2007-11-20 04:54:00.025
> !MESSAGE assertion failed: Parsing error: invalid attribute
> ( org.eclipse.core.internal.registry.ConfigurationElementHandl e @23db)
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> Parsing error: invalid attribute
> ( org.eclipse.core.internal.registry.ConfigurationElementHandl e @23db)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:109)
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil eManager.processExtensions
> (ConnectionProfileManager.java:171)
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil eManager.getProviders
> (ConnectionProfileManager.java:91)
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil eManager.getProvider
> (ConnectionProfileManager.java:96)
> at
> org.eclipse.datatools.connectivity.internal.ConnectionProfil e. <init>
> (ConnectionProfile.java:102)
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil eMgmt.readCPsFromXML1_0
> (ConnectionProfileMgmt.java:527)
> at
> org.eclipse.datatools.connectivity.internal.ConnectionProfil eMgmt.loadCPs
> (ConnectionProfileMgmt.java:690)
> at
> org.eclipse.datatools.connectivity.internal.ConnectionProfil eMgmt.loadCPs
> (ConnectionProfileMgmt.java:474)
> at
>
org.eclipse.datatools.connectivity.internal.InternalProfileM anager.loadProfiles
> (InternalProfileManager.java:785)
> at
>
org.eclipse.datatools.connectivity.internal.InternalProfileM anager.getProfiles
> (InternalProfileManager.java:117)
> at
>
org.eclipse.datatools.connectivity.internal.InternalProfileM anager.getProfileByName
> (InternalProfileManager.java:192)
> at
> org.eclipse.datatools.connectivity.ProfileManager.getProfile ByName
> (ProfileManager.java:92)
> at
> org.eclipse.datatools.sqltools.core.profile.ProfileUtil.getP rofile
> (ProfileUtil.java:225)
> at
>
org.eclipse.datatools.sqltools.core.profile.ProfileUtil.getD atabaseVendorDefinitionId
> (ProfileUtil.java:275)
> at
>
org.eclipse.datatools.sqltools.core.profile.ProfileUtil.getD atabaseVendorDefinitionId
> (ProfileUtil.java:263)
> at
> org.eclipse.datatools.sqltools.sqleditor.SQLEditorConnection Info. <init>
> (SQLEditorConnectionInfo.java:85)
> at
> org.eclipse.datatools.sqltools.sqleditor.SQLEditorConnection Info.decode
> (SQLEditorConnectionInfo.java:200)
> at
>
org.eclipse.datatools.sqltools.internal.sqlscrapbook.util.SQ LFileUtil.getConnectionInfo
> (SQLFileUtil.java:35)
> at
>
org.eclipse.datatools.sqltools.internal.sqlscrapbook.editor. SQLScrapbookEditorInput. <init>
> (SQLScrapbookEditorInput.java:49)
> at
>
org.eclipse.datatools.sqltools.internal.sqlscrapbook.editor. SQLScrapbookEditorInputFactory.createElement
> (SQLScrapbookEditorInputFactory.java:61)
> at org.eclipse.ui.internal.EditorReference.getRestoredInput
> (EditorReference.java:361)
> at org.eclipse.ui.internal.EditorReference.getEditorInput
> (EditorReference.java:324)
> at org.eclipse.jst.jsf.designtime.internal.jsp.StartupHandler
> $JSPEditorListener.getIFile(StartupHandler.java:192)
> at org.eclipse.jst.jsf.designtime.internal.jsp.StartupHandler
> $JSPEditorListener.isValidJSPEditor(StartupHandler.java:152)
> at org.eclipse.jst.jsf.designtime.internal.jsp.StartupHandler
> $1.run(StartupHandler.java:62)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages
> (Synchronizer.java:123)
> at org.eclipse.swt.widgets.Display.runAsyncMessages
> (Display.java:3296)
> at org.eclipse.swt.widgets.Display.readAndDispatch
> (Display.java:2974)
> at org.eclipse.ui.internal.Workbench.runEventLoop
> (Workbench.java:2389)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 19)
> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault
> (Realm.java:289)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench
> (Workbench.java:461)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench
> (PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start
> (IDEApplication.java:106)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run
> (EclipseAppHandle.java:169)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication
> (EclipseAppLauncher.java:106)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start
> (EclipseAppLauncher.java:76)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run
> (EclipseStarter.java:363)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run
> (EclipseStarter.java:176)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework
> (Main.java:508)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1173)

> !ENTRY org.eclipse.core.jobs 4 2 2007-11-20 05:01:21.432
> !MESSAGE An internal error occurred during: "Ping server job".
> !STACK 0
> java.lang.NullPointerException
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil e.createConnection
> (ConnectionProfile.java:354)
> at org.eclipse.datatools.connectivity.ui.PingJob.run
> (PingJob.java:57)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

> !ENTRY org.eclipse.core.jobs 4 2 2007-11-20 05:03:42.886
> !MESSAGE An internal error occurred during: "Ping server job".
> !STACK 0
> java.lang.NullPointerException
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil e.createConnection
> (ConnectionProfile.java:354)
> at org.eclipse.datatools.connectivity.ui.PingJob.run
> (PingJob.java:57)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)



> Any and all ideas appreciated, thanks.

> Paul
Re: "Unsupported" folder/profiles, NullPointerException connecting ... [message #39494 is a reply to message #39276] Sat, 01 December 2007 22:29 Go to previous message
Eclipse UserFriend
Originally posted by: paul.n.woods.gmail.com

John - thanks for the reply, and the notes.

I didn't pay that close attention the version I was using, I'm not sure
how I managed to install 3.3.2. I re-installed eclipse from a fresh
download, and upon doing the updates again, I am at 3.3.1.1 now.
Between 3.3.1.1 and the fresh install of DTP, everything seems to be
working okay.

I am still using Suns 1.6 VM. If I find I still have issues, I might try
1.5.


Thanks again,

Paul
Re: "Unsupported" folder/profiles, NullPointerException connecting ... [message #588777 is a reply to message #38962] Wed, 28 November 2007 19:51 Go to previous message
John Graham is currently offline John GrahamFriend
Messages: 183
Registered: July 2009
Senior Member
Paul,

In this case one or more extensions for database support is not being
parsed by the platform. This would explain why you had HSQLDB support at
one time, and then later not. Now, why this is happening is not
immediately clear to me. Based on the log entries, it appears that the
extension declaration in the HSQLDB support plug-in is somehow corrupted
(or believed to be corrupted by the platform extension loader)...

Some questions/observations:
1. Eclipse 3.3.2? Is this a nightly build of the 3.3.2 stream? DTP 1.5.1
was built on Eclipse 3.3.1.1. Not sure that this will make a difference.
If possible, switch to Eclipse 3.3.1.1 instead.

2. Our primary VM level is 1.5, though we've done some testing on 1.6.
We've also tested with Ubuntu along the way, but neither Ubuntu nor 1.6 VM
are our primary test environment. If possible, try using a 1.5 VM and see
if that makes any difference.

It would be also useful if you could file a bug report for this issue, so
we can try to track it further.

HTH,
John Graham
Eclipse Data Tools Platform PMC Chair

Paul wrote:

> Hope this is the correct place to post this - sorry if not.

> Two days ago I'm using the Database Development perspective with Eclipse
> 3.3 quite happily with HSQLDB, shut it down, and the next day come back
> to work. Upon loading the Database Perspective, a see a new folder in
> the Data Source Explorer window, titled "Unsupported". The connection I
> was previously using is listed there, and unusable.

> I create a new profile and connection, everything the same, and go to
> work. Eventually, the "unsupported" profile suddenly appears underneath
> the "Databases" folder with the new one - now working.

> Today, I have the same issue, except that now I cannot do anything to get
> a valid connection. Trying to ping or open the old one in the unsupported
> folder gives me a NullPointerException.

> Eclipse 3.3.2
> Data Tools Platform 1.5.1.200709261
> Java 1.6.0_03 on the latest Ubuntu


> These are from my log file (the top one is from Eclipse startup I
> believe ...):

> !ENTRY org.eclipse.datatools.connectivity 4 10001 2007-11-20 04:54:00.025
> !MESSAGE assertion failed: Parsing error: invalid attribute
> ( org.eclipse.core.internal.registry.ConfigurationElementHandl e @23db)
> !STACK 0
> org.eclipse.core.runtime.AssertionFailedException: assertion failed:
> Parsing error: invalid attribute
> ( org.eclipse.core.internal.registry.ConfigurationElementHandl e @23db)
> at org.eclipse.core.runtime.Assert.isTrue(Assert.java:109)
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil eManager.processExtensions
> (ConnectionProfileManager.java:171)
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil eManager.getProviders
> (ConnectionProfileManager.java:91)
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil eManager.getProvider
> (ConnectionProfileManager.java:96)
> at
> org.eclipse.datatools.connectivity.internal.ConnectionProfil e. <init>
> (ConnectionProfile.java:102)
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil eMgmt.readCPsFromXML1_0
> (ConnectionProfileMgmt.java:527)
> at
> org.eclipse.datatools.connectivity.internal.ConnectionProfil eMgmt.loadCPs
> (ConnectionProfileMgmt.java:690)
> at
> org.eclipse.datatools.connectivity.internal.ConnectionProfil eMgmt.loadCPs
> (ConnectionProfileMgmt.java:474)
> at
>
org.eclipse.datatools.connectivity.internal.InternalProfileM anager.loadProfiles
> (InternalProfileManager.java:785)
> at
>
org.eclipse.datatools.connectivity.internal.InternalProfileM anager.getProfiles
> (InternalProfileManager.java:117)
> at
>
org.eclipse.datatools.connectivity.internal.InternalProfileM anager.getProfileByName
> (InternalProfileManager.java:192)
> at
> org.eclipse.datatools.connectivity.ProfileManager.getProfile ByName
> (ProfileManager.java:92)
> at
> org.eclipse.datatools.sqltools.core.profile.ProfileUtil.getP rofile
> (ProfileUtil.java:225)
> at
>
org.eclipse.datatools.sqltools.core.profile.ProfileUtil.getD atabaseVendorDefinitionId
> (ProfileUtil.java:275)
> at
>
org.eclipse.datatools.sqltools.core.profile.ProfileUtil.getD atabaseVendorDefinitionId
> (ProfileUtil.java:263)
> at
> org.eclipse.datatools.sqltools.sqleditor.SQLEditorConnection Info. <init>
> (SQLEditorConnectionInfo.java:85)
> at
> org.eclipse.datatools.sqltools.sqleditor.SQLEditorConnection Info.decode
> (SQLEditorConnectionInfo.java:200)
> at
>
org.eclipse.datatools.sqltools.internal.sqlscrapbook.util.SQ LFileUtil.getConnectionInfo
> (SQLFileUtil.java:35)
> at
>
org.eclipse.datatools.sqltools.internal.sqlscrapbook.editor. SQLScrapbookEditorInput. <init>
> (SQLScrapbookEditorInput.java:49)
> at
>
org.eclipse.datatools.sqltools.internal.sqlscrapbook.editor. SQLScrapbookEditorInputFactory.createElement
> (SQLScrapbookEditorInputFactory.java:61)
> at org.eclipse.ui.internal.EditorReference.getRestoredInput
> (EditorReference.java:361)
> at org.eclipse.ui.internal.EditorReference.getEditorInput
> (EditorReference.java:324)
> at org.eclipse.jst.jsf.designtime.internal.jsp.StartupHandler
> $JSPEditorListener.getIFile(StartupHandler.java:192)
> at org.eclipse.jst.jsf.designtime.internal.jsp.StartupHandler
> $JSPEditorListener.isValidJSPEditor(StartupHandler.java:152)
> at org.eclipse.jst.jsf.designtime.internal.jsp.StartupHandler
> $1.run(StartupHandler.java:62)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages
> (Synchronizer.java:123)
> at org.eclipse.swt.widgets.Display.runAsyncMessages
> (Display.java:3296)
> at org.eclipse.swt.widgets.Display.readAndDispatch
> (Display.java:2974)
> at org.eclipse.ui.internal.Workbench.runEventLoop
> (Workbench.java:2389)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 19)
> at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault
> (Realm.java:289)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench
> (Workbench.java:461)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench
> (PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start
> (IDEApplication.java:106)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run
> (EclipseAppHandle.java:169)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication
> (EclipseAppLauncher.java:106)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start
> (EclipseAppLauncher.java:76)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run
> (EclipseStarter.java:363)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run
> (EclipseStarter.java:176)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework
> (Main.java:508)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1173)

> !ENTRY org.eclipse.core.jobs 4 2 2007-11-20 05:01:21.432
> !MESSAGE An internal error occurred during: "Ping server job".
> !STACK 0
> java.lang.NullPointerException
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil e.createConnection
> (ConnectionProfile.java:354)
> at org.eclipse.datatools.connectivity.ui.PingJob.run
> (PingJob.java:57)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

> !ENTRY org.eclipse.core.jobs 4 2 2007-11-20 05:03:42.886
> !MESSAGE An internal error occurred during: "Ping server job".
> !STACK 0
> java.lang.NullPointerException
> at
>
org.eclipse.datatools.connectivity.internal.ConnectionProfil e.createConnection
> (ConnectionProfile.java:354)
> at org.eclipse.datatools.connectivity.ui.PingJob.run
> (PingJob.java:57)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)



> Any and all ideas appreciated, thanks.

> Paul
Re: "Unsupported" folder/profiles, NullPointerException connecting ... [message #588852 is a reply to message #39276] Sat, 01 December 2007 22:29 Go to previous message
Paul is currently offline PaulFriend
Messages: 55
Registered: July 2009
Member
John - thanks for the reply, and the notes.

I didn't pay that close attention the version I was using, I'm not sure
how I managed to install 3.3.2. I re-installed eclipse from a fresh
download, and upon doing the updates again, I am at 3.3.1.1 now.
Between 3.3.1.1 and the fresh install of DTP, everything seems to be
working okay.

I am still using Suns 1.6 VM. If I find I still have issues, I might try
1.5.


Thanks again,

Paul
Previous Topic:Reverse Engineering for PostgreSQL
Next Topic:generic JDBC is unsupported
Goto Forum:
  


Current Time: Fri Dec 19 10:06:09 GMT 2014

Powered by FUDForum. Page generated in 0.02240 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software