|
Re: Problem with database connection (postgresql) [message #509855 is a reply to message #509653] |
Mon, 25 January 2010 15:33 |
|
Christoph,
Where are you putting the postgresql driver at?
Jason
Christoph Eiden wrote:
> Hi all,
>
> I downloaded the BIRT all-in-one package 2.5.1 and the latest jdbc4
> driver for postgresql from http://jdbc.postgresql.org/ Unfortunately
> I'm not able to connect to my database; when I click 'Test connection' I
> get this error:
>
> Quote:
>> org.eclipse.birt.report.data.oda.jdbc.JDBCException: There is an error
>> in get connection, Der Verbindungsversuch schlug fehl..
>> at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.doCo
>> nnect(JDBCDriverManager.java:262)
>> at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.getC
>> onnection(JDBCDriverManager.java:186)
>> at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.tryC
>> reateConnection(JDBCDriverManager.java:706)
>> at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.test
>> Connection(JDBCDriverManager.java:612)
>> at org.eclipse.birt.report.data.oda.jdbc.ui.util.DriverLoader.t
>> estConnection(DriverLoader.java:120)
>> at org.eclipse.birt.report.data.oda.jdbc.ui.util.DriverLoader.t
>> estConnection(DriverLoader.java:133)
>> at org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelecti
>> onPageHelper.testConnection(JDBCSelectionPageHelper.java:653 )
>> at org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelecti
>> onPageHelper.access$7(JDBCSelectionPageHelper.java:627)
>> at org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelecti
>> onPageHelper$7.widgetSelected(JDBCSelectionPageHelper.java:5 49)
>> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe
>> ner.java:228)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
>> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja
>> va:3493)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java
>> :3112)
>> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825 )
>> at org.eclipse.jface.window.Window.open(Window.java:801)
>> at org.eclipse.birt.report.designer.ui.dialogs.BaseDialog.open(
>> BaseDialog.java:110)
>> at org.eclipse.birt.report.designer.data.ui.providers.EditableD
>> ataSourceNodeProvider.performEdit(EditableDataSourceNodeProv
>> ider.java:72)
>> at org.eclipse.birt.report.designer.internal.ui.views.DefaultNo
>> deProvider.performRequest(DefaultNodeProvider.java:426)
>> at org.eclipse.birt.report.designer.internal.ui.views.actions.E
>> ditAction.doAction(EditAction.java:90)
>> at org.eclipse.birt.report.designer.internal.ui.views.actions.A
>> bstractElementAction.run(AbstractElementAction.java:70)
>> at org.eclipse.birt.report.designer.internal.ui.views.RenameLis
>> tener.doubleClick(RenameListener.java:214)
>> at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredV
>> iewer.java:821)
>> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>> at org.eclipse.core.runtime.Platform.run(Platform.java:888)
>> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
>> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:17 5)
>> at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(S
>> tructuredViewer.java:819)
>> at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSel
>> ect(AbstractTreeViewer.java:1419)
>> at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSe
>> lected(StructuredViewer.java:1195)
>> at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEven
>> t(OpenStrategy.java:238)
>> at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.ja
>> va:235)
>> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrate
>> gy.java:296)
>> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
>> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
>> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja
>> va:3493)
>> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java
>> :3112)
>> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav
>> a:2405)
>> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
>> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
>> at org.eclipse.core.databinding.observable.Realm.runWithDefault
>> (Realm.java:332)
>> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work
>> bench.java:493)
>> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j
>> ava:149)
>> at org.eclipse.ui.internal.ide.application.IDEApplication.start
>> (IDEApplication.java:113)
>> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips
>> eAppHandle.java:194)
>> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher
>> .runApplication(EclipseAppLauncher.java:110)
>> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher
>> .start(EclipseAppLauncher.java:79)
>> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS
>> tarter.java:368)
>> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS
>> tarter.java:179)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>> ssorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>> thodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
>> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
>> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>
>
> I'm using BIRT on Debian Squeeze with Postgresql 8.4.1. I can connect to
> the database on the command line and with pgadmin.
>
> All help on this issue is much appreciated.
>
> Christoph
|
|
|
Re: Problem with database connection (postgresql) [message #509928 is a reply to message #509855] |
Mon, 25 January 2010 19:20 |
Christoph Eiden Messages: 4 Registered: January 2010 |
Junior Member |
|
|
Jason,
I put the driver into a separate folder (jdbc_driver/) in my home directory and add it using the manage driver dialog when I create a data source.
Eclipse is installed in my home directory (eclipse/) as well.
The driver is copied to the directory ~/eclipse/plugins/org.eclipse.birt.report.data.oda.jdbc_2.5. 1.v20090821/drivers/ ahen adding it.
Thanks,
Christoph
[Updated on: Tue, 26 January 2010 06:07] Report message to a moderator
|
|
|
Re: Problem with database connection (postgresql) [message #510473 is a reply to message #509928] |
Wed, 27 January 2010 10:32 |
|
Christoph,
Can you verify the driver is no where else in your classpath.
Also can you open a bug for this?
Jason
Christoph Eiden wrote:
> Jason,
>
> I put the driver into a separate folder in my home directory and add it
> using the manage driver dialog when I create a data source.
>
> Eclipse is installed in my home directory as well.
>
> Thanks,
> Christoph
>
> Jason Weathersby wrote on Mon, 25 January 2010 16:33
>> Christoph,
>>
>> Where are you putting the postgresql driver at?
>>
>> Jason
>>
>> Christoph Eiden wrote:
>> > Hi all,
>> > > I downloaded the BIRT all-in-one package 2.5.1 and the latest
>> jdbc4 > driver for postgresql from http://jdbc.postgresql.org/
>> Unfortunately > I'm not able to connect to my database; when I click
>> 'Test connection' I > get this error:
>> > > Quote:
>> >> org.eclipse.birt.report.data.oda.jdbc.JDBCException: There is an
>> error >> in get connection, Der Verbindungsversuch schlug fehl..
>> >> at
>> org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.doCo >>
>> nnect(JDBCDriverManager.java:262)
>> >> at
>> org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.getC >>
>> onnection(JDBCDriverManager.java:186)
>> >> at
>> org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.tryC >>
>> reateConnection(JDBCDriverManager.java:706)
>> >> at
>> org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.test >>
>> Connection(JDBCDriverManager.java:612)
>> >> at
>> org.eclipse.birt.report.data.oda.jdbc.ui.util.DriverLoader.t >>
>> estConnection(DriverLoader.java:120)
>> >> at
>> org.eclipse.birt.report.data.oda.jdbc.ui.util.DriverLoader.t >>
>> estConnection(DriverLoader.java:133)
>> >> at
>> org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelecti >>
>> onPageHelper.testConnection(JDBCSelectionPageHelper.java:653 )
>> >> at
>> org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelecti >>
>> onPageHelper.access$7(JDBCSelectionPageHelper.java:627)
>> >> at
>> org.eclipse.birt.report.data.oda.jdbc.ui.profile.JDBCSelecti >>
>> onPageHelper$7.widgetSelected(JDBCSelectionPageHelper.java:5 49)
>> >> at
>> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListe >>
>> ner.java:228)
>> >> at
>> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
>> >> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
>> >> at
>> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja >> va:3493)
>> >> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java >> :3112)
>> >> at
>> org.eclipse.jface.window.Window.runEventLoop(Window.java:825 )
>> >> at org.eclipse.jface.window.Window.open(Window.java:801)
>> >> at
>> org.eclipse.birt.report.designer.ui.dialogs.BaseDialog.open( >>
>> BaseDialog.java:110)
>> >> at
>> org.eclipse.birt.report.designer.data.ui.providers.EditableD >>
>> ataSourceNodeProvider.performEdit(EditableDataSourceNodeProv >>
>> ider.java:72)
>> >> at
>> org.eclipse.birt.report.designer.internal.ui.views.DefaultNo >>
>> deProvider.performRequest(DefaultNodeProvider.java:426)
>> >> at
>> org.eclipse.birt.report.designer.internal.ui.views.actions.E >>
>> ditAction.doAction(EditAction.java:90)
>> >> at
>> org.eclipse.birt.report.designer.internal.ui.views.actions.A >>
>> bstractElementAction.run(AbstractElementAction.java:70)
>> >> at
>> org.eclipse.birt.report.designer.internal.ui.views.RenameLis >>
>> tener.doubleClick(RenameListener.java:214)
>> >> at
>> org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredV >>
>> iewer.java:821)
>> >> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>> >> at org.eclipse.core.runtime.Platform.run(Platform.java:888)
>> >> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
>> >> at
>> org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:17 5)
>> >> at
>> org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(S >>
>> tructuredViewer.java:819)
>> >> at
>> org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSel >>
>> ect(AbstractTreeViewer.java:1419)
>> >> at
>> org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSe >>
>> lected(StructuredViewer.java:1195)
>> >> at
>> org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEven >>
>> t(OpenStrategy.java:238)
>> >> at
>> org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.ja >> va:235)
>> >> at
>> org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrate >>
>> gy.java:296)
>> >> at
>> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :84)
>> >> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
>> >> at
>> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja >> va:3493)
>> >> at
>> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java >> :3112)
>> >> at
>> org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav >> a:2405)
>> >> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
>> >> at
>> org.eclipse.ui.internal.Workbench.access$4(Workbench.java:22 21)
>> >> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
>> >> at
>> org.eclipse.core.databinding.observable.Realm.runWithDefault >>
>> (Realm.java:332)
>> >> at
>> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work >>
>> bench.java:493)
>> >> at
>> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j >> ava:149)
>> >> at
>> org.eclipse.ui.internal.ide.application.IDEApplication.start >>
>> (IDEApplication.java:113)
>> >> at
>> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips >>
>> eAppHandle.java:194)
>> >> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher >>
>> .runApplication(EclipseAppLauncher.java:110)
>> >> at
>> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher >>
>> .start(EclipseAppLauncher.java:79)
>> >> at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS >>
>> tarter.java:368)
>> >> at
>> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS >>
>> tarter.java:179)
>> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce >>
>> ssorImpl.java:39)
>> >> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe >>
>> thodAccessorImpl.java:25)
>> >> at java.lang.reflect.Method.invoke(Method.java:597)
>> >> at
>> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 559)
>> >> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
>> >> at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
>> > > > I'm using BIRT on Debian Squeeze with Postgresql 8.4.1. I can
>> connect to > the database on the command line and with pgadmin.
>> > > All help on this issue is much appreciated.
>> > > Christoph
>
>
|
|
|
|
Re: Problem with database connection (postgresql) [message #513966 is a reply to message #511137] |
Thu, 11 February 2010 19:49 |
Christoph Eiden Messages: 4 Registered: January 2010 |
Junior Member |
|
|
Christoph Eiden <ceidix@googlemail.com> writes:
> Jason,
>
> Yes, I double-checked and the driver is nowhere else in my classpath.
>
> I'll open a bug on this issue.
>
> Thanks,
> Christoph
Hi all,
Just to close this issue, actually, it was caused by changes in Debian. I found a solution in message #505058:
,----
| Originally posted by: gunnar.stahl.gunnarstahl.org
|
| The problem was caused by a pretty unbelievable thing introduced in debian. Found out that java was no longer able to do any sort of network connections anymore. Even connections to localhost failed...
|
| Someone decided to introduce a ipv6-only switch in netbase via /etc/sysctl.d/bindv6only.conf. While this may or may not be a usefull default behaviour for the general the result is that java is no longer able to do networking at all.
|
| So to solve it you have to edit /etc/sysctl.d/bindv6only.conf and
| change the value of net.ipv6.bindv6only from "1" to "0". Then do a
| "sudo invoke-rc.d procps restart". After that, java has networking
| again.
|
| Found that solution on "http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560056".
`----
After following this, the connection works fine.
Regards,
Christoph
|
|
|
Re: Problem with database connection (postgresql) [message #513971 is a reply to message #513966] |
Thu, 11 February 2010 20:13 |
|
Thanks for adding this.
Christoph Eiden wrote:
> Christoph Eiden <ceidix@googlemail.com> writes:
>
>> Jason,
>>
>> Yes, I double-checked and the driver is nowhere else in my classpath.
>>
>> I'll open a bug on this issue.
>>
>> Thanks,
>> Christoph
>
> Hi all,
>
> Just to close this issue, actually, it was caused by changes in Debian. I found a solution in message #505058:
>
> ,----
> | Originally posted by: gunnar.stahl.gunnarstahl.org
> |
> | The problem was caused by a pretty unbelievable thing introduced in debian. Found out that java was no longer able to do any sort of network connections anymore. Even connections to localhost failed...
> |
> | Someone decided to introduce a ipv6-only switch in netbase via /etc/sysctl.d/bindv6only.conf. While this may or may not be a usefull default behaviour for the general the result is that java is no longer able to do networking at all.
> |
>
> | So to solve it you have to edit /etc/sysctl.d/bindv6only.conf and
> | change the value of net.ipv6.bindv6only from "1" to "0". Then do a
> | "sudo invoke-rc.d procps restart". After that, java has networking
> | again.
> |
> | Found that solution on "http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560056".
> `----
>
> After following this, the connection works fine.
>
> Regards,
> Christoph
|
|
|
Powered by
FUDForum. Page generated in 0.04676 seconds