Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    #16
    sc_snapshot-2010-03-09

    Comment


      #17
      That explains it - use a nightly as indicated.

      Comment


        #18
        same error

        Comment


          #19
          Given that there are applications running right now on the latest snapshot that are not exhibiting this problem, most likely you didn't correctly install the new version. Follow the step by step installation instructions.

          http://www.smartclient.com/smartgwtee/javadoc/com/smartgwt/client/docs/SgwtEESetup.html

          Comment


            #20
            I started twice from scratch,
            first with the BuiltinDS example and then with the ShowcaseEE example.

            I am really lost with it, any other idea rather than start over again?

            Comment


              #21
              We tried using the "FileUpload" example on our Oracle Databases. We created the schema on Oracle 9i 11g. Without modifying the code or XML dataSource, just changing the server.properties for Database, we transfered the example to Oracle.
              It allowed us to upload the images, but could not download them, same error as before. ("closed connection", or "must be logged on to server" on older version)

              We tried simulating this error with our own code, and it appears to happen if you select a blob, take it from the resultset, and then close the connection before calling "read" on the blob's stream. It's ok to close the ResultSet or the Statement, but closing the connection is what causing this exact error.
              Using that information we tried to debug through SQLDataSource's code, and it appears to try and close the connection (through calling "freeDataSource").

              Why would it do that? Are there pool configurations we should use? currently we just use the "thin" configuration (server, port, sid, user, password).
              If we want to use DB Datasource from a Websphere Application Server, what configs do we use?

              Comment


                #22
                We made it work by an ugly patch that feels very bad for us.

                While debugging we saw that freeDataSource() is called before the Blob is read.

                so we override this method to do none and than downloadFile worked.

                Do you have any better idea or fix for this?

                Comment


                  #23
                  What are the exact settings you're putting into the Admin Console and what is the exact URL you downloaded this JDBC driver from?

                  To use container-managed pooling, just use the "JNDI" option and enter the JNDI name you used when you configured the WebSphere DataSource.

                  Comment


                    #24
                    We are using Oracle`s official client.

                    Are you talking about the server.properties settings (we are not using the admin console at all)?
                    If so, we only specify the serverName, portNumber, databaseName, user and password.

                    Comment


                      #25
                      anything new?
                      we still have an empty call to freeDataSource...

                      Comment


                        #26
                        It should be obvious that saying only "Oracle's official client" is useless. It's easy to download the wrong file, that's why we asked for details.

                        Have you tried using the JNDI option?

                        Comment


                          #27
                          We've found and fixed the issue with freeing connections too soon with connection pooling off and it will be available in the next nightly build. Note that this should not affect either pooled connections or JDNI-based pooling, which are still the recommended approaches for a production deployment.

                          Comment


                            #28
                            COOL!

                            Will check soon!

                            Comment

                            Working...
                            X