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.

createJavaVM (yet again)

2 posts in EJB Client Last posting was on 2010-07-01 14:44:28.0Z
Dale H. Shipman Posted on 2009-03-09 18:42:53.0Z
Sender: 6faf.49b55ef3.1804289383@sybase.com
From: Dale H. Shipman
Newsgroups: sybase.public.powerbuilder.ejbclient
Subject: createJavaVM (yet again)
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <49b5632d.7046.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 9 Mar 2009 10:42:53 -0800
X-Trace: forums-1-dub 1236624173 10.22.241.41 (9 Mar 2009 10:42:53 -0800)
X-Original-Trace: 9 Mar 2009 10:42:53 -0800, 10.22.241.41
Lines: 39
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.ejbclient:810
Article PK: 424901

I have developed a test application that successfully
fetches an EJB from a WebSphere 6.1 server using either the
IBM SDK50 or SDK60 when in the development environment;
however, when compiled, said application fails to load the
JVM.

I've been through every related thread in this discussion
and have double and triple checked all of the environment
and registry settings and still no joy. That said, if I
clear the JDK directory (and all subdirectories), and
overlay it with the JDK14 that came with PowerBuilder
(currently running 10.0), the application has no problem
starting the JVM. So, unless I'm missing something, the
various registry settings and environment variables must be
set correctly or the JVM in the JDK14 wouldn't successfully
start. Yes, no?

In all cases I have the java implementation stored in the
default C:\Program Files\Sybase\Shared\PowerBuilder\jdk14
directory. By simply changing out the contents of the
..\jdk14 directory with various JDKs and SDKs, I get the
following results:

Development environment:
Sybase sourced JDK (1.4.0): JVM starts, however, Lookup
fails.
IBM sourced SDK50 (1.5.0): JVM starts and application works.
IBM sourced SDK60 (1.6.0): JVM starts and application works.

Compiled / Runtime environment:
Sybase sourced JDK (1.4.0): JVM starts, however, Lookup
fails.
IBM sourced SDK50 (1.5.0): JVM fails to start.
IBM sourced SDK60 (1.6.0): JVM fails to start.

Is there something about the runtime environment that
prevents any IBM SDK version of Java from running?

Thanks in advance for your help in this matter.


Murat Yelkovan Posted on 2010-07-01 14:44:28.0Z
From: "Murat Yelkovan" <muratyelkovan@yahoo.com>
Newsgroups: sybase.public.powerbuilder.ejbclient
References: <49b5632d.7046.1681692777@sybase.com>
Subject: Re: createJavaVM (yet again)
Lines: 55
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4c2ca9cc$1@forums-1-dub>
Date: 1 Jul 2010 07:44:28 -0700
X-Trace: forums-1-dub 1277995468 10.22.241.152 (1 Jul 2010 07:44:28 -0700)
X-Original-Trace: 1 Jul 2010 07:44:28 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.ejbclient:817
Article PK: 424908

Hi

Try to copy these files to the application directory.
pbejbclient115.jar
pbejbclient115.pbd
pbejbclient115.pbx
pbjdbc12115.jar
PBjvm115.DLL

Add jdk directory to the system path. Example : c:\jdk1.4\jre\bin\client;

<Dale H. Shipman> wrote in message
news:49b5632d.7046.1681692777@sybase.com...
>I have developed a test application that successfully
> fetches an EJB from a WebSphere 6.1 server using either the
> IBM SDK50 or SDK60 when in the development environment;
> however, when compiled, said application fails to load the
> JVM.
>
> I've been through every related thread in this discussion
> and have double and triple checked all of the environment
> and registry settings and still no joy. That said, if I
> clear the JDK directory (and all subdirectories), and
> overlay it with the JDK14 that came with PowerBuilder
> (currently running 10.0), the application has no problem
> starting the JVM. So, unless I'm missing something, the
> various registry settings and environment variables must be
> set correctly or the JVM in the JDK14 wouldn't successfully
> start. Yes, no?
>
> In all cases I have the java implementation stored in the
> default C:\Program Files\Sybase\Shared\PowerBuilder\jdk14
> directory. By simply changing out the contents of the
> ..\jdk14 directory with various JDKs and SDKs, I get the
> following results:
>
> Development environment:
> Sybase sourced JDK (1.4.0): JVM starts, however, Lookup
> fails.
> IBM sourced SDK50 (1.5.0): JVM starts and application works.
> IBM sourced SDK60 (1.6.0): JVM starts and application works.
>
> Compiled / Runtime environment:
> Sybase sourced JDK (1.4.0): JVM starts, however, Lookup
> fails.
> IBM sourced SDK50 (1.5.0): JVM fails to start.
> IBM sourced SDK60 (1.6.0): JVM fails to start.
>
> Is there something about the runtime environment that
> prevents any IBM SDK version of Java from running?
>
> Thanks in advance for your help in this matter.