Discussion:
Problem connecting to database from Easerver component
(too old to reply)
Stelios Vasiliadis
2008-05-23 13:55:56 UTC
Permalink
Hi

We are planing to transfer our application from powerbuilder 9 and
easerver 5.5 (windows) to powerbuilder 10.5.2 and easerver 6.0.2 (Linux).
But even that we transfer the same code that was working in the old
instalation we get the following error (in sqlerrtext property) when a
component in jaguar tries to connect to the database (ASE 12.5.3 ESD 4)

"Failed to get a valid Database Connection from Jaguar yet no error was
returned"

Also sqlcode returns -1 and SQLDBCode returns 999


The code that we use to connect is the following

sqlca.DBMS = "SYJ"
sqlca.AutoCommit = True
sqlca.DBParm = "UseContextObject='Yes',CacheName='DATABASENAME'"
connect using sqlca;

Also the ping from database source in resources in the jaguar manager always
returns OK. Another thing is that we have a similar instalation for another
project with the only difference that is the easerver is in windows and we
don't have any problem

Can somebody help??

Thanks in advance

Stelios
Evan Ireland
2008-05-25 21:02:09 UTC
Permalink
This post might be inappropriate. Click to display it.
Evan Ireland
2008-05-25 21:02:20 UTC
Permalink
This post might be inappropriate. Click to display it.
Stelios Vasiliadis
2008-05-26 07:22:28 UTC
Permalink
Below is the error in the log

2008-05-26 09:23:13.363 INFO btpool0-1 [SystemException]
java.lang.NumberFormatException was thrown by method
com.sybase.jaguar.jcm.JagCm.getConnection
2008-05-26 09:23:13.363 INFO btpool0-1 java.lang.NumberFormatException:
For input string: "@"
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.Long.parseLong(Long.java:394)
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.Long.parseLong(Long.java:452)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.jcm.JagCm.getConnection(JagCm.java:172)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(Native Method)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:289)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:97)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject_DJC.invoke(JaguarObject_DJC.java:341)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_ps_EJB.f_createctlbridgefile(uo_ps_EJB.java:169)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote.f_createctlbridgefile(uo_psRemote.java:205)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.access$101(uo_psRemote_DJC.java:4)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC$2.invoke(uo_psRemote_DJC.java:482)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:675)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported(TransactionManager.java:631)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.f_createctlbridgefile(uo_psRemote_DJC.java:507)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.$invoke_0(uo_psRemote_DJC.java:197)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.$invoke(uo_psRemote_DJC.java:156)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarServer.iiopHandler(JaguarServer.java:262)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.RequestHandler.processRequest(RequestHandler.java:9)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:625)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:326)
2008-05-26 09:23:13.363 INFO btpool0-1 at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Post by Evan Ireland
Post by Stelios Vasiliadis
Hi
We are planing to transfer our application from powerbuilder 9 and
easerver 5.5 (windows) to powerbuilder 10.5.2 and easerver 6.0.2
(Linux). But even that we transfer the same code that was working in the
old instalation we get the following error (in sqlerrtext property) when
a component in jaguar tries to connect to the database (ASE 12.5.3 ESD 4)
"Failed to get a valid Database Connection from Jaguar yet no error was
returned"
Also sqlcode returns -1 and SQLDBCode returns 999
The code that we use to connect is the following
sqlca.DBMS = "SYJ"
sqlca.AutoCommit = True
sqlca.DBParm = "UseContextObject='Yes',CacheName='DATABASENAME'"
connect using sqlca;
Also the ping from database source in resources in the jaguar manager
always returns OK. Another thing is that we have a similar instalation
for another project with the only difference that is the easerver is in
windows and we don't have any problem
Can somebody help??
Thanks in advance
Stelios
Is there anything logged in the server log file (in logs/xxx.log)?
Evan Ireland
2008-05-26 21:44:52 UTC
Permalink
OK, so something is not right with the definition of the data source.
Assuming that your data source is named "DATABASENAME", what is the
contents of file:

Repository/Instance/com/sybase/djc/sql/DataSource/DATABASENAME.properties
Post by Stelios Vasiliadis
Below is the error in the log
2008-05-26 09:23:13.363 INFO btpool0-1 [SystemException]
java.lang.NumberFormatException was thrown by method
com.sybase.jaguar.jcm.JagCm.getConnection
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.Long.parseLong(Long.java:394)
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.Long.parseLong(Long.java:452)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.jcm.JagCm.getConnection(JagCm.java:172)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(Native Method)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:289)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:97)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject_DJC.invoke(JaguarObject_DJC.java:341)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_ps_EJB.f_createctlbridgefile(uo_ps_EJB.java:169)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote.f_createctlbridgefile(uo_psRemote.java:205)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.access$101(uo_psRemote_DJC.java:4)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC$2.invoke(uo_psRemote_DJC.java:482)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:675)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported(TransactionManager.java:631)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.f_createctlbridgefile(uo_psRemote_DJC.java:507)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.$invoke_0(uo_psRemote_DJC.java:197)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.$invoke(uo_psRemote_DJC.java:156)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarServer.iiopHandler(JaguarServer.java:262)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.RequestHandler.processRequest(RequestHandler.java:9)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:625)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:326)
2008-05-26 09:23:13.363 INFO btpool0-1 at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Post by Evan Ireland
Post by Stelios Vasiliadis
Hi
We are planing to transfer our application from powerbuilder 9 and
easerver 5.5 (windows) to powerbuilder 10.5.2 and easerver 6.0.2
(Linux). But even that we transfer the same code that was working in the
old instalation we get the following error (in sqlerrtext property) when
a component in jaguar tries to connect to the database (ASE 12.5.3 ESD 4)
"Failed to get a valid Database Connection from Jaguar yet no error was
returned"
Also sqlcode returns -1 and SQLDBCode returns 999
The code that we use to connect is the following
sqlca.DBMS = "SYJ"
sqlca.AutoCommit = True
sqlca.DBParm = "UseContextObject='Yes',CacheName='DATABASENAME'"
connect using sqlca;
Also the ping from database source in resources in the jaguar manager
always returns OK. Another thing is that we have a similar instalation
for another project with the only difference that is the easerver is in
windows and we don't have any problem
Can somebody help??
Thanks in advance
Stelios
Is there anything logged in the server log file (in logs/xxx.log)?
Stelios Vasiliadis
2008-05-27 07:18:56 UTC
Permalink
Here it is the file
Post by Evan Ireland
OK, so something is not right with the definition of the data source.
Assuming that your data source is named "DATABASENAME", what is the
Repository/Instance/com/sybase/djc/sql/DataSource/DATABASENAME.properties
Post by Stelios Vasiliadis
Below is the error in the log
2008-05-26 09:23:13.363 INFO btpool0-1 [SystemException]
java.lang.NumberFormatException was thrown by method
com.sybase.jaguar.jcm.JagCm.getConnection
2008-05-26 09:23:13.363 INFO btpool0-1
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.Long.parseLong(Long.java:394)
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.Long.parseLong(Long.java:452)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.jcm.JagCm.getConnection(JagCm.java:172)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(Native Method)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:289)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:97)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject_DJC.invoke(JaguarObject_DJC.java:341)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_ps_EJB.f_createctlbridgefile(uo_ps_EJB.java:169)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote.f_createctlbridgefile(uo_psRemote.java:205)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.access$101(uo_psRemote_DJC.java:4)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC$2.invoke(uo_psRemote_DJC.java:482)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:675)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported(TransactionManager.java:631)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.f_createctlbridgefile(uo_psRemote_DJC.java:507)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.$invoke_0(uo_psRemote_DJC.java:197)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.$invoke(uo_psRemote_DJC.java:156)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarServer.iiopHandler(JaguarServer.java:262)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.RequestHandler.processRequest(RequestHandler.java:9)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:625)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:326)
2008-05-26 09:23:13.363 INFO btpool0-1 at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Post by Evan Ireland
Post by Stelios Vasiliadis
Hi
We are planing to transfer our application from powerbuilder 9 and
easerver 5.5 (windows) to powerbuilder 10.5.2 and easerver 6.0.2
(Linux). But even that we transfer the same code that was working in the
old instalation we get the following error (in sqlerrtext property) when
a component in jaguar tries to connect to the database (ASE 12.5.3 ESD 4)
"Failed to get a valid Database Connection from Jaguar yet no error was
returned"
Also sqlcode returns -1 and SQLDBCode returns 999
The code that we use to connect is the following
sqlca.DBMS = "SYJ"
sqlca.AutoCommit = True
sqlca.DBParm = "UseContextObject='Yes',CacheName='DATABASENAME'"
connect using sqlca;
Also the ping from database source in resources in the jaguar manager
always returns OK. Another thing is that we have a similar instalation
for another project with the only difference that is the easerver is in
windows and we don't have any problem
Can somebody help??
Thanks in advance
Stelios
Is there anything logged in the server log file (in logs/xxx.log)?
begin 666 iApplyNUA.properties
M(TEN<W1A;F-E(%!R;W!E<G1I97,*(TUO;B!-87D@,C8@,#DZ-3$Z,***@1453
M5" R,# X"G-E=%-E<W-I;VY!=71H/69A;'-E"FES1&]W;FQO861::7!P960]
M9F%L<V4*;6%X5V%I=%1I;64]-C *9&%T86)A<V54>7!E/5-Y8F%S95]!4T4*
M9&%T86)A<V53=&]P0V]M;6%N9#T*86QI87-&;W(]"FUA>%!O;VQ3:7IE/3$P
M"GAA1&%T85-O=7)C94-L87-S/5MD969A=6QT70IH:6=H079A:6QA8FEL:71Y
M/69A;'-E"G!I;F=#;VYN96-T:6]N<SUT<G5E"G-E<G9E<DYA;64],3DR+C$V
M."XQ,2XQ,#<*<&]R=$YU;6)E<CTU,# P"F1A=&%B87-E0V]M;6%N9$5C:&\]
M9F%L<V4*9&ES86)L95!R969E=&-H/69A;'-E"F1A=&%B87-E0W)E871E0V]M
M;6%N9#T*<&EN9T%N9%-E=%-E<W-I;VY!=71H/69A;'-E"FQA;F=U86=E/0IC
M;VUM:710<F]T;V-O;#UP97-S:6UI<W1I8PID871A8F%S94YA;64]24%04$Q9
M54$*<W1A<G1786ET/38P"F1R:79E<D-L87-S/5MD969A=6QT70IO=VYE<E!R
M969I>#T*<F]L94YA;64]"FID8F-$<FEV97)$;W=N;&]A9%523#T*9&%T86)A
M<V5&:6QE/0IU<V5R/6EA<'!L>75A861M"FUI;E!O;VQ3:7IE/3 *;6%X4W1A
M=&5M96YT<STP"FUA>$ED;&54:6UE/38P"G!A<W-W;W)D/2H*<')O>'E&;W(]
M"F1A=&%B87-E4W1A<G1#;VUM86YD/0ID871A8F%S95523#U;9&5F875L=%T*
M<&EN9U-13#U;9&5F875L=%T*8V]D95-E=#U;<V5R=F5R70IS97)V:6-E3F%M
M93U;9&5F875L=%T*:6YI=&EA;%!O;VQ3:7IE/3 *9&ES86)L951R:6=G97)S
M/69A;'-E"FYE='=O<FM0<F]T;V-O;#U;9&5F875L=%T*<V5T4V5S<VEO;D%U
M=&A3>7-T96U)1#T*9&%T85-O=7)C94-L87-S/5MD969A=6QT70IU<V54<F%N
3<V%C=&EO;F%L4&EN9SUT<G5E"@``
`
end
Evan Ireland
2008-05-29 20:13:46 UTC
Permalink
Stellos,

You should use a "database type" of "JCM_Sybase" to access ASE from
PowerBuilder components. Look at "Configuring database types" in
"Database Access" in:

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc38034_0600/html/eassag/title.htm&toc=/com.sybase.help.eas_6.0/toc.xml

It looks like we need to improve the documentation to make it more clear
that accessing Sybase, Oracle or ODBC from PowerBuilder (or C++)
components requires the use of a data source with database type JCM_xxx.

PowerBuilder components can also use JDBC connection caches (e.g. with a
database type of Sybase_ASA, Sybase_ASE, ...), but in that case you need
to set:

sqlca.DBMS = "JDBC"
Post by Stelios Vasiliadis
Here it is the file
Post by Evan Ireland
OK, so something is not right with the definition of the data source.
Assuming that your data source is named "DATABASENAME", what is the
Repository/Instance/com/sybase/djc/sql/DataSource/DATABASENAME.properties
Post by Stelios Vasiliadis
Below is the error in the log
2008-05-26 09:23:13.363 INFO btpool0-1 [SystemException]
java.lang.NumberFormatException was thrown by method
com.sybase.jaguar.jcm.JagCm.getConnection
2008-05-26 09:23:13.363 INFO btpool0-1
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.Long.parseLong(Long.java:394)
2008-05-26 09:23:13.363 INFO btpool0-1 at
java.lang.Long.parseLong(Long.java:452)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.jcm.JagCm.getConnection(JagCm.java:172)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(Native Method)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:289)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:97)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarObject_DJC.invoke(JaguarObject_DJC.java:341)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_ps_EJB.f_createctlbridgefile(uo_ps_EJB.java:169)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote.f_createctlbridgefile(uo_psRemote.java:205)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.access$101(uo_psRemote_DJC.java:4)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC$2.invoke(uo_psRemote_DJC.java:482)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported1(TransactionManager.java:675)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.transaction.TransactionManager.invokeNotSupported(TransactionManager.java:631)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.f_createctlbridgefile(uo_psRemote_DJC.java:507)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.$invoke_0(uo_psRemote_DJC.java:197)
2008-05-26 09:23:13.363 INFO btpool0-1 at
ejb.components.iapplyua.uo_psRemote_DJC.$invoke(uo_psRemote_DJC.java:156)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.JaguarServer.iiopHandler(JaguarServer.java:262)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.jaguar.server.RequestHandler.processRequest(RequestHandler.java:9)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:625)
2008-05-26 09:23:13.363 INFO btpool0-1 at
com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:326)
2008-05-26 09:23:13.363 INFO btpool0-1 at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Post by Evan Ireland
Post by Stelios Vasiliadis
Hi
We are planing to transfer our application from powerbuilder 9 and
easerver 5.5 (windows) to powerbuilder 10.5.2 and easerver 6.0.2
(Linux). But even that we transfer the same code that was working in the
old instalation we get the following error (in sqlerrtext property) when
a component in jaguar tries to connect to the database (ASE 12.5.3 ESD 4)
"Failed to get a valid Database Connection from Jaguar yet no error was
returned"
Also sqlcode returns -1 and SQLDBCode returns 999
The code that we use to connect is the following
sqlca.DBMS = "SYJ"
sqlca.AutoCommit = True
sqlca.DBParm = "UseContextObject='Yes',CacheName='DATABASENAME'"
connect using sqlca;
Also the ping from database source in resources in the jaguar manager
always returns OK. Another thing is that we have a similar instalation
for another project with the only difference that is the easerver is in
windows and we don't have any problem
Can somebody help??
Thanks in advance
Stelios
Is there anything logged in the server log file (in logs/xxx.log)?
unknown
2008-06-06 11:58:10 UTC
Permalink
Hi!
Post by Evan Ireland
Post by Stelios Vasiliadis
we get the following error (in
sqlerrtext property) when a component in jaguar tries
to connect to the database (ASE 12.5.3 ESD 4)
"Failed to get a valid Database Connection from Jaguar
yet no error was returned"
Also sqlcode returns -1 and SQLDBCode returns 999
Is there anything logged in the server log file (in
logs/xxx.log)?
I have a same error if to specify the incorrect
login/password. I use ODBC without a connection cache. How
to receive a code of a real error in SQLCA.
EAS 6.0.1.14, PB 10.2.1 9948

WBR, Oleg
Chris Pollach
2008-06-06 12:30:02 UTC
Permalink
Oleg;

What is in the SQLErrText ?
--
Regards ... Chris
http://chrispollach.pbdjmagazine.com
Post by unknown
Hi!
Post by Evan Ireland
Post by Stelios Vasiliadis
we get the following error (in
sqlerrtext property) when a component in jaguar tries
to connect to the database (ASE 12.5.3 ESD 4)
"Failed to get a valid Database Connection from Jaguar
yet no error was returned"
Also sqlcode returns -1 and SQLDBCode returns 999
Is there anything logged in the server log file (in
logs/xxx.log)?
I have a same error if to specify the incorrect
login/password. I use ODBC without a connection cache. How
to receive a code of a real error in SQLCA.
EAS 6.0.1.14, PB 10.2.1 9948
WBR, Oleg
unknown
2008-06-06 13:41:17 UTC
Permalink
Hi!
Post by Chris Pollach
What is in the SQLErrText ?
"Error: Failed to get a valid Database Connection from
Jaguar yet no error was returned from the Jaguar Server!"

Serve.log:
--------
ERROR HttpListener0-0 [OdbcConnection] ODBCError: SQLError:
18456, SQLState: 28000, Msg: [Microsoft][ODBC SQL Server
Driver][SQL Server]Login failed for user 'user0'..
INFO HttpListener0-0 [SystemException]
com.sybase.djc.DataStoreException was thrown by method
com.sybase.jaguar.jcm.JagCm.getConnection
INFO HttpListener0-0 com.sybase.djc.DataStoreException:
Connection Failed: java.sql.SQLException: Error connecting
to database - see log file for details.
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionPool.createConnection(ConnectionPool.java:734)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionPool.getConnectionHandle(ConnectionPool.java:229)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionPool.getConnection(ConnectionPool.java:196)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionPool.getConnection(ConnectionPool.java:160)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionWrapper.checkOpen(ConnectionWrapper.java:203)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionWrapper.getConnection(ConnectionWrapper.java:176)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionWrapper_DJC.nativeSQL(ConnectionWrapper_DJC.java:102)
INFO HttpListener0-0 at
com.sybase.jaguar.jcm.JagCm.getConnection(JagCm.java:172)
INFO HttpListener0-0 at
com.sybase.jaguar.server.JaguarObject.invoke(Native Method)
INFO HttpListener0-0 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:289)
INFO HttpListener0-0 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:97)
INFO HttpListener0-0 at
com.sybase.jaguar.server.JaguarObject_DJC.invoke(JaguarObject_DJC.java:333)


WBR, Oleg.
Post by Chris Pollach
--
Regards ... Chris
http://chrispollach.pbdjmagazine.com
Post by unknown
Post by Evan Ireland
Post by Stelios Vasiliadis
we get the following error (in
sqlerrtext property) when a component in jaguar tries
to connect to the database (ASE 12.5.3 ESD 4)
"Failed to get a valid Database Connection from Jaguar
yet no error was returned"
Also sqlcode returns -1 and SQLDBCode returns 999
Is there anything logged in the server log file (in
logs/xxx.log)?
I have a same error if to specify the incorrect
login/password. I use ODBC without a connection cache.
How to receive a code of a real error in SQLCA.
EAS 6.0.1.14, PB 10.2.1 9948
WBR, Oleg
Chris Pollach
2008-06-09 11:18:03 UTC
Permalink
Oleg;

Looks like a Login failure ...

=>SQLState: 28000, Msg: [Microsoft][ODBC SQL Server
Driver][SQL Server]Login failed for user 'user0'..
--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com
Post by unknown
Hi!
Post by Chris Pollach
What is in the SQLErrText ?
"Error: Failed to get a valid Database Connection from
Jaguar yet no error was returned from the Jaguar Server!"
--------
18456, SQLState: 28000, Msg: [Microsoft][ODBC SQL Server
Driver][SQL Server]Login failed for user 'user0'..
INFO HttpListener0-0 [SystemException]
com.sybase.djc.DataStoreException was thrown by method
com.sybase.jaguar.jcm.JagCm.getConnection
Connection Failed: java.sql.SQLException: Error connecting
to database - see log file for details.
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionPool.createConnection(ConnectionPool.java:734)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionPool.getConnectionHandle(ConnectionPool.java:229)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionPool.getConnection(ConnectionPool.java:196)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionPool.getConnection(ConnectionPool.java:160)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionWrapper.checkOpen(ConnectionWrapper.java:203)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionWrapper.getConnection(ConnectionWrapper.java:176)
INFO HttpListener0-0 at
com.sybase.djc.sql.ConnectionWrapper_DJC.nativeSQL(ConnectionWrapper_DJC.java:102)
INFO HttpListener0-0 at
com.sybase.jaguar.jcm.JagCm.getConnection(JagCm.java:172)
INFO HttpListener0-0 at
com.sybase.jaguar.server.JaguarObject.invoke(Native Method)
INFO HttpListener0-0 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:289)
INFO HttpListener0-0 at
com.sybase.jaguar.server.JaguarObject.invoke(JaguarObject.java:97)
INFO HttpListener0-0 at
com.sybase.jaguar.server.JaguarObject_DJC.invoke(JaguarObject_DJC.java:333)
WBR, Oleg.
Post by Chris Pollach
--
Regards ... Chris
http://chrispollach.pbdjmagazine.com
Post by unknown
Post by Evan Ireland
Post by Stelios Vasiliadis
we get the following error (in
sqlerrtext property) when a component in jaguar tries
to connect to the database (ASE 12.5.3 ESD 4)
"Failed to get a valid Database Connection from Jaguar
yet no error was returned"
Also sqlcode returns -1 and SQLDBCode returns 999
Is there anything logged in the server log file (in
logs/xxx.log)?
I have a same error if to specify the incorrect
login/password. I use ODBC without a connection cache.
How to receive a code of a real error in SQLCA.
EAS 6.0.1.14, PB 10.2.1 9948
WBR, Oleg
Loading...