1 2 Previous Next 21 Replies Latest reply on Sep 21, 2009 6:07 AM by hellow Go to original post
      • 15. Re: JBPM 4.x using Sybase ASE 11/12 on Jboss 5.1.0GA
        hellow
        hellow Sep 17, 2009 5:08 AM (in response to hellow)

        I think you right. Just spoke with the DBA who turned Auditing on. He pulled some of the queries which are being executed and they seem to have syntax issues with Sybase.

        Thanks for help dudes

        Now I just need to convince them to let me use mySQL or something which actually is working :D

          • Actions
        • 16. Re: JBPM 4.x using Sybase ASE 11/12 on Jboss 5.1.0GA
          kukeltje
          kukeltje Sep 17, 2009 5:40 AM (in response to hellow)

          Or change the queries in the source so we can have a look to and maybe fix it on our side ;-)

            • Actions
          • 17. Re: JBPM 4.x using Sybase ASE 11/12 on Jboss 5.1.0GA
            hellow
            hellow Sep 17, 2009 9:29 AM (in response to hellow)

            kukeltje: hehehe, will see what i can do

            On a related note I tried Oracle and mySQL now and I think I have found a pattern.

            When you access the reporting screen it displays this on mySQL:

            Caused by: java.sql.SQLException: Access denied for user 'sa'@'localhost' (using password: NO)
 at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:946)
 at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2985)
 at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:885)
 at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:3421)
 at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1247)
 at com.mysql.jdbc.Connection.createNewIO(Connection.java:2775)
 at com.mysql.jdbc.Connection.<init>(Connection.java:1555)
 at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:285)
 at com.mysql.jdbc.jdbc2.optional.MysqlDataSource.getConnection(MysqlDataSource.java:425)
 at com.mysql.jdbc.jdbc2.optional.MysqlDataSource.getConnection(MysqlDataSource.java:140)
 at com.mysql.jdbc.jdbc2.optional.MysqlXADataSource.getXAConnection(MysqlXADataSource.java:58
)


            For Oracle: 

            Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

 at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
 at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:406)
 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399)
 at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:799)
 at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:368)
 at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:508)
 at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:203)
 at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:510)
 at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:275)
 at oracle.jdbc.xa.client.OracleXADataSource.getPooledConnection(OracleXADataSource.java:454

 at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:159)
 at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:130)
 at org.jboss.resource.adapter.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XA
anagedConnectionFactory.java:137)


            For Sybase: 

            Caused by: java.sql.SQLException: Login failed
 at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
 at net.sourceforge.jtds.jdbc.TdsCore.tdsLoginAckToken(TdsCore.java:2956)
 at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2264)
 at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:603)
 at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:357)
 at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
 at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
 at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(Loca
lManagedConnectionFactory.java:172)


            I think it's trying to use a user called sa with null password. If you add that to mySQL then the error disappears. Sybase and Oracle won't let me add users with no passwords (for good reason :P).

            I think this might be the actual problem...any clue where to force a different user? Or where it is setting this user.

            I thought it was in jbpm.hibernate.cfg.xml but that doesn't seem to work :(

              • Actions
            • 18. Re: JBPM 4.x using Sybase ASE 11/12 on Jboss 5.1.0GA
              kukeltje
              kukeltje Sep 17, 2009 11:12 AM (in response to hellow)

              user sa is normally one for hsqldb so that leads me to think (again) that a different config file is used. Can you do a zgrep or something on all jbpm and console related jar's?

                • Actions
              • 19. Re: JBPM 4.x using Sybase ASE 11/12 on Jboss 5.1.0GA
                hellow
                hellow Sep 18, 2009 5:16 AM (in response to hellow)

                yep I think you are right.....I found that user in server\default\deploy\hsqldb-ds.xml

                  • Actions
                • 20. Re: JBPM 4.x using Sybase ASE 11/12 on Jboss 5.1.0GA
                  hellow
                  hellow Sep 18, 2009 6:19 AM (in response to hellow)

                  http://www.mail-archive.com/jboss-user@lists.jboss.org/msg147697.html//www.mail-archive.com/jboss-user@lists.jboss.org/msg147697.html

                  That seems to be the same problem I am getting

                    • Actions
                  • 21. Re: JBPM 4.x using Sybase ASE 11/12 on Jboss 5.1.0GA
                    hellow
                    hellow Sep 21, 2009 6:07 AM (in response to hellow)

                    so it was a user problem....

                    and since the birt reporting is installed in /data/birt it took so long to find the actual culprits:

                    I changed this file -> server.home\server\default\data\birt\overall_activity.rptdesign

                     <data-sources>
 <oda-data-source extensionID="org.eclipse.birt.report.data.oda.jdbc" name="HsqlDB on JBoss" id="248">
 <property name="odaDriverClass">org.hsqldb.jdbcDriver</property>
 <property name="odaURL">jdbc:hsqldb:hsql://localhost:1701</property>
 <property name="odaUser">sa</property>
 <property name="odaJndiName">java:/JbpmDS</property>
 </oda-data-source>
 </data-sources>


                    to 
                    <data-sources>
 <oda-data-source extensionID="org.eclipse.birt.report.data.oda.jdbc" name="HsqlDB on JBoss" id="248">
 <property name="odaJndiName">java:/JbpmDS</property>
 </oda-data-source>
 </data-sources>


                    and server.home\server\default\data\birt\specific_system_overview.rptdesign

                    from 
                     <data-sources>
 <oda-data-source extensionID="org.eclipse.birt.report.data.oda.jdbc" name="HsqlDB on JBoss" id="248">
 <property name="odaDriverClass">org.hsqldb.jdbcDriver</property>
 <property name="odaURL">jdbc:hsqldb:hsql://localhost:1701</property>
 <property name="odaUser">sa</property>
 <property name="odaJndiName">java:/JbpmDS</property>
 </oda-data-source>
 </data-sources>


                    to 
                    <data-sources>
 <oda-data-source extensionID="org.eclipse.birt.report.data.oda.jdbc" name="HsqlDB on JBoss" id="248">
 <property name="odaJndiName">java:/JbpmDS</property>
 </oda-data-source>
 </data-sources>


                    and walla...the login failures disappear

                      • Actions
                    1 2 Previous Next