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.

JVM logging questions

2 posts in EJB Client Last posting was on 2006-03-29 11:33:38.0Z
Bede <bede_nosp Posted on 2006-02-16 16:08:39.0Z
From: Bede <bede_nosp@m_sofico.be>
Newsgroups: sybase.public.powerbuilder.ejbclient
Subject: JVM logging questions
Message-ID: <MPG.1e5eb2c44616d4df98978c@forums.sybase.com>
Organization: Sofico
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
User-Agent: MicroPlanet-Gravity/2.70.2067
NNTP-Posting-Host: uu194-7-38-226.unknown.uunet.be
X-Original-NNTP-Posting-Host: uu194-7-38-226.unknown.uunet.be
Date: 16 Feb 2006 08:08:39 -0800
X-Trace: forums-1-dub 1140106119 194.7.38.226 (16 Feb 2006 08:08:39 -0800)
X-Original-Trace: 16 Feb 2006 08:08:39 -0800, uu194-7-38-226.unknown.uunet.be
Lines: 39
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.ejbclient:626
Article PK: 424748

Does anyone have any information (official or not) on the following:

1. Sybase is stating (see http://www.sybase.com/detail?id=1031011
#BABJACID ) that it are limitations in Sun JDK 1.4, that are the causing
the JDK 1.4 VM.OUT logging not to be possible, and that the customer
should use JDK1.3 to get logging.
However, when trying to dig a bit deaper into the reason how/why JDK
would be causing this exaclty, a Sybase official states: "I cannot give
you more informations about what exactly cause this problem because it's
for Sybase internal use only."
=> This is basically admitting that the problem originates from the
ejbclient layer in PB and not the jdk.

Secondly, the fact that we should workaround this issue by using JDK1.3
is not a possibility, simply because our java classes use JDK1.4 and
cannot run on JDK 1.3.


2. When will JDK 1.4 and later java version be supported? Obviously
we'll need this to work with future releases of both PB and java as
well.

3. We would like to know if / when to expect it to be
possible to log data/stacktraces/... into this VM.OUT logfile from
within the java classes at the PB client. Also, the VM.OUT logging
should include everything that the java classes write to STDOUT.

4. Alternatively, it would be a big improvement to have a getStackTrace
() method on Throwable. When an error occurs in a java class a
StackTrace is generated (on java side). Unfortunately, this StackTrace -
which holds crucial information in order to find the root cause of the
problem- is not retained in the PowerBuilder Error which is thrown.


Any info, thoughs would be really helpful.
TIA,

Ben


Bede <bede_nosp Posted on 2006-03-29 11:33:38.0Z
From: Bede <bede_nosp@m_sofico.be>
Newsgroups: sybase.public.powerbuilder.ejbclient
Subject: Re: JVM logging questions
Message-ID: <MPG.1e947eea5229e77e989796@forums.sybase.com>
References: <MPG.1e5eb2c44616d4df98978c@forums.sybase.com>
Organization: Sofico
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
User-Agent: MicroPlanet-Gravity/2.70.2067
X-Original-NNTP-Posting-Host: uu194-7-38-226.unknown.uunet.be
X-Original-Trace: 29 Mar 2006 02:24:46 -0800, uu194-7-38-226.unknown.uunet.be
Lines: 60
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 29 Mar 2006 02:24:48 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 29 Mar 2006 03:33:38 -0800
X-Trace: forums-1-dub 1143632018 10.22.108.75 (29 Mar 2006 03:33:38 -0800)
X-Original-Trace: 29 Mar 2006 03:33:38 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.ejbclient:630
Article PK: 424749

finally got a solution for the first problem.
You can get logging for JDK/JRE 1.4 when you use the following registry
settings:

[HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\PowerBuilder\9.0\Java\PBIDEConfig
\PBJVMconfig]
"Count"="3"
"0"="-verbose:jni"
"1"="-verbose:class"
"2"="-verbose:gc"

don't know why this was such a big secret

Cheers,

ben


In article <MPG.1e5eb2c44616d4df98978c@forums.sybase.com>,
bede_nosp@m_sofico.be says...

> Does anyone have any information (official or not) on the following:
>
> 1. Sybase is stating (see http://www.sybase.com/detail?id=1031011
> #BABJACID ) that it are limitations in Sun JDK 1.4, that are the causing
> the JDK 1.4 VM.OUT logging not to be possible, and that the customer
> should use JDK1.3 to get logging.
> However, when trying to dig a bit deaper into the reason how/why JDK
> would be causing this exaclty, a Sybase official states: "I cannot give
> you more informations about what exactly cause this problem because it's
> for Sybase internal use only."
> => This is basically admitting that the problem originates from the
> ejbclient layer in PB and not the jdk.
>
> Secondly, the fact that we should workaround this issue by using JDK1.3
> is not a possibility, simply because our java classes use JDK1.4 and
> cannot run on JDK 1.3.
>
>
> 2. When will JDK 1.4 and later java version be supported? Obviously
> we'll need this to work with future releases of both PB and java as
> well.
>
> 3. We would like to know if / when to expect it to be
> possible to log data/stacktraces/... into this VM.OUT logfile from
> within the java classes at the PB client. Also, the VM.OUT logging
> should include everything that the java classes write to STDOUT.
>
> 4. Alternatively, it would be a big improvement to have a getStackTrace
> () method on Throwable. When an error occurs in a java class a
> StackTrace is generated (on java side). Unfortunately, this StackTrace -
> which holds crucial information in order to find the root cause of the
> problem- is not retained in the PowerBuilder Error which is thrown.
>
>
> Any info, thoughs would be really helpful.
> TIA,
>
> Ben
>
>