Variman server is running, but unable to login (not prompted at all in browser due to exception in readFully)

[Tom Swift]

Hi All,

I've had Variman running successfully for a few years without issues.  I am now migrating to a new server.  With my old server, as a quick test, if I just went to my browser to login at domain.com:6103/rets/login then I would get promped for username/pw and could login successfully.  With the new server, I don't even get prompted.  I have logging set to debug and this is what I get (see below).  It seems like its trying to execute some internal sql and fails even before it prompts me.  Just a guess based on the stack.  The server is up and running so I know my db username and pw are correct.

ANY IDEAS?  Thanks!

20 Jun 2013 12:15:49,999 WARN  [20.164.29.111 ] org.hibernate.util.JDBCExceptionReporter
-> SQL Error: 0, SQLState: 08003
20 Jun 2013 12:15:49,999 ERROR [20.164.29.111 ] org.hibernate.util.JDBCExceptionReporter
-> No operations allowed after connection closed.Connection was implicitly closed due to underlying exception/error:


** BEGIN NESTED EXCEPTION **

com.mysql.jdbc.CommunicationsException
MESSAGE: Communications link failure due to underlying exception:

** BEGIN NESTED EXCEPTION **

java.io.EOFException
MESSAGE: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost.

STACKTRACE:

java.io.EOFException: Can not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost.
    at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1997)
    at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2411)
    at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2916)
    at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631)
    at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723)
    at com.mysql.jdbc.Connection.execSQL(Connection.java:3283)
    at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1332)
    at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1467)
    at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208)
    at org.hibernate.loader.Loader.getResultSet(Loader.java:1812)
    at org.hibernate.loader.Loader.doQuery(Loader.java:697)
    at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259)
    at org.hibernate.loader.Loader.doList(Loader.java:2232)
    at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2129)
    at org.hibernate.loader.Loader.list(Loader.java:2124)
    at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:401)
    at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:363)
    at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196)
    at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1149)
    at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102)
    at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:835)
    at org.realtors.rets.server.UserUtils.findByUsername(UserUtils.java:50)
    at org.realtors.rets.server.UserUtils.findByUsername(UserUtils.java:30)
    at org.realtors.rets.server.webapp.auth.HibernateUserMap.findUser(HibernateUserMap.java:26)
    at org.realtors.rets.server.webapp.auth.AuthenticationFilter.findAuthorizedUser(AuthenticationFilter.java:211)
    at org.realtors.rets.server.webapp.auth.AuthenticationFilter.verifyResponse(AuthenticationFilter.java:189)
    at org.realtors.rets.server.webapp.auth.AuthenticationFilter.doAuthentication(AuthenticationFilter.java:152)
    at org.realtors.rets.server.webapp.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:100)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Unknown Source)

[Keith T. Garner]

The big problem is that it seems like variman and your mysql server are having problems communicating and the mysql server is dropping the connection before sending any data in a response. I'm not sure what that is...a packet sniff might be able to help you determine that.

Keith

> --
> You received this message because you are subscribed to the Google Groups "Variman RETS Server" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to variman-discu...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
Keith T. Garner kga...@kgarner.com
"Make no little plans; they have no magic to
stir men's blood." - Daniel H. Burnham

[clove...@gmail.com]

Hi Keith,

Thanks for your response. I turned on mysql query logging and no variman queries are being logged.  So it must be an issue even before that at a lower level, as you suggested.  With the server migration (also went from 32-bit to 64-bit), I have the latest variman 3.2.3, latest Java jre1.7.0_21, and mysql 5.5.30.  Perhaps I'll try and go back to what I originally had for java and variman on the old server.  If that doesn't work, maybe it's mysql ...

-Tom

[Mark Klein]

On Jun 20, 2013, at 10:55 AM, clove...@gmail.com wrote:

> Hi Keith,
>
> Thanks for your response. I turned on mysql query logging and no variman queries are being logged. So it must be an issue even before that at a lower level, as you suggested. With the server migration (also went from 32-bit to 64-bit), I have the latest variman 3.2.3, latest Java jre1.7.0_21, and mysql 5.5.30. Perhaps I'll try and go back to what I originally had for java and variman on the old server. If that doesn't work, maybe it's mysql ...

One thought ... (and I'm a PostgreSQL user, not MySql ... ) for PostreSQL, one needs to enable permissions for incoming network connections. Does MySql do the same? I'm betting it is permissions, though it could also be Java versions vs. the hibernate implementation ... I've not built against Java 1.7.


Regards,

M.
--
To quote my Bro: "Please forgive spelling and grammar mistakes, they're the fault of [his] iPhone."

[clove...@gmail.com]

So I got a little further along.  There is a good mysql article http://dev.mysql.com/doc/refman/5.0/en/connector-j-usagenotes-troubleshooting.html#qandaitem-21-3-15-1-7 which helped get past the first issue mentioned in this post.  Basically, I upgraded mysql-connector-java-5.0.8-bin.jar to mysql-connector-java-5.1.25-bin.jar and that got me to the prompt so that I could enter a username/pw.  But it still fails (see below)

As for your incoming permissions question, yes mysql has something similar and it's currently allowing all connections.

Here is the new failure/exception (in red below):

20 Jun 2013 16:12:47,872 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter
-> Variman version 3.2.3
20 Jun 2013 16:12:47,872 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter
-> Authorizing URI: GET /rets/login null
20 Jun 2013 16:12:47,872 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter
-> User-Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0; BOIE9;ENUS)
20 Jun 2013 16:12:47,873 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.DigestAuthorizationRequest
-> Authorization header: <null>
20 Jun 2013 16:12:47,885 DEBUG [22.222.22.222 ] org.realtors.rets.server.SessionHelper
-> createQuery
20 Jun 2013 16:12:47,885 DEBUG [22.222.22.222 ] org.realtors.rets.server.SessionHelper
-> beginSession
20 Jun 2013 16:12:48,144 DEBUG [22.222.22.222 ] org.realtors.rets.server.SessionHelper
-> close
20 Jun 2013 16:12:48,153 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.NonceTable
-> Created new nonce <f1b19be091e399af58c22b26a7ea3d11>, table size: 1
20 Jun 2013 16:12:48,154 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter
-> Sending 401 with header: Digest realm="RETS Server", qop="auth", nonce="f1b19be091e399af58c22b26a7ea3d11", opaque="687bf0fc4a1171799442140442769f1e"
20 Jun 2013 16:14:12,235 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter
-> Variman version 3.2.3
20 Jun 2013 16:14:12,235 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter
-> Authorizing URI: GET /rets/login null
20 Jun 2013 16:14:12,236 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter
-> User-Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0; BOIE9;ENUS)
20 Jun 2013 16:14:12,236 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.DigestAuthorizationRequest
-> Authorization header: <Digest username="mytestuser",realm="RETS Server",nonce="f1b19be088e399af58c22b26a7ea3d11",uri="/rets/login",cnonce="cbb29f8d888897205b161c34bc793306",nc=00000001,response="f841077fe2888d11dafd1f1d2410dd6a",qop="auth",opaque="687bf0fc4a1188888442140442769f1e">
20 Jun 2013 16:14:12,236 DEBUG [22.222.22.222 ] org.realtors.rets.server.SessionHelper
-> createQuery
20 Jun 2013 16:14:12,236 DEBUG [22.222.22.222 ] org.realtors.rets.server.SessionHelper
-> beginSession
20 Jun 2013 16:14:12,243 WARN  [22.222.22.222 ] org.hibernate.jdbc.AbstractBatcher
-> exception clearing maxRows/queryTimeout
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: No operations allowed after statement closed.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
    at com.mysql.jdbc.Util.getInstance(Util.java:386)
    at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1015)
    at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:989)
    at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:975)
    at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:920)
    at com.mysql.jdbc.StatementImpl.checkClosed(StatementImpl.java:461)
    at com.mysql.jdbc.StatementImpl.getMaxRows(StatementImpl.java:2216)
    at org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:298)
    at org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:234)
    at org.hibernate.loader.Loader.getResultSet(Loader.java:1826)

20 Jun 2013 16:14:12,248 WARN  [22.222.22.222 ] org.hibernate.util.JDBCExceptionReporter
-> SQL Error: 0, SQLState: 08S01
20 Jun 2013 16:14:12,248 ERROR [22.222.22.222 ] org.hibernate.util.JDBCExceptionReporter
-> Communications link failure

The last packet successfully received from the server was 84,097 milliseconds ago.  The last packet sent successfully to the server was 1 milliseconds ago.

-Tom

[Mark Klein]

On Jun 20, 2013, at 1:29 PM, clove...@gmail.com wrote:

> So I got a little further along. There is a good mysql article http://dev.mysql.com/doc/refman/5.0/en/connector-j-usagenotes-troubleshooting.html#qandaitem-21-3-15-1-7
> which helped get past the first issue mentioned in this post.
> Basically, I upgraded mysql-connector-java-5.0.8-bin.jar to mysql-
> connector-java-5.1.25-bin.jar and that got me to the prompt so that
> I could enter a username/pw. But it still fails (see below)

Is this against the demo database or your own? It looks like the
"overhead" tables haven't been created. You need to use the admin app
to do that. From the command line:

java -jar variman-admin.jar create-schema

or ... bring up the GUI and select DATABASE->Create Schema.



Regards,


M.

--
Mark Klein
PGP Key Available
www.dis.com

[clove...@gmail.com]

I copied the "overhead" tables from the old server.  As a matter of fact, I just copied the entire database and moved it over which included the tables rets_accounting, rets_group, rets_user, and rets_user_groups.  I'm just curious, why did you think those were not created yet?  Was there something in the log?

-Tom

[clove...@gmail.com]

So as a test, I went back to my old 3.2.2 rets server and modified rets-config.xml to point to the new mysql 5.5.30 server.  As I suspected this did not work and I get the same error as originally posted.  So this issue seems to boil down to the newer version of MySQL and it's interaction with Variman.  I've looked into the MySQL variables like wait_timeout, net_write_timeout, net_read_timeout but these values are all the same as the old server.  The fact that I had to upgrade the mysql java connector to get past the first error also leaves me suspicious if anything else in Variman needs upgrading to work with newer MySQL servers.  I found some article talking about c3p0 and hibernate but I have no idea how to upgrade these or if I should even try.

Thanks again to any replies, suggestions, comments.

-Tom

[Mark Klein]

On Jun 21, 2013, at 11:33 AM, clove...@gmail.com wrote:

> So as a test, I went back to my old 3.2.2 rets server and modified
> rets-config.xml to point to the new mysql 5.5.30 server. As I
> suspected this did not work and I get the same error as originally
> posted. So this issue seems to boil down to the newer version of
> MySQL and it's interaction with Variman. I've looked into the MySQL
> variables like wait_timeout, net_write_timeout, net_read_timeout but
> these values are all the same as the old server. The fact that I
> had to upgrade the mysql java connector to get past the first error
> also leaves me suspicious if anything else in Variman needs
> upgrading to work with newer MySQL servers. I found some article
> talking about c3p0 and hibernate but I have no idea how to upgrade
> these or if I should even try.
>
> Thanks again to any replies, suggestions, comments.

At this point, it probably is a versioning issue somewhere between
hibernate, jdbc and MySql. I'd look to see if maybe updating the
hibernate jars might help.

[clove...@gmail.com]

Hi Mark,

Ok, so I took your suggestion and attempted to update hibernate using http://sourceforge.net/projects/hibernate/files/hibernate4/ which gave me these jars for 4.2.2:

antlr-2.7.7.jar
dom4j-1.6.1.jar
hibernate-commons-annotations-4.0.2.Final.jar
hibernate-core-4.2.2.Final.jar
hibernate-jpa-2.0-api-1.0.1.Final.jar
javassist-3.15.0-GA.jar
jboss-logging-3.1.0.GA.jar
jboss-transaction-api_1.1_spec-1.0.1.Final.jar

I saved away hibernate.jar from variman/WEB-INF/lib and put the above jars in the directory.  The only file that already existed was dom4j-1.6.1.jar and this was identical.  So after restarting the Variman server, I wasn't surprised to get the exception/error below.  So this means I either don't have the right jar or the api has changed.  Any suggestions for upgrading hibernate?  Thanks again.

21 Jun 2013 22:37:35,004 DEBUG [ ] org.realtors.rets.server.SessionHelper
-> beginSession
21 Jun 2013 22:37:35,004 DEBUG [ ] org.realtors.rets.server.SessionHelper
-> close
21 Jun 2013 22:37:35,005 FATAL [ ] org.realtors.rets.server.webapp.InitServlet
-> Caught
java.lang.NoSuchMethodError: org.hibernate.SessionFactory.openSession()Lorg/hibernate/classic/Session;
    at org.realtors.rets.server.SessionHelper.beginSession(SessionHelper.java:36)
    at org.realtors.rets.server.SessionHelper.getConnection(SessionHelper.java:45)
    at org.realtors.rets.server.webapp.InitServlet.logDatabaseInfo(InitServlet.java:208)
    at org.realtors.rets.server.webapp.InitServlet.initHibernate(InitServlet.java:194)
    at org.realtors.rets.server.webapp.InitServlet.init(InitServlet.java:53)
    at javax.servlet.GenericServlet.init(GenericServlet.java:212)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1172)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:992)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4058)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4371)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
    at org.realtors.rets.server.tomcat.EmbeddedTomcat.registerWebapp(EmbeddedTomcat.java:182)
    at org.realtors.rets.server.tomcat.EmbeddedTomcat.main(EmbeddedTomcat.java:243)

[Mark Klein]

On Jun 21, 2013, at 7:53 PM, clove...@gmail.com wrote:

> I saved away hibernate.jar from variman/WEB-INF/lib and put the
> above jars in the directory. The only file that already existed was
> dom4j-1.6.1.jar and this was identical. So after restarting the
> Variman server, I wasn't surprised to get the exception/error
> below. So this means I either don't have the right jar or the api
> has changed. Any suggestions for upgrading hibernate? Thanks again.
>

> java.lang.NoSuchMethodError:
> org.hibernate.SessionFactory.openSession()Lorg/hibernate/classic/
> Session;

"classic" in the path looks suspiciously like the APIs have changed.
You may need to try rebuilding things from source with the new jars.

Or ... can you use the older MySql with Variman?

[Mark Klein]

On Jun 21, 2013, at 7:53 PM, clove...@gmail.com wrote:

> java.lang.NoSuchMethodError:
> org.hibernate.SessionFactory.openSession()Lorg/hibernate/classic/
> Session;

Quick visit to the hibernate web pages ... there are big differences
between hibernate 3 and hibernate 4, including changes to session
management (SessionFactory was deprecated). May as well roll back to
the old jars ... it ain't gonna work with the new jars without code
changes.

You problem is somehow related to MySql. I'd suggest seeing if you can
either use an older version of MySql or see if there is an updated
jdbc jar just for MySql. There were also some big changes to Java
between 1.5 and 1.7 and I see the mysql-connector is "mysql-connector-
java-5.0.8-bin.jar". If updating that jar doesn't work, I think you're
out of luck until the code can be refreshed to the latest and greatest.

[clove...@gmail.com]

Hi Mark, thanks again for your input.  I did try the latest hibernate3 jars and that got the server back up again.  Regarding the mysql-connector jar, that was the first thing I updated and it got me past the original exception/error I posted in this topic.  However, even with the latest hibernate3, I get the exception below (and was never prompted for a username/pw).

Do you know if Variman still being developed?

My current variman/WEB-INF/lib looks like (with comments):

antlr-2.7.6.jar  // updated with hiberate3
c3p0-0.9.1.jar
commons-codec.jar
commons-collections-3.1.jar  // updated with hiberate3
commons-lang.jar
commons-logging.jar
dom4j-1.6.1.jar
dtdparser121.jar
hibernate3.jar   // updated with hiberate3
hibernate-jpa-2.0-api-1.0.1.Final.jar  // from hibernate4 package or else we fail
javassist-3.12.0.GA.jar  // updated with hiberate3
jdom.jar
jta-1.1.jar  // updated with hiberate3
jtds.jar
log4j.jar
mysql-connector-java-5.1.25-bin.jar  // updated mysql connector
postgresql-jdbc.jar
rets-client.jar
slf4j-api-1.5.8.jar  // updated with hiberate3
slf4j-log4j12-1.5.8.jar
spring.jar
variman-hibernate.jar

THE NEW EXCEPTION WITH LATEST HIBERNATE 3:

22 Jun 2013 10:48:03,333 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter
-> Variman version 3.2.3
22 Jun 2013 10:48:03,333 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter

-> Authorizing URI: GET /rets/login null

22 Jun 2013 10:48:03,333 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter
-> User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:21.0) Gecko/20100101 Firefox/21.0
22 Jun 2013 10:48:03,334 DEBUG [22.222.22.222 ] org.realtors.rets.server.webapp.auth.DigestAuthorizationRequest
-> Authorization header: <null>
22 Jun 2013 10:48:03,346 DEBUG [22.222.22.222 ] org.realtors.rets.server.SessionHelper
-> createQuery
22 Jun 2013 10:48:03,346 DEBUG [22.222.22.222 ] org.realtors.rets.server.SessionHelper
-> beginSession
22 Jun 2013 10:48:03,576 WARN  [22.222.22.222 ] org.hibernate.util.JDBCExceptionReporter

-> SQL Error: 0, SQLState: 08S01

22 Jun 2013 10:48:03,576 ERROR [22.222.22.222 ] org.hibernate.util.JDBCExceptionReporter
-> Communications link failure

The last packet successfully received from the server was 192,593 milliseconds ago.  The last packet sent successfully to the server was 1 milliseconds ago.
22 Jun 2013 10:48:03,576 DEBUG [22.222.22.222 ] org.realtors.rets.server.SessionHelper
-> close
22 Jun 2013 10:48:03,580 ERROR [22.222.22.222 ] org.realtors.rets.server.webapp.auth.AuthenticationFilter
-> Caught
org.realtors.rets.server.RetsServerException: org.hibernate.exception.JDBCConnectionException: Cannot open connection
    at org.realtors.rets.server.webapp.auth.HibernateUserMap.findUser(HibernateUserMap.java:30)

    at org.realtors.rets.server.webapp.auth.AuthenticationFilter.findAuthorizedUser(AuthenticationFilter.java:211)
    at org.realtors.rets.server.webapp.auth.AuthenticationFilter.verifyResponse(AuthenticationFilter.java:189)
    at org.realtors.rets.server.webapp.auth.AuthenticationFilter.doAuthentication(AuthenticationFilter.java:152)
    at org.realtors.rets.server.webapp.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:100)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Unknown Source)

[Mark Klein]

On Jun 22, 2013, at 8:10 AM, clove...@gmail.com wrote:

> Hi Mark, thanks again for your input. I did try the latest
> hibernate3 jars and that got the server back up again. Regarding
> the mysql-connector jar, that was the first thing I updated and it
> got me past the original exception/error I posted in this topic.
> However, even with the latest hibernate3, I get the exception below
> (and was never prompted for a username/pw).

Still looks like a sql/jdbc mismatch.

>
> Do you know if Variman still being developed?

There have been a few patches submitted but aside from that, no. My
funding stopped a couple of years back and while I tinker with it
periodically and review and apply patches, I'm not doing active
development on it. It is a community project, so feel free to submit
patches if you want. But, I needed to move on to other paying
projects, so Variman mostly just sits these days.