WebLogic 5.1 & IBM JDK 1.1.8 on RedHat Linux 6.2

Hello
I am trying to get WebLogic 5.1 to run with IBM JDK 1.1.8 on a RedHat 6.2 machine. When I start the sample server, it always SIGEV in the native thread (something like that).
I do not have any problems with the Blackdown 1.2.X JDK. I would like to evaluate the IBM JDK as that is the preferred solution in my group.
Please reply
Thanks you
Narayanan Iyer
[email protected]

Hi Michael
It appears to be a bug in the IBM JDK 1.1.8 release version built on May ??
,2000. I downloaded the newer version IBM JDK 1.1.8 built on July 13,2000
and it appears to be fine with SP4.
I am curious as to the status of IBM JDK1.3 on RedHat 6.2 and well as the
SUN JDK1.3. Both appear to crash. I would really like to take advantage of
the performance features offered.
Thanks
"Michael Girdley" <[email protected]> wrote in message
news:[email protected]..
>
>
Could you please post the error?
You should also make sure that you are using a certified JVM. Theplatform
support page for WebLogic Server is located at:
http://www.weblogic.com/platforms/index.html
This page has the latest and greatest information on the platforms that
WebLogic is certified and supported on.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Narayanan Iyer" <[email protected]> wrote in message
news:[email protected]..
Hello
I am trying to get WebLogic 5.1 to run with IBM JDK 1.1.8 on a RedHat
6.2
machine. When I start the sample server, it always SIGEV in the native
thread (something like that).
I do not have any problems with the Blackdown 1.2.X JDK. I would like toevaluate the IBM JDK as that is the preferred solution in my group.
Please reply
Thanks you
Narayanan Iyer
[email protected]

Similar Messages

Weblogic installation with IBM JDK

Hi,
We are planning to install Oracle Fusion Middleware components 11gR1 (11.1.1.6+) on IBM AIX Power 64 Bit servers. When i checked the certification matrix IBM JDK 7 SR3+ IV33133 is the certified version of JDK for weblogic installation.
Please help me on how to exactly get/download the IBM JDK 7 SR3+ IV33133? I have checked the IBM JDK downloads page and not exactly getting how can we get SR3+ IV33133?
Best Regards,
Kartheek

Hi Prakash,
I guess the '+' sign in the IBM JDK 7 SR3 + IV33133 is bit tricky. I doubt whether it is IBM JDK 7 SR3 added with IV33133.
I have spent quite some time on this JDK installation and got to know that the 3rd party products that are certified to run only on specific versions of IBM's Java for AIX can be downloaded from IBM Java for ISVs download page.
Here are steps that i have followed to download the IBM JDK 7 SR3+ IV33133
1.Go to the IBM Java for ISVs download site at the following URL:
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?lang=en_US&source=swg-ibmjavaisv
2.Log in using your IBM ID and password.
3.Enter the associated Access Key MJ3D7TQGMK in the IBM Java for ISVs page
4.Click on submit
5.On the IBM SDK Interim Fixes (iFix) for Oracle page you will see the below JDK versions that are exactly matching the one provided in the certification matrix.
pap6470sr3ifx-20121213_01 (SR3+IV33133)
Java7_64.0.0.61.tar.gz (115 MB)
pap6470sr3ifx-20121213_01 (SR3+IV33133)
pap6470sr3ifx-20121213_01-sdk.tar.Z (184 MB)
6.installed the JDK
Please can you confirm that this procedure is correct?
Best Regards,
Kartheek

Gdb gets SIGSEGV from JVM in JDK 1.3.1_01 on RedHat Linux 6.2

Hi all,
I'd love to know if anyone has a fix for this problem? I am also posting it as a bug.
Thanks in advance!
OVERVIEW:
When running Tomcat 4.0 via the Java launcher in a gdb debugging session (Red Hat Linux 6.2), I get a SIGSEGV signal (Segmentation fault) when I execute some of the example JSPs/servlets. Since Tomcat is pure Java, I'm assuming the problem is most likely with the JVM and the way it handles signals, or possibly with gdb since I only see this behavior with gdb. The problem is fairly reproducible; I usually get it when I execute the "ErrorPage" JSP sample in Tomcat's "examples" webapp.
Note that I don't see these signals when running the JVM standalone (outside of gdb). What's also weird is that I successfully tell gdb to "continue" after the segfault, and the app continues to work like nothing ever happend.
As an aside, the reason why I did this test was because I was experiencing very similar problems in my own application that embeds a JVM via JNI.
DESCRIPTION:
Here is what I did to see the problem.
First, I set the debugger in the environment, so that the jdk/bin/java script can run the java launcher in gdb:
export DEBUG_PROG=gdb
Next, I run the jdk/bin/java script:
cd jdk1.3.1_01/bin
java
This brings up the Java launcher within gdb, and I run it as I specify the necessary arguments to startup Tomcat:
GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
(gdb) set args -classpath /u0/ruvinsky/tomcat4.bin/bin/bootstrap.jar:/u0/ruvinsky/src-java-launcher/jdk1.3.1_01/lib/tools.jar -Dcatalina.base=/u0/ruvinsky/tomcat4.bin -Dcatalina.home=/u0/ruvinsky/tomcat4.bin org.apache.catalina.startup.Bootstrap start
(gdb) run
Starting program: /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/bin/i386/native_threads/java -classpath /u0/ruvinsky/tomcat4.bin/bin/bootstrap.jar:/u0/ruvinsky/src-java-launcher/jdk1.3.1_01/lib/tools.jar -Dcatalina.base=/u0/ruvinsky/tomcat4.bin -Dcatalina.home=/u0/ruvinsky/tomcat4.bin org.apache.catalina.startup.Bootstrap start
[New Thread 1710 (manager thread)]
[New Thread 1709 (initial thread)]
[New Thread 1711]
[New Thread 1712]
[New Thread 1713]
[New Thread 1714]
[New Thread 1715]
[New Thread 1716]
[New Thread 1717]
Starting service Tomcat-Standalone
Apache Tomcat/4.0
[New Thread 1720]
[New Thread 1721]
[New Thread 1722]
[New Thread 1723]
[New Thread 1724]
[New Thread 1725]
[New Thread 1726]
[New Thread 1727]
[New Thread 1728]
[New Thread 1729]
[New Thread 1730]
[New Thread 1731]
Starting service Tomcat-Apache
Apache Tomcat/4.0
[New Thread 1732]
[Switching to Thread 1730]
Program received signal SIGSEGV, Segmentation fault.
0x2bfee3f4 in ?? ()
(gdb) continue
Continuing.
I even tried building a debug version of the java launcher by hand in hope of finding a more detailed stack trace, but all I got was the following:
(gdb) bt
#0 0x806973d in ?? ()
#1 0x8060891 in ?? ()
#2 0x8060891 in ?? ()
#3 0x8060963 in ?? ()
#4 0x8060891 in ?? ()
#5 0x8060891 in ?? ()
#6 0x8060891 in ?? ()
#7 0x8060963 in ?? ()
#8 0x8060891 in ?? ()
#9 0x8060891 in ?? ()
#10 0x8060963 in ?? ()
#11 0x8060891 in ?? ()
#12 0x8060963 in ?? ()
#13 0x8060963 in ?? ()
#14 0x8060963 in ?? ()
#15 0x8060963 in ?? ()
#16 0x8060963 in ?? ()
#17 0x8060891 in ?? ()
#18 0x8060963 in ?? ()
#19 0x8060891 in ?? ()
#20 0x8060963 in ?? ()
#21 0x8060963 in ?? ()
#22 0x8060963 in ?? ()
#23 0x8060963 in ?? ()
#24 0x8060891 in ?? ()
#25 0x8060963 in ?? ()
#26 0x8060963 in ?? ()
#27 0x8060963 in ?? ()
#28 0x8060891 in ?? ()
#29 0x8060963 in ?? ()
#30 0x8060963 in ?? ()
#31 0x8060891 in ?? ()
#32 0x8060963 in ?? ()
#33 0x2add3d70 in StubRoutines::_code1 ()
from /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
#34 0x2abcb604 in JavaCalls::call_helper ()
from /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
#35 0x2ac2948d in os::os_exception_wrapper ()
from /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
#36 0x2abcb840 in JavaCalls::call ()
from /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
#37 0x2abcb1bb in JavaCalls::call_virtual ()
from /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
#38 0x2abcbccb in JavaCalls::call_virtual ()
from /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
#39 0x2abede80 in thread_entry ()
from /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
#40 0x2ac599c7 in JavaThread::thread_main_inner ()
from /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
#41 0x2ac56903 in JavaThread::run ()
from /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
#42 0x2ac27e73 in _start ()
from /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
#43 0x2aacc535 in pthread_start_thread (arg=0x7d3ffe40) at manager.c:241
(gdb) info shared
From To Syms Read Shared Object Library
0x2aac7000 0x2aad8ad8 Yes /lib/libpthread.so.0
0x2aad9000 0x2aae2e38 Yes /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/native_threads/libhpi.so
0x2aae3000 0x2addce90 Yes /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/client/libjvm.so
0x2addd000 0x2addfd0c Yes /lib/libdl.so.2
0x2ade1000 0x2aed537c Yes /lib/libc.so.6
0x2aed6000 0x2aeeb1c8 Yes /lib/libnsl.so.1
0x2aeec000 0x2af08098 Yes /lib/libm.so.6
0x2af09000 0x2af4af90 Yes /usr/lib/libstdc++-libc6.1-1.so.2
0x2aaab000 0x2aabecb0 Yes /lib/ld-linux.so.2
0x2af4b000 0x2af5d414 Yes /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/libverify.so
0x2af5e000 0x2af81fe8 Yes /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/libjava.so
0x2af82000 0x2af98360 Yes /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/libzip.so
0x340c6000 0x340ce9a0 Yes /lib/libnss_files.so.2
0x340cf000 0x340d8fb4 Yes /lib/libnss_nisplus.so.2
0x340d9000 0x340e21f8 Yes /lib/libnss_nis.so.2
0x343e9000 0x343f242c Yes /u0/ruvinsky/src-java-launcher/jdk1.3.1_01/jre/lib/i386/libnet.so
0x343fa000 0x343fd850 Yes /lib/libnss_dns.so.2
0x3497f000 0x3498d9fc Yes /lib/libresolv.so.2
As a reference, I built the Java launcher code included in the JDK 1.3.1_01 distribution, producing the replacement binary for:
jdk1.3.1_01/bin/i386/native_threads/java
I copied the source files out of the jdk1.3.1_01/src/src/launcher/ directory, and they consist of the following files:
java.c
java.h
java_md.c
java_md.h
My build directory also contains the jdk1.3.1_01 subdirectory to include the JNI headers from and as a sample jdk to test the build output with.
The following are my build commands (mainly borrowed from the JDK build process):
cc -g -W -Wall -Werror -Wno-unused -Wno-parentheses -Di386 -DARCH='"i386"' -DSOLARIS2 -DRELEASE='"1.3.1-testing-110101"' -DFULL_VERSION='"1.3.1-testing-110101"' -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -D_REENTRANT -D_LITTLE_ENDIAN -DUSE_APPHOME -DPROGNAME='"java"' -I./jdk1.3.1_01/include -I./jdk1.3.1_01/include/linux -c -o build/objs/java.o java.c
cc -g -W -Wall -Werror -Wno-unused -Wno-parentheses -Di386 -DARCH='"i386"' -DSOLARIS2 -DRELEASE='"1.3.1-testing-110101"' -DFULL_VERSION='"1.3.1-testing-110101"' -D_LARGEFILE64_SOURCE -D_GNU_SOURCE -D_REENTRANT -D_LITTLE_ENDIAN -DUSE_APPHOME -DPROGNAME='"java"' -I./jdk1.3.1_01/include -I./jdk1.3.1_01/include/linux -c -o build/objs/java_md.o java_md.c
cc -o jdk1.3.1/bin/i386/native_threads/java -z defs -Ljdk1.3.1_01/jre/lib/i386/native_threads -Ljdk1.3.1_01/jre/lib/i386/classic build/objs/java.o build/objs/java_md.o -lpthread -lhpi -ljvm -ldl -lc

Also experiencing SIGSEGV with tomcat 4.0 on AIX. Runs for months. Then out of the blue, crashes.
I wonder if setting reloadable=false in .../conf/server.xml could be the culprit ?
Or the servlet writing to a local file using a BufferedOutputStream ?

Bug in WebLogic 8.1 SP4 for IBM JDK 1.4.2?

Hello,

In a previous thread i posted (http://forums.bea.com/bea/thread.jspa?threadID=600006934&tstart=0), I reported that we had problems in trying to use JAAS in connecting Acegi with WebLogic 8.1 SP4 on IBM JDK 1.4.2

We did some more research and found the following:
 
WebLogic uses the class weblogic.security.service.ServerConfiguration for reading the JAAS config file. This class extends the default javax.security.auth.login.Configuration class. To see what's going on we decompiled the class and it looks like this:


try {
 // code omitted.
} catch (Exception exception) {
 String s1 = System.getProperty("login.configuration.provider");
 if(s1 == null)
 s1 = "com.sun.security.auth.login.ConfigFile";
 if(!s1.equals("weblogic.security.service.ServerConfiguration"))
 try
 Configuration configuration = (Configuration)Class.forName(s1).newInstance();
 configuration.refresh();
 aappconfigurationentry = configuration.getAppConfigurationEntry(s);
 catch(Exception exception1) { }


The following happens when trying to authenticate through JAAS:

- The "omitted code" throws the Exception weblogic.security.service.InvalidParameterException: [Security:090396]Security Realm sample does not exist.

Why is this Exception thrown? Why does the name of my JAAS configuration in the JAAS config file needs to be the same as a Security Realm? Or this try-catch block used as some kind of control flow and is this exception expected?

- Then in the catch block the System.property login.configuration.provider is retrieved. However the JDK Specification of the class javax.security.auth.login.Configuration (sse the javadoc) states that:
The default Configuration implementation can be changed by setting the value of the "login.configuration.provider" security property (in the Java security properties file) to the fully qualified name of the desired Configuration implementation class

So because the System property is read instead of the Security property (which contains the correct IBM class), null is returned. Is this a bug?

- Because the System property is null the code then tries to load the class com.sun.security.auth.login.ConfigFile, which of course is not present in the IBM JDK, and a ClassNotFoundException is thrown. Since
the Exception is swallowed by the nested catch block we will not see this exception and null is returned that eventually leads to the "No LoginModule found..." exception.

So to summarize, my questions are these:

- Does the name of the JAAS configuration in the JAAS config file need to be the same as the name of the Realm? And if so why? 
- Is it a bug that instead of reading the Security this code is reading the System property?

Regards, 
Lars Vonk

PS 
As a workaround we set the System property login.configuration.provider to the correct value com.ibm.security.auth.login.ConfigFile and then it works.

Sorry, i saw the forum about your problem in BEA 8.1 SP 6 about a
weblogic.security.SSL.SSLCertificate.verify(SSLCertificate.java:235)
error and you said that bea sent a path named CR295205_810sp6.jar.
I have the same problem
Do you have this patch?
Could you send it to me?
my email address is
[email protected]

IBM JDK 6 32bit & 64bit Reflection Invoke issue on Weblogic 10.3

We just found a issue on Weblogic 10.3 with IBM JDK 6 32bit, which calls different method during reflection invoke with that been processed under 64bit JDK, here is my source code:
public class ButtonTag extends InputTag {
private boolean checkNotNull = false;
public void setCheckNotNull(Object checkNotNull) {
public void setCheckNotNull(boolean checkNotNull) {
this.checkNotNull = checkNotNull;
this.setUserSetCheckNotNull(true);
Under 64bit, reflection invoke will call setCheckNotNull(boolean checkNotNull), however under 32bit, it will call setCheckNotNull(Object checkNotNull), actually 32bit version is doing something wrong, we are not sure it is a issue of weblogic or IBM JDK, pls refer the information below for details, Thanks
OS: AIX 5.3
AIX@ /usr/java6/bin./java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap3260sr2-20080818_01(SR2))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc-32 jvmap3260-20080816_22093 (JIT enabled, AOT enabled)
J9VM - 20080816_022093_bHdSMr
JIT - r9_20080721_1330ifx2
GC - 20080724_AA)
JCL - 20080808_02
AIX@ /usr/java6_64/bin./java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460sr6-20090925_01(SR6))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr6-20090923_42924 (JIT enabled, AOT enabled)
J9VM - 20090923_042924
JIT - r9_20090902_1330ifx1
GC - 20090817_AA)
JCL - 20090924_01
AIX server107 3 5 00CE9E7B4C00

The problem was the name of the Seam EJB module. Changing the jar to jboss-seam.jar, everything worked. This issue does not appear on JBoss 4.2.3.GA, where I also tested.
Edited by: deadlock_gr on Jun 10, 2010 9:55 AM
Edited by: deadlock_gr on Jun 10, 2010 9:56 AM

Error reconciling AD Lookups OIM 11g IBM JDK 6 64 bit

Hi,
I'm setting up SSL from OIM 11g to AD 2008, my environment is OIM 11g+ Weblogic 10.3.3 generic on IBM AIX 6.1 + IBM JDK 6 64 bit. I imported the certificate as described in AD connector documentation with "keytool". I'm getting the following ERROR when I try to run the scheduled jobs in order to perform lookup reconciliation (groups and organizations)
<Mar 6, 2011 3:11:51 AM CST> <Error> <OIMCP.ADCS> <BEA-000000> <com.thortech.xl.integration.ActiveDirectory.tcADUtilLDAPController : addSecurityProvider : ClassNotFoundException has occured com.sun.net.ssl.internal.ssl.Provider>
<Mar 6, 2011 3:11:51 AM CST> <Error> <OIMCP.ADCS> <BEA-000000>
I have reviewed "java.security" in the IBM JRE and there is nothing about SUN JSSE provider. I understand I need to setup Sun JSSE in the IBM JDK but I'm not able to find information about that. I dont know if it's possible to use Sun JSSE provider in IBM or if I need to change the security provider to IBM's implementation. How to do that? I think somewhere in the weblogic configuration.
Please helps me, how can I set up the correct configuration.
Regards
Juan

From Sun JDK 1.6 updae 18+ 64 bit, copy the jsse.jar in the OIM_HOME/server/ThirdParty and restart the servers

How to configure weblogic client in IBM JRE

I'm trying to get a java client (Lotus Domino java agent) app to connect to
Weblogic 6.1 sp3.
Both run separately fine.
Domino is running with IBM JDK version :
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1)
Classic VM (build 1.3.1, J2RE 1.3.1 IBM Windows 32 build cn131-20020710 (JIT
enabled: jitc))
I put weblogic.jar in the app's classpath but when i try to get an
InitialContext, I get the following stack trace :
04/04/2003 16:04:35 HTTP JVM: weblogic.utils.AssertionError: ***** ASSERTION
FAILED *****[ Assertion violated ]
04/04/2003 16:04:35 HTTP JVM: at weblogic.utils.Debug.assert(Debug.java:74)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:123)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:106)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.rmi.internal.ClientRuntimeDescriptor.computeInterfaces(ClientRuntim
eDescriptor.java:218)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.rmi.internal.ClientRuntimeDescriptor.intern(ClientRuntimeDescriptor
.java:111)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.jndi.WLInitialContextFactoryDelegate.<clinit>(WLInitialContextFacto
ryDelegate.java:154)
04/04/2003 16:04:35 HTTP JVM: at java.lang.Class.forName1(Native Method)
04/04/2003 16:04:35 HTTP JVM: at java.lang.Class.forName(Class.java:142)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:145)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.init(InitialContext.java:218)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.<init>(InitialContext.java:174)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.<init>(EJBHomeFactory.java:29)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.getFactory(EJBHomeFactory.java:49)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.lookUpHome(EJBHomeFactory.java:56)
04/04/2003 16:04:35 HTTP JVM: at WQO.NotesMain(WQO.java:13)
04/04/2003 16:04:35 HTTP JVM: at lotus.domino.AgentBase.runNotes(Unknown
Source)
04/04/2003 16:04:35 HTTP JVM: at
lotus.domino.NotesThread.run(NotesThread.java:208)
04/04/2003 16:04:35 HTTP JVM: weblogic.utils.AssertionError: ***** ASSERTION
FAILED *****[ Assertion violated ]
04/04/2003 16:04:35 HTTP JVM: at weblogic.utils.Debug.assert(Debug.java:74)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:123)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:106)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.rmi.internal.ClientRuntimeDescriptor.computeInterfaces(ClientRuntim
eDescriptor.java:218)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.rmi.internal.ClientRuntimeDescriptor.intern(ClientRuntimeDescriptor
.java:111)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.jndi.WLInitialContextFactoryDelegate.<clinit>(WLInitialContextFacto
ryDelegate.java:154)
04/04/2003 16:04:35 HTTP JVM: at java.lang.Class.forName1(Native Method)
04/04/2003 16:04:35 HTTP JVM: at java.lang.Class.forName(Class.java:142)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:145)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.init(InitialContext.java:218)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.<init>(InitialContext.java:174)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.<init>(EJBHomeFactory.java:29)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.getFactory(EJBHomeFactory.java:49)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.lookUpHome(EJBHomeFactory.java:56)
04/04/2003 16:04:35 HTTP JVM: at WQO.NotesMain(WQO.java:13)
04/04/2003 16:04:35 HTTP JVM: at lotus.domino.AgentBase.runNotes(Unknown
Source)
04/04/2003 16:04:35 HTTP JVM: at
lotus.domino.NotesThread.run(NotesThread.java:208)
Anybody have any idea what is going on?
Thanks.

Sorry, forgot to mention : both are running on separate boxers running W2K
sp3.
I will however see if i can change any of the vm parameters like jit
j.
"Wayne W. Scott" <[email protected]> wrote in message
news:[email protected]...
>
Well, I guess you are running on AIX 4.3.3. First make sure PTF 9 is onthe OS.
>
Next, check with IBM for updates to that JDK. I believe they have an SP2.
Finally, turn off jit. Then see how the system behaves.
Wayne Scott
Jo Willems wrote:
I'm trying to get a java client (Lotus Domino java agent) app to connect
to
Weblogic 6.1 sp3.
Both run separately fine.
Domino is running with IBM JDK version :
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1)
Classic VM (build 1.3.1, J2RE 1.3.1 IBM Windows 32 build cn131-20020710(JIT
enabled: jitc))
I put weblogic.jar in the app's classpath but when i try to get an
InitialContext, I get the following stack trace :
04/04/2003 16:04:35 HTTP JVM: weblogic.utils.AssertionError: *****ASSERTION
FAILED *****[ Assertion violated ]
04/04/2003 16:04:35 HTTP JVM: atweblogic.utils.Debug.assert(Debug.java:74)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:123)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:106)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.rmi.internal.ClientRuntimeDescriptor.computeInterfaces(ClientRuntim
eDescriptor.java:218)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.rmi.internal.ClientRuntimeDescriptor.intern(ClientRuntimeDescriptor
..java:111)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.jndi.WLInitialContextFactoryDelegate.<clinit>(WLInitialContextFacto
ryDelegate.java:154)
04/04/2003 16:04:35 HTTP JVM: at java.lang.Class.forName1(Native Method)
04/04/2003 16:04:35 HTTP JVM: at java.lang.Class.forName(Class.java:142)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:145)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.init(InitialContext.java:218)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.<init>(InitialContext.java:174)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.<init>(EJBHomeFactory.java:29)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.getFactory(EJBHomeFactory.java:49)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.lookUpHome(EJBHomeFactory.java:56)
04/04/2003 16:04:35 HTTP JVM: at WQO.NotesMain(WQO.java:13)
04/04/2003 16:04:35 HTTP JVM: at lotus.domino.AgentBase.runNotes(Unknown
Source)
04/04/2003 16:04:35 HTTP JVM: at
lotus.domino.NotesThread.run(NotesThread.java:208)
04/04/2003 16:04:35 HTTP JVM: weblogic.utils.AssertionError: *****ASSERTION
FAILED *****[ Assertion violated ]
04/04/2003 16:04:35 HTTP JVM: atweblogic.utils.Debug.assert(Debug.java:74)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:123)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.j2ee.ApplicationManager.loadClass(ApplicationManager.java:106)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.rmi.internal.ClientRuntimeDescriptor.computeInterfaces(ClientRuntim
eDescriptor.java:218)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.rmi.internal.ClientRuntimeDescriptor.intern(ClientRuntimeDescriptor
..java:111)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.jndi.WLInitialContextFactoryDelegate.<clinit>(WLInitialContextFacto
ryDelegate.java:154)
04/04/2003 16:04:35 HTTP JVM: at java.lang.Class.forName1(Native Method)
04/04/2003 16:04:35 HTTP JVM: at java.lang.Class.forName(Class.java:142)
04/04/2003 16:04:35 HTTP JVM: at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:145)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.init(InitialContext.java:218)
04/04/2003 16:04:35 HTTP JVM: at
javax.naming.InitialContext.<init>(InitialContext.java:174)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.<init>(EJBHomeFactory.java:29)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.getFactory(EJBHomeFactory.java:49)
04/04/2003 16:04:35 HTTP JVM: at
com.approach.domino.util.EJBHomeFactory.lookUpHome(EJBHomeFactory.java:56)
04/04/2003 16:04:35 HTTP JVM: at WQO.NotesMain(WQO.java:13)
04/04/2003 16:04:35 HTTP JVM: at lotus.domino.AgentBase.runNotes(Unknown
Source)
04/04/2003 16:04:35 HTTP JVM: at
lotus.domino.NotesThread.run(NotesThread.java:208)
Anybody have any idea what is going on?
Thanks.

Error while parsing JSP with WebLogic 5.1/SP9/JDK 1.2.2

Hello everybody,
          I get the error given below when calling a JSP in a WebLogic
          application which seems to work fine in all other (non-JSP) parts:
          java.lang.NullPointerException:
               at weblogic.servlet.jsp.JspLexer.addSetPropertyValue(JspLexer.java:1432)
               at weblogic.servlet.jsp.JspLexer.mXML_SET_PROPERTY(JspLexer.java,
          Compiled Code)
               at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1726)
               at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
               at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
          Code)
               at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
               at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
               at weblogic.servlet.jsp.JspParser.parse(JspParser.java:159)
               at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:109)
               at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
          Compiled Code)
               at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
          Code)
               at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
               at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
               at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
               at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
               at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
          Code)
          I know that this error has been reported more than once in these
          discussion groups, and all people who solved it say
          - that it occurs only wen running WebLogic 5.1 with JDK 1.3 instead of
          1.2.2
          - that it may also be caused by bad jsp code
          But in my case, it has to be another reason, because
          - I am using jdk 1.2.2
          - the same JSP file is running withour errors on WebLogic 6
          I wonder if it could have something to do with the operating system:
          the parsing error is produced on a Windows version of WL 5.1, while my
          WL 6 which doesn't cause errors is running with Linux.
          Many thanks in advance for any help,
          Eckhard Beisswenger


Once again me!
          After a long time, I stumbled by accident across the answer that solves the problem I described above. It is explained at
          http://support.bea.com/application;JSESSIONID_WLCS_DEFAULT=2R2lzQfEBxFRMX2z0AxeU1Un3N1522I9fCIUI7GfjnjsiSYkPscz
          The clue is that weblogic complains about corresponding get and set methods, when the type of the set methods parameter is different from the return type of the corresponding get method. Unfortunately, the weblogic lexer class gives only a NullPointerException without any hint.

OAS 10.1.3 PatchSet 3 on IBM AIX 5.3 installs a 2 year old IBM JDK - why ?

We're running OAS 10.1.3.0.0 on IBM AIX 5.3 and due to some crashing issues OSS recommended to upgrade to PatchSet 3 (so 10.1.3.3.0).
We originally were running OAS with IBM's SR4 of the IBM JDK.
Now after the upgrade to Patchset 3 (on a test machine), the ORACLE_HOME/jdk version seems to be the first release of the v5 jdk from 2005. It's SR nothing ... J2RE 1.5.0 IBM AIX build jclap32dev-20051102 java
It's 2 years old for heavans sake !!!! Not even DST patched.
What am I missing? OAS 10.1.3.3.0 is pretty much THEE most latest version of OAS Oracle has, yet it comes with a 2 year old JDK. Why? This doesn't sound right, why would a company of Oracle stature do this?
Are others experiencing this also? Why doesn't Oracle bundle a more updated JDK with OAS?

It's not a symlink.
Oracle has a script (jdkfix.sh) and a procedure for upgrading the jdk inside OH/jdk. We went thru this on all our OAS 10.1.2.0.2 enviro's and 10.1.3.0.0.
One metalink note that talks about this is Doc. 272808.1.
Basically, you install the AIX jdk in the IBM /usr directory and then run jdkfix.sh which essentially copies the jdk over to ORACLE_HOME/jdk.
There don't seem to be any Oracle supplied patches for any OAS that upgrades the jdk. Which is a bit wonky.
Here's the ls -l from our prod OAS 10.1.3.0.0 install:
drwx------   6 oracle   oinstall        256 Nov 29 2006 Apache
drwx------   5 oracle   oinstall        256 Nov 29 2006 BC4J
drwx------   5 oracle   oinstall       4096 Mar 04 2007 OPatch
drwx------   5 oracle   oinstall        256 Nov 29 2006 ant
drwx------   3 oracle   oinstall        256 Nov 29 2006 assistants
drwx------   6 oracle   oinstall       4096 Nov 29 2006 backup_restore
drwx------   2 oracle   oinstall       4096 Nov 29 2006 bin
drwx------   2 oracle   oinstall        256 Nov 29 2006 cfgtoollogs
drwx------   5 oracle   oinstall        256 Nov 29 2006 chgip
drwx------   2 oracle   oinstall        256 Nov 29 2006 config
drwx------   8 oracle   oinstall        256 Nov 29 2006 datadirect
drwx------   4 oracle   oinstall        256 Nov 29 2006 diagnostics
drwx------   7 oracle   oinstall       4096 Nov 29 2006 dsa
drwx------   3 oracle   oinstall        256 Nov 29 2006 emdw
drwx------   3 oracle   oinstall        256 Nov 29 2006 encryption
drwx------   4 oracle   oinstall        256 Nov 29 2006 has
drwx------   3 oracle   oinstall        256 Nov 29 2006 hs
drwx------   5 oracle   oinstall        256 Nov 29 2006 iaspt
drwxr-xr-x   2 oracle   oinstall        256 Dec 20 2006 ibmFix
drwx------   3 oracle   oinstall        256 Nov 29 2006 install
-rw-------   1 oracle   oinstall         38 Nov 29 2006 install.platform
drwx------ 13 oracle   oinstall       4096 Mar 04 2007 inventory
drwx------   5 oracle   oinstall        256 Dec 03 2006 j2ee
drwx------   6 oracle   oinstall        256 Nov 29 2006 javacache
drwx------   3 oracle   oinstall        256 Nov 29 2006 javavm
drwx------   4 oracle   oinstall        256 Nov 29 2006 jdbc
drwxr-xr-x   7 oracle   oinstall        256 Mar 14 2007 jdk
drwxr-xr-x   7 oracle   system          256 Dec 20 2006 jdk.141
drwx---r-x   8 oracle   oinstall        256 Nov 29 2006 jdk.bundled
drwx------   2 oracle   oinstall       4096 Nov 29 2006 jlib
drwx------   3 oracle   oinstall        256 Nov 29 2006 jre
drwx------   8 oracle   oinstall        256 Nov 29 2006 ldap
drwx------   2 oracle   oinstall      12288 Nov 29 2006 lib
drwx------   2 oracle   oinstall      12288 Nov 29 2006 lib32
drwx------   3 oracle   oinstall        256 Nov 29 2006 mds
drwx------ 12 oracle   oinstall       4096 Nov 29 2006 network
drwx------   5 oracle   oinstall        256 Nov 29 2006 nls
drwxr-xr-x 10 oracle   oinstall       4096 Jan 28 2007 opmn
drwx------   4 oracle   oinstall        256 Nov 29 2006 opsm
-rw-r--r--   1 oracle   oinstall         55 Nov 28 2006 oraInst.loc
drwx------   4 oracle   oinstall        256 Nov 29 2006 oracore
drwx------   4 oracle   oinstall        256 Nov 29 2006 ord
drwx------   6 oracle   oinstall        256 Nov 29 2006 oui
drwx------   4 oracle   oinstall        256 Nov 29 2006 owm
-rw-r-----   1 oracle   oinstall     312588 Mar 04 2007 p2617419_10102_GENERIC_OPATCH.zip
drwx------   6 oracle   oinstall        256 Nov 29 2006 perl
drwx------   5 oracle   oinstall        256 Nov 29 2006 plsql
drwx------   6 oracle   oinstall        256 Nov 29 2006 precomp
drwx------ 10 oracle   oinstall        256 Nov 29 2006 rdbms
drwx------   3 oracle   oinstall        256 Nov 29 2006 relnotes
-rwx------   1 oracle   oinstall       5532 Nov 29 2006 root.sh
drwx------   4 oracle   oinstall        256 Nov 29 2006 rules
drwx------   3 oracle   oinstall        256 Nov 29 2006 slax
drwx------   3 oracle   oinstall        256 Nov 29 2006 sqlj
drwx------   7 oracle   oinstall        256 Nov 29 2006 sqlplus
drwx------   5 oracle   oinstall        256 Nov 29 2006 srvm
drwx------   4 oracle   oinstall        256 Nov 29 2006 sysman
drwx------   3 oracle   oinstall        256 Nov 29 2006 tg4sybs
drwx------   4 oracle   oinstall        256 Nov 29 2006 toplink
drwx------   4 oracle   oinstall        256 Nov 29 2006 uix
drwx------   3 oracle   oinstall        256 Nov 29 2006 webservices
drwx------   4 oracle   oinstall        256 Nov 29 2006 xdk
drwx------   4 oracle   oinstall        256 Nov 29 2006 xdsOn our test OAS 10.1.3.3.0 machine :
drwx------   6 oracle   oinstall        256 Oct 04 10:04 Apache
drwx------   5 oracle   oinstall        256 Oct 04 10:03 BC4J
drwx------   5 oracle   oinstall        256 Feb 07 15:37 OPatch
drwx------   5 oracle   oinstall        256 Oct 04 10:03 ant
drwx------   3 oracle   oinstall        256 Oct 04 10:03 assistants
drwx------   6 oracle   oinstall       4096 Oct 04 10:01 backup_restore
drwx------   2 oracle   oinstall       4096 Feb 07 15:43 bin
drwx------   2 oracle   oinstall        256 Feb 07 15:45 cfgtoollogs
drwx------   5 oracle   oinstall        256 Oct 04 10:01 chgip
drwx------   6 oracle   oinstall        256 Feb 07 15:37 clone
drwx------   2 oracle   oinstall       4096 Feb 07 15:43 config
drwx------   8 oracle   oinstall        256 Oct 04 09:59 datadirect
drwx------   2 oracle   oinstall        256 Feb 07 15:39 deconfig
drwx------   5 oracle   oinstall        256 Feb 07 15:38 diagnostics
drwx------   7 oracle   oinstall       4096 Feb 07 15:38 dsa
drwx------   3 oracle   oinstall        256 Oct 04 10:01 emdw
drwx------   3 oracle   oinstall        256 Oct 04 10:00 encryption
drwx------   4 oracle   oinstall        256 Oct 04 10:01 has
drwx------   3 oracle   oinstall        256 Oct 04 10:00 hs
drwx------   5 oracle   oinstall        256 Oct 04 10:03 iaspt
drwx------   3 oracle   oinstall       4096 Feb 07 15:43 install
-rw-------   1 oracle   oinstall         38 Oct 04 09:58 install.platform
drwx------ 14 oracle   oinstall       4096 Feb 07 15:46 inventory
drwx------   5 oracle   oinstall        256 Oct 10 17:11 j2ee
drwx------   6 oracle   oinstall        256 Oct 04 10:02 javacache
drwx------   3 oracle   oinstall        256 Oct 04 10:00 javavm
drwx------   4 oracle   oinstall        256 Oct 04 10:03 jdbc
drwx---r-x   8 oracle   oinstall        256 Oct 04 09:59 jdk
drwx------   2 oracle   oinstall       4096 Feb 07 15:39 jlib
drwx------   3 oracle   oinstall        256 Oct 04 09:59 jre
drwx------   8 oracle   oinstall        256 Oct 04 10:02 ldap
drwx------   2 oracle   oinstall       8192 Feb 07 15:46 lib
drwx------   2 oracle   oinstall       8192 Feb 07 15:46 lib32
drwx------   3 oracle   oinstall        256 Oct 04 10:03 mds
drwx------ 12 oracle   oinstall       4096 Oct 04 10:07 network
drwx------   5 oracle   oinstall        256 Oct 04 10:02 nls
drwx------   3 oracle   oinstall        256 Feb 07 15:43 opatches
drwx------   7 oracle   oinstall        256 Oct 04 10:02 opmn
drwx------   4 oracle   oinstall        256 Oct 04 10:00 opsm
-rw-------   1 oracle   oinstall         68 Jan 12 2007 oraInst.loc
drwx------   4 oracle   oinstall        256 Oct 04 10:02 oracore
drwx------   4 oracle   oinstall        256 Oct 04 10:01 ord
drwx------   6 oracle   oinstall       4096 Feb 07 15:43 oui
drwx------   4 oracle   oinstall        256 Oct 04 10:03 owm
drwx------   6 oracle   oinstall        256 Oct 04 10:02 perl
drwx------   5 oracle   oinstall        256 Oct 04 10:01 plsql
drwx------   6 oracle   oinstall        256 Oct 04 10:01 precomp
drwx------ 10 oracle   oinstall        256 Oct 04 10:03 rdbms
drwx------   3 oracle   oinstall        256 Oct 04 10:03 relnotes
-rwx------   1 oracle   oinstall        607 Feb 07 15:43 root.sh
-rwx------   1 oracle   oinstall       5510 Oct 04 10:09 root.sh.old
drwx------   5 oracle   oinstall        256 Feb 07 15:38 rules
drwx------   3 oracle   oinstall        256 Oct 04 10:01 slax
drwx------   3 oracle   oinstall        256 Oct 04 10:03 sqlj
drwx------   7 oracle   oinstall        256 Oct 04 10:03 sqlplus
drwx------   5 oracle   oinstall        256 Oct 04 10:02 srvm
drwx------   4 oracle   oinstall        256 Oct 04 10:02 sysman
drwx------   3 oracle   oinstall        256 Oct 04 10:00 tg4sybs
drwx------   4 oracle   oinstall        256 Oct 04 10:02 toplink
drwx------   4 oracle   oinstall        256 Oct 04 10:02 uix
drwx------   3 oracle   oinstall        256 Oct 04 10:03 webservices
drwx------   5 oracle   oinstall        256 Feb 07 15:37 xdk
drwx------   4 oracle   oinstall        256 Oct 04 09:59 xds
drwx------   4 oracle   oinstall        256 Feb 07 15:38 xqs

NW04s Linux Trial : problem installing IBM JDK Fedora Core 6

Hi,
I'm trying to install the NW04S Linux Preview on a Fedora Core 6 distribution and I'm encountering a problem with the IBM JDK 1.4.2 installation.
I've downloaded the RPM package from IBM (IBMJava2-AMD64-142-SDK-1.4.2-7.0.x86_64.rpm
), installed it as root but when I try to invoke the virtual machine (java) or the compiler (javac), I got the following error :
libjvm.so preloadLibrary: /libj9vm22.so: cannot open shared object file: No such file or directory
libjvm.so failed to load: j9vm22
Has anyone tried to install the Linux Preview on Fedora and encountered the same problem. It might be connected to some sort of the linux dynamic linker/loader (ld.so) or versions of librairies.
I'm really lost here and I won't be able to start the installation without a working virtual machine.
Thanks

I have double checked the link provided to the IBM JDK in the Linux Trial and it seems I had the wrong version. I've downloaded IBMJava2-AMD64-142-SDK-1.4.2-7.0.x86_64.rpm (1.4.2-7) and the special version for SAP is the IBMJava2-AMD64-142-SDK-1.4.2-2.0.x86_64.rpm (1.4.2-2).
I have installed it : rpm -ivh IBMJava2-AMD64-142-SDK-1.4.2-2.0.x86_64.rpm
I have installed it and activated it as the default JVM using alternatives command :
alternatives --install /usr/bin/java java /opt/IBMJava2-amd64-142/bin/java 2
alternatives --config java
I now have a different error :
[root@macpro ~]# java
JVM not found: libjvm.so - libjvm.so
What could have I done wrong ?
Thanks for you help

Latest IBM JDK version supported by SAP

Hi there, we are having some Java performance issues in our landscape and the recommendation from SAP is to install the latest IBM JDK release supported by SAP, can you help me determine what the latest release is and where I can find the download?
Thanks

Hey James,
The best thing to do is to check the Product Availability Matrix (PAM) for your release on service marketplace.
http://service.sap.com/pam
We're on Netweaver7 with EhP1 and the PAM suggestst the latest server-side JDK supported for us is 1.4.2. Here's the results or "java -version" on an ECC6.0 server in our landscape:
root@#######:/>java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20080122 (SR10) (JIT enabled: jitc))
Hope this helps.
-Kevin

SPNego for multi-forest using IBM JDK

Hi All,
I need to setup SPNego authentication for EP7 and IBM JDK for a multi-forest landscape (2 Active directory domains). There's a guide about how to do this for Sun JDK : https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c771c3d3-0c01-0010-b5b6-86755a2cf778 but I need one for IBM JDK as the login stack mudules are different.
Can anyone supply me with a guide or any helpful information regarding this ? Do you know if it works? I've currently got SPNego working for a single domain.
Thanks in Advance,
Anthony

Jan,
ok, thanks. I will now explain how I think we can help.
Firstly, to be sure you understand - I represent a SAP partner company known as CyberSafe, and we have a product which uses SPNEGO for Kerberos authentication in a browser environment, so my answer relates mainly to our product functionality, and not related to the SAP login module, which has less functionality.
I must also apologise in case anybody reading this thread has an issue with me discussing non-SAP software. My view is that the most important thing on this forum is to help you (the SAP customer) get a solution that meets your needs, and if this involves SAP Partner products as well as SAP products, then that is acceptable.
Firstly, our product does not use the Java implementation of Kerberos. Instead, we use a JNI (Java Native Interface) so that our host based Kerberos library can be used to implement the protocol. This means that any differences between IBM, SUN or any other vendor JDK version related to Kerberos functionality, multi-domain support etc. are not relavent to our product. We support many things in our product which are not supported in Java implementations of Kerberos, so you don't need to wait for new versions of JDK to take advantage.
Secondly, and perhaps more relavent to this discussion is that our login module authenticates the user by decrypting the service ticket received using the key in the Key Table File on the host, and then we map this principal name onto a SAP user id. We then (via. the login module stack) cause the SAP system to issue an SSO2 logon ticket for this user id. The secret is the way we perform the mapping - we are not dependant on UME datasources for this, and I will describe below how we acheive mapping by using an example :
Lets suppose a user is authenticated as user.name@DOMAIN1, the SAP system login module has been setup using domain 2 (Realm = DOMAIN2) and trusted via a key in a key table file, with principal name of HTTP/hostname@DOMAIN2. Then, using normal Kerberos cross realm trust, and cross realm TGTs the browser requests a ticket from AD for HTTP/hostname@DOMAIN2, and this is issued by AD in domain 2 using the cross realm TGT, but the principal name of the authenticated user inside this service ticket is user.name@DOMAIN1. The login module on the SAP server can decrypt the ticket it receives to find the users Kerberos principal name.
So, the login module knows the user is user.name@DOMAIN1, it then has to decide how to determine the SAP user id. Our login module currently supports two different methods of performing this mapping, but we are adding more methods in each release to make the product even more flexible. Currently we support the following methods :
1. Simple mapping - this is where we remove the realm name and convert the principal name to upper case, so in this example user.name@DOMAIN1 would be mapped to a SAP userid of USER.NAME and used to issue an SSO2 ticket. Clearly this is only suitable for single domains, and makes administration very easy - many of our customers use this method, but you would need a different mapping method due to yoru multiple domains.
2. USRACL mapping - Since we also sell an SNC product for SAP GUI SSO, our customers already maintain mapping of Kerberos principal name to SAP user id using a table in ABAP engine called USRACL. This table is maintained using SU01 transaction. We now have support in our login module to read the USRACL table using the authenticated Kerberos principal name of the user (e.g. user.name@DOMAIN1) and find the required SAP user id, so that an SSO2 logon ticket can be issued.
I hope this helps you understand. If you are interested in more detail about our product, and how we might be able to help you, please feel free to contact me offline instead of via this forum.
Thanks,
Tim

Encryption program does not work in IBM JDK

Hi
I have a encrypt, decrypt program, which does not work in IBM JDK
the code is as below, it gives PBEWithMD5AndDES does not exist kind of error when running with IBM JDK
import java.io.UnsupportedEncodingException;
import java.security.spec.AlgorithmParameterSpec;
import java.security.spec.KeySpec;
import javax.crypto.Cipher;
import javax.crypto.IllegalBlockSizeException;
import javax.crypto.SecretKey;
import javax.crypto.SecretKeyFactory;
import javax.crypto.spec.PBEKeySpec;
import javax.crypto.spec.PBEParameterSpec;
public class MapsPasswordUtil
     Cipher ecipher;
     Cipher dcipher;
     // 8-byte Salt
     byte[] salt = { (byte) 0xA9, (byte) 0x9B, (byte) 0xC8, (byte) 0x32,
               (byte) 0x56, (byte) 0x35, (byte) 0xE3, (byte) 0x03 };
     // Iteration count
     int iterationCount = 19;
     public MapsPasswordUtil(String passPhrase)
          try
               KeySpec keySpec = new PBEKeySpec(passPhrase.toCharArray(), salt,
                         iterationCount);
               SecretKey key = SecretKeyFactory.getInstance("PBEWithMD5AndDES")
                         .generateSecret(keySpec);
               ecipher = Cipher.getInstance(key.getAlgorithm());
               dcipher = Cipher.getInstance(key.getAlgorithm());
               // Prepare the parameter to the ciphers
               AlgorithmParameterSpec paramSpec = new PBEParameterSpec(salt,
                         iterationCount);
               // Create the ciphers
               ecipher.init(Cipher.ENCRYPT_MODE, key, paramSpec);
               dcipher.init(Cipher.DECRYPT_MODE, key, paramSpec);
          } catch (java.security.InvalidAlgorithmParameterException e)
               e.printStackTrace();
          } catch (java.security.spec.InvalidKeySpecException e)
               e.printStackTrace();
          } catch (javax.crypto.NoSuchPaddingException e)
               e.printStackTrace();
          } catch (java.security.NoSuchAlgorithmException e)
               e.printStackTrace();
          } catch (java.security.InvalidKeyException e)
               e.printStackTrace();
     public String encrypt(String str)
          try
               // Encode the string into bytes using utf-8
               byte[] utf8 = str.getBytes("UTF8");
               // Encrypt
               byte[] enc = ecipher.doFinal(utf8);
               // Encode bytes to base64 to get a string
               return new sun.misc.BASE64Encoder().encode(enc);
          } catch (javax.crypto.BadPaddingException e)
               e.printStackTrace();
          } catch (IllegalBlockSizeException e)
               e.printStackTrace();
          } catch (UnsupportedEncodingException e)
               e.printStackTrace();
          return null;
     public String decrypt(String str)
          try
               // Decode base64 to get bytes
               byte[] dec = new sun.misc.BASE64Decoder().decodeBuffer(str);
               // Decrypt
               byte[] utf8 = dcipher.doFinal(dec);
               // Decode using utf-8
               return new String(utf8, "UTF8");
          } catch (javax.crypto.BadPaddingException e)
               e.printStackTrace();
          } catch (IllegalBlockSizeException e)
               e.printStackTrace();
          } catch (UnsupportedEncodingException e)
               e.printStackTrace();
          } catch (java.io.IOException e)
               e.printStackTrace();
          return null;
}

Works for me with the latest IBM JDK. You will need to specify your context i.e. what platform, what JDK/JRE etc etc etc.
P.S. That exception handling is rubbish.
Edited by: sabre150 on Mar 23, 2009 6:01 AM
I suspect that you are using JDK 1.5 and that you have fallen foul of the bug where key.getAlgorithm() does net return the correct value. You get round this by specifying it as             SecretKey key = SecretKeyFactory.getInstance("PBEWithMD5AndDES").generateSecret(keySpec);
            ecipher = Cipher.getInstance("PBEWithMD5AndDES");Of course if you are clever you will just define a static final constant for this algorithm.
Edited by: sabre150 on Mar 23, 2009 6:09 AM

Different complining result between SUN JDK 1.4 and IBM JDK 1.3.1

Hi! I simplifed my code as following:
public class TestException2 {
    public Object test() {
        java.sql.Connection cn = null;
        try {
             // 1st. close
            cn.close();
        catch (java.sql.SQLException se) {
             // 2nd. close
            cn.close();
        finally {
            return new Object();
}But I get different compiling result betwueen SUN JDK 1.4.2 and IBM JDK 1.3.1 (I have to deploied my app to the websphere 5.0)
In Sun JDK 1.4.2, I only got a warning:
[e:\work\test]javac TestException2.java
TestException2.java:14: warning: finally clause cannot complete normally
        ^
1 warningIn IBM JDK 1.3.1, I got an error:
TestException2.java:10: unreported exception java.sql.SQLException; must be caught or declared to be
thrown
            cn.close();
              ^
1 errorWhat happend? Who is right?
Thank you!
[ I believe the code should not pass the compilation ... ]

Many other people agree with you, including some Sun engineers.
Perhaps Sun just feels an obligation to continue to allow it for legacy reasons.
You might also investigate the compiler that comes with Eclipse.
http://www.eclipse.org/
It has a more flexible approach: for some cases, it lets you decide what is a warning and what is an error.

JSPM startup fails with IBM JDK 1.4.2 SR13

Hi experts,
I´m upgrading my Portal to EHP1 SP06. After the upgrade I checked SDM and JSPM, SDM is working fine but the JSPM don´t start any more.
I just getting the information after starting the script 'go' under AIX:
'Waiting for SDTServer to connect ...'
Nothing happened after 10min...
Just want to let you that this issue is caused by a buggy version of the AIX JDK.
There is a new sapnote 1422869 for this issue, please have a look.
Solution
Use the actual recommended "IBM JDK 1.4.2 SR13 FP4 ifix" or SR13 without any FP.
The problem was introduced with SR13 FP2 and is in FP3 and FP4 too.
Install the recommended "IBM JDK 1.4.2 SR13 FP4 ifix" to solve the problem (see SAP note 1008311 or 1024539). As a workaround you can use the remote GUI from another system using a not affected JDK.
I installed IBM JDK 1.4.2 SR13 without any FP and the JSPM is working again
You can get the new Java versions directly from IBM, click here to download it.
Regards,
Jens

Hi,
While installing solution manager 4 (SLES x86_64) I also run into the problem "ibjvm.so preloadLibrary: /opt/IBMJava2-amd64-142/jre/bin/j9vm/libj9vm22.so: cannot open shared object file: No such file or directory" during the phase "Create Java users"
I've taken your advice (Chris B) and the installation carries on with out a problem. (and the java instance has started)
When I stop and start sap, I then cannot get the Java instance to start again!
The error in the "std_bootstrap.out" has the message; "libjvm.so preloadLibrary: /opt/IBMJava2-amd64-142/jre/libj9vm22.so: cannot open shared object file: No such file or directory
libjvm.so failed to load: j9vm22"
I have set all the environmental variables including the LD_LIBRARY_PATH and JAVA_HOME
I was wondering if you had the same problem, else if anyone else could please please help.
Thanks,
Chris G
Message was edited by: Chris Geladaris

WebLogic 5.1 & IBM JDK 1.1.8 on RedHat Linux 6.2

Similar Messages

Maybe you are looking for