Hi List,
We just discovered a nasty problem.
When using Geoserver 2.1.2 and Ms SQL Server 2008, creating a new SQL
Server store... well... it doesn't work. We get a timeout, Wicket kills the
thread and nothing gets created.
Creating the xml files by hand (or in our case, copying it from a working
version) kills the GeoServer proces.
Luckely, we had a working 2.1.2 situation, so we started comparing. We
found out that this is a problem caused by the JAVA JRE 1.6.0 Update 29!
When we downgraded the JRE to update 26, Geoserver could connect to MS SQL
without any problems.
I'm not sure yet where the real problem lies. It could either be with the
JRE update, or within the MS SQL .JAR file. We will investigate that as
well. For now, downgrading the JRE to update 26 is good enough for our
development, so it might take some time before we start ripping down our
development installation. :)
I hope I helped a few who were struggling with this problem.
Regards,
Casper
PS As I found some posts on this list that looked really simular to our
situation, I'll add some tags for people to find this post with: MSSQL
2008, org.apache.wicket.WicketRuntimeException: After 1 minute the Pageman
null is still lock by.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
