Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.


2 posts in JConnect version 3.0 Last posting was on 2001-03-13 13:07:11.0Z
Graeme Manning Posted on 2000-12-06 01:04:33.0Z
Message-ID: <>
Date: Tue, 05 Dec 2000 18:04:33 -0700
From: Graeme Manning <>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: MissingResourceException
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jconnect30
Lines: 28
Path: forums-1-dub!!
Xref: forums-1-dub sybase.public.jconnect30:204
Article PK: 256603

I get the following error when running my app from a jar file crearted
from VisualCafe.

java.util.MissingResourceException: Can't find resource for base name
.jdbc.resource.Messages, locale en_US
at java.util.ResourceBundle.getBundle(
at java.util.ResourceBundle.getBundle(
at com.sybase.jdbc.ErrorMessage.<clinit>(
at com.sybase.jdbc.SybDriver.connect(
at java.sql.DriverManager.getConnection(
at java.sql.DriverManager.getConnection(
at Database.ConnectionPool.initialise(,
Compiled Code
at Database.ConnectionPool.Initialise(
at Site.PPPrintSiteAppMgr.startApp(
at Site.PPPrintSiteAppMgr.main(

com.sybase.jdbc.resource does not contain Messages_en_US

Any ideas?


lance.andersen Posted on 2001-03-13 13:07:11.0Z
Date: Tue, 13 Mar 2001 08:07:11 -0500
Newsgroups: sybase.public.jconnect30
Subject: Re: MissingResourceException
Message-ID: <19B1E1528F645CD9004811C385256A0E.000871E0852569AD@webforums>
References: <>
Lines: 7
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!!!!news
Xref: forums-1-dub sybase.public.jconnect30:191
Article PK: 256596

This error is due to a bug in the JVM you are using. We
have provided relief via the latest 4.2 and 5.2 ebfs to
this issue.

You can also work around this by creating the class that
fails and have it extend from Messages and be an empty class.