JZ00L:Login failed

[eitanfux]

Hi all,
I working with adaptive server anywhere 7, with Jconnect 4.2 and over
Jonas aplication server.
the database engine run as a NT service.
after working for 20-30 min I got the JZ00L: Login failed error.
its happen only with windows 2000 Server, not with 2000 profesional.
do you know why the connection failed?
who can I trace the pooling connection and/or the database activities
with sybase.
thanks
eitan
cisco system

--------------------------------------------------------------------------------------------------------------------

java.sql.SQLException: JZ00L: Login failed. Examine the SQLWarnings
chained to this exception for the reason(s).
at com.sybase.jdbc.ErrorMessage.raiseError(ErrorMessage.java)
at com.sybase.tds.Tds.processLoginAckToken(Tds.java)
at com.sybase.tds.Tds.doLogin(Tds.java)
at com.sybase.tds.Tds.login(Tds.java)
at com.sybase.jdbc.SybConnection.tryLogin(SybConnection.java)
at com.sybase.jdbc.SybConnection.regularConnect(SybConnection.java)
at com.sybase.jdbc.SybConnection.<init>(SybConnection.java)
at com.sybase.jdbc.SybDriver.connect(SybDriver.java)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:177)
at
org.objectweb.jonas.jdbc_xa.XADataSourceImpl.getXAConnection(XADataSourceImpl.java:163)

at
org.objectweb.jonas.dbm.ConnectionManager.getConnection(ConnectionManager.java:324)

at
org.objectweb.jonas.dbm.ConnectionManager.getConnection(ConnectionManager.java:293)

at
com.cisco.nm.qpm.server.framework.BaseEntity.getConnection(BaseEntity.java:289)

at
com.cisco.nm.qpm.server.framework.BaseEntity.getConnection(BaseEntity.java:253)

at
com.cisco.nm.qpm.server.framework.QueryEntity.ejbFindByFreeSQL(QueryEntity.java:39)

at
com.cisco.nm.qpm.server.framework.QueryEntity.ejbFindByCondition(QueryEntity.java:81)

at
com.cisco.nm.qpm.server.policy.db.ejb.JOnASPolicyDBEntityHome.findByCondition(classes\com\cisco\nm\qpm\server\policy\db\ejb\JOnASPolicyDBEntityHome.java:148)

at
com.cisco.nm.qpm.server.policy.db.ejb.JOnASPolicyDBEntityHome_Skel.dispatch(classes\com\cisco\nm\qpm\server\policy\db\ejb\JOnASPolicyDBEntityHome_Skel.java:111)

at
sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:319)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:187)
at sun.rmi.transport.Transport$1.run(Transport.java:142)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:139)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:443)

at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:643)

at java.lang.Thread.run(Thread.java:484)

[nick.elson@sybase.com Nick Elson]

I don't know the ObjectWeb Jonas product but
if it is J2EE compliant then you will probably need
to run JConnect 5.2 or 5.5. since that is the Java2
compatable driver. [Connnect 4.x is for Java 1.1.x
JVMs.]

Having said that, if you continue to have problems
with the compatable driver, you will want to post
the information on the

sybase.public.jconnect40
sybase.public.jconnect50

newsgroups. More JConncect expertise and
shared experience will be found there.

Other than that a login failure is probably
something specific and probably something
that is not a function of the OS.

You could always set up the auditing function to
do post mortems. You can also set up the server
with '-zr ALL -o file.txt' to capture all activity.

Since this is pure TDS, you can also install RIBO
if you chose to trace logins at that level (packet
sniffing that is). Ribo is a JConnect based utility
and it can usually be found at

... \Shared\jutils-2_0\ribo

if you installed those.

"eitanfux" <eita...@yahoo.com> wrote in message
news:3C83F551...@yahoo.com...

classes\com\cisco\nm\qpm\server\policy\db\ejb\JOnASPolicyDBEntityHome_Skel.j