Re: one last Eclipse mystery... can't connect to any database.
Re: one last Eclipse mystery... can't connect to any database.
- Subject: Re: one last Eclipse mystery... can't connect to any database.
- From: Tim Worman <email@hidden>
- Date: Mon, 16 Jul 2012 11:18:11 -0700
I also did a fresh install yesterday and haven't had any problems connecting to mysql. This doesn't sound like an eclipse or wolips problem since those aren't involved in your actual database connection.
Most likely you have a overridden db connection property that is not correct in your development environment. FWIW, when I connect to local MySQL databases, I use 127.0.0.1.
Tim
UCLA GSE&IS
On Jul 16, 2012, at 10:18 AM, George Domurot <email@hidden> wrote:
> We've done several fresh installs recently, without issue. However, we did create fresh workspaces. Not sure if that matters, but it might be worth a try to create a new workspace, import, run and test.
>
> Also, we are using Eclipse Indigo Service Release 2 with latest WOLips.
>
> -G
>
> On Jul 16, 2012, at 9:57 AM, Pascal Robert wrote:
>
>>
>> Le 2012-07-16 à 12:47, James Cicenia a écrit :
>>
>>> I can access my mysql database from command line and Navicat. My built app works on the server. I have changed workspaces. Still Eclipse won't let me connect to any mysql database be it local or remote.
>>>
>>> I am using the latest wolips and eclipse 3.7.2.
>>>
>>> I guess I will try another Golips install.
>>
>> I don't think it's going to change your problem. Do you have the JDBC driver in the class path?
>>
>>> Meanwhile, is there something to see if Eclipse is allowed to access the 3306 port?
>>
>> Beside having the JDBC driver is your class path, no. If port 3306 was blocked, you wouldn't be able to access it by the command line client and Navicat.
>>
>>> Thanks
>>> James
>>>
>>>
>>>
>>> On Mon, Jul 16, 2012 at 9:38 AM, G Brown <email@hidden> wrote:
>>> One thing I discovered: You should discard eclipse workspaces when things don't work. I had an eclipse workspace since the Flood (Noah's) , and in that old one some things don't work. If I create a new workspace, and add projects to the new workspace, then things work. I think it will be standard best practice for me to change workspaces with each version of eclipse, or when things don't work.
>>>
>>>
>>> On Jul 14, 2012, at 1:43 PM, James Cicenia wrote:
>>>
>>>> Hello -
>>>>
>>>> I am having another head scratching mystery. No matter what I do, no matter the database, no matter the credentials entered and no matter whether the database is local or remote, WO won't connect to the database. I can connect to all databases using Navicat just fine. This only effects my Eclipse and not my deployed apps. Is there another obscure switch in Eclipse?
>>>>
>>>> Thanks
>>>> James
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>
>>
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden