🚀 go-pugleaf

Hi Sergio,

You're right -- my mistake.  The list below does say:
"BEA WebLogic Server 8 (Sun JDK 1.4.1_02)"
... with no mention of BEA WebLogic Server 7 (for Solaris).

In this case, please follow the directions in Help section, located within the Optimizeit ServerTrace GUI, on how to
integrate with other appservers.  There's no reason why your configuration would not be a valid one -- this
configuration was simply was not QA-certified.

I'd be curious to know the results of your test, if you'd like to share them.

Regards,
- Will

________________________________________
From: Sergio Zu�iga [mailto:sezunigab@yahoo.com]
Sent: Friday, February 06, 2004 8:39 AM
To: Will McQueen
Subject: Re: ServerTrace in Solaris 8 and Weblogic 7

Hi Will,

The readme.txt file, is in the servertrace dir, in windows, and it's exactly as in your post. In the company where i work, we have purchased a license of the Optimizeit ServerTrace, but, we have Solaris 8
and weblogic 7, that's why i asked this, beacause we don�t know if this configuration will actually works.
So, its only certified with weblogic 8, not 7,then we have to test the configuration.

Thanks Will.


Will McQueen wrote:

> Hi Sergio,
>
> Below are snippets from the ServerTrace 2.0 readme.txt file from the Windows build.  Where exactly did you get the Readme.txt file that you refer to?  Could you please email it to me?  The configuration
> you mentioned is indeed included in the list below.
>
> If a configuration isn't listed, it means that it was not fully QA-Certified.  This doesn't necessarily mean that the configuration won't be possible -- just that it hasn't been tested.  If you are a
> current customer, please feel free to try any configurations not listed.  If you are considering a purchase of ServerTrace, please contact Sales for more info.  Sales might be able to provide you with a
> trial copy.
>
> Hope this helps,
> - Will
>
> ServerTrace currently supports these server-side operating systems:
>     * Microsoft Windows 2000/NT
>     * Microsoft Windows XP
>     * Sun Solaris 7 (2.7), 8 (2.8), and 9 (2.9)
>     * Red Hat Linux 7.2, Red Hat Linux 8, and Enterprise Linux WS 2.1
>     * HP-UX 11
>     * IBM AIX version 4.3.3, AIX 5L version 5.1
>
>   Windows 2000/NT, XP
>     * Borland Enterprise Server 5.2.1 (Sun JDK 1.4.1)
>     * BEA WebLogic Server 6 (Sun JDK 1.3.1)
>     * BEA WebLogic Server 7 (Sun JDK 1.3.1_06)
>     * BEA WebLogic Server 8 (Sun JDK 1.4.1_02, WebLogic JRockit JVM)
>     * IBM WebSphere 3.5 (IBM JDK 1.2.2)
>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
>     * JBoss 3.2 (Sun JDK 1.3.1)
>     * Macromedia JRun 4 (Sun JDK 1.3.1))
>     * Oracle9iAS J2EE (Sun JDK 1.3.1_02)
>     * Tomcat 3.3 (Sun JDK 1.3.1)
>     * Tomcat 4.1 (Sun JDK 1.3.1)
>   Solaris 7, 8, and 9
>     * BEA WebLogic Server 8 (Sun JDK 1.4.1_02)
>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
>     * Oracle9iAS J2EE (Sun JDK 1.3.1_02)
>     * iPlanet 6.5 (Sun JDK 1.3.1)
>   Red Hat Linux 7.2, and 8
>     * Borland Enterprise Server 5.2.1 (Sun JDK 1.4.1)
>     * BEA WebLogic Server 6 (Sun JDK 1.3.1)
>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
>     * JBoss 3.2 (Sun JDK 1.3.1)
>   Red Hat Enterprise Linux WS 2.1
>     * Borland Enterprise Server 5.2.1 (Sun JDK 1.4.1)
>     * BEA WebLogic Server 7 (Sun JDK 1.3.1_06)
>     * BEA WebLogic Server 8 (Sun JDK 1.4.1_02, WebLogic JRockit JVM)
>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
>     * Tomcat 3.3 (Sun JDK 1.3.1)
>     * Tomcat 4.1 (Sun JDK 1.3.1)
>   HP-UX 11
>     * Oracle9iAS J2EE (Sun JDK 1.3.1)
>     * BEA WebLogic Server 6, 7 (Sun JDK 1.3.1)
>     * Tomcat 4 (Sun JDK 1.3.1)
>   AIX 4.3.3
>     * JBoss 3.2 (IBM JDK 1.3.1)
>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
>     * BEA WebLogic Server 7 (IBM JDK 1.3.1)
>   AIX 5.1
>     * Borland Enterprise Server 5.2.1 (IBM JDK 1.4.1)
>     * JBoss 3.2 (IBM JDK 1.3.1)
>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
>     * BEA WebLogic Server 7 (IBM JDK 1.3.1)
>     * BEA WebLogic Server 8 (IBM JDK 1.4.1)
>
> Sergio Zuniga wrote:
>
> > Hello, i've read in a readme.txt file of server trace 2.0, that solaris 8 and weblogic 7 are not supported for installing Optimizeit serverTrace 2.0. Is there an update or a patch for this situation ??
> >
> > Thanks

Hi,

I have a problem in an environment similar to the one mentioned on this thread. I am trying to run Optimizeit ServerTrace Version 1.1 Developer Edition on Solaris 9 with JDK 1.3.1_08 and weblogic 7.0.

I have set following settings as per notes in integration section.

$OPTIT_HOME=<strace-install-location>

JVM_OPTIONS = "-Xrunoii:filter=$OPTIT_HOME/filters/WebLogic.oif -Xbootclasspath/a:$OPTIT_HOME/lib/oibcp.jar"

export CLASSPATH=$CLASSPATH:$OPTIT_HOME/lib/optit.jar
export LD_LIBRARY_PATH=$OPTIT_HOME/lib:$LD_LIBRARY_PATH


When I try to run the program, I get following error.


Optimizeit Error: the library libpri.so could not be loaded because <ld.so.1: /usr/local/share/j2sdk1_3_1_08/bin/../bin/sparc/native_threads/java: fatal: libpri.so: open failed: No such file or directory>.
Make sure to set your LD_LIBRARY_PATH so it includes Optimizeit lib and ext directories.
Optimizeit Error: Exiting...

I have managed to run the same installation with SunOne application server using JDK 1.4.1_02.


Any help would be appreciated. 

Thanks,
Manish



Will McQueen <wmcqueen@borland.com> wrote:
>Hi Sergio,
>
>You're right -- my mistake.  The list below does say:
>"BEA WebLogic Server 8 (Sun JDK 1.4.1_02)"
>... with no mention of BEA WebLogic Server 7 (for Solaris).
>
>In this case, please follow the directions in Help section, located within the Optimizeit ServerTrace GUI, on how to
>integrate with other appservers.  There's no reason why your configuration would not be a valid one -- this
>configuration was simply was not QA-certified.
>
>I'd be curious to know the results of your test, if you'd like to share them.
>
>Regards,
>- Will
>
>________________________________________
>From: Sergio Zu�iga [mailto:sezunigab@yahoo.com]
>Sent: Friday, February 06, 2004 8:39 AM
>To: Will McQueen
>Subject: Re: ServerTrace in Solaris 8 and Weblogic 7
>
>Hi Will,
>
>The readme.txt file, is in the servertrace dir, in windows, and it's exactly as in your post. In the company where i work, we have purchased a license of the Optimizeit ServerTrace, but, we have Solaris 8
>and weblogic 7, that's why i asked this, beacause we don�t know if this configuration will actually works.
>So, its only certified with weblogic 8, not 7,then we have to test the configuration.
>
>Thanks Will.
>
>
>Will McQueen wrote:
>
>> Hi Sergio,
>>
>> Below are snippets from the ServerTrace 2.0 readme.txt file from the Windows build.  Where exactly did you get the Readme.txt file that you refer to?  Could you please email it to me?  The configuration
>> you mentioned is indeed included in the list below.
>>
>> If a configuration isn't listed, it means that it was not fully QA-Certified.  This doesn't necessarily mean that the configuration won't be possible -- just that it hasn't been tested.  If you are a
>> current customer, please feel free to try any configurations not listed.  If you are considering a purchase of ServerTrace, please contact Sales for more info.  Sales might be able to provide you with a
>> trial copy.
>>
>> Hope this helps,
>> - Will
>>
>> ServerTrace currently supports these server-side operating systems:
>>     * Microsoft Windows 2000/NT
>>     * Microsoft Windows XP
>>     * Sun Solaris 7 (2.7), 8 (2.8), and 9 (2.9)
>>     * Red Hat Linux 7.2, Red Hat Linux 8, and Enterprise Linux WS 2.1
>>     * HP-UX 11
>>     * IBM AIX version 4.3.3, AIX 5L version 5.1
>>
>>   Windows 2000/NT, XP
>>     * Borland Enterprise Server 5.2.1 (Sun JDK 1.4.1)
>>     * BEA WebLogic Server 6 (Sun JDK 1.3.1)
>>     * BEA WebLogic Server 7 (Sun JDK 1.3.1_06)
>>     * BEA WebLogic Server 8 (Sun JDK 1.4.1_02, WebLogic JRockit JVM)
>>     * IBM WebSphere 3.5 (IBM JDK 1.2.2)
>>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
>>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
>>     * JBoss 3.2 (Sun JDK 1.3.1)
>>     * Macromedia JRun 4 (Sun JDK 1.3.1))
>>     * Oracle9iAS J2EE (Sun JDK 1.3.1_02)
>>     * Tomcat 3.3 (Sun JDK 1.3.1)
>>     * Tomcat 4.1 (Sun JDK 1.3.1)
>>   Solaris 7, 8, and 9
>>     * BEA WebLogic Server 8 (Sun JDK 1.4.1_02)
>>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
>>     * Oracle9iAS J2EE (Sun JDK 1.3.1_02)
>>     * iPlanet 6.5 (Sun JDK 1.3.1)
>>   Red Hat Linux 7.2, and 8
>>     * Borland Enterprise Server 5.2.1 (Sun JDK 1.4.1)
>>     * BEA WebLogic Server 6 (Sun JDK 1.3.1)
>>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
>>     * JBoss 3.2 (Sun JDK 1.3.1)
>>   Red Hat Enterprise Linux WS 2.1
>>     * Borland Enterprise Server 5.2.1 (Sun JDK 1.4.1)
>>     * BEA WebLogic Server 7 (Sun JDK 1.3.1_06)
>>     * BEA WebLogic Server 8 (Sun JDK 1.4.1_02, WebLogic JRockit JVM)
>>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
>>     * Tomcat 3.3 (Sun JDK 1.3.1)
>>     * Tomcat 4.1 (Sun JDK 1.3.1)
>>   HP-UX 11
>>     * Oracle9iAS J2EE (Sun JDK 1.3.1)
>>     * BEA WebLogic Server 6, 7 (Sun JDK 1.3.1)
>>     * Tomcat 4 (Sun JDK 1.3.1)
>>   AIX 4.3.3
>>     * JBoss 3.2 (IBM JDK 1.3.1)
>>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
>>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
>>     * BEA WebLogic Server 7 (IBM JDK 1.3.1)
>>   AIX 5.1
>>     * Borland Enterprise Server 5.2.1 (IBM JDK 1.4.1)
>>     * JBoss 3.2 (IBM JDK 1.3.1)
>>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
>>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
>>     * BEA WebLogic Server 7 (IBM JDK 1.3.1)
>>     * BEA WebLogic Server 8 (IBM JDK 1.4.1)
>>
>> Sergio Zuniga wrote:
>>
>> > Hello, i've read in a readme.txt file of server trace 2.0, that solaris 8 and weblogic 7 are not supported for installing Optimizeit serverTrace 2.0. Is there an update or a patch for this situation ??
>> >
>> > Thanks
>

Hi Manish,

Here's some background info:

These are the dll's used by each product:
    Optimizeit Profiler:  pri.dll
    Optimizeit Code Coverage:  cci.dll
    Optimizeit Thread Debugger:  tdi.dll
    Optimizeit ServerTrace:  j2i.dll

You have the option of specifying one of the above dll's in place of
oii.dll, but you need to append "startAudit=t" to the -Xrun command.  For
example
    -Xrunpri:startAudit=t,filter=...
    -Xruncci:startAudit=t,filter=...
    -Xruntdi:startAudit=t,filter=...
    -Xrunj2i:startAudit=t,filter=...

We prefer that the "oii.dll" is used instead:
    -Xrunoii:filter=...
Some advantages to this are:
    1)  You don't need to change your startup script each time you want to
use a different tool (PR, CC, TD, ST).  This requires you to use the
<ST_HOME>/
    2)  You don't need to include the "startAudit=t" option

Now that we have all that background info behind us, the error you're
getting is:
"libpri.so: open failed: No such file or directory".
There appears to be an attempt to use Optimizeit Profiler rather than
Optimizeit ServerTrace.  This could happen if your LD_LIBRARY_PATH points to
an Optimizeit Suite dir, which doesn't appear to be the case here.  It could
be that the oiselector is set to run Profiler instead of ServerTrace.  Try
running "<ST_HOME>/oiselector".  You should see something like:
    Selected tool:  ServerTrace
    Port range:  1473-1483

If the selected tool shows something different such as "Profiler", the run
"<ST_HOME>/oiselector -config" and choose ServerTrace.

The settings for oiselector are stored in your user home dir:  ".oi_audit"
("Optimizeit Audit System").  If you continue to have problems, please
include the contents of this file in your next newsgroup post.

Hope this helps,
- Will

"Manish" <shah_m@yahoo.com> wrote in message
news:404fc1c2$1@newsgroups.borland.com...
>
> Hi,
>
> I have a problem in an environment similar to the one mentioned on this
thread. I am trying to run Optimizeit ServerTrace Version 1.1 Developer
Edition on Solaris 9 with JDK 1.3.1_08 and weblogic 7.0.
>
> I have set following settings as per notes in integration section.
>
> $OPTIT_HOME=<strace-install-location>
>
> JVM_OPTIONS =
"-Xrunoii:filter=$OPTIT_HOME/filters/WebLogic.oif -Xbootclasspath/a:$OPTIT_H
OME/lib/oibcp.jar"
>
> export CLASSPATH=$CLASSPATH:$OPTIT_HOME/lib/optit.jar
> export LD_LIBRARY_PATH=$OPTIT_HOME/lib:$LD_LIBRARY_PATH
>
>
> When I try to run the program, I get following error.
>
>
> Optimizeit Error: the library libpri.so could not be loaded because
<ld.so.1:
/usr/local/share/j2sdk1_3_1_08/bin/../bin/sparc/native_threads/java: fatal:
libpri.so: open failed: No such file or directory>.
> Make sure to set your LD_LIBRARY_PATH so it includes Optimizeit lib and
ext directories.
> Optimizeit Error: Exiting...
>
> I have managed to run the same installation with SunOne application server
using JDK 1.4.1_02.
>
>
> Any help would be appreciated.
>
> Thanks,
> Manish
>
>
>
> Will McQueen <wmcqueen@borland.com> wrote:
> >Hi Sergio,
> >
> >You're right -- my mistake.  The list below does say:
> >"BEA WebLogic Server 8 (Sun JDK 1.4.1_02)"
> >... with no mention of BEA WebLogic Server 7 (for Solaris).
> >
> >In this case, please follow the directions in Help section, located
within the Optimizeit ServerTrace GUI, on how to
> >integrate with other appservers.  There's no reason why your
configuration would not be a valid one -- this
> >configuration was simply was not QA-certified.
> >
> >I'd be curious to know the results of your test, if you'd like to share
them.
> >
> >Regards,
> >- Will
> >
> >________________________________________
> >From: Sergio Zu�iga [mailto:sezunigab@yahoo.com]
> >Sent: Friday, February 06, 2004 8:39 AM
> >To: Will McQueen
> >Subject: Re: ServerTrace in Solaris 8 and Weblogic 7
> >
> >Hi Will,
> >
> >The readme.txt file, is in the servertrace dir, in windows, and it's
exactly as in your post. In the company where i work, we have purchased a li
cense of the Optimizeit ServerTrace, but, we have Solaris 8
> >and weblogic 7, that's why i asked this, beacause we don�t know if this
configuration will actually works.
> >So, its only certified with weblogic 8, not 7,then we have to test the
configuration.
> >
> >Thanks Will.
> >
> >
> >Will McQueen wrote:
> >
> >> Hi Sergio,
> >>
> >> Below are snippets from the ServerTrace 2.0 readme.txt file from the
Windows build.  Where exactly did you get the Readme.txt file that you refer
to?  Could you please email it to me?  The configuration
> >> you mentioned is indeed included in the list below.
> >>
> >> If a configuration isn't listed, it means that it was not fully
QA-Certified.  This doesn't necessarily mean that the configuration won't be
possible -- just that it hasn't been tested.  If you are a
> >> current customer, please feel free to try any configurations not
listed.  If you are considering a purchase of ServerTrace, please contact
Sales for more info.  Sales might be able to provide you with a
> >> trial copy.
> >>
> >> Hope this helps,
> >> - Will
> >>
> >> ServerTrace currently supports these server-side operating systems:
> >>     * Microsoft Windows 2000/NT
> >>     * Microsoft Windows XP
> >>     * Sun Solaris 7 (2.7), 8 (2.8), and 9 (2.9)
> >>     * Red Hat Linux 7.2, Red Hat Linux 8, and Enterprise Linux WS 2.1
> >>     * HP-UX 11
> >>     * IBM AIX version 4.3.3, AIX 5L version 5.1
> >>
> >>   Windows 2000/NT, XP
> >>     * Borland Enterprise Server 5.2.1 (Sun JDK 1.4.1)
> >>     * BEA WebLogic Server 6 (Sun JDK 1.3.1)
> >>     * BEA WebLogic Server 7 (Sun JDK 1.3.1_06)
> >>     * BEA WebLogic Server 8 (Sun JDK 1.4.1_02, WebLogic JRockit JVM)
> >>     * IBM WebSphere 3.5 (IBM JDK 1.2.2)
> >>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
> >>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
> >>     * JBoss 3.2 (Sun JDK 1.3.1)
> >>     * Macromedia JRun 4 (Sun JDK 1.3.1))
> >>     * Oracle9iAS J2EE (Sun JDK 1.3.1_02)
> >>     * Tomcat 3.3 (Sun JDK 1.3.1)
> >>     * Tomcat 4.1 (Sun JDK 1.3.1)
> >>   Solaris 7, 8, and 9
> >>     * BEA WebLogic Server 8 (Sun JDK 1.4.1_02)
> >>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
> >>     * Oracle9iAS J2EE (Sun JDK 1.3.1_02)
> >>     * iPlanet 6.5 (Sun JDK 1.3.1)
> >>   Red Hat Linux 7.2, and 8
> >>     * Borland Enterprise Server 5.2.1 (Sun JDK 1.4.1)
> >>     * BEA WebLogic Server 6 (Sun JDK 1.3.1)
> >>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
> >>     * JBoss 3.2 (Sun JDK 1.3.1)
> >>   Red Hat Enterprise Linux WS 2.1
> >>     * Borland Enterprise Server 5.2.1 (Sun JDK 1.4.1)
> >>     * BEA WebLogic Server 7 (Sun JDK 1.3.1_06)
> >>     * BEA WebLogic Server 8 (Sun JDK 1.4.1_02, WebLogic JRockit JVM)
> >>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
> >>     * Tomcat 3.3 (Sun JDK 1.3.1)
> >>     * Tomcat 4.1 (Sun JDK 1.3.1)
> >>   HP-UX 11
> >>     * Oracle9iAS J2EE (Sun JDK 1.3.1)
> >>     * BEA WebLogic Server 6, 7 (Sun JDK 1.3.1)
> >>     * Tomcat 4 (Sun JDK 1.3.1)
> >>   AIX 4.3.3
> >>     * JBoss 3.2 (IBM JDK 1.3.1)
> >>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
> >>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
> >>     * BEA WebLogic Server 7 (IBM JDK 1.3.1)
> >>   AIX 5.1
> >>     * Borland Enterprise Server 5.2.1 (IBM JDK 1.4.1)
> >>     * JBoss 3.2 (IBM JDK 1.3.1)
> >>     * IBM WebSphere Advanced Edition 4.0 (IBM JDK 1.3.0)
> >>     * IBM WebSphere Advanced Edition 5.0 (IBM JDK 1.3.1)
> >>     * BEA WebLogic Server 7 (IBM JDK 1.3.1)
> >>     * BEA WebLogic Server 8 (IBM JDK 1.4.1)
> >>
> >> Sergio Zuniga wrote:
> >>
> >> > Hello, i've read in a readme.txt file of server trace 2.0, that
solaris 8 and weblogic 7 are not supported for installing Optimizeit
serverTrace 2.0. Is there an update or a patch for this situation ??
> >> >
> >> > Thanks
> >
>