gvSIG bugs #1906
Aplicación colgada al conectar a PostGIS
| Status: | Closed | % Done: | 0% | |
|---|---|---|---|---|
| Priority: | Normal | Spent time: | - | |
| Assignee: |  Juan Lucas Domínguez | |||
| Category: | - | |||
| Target version: | 2.1.0-2217-devel | |||
| Severity: | Add-on version: | |||
| gvSIG version: | 2.0.0 | Add-on build: | ||
| gvSIG build: | Add-on resolve version: | |||
| Operative System: | Add-on resolve build: | |||
| Keywords: | Proyecto: | |||
| Has patch: | No | Hito: | ||
| Add-on name: | Unknown |
Description
Al intentar conectar a la base de datos PostGIS la aplicación se queda colgada. Los mismos parámetros empleado en gvSIG 1.X realiza la conexión sin problemas:
Tampoco aparece ningún error en el log, las últimas lineas son las siguientes:
INFO [AWT-EventQueue-1] (DefaultActionInfo.java:212) - org.gvsig.app:org.gvsig.app.extension.AddLayer.execute('view-layer-add')
WARN [AWT-EventQueue-1] (Messages.java:141) - org.gvsig.gui.beans -- Cannot find translation for values_of_the_selected_field_explanation
WARN [AWT-EventQueue-1] (Messages.java:141) - org.gvsig.gui.beans -- Cannot find translation for fields_of_the_selected_feature_explanation
WARN [AWT-EventQueue-1] (Messages.java:141) - org.gvsig.i18n.Messages -- Cannot find translation for JDBCDriverClass
WARN [AWT-EventQueue-1] (Messages.java:141) - org.gvsig.i18n.Messages -- Cannot find translation for URL
WARN [AWT-EventQueue-1] (Messages.java:141) - org.gvsig.i18n.Messages -- Cannot find translation for URL
error-conectar-postgis.png (17.5 KB)
History
#1
Updated by José Vicente Higón almost 11 years ago
- Description updated (diff)
#2
Updated by Juan Lucas Domínguez over 10 years ago
- Assignee set to Juan Lucas Domínguez
#3
Updated by Juan Lucas Domínguez over 10 years ago
This still happens with latest builds?
#4
Updated by Juan Lucas Domínguez over 10 years ago
- Status changed from New to Awaiting response
This still happens with latest builds?
#5
Updated by José Vicente Higón over 10 years ago
Juan Lucas Domínguez wrote:
This still happens with latest builds?
No, no he podido reproducir el error en los últimos builds. Creo que ya funciona.
#6
Updated by Juan Lucas Domínguez over 10 years ago
- Status changed from Awaiting response to Fixed
Ok, quizá está relacionado con #2160
#7
Updated by Joaquín del Cerro Murciano over 10 years ago
- Target version set to 2.1.0-2217-devel
#8
Updated by Álvaro Anguix over 10 years ago
- Status changed from Fixed to Closed