facebook

unable to open firebird db connection

  1. MyEclipse Archived
  2.  > 
  3. Database Tools (DB Explorer, Hibernate, etc.)
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #287903 Reply

    KIG
    Participant

    Hi,

    I faced a strange behaviour with myeclipse 6.5. I’ve created a new firebird db connection, opened it and performed the hibernate reverse engineering. Everything worked fine. After a while I’m unable to open the firebird connection but no error is reported. When I edit the connection the button “Test cn” says also successful. In my application the firebird database is still working, so the problem is limited to the db explorer.

    I’m using jaybird 2.16 and Firebird 2.1.

    In the log I can see the following error:

    !ENTRY org.eclipse.ui 4 0 2008-08-04 09:09:11.671
    !MESSAGE Unhandled event loop exception
    !STACK 0
    java.lang.NoClassDefFoundError
    at com.genuitec.eclipse.sqlexplorer.edittable.TableEditUtil.getDialect(TableEditUtil.java:217)
    at com.genuitec.eclipse.sqlexplorer.edittable.TableEditUtil.addSchemas(TableEditUtil.java:570)
    at com.genuitec.eclipse.sqlexplorer.wizards.ConnectionProfileWizardSchemaPage$5.widgetSelected(ConnectionProfileWizardSchemaPage.java:211)

    With an older myeclipse version 6.0 the connection can still be opened.

    How can I solve the problem in myeclipse 6.5?

    Thanks in advance,

    Klaus

    #287913 Reply

    Loyal Water
    Member

    Klaus,
    Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

    Can you paste the entire error message that gets recorded under <workspace>/.metadata/.log file.

    #287915 Reply

    KIG
    Participant

    attached, please find the summary

    *** Date:
    Montag, 4. August 2008 14.06 Uhr CEST

    ** System properties:
    OS=WindowsXP
    OS version=5.1
    Java version=1.5.0_15

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 6.5.0 GA
    Build id: 6.5.0-GA-20080609

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 6.5.0 GA
    Build id: 6.5.0-GA-20080609

    Eclipse Project SDK

    Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
    Build id: M20080221-1800

    Eclipse Platform

    Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
    Build id: M20080221-1800

    Eclipse Java Development Tools

    Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
    Build id: M20080221-1800

    Eclipse Graphical Editing Framework

    Version: 3.3.2.v20080129
    Build id: 20080221-1602

    Eclipse RCP

    Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
    Build id: M20080221-1800

    Eclipse Plug-in Development Environment

    Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
    Build id: M20080221-1800

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -showsplash
    -launcher
    C:\Program Files\MyEclipse 6.5\eclipse.exe
    -name
    Eclipse
    –launcher.library
    C:\Program Files\MyEclipse 6.5\../Pulse\Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
    -startup
    C:\Program Files\MyEclipse 6.5\../Pulse\Common\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
    -exitdata
    14f0_7c
    -configuration
    ../../../configuration
    -clean
    -configuration
    C:\Program Files\MyEclipse 6.5\configuration
    -vm
    C:\Program Files\Pulse\Common\binary\com.sun.java.jre.win32.x86_1.5.0.015\bin\javaw.exe

    The .log file contains only the following lines. So the previously reported exception has probably nothing to do with my exception:

    !SESSION 2008-08-04 14:16:23.914 ———————————————–
    eclipse.buildId=M20080221-1800
    java.version=1.5.0_15
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
    Command-line arguments: -os win32 -ws win32 -arch x86 -clean

    !ENTRY org.eclipse.jface 2 0 2008-08-04 14:17:22.584
    !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
    !SUBENTRY 1 org.eclipse.jface 2 0 2008-08-04 14:17:22.584
    !MESSAGE A conflict occurred for ALT+CTRL+J:
    Binding(ALT+CTRL+J,
    ParameterizedCommand(Command(org.eclipse.ui.edit.text.join.lines,Join Lines,
    Join lines of text,
    Category(org.eclipse.ui.category.textEditor,Text Editing,Text Editing Commands,true),
    ,
    ,,true),null),
    org.eclipse.ui.defaultAcceleratorConfiguration,
    org.eclipse.ui.textEditorScope,,,system)
    Binding(ALT+CTRL+J,
    ParameterizedCommand(Command(com.cloudgarden.jigloo.commands.openJiglooPrefs,Open Jigloo Preferences Page,
    Open Jigloo Preferences Page,
    Category(com.cloudgarden.jigloo.actions.category,Jigloo,Jigloo Actions,true),
    LegacyHandlerWrapper(ActionHandler(action=org.eclipse.ui.internal.EditorPluginAction@18f9ba9)),
    ,,true),null),
    org.eclipse.ui.defaultAcceleratorConfiguration,
    org.eclipse.ui.textEditorScope,,,system)

    #287972 Reply

    Loyal Water
    Member

    Are you using the same version of Firebird and the same driver on both versions of MyEclipse? Can you try another version of the driver.

    #288001 Reply

    KIG
    Participant

    Yes, I’m using jaybird 2.16 and Firebird 2.1in both MyEclipse environments. When I start a new Project in MyEclipse 6.5 I’m able to open the firebird connection. After a reboot of myeclipse it won’t work any longer. I did also a fresh installation of myeclipse 6.5 and faced the same behaviour.

    #288004 Reply

    KIG
    Participant

    the problem is solved. After installing the latest update for eclipse the db connections are working. Of course, the reason or incompatibility isn’t clear at all but thanks for your assistence

    #288022 Reply

    Loyal Water
    Member

    Glad you resolved the issue. Thanks for letting me know.

Viewing 7 posts - 1 through 7 (of 7 total)
Reply To: unable to open firebird db connection

This topic is marked as closed to new replies, however your posting capabilities still allow you to do so.

You must be logged in to post in the forum log in