Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - 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.

Jaguar Newbie question

3 posts in General Discussion (old) Last posting was on 2000-02-28 16:03:00.0Z
Thorsten Kummer Posted on 2000-02-28 14:19:16.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 28 Feb 2000 14:19:16 +0000
From: Thorsten Kummer <Kummer@planet.de>
X-Mailer: Mozilla 4.7 [de] (WinNT; I)
X-Accept-Language: de
MIME-Version: 1.0
Subject: Jaguar Newbie question
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 43
NNTP-Posting-Host: datenbank3.planet.de 194.59.16.226
Message-ID: <347_38BA83E4.190C0DB4@planet.de>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27670
Article PK: 159036

Hi,

we're new to jaguar and ran into a problem we could not deal with.

We tried to set up a sample EJB project as suggested in sybase developer
network (simple calculator application).
We followed the instructions given there, but when it comes to a first
test, our client application brings up the following
messages in the PowerJ debug log:

Logging started Feb 28, 2000 2:12:37 PM
PowerJ component library (PJClass) version 3.5.1 (debug)
setInitialCtxName : Name was "com.sybase.ejb.InitialContextFactory"
changed to "com.sybase.ejb.InitialContextFactory"
SettingContextForEJB true
setUser: new user is jagadmin
setPassword: new password is
setURL: new URL is iiop://localhost:9000
connect: trigger event: Connecting
connect: Connecting using javax.naming
User:: jagadmin
Password::
Factory:: com.sybase.ejb.InitialContextFactory
About to create javax.naming.InitialContext in connectUsingJavaxNaming()

Listing Arguments --
Listing Properties --
java.naming.security.credentials =
java.naming.factory.initial = com.sybase.ejb.InitialContextFactory
java.naming.provider.url = iiop://localhost:9000
java.naming.security.principal = jagadmin
connect: trigger event: Connected
lookup: component Calculator connected=true useJavaxNaming=true
javax.naming lookup failed for component: Calculator
Exception: [Root exception is org.omg.CORBA.BAD_OPERATION: The delegate
has not been set! minor code: 0 completed:
No]javax.naming.NamingException

What goes wrong???
I think, the last two lines of the debug log are the ones that couse the
problems.
Could somebody of you help us?

Thanks in advance from Germany

Thorsten


Jim O'Neil [Sybase] Posted on 2000-02-28 14:27:06.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 28 Feb 2000 09:27:06 -0500
From: "Jim O'Neil [Sybase]" <joneil@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Jaguar Newbie question
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 54
NNTP-Posting-Host: joneil-nt.sybase.com 204.167.42.111
Message-ID: <347_38BA85BA.65C95F35@sybase.com>
References: <347_38BA83E4.190C0DB4@planet.de>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27667
Article PK: 159033


Thorsten Kummer wrote:

> Hi,
>
> we're new to jaguar and ran into a problem we could not deal with.
>
> We tried to set up a sample EJB project as suggested in sybase developer
> network (simple calculator application).
> We followed the instructions given there, but when it comes to a first
> test, our client application brings up the following
> messages in the PowerJ debug log:
>
> Logging started Feb 28, 2000 2:12:37 PM
> PowerJ component library (PJClass) version 3.5.1 (debug)
> setInitialCtxName : Name was "com.sybase.ejb.InitialContextFactory"
> changed to "com.sybase.ejb.InitialContextFactory"
> SettingContextForEJB true
> setUser: new user is jagadmin
> setPassword: new password is
> setURL: new URL is iiop://localhost:9000
> connect: trigger event: Connecting
> connect: Connecting using javax.naming
> User:: jagadmin
> Password::
> Factory:: com.sybase.ejb.InitialContextFactory
> About to create javax.naming.InitialContext in connectUsingJavaxNaming()
>
> Listing Arguments --
> Listing Properties --
> java.naming.security.credentials =
> java.naming.factory.initial = com.sybase.ejb.InitialContextFactory
> java.naming.provider.url = iiop://localhost:9000
> java.naming.security.principal = jagadmin
> connect: trigger event: Connected
> lookup: component Calculator connected=true useJavaxNaming=true
> javax.naming lookup failed for component: Calculator
> Exception: [Root exception is org.omg.CORBA.BAD_OPERATION: The delegate
> has not been set! minor code: 0 completed:
> No]javax.naming.NamingException
>
> What goes wrong???
> I think, the last two lines of the debug log are the ones that couse the
> problems.
> Could somebody of you help us?
>
> Thanks in advance from Germany
>
> Thorsten

This is more Dave's turf, but from what I recall this message is what you
get when you're using a Java 1.2 client and it's known bug that has either
been recently fixed or will be soon. Can you downgrade to a 1.1.x client to
confirm that it works there?
--
Jim O'Neil
Senior Technical Support Engineer
Sybase, Inc


Thorsten Kummer Posted on 2000-02-28 16:03:00.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 28 Feb 2000 16:03:00 +0000
From: Thorsten Kummer <Kummer@planet.de>
X-Mailer: Mozilla 4.7 [de] (WinNT; I)
X-Accept-Language: de
MIME-Version: 1.0
Subject: Re: Jaguar Newbie question
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 60
NNTP-Posting-Host: datenbank3.planet.de 194.59.16.226
Message-ID: <347_38BA9C34.1F765C80@planet.de>
References: <347_38BA83E4.190C0DB4@planet.de> <347_38BA85BA.65C95F35@sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27665
Article PK: 159032

Please note that it works with a 1.1.8_002 Client.
Thanks for help.

Regards
Thorsten

"Jim O'Neil [Sybase]" schrieb:

> Thorsten Kummer wrote:
>
> > Hi,
> >
> > we're new to jaguar and ran into a problem we could not deal with.
> >
> > We tried to set up a sample EJB project as suggested in sybase developer
> > network (simple calculator application).
> > We followed the instructions given there, but when it comes to a first
> > test, our client application brings up the following
> > messages in the PowerJ debug log:
> >
> > Logging started Feb 28, 2000 2:12:37 PM
> > PowerJ component library (PJClass) version 3.5.1 (debug)
> > setInitialCtxName : Name was "com.sybase.ejb.InitialContextFactory"
> > changed to "com.sybase.ejb.InitialContextFactory"
> > SettingContextForEJB true
> > setUser: new user is jagadmin
> > setPassword: new password is
> > setURL: new URL is iiop://localhost:9000
> > connect: trigger event: Connecting
> > connect: Connecting using javax.naming
> > User:: jagadmin
> > Password::
> > Factory:: com.sybase.ejb.InitialContextFactory
> > About to create javax.naming.InitialContext in connectUsingJavaxNaming()
> >
> > Listing Arguments --
> > Listing Properties --
> > java.naming.security.credentials =
> > java.naming.factory.initial = com.sybase.ejb.InitialContextFactory
> > java.naming.provider.url = iiop://localhost:9000
> > java.naming.security.principal = jagadmin
> > connect: trigger event: Connected
> > lookup: component Calculator connected=true useJavaxNaming=true
> > javax.naming lookup failed for component: Calculator
> > Exception: [Root exception is org.omg.CORBA.BAD_OPERATION: The delegate
> > has not been set! minor code: 0 completed:
> > No]javax.naming.NamingException
> >
> > What goes wrong???
> > I think, the last two lines of the debug log are the ones that couse the
> > problems.
> > Could somebody of you help us?
> >
> > Thanks in advance from Germany
> >
> > Thorsten
>
> This is more Dave's turf, but from what I recall this message is what you
> get when you're using a Java 1.2 client and it's known bug that has either
> been recently fixed or will be soon. Can you downgrade to a 1.1.x client to
> confirm that it works there?
> --
> Jim O'Neil
> Senior Technical Support Engineer
> Sybase, Inc