AES in JDK 1.3.1_06

HI,
This is realy realy urgent.
Ca anybody tell me if I can user AES encryption in JDK 1.3.1_06. I tried with JCE 1.2.2 provider bu got
"No Such Algorithm exists java.security.NoSuchAlgorithmException: Cannot find any provider supporting AES"
error -
Following is the sample steps I used -
String key2 = "FFF3454D1E9CCDE00101010101010101";
byte [] keybytes = key2.getBytes();
SecretKeySpec keyspec = new SecretKeySpec(keybytes, "AES");
Cipher aesCipher = Cipher.getInstance("AES");
aesCipher.init(Cipher.ENCRYPT_MODE,keyspec);
strDataToEncrypt = "Hello World of Encryption using AES ";
byte[] byteDataToEncrypt = strDataToEncrypt.getBytes();
byte[] byteCipherText = aesCipher.doFinal(byteDataToEncrypt);
please help me in this, using JDK version 1.3.1_06
Thanks and Regards,
Andy

www.bouncycastle.org

Similar Messages

9.0.4 compatibility with jdk 1.5

Hi,
Please do let me know if Oracle AS version 9.0.4.1 is compatible with jdk 1.5.
What is the jdk version compatible with 9.0.4.1?
Found the following in the Metalink -> Certify
In general, Oracle Application Server 10g (9.0.4, 10.1.2.x and 10.1.3.x) support using JDK
extensions higher than one the product originally shipped with. On 9.0.4, it is possible to move from JDK 1.3.1_06 to extension JDK 1.3.1_07 or beyond.
Does this imply that 9.0.4 is certified with JDK 1.5?????
Thanks in advance.
Regards,
Sindhiya V.

desuported? Can you post a source for this?
9.0.4 is not certified with JDK 1.5 and will not be. AS 10.1.3 is the first release that is (as far as I know).

JDialog Buttons don't respond in JDK 1.3.1

Hi,
I recently had to change from JDK 1.3 to JDK 1.3.1, in order to be able to use the MS Global IME and Japanese Characters in my App.
The problem is that some of my Dialogs stopped responding both to mouse and keyboard events (I can still close the Dialog through the window menu and the (x) button on the top-right corner).
I've looked in the Bug database, and found some entries that look like what I'm getting (http://developer.java.sun.com/developer/bugParade/bugs/4531693.html). The status of these bugs is fixed (I don't know in which version). I downloaded JDK 1.3.1_06 (the last version for JDK 1.3.1!?) and still have the same problems.
If anyone has solved this problem or can help me solve it, I would really like to know!
TIA,
Paulo Breda

Actually, I think 1.4.1 also has the problem, eventhough I didn't test.
Anyway changing to 1.4.1 isn't a choice, because it would imply too many changes to the code, and to third-party components, that aren't supported...
If someone has a better solution, I'm willing to give my Duke dollars away!

JAXB for jdk1.3.1_06

I am using JDK 1.3.1_06.. So am I not going to be able to use the functionality of JAXB?? What version of the Web services pack should I be downloading to use the JAXB functionality, using an xsd schema and generating java files to store xml data .....
thank you for your reply

JAXB RI requires at least J2SE1.3.1

Type-mapping not working correctly, get "Unable to find a javaType for the xmlType" WARNING

I'm manually creating a web-services.xml file, and using the autogen ant task to
generate the codec XML/Java classes. The XML definition is provided by SAP.
The ant build.xml file:
<project name="buildWebservice" default="stubgen">
<target name="stubgen">
<clientgen ear="C:\projects\RMIS\ifrrequests\RMIS.ear"
packageName="com.aa.rmis.webservice.client"
clientJar="C:\projects\RMIS\ifrrequests\rmisws-client.jar"
autotype="False" />
</target>
<target name="all" depends="stubgen"/>
</project>
The problem is seen below in the output from Ant. Note the WARNINIG. The problem
is that the xml type cannot be mapped to the Java type.
C:\projects\RMIS\ifrrequests>ant -buildfile clientbuild.xml
Buildfile: clientbuild.xml
stubgen:
[clientgen] Generating client jar for RMIS.ear ...
[clientgen] WARNINIG: Unable to find a javaType for the xmlType:['urn:sap-com:do
cument:sap:business']:PaymentRequest.Create. Make sure that you have registered
this xml type in the type mapping
[clientgen] Using SOAPElement instead
[clientgen] Compiling 4 source files to C:\DOCUME~1\944377\LOCALS~1\Temp\rmisws-
client.jar-836624340
[clientgen] Building jar: C:\projects\RMIS\ifrrequests\rmisws-client.jar
BUILD SUCCESSFUL
Total time: 17 seconds
The Java source that has the implementation of the service methods is simply:
package com.aa.rmis.webservice;
import com.aa.rmis.ifr.request.*;
public class TestService
public TestService()
public int serviceRequest(PaymentRequestCreate request)
System.out.println("Received serviceRequest message");
return 0;
public void testStringRequest(String request)
The web-service.xml file is attached, which contains the schema for the SAP PaymentRequest.Create
object definition.
Another problem I have, which is probably related, is that the service method
that has a complex data type (non-built in data type) is not being deployed into
the WebLogic server. But the other service method that simply takes a String
parameter is.
The steps I took are:
1. Get XML from SAP Interface Repository (IFR) for PaymentRequest
2. Use ant task autogen to generate the request codec classes
3. Create the web-services.xml file by inserting the schema definition and the
mapping file created by the autogen task, and defining the operations
4. Build web-services.war file that contains all autogen compiled class files,
the web-services.xml file, and the service implementation class
5. Build the ear file that holds the web service files
6. Use the clientgen ant task to generate (included above) to generate the client
jar file that should contain the proxy for both of the service methods
Environment:
* WebLogic 7.02
* JDK 1.3.1_06
* JBuilder 9 Enterprise
* Ant 1.4
Possible causes:
* Namespace not being used correctly
* copied verbatim the mapping xml file generated by autogen into the web-services.xml
file
* xml-schema part of web-services.xml might not be set correctly
* operation definition might not be using the correct namespace
* Classpath used for ant might not be right
* Doubt this is the problem, but I'm out of other ideas
* Set by using the setWLEnv.cmd file provided by WebLogic
* Tried adding the generated classes directory for my project to the classpath,
but did not work
I've been referencing the Programming WebLogic Web Services document throughout
this entire process. I must be missing something.
Can anybody from BEA help me out with this problem?
Thanks in advance.
[web-services.xml]

Hi JD,
I spent a few cycles looking over your web-services.xml file, however I
don't have any suggestions other that one that looks like you have
already tried, at the top, in the <schema...>
targetNamespace="urn:sap-com:document:sap:business"
Making edits to these generated files can be tricky and my only
suggestion is to create a small reproducer to run by our outstanding
support team.
A quick look at our problem database shows one issue (CR095109) related
to a similar problem at deploy time that was fixed with 7.0SP3. Again,
the support folks will be able to help focus in on the issue.
Regards,
Bruce
JD wrote:
>
The first posting contains the wrong web-services.xml file. Please refer to this
one instead.
"JD" <[email protected]> wrote:
I'm manually creating a web-services.xml file, and using the autogen
ant task to
generate the codec XML/Java classes. The XML definition is provided
by SAP.
The ant build.xml file:
<project name="buildWebservice" default="stubgen">
<target name="stubgen">
<clientgen ear="C:\projects\RMIS\ifrrequests\RMIS.ear"
packageName="com.aa.rmis.webservice.client"
clientJar="C:\projects\RMIS\ifrrequests\rmisws-client.jar"
autotype="False" />
</target>
<target name="all" depends="stubgen"/>
</project>
The problem is seen below in the output from Ant. Note the WARNINIG.
The problem
is that the xml type cannot be mapped to the Java type.
C:\projects\RMIS\ifrrequests>ant -buildfile clientbuild.xml
Buildfile: clientbuild.xml
stubgen:
[clientgen] Generating client jar for RMIS.ear ...
[clientgen] WARNINIG: Unable to find a javaType for the xmlType:['urn:sap-com:do
cument:sap:business']:PaymentRequest.Create. Make sure that you have
registered
this xml type in the type mapping
[clientgen] Using SOAPElement instead
[clientgen] Compiling 4 source files to C:\DOCUME~1\944377\LOCALS~1\Temp\rmisws-
client.jar-836624340
[clientgen] Building jar: C:\projects\RMIS\ifrrequests\rmisws-client.jar
BUILD SUCCESSFUL
Total time: 17 seconds
The Java source that has the implementation of the service methods is
simply:
package com.aa.rmis.webservice;
import com.aa.rmis.ifr.request.*;
public class TestService
public TestService()
public int serviceRequest(PaymentRequestCreate request)
System.out.println("Received serviceRequest message");
return 0;
public void testStringRequest(String request)
The web-service.xml file is attached, which contains the schema for the
SAP PaymentRequest.Create
object definition.
Another problem I have, which is probably related, is that the service
method
that has a complex data type (non-built in data type) is not being deployed
into
the WebLogic server. But the other service method that simply takes
a String
parameter is.
The steps I took are:
1. Get XML from SAP Interface Repository (IFR) for PaymentRequest
2. Use ant task autogen to generate the request codec classes
3. Create the web-services.xml file by inserting the schema definition
and the
mapping file created by the autogen task, and defining the operations
4. Build web-services.war file that contains all autogen compiled class
files,
the web-services.xml file, and the service implementation class
5. Build the ear file that holds the web service files
6. Use the clientgen ant task to generate (included above) to generate
the client
jar file that should contain the proxy for both of the service methods
Environment:
* WebLogic 7.02
* JDK 1.3.1_06
* JBuilder 9 Enterprise
* Ant 1.4
Possible causes:
* Namespace not being used correctly
* copied verbatim the mapping xml file generated by autogen into
the web-services.xml
file
* xml-schema part of web-services.xml might not be set correctly
* operation definition might not be using the correct namespace
* Classpath used for ant might not be right
* Doubt this is the problem, but I'm out of other ideas
* Set by using the setWLEnv.cmd file provided by WebLogic
* Tried adding the generated classes directory for my project to
the classpath,
but did not work
I've been referencing the Programming WebLogic Web Services document
throughout
this entire process. I must be missing something.
Can anybody from BEA help me out with this problem?
Thanks in advance.
Name: web-services.xml
web-services.xml Type: ACT Project (text/xml)
Encoding: base64

Utf-8 encoding of SOAPPartImpl

The XML Document I am trying to send in a SOAP response contains an E with an
accent (comes from a UTF-8 Oracle db). On JDK 1.3.1_01 on Win2K, when I do not
set -Dfile.encoding (it defaults to ISO-8859-1) - the webservices throws an exception
that there are invalid characters (webservices spec says utf-8 only). When I
set -Dfile.encoding, it works fine. So it seems like SOAPPartImpl is doing a str.getBytes()
when it should be doing str.getBytes("utf-8"). OK, so that's one problem. I
get around it by setting -Dfile.encoding=utf-8.
But on Linux, JDK 1.3.1_06, -Dfile.encoding does not seem to have any effect.
Help? Ideas?
Thanks,
Mike

Setting weblogic.webservice.i18n.charset="UTF-8" didn't seem to work
But this did ...
LC_ALL="en_US.UTF-8"
export LC_ALL
"manoj cheenath" <[email protected]> wrote:
You can set the following system property:
weblogic.webservice.i18n.charset="UTF-8"
http://manojc.com
"Mike Reiche" <[email protected]> wrote in message
news:3ed6437b$[email protected]..
The XML Document I am trying to send in a SOAP response contains anE with
an
accent (comes from a UTF-8 Oracle db). On JDK 1.3.1_01 on Win2K,when I
do not
set -Dfile.encoding (it defaults to ISO-8859-1) - the webservices throwsan exception
that there are invalid characters (webservices spec says utf-8 only).When I
set -Dfile.encoding, it works fine. So it seems like SOAPPartImpl isdoing
a str.getBytes()
when it should be doing str.getBytes("utf-8"). OK, so that's oneproblem. I
get around it by setting -Dfile.encoding=utf-8.
But on Linux, JDK 1.3.1_06, -Dfile.encoding does not seem to have anyeffect.
Help? Ideas?
Thanks,
Mike

Custom tag attribute named operation

          Hi,
          I ported a web application from WL6.1sp4 to WL7.0sp2 and expirienced a wired problem.
          All my JSP's did not compile anymore. I received a error message "no setter for
          attribute operation defined", although there was a a method setOperation in the
          current code and there were no code modifications at all.
          After replacing all attributes named operation with opmode the system worked fine
          again.
          Is there any restriction in naming your attributes in custom tags?
          Thanks for help
          Michael


          Me again,
          I checked again the parameters of the VM (Sun JDK 1.3.1_06) and tried the the
          different options of the HotSpot compiler. I found out that the problem I reported
          with the last posting can easily be reproduced if you run the VM in HotSpot-Classic
          mode.
          I suppose it is a bug in Sun's VM for Windows. Does somebody have similar expiriences?
          Michael
          "Michael" <[email protected]> wrote:
          >
          >Hi,
          >
          >I ported a web application from WL6.1sp4 to WL7.0sp2 and expirienced
          >a wired problem.
          >All my JSP's did not compile anymore. I received a error message "no
          >setter for
          >attribute operation defined", although there was a a method setOperation
          >in the
          >current code and there were no code modifications at all.
          >
          >After replacing all attributes named operation with opmode the system
          >worked fine
          >again.
          >
          >Is there any restriction in naming your attributes in custom tags?
          >
          >Thanks for help
          >Michael

WLS 6.1 SP4: bug in ExecuteThread's contextClassLoader behavior?

Platform: WebLogic Server 6.1 SP4, JDK 1.3.1_06, Windows
When creating a new thread from a serlvet with a current
thread of type "weblogic.kernel.ExecuteThread", the
contextClassLoader of the new thread is set incorrectly.
The contextClassLoader of the child thread should be of
type "weblogic.utils.classloaders.ChangeAwareClassLoader",
but instead is of type "sun.misc.Launcher$AppClassLoader".
By stepping through the code with a debugger, I was able
to determine that the ExecuteThread class has a private
variable named contextClassLoader and that it returns the
value of this variable from the getContextClassLoader
method.
When a Thread is created, its initialization code uses the
private contextClassLoader member of the Thread class from
the parent thread to set the contextClassLoader of the new
thread. Since the ExecuteThread class does not appear to
change that value (presumably by calling
super.setContextClassLoader()), the new thread now has the
incorrect context class loader.
Because of this, the code executing in the new thread uses
the wrong class loader for certain JNDI operations,
causing them to fail. Specifically calls to
NamingManager.getObjectInstance passing a Reference object
fails to create the instance because it does not have
access to the correct class loader.
Is this a known issue? When will it be fixed?

This looks like a bug. contact [email protected]
As a workaround try the following
Thread thread = new Thread();
thread.setContextClassLoader(Thread.currentThread().getContextClassLoader());
Zachary Roadhouse wrote:
Platform: WebLogic Server 6.1 SP4, JDK 1.3.1_06, Windows
When creating a new thread from a serlvet with a current
thread of type "weblogic.kernel.ExecuteThread", the
contextClassLoader of the new thread is set incorrectly.
The contextClassLoader of the child thread should be of
type "weblogic.utils.classloaders.ChangeAwareClassLoader",
but instead is of type "sun.misc.Launcher$AppClassLoader".
By stepping through the code with a debugger, I was able
to determine that the ExecuteThread class has a private
variable named contextClassLoader and that it returns the
value of this variable from the getContextClassLoader
method.
When a Thread is created, its initialization code uses the
private contextClassLoader member of the Thread class from
the parent thread to set the contextClassLoader of the new
thread. Since the ExecuteThread class does not appear to
change that value (presumably by calling
super.setContextClassLoader()), the new thread now has the
incorrect context class loader.
Because of this, the code executing in the new thread uses
the wrong class loader for certain JNDI operations,
causing them to fail. Specifically calls to
NamingManager.getObjectInstance passing a Reference object
fails to create the instance because it does not have
access to the correct class loader.
Is this a known issue? When will it be fixed?--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

SSL connection, KeyManager and TrustManager

Hello everyone,
I am trying to established an SSL connection to a OC4J Server. The server is correctly configured, as the communications using Internet Explorer goes well.
I am using JDK 1.3.1_06 with JSSE 1.0.3 and OC4J 9.0.3.
But now I have a stand-alone java program that sends SOAP messages to the ssl port in the server using JAXM. When I send the message, I received the following exception:
javax.net.ssl.SSLException: untrusted server cert chain
The following I tried was to connect using a socket to test the handshacking. I received the same exception.
I am using a KeyStore dinamically generated with the PKCS12 certificate of the cliente that is requesting the service, and a TrustStore dinamically generated with the CA certificate for both the client and the server. I am also tries to use the default cacerts file with this certificate imported in.
The KeyManager is initialized in this way:
----- KeyManager start -----
java.security.KeyStore ks = java.security.KeyStore.getInstance
     ("pkcs12", "SunJSSE");
ks.load(new FileInputStream(file),pass.toCharArray());
KeyManagerFactory kmf = KeyManagerFactory.getInstance     ("SunX509", "SunJSSE");
kmf.init(ks, pass.toCharArray());
KeyManager[] km = (KeyManager[])kmf.getKeyManagers();
----- KeyManager end -----
The TrustManager is initialized in this way:
----- TrustManager start -----
FileInputStream fis = new FileInputStream(file);
java.io.DataInputStream dis = new java.io.DataInputStream(fis);
byte[] bytes = new byte[dis.available()];
dis.readFully(bytes);
java.io.ByteArrayInputStream bais =
     new java.io.ByteArrayInputStream(bytes);
java.security.cert.CertificateFactory cf =          java.security.cert.CertificateFactory.getInstance("X.509");
java.security.cert.X509Certificate caCert =
     (java.security.cert.X509Certificate)
          cf.generateCertificate(bais);
java.security.KeyStore ksCA =
     java.security.KeyStore.getInstance("pkcs12", "SunJSSE");
ksCA.load(null, null);
ksCA.setCertificateEntry("trustedCA", caCert);
TrustManagerFactory tmf =
     TrustManagerFactory.getInstance("SunX509", "SunJSSE");
tmf.init(ksCA);
TrustManager[] tm = (TrustManager[])tmf.getTrustManagers();
----- TrustManager end -----
And finally, this is the way I create the ssl connection:
----- main start -----
// loads the jsse provider
System.setProperty("java.protocol.handler.pkgs",
     "com.sun.net.ssl.internal.www.protocol");
java.security.Security.addProvider(
     new com.sun.net.ssl.internal.ssl.Provider());
// keymanager
com.sun.net.ssl.KeyManager[] km = getKeyManager(args[0], args[1]);
// trustmanager
com.sun.net.ssl.TrustManager[] tm = getTrustManager(args[2]);
// ssl context configuration
com.sun.net.ssl.SSLContext ctx =
     com.sun.net.ssl.SSLContext.getInstance("SSL");
ctx.init(km, tm, null);
com.sun.net.ssl.HttpsURLConnection.setDefaultSSLSocketFactory(
     ctx.getSocketFactory());
// url
URL url = new URL(
     "https", my_ip
     my_port, a_page,
     new com.sun.net.ssl.internal.www.protocol.https.Handler());
// connection
com.sun.net.ssl.HttpsURLConnection conn =
     (com.sun.net.ssl.HttpsURLConnection)url.openConnection();
conn.connect();
----- main end -----
This is the full exception trace:
javax.net.ssl.SSLException: untrusted server cert chain
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.a(DashoA6275)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(DashoA6275)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(DashoA6275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(DashoA6275)
at java.io.OutputStream.write(OutputStream.java:56)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA6275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.doConnect(DashoA6275)
at com.sun.net.ssl.internal.www.protocol.https.NetworkClient.openServer(DashoA6275)
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.l(DashoA6275)
at com.sun.net.ssl.internal.www.protocol.https.HttpClient.<init>(DashoA6275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.<init>(DashoA6275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a(DashoA6275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsClient.a(DashoA6275)
at com.sun.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(DashoA6275)
at pruebas.SSLClient.main(SSLClient.java)
Has anyone some idea of what is happening. Thanks in advance,
Jorge Hidalgo

hi
how your client i.e stanadlone application (SOAP client) is getting the server certificates if client doesn't get the server certificate and vice versa then u will get this exception.
check on both side.
pras

Javax.mail.message.recipienttype not found

Hi,
I use jdev10g and i want to send a mail message.
Here's a little snip of my class for sending a mail.
Jdeveloper gives me a error about Message.RecipientType.TO.
"Member 'RecipientType' not found in javax.mail.Message"
import javax.mail.Message;
message.addRecipient(Message.RecipientType.TO,
new InternetAddress(to));
I've installed the javamail-1.1.3 API.
In my project properties -> libraries, i've added this library with the correct path to the jar file.
I'm sure that this API have this Message class.
What is going wrong, have i missed something ???
Greetings,
Peter

Hi! Srikanth,
1. I checked MailerEJB.deploy under "Dependency Analyzer",
I checked activation.jar and mail.jar under the J2EE node.
I did the same for the MailerJSP.deploy.
2. I used same jdeveloper version and jdk 1.3.1_06.
3. I did a clean deploy for the ejb and mailerjsp.deploy
4. I recompiled and run the jpr,
from the message window, I got:
C:\jdeveloper\jdk\bin\javaw.exe -ojvm -classpath C:\oc4j\samples\ejb\EJBCallsJSP\classes;C:\oc4j\samples\ejb\EJBCallsJSP;C:\jdeveloper\jdev\lib\jdev-rt.jar;C:\jdeveloper\j2ee\home\lib\activation.jar;C:\jdeveloper\j2ee\home\lib\ejb.jar;C:\jdeveloper\j2ee\home\lib\jaas.jar;C:\jdeveloper\j2ee\home\lib\jaxp.jar;C:\jdeveloper\j2ee\home\lib\jcert.jar;C:\jdeveloper\j2ee\home\lib\jdbc.jar;C:\jdeveloper\j2ee\home\lib\jms.jar;C:\jdeveloper\j2ee\home\lib\jndi.jar;C:\jdeveloper\j2ee\home\lib\jnet.jar;C:\jdeveloper\j2ee\home\lib\jsse.jar;C:\jdeveloper\j2ee\home\lib\jta.jar;C:\jdeveloper\j2ee\home\lib\mail.jar;C:\jdeveloper\j2ee\home\oc4j.jar;C:\jdeveloper\jdbc\lib\classes12.jar;C:\jdeveloper\jdbc\lib\nls_charset12.jar oracle.otnsamples.ejbcallsjsp.mailclient.MailClientSample
I didn't see any error from this message window.
5. The no provider for smtp error is prompted from the mail client.
From above settings and running the application, I couldn't figure out where the error was coming from ?
Thanks
David

Aspects Developer "Verifier jar file not found error"

Hello all.
I'm working in a Java Card project and I have some troubles.
When I tried to compile, verify and load my solution in Aspects Developer's Software, I achieved the following error message: " could not found Verifier jar file".
So I couldn't test my applet nor simulate it.
Then I compiled myself (with Java Card's commands) and execute the verifier file provided with Java Card, and all was good, so i decided to test my java card applet on the simulator or the real card, both with Aspects Developer SW.
Then the error I got was "Read past end of stream".
What am I doing in the wrong way?What can I do test my applet in a Simulator?
Thank very much for your help.
Regards.
Mike L.

Hi,
This error message indicates that an incompatible version of the Java JDK is being used with Developer.
The release notes distributed with Developer are a little misleading. Currently Developer supports Java JDK versions greater than 1.2.2 but not 1.4.x. For example, I have JDK 1.3.1_06 installed on my machine.
Developer currently supports JavaCard development kit 2.1.2 and this specification restricts the versions of JDK that can be used. For more detail look at JCDevKit_User_Guide.pdf which can be found under <JAVA_CARD_INSTALL_DIR>\java_card_kit-2_1_2\doc\en\guides
Cheers,
Alasdair

Weblogic crashes with a coredump on solaris

Hi All,
Recently our weblogic server on solaris started to give core dumps.
It doesnt say why it crashed and the only available information are the
coredump file and the log file which is created for that crash. One other
noticable thing was somewhere in the output it said,
An irrecoverable stack overflow has occurred.
Unexpected Signal : 11 occurred at PC=0xb77e8
Function name=(N/A)
Library=(N/A)
NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.
Current Java thread:
Dynamic libraries:
0x10000 /opt/customer/bea/jdk131/jre/bin/sparc/native_threads/java
0xff350000 /usr/lib/libthread.so.1
0xff390000 /usr/lib/libdl.so.1
0xff200000 /usr/lib/libc.so.1
0xff330000 /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1
0xfe000000 /opt/customer/bea/jdk131/jre/lib/sparc/server/libjvm.so
0xff2e0000 /usr/lib/libCrun.so.1
0xff1e0000 /usr/lib/libsocket.so.1
0xff100000 /usr/lib/libnsl.so.1
0xff0d0000 /usr/lib/libm.so.1
0xff310000 /usr/lib/libw.so.1
0xff0b0000 /usr/lib/libmp.so.2
0xff080000 /opt/customer/bea/jdk131/jre/lib/sparc/native_threads/libhpi.so
0xff050000 /opt/customer/bea/jdk131/jre/lib/sparc/libverify.so
0xfdc80000 /opt/customer/bea/jdk131/jre/lib/sparc/libjvm.so
0xfe7c0000 /opt/customer/bea/jdk131/jre/lib/sparc/libjava.so
0xff020000 /opt/customer/bea/jdk131/jre/lib/sparc/libzip.so
0xfe560000 /usr/lib/locale/en_US.ISO8859-15/en_US.ISO8859-15.so.2
0xfe530000 /opt/customer/bea/jdk131/jre/lib/sparc/libhprof.so
0xfc920000 /opt/customer/bea/jdk131/jre/lib/sparc/libnet.so
0xfa6e0000 /usr/lib/nss_files.so.1
0xfa6c0000 /opt/customer/bea/wlserver6.1/lib/solaris/libmuxer.so
0xfa6a0000 /usr/ucblib/libucb.so.1
0xfa460000 /usr/lib/libresolv.so.1
0xfa420000 /usr/lib/libelf.so.1
Local Time = Wed May 29 15:21:52 2002
Elapsed Time = 13736
# HotSpot Virtual Machine Error : 11
# Error ID : 4F530E43505002C4 01
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Server VM (1.3.1_01 mixed mode)
# An error report file has been saved as hs_err_pid26165.log.
# Please refer to the file for further information.
Abort - core dumped
LD_LIBRARY_PATH=/opt/customer/bea/wlserver6.1/lib/solaris:/opt/customer/bea/
wlserver6.1/lib/solaris/oci816_8:/usr/local/lib
Any ideas? I can send the coredump if required.
Thank You
Saman

So your SP2 machines are more stabel than SP3 and SP4?
Thanks,
Chuck
Kevin Toomey wrote:
I'm seeing something similiar. I recently upgraded our admin server to SP4 and
JDK 1.3.1_06. Some of the managed servers in the domain are still at SP2 with
JDK 1.3.1_02. The admin server is crashing with no dumps and no error messages
to the log.
Hella <[email protected]> wrote:
We have been experiencing numerous crashes (with core dumps) runninig
6.1sp3 on Solaris 8 64-bit. The server is at the latest recommended
patch cluster (to include the J2SE patch cluster) We are using J2SE
1.3.1 and have tried all revisions to include 06. It seems the 04 rev
is
the most stable but still we get numerous crashes a day.
Does anyone know of any problems with the above combinations?
Thanks greatly,
Chuck

Font.properties

Is the jre using font.properties at all when displaying characters in the GUI? I removed all font.properties* files from my jre/lib directory and I am still able to display English characters and double-byte Korean characters. Certain fonts are not working for the Korean, but this all seems independent of the font.properties files. I'm using jdk 1.3.1_06.
Bleu

I have i18n.jar in my classpath and LocaleElements_ko.class is in it. The only font that works for me in Korean is Dialog with BOLD style. What relationship does font.properties have to i18n.jar? I guess the jre is getting the appropriate Font based on the Locale out of the i18n.jar? What do i need to do to get additional fonts (really I just want Dialog with PLAIN style) to work in Korean?
thanks,
Bleu

JDBC metadata problem

I have found an inconsistency when querying JDBC metadata. When using the DataBaseMetadata.getTypeInfo() method no line is returned for java.sql.Types.DECIMAL (numeric value 3). So it seams, that Oracle is not supporting this type. But when I'm querying metadata for table columns (DataBaseMetadata.getColumns) or user types (DataBaseMetadata.getUDTs) I can get java.sql.Types.DECIMAL as a value for column datatype.
I tried this with JDBC driver version 9.0.2.0.0 (that's what the manifest says) / 9.2.0.3.0 (that's what the DataBaseMetadata.getDriverVersion says) on JDK 1.3.1_06 and Oracle 9i Enterprise Release 9.0.1.0.0 server.
Am I missing something or is this a bug?

I have found an inconsistency when querying JDBC metadata. When using the DataBaseMetadata.getTypeInfo() method no line is returned for java.sql.Types.DECIMAL (numeric value 3). So it seams, that Oracle is not supporting this type. But when I'm querying metadata for table columns (DataBaseMetadata.getColumns) or user types (DataBaseMetadata.getUDTs) I can get java.sql.Types.DECIMAL as a value for column datatype.
I tried this with JDBC driver version 9.0.2.0.0 (that's what the manifest says) / 9.2.0.3.0 (that's what the DataBaseMetadata.getDriverVersion says) on JDK 1.3.1_06 and Oracle 9i Enterprise Release 9.0.1.0.0 server.
Am I missing something or is this a bug?

How do I time my program?

Hello all:
I have an assignment in which I am required to time(in milliseconds) how long the program takes to execute. Obviously the time will vary depending on the system that the code in run with. I am currently using WinXP and JDK 1.3.1_06.
Does anyone know how this is done? Is this done through the command-line, or is it something I have to build into my program?
Thanks.

Thank you, FoxyLady!!!
I tried it with my program on my XP laptop (1.7 gig cpu), time was 30 milliseconds, then on my old Win2K desktop (350 mg cpu), time was 191 milliseconds.
It appears to work perfectly!!

AES in JDK 1.3.1_06

Similar Messages

Maybe you are looking for