Jdk1.3 vs jdk1.4 SASL authentication
I'm trying to get SASL authentication work with jdk1.3 and iPlanet Directory Server. Everytime I get same exception:
SASL authentication failed. Root exception is java.lang.NoSuchMethodError
When I try with jdk1.4 everything works fine. Now I'm just wondering that is there other things that I should take care when I try get authentication work with jdk1.3. I know that all the extension packages are integrated to the jdk1.4 and I have set same packages to the CLASSPATH when I'm trying to do same with jdk1.3, but same exception occurs than above.
Does anyone know what's the problem?
Thanks,
Janne
Hi ,
Jsse 1.0.3 (strictly this version only) is needed along with jdk1.3 for the SASL or SSL authentication to be done fine.
Hope this helps,
Regards,
Sathya
Similar Messages
-
Jdk1.3 vs jdk1.4 and SASL authentication
I'm trying to get SASL authentication work with jdk1.3 and iPlanet Directory Server. Everytime I get same exception:
SASL authentication failed. Root exception is java.lang.NoSuchMethodError
When I try with jdk1.4 everything works fine. Now I'm just wondering that is there other things that I should take care when I try get authentication work with jdk1.3. I know that all the extension packages are integrated to the jdk1.4 and I have set same packages to the CLASSPATH when I'm trying to do same with jdk1.3, but same exception occurs than above.
Does anyone know what's the problem?
Thanks,
JanneHi ,
Jsse 1.0.3 (strictly this version only) is needed along with jdk1.3 for the SASL or SSL authentication to be done fine.
Hope this helps,
Regards,
Sathya -
SASL Authentication...again...
Last time i posted this question:
While using iDS 5.1 and a test user "uid=jdoe,ou=xxx,o=xxx" we've been getting same results over and over again: Authentication failed. Passwords are being set to CLEARTEXT, user being created using default user template so it contains the userpassword-attribute, and in the Java-code we've been using MD5 Digest authentication 'cause that's the method it supports. This is what is being done in the code:
1. Client connects server using ldapHost and ldapPort.
2. Hashtable "env" is being constructed.
3. Environment properties INITIAL_CONTEXT_FACTORY, PROVIDER_URL, SECURITY_PRINCIPAL and SECURITY_CREDENTIALS of context are being specified.
4. if ldapconnection.isauthenticated() is TRUE, print "success", else print "failed".
All environment properties are of course used via env.put(context.property_name, "value");
Is this it? What else should it do? All values match the ones being set in DS. Still authentication fails. "
We still have this problem but the thing that has come up is the supportedSASLMechanisms gives "no attributes" if asked with database name, but gives correct values when asked just with IP-address of server. To make long story short, this works:
Attributes attrs = ctx.getAttributes("ldap://<ip-address>"new String[]{"supportedSASLMechanisms"});
System.out.println(attrs);
This doesn't work:
Attributes attrs = ctx.getAttributes("ldap://<ip-address>/o=<organization>"new String[]{"supportedSASLMechanisms"});
System.out.println(attrs);
Is there a access control in NetscapeRoot that differs from our database controls that makes this happen?I think I have get little bit closer to get SASL authentication work, but now my program throws this kind of exception:
javax.naming.AuthenticationException: SASL authentication failed. Root exception is java.lang.NoSuchMethodError
at com.sun.jndi.ldap.sasl.LdapSasl.saslBind(LdapSasl.java:116)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.jndi.ldap.LdapClient.saslBind(LdapClient.java:369)
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:185)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2386)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:239)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:74)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:78)
My code (I'm using jdk1.3.1):
import javax.naming.*;
import javax.naming.directory.*;
import java.util.Hashtable;
class DigestTesti {
public static void main(String[] args) {
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL, "ldap://000.000.000.000:000");
env.put(Context.SECURITY_AUTHENTICATION, "DIGEST-MD5");
env.put(Context.SECURITY_PRINCIPAL, "dn:uid=JDoe,ou=...,o=...,dc=..., dc=...");
env.put(Context.SECURITY_CREDENTIALS, "...");
env.put("java.naming.security.sasl.realm", "...");
try {
DirContext ctx = new InitialDirContext(env);
System.out.println(ctx);
} catch (NamingException e) {
e.printStackTrace();
What could been wrong with my code?
Regards,
Janne -
Cannot use SASL Authentication Through GSSAPI on DS 6.3
I try to kerberized DS 6.3. I do step by step instruction from "Sun Java System Directory Server Enterprise Edition 6.3" and it doesn't work.
When I try to configure the Directory Server to Enable GSSAPI I get an error:
modifying entry cn=SASL,cn=security,cn=config
ldap_modify: DSA is unwilling to perform
ldap_modify: additional info: Modification not allowed on attribute dsSaslPluginsPath
After all when I try to authenticate to the Directory Server i get response:
ldap_sasl_interactive_bind_s: Authentication method not supported
ldap_sasl_interactive_bind_s: additional info: sasl mechanism not supported
Logs file:
+[22/Sep/2008:10:28:11 +0200] conn=2 op=-1 msgId=-1 - fd=22 slot=22 LDAP connection from 10.3.233.4:33054 to 10.3.233.4+
+[22/Sep/2008:10:28:11 +0200] conn=2 op=0 msgId=1 - BIND dn="" method=sasl version=3 mech=GSSAPI+
+[22/Sep/2008:10:28:11 +0200] conn=2 op=0 msgId=1 - RESULT err=7 tag=97 nentries=0 etime=0, sasl mechanism not supported+
+[22/Sep/2008:10:28:11 +0200] conn=2 op=1 msgId=2 - UNBIND+
+[22/Sep/2008:10:28:11 +0200] conn=2 op=1 msgId=-1 - closing from 10.3.233.4:33054 - U1 - Connection closed by unbind client -+
+[22/Sep/2008:10:28:12 +0200] conn=2 op=-1 msgId=-1 - closed.+
system specyfication:
Solaris 10 x86 64-bit
DS 6.3 B2008.0311.0212 NATSee http://forums.sun.com/thread.jspa?forumID=761&threadID=5202246 for a description of the problem and a workaround.
If you have a Sun support contract, you can request an escalation of CR 6637404.
Also, note that it looks like part of the documentation went missing. In DS5.2 the docs included an additional step
Chapter 11 Implementing Security
Configuring Client Authentication
SASL Authentication Through GSSAPI (Solaris Only)
http://docs.sun.com/source/816-6698-10/ssl.html#18500
ldapmodify -D 'cn=directory manager'
dn: cn=SASL,cn=security,cn=config
changetype: modify
add: dsSaslPluginsEnable
dsSaslPluginsEnable: GSSAPI
replace: dsSaslPluginsPath
dsSaslPluginsPath: /usr/lib/mps/sasl2/libsasl.so
modifying entry cn=SASL,cn=security,cn=config
ldap_modify: DSA is unwilling to perform
ldap_modify: additional info: Adding attributes is not allowed
------------------------------------------------------------- -
Difference between JDB of jdk1.3 & jdk1.4 (hot swap)
Hello all,
I have compiled & enahnced ny classes using jdk1.3.
By enhancing the classes I mean I am modifying the classfile at bytecode level & not at source code level. For enhancing the classes we load the original classes once & then change the bytecodes.
When I try to debug the the classes after enhancement using JDB of jdk1.3 I am getting error like,
"Unable to set breakpoint Person:11 : No linenumber information for Person. Try compiling with debugging on."
But when debugged the class using JDB of jdk1.4 its working fine.
Did anybody come around this situation anytime?
Do anybody know , is there any difference in JDB of jdk1.3 & jdk1.4?
According to jdk1.4 datasheet, JDB 1.4 provides one feature
called "hotswap". Does this feature helping us to debug the classes even after enhancement? If yes then how it is doing?Hello all,
I have compiled & enahnced ny classes using jdk1.3.
By enhancing the classes I mean I am modifying the
e classfile at bytecode level & not at source code
level. For enhancing the classes we load the original
classes once & then change the bytecodes.What kind of changes are you making when you "enhance"?
Do you write the modified .class files out again, and
then run them? Is the debug information in the new .class
file (line number table, local variable information, etc)
still accurate and consistent after your modification?
Do the enhanced classes run OK when you turn on verification?
EG: without debugging, can you run them with -Xfuture
added to the command line?
Can you use javap -l -verbose <class id> to inspect
the modified class?
When I try to debug the the classes after
r enhancement using JDB of jdk1.3 I am getting error
like,
"Unable to set breakpoint Person:11 : No linenumber
information for Person. Try compiling with debugging
on."
But when debugged the class using JDB of jdk1.4 its
working fine.
Did anybody come around this situation anytime?
Do anybody know , is there any difference in JDB of
jdk1.3 & jdk1.4?
According to jdk1.4 datasheet, JDB 1.4 provides one
feature
called "hotswap". Does this feature helping us to
debug the classes even after enhancement? If yes then
how it is doing?"hotswap" allows you to redefine the bytecodes of a class. Not all
JVM implementations support this feature. Refer to this page for more
information:
http://java.sun.com/j2se/1.4.1/docs/guide/jpda/jdi/com/sun/jdi/VirtualMachine.html#redefineClasses(java.util.Map)
redefineClass is implemented in the jdb reference debugger
via the redefine <class id> <class file name> command. -
On solaris10, Performance of JDK1.6_12/JDK1.6_19 is worse than JDK1.5_22?
1. My test is ON solaris 10
bash-3.00# cat /etc/release
Solaris 10 5/08 s10s_u5wos_10 SPARC
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 24 March 2008
T-3000 Recovery Version: T3.04.01.01 Tue Nov 25 08:25:07 CST 2008
bash-3.00#
bash-3.00# showrev
Hostname: T2000G2
Hostid: 84cb7384
Release: 5.10
Kernel architecture: sun4v
Application architecture: sparc
Hardware provider: Sun_Microsystems
Domain: emsdomain
Kernel version: SunOS 5.10 Generic_137111-052. My test code:
public class Test {
public static void main(String[] args){
long start = System.currentTimeMillis();
int n=0;
for (long i=0;i<100000000;i++){
n ++;
System.out.println("time: "+(System.currentTimeMillis()-start)/1000.0);
}3.Test result
a) Default JDK is JDK1.6_12.
It print:
bash-3.00# java Test
time: 2.834b) Latest JDK1.6_19:
It print:
bash-3.00# java Test
time: 2.912c) JDK1.5_22
It print:
bash-3.00# java Test
time: 1.0394.Summary:
JDK1.6_12/JDK1.6_19 is almost *3 times slower than* JDK1.5_22.
After J2SE_Solaris_10_Recommended.zip is installed(ONLY part of them is installed successfully),
the result is the same!!!
Does this because the solaris 10 OS is not patched with the latest patch[10_Recommended.zip]?
Edited by: xiangyingbing on Apr 8, 2010 8:31 PMI am wondering why the default JDK1.6_12 on solaris is sooooooooooooooooo slow！！！
I am wondering why the default JDK1.6_12 on solaris is sooooooooooooooooo slow！！！
I am wondering why the default JDK1.6_12 on solaris is sooooooooooooooooo slow！！！ -
Mail SASL authentication problem - solved
My outgoing mail stopped working. I had been relaying mail through my ISP's smtp server and at some point i started getting SASL authentication errors ("no worthy mechs found").
I searched and found a thread that contained a fix: http://discussions.apple.com/thread.jspa?threadID=2207959
The fix was rather mysterious (to me at least) in that it involved adding one line to my /etc/postcript/main.cf file. The line was: "smtpsasl_securityoptions =".
I was going to post a reply to the thread, but the thread is "archived".
Why do threads get archived? Too old?
Well, anyway, I don't like having to open a separate thread for this, but I hope this helps someone solve the same problem I was having.
Also, if anyone has any kind of real explanation for why this fix works and/or whether it is likely to survive future software changes made by apple (or has a better way to fix that will), I would love to hear about it.
Thanks.Try installing ldap1.2.4 and putting ldap.jar and providerutil.jar in your bootclasspath.
-
Is this a bug in Swing in JDK1.6/JDK1.7 but not in JDK1.5?
I have an application for which GUI was developed in Java Swing JDK1.5.I am planning to upgrade the JDK to JDK1.6 but doing so produces problem for me.
Problem Statement : If I open few dialogs(say 10) and dispose them and than call method 'getOwnedWindows()' , it returns 0 in JDK1.5 but returns 10 in JDK1.6. As in JDK1.6 it returns 10, my algorithm to set focus is not working correctly as it is able to find invlaid/disposed dialogs and try to set the focus on it but not on the correct and valid dialog or component because algorithm uses getOwnedWindows() to get the valid and currently open dialog.
Can anyone suggest me the workaround to avoid this problem in JDK1.6?
Following piece of code can demonstrate the problem.
Custom Dialog Class :
import javax.swing.JDialog;
import java.awt.event.ActionListener;
import javax.swing.JPanel;
import javax.swing.JFrame;
import javax.swing.JLabel;
import javax.swing.JButton;
import java.awt.event.ActionEvent;
public class CustomDialog extends JDialog implements ActionListener {
private JPanel myPanel = null;
private JButton yesButton = null;
private JButton noButton = null;
private boolean answer = false;
public boolean getAnswer() { return answer; }
public CustomDialog(JFrame frame, boolean modal, String myMessage) {
super(frame, modal);
myPanel = new JPanel();
getContentPane().add(myPanel);
myPanel.add(new JLabel(myMessage));
yesButton = new JButton("Yes");
yesButton.addActionListener(this);
myPanel.add(yesButton);
noButton = new JButton("No");
noButton.addActionListener(this);
myPanel.add(noButton);
pack();
setLocationRelativeTo(frame);
setVisible(true);
//System.out.println("Constrtuctor ends");
public void actionPerformed(ActionEvent e) {
if(yesButton == e.getSource()) {
System.err.println("User chose yes.");
answer = true;
//setVisible(false);
else if(noButton == e.getSource()) {
System.err.println("User chose no.");
answer = false;
//setVisible(false);
public void customFinalize() {
try {
finalize();
} catch (Throwable e) {
e.printStackTrace();
}Main Class:
import java.awt.event.ActionListener;
import javax.swing.JFrame;
import javax.swing.JButton;
import java.awt.event.WindowAdapter;
import java.awt.event.WindowEvent;
import java.awt.event.ActionEvent;
import java.awt.FlowLayout;
import java.awt.Window;
public class TestTheDialog implements ActionListener {
JFrame mainFrame = null;
JButton myButton = null;
JButton myButton_2 = null;
public TestTheDialog() {
mainFrame = new JFrame("TestTheDialog Tester");
mainFrame.addWindowListener(new WindowAdapter() {
public void windowClosing(WindowEvent e) {System.exit(0);}
myButton = new JButton("Test the dialog!");
myButton_2 = new JButton("Print no. of owned Windows");
myButton.addActionListener(this);
myButton_2.addActionListener(this);
mainFrame.setLocationRelativeTo(null);
FlowLayout flayout = new FlowLayout();
mainFrame.setLayout(flayout);
mainFrame.getContentPane().add(myButton);
mainFrame.getContentPane().add(myButton_2);
mainFrame.pack();
mainFrame.setVisible(true);
public void actionPerformed(ActionEvent e) {
if(myButton == e.getSource()) {
System.out.println("getOwnedWindows 1 " + mainFrame.getOwnedWindows().length);
createMultipleDialogs();
int i = 0;
for (Window singleWindow : mainFrame.getOwnedWindows()) {
System.out.println("getOwnedWindows " + i++ + " "
+ singleWindow.isShowing() + " "
+ singleWindow.isVisible() + " " + singleWindow);
System.out.println("getOwnedWindows 2 " + mainFrame.getOwnedWindows().length);
//System.gc();
System.out.println("getOwnedWindows 3 " + mainFrame.getOwnedWindows().length);
//System.gc();
System.out.println("getOwnedWindows 4 " + mainFrame.getOwnedWindows().length);
} else if (myButton_2 == e.getSource()) {
System.out.println("getOwnedWindows now: " + mainFrame.getOwnedWindows().length);
public void createMultipleDialogs() {
for (int a = 0; a < 10; a++) {
CustomDialog myDialog = new CustomDialog(mainFrame, false,
"Do you like Java?");
myDialog.dispose();
myDialog.customFinalize();
public static void main(String argv[]) {
TestTheDialog tester = new TestTheDialog();
}Running the above code gives different output for JDK1.5 and JDK1.6
I would appreciate your help in this regards.
ThanksFix your algorithm to check if the windows are displayable/showing instead of assuming they are?
-
Diff Between Jdk1.3 & Jdk1.4(abt stack trace)
Jdk 1.4 gives a facility that we can aceess stack trace across jvms but we cant' do it through 1.3. If we want to achieve through jdk1.3 then how can we do it.
See printStackTrace(PrintStream s) and printStackTrace(PrintWriter s)
Kaj -
I am developing support for the DIGEST-MD5 sasl mechnism on a c-ldap client. I am using the evaluation version of the iPlanet Directory Server 5.0 which lists DIGEST-MD5 as a supported SASL mechanism. The server is running on NT 4.0 After installing the Directory Server with the test database, a changed the passwordStorageScheme from the default of SSHA to clear text. I then added my test user. When I run my test I always get back a resultCode of 49 (invalidCredentials). The digest-challenge I receive from the server and my digest-response are shown below. I have satisfied myself that the calculation of the response directive in the digest response is correct. Does anyone see any problems in the digest response or have any other suggestions? Is there a known problem with the iPlanet Directory Server 5.0?
digest-challenge:
realm="BGB2.ndp.provo.novell.com",nonce="Ed8UPLXsWaC6CN",qop="auth",algorithm=md5-sess,charset=utf-8
digest-response:
username="uid=bgbrown,ou=people,dc=siroe,dc=com",realm="BGB2.ndp.provo.novell.com",cnonce="A9IuPJKr30RiwL",nc=00000001,qop=auth,digest-uri="ldap/BGB2.ndp.provo.novell.com",response=97061205298e5ebaf206c8ac3598fdce,charset=utf-8,nonce="Ed8UPLXsWaC6CN"Found the answer. When the username is an LDAP DN it needs to be proceeded by "dn:".
example: username="dn:uid=bgbrown,ou=people,dc=siroe,dc=com"
The server also accepts a simple uid value.
example: username="bgbrown" -
While using iDS 5.1 and a test user "uid=jdoe,ou=xxx,o=xxx" we've been getting same results over and over again: Authentication failed. Passwords are being set to CLEARTEXT, user being created using default user template so it contains the userpassword-attribute, and in the Java-code we've been using MD5 Digest authentication 'cause that's the method it supports. This is what is being done in the code:
1. Client connects server using ldapHost and ldapPort.
2. Hashtable "env" is being constructed.
3. Environment properties INITIAL_CONTEXT_FACTORY, PROVIDER_URL, SECURITY_PRINCIPAL and SECURITY_CREDENTIALS of context are being specified.
4. if ldapconnection.isauthenticated() is TRUE, print "success", else print "failed".
All environment properties are of course used via env.put(context.property_name, "value");
Is this it? What else should it do? All values match the ones being set in DS. Still authentication fails.Some update, i got it working with SSL disabled.
-
I want to authenticate using GSS-API for SMTP.
Can anyone please guide me?
Is there any doc or sample code available?Wow, this is an obscure solution, but it works. According to this thread, the problem is that:
Although Comcast advertises "AUTH LOGIN PLAIN", the Postfix SASL library won't do plain text auth by default. It needs to be told it's okay with:
smtp_sasl_security_options = noanonymous
Solution:
$ su -
$ cd /etc/postfix
$ cp main.cf main.cf.no_smtp_sasl_security_options
$ echo 'smtp_sasl_security_options = noanonymous' >> ./main.cf
$ serveradmin stop mail
$ serveradmin start mail
I'm not sure how often /etc/postfix/main.cf is overwritten, but presumably this happens every time you change and save Mail settings in Server Admin, so you must redo these steps every time you change the Mail server if you want to use smtp.comcast.net as your mail relay.
AAPL, would you please add a toggle to handle this in Server Admin? -
Hello,
I recently installed POSTFIX which uses SASL authentication, I have found javadocs for javax.security.sasl but am unsure how to implement these, does anyone have any experience of doing this?
Can I leave the rest of my smtp code and just alter the authentication bit, or will more need to change?
Any pointers appreciatedI think I have get little bit closer to get SASL authentication work, but now my program throws this kind of exception:
javax.naming.AuthenticationException: SASL authentication failed. Root exception is java.lang.NoSuchMethodError
at com.sun.jndi.ldap.sasl.LdapSasl.saslBind(LdapSasl.java:116)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.jndi.ldap.LdapClient.saslBind(LdapClient.java:369)
at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:185)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2386)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:239)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:74)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:78)
My code (I'm using jdk1.3.1):
import javax.naming.*;
import javax.naming.directory.*;
import java.util.Hashtable;
class DigestTesti {
public static void main(String[] args) {
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL, "ldap://000.000.000.000:000");
env.put(Context.SECURITY_AUTHENTICATION, "DIGEST-MD5");
env.put(Context.SECURITY_PRINCIPAL, "dn:uid=JDoe,ou=...,o=...,dc=..., dc=...");
env.put(Context.SECURITY_CREDENTIALS, "...");
env.put("java.naming.security.sasl.realm", "...");
try {
DirContext ctx = new InitialDirContext(env);
System.out.println(ctx);
} catch (NamingException e) {
e.printStackTrace();
What could been wrong with my code?
Regards,
Janne -
Changing from JDK 1.2 to JDK1.3
Hello,
I have JDK1.2, JDK1.3 and JDK 1.4 in my system. By default the version is taken as JDK 1.2.
I need to change this to 1.3. I have tried changing the registry settings which didn't work.
Any suggestions on this would be appriciated
Regards
V123Maybe my question did not have the correct approach.
I need to develop a web service client which must run on java virtual machine 1.2
I ve tried with axis, glue and jax-rpc but all they need the java.lang.reflect.InvocationHandler interface available since jdk1.3
So the question is: What can I use to write that client without that interface? -
No ocijdbc8 Error (RH71,ORA816,JDK1.3)
I meet same ploblem when change any element
for connect remote db:
Exception in thread "main" java.lang.UnsatisfiedLinkError: no ocijdbc8 in java.l
ibrary.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
at oracle.jdbc.oci8.OCIDBAccess.logon(OCIDBAccess.java:209)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:198)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.ja
va:251)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:224)
at java.sql.DriverManager.getConnection(DriverManager.java:517)
at java.sql.DriverManager.getConnection(DriverManager.java:177)
at JdbcCheckup.main(JdbcCheckup.java:42)
the program is $ORACLE_HOME/jdbc/demo/samples/oci8/bisic_samplem/JdbcCheckup.java
OS: RH7.1(japanese)
JDK : JDK1.3(JDK1.2.2 dont work on RH71)
ORACLE: oracle EE816 for Linux
(libocijdbc8.so is in the $ORACLE_HOME/lib)
JDBC: classes12.zip for solaris(oracle816)
please help me,thank you.
xu
nullXu Fang,
OCI8 (JDBC 1.2 'thick' driver) is not supported on Linux (8.1.5,8.1.6 or 8.1.7). You can use the thin driver, but not the OCI8 driver.
Regards,
Josue Amaro
Linux Product Manager
Oracle Corporation
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Xu FANG ([email protected]):
I meet same ploblem when change any element
for connect remote db:<HR></BLOCKQUOTE>
null
Maybe you are looking for
-
Is it possible to use a 30" Apple display with a Windows PC laptop?
First let me say that I can't switch to a Mac, since this is what they gave me at work. OK, that being said, I have an IBM ThinkPad T43 (not a bad computer by the way, it's reliable). I have this hooked into a docking station and it is currently powe
-
How to delete tweet in Twitter app
Hello, i want to ask you how to delete a tweet in Twitter for iPad. Thx and sorry for my bad english ;-) Mark.
-
Please tell me, which is better either BASE64 or Quoted-Printable.
Hello all. Does anyone tell me, Which is better on MIME either BASE64 or Quoted-Printable? I'm not so familiar with MIME. Any Opinion will be appreciated. Thanks. p.s. excuse me for my english.
-
I1111 for SC (Item in Transfer Process)
Hi, Business is using SRM 3.0 ECS. Scenario is that User is creating Shopping cart thru Catalogue and there is Approval process for SC. Once the SC gets approved PO is created by the system.(I1113).For this perticular SC error is Item in transfer pro
-
How Do I Uninstall Flash Player From My Mac?
I can't install the correct flash player version on my macbook until I uninstall the incorrect version. How do I uninstall it?