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.

javax.naming lookup failed

4 posts in General Discussion (old) Last posting was on 2000-03-19 07:54:41.0Z
Yuhong Liu Posted on 2000-03-17 14:36:33.0Z
Newsgroups: sybase.public.easerver
Reply-To: "Yuhong Liu" <yliu@si-ecc.com>
From: "Yuhong Liu" <yliu@si-ecc.com>
Subject: javax.naming lookup failed
Date: Fri, 17 Mar 2000 09:36:33 -0500
Lines: 21
Organization: SI-ECC
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: 207.18.189.46
Message-ID: <347_2773$5Bk$GA.111@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26210
Article PK: 156877

Hi,

I created a very simple stateless session bean and deploy it to Jagaur. Then
I created a client to call it. I did it just like instructed in PJ help: "
Creating EJB client applications"

But I got:
....
lookup: component Bean1 connected=true useJavaxNaming=true
javax.naming lookup failed for component: Bean1
Exception: [Root exception is org.omg.CORBA.BAD_OPERATION: The delegate has
not been set! minor code: 0 completed: No]javax.naming.NamingException


What did I miss here?


Yuhong Liu
yliu@si-ecc.com


Andreas S. Brunvoll Posted on 2000-03-17 14:44:35.0Z
Newsgroups: sybase.public.easerver
Date: Fri, 17 Mar 2000 15:44:35 +0100
From: "Andreas S. Brunvoll" <abr@avenir.no>
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: javax.naming lookup failed
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 24
NNTP-Posting-Host: 139.108.179.131
Message-ID: <347_38D244D3.D8251DCB@avenir.no>
References: <347_2773$5Bk$GA.111@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26209
Article PK: 156878

It could be that you are using JDK 1.2 at the client application. There is a bug in the 1.2 implementation that forces you to use JDK 1.1.x at the EJB-client. See earlier postings regarding the subject.

Andreas

Yuhong Liu wrote:

Hi,

I created a very simple stateless session bean and deploy it to Jagaur. Then
I created a client to call it. I did it just like instructed in PJ help: "
Creating EJB client applications"

But I got:
....
lookup: component Bean1 connected=true useJavaxNaming=true
javax.naming lookup failed for component: Bean1
Exception: [Root exception is org.omg.CORBA.BAD_OPERATION: The delegate has
not been set!  minor code: 0  completed: No]javax.naming.NamingException

What did I miss here?

Yuhong Liu
yliu@si-ecc.com


Vitaly Geraymovych Posted on 2000-03-17 21:33:09.0Z
Newsgroups: sybase.public.easerver
Date: Fri, 17 Mar 2000 16:33:09 -0500
From: Vitaly Geraymovych <vitaly@cavasoft.com>
Reply-To: vitaly@cavasoft.com
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: javax.naming lookup failed
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 26
NNTP-Posting-Host: newt.westat.com 198.232.250.51
Message-ID: <347_38D2A494.CA4CC7F@cavasoft.com>
References: <347_2773$5Bk$GA.111@forums.sybase.com> <347_38D244D3.D8251DCB@avenir.no>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26157
Article PK: 156835

Andreas,

Who is responsible for this bug: Jaguar or JDK 1.2. Just curious when
some fix will arrive.

Thanks,
Vitaly

"Andreas S. Brunvoll" wrote:

> It could be that you are using JDK 1.2 at the client application.
> There is a bug in the 1.2 implementation that forces you to use JDK
> 1.1.x at the EJB-client. See earlier postings regarding the subject.
>
> Andreas
>
> Yuhong Liu wrote:
>
>> Hi,
>>
>> I created a very simple stateless session bean and deploy it to
>> Jagaur. Then
>> I created a client to call it. I did it just like instructed in PJ
>> help: "
>> Creating EJB client applications"
>>
>> But I got:
>> ....
>> lookup: component Bean1 connected=true useJavaxNaming=true
>> javax.naming lookup failed for component: Bean1
>> Exception: [Root exception is org.omg.CORBA.BAD_OPERATION: The
>> delegate has
>> not been set! minor code: 0 completed:
>> No]javax.naming.NamingException
>>
>> What did I miss here?
>>
>> Yuhong Liu
>> yliu@si-ecc.com
>


Dave Wolf [Sybase] Posted on 2000-03-19 07:54:41.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: javax.naming lookup failed
Date: Sun, 19 Mar 2000 02:54:41 -0500
Lines: 53
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
NNTP-Posting-Host: vpn-eme-010.sybase.com 130.214.8.10
Message-ID: <347_S39t9jXk$GA.285@forums.sybase.com>
References: <347_2773$5Bk$GA.111@forums.sybase.com> <347_38D244D3.D8251DCB@avenir.no> <347_38D2A494.CA4CC7F@cavasoft.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:26119
Article PK: 156803

The "bug" is caused by a change in the classes distributed by the Java2 VM
in combination with how the Java2 VM loads classes. This broke some
functionality we had. We have fixed the bug in EAS and the fix is pending
within weeks. Please contact support to get on the list for the fix.

Dave Wolf
Internet Applications Division

"Vitaly Geraymovych" <vitaly@cavasoft.com> wrote in message
news:38D2A494.CA4CC7F@cavasoft.com...
> Andreas,
>
> Who is responsible for this bug: Jaguar or JDK 1.2. Just curious when
> some fix will arrive.
>
> Thanks,
> Vitaly
>
> "Andreas S. Brunvoll" wrote:
>
> > It could be that you are using JDK 1.2 at the client application.
> > There is a bug in the 1.2 implementation that forces you to use JDK
> > 1.1.x at the EJB-client. See earlier postings regarding the subject.
> >
> > Andreas
> >
> > Yuhong Liu wrote:
> >
> >> Hi,
> >>
> >> I created a very simple stateless session bean and deploy it to
> >> Jagaur. Then
> >> I created a client to call it. I did it just like instructed in PJ
> >> help: "
> >> Creating EJB client applications"
> >>
> >> But I got:
> >> ....
> >> lookup: component Bean1 connected=true useJavaxNaming=true
> >> javax.naming lookup failed for component: Bean1
> >> Exception: [Root exception is org.omg.CORBA.BAD_OPERATION: The
> >> delegate has
> >> not been set! minor code: 0 completed:
> >> No]javax.naming.NamingException
> >>
> >> What did I miss here?
> >>
> >> Yuhong Liu
> >> yliu@si-ecc.com
> >
>