Problem with keystore

Good morning.
I have a certificate issued by Thawte.
The problem is that i lost the keystore that i used to create the certificate request.
I import certificate in a new keystore.
So that originates when I attempt start tomcat, i have the following error:
No available certificate or key corresponds to the SSL cipher suites which are enabledIs there any way to solve this?

Alejandro77 wrote:
Good morning.
I have a certificate issued by Thawte.
The problem is that i lost the keystore that i used to create the certificate request.
I import certificate in a new keystore.
So that originates when I attempt start tomcat, i have the following error:
No available certificate or key corresponds to the SSL cipher suites which are enabledIs there any way to solve this?Your Thwarte signed certificate contains only the public key of the key-pair you generated. Since you need both the private and public keys then unless you have the original keystore or you exported from the original keystore the private key then you are stuffed.

Similar Messages

Problema with Keystore entry in SOAP Adapter

Hi all,
I have a RFC to SOAP scenario wich uses a certicate X.509. I import the certificate in Visual Admin in Key Storage node following this steps:
/people/varadharajan.krishnasamy/blog/2007/05/11/how-to-use-digital-certificates-for-signing-encrypting-messages-in-xi
In Integration Directory, in SOAP Adapter receiver, I want to place the certificate in Keystore view but does'nt appear, there are two entries, service_ssl an TicketStore but I dont find my certificate.
Any suggestions???
Regards,
Pablete

Hi.
Look this links below:
PI 7.1 SOAP scenario with SSL certificate
SOAP adapter - digital signature
Digital signed File Upload to XI (PI)
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/40f6fee6-9316-2a10-d2a9-954d4df7dd33
I hope it helps you.
Regards.
Bruno

Problem with creating Kestore in DOS Environment

Hi
I am new to java security ,trying to generate keys by using ketool command but getting problem.
I am executing following keytool command from DOS prompt
c:\>keytool -genkey -keyalg "RSA" -sigalg "SHA1withRSA" -keystore myKeystore -storepass abcdef -alias xyz -keypass wxyzabc
when I execute the above command it displaying keytool Help. I suspect the problem with " -keystore myKeystore " parameter , if I remove that parameter the command gets executing.
Without giving -keystore parameter can create keys , in that case where should I look for the generated keys ,please help me out.
2) how can i create Certification request by using above generated keys.
please try to help me.
with regards.
jl.

c:\>keytool -genkey -keyalg "RSA" -sigalg
"SHA1withRSA" -keystore myKeystore -storepass abcdef
-alias xyz -keypass wxyzabcOn Win2K under 1.4.2, that exact line works just fine for keytool - it goes right to asking me for the identifying information. What's your environment look like?
2) how can i create Certification request by using
above generated keys.c:\> keytool -certreq -keystore myKeystore -storepass abcdef -alias xyz -keypass wxyzabc -file mycertreq.csr
Grant

Problem with Content Server 4 keystore access on Ubuntu 8.04

Hello,
Setting up the Content Server I encounter this problem with the fulfillment server Status check-up:
exception
javax.servlet.ServletException: Servlet execution threw an exception
root cause
java.lang.Error: Problem reading key and certificate from keystore
     com.adobe.adept.fulfillment.security.ServerConfig.init(ServerConfig.java:201)
     com.adobe.adept.fulfillment.security.ServerConfig.getSigningURL(ServerConfig.java:48)
     com.adobe.adept.fulfillment.servlet.FulfillmentServerStatus.getServers(FulfillmentServerStatus.java:34)
     com.adobe.adept.common.servlet.Status.checkUp(Status.java:355)
     com.adobe.adept.common.servlet.Status.doGet(Status.java:421)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
I've created operator.p12 according to the instructions in the Quickstart guide
and placed it in /etc where it is accessible by the server. I used OpenSSL 0.9.8k
for this.
I can use "openssl pkcs12 -in operator.p12 -out file.pem" to view the contents of
the file.
My Content Server fulfillment configuration is as follows:
com.adobe.adept.init1=com.adobe.adept.shared.util.SharedInitialization
com.adobe.adept.log.level=trace
com.adobe.adept.log.file=/var/log/fulfillment.log
com.adobe.adept.persist.sql.driverClass=com.mysql.jdbc.Driver
com.adobe.adept.persist.sql.connection=jdbc:mysql://127.0.0.1:3306/adept
com.adobe.adept.persist.sql.dialect=mysql
com.adobe.adept.persist.sql.user=ereading
com.adobe.adept.persist.sql.password=********
com.adobe.adept.fulfillment.security.licensesignURL=https://eusigningservice.adobe.com/licensesign
com.adobe.adept.fulfillment.security.keystore.user=operator
com.adobe.adept.fulfillment.security.keystore.password=********
com.adobe.adept.fulfillment.security.pkcs12.file=file:///etc/operator.p12
com.adobe.adept.serviceURL=http://******.dmz.******.org/fulfillment
Any ideas?
Best regards,
Teemu

for solve this, change this
com.adobe.adept.fulfillment.security.pkcs12.file=file:///etc/operator.p12
for this
com.adobe.adept.fulfillment.security.pkcs12.file=/etc/operator.p12

Problem with Configuring Tomcat for running jsp web applications..Plz HELP

I am using Tomcat 5.5 and Jdk 1.5.0_12 and Oracle 10g. I am using jdbc-odbc bridge connection
to connect to the database. I have placed my project folder called
tdm under the webapps folder in Tomcat. This 'tdm' folder consists of
a collection of html pages,jsp pages and images of my project. Also I created a
WEB-INF folderand in that I have lib folder which contains catalina-root.jar
, classes12.jar and nls_charset.jar files. And also in the WEB-INF folder I have the web.xml
file which looks like this
<?xml version="1.0" encoding="ISO-8859-1"?>

<web-app>
<resource-ref>
<description>Oracle Datasource example</description>
<res-ref-name>jdbc/gdn</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</web-app>
My Server.xml file in Tomcat\conf folder is as follows



<Server port="8005" shutdown="SHUTDOWN">

<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />

<GlobalNamingResources>

<Environment name="simpleValue" type="java.lang.Integer" value="30"/>

<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
<Resource name="jdbc/gdn" auth="Container"
type="javax.sql.DataSource" driverClassName="sun.jdbc.odbc.JdbcOdbcDriver"
url="jdbc:odbc:gdn"
username="system" password="tiger" maxActive="20" maxIdle="10"
maxWait="-1"/>
</GlobalNamingResources>


<Service name="Catalina">


<Connector
port="5050" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />

     



<Connector port="8009"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />






<Engine name="Catalina" defaultHost="localhost">




<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>







<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">









<Context path="/tdm" docBase="tdm" debug="0" reloadable="true" />
</Host>
</Engine>
</Service>
</Server>
I have set the context path to /tdm in the server.xml file. Should this be placed in context.xml?
My first page in the project is called Homepage.html. To start my project I give http://localhost:5050/tdm/homepage.html
in a browser. Here I accept a username and password from the user and then do the validation in
a valid.jsp file, where I connect to the database and check and use jsp:forward to go to next pages
accordingly. However when I enter the username and password and click Go in the homepage, nothing is
displayed on the next page. The URL in the browser says valid.jsp but a blank screen appears.
WHY DOES IT HAPPEN SO? DOES IT MEAN THAT TOMCAT IS NOT RECOGNIZING JAVA IN MY SYSTEM OR IS IT A PROBLEM
WITH THE DATABASE CONNECTION OR SOMETHING ELSE? I FEEL THAT TOMCAT IS NOT EXECUTING JSP COMMANDS?
IS IT POSSIBLE?WHY WILL THIS HAPPEN?
I set the JAVA_HOME and CATALINA_HOME environment to the jdk and tomcat folders resp.
Is there any other thing that I need to set in classpath? Should I have my project as a
WAR file in the webapps of TOMCAT or just a folder i.e. directory structure will fine?

I am using Tomcat 5.5 and Jdk 1.5.0_12 and Oracle 10g. I am using jdbc-odbc bridge connection
to connect to the database. I have placed my project folder called
tdm under the webapps folder in Tomcat. This 'tdm' folder consists of
a collection of html pages,jsp pages and images of my project. Also I created a
WEB-INF folderand in that I have lib folder which contains catalina-root.jar
, classes12.jar and nls_charset.jar files. And also in the WEB-INF folder I have the web.xml
file which looks like this
<?xml version="1.0" encoding="ISO-8859-1"?>

<web-app>
<resource-ref>
<description>Oracle Datasource example</description>
<res-ref-name>jdbc/gdn</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</web-app>
My Server.xml file in Tomcat\conf folder is as follows



<Server port="8005" shutdown="SHUTDOWN">

<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />

<GlobalNamingResources>

<Environment name="simpleValue" type="java.lang.Integer" value="30"/>

<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
<Resource name="jdbc/gdn" auth="Container"
type="javax.sql.DataSource" driverClassName="sun.jdbc.odbc.JdbcOdbcDriver"
url="jdbc:odbc:gdn"
username="system" password="tiger" maxActive="20" maxIdle="10"
maxWait="-1"/>
</GlobalNamingResources>


<Service name="Catalina">


<Connector
port="5050" maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />

     



<Connector port="8009"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />






<Engine name="Catalina" defaultHost="localhost">




<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>







<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false">









<Context path="/tdm" docBase="tdm" debug="0" reloadable="true" />
</Host>
</Engine>
</Service>
</Server>
I have set the context path to /tdm in the server.xml file. Should this be placed in context.xml?
My first page in the project is called Homepage.html. To start my project I give http://localhost:5050/tdm/homepage.html
in a browser. Here I accept a username and password from the user and then do the validation in
a valid.jsp file, where I connect to the database and check and use jsp:forward to go to next pages
accordingly. However when I enter the username and password and click Go in the homepage, nothing is
displayed on the next page. The URL in the browser says valid.jsp but a blank screen appears.
WHY DOES IT HAPPEN SO? DOES IT MEAN THAT TOMCAT IS NOT RECOGNIZING JAVA IN MY SYSTEM OR IS IT A PROBLEM
WITH THE DATABASE CONNECTION OR SOMETHING ELSE? I FEEL THAT TOMCAT IS NOT EXECUTING JSP COMMANDS?
IS IT POSSIBLE?WHY WILL THIS HAPPEN?
I set the JAVA_HOME and CATALINA_HOME environment to the jdk and tomcat folders resp.
Is there any other thing that I need to set in classpath? Should I have my project as a
WAR file in the webapps of TOMCAT or just a folder i.e. directory structure will fine?

Problem with socket permissions!

Hi All!
I'm developing an applet that displays an image after downlading it from a server; this server is different from the server I download the applet from, so I have problems with security. In fact I get the following exception:
java.security.AccessControlException: access denied (java.net.SocketPermission 172.16.1.22:8080 connect,resolve)
I'm using:
- Java Plugin 1.3;
- Netscape 7.0;
- IE 6;
I've tried to self-sign the applet but with no results (maybe I cannot use selfsigned certificate with java plugin 1.3);
After that I've created a new policy file ("MyPolicy" file)and mentioned it into:
C:\Program Files\JavaSoft\JRE\1.3.1_03\lib\security\java.policy
but it didn't resolve my problem (maybe I'm doing something wrong in creating my policy file??!!).
Which steps do I have to follow in order to make my applet connect to images server without security problems?
Thanks so much in advance,
Carlo

1.     Compile the applet
2.     Create a JAR file
3.     Generate Keys
4.     Sign the JAR file
5.     Export the Public Key Certificate
6.     Import the Certificate as a Trusted Certificate
7.     Create the policy file
8.     Run the applet
Susan
Susan bundles the applet executable in a JAR file, signs the JAR file, and exports the public key certificate.
1.     Compile the Applet
In her working directory, Susan uses the javac command to compile the SignedAppletDemo.java class. The output from the javac command is the SignedAppletDemo.class.
javac SignedAppletDemo.java
2.     Make a JAR File
Susan then makes the compiled SignedAppletDemo.class file into a JAR file. The -cvf option to the jar command creates a new archive (c), using verbose mode (v), and specifies the archive file name (f). The archive file name is SignedApplet.jar.
jar cvf SignedApplet.jar SignedAppletDemo.class
3.     Generate Keys
Susan creates a keystore database named susanstore that has an entry for a newly generated public and private key pair with the public key in a certificate. A JAR file is signed with the private key of the creator of the JAR file and the signature is verified by the recipient of the JAR file with the public key in the pair. The certificate is a statement from the owner of the private key that the public key in the pair has a particular value so the person using the public key can be assured the public key is authentic. Public and private keys must already exist in the keystore database before jarsigner can be used to sign or verify the signature on a JAR file.
In her working directory, Susan creates a keystore database and generates the keys:
keytool -genkey -alias signFiles -keystore susanstore -keypass kpi135 -dname "cn=jones" -storepass ab987c
This keytool -genkey command invocation generates a key pair that is identified by the alias signFiles. Subsequent keytool command invocations use this alias and the key password (-keypass kpi135) to access the private key in the generated pair.
The generated key pair is stored in a keystore database called susanstore (-keystore susanstore) in the current directory, and accessed with the susanstore password (-storepass ab987c).
The -dname "cn=jones" option specifies an X.500 Distinguished Name with a commonName (cn) value. X.500 Distinguished Names identify entities for X.509 certificates.
You can view all keytool options and parameters by typing:
keytool -help
4.     Sign the JAR File
JAR Signer is a command line tool for signing and verifying the signature on JAR files. In her working directory, Susan uses jarsigner to make a signed copy of the SignedApplet.jar file.
jarsigner -keystore susanstore -storepass ab987c -keypass kpi135 -signedjar SSignedApplet.jar SignedApplet.jar signFiles
The -storepass ab987c and -keystore susanstore options specify the keystore database and password where the private key for signing the JAR file is stored. The -keypass kpi135 option is the password to the private key, SSignedApplet.jar is the name of the signed JAR file, and signFiles is the alias to the private key. jarsigner extracts the certificate from the keystore whose entry is signFiles and attaches it to the generated signature of the signed JAR file.
5.     Export the Public Key Certificate
The public key certificate is sent with the JAR file to the whoever is going to use the applet. That person uses the certificate to authenticate the signature on the JAR file. To send a certificate, you have to first export it.
The -storepass ab987c and -keystore susanstore options specify the keystore database and password where the private key for signing the JAR file is stored. The -keypass kpi135 option is the password to the private key, SSignedApplet.jar is the name of the signed JAR file, and signFiles is the alias to the private key. jarsigner extracts the certificate from the keystore whose entry is signFiles and attaches it to the generated signature of the signed JAR file.
5: Export the Public Key Certificate
The public key certificate is sent with the JAR file to the whoever is going to use the applet. That person uses the certificate to authenticate the signature on the JAR file. To send a certificate, you have to first export it.
In her working directory, Susan uses keytool to copy the certificate from susanstore to a file named SusanJones.cer as follows:
keytool -export -keystore susanstore -storepass ab987c -alias signFiles -file SusanJones.cer
Ray
Ray receives the JAR file from Susan, imports the certificate, creates a policy file granting the applet access, and runs the applet.
6.     Import Certificate as a Trusted Certificate
Ray has received SSignedApplet.jar and SusanJones.cer from Susan. He puts them in his home directory. Ray must now create a keystore database (raystore) and import the certificate into it. Ray uses keytool in his home directory /home/ray to import the certificate:
keytool -import -alias susan -file SusanJones.cer -keystore raystore -storepass abcdefgh
7.     Create the Policy File
The policy file grants the SSignedApplet.jar file signed by the alias susan permission to create newfile (and no other file) in the user's home directory.
Ray creates the policy file in his home directory using either policytool or an ASCII editor.
keystore "/home/ray/raystore";
// A sample policy file that lets a JavaTM program
// create newfile in user's home directory
// Satya N Dodda
grant SignedBy "susan"
     permission java.security.AllPermission;
8.     Run the Applet in Applet Viewer
Applet Viewer connects to the HTML documents and resources specified in the call to appletviewer, and displays the applet in its own window. To run the example, Ray copies the signed JAR file and HTML file to /home/aURL/public_html and invokes Applet viewer from his home directory as follows:
Html code :
</body>
</html>
<OBJECT classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
width="600" height="400" align="middle"
codebase="http://java.sun.com/products/plugin/1.3/jinstall-13-win32.cab#Version=1,3,1,2">
<PARAM NAME="code" VALUE="SignedAppletDemo.class">
<PARAM NAME="archive" VALUE="SSignedApplet.jar">
<PARAM NAME="type" VALUE="application/x-java-applet;version=1.3">
</OBJECT>
</body>
</html>
appletviewer -J-Djava.security.policy=Write.jp
http://aURL.com/SignedApplet.html
Note: Type everything on one line and put a space after Write.jp
The -J-Djava.security.policy=Write.jp option tells Applet Viewer to run the applet referenced in the SignedApplet.html file with the Write.jp policy file.
Note: The Policy file can be stored on a server and specified in the appletviewer invocation as a URL.
9.     Run the Applet in Browser
Download JRE 1.3 from Javasoft

Problem with Application server

Hi All,
I'm facing problem with Application Server. When I installed the appserver and started it.. It started with the message " server has been started and some services will run at back". But when I tried stopping it using the stop default server i got the message that there is no server running but when i saw in the task manager i cud see two process running 1) appserver.exe and 2) imqbroker(something).exe so eventually I had to kill it.
Now when I'm trying to start the application server again its giving me this message "CLI156 Could not start the domain domain1" and below is the log file attached if its of any help
[#|2005-08-31T23:37:57.000+1000|WARNING|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-08-31T23:37:57.015+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/endorsed
-Djava.security.policy=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0/jre/lib/ext;C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0\jre\bin\client;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\Java\jdk1.5.0\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Sun\AppServer\bin;;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\jre\jdk1.5.0\bin;.;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0/lib/tools.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/appserv-rt.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\admin-cli.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-admin.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\dom.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote_optional.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\rmissl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xalan.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xercesImpl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-upgrade.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-ext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\activation.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-cmp.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-jstl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-launcher.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-logging.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee-svc.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jax-qname.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\mail.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\relaxngDatatype.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xsdlib.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/install/applications/jmsra/imqjmsra.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/jaxm-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/fscontext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/ant/lib/ant.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbclient.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-08-31T23:38:03.515+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Program Files\netbeans-4.1\SunAppServer8.1\imq\bin].|#]
[#|2005-08-31T23:38:03.515+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
[#|2005-08-31T23:38:15.796+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-08-31T23:38:16.484+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-09-01T00:48:45.484+1000|WARNING|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-09-01T00:48:45.531+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/endorsed
-Djava.security.policy=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0/jre/lib/ext;C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0\jre\bin\client;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\Java\jdk1.5.0\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Sun\AppServer\bin;;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\jre\jdk1.5.0\bin;.;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0/lib/tools.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/appserv-rt.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\admin-cli.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-admin.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\dom.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote_optional.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\rmissl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xalan.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xercesImpl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-upgrade.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-ext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\activation.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-cmp.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-jstl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-launcher.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-logging.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee-svc.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jax-qname.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\mail.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\relaxngDatatype.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xsdlib.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/install/applications/jmsra/imqjmsra.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/jaxm-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/fscontext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/ant/lib/ant.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbclient.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-09-04T04:12:39.281+1000|WARNING|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-09-04T04:12:39.343+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.tools.launcher|_ThreadID=10;|
C:/Program Files/Java/jdk1.5.0\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/logs/server.log
-Djava.endorsed.dirs=C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/endorsed
-Djava.security.policy=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/server.policy
-Djava.security.auth.login.config=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0/jre/lib/ext;C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=domain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=domain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=C:/Program Files/netbeans-4.1/SunAppServer8.1/config
-Djava.library.path=C:\Program Files\Java\jdk1.5.0\jre\bin\client;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\Java\jdk1.5.0\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\lib;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\Program Files\netbeans-4.1\SunAppServer8.1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Sun\AppServer\bin;;C:\Program Files\Java\jdk1.5.0\bin;.;C:\Program Files\jre\jdk1.5.0\bin;.;
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
C:/Program Files/Java/jdk1.5.0/lib/tools.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/appserv-rt.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\admin-cli.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-admin.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\dom.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jmxremote_optional.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jsf-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\rmissl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xalan.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xercesImpl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-upgrade.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-ext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\activation.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-cmp.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\appserv-jstl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-launcher.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\commons-logging.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\j2ee-svc.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jax-qname.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxr-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\jaxrpc-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\mail.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\relaxngDatatype.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\saaj-impl.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib\xsdlib.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/install/applications/jmsra/imqjmsra.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/jaxm-api.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/imq/lib/fscontext.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/lib/ant/lib/ant.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbclient.jar;C:/Program Files/netbeans-4.1/SunAppServer8.1/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start
display
native|#]
[#|2005-09-04T04:13:50.453+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
[#|2005-09-04T04:13:50.453+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory C:\Program Files\netbeans-4.1\SunAppServer8.1\imq\var\instances|#]
[#|2005-09-04T04:13:50.453+1000|INFO|sun-appserver-pe8.1_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
[#|2005-09-04T04:13:50.453+1000|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false
com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: no further information
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:427)
     at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:54)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: no further information
     at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
     at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:176)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:101)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:54)
     at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:61)
     at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:281)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
     at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:613)
     at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1194)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1894)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:712)
     at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:293)
     at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
     at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
     at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
     at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:783)
     at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:335)
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:396)
     ... 3 more
Caused by: java.net.ConnectException: Connection refused: no further information
     at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
     at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:525)
     at com.sun.enterprise.server.ss.ASClientSocketImpl.connect(ASClientSocketImpl.java:175)
     at java.net.Socket.connect(Socket.java:507)
     at java.net.Socket.connect(Socket.java:457)
     at java.net.Socket.<init>(Socket.java:365)
     at java.net.Socket.<init>(Socket.java:178)
     at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:156)
     ... 21 more
|#]
[#|2005-09-04T04:13:50.484+1000|SEVERE|sun-appserver-pe8.1_01|javax.enterprise.system.core|_ThreadID=10;|Exception while stoppping Lifecycle.
com.sun.appserv.server.ServerLifecycleException: MQ startup failed :[C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: no further information
     at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:376)
     at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:445)
     at com.sun.enterprise.server.ss.ASLazyKernel.stopLifecycle(ASLazyKernel.java:175)
     at com.sun.enterprise.server.ss.ASLazyKernel.stopMQ(ASLazyKernel.java:169)
     at com.sun.enterprise.server.ss.ASLazyKernel.exitServer(ASLazyKernel.java:74)
     at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:67)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
|#]
Thanks in advance
Ajay

The VERY FIRST message in the server log gives you a hint as to what the problem might be. The server thinks you have spaces in your PATH to the application server. Therefore, the solution is to kill the server however you need to (task manager, whatever) and then reinstall it in a path that doesn't contain spaces. That's the low-hanging fruit here; if that doesn't work, well, then we will have to find some other solution.

Urgent : Problem with Client when OC4J has been setup in 2 way SSL mode

This is the output that is generated in the JDeveloper console on running the example from b14429.pdf. Examle :
====================================================
import HTTPClient.HTTPConnection;
import HTTPClient.HTTPResponse;
import javax.security.cert.X509Certificate;
import oracle.security.ssl.OracleSSLCredential;
import java.io.IOException;
import javax.net.ssl.SSLPeerUnverifiedException;
public class SSLSocketClientWithClientAuth {
public static void main(String[] args) {
if (args.length < 4) {
System.out.println("Usage: java HTTPSConnectionTest [host] [port] " +
"[wallet] [password]");
System.exit(-1);
String hostname = args[0].toLowerCase();
int port = Integer.decode(args[1]).intValue();
String walletPath = args[2];
String password = args[3];
HTTPConnection httpsConnection = null;
OracleSSLCredential credential = null;
try {
httpsConnection = new HTTPConnection("https", hostname, port);
} catch (IOException e) {
System.out.println("HTTPS Protocol not supported");
System.exit(-1);
try {
credential = new OracleSSLCredential();
credential.setWallet(walletPath, password);
} catch (IOException e) {
System.out.println("Could not open wallet");
System.exit(-1);
httpsConnection.setSSLEnabledCipherSuites(new String[]{"SSL_RSA_WITH_3DES_EDE_CBC_SHA"});
httpsConnection.setSSLCredential(credential);
try {
httpsConnection.connect();
} catch (IOException e) {
System.out.println("Could not establish connection");
e.printStackTrace();
System.exit(-1);
// X509Certificate x509 = new X509Certificate();
//javax.servlet.request.
X509Certificate[] peerCerts = null;
try {
peerCerts =
(httpsConnection.getSSLSession()).getPeerCertificateChain();
} catch (javax.net.ssl.SSLPeerUnverifiedException e) {
System.err.println("Unable to obtain peer credentials");
e.printStackTrace();
System.exit(-1);
String peerCertDN =
peerCerts[peerCerts.length - 1].getSubjectDN().getName();
peerCertDN = peerCertDN.toLowerCase();
if (peerCertDN.lastIndexOf("cn=" + hostname) == -1) {
System.out.println("Certificate for " + hostname +
" is issued to " + peerCertDN);
System.out.println("Aborting connection");
System.exit(-1);
try {
HTTPResponse rsp = httpsConnection.Get("/");
System.out.println("Server Response: ");
System.out.println(rsp);
} catch (Exception e) {
System.out.println("Exception occured during Get");
e.printStackTrace();
System.exit(-1);
================================================================
C:\j2sdk1.4.2_09\bin\javaw.exe -client -classpath "D:\eclipse\workspace\OC4JClient\OC4JClient\classes;D:\eclipse\workspace\jdev\extensions\.jar;C:\Documents and Settings\nilesh_bafna\Desktop\Nitin\lib\jssl-1_1.jar;E:\product\10.1.3.1\OracleAS_1\j2ee\home\lib\http_client.jar;E:\product\10.1.3.1\OracleAS_1\jlib\javax-ssl-1_1.jar" -Djava.protocol.handler.pkgs=HTTPClient -Djavax.net.debug=ssl -Djavax.net.ssl.keyStore=F:/oc4jcert/client.keystore -Djavax.net.ssl.keyStorePassword=welcome1 -Djavax.net.ssl.trustStore=F:/oc4jcert/client.keystore -Djavax.net.ssl.trustStorePassword=welcome1 -DOracle.ssl.defaultCipherSuites=SSL_RSA_WITH_RC4_128_MD5 SSLSocketClientWithClientAuth ps4372.persistent.co.in 443 F:/oc4jcert/client.keystore welcome1
keyStore is : F:/oc4jcert/client.keystore
keyStore type is : jks
init keystore
init keymanager of type SunX509
found key for : oracle-client
chain [0] = [
Version: V3
Subject: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: SunJSSE RSA public key:
public exponent:
010001
modulus:
87fcc8e9 0ffcef8e 61f3be10 be7c9715 2792849b 3bbdeb1c cc76b337 4b82bbab
86972c63 9af3adfd 35b5df99 9078a0d1 6dc760d8 0549a95a bfa7648a 9eadd326
a6bc4b61 d8f8b42f 44e0b178 ff1dee20 db8406cd d800c26a 9c5a6ed9 4d6f2aef
bc919814 3b46be39 e129280c e83afe12 c9d4e3d7 fb5787b1 d98bed4a 4f0833d5
Validity: [From: Thu Jan 18 21:18:14 GMT+05:30 2007,
               To: Wed Apr 18 21:18:14 GMT+05:30 2007]
Issuer: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
SerialNumber: [    45af96be]
Algorithm: [MD5withRSA]
Signature:
0000: 41 47 35 41 90 10 E3 77 A7 F3 F5 81 37 49 4F 57 AG5A...w....7IOW
0010: 01 11 82 A2 FB 69 46 E8 18 6C EE 11 23 A6 67 2E .....iF..l..#.g.
0020: 68 4D D6 A6 E7 09 45 24 58 18 9A E5 44 49 10 9B hM....E$X...DI..
0030: F1 EC 99 4A 45 5F A4 4F 71 3F 05 3D 45 29 42 CD ...JE_.Oq?.=E)B.
0040: 11 87 DA 0C AA DC 55 4E CF 22 4A 94 85 CB E5 EB ......UN."J.....
0050: BA E1 10 D2 C8 80 2C 6B 65 94 13 01 1F 6E 18 C3 ......,ke....n..
0060: 87 33 8C 65 C7 03 16 03 24 FB 0D B0 6D D8 E7 AA .3.e....$...m...
0070: A1 A5 48 90 0D D6 8C 47 50 2A AA 7C 7B 14 E5 B7 ..H....GP*......
trustStore is: F:\oc4jcert\client.keystore
trustStore type is : jks
init truststore
adding as trusted cert:
Subject: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
Issuer: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
Algorithm: RSA; Serial number: 0x45af96be
Valid from Thu Jan 18 21:18:14 GMT+05:30 2007 until Wed Apr 18 21:18:14 GMT+05:30 2007
adding as trusted cert:
Subject: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
Issuer: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
Algorithm: RSA; Serial number: 0x45af95dc
Valid from Thu Jan 18 21:14:28 GMT+05:30 2007 until Wed Apr 18 21:14:28 GMT+05:30 2007
init context
trigger seeding of SecureRandom
done seeding SecureRandom
%% No cached client session
*** ClientHello, TLSv1
RandomCookie: GMT: 1152299454 bytes = { 41, 212, 166, 48, 109, 77, 185, 232, 204, 95, 158, 141, 60, 96, 196, 172, 49, 19, 49, 22, 222, 234, 47, 76, 27, 130, 5, 176 }
Session ID: {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
Compression Methods: { 0 }
main, WRITE: TLSv1 Handshake, length = 73
main, WRITE: SSLv2 client hello message, length = 98
main, READ: TLSv1 Handshake, length = 839
*** ServerHello, TLSv1
RandomCookie: GMT: 1152299454 bytes = { 206, 186, 162, 116, 179, 72, 44, 198, 189, 25, 70, 227, 170, 235, 83, 186, 152, 49, 194, 222, 248, 3, 191, 170, 248, 95, 134, 35 }
Session ID: {69, 175, 178, 190, 47, 141, 131, 115, 241, 226, 39, 29, 241, 65, 235, 165, 57, 40, 52, 85, 68, 85, 68, 84, 108, 141, 1, 125, 193, 191, 158, 208}
Cipher Suite: SSL_RSA_WITH_RC4_128_MD5
Compression Method: 0
%% Created: [Session-1, SSL_RSA_WITH_RC4_128_MD5]
** SSL_RSA_WITH_RC4_128_MD5
*** Certificate chain
chain [0] = [
Version: V3
Subject: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: SunJSSE RSA public key:
public exponent:
010001
modulus:
6f24d75b 96919725 ad6ea93a cab0bd96 a49d2f3c e14f5c09 0e228e36 de64e0f2
f2b82740 1653bdb4 5024d281 21ed8c4c 89bc322b 4dc9ffb2 0e97cd95 16e6fe1e
380340c9 f3c67e2c 18d06461 f4f30eaf 4394716e 7bc66d80 810a9cb5 9c168b36
cdd99919 67074ebc edebf02e ebf0accb 2193bc38 7ae1cdda af5ff300 ed0e7763
Validity: [From: Thu Jan 18 21:14:28 GMT+05:30 2007,
               To: Wed Apr 18 21:14:28 GMT+05:30 2007]
Issuer: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
SerialNumber: [    45af95dc]
Algorithm: [MD5withRSA]
Signature:
0000: 05 4E EE 12 5B DD 7F 26 92 37 67 C9 D0 73 46 4D .N..[..&.7g..sFM
0010: 7E A5 1E 67 38 06 D9 5F 9F B7 2F E8 F6 9E BF 88 ...g8.._../.....
0020: 01 31 7D EA 42 5E 4F 9E D7 8F DA 9F 94 A5 EF 47 .1..B^O........G
0030: E3 E9 BA DE 94 15 C6 03 DE C9 C0 7D CE 58 C0 27 .............X.'
0040: 0F 1A 66 EC 73 53 5D 1D DE 7E FA 35 15 E0 2A CC ..f.sS]....5..*.
0050: C9 74 CC 58 E9 B6 2F 68 A0 89 2B F3 E6 61 7D E1 .t.X../h..+..a..
0060: 21 AF BE E8 83 49 B1 BD 36 C5 2D 1B 0D A1 0E 63 !....I..6.-....c
0070: 02 4A 82 71 B0 E1 9C AD 55 67 F9 17 A5 96 18 EB .J.q....Ug......
Found trusted certificate:
Version: V3
Subject: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: SunJSSE RSA public key:
public exponent:
010001
modulus:
6f24d75b 96919725 ad6ea93a cab0bd96 a49d2f3c e14f5c09 0e228e36 de64e0f2
f2b82740 1653bdb4 5024d281 21ed8c4c 89bc322b 4dc9ffb2 0e97cd95 16e6fe1e
380340c9 f3c67e2c 18d06461 f4f30eaf 4394716e 7bc66d80 810a9cb5 9c168b36
cdd99919 67074ebc edebf02e ebf0accb 2193bc38 7ae1cdda af5ff300 ed0e7763
Validity: [From: Thu Jan 18 21:14:28 GMT+05:30 2007,
               To: Wed Apr 18 21:14:28 GMT+05:30 2007]
Issuer: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
SerialNumber: [    45af95dc]
Algorithm: [MD5withRSA]
Signature:
0000: 05 4E EE 12 5B DD 7F 26 92 37 67 C9 D0 73 46 4D .N..[..&.7g..sFM
0010: 7E A5 1E 67 38 06 D9 5F 9F B7 2F E8 F6 9E BF 88 ...g8.._../.....
0020: 01 31 7D EA 42 5E 4F 9E D7 8F DA 9F 94 A5 EF 47 .1..B^O........G
0030: E3 E9 BA DE 94 15 C6 03 DE C9 C0 7D CE 58 C0 27 .............X.'
0040: 0F 1A 66 EC 73 53 5D 1D DE 7E FA 35 15 E0 2A CC ..f.sS]....5..*.
0050: C9 74 CC 58 E9 B6 2F 68 A0 89 2B F3 E6 61 7D E1 .t.X../h..+..a..
0060: 21 AF BE E8 83 49 B1 BD 36 C5 2D 1B 0D A1 0E 63 !....I..6.-....c
0070: 02 4A 82 71 B0 E1 9C AD 55 67 F9 17 A5 96 18 EB .J.q....Ug......
*** CertificateRequest
Cert Types: RSA, DSS,
Cert Authorities:
<CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US>
*** ServerHelloDone
matching alias: oracle-client
*** Certificate chain
chain [0] = [
Version: V3
Subject: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: SunJSSE RSA public key:
public exponent:
010001
modulus:
87fcc8e9 0ffcef8e 61f3be10 be7c9715 2792849b 3bbdeb1c cc76b337 4b82bbab
86972c63 9af3adfd 35b5df99 9078a0d1 6dc760d8 0549a95a bfa7648a 9eadd326
a6bc4b61 d8f8b42f 44e0b178 ff1dee20 db8406cd d800c26a 9c5a6ed9 4d6f2aef
bc919814 3b46be39 e129280c e83afe12 c9d4e3d7 fb5787b1 d98bed4a 4f0833d5
Validity: [From: Thu Jan 18 21:18:14 GMT+05:30 2007,
               To: Wed Apr 18 21:18:14 GMT+05:30 2007]
Issuer: CN=ps4372.persistent.co.in, OU=Marketing, O=Oracle, L=Atlanta, ST=Georgia, C=US
SerialNumber: [    45af96be]
Algorithm: [MD5withRSA]
Signature:
0000: 41 47 35 41 90 10 E3 77 A7 F3 F5 81 37 49 4F 57 AG5A...w....7IOW
0010: 01 11 82 A2 FB 69 46 E8 18 6C EE 11 23 A6 67 2E .....iF..l..#.g.
0020: 68 4D D6 A6 E7 09 45 24 58 18 9A E5 44 49 10 9B hM....E$X...DI..
0030: F1 EC 99 4A 45 5F A4 4F 71 3F 05 3D 45 29 42 CD ...JE_.Oq?.=E)B.
0040: 11 87 DA 0C AA DC 55 4E CF 22 4A 94 85 CB E5 EB ......UN."J.....
0050: BA E1 10 D2 C8 80 2C 6B 65 94 13 01 1F 6E 18 C3 ......,ke....n..
0060: 87 33 8C 65 C7 03 16 03 24 FB 0D B0 6D D8 E7 AA .3.e....$...m...
0070: A1 A5 48 90 0D D6 8C 47 50 2A AA 7C 7B 14 E5 B7 ..H....GP*......
JsseJCE: Using JSSE internal implementation for cipher RSA/ECB/PKCS1Padding
*** ClientKeyExchange, RSA PreMasterSecret, TLSv1
Random Secret: { 3, 1, 236, 206, 185, 158, 75, 201, 230, 16, 170, 40, 193, 70, 188, 134, 36, 134, 14, 20, 191, 121, 246, 8, 7, 2, 137, 66, 166, 10, 185, 246, 104, 154, 27, 82, 161, 133, 11, 130, 11, 130, 71, 84, 155, 165, 239, 227 }
main, WRITE: TLSv1 Handshake, length = 763
SESSION KEYGEN:
PreMaster Secret:
0000: 03 01 EC CE B9 9E 4B C9 E6 10 AA 28 C1 46 BC 86 ......K....(.F..
0010: 24 86 0E 14 BF 79 F6 08 07 02 89 42 A6 0A B9 F6 $....y.....B....
0020: 68 9A 1B 52 A1 85 0B 82 0B 82 47 54 9B A5 EF E3 h..R......GT....
CONNECTION KEYGEN:
Client Nonce:
0000: 45 AF B2 BE 29 D4 A6 30 6D 4D B9 E8 CC 5F 9E 8D E...)..0mM..._..
0010: 3C 60 C4 AC 31 13 31 16 DE EA 2F 4C 1B 82 05 B0 <`..1.1.../L....
Server Nonce:
0000: 45 AF B2 BE CE BA A2 74 B3 48 2C C6 BD 19 46 E3 E......t.H,...F.
0010: AA EB 53 BA 98 31 C2 DE F8 03 BF AA F8 5F 86 23 ..S..1......._.#
Master Secret:
0000: CA 5C BA B3 D0 C9 26 A9 3A 06 08 8F 27 2E CE 17 .\....&.:...'...
0010: 93 98 BC DF EF 78 2A 99 DB 3E 50 3B 01 D1 84 5F .....x*..>P;..._
0020: 28 80 CE 7C 7C C1 12 A4 11 F6 33 9B 2E D9 6F BE (.........3...o.
Client MAC write Secret:
0000: 80 FF CE 99 7C 45 4C D8 60 FA 40 79 A2 A4 36 7C .....EL.`[email protected].
Server MAC write Secret:
0000: 2D F1 A0 A8 ED A1 7B DD 89 A5 01 90 43 BF F1 19 -...........C...
Client write key:
0000: E1 3F 33 54 D3 C5 3A 26 4A 41 65 DA AC 44 3B 28 .?3T..:&JAe..D;(
Server write key:
0000: C5 08 52 AE A9 0A 4F D0 AD 54 49 C6 4E 2F 9C 4E ..R...O..TI.N/.N
... no IV for cipher
JsseJCE: Using JSSE internal implementation for cipher RSA/ECB/PKCS1Padding
*** CertificateVerify
main, WRITE: TLSv1 Handshake, length = 134
main, WRITE: TLSv1 Change Cipher Spec, length = 1
main, handling exception: java.net.SocketException: Software caused connection abort: socket write error
main, SEND TLSv1 ALERT: fatal, description = unexpected_message
main, WRITE: TLSv1 Alert, length = 2
Exception sending alert: java.net.SocketException: Software caused connection abort: socket write error
main, called closeSocket()
IOException in getSession(): java.net.SocketException: Software caused connection abort: socket write error
Unable to obtain peer credentials
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
     at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificateChain(DashoA12275)
     at SSLSocketClientWithClientAuth.main(SSLSocketClientWithClientAuth.java:56)
Process exited with exit code -1.
=====================================================
I think this is the problem with ciphers. So can anybody please help me with this!!!. This is very urgent!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Thanks in advance
Nilesh

Thanks for your prompt reply I was able to make it run. Actually I am using the same keystore and truststore at both the client and the server end. I added those properties in opmn.xml as startup parameters.
I have another query I am using JDev to create a client proxy for my webservice that is deployed in OC4J. I have setup OC4J in 2 way SSL (mutual authentication)
When I invoke my client proxy with these system properties set
System.setProperty("javax.net.ssl.keyStore",keyStore);
System.setProperty("javax.net.ssl.keyStorePassword", keyStorePassword);
System.setProperty("javax.net.ssl.trustStore", trustStore);
System.setProperty("javax.net.ssl.trustStorePassword",trustStorePassword);
System.setProperty("javax.net.ssl.keyStoreType","JKS");
System.setProperty("javax.net.ssl.trustStoreType","JKS");
I get an exception in the log.xml which is
<MSG_TEXT>IOException in ServerSocketAcceptHandler$AcceptHandlerHorse:run</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[javax.net.ssl.SSLProtocolException: handshake alert: no_certificate
            at com.sun.net.ssl.internal.ssl.ServerHandshaker.handshakeAlert(ServerHandshaker.java:1031)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1535)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:863)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1025)
            at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1038)
            at oracle.oc4j.network.ServerSocketAcceptHandler.doSSLHandShaking(ServerSocketAcceptHandler.java:250)
            at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:868)
            at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
            at java.lang.Thread.run(Thread.java:595)
]]></SUPPL_DETAIL>
Isn't setting these properties enough for sending a client certificate. Please help!!!!
Thanks,
Nilesh.

Problem with XI J2EE Stack

We are getting the following error when the XI stack starts up. It seems to point to a problem in the Exchange Profile. However, I am not sure whether it is complaining because of incorrect parameters or because it is unable to access it. This instance of XI has been running just fine for the last few months and we have had no problems with it. All the J2EE services are shut down as the exception shows. Any insight into what the problem might be is well appreciated.
FYI, We haven't added any patches for the last couple of months. It was working fine during that time.
Included is the output from the log.
stdout/stderr redirect
node name   : server0
pid         : 4500
system name : XID
system nr. : 00
started at : Thu Jan 20 14:57:26 2005
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude iaik/security/md/SHA a
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
SAP J2EE Engine Version 6.40   PatchLevel 87037.313 is starting...
Loading: LogManager ... 4687 ms.
Loading: PoolManager ... 16 ms.
Loading: ApplicationThreadManager ... 142 ms.
Loading: ThreadManager ... 158 ms.
Loading: IpVerificationManager ... 126 ms.
Loading: ClassLoaderManager ... 78 ms.
Loading: ClusterManager ... 1558 ms.
Loading: LockingManager ... 724 ms.
Loading: ConfigurationManager ... 5647 ms.
Loading: LicensingManager ... 47 ms.
Loading: ServiceManager ...
Loading services.:
Service cross started. (47 ms).
Service memory started. (47 ms).
Service file started. (173 ms).
Service timeout started. (126 ms).
Service userstore started. (31 ms).
Service runtimeinfo started. (31 ms).
Service tcsecvsi~service started. (362 ms).
Service p4 started. (1541 ms).
Service trex.service started. (692 ms).
Service jmx_notification started. (865 ms).
Service classpath_resolver started. (126 ms).
Service tcsecwssec~service started. (661 ms).
Service deploy started. (10662 ms).
Service log_configurator started. (11997 ms).
Service locking started. (16 ms).
Service apptracing started. (424 ms).
Service http started. (533 ms).
Service naming started. (816 ms).
Service ts started. (203 ms).
Service javamail started. (298 ms).
Service failover started. (220 ms).
Service licensing started. (47 ms).
Service appclient started. (282 ms).
Service jmsconnector started. (455 ms).
Service connector started. (204 ms).
Service configuration started. (16 ms).
Service webservices started. (2887 ms).
Service dbpool started. (9428 ms).
Service com.sap.aii.af.svc started. (942 ms).
Service com.sap.security.core.ume.service started. (4048 ms).
Service security started. (5083 ms).
Service applocking started. (486 ms).
Service shell started. (675 ms).
Service tceCATTPingservice started. (189 ms).
Service classload started. (549 ms).
Service telnet started. (220 ms).
Service keystore started. (1789 ms).
Service ssl started. (156 ms).
Service ejb started. (2322 ms).
Service servlet_jsp started. (2400 ms).
Service tcsecsecurestorage~service started. (753 ms).
Service dsr started. (2150 ms).
Service jmx started. (2730 ms).
Service webdynpro started. (2526 ms).
Service tcsecdestinations~service started. (753 ms).
Service pmi started. (392 ms).
Service basicadmin started. (894 ms).
Service adminadapter started. (659 ms).
Service sld started. (2824 ms).
Service rfcengine started. (5098 ms).
Service monitor started. (4032 ms).
Service tc.monitoring.logviewer started. (7608 ms).
Service com.sap.aii.af.ms.svc started. (7640 ms).
Service jms_provider started. (11437 ms).
Service com.sap.aii.af.cpa.svc started. (11718 ms).
Service com.sap.aii.adapter.marketplace.svc started. (188 ms).
Service com.sap.aii.adapter.xi.svc started. (282 ms).
Service com.sap.aii.af.security.service started. (204 ms).
Service com.sap.aii.adapter.bc.svc started. (361 ms).
Service com.sap.aii.adapter.mail.svc started. (94 ms).
Service com.sap.aii.adapter.jms.svc started. (644 ms).
Service com.sap.aii.adapter.jdbc.svc started. (612 ms).
Service com.sap.aii.adapter.file.svc started. (659 ms).
Service com.sap.aii.af.ispeak.svc started. (706 ms).
Service com.sap.aii.adapter.rfc.svc started. (1882 ms).
ServiceManager started for 69917 ms.
Framework started for 84184 ms.
SAP J2EE Engine Version 6.40   PatchLevel 87037.313 is running!
PatchLevel 87037.313 October 19, 2004 19:52 GMT
>### Excluding compile: iaik.security.md.SHA::a
Jan 22, 2005 3:03:51 AM         com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Jan 25, 2005 10:17:28... ...utilxi.prop.api.PropertySourceFactory [SAPEngine_Application_Thread[impl:3]_0] Fatal: XI properties could not be initialized. Check ExchangeProfile (or aii.properties).
Thrown:
java.lang.Throwable: dummy Throwable for stack trace
     at com.sap.aii.utilxi.prop.api.PropertySourceFactory.getPropertySource(PropertySourceFactory.java:55)
     at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:528)
     at com.sap.aii.utilxi.misc.api.AIIProperties.<init>(AIIProperties.java:301)
     at com.sap.aii.utilxi.misc.api.AIIProperties.getInstance(AIIProperties.java:328)
     at com.sap.aii.ib.server.util.perf.TimerFactory.<clinit>(TimerFactory.java:86)
     at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:73)
     at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
     at $Proxy30.processFunction(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95)
     at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
     at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Jan 29, 2005 7:37:28 AM         com.sap.engine.core.configuration [SAPEngine_Application_Thread[impl:3]_23] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Jan 31, 2005 4:11:19 PM ...l.cache.WebResourceCache.startService [Thread[Thread-1140,5,SAPEngine_Application_Thread[impl:3]_Group]] Fatal: Tried to save: ~wd_key0_1107205757104
Feb 5, 2005 3:07:25 AM          com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Feb 5, 2005 3:02:56 PM          com.sap.engine.core.configuration [SAPEngine_System_Thread[impl:5]_78] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Feb 6, 2005 3:03:13 PM          com.sap.engine.core.configuration [SAPEngine_System_Thread[impl:5]_77] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Feb 19, 2005 3:15:45 AM         com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
SAP J2EE Engine Version 6.40   PatchLevel 87037.313 is shutting down! PatchLevel 87037.313 October 19, 2004 19:52 GMT
Stopping services.
Service com.sap.aii.adapter.rfc.svc stopped. (439 ms)
Service com.sap.aii.af.ispeak.svc stopped. (78 ms)
Service com.sap.aii.adapter.marketplace.svc stopped. (15 ms)
Service com.sap.aii.adapter.jdbc.svc stopped. (79 ms)

Hi Sunit,
Did you figure out what happened? We're seeing the same issue.
Thanks,
Jay

Problem with https internet url for Portal

Hello ,
We are running EP 7 SP 13.
We had a problem with the j2ee engine going down due to a db problem .It is ok now and and j2ee is up and running fine and the portal is accessible from the intranet.
But there is a problem with the https url that we use for internet access. It gives "page cannot be displayed error".
There is a IISproxy in place for internet access.Https certificate has not expired. Couldnt find much in the portal logs and trace or am I looking in the wrong place?
Any help would be most appreciated.
Rgds

Hi Vineeth
Check the IIS settings, , they might not have started properly.
EP5: Enabling SSL and renewing the J2EE certificate
SAP Note Number: 685306
Can you check the contents of Keystore in Visual admin,
Regards
Kaleem
Edited by: Kaleem on Aug 19, 2008 2:11 PM

Problems with OracleAS adapter for Siebel

Hi,
I have a problem starting the Java data bean connection from the OracleAS Adapter Application Explorer. When I try to connect to my Siebel Instance I get the following error from the application explorer
Problem Activating adapter. (null). See logs for details.
When I look in my logs $ORACLE_HOME/adapters/application/config/siebelconnection/logs I get the following information
Wed, 11 Oct 2006 16:51:28.0188 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA]
Found adapter 'IWAF'
Wed, 11 Oct 2006 16:51:28.0204 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA]
Found adapter 'Siebel'
Wed, 11 Oct 2006 16:51:28.0219 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA]
[storage] Repository URL 'file:///space/oracle/product/10.1.2.0.2/eaidev1/adapte
rs/application/config/SiebelConnection/repository.xml' resolved to repositoty ty
pe: file
Wed, 11 Oct 2006 16:51:28.0220 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA]
[storage] Getting Repository reference: 'file:///space/oracle/product/10.1.2.0.2
/eaidev1/adapters/application/config/SiebelConnection/repository.xml&user=null&p
assword=***'...
Wed, 11 Oct 2006 16:51:28.0394 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA]
[storage] Created Repository System storage.
Wed, 11 Oct 2006 16:51:28.0398 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA]
[state] State Repository URL 'file:///space/oracle/product/10.1.2.0.2/eaidev1/ad
apters/application/config/SiebelConnection/st_repository.xml' repositoty type: f
ile
Wed, 11 Oct 2006 16:51:28.0399 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA]
[state] Getting Repository reference: 'file:///space/oracle/product/10.1.2.0.2/e
aidev1/adapters/application/config/SiebelConnection/st_repository.xml&user=null&
password=***'...
"aejca_1160581888102.log" 100 lines, 13137 characters
Wed, 11 Oct 2006 16:51:28.0188 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] Found adapter 'IWAF'
Wed, 11 Oct 2006 16:51:28.0204 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] Found adapter 'Siebel'
Wed, 11 Oct 2006 16:51:28.0219 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [storage] Repository URL 'file:///space/oracl
e/product/10.1.2.0.2/eaidev1/adapters/application/config/SiebelConnection/repository.xml' resolved to repositoty type: file
Wed, 11 Oct 2006 16:51:28.0220 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [storage] Getting Repository reference: 'file
:///space/oracle/product/10.1.2.0.2/eaidev1/adapters/application/config/SiebelConnection/repository.xml&user=null&password=**
Wed, 11 Oct 2006 16:51:28.0394 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [storage] Created Repository System storage.
Wed, 11 Oct 2006 16:51:28.0398 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [state] State Repository URL 'file:///space/o
racle/product/10.1.2.0.2/eaidev1/adapters/application/config/SiebelConnection/st_repository.xml' repositoty type: file
Wed, 11 Oct 2006 16:51:28.0399 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [state] Getting Repository reference: 'file:/
//space/oracle/product/10.1.2.0.2/eaidev1/adapters/application/config/SiebelConnection/st_repository.xml&user=null&password=*
Wed, 11 Oct 2006 16:51:28.0415 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [state] Created State Repository System stora
ge.
Wed, 11 Oct 2006 16:51:28.0449 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] Creating IWAF Container classload
er using libdir '/space/oracle/product/10.1.2.0.2/eaidev1/adapters/application/lib'.
Wed, 11 Oct 2006 16:51:28.0751 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] *********************************
Wed, 11 Oct 2006 16:51:28.0752 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] Building adapters list...
Wed, 11 Oct 2006 16:51:28.0753 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] *********************************
Wed, 11 Oct 2006 16:51:28.0754 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] *********************************
Wed, 11 Oct 2006 16:51:28.0754 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] Adapter: Siebel
Wed, 11 Oct 2006 16:51:28.0755 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] *********************************
Wed, 11 Oct 2006 16:51:28.0755 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] Inspecting adapter 'Siebel' modul
es.
Wed, 11 Oct 2006 16:51:28.0770 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] Skiping IWAF Container adapter.
Wed, 11 Oct 2006 16:51:28.0807 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] *********************************
Wed, 11 Oct 2006 16:51:28.0808 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] Building default security manager
Wed, 11 Oct 2006 16:51:28.0809 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] *********************************
Wed, 11 Oct 2006 16:51:28.0811 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] iway.home is set to '/space/oracl
e/product/10.1.2.0.2/eaidev1/adapters/application'.
Wed, 11 Oct 2006 16:51:28.0812 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] iway.config is set to 'SiebelConn
ection'.
Wed, 11 Oct 2006 16:51:28.0813 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] Using default: keystore.type=jks
and keystore.password=iwaysoftware
Wed, 11 Oct 2006 16:51:28.0814 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] Security manager using keystore :
/space/oracle/product/10.1.2.0.2/eaidev1/adapters/application/config/SiebelConnection/security/keystore.jks
Wed, 11 Oct 2006 16:51:29.0416 BST - Thread[Thread-5,6,main] [warn ] [IWAF JCA] [container] Security manager will not be avai
lable due to problem.
java.lang.IllegalStateException: Problem loading keystore: java.io.EOFException; make sure the password is correct
at com.iwaysoftware.security.KeyStoreUtil.getKeyStore(KeyStoreUtil.java:39)
at com.ibi.adapters.util.security.SecurityManagerImpl.<init>(SecurityManagerImpl.java:45)
at com.iwaysoftware.af.container.IWAFFactory.buildSecurityManager(IWAFFactory.java:209)
at com.iwaysoftware.af.container.IWAFContainer.start(IWAFContainer.java:169)
at com.ibi.afjca.spi.IWAFManagedConnectionFactory.getContainer(IWAFManagedConnectionFactory.java:536)
at com.ibi.afjca.spi.IWAFManagedConnectionFactory.createManagedConnection(IWAFManagedConnectionFactory.java:215)
at com.ibi.afjca.spi.IWAFConnectionManager.allocateConnection(IWAFConnectionManager.java:35)
at com.ibi.afjca.cci.IWAFConnectionFactory.getConnection(IWAFConnectionFactory.java:103)
at com.iwaysoftware.iwae.common.JCATransport.initJCA(JCATransport.java:104)
at com.iwaysoftware.iwae.common.JCATransport.<init>(JCATransport.java:85)
at com.iwaysoftware.iwae.common.AdapterClient.<init>(AdapterClient.java:85)
at com.ibi.bse.ConfigWorker.run(ConfigWorker.java:41)
at java.lang.Thread.run(Thread.java:595)
Wed, 11 Oct 2006 16:51:29.0419 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] *********************************
Wed, 11 Oct 2006 16:51:29.0420 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] Starting IWAF container managers.
Wed, 11 Oct 2006 16:51:29.0420 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] *********************************
Wed, 11 Oct 2006 16:51:29.0420 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] IWAF AdapterManager starting...
Wed, 11 Oct 2006 16:51:29.0421 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] IWAF AdapterManager started.
Wed, 11 Oct 2006 16:51:29.0421 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] IWAF ChannelManager starting...
Wed, 11 Oct 2006 16:51:29.0421 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] IWAF ChannelManager started.
Wed, 11 Oct 2006 16:51:29.0422 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] IWAF ChainManager starting...
Wed, 11 Oct 2006 16:51:29.0422 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] IWAF ChainManager started.
Wed, 11 Oct 2006 16:51:29.0422 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] IWAF PortManager starting...
Wed, 11 Oct 2006 16:51:29.0422 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] IWAF PortManager started.
Wed, 11 Oct 2006 16:51:29.0423 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] ********************
Wed, 11 Oct 2006 16:51:29.0423 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] IWAF AEManager start
ing...
Wed, 11 Oct 2006 16:51:29.0423 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] ********************
Wed, 11 Oct 2006 16:51:29.0424 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] ********************
Wed, 11 Oct 2006 16:51:29.0424 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] Building Target ID l
ist..
Wed, 11 Oct 2006 16:51:29.0424 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] ********************
Wed, 11 Oct 2006 16:51:29.0826 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] Creating TID for ada
pter 'Siebel' configuration 'ReutersSiebel'.
Wed, 11 Oct 2006 16:51:29.0840 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [Siebel.service_ReutersSiebel] Cr
eated adapter instance for class'class com.ibi.adapter.siebelaf.SiebelAdapter'.
Wed, 11 Oct 2006 16:51:29.0892 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] ********************
Wed, 11 Oct 2006 16:51:29.0893 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] Building Port list..
Wed, 11 Oct 2006 16:51:29.0893 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] ********************
Wed, 11 Oct 2006 16:51:29.0902 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] ********************
Wed, 11 Oct 2006 16:51:29.0902 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] Building Channel lis
t..
Wed, 11 Oct 2006 16:51:29.0911 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] ********************
Wed, 11 Oct 2006 16:51:29.0945 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [Siebel.channel_ReutersSiebelHTTP
] Created adapter instance for class'class com.ibi.http.adapter.HTTPListenerAdapter'.
Wed, 11 Oct 2006 16:51:29.0955 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] Creating channel for
adapter 'Siebel' configuration 'ReutersSiebelHTTP'.
Wed, 11 Oct 2006 16:51:29.0992 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] IWAF AEManager start
ed.
Wed, 11 Oct 2006 16:51:29.0992 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] [AE manager] ********************
Wed, 11 Oct 2006 16:51:30.0008 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA] [container] IWAF contained started.
Wed, 11 Oct 2006 16:51:30.0018 BST - Thread[Thread-5,6,main] [info ] [IWAF JCA IAEAdapter] IWAFManagedConnection for IAEAdapt
er:null has listener registered: com.ibi.afjca.spi.IWAFConnectionManager@cb754f
Wed, 11 Oct 2006 16:51:31.0282 BST - Thread[AWT-EventQueue-0,6,main] [info ] [IWAF JCA] [container] Loaded and initialized ad
apter class 'com.ibi.adapter.siebelaf.SiebelAdapter'.
Wed, 11 Oct 2006 16:51:31.0289 BST - Thread[AWT-EventQueue-0,6,main] [info ] [IWAF JCA] [container] Loaded and initialized ad
apter class 'com.ibi.http.adapter.HTTPListenerAdapter'.
Wed, 11 Oct 2006 16:51:31.0303 BST - Thread[AWT-EventQueue-0,6,main] [info ] [IWAF JCA] [container] [com.ibi.mq.MQListenerAda
pter] init called.
Wed, 11 Oct 2006 16:51:31.0303 BST - Thread[AWT-EventQueue-0,6,main] [info ] [IWAF JCA] [container] Loaded and initialized ad
apter class 'com.ibi.mq.MQListenerAdapter'.
Wed, 11 Oct 2006 16:51:31.0332 BST - Thread[AWT-EventQueue-0,6,main] [info ] [IWAF JCA] [container] [com.ibi.file.FileListene
rAdapter] init called.
Wed, 11 Oct 2006 16:51:31.0332 BST - Thread[AWT-EventQueue-0,6,main] [info ] [IWAF JCA] [container] Loaded and initialized ad
apter class 'com.ibi.file.FileListenerAdapter'.
Wed, 11 Oct 2006 16:51:58.0450 BST - Thread[Thread-7,6,main] [info ] [IWAF JCA] [container] [Siebel.service_ReutersSiebel] Cr
eated adapter instance for class'class com.ibi.adapter.siebelaf.SiebelAdapter'.
Wed, 11 Oct 2006 16:51:58.0811 BST - Thread[Thread-7,6,main] [error] [IWAF JCA] [container] [Siebel.service_ReutersSiebel] Pr
oblem activating adapter. (null). Check logs for more information
java.lang.IllegalStateException
at com.ibi.adapter.siebelaf.SiebelAdapter.activate(SiebelAdapter.java:143)
at com.iwaysoftware.af.container.adapter.ProxyAdapter.activate(ProxyAdapter.java:104)
at com.iwaysoftware.af.container.adapter.AdapterConfiguration.activateAdapter(AdapterConfiguration.java:319)
at com.iwaysoftware.af.container.adapter.AdapterConfiguration.getActivatedAdapter(AdapterConfiguration.java:299)
at com.iwaysoftware.af.container.AdapterManager.getActivatedAdapter(AdapterManager.java:269)
at com.iwaysoftware.af.container.IWAFContainer.getActivatedAdapter(IWAFContainer.java:526)
at com.iwaysoftware.af.container.AEManager.getTargetAdapter(AEManager.java:646)
at com.iwaysoftware.af.container.ae.AETargetMessage.buildGETTARGET(AETargetMessage.java:255)
at com.iwaysoftware.af.container.ae.AETargetMessage.build(AETargetMessage.java:84)
at com.iwaysoftware.af.container.ae.AETargetMessage.<init>(AETargetMessage.java:54)
at com.iwaysoftware.af.container.AEManager.dispatch(AEManager.java:131)
at com.iwaysoftware.af.container.IWAFContainer.dispatchAERequest(IWAFContainer.java:612)
at com.ibi.afjca.cci.IWAFInteraction.execIWAE(IWAFInteraction.java:270)
at com.ibi.afjca.cci.IWAFInteraction.exec(IWAFInteraction.java:155)
at com.ibi.afjca.cci.IWAFInteraction.execute(IWAFInteraction.java:93)
at com.iwaysoftware.iwae.common.JCATransport.execute(JCATransport.java:204)
at com.iwaysoftware.iwae.common.AdapterClient.getTarget(AdapterClient.java:293)
at com.ibi.bse.TargetWorker.run(TargetWorker.java:37)
at java.lang.Thread.run(Thread.java:595)
My platform is AS 10g (10.1.2.0.2) with Adapters (10.1.2.0.2) on Solaris 10. I am connecting to a Siebel 7.8 instance running on Windows 2000 SP4.
I would be very grateful of any help you could give.
Regards,
Mark.

Hi,
There could be couple of possible reasons for this. Please see below:
1. When you configure a adapter target for Siebel 7.7 or 7.8, do not supply a value for "Siebel Server" field. Please see details related to this in the "Defining a Target to Siebel" section of the Siebel adapter user guide.
2. If the adapter is installed in the UNIX platform, then necessary encoding should be added to the Application Explorer and the Application Server. Please see the details for this in the "Establishing a Connection (Target) for Siebel" of the Siebel adapter user guide.
Let me know whether this sorts out the issue or not.
Regards,
Kris

Sun PKCS#11 NSS Problem with CA Certificates

There appears to be a problem with the Sun PKCS#11 provider's NSS specific functionality.
If Firefox 2.x based KeyStore is loaded which contains CA Certificates which have been imported into the the standard "Software Security Device" (and are therefore not in the root store) they are not visible as Certificate Entries when enumerating the KeyStore aliases.
If a personal key/cert pair is present then the corresponding CA Certs can be obtained via KeyStore.getCertificateChain(alias) but this doesn't help when I have other CA's present that need to be accessed.
These additional CA Certificates are visible via the FireFox "Certificate Manager" and via the JSS API's - anyone aware of this problem ?

You need to use the trustanchors nssModule, read the JavaTM PKCS#11 Reference Guide at --
http://java.sun.com/javase/6/docs/technotes/guides/security/p11guide.html#Config
For example, you can write your config file like this --
name=NSS
nssSecmodDirectory=path_of_your_dbs
nssLibraryDirectory=path_of_dll_or_so
nssModule=trustanchors

Problem with placing self-signed certificate in trust store on WLS 10.3

I have had some problems setting up two-way SSL on WLS 10.3.2.
1. I have not been able to use the java properties listed on
http://weblogic-wonders.com/weblogic/2010/11/09/enforce-weblogic-to-use-sun-ssl-implementation-rather-than-certicom/
to use the native Java SSL implementation rather than the certicom. Has anyone else had success using these?
-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol
-Dssl.SocketFactory.provider=com.sun.net.ssl.internal.SSLSocketFactoryImpl
-DUseSunHttpHandler=true
-Dweblogic.wsee.client.ssl.usejdk=true (for webservice clients)
2. When I use the ValidateCertChain to validate my keystore with the self-signed certificate I get the message
CA cert not marked with critical BasicConstraint indicating it is a CA
Certificate chain is invalid
which I read was a problem with certificates generated by keytool, yet I find I was not able to circumvent this
by setting the property weblogic.security.SSL.enforceConstraints to off in the WLS server environment.
Has anyone else noticed this?
3. The error I get is
####<Feb 15, 2011 1:12:21 PM EST> <Debug> <SecuritySSL> <hostname> <server
<[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1297793541204> <BEA-000000> <Exception during hands
hake, stack trace follows
java.lang.NullPointerException
at com.certicom.security.cert.internal.x509.X509V3CertImpl.checkValidity(Unknown Source)
at com.certicom.security.cert.internal.x509.X509V3CertImpl.checkValidity(Unknown Source)
at com.certicom.tls.interfaceimpl.CertificateSupport.findInTrusted_Validity(Unknown Source)
####<Feb 15, 2011 1:12:21 PM EST> <Debug> <SecuritySSL> <hostname> <server> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tunin
g)'> <<WLS Kernel>> <> <> <1297793541207> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 40
java.lang.Exception: New alert stack
at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
Are there other conditions besides the issue about the missing Basic Constraint field that can raise an
alert with type 40?
4. Steps I used to generate jks keystore for inclusion in trust keystore (actual values substituted):
** keytool -genkey -alias mykey -keystore mykeystore -validity 35600 \
-dname "cn=Common Name, ou=Common Name, o=Org, l=location, s=state, c=US" \
-storepass mypass -keypass mypass
** exported a DER format head certificate of mykey into mykey.cer.der
** keytool -import -trustcacerts -keystore DemoTrust.jks -alias mykey -file mykey.cer.der
Any comments appreciated and thanks for this forum.

Faisal,
Certicom has an internal restriction that a Date must be notBefore 1970 and notAfter 2105 inclusive.The Java-generated key is valid until Wed Mar 14 11:03:59 EDT 2108. Your knowledge of this area is
quite impressive, thank you so much for this!

Problem with SSL

I have created a java application that communicates with a Server via HTTPS.
I use both jdk and jre 1.5
I know this has somthing to do with Certificates and Storing them
But i dont know exactly what to do.
Can Som1 pls help me
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1518)
     at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:174)
     at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:168)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:848)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:106)
     at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:495)
     at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:433)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:818)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1030)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:622)
     at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59)
     at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
     at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
     at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:827)
     at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1975)
     at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)
     at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)
     at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)
     at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)
     at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)
     at lk.informatics.infopro.connector.command.AptiloHTTPCommand.httpPost(AptiloHTTPCommand.java:106)
     at lk.informatics.infopro.connector.command.AptiloHTTPCommand.performTask(AptiloHTTPCommand.java:134)
     at lk.informatics.infopro.connector.SimpleRMIImpl.performTask(SimpleRMIImpl.java:112)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
     at sun.rmi.transport.Transport$1.run(Transport.java:153)
     at java.security.AccessController.doPrivileged(Native Method)
     at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
     at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
     at java.lang.Thread.run(Thread.java:595)
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:221)
     at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:145)
     at sun.security.validator.Validator.validate(Validator.java:203)
     at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:172)
     at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(SSLContextImpl.java:320)
     at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:841)
     ... 30 more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
     at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:236)
     at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:194)
     at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:216)
     ... 35 more

The problem that i had was that my application was unable to find a valid certificate that proved that the site can be trusted.
What you need to do is to tell the application that the site can be trusted and point it to a certificate that proves the site that you want to communicate with is a valid one.
If the application cannot find a proper certificate then it results in a failed SSL handshake.
What you must do is save the certificate provided by the site you wish to communicate and point the application to it. Done in 3 steps
1.     Save the certificate provided by the end site on the as a .cer file
     eg:- theSite.cer
     This can be done via IE or Mozilla (Has not been tested with Mozilla yet)
To do this open the site on your browser, When the browser asks if you
wish to accept the certificate provided by the site view the certificate and
save it.
2.     Create a keyStore and add the saved certificate to it. Use the java "keytool" command in the command prompt to achive this
     keytool -import -alias ALIAS -file CERTIFICATE.cer -keystore KEY_STORE_NAME
     eg:-
     keytool -import -alias test -file theSite.cer -keystore TS
3.     In you application make sure that you specify where to look for the Trusted Key Store in.
     System.setProperty("javax.net.ssl.trustStore", "TRUST_STORE_NAME");
     System.setProperty("javax.net.ssl.trustStorePassword", "TRUST_STORE_PASSWORD");
     eg:-
     System.setProperty("javax.net.ssl.trustStore", "C:\\Key_Store\\TS");
     System.setProperty("javax.net.ssl.trustStorePassword", "XXX");
     ALT: you can also specify the above values on the java execution command as
-Djavax.net.ssl.trustStore=C:\Key_Store\TS -Djavax.net.ssl.trustStorePassword=XXX
-Djavax.net.debug=all
Can be used to view all debug information.
Simply put we save the sites certificate in step 1. create a new KeyStore and and save the certificate in it in step 2 and show the application where to look for the valid certificate by pointing it to the proper keyStore in step 3.
Note that you can save multiple certificates on the same keyStore.
If you have any problems with this let me know

Problems with Oracle Web Logic 10.3.6, certificates and proxies

Good morning.
We are trying to establish a SSL connection using Apache Cxf and WebLogic Server 10.3.6.
For that, we are passing through a proxy. Using Apache Tomcat, the test is ok, we can connect to the endpoint correctly. But in WebLogic 10.3.6, we have problems with the certificates.
In our code, we are loading the certificates programatically.
The web-services-config.xml is the following:
<?xml version="1.0" encoding="UTF-8"?>
<beans
     xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd http://cxf.apache.org/configuration/security http://cxf.apache.org/schemas/configuration/security.xsd http://cxf.apache.org/transports/http/configuration http://cxf.apache.org/schemas/configuration/http-conf.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-2.5.xsd"
     xmlns:http="http://cxf.apache.org/transports/http/configuration"
     xmlns:sec="http://cxf.apache.org/configuration/security" xmlns:jaxws="http://cxf.apache.org/jaxws"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.springframework.org/schema/beans">
     <jaxws:client address="@SNE.SNE_WS_URL@"
          serviceClass="com.bankia.sne.ws.clientes.buzonAPESNE.APESNEBuzonWSTipoPuerto"
          id="puertoAPESNEBuzonWS" />
     <http:conduit name="@SNE.SNE_WS_URL@">
          <http:client Connection="Keep-Alive" AutoRedirect="true"
               ProxyServerType="HTTP" ProxyServerPort="@SNE.PROXY_PORT@"
               ProxyServer="@SNE.PROXY_HOST@" />
          <http:proxyAuthorization>+
               <sec:UserName>@SNE.PROXY_USER@</sec:UserName>
               <sec:Password>@SNE.PROXY_PASSWORD@</sec:Password>
          </http:proxyAuthorization>
          <http:tlsClientParameters>
               <sec:cipherSuitesFilter>
                    
                    <sec:include>.*EXPORT.*</sec:include>
                    <sec:include>.*EXPORT1024.*</sec:include>
                    <sec:include>.*WITHDES_.*</sec:include>
                    <sec:include>.*WITHNULL_.*</sec:include>
                    <sec:exclude>.*DHanon_.*</sec:exclude>
               </sec:cipherSuitesFilter>
          </http:tlsClientParameters>
     </http:conduit>
</beans>
That's the code used for establish the CXF connection:
private void configuraConexion(Buzon buzon){
          try {
               LOGGER.debug("Configurando conexión con el sevicio Web para el buzón con id " + buzon.getId() + " ...");
               Client client = ClientProxy.getClient(puertoAPESNEBuzonWS);
               HTTPConduit httpConduit = (HTTPConduit) client.getConduit();
               TLSClientParameters tlsParams = httpConduit.getTlsClientParameters();
               Certificado certificado = buzon.getCertificado();
               byte[] bytes = certificado.bytesCertificado();
               CertificadoSerializable certSerializado = (CertificadoSerializable)Serializador.desserializar(bytes);
               //Cargamos el truststore de disco
               TrustManagerFactory trustFactory = TrustManagerFactory.getInstance(TrustManagerFactory.getDefaultAlgorithm());
               KeyStore truststore = KeyStore.getInstance(Propiedades.getProperty(KEY_SERVICIO_WEB_ALMACEN_TRUSTSTORE));
               String contrasenia = Propiedades.getProperty(KEY_SERVICIO_WEB_TRUSTORE_PASSWORD);
               // -- provide your truststore
               File ficheroTruststore = null;
               String rutaTrustore = Propiedades.getProperty(KEY_SERVICIO_WEB_TRUSTORE_RUTA) Propiedades.getProperty(KEY_SERVICIO_WEB_NOMBRE_TRUSTSTORE);
               LOGGER.debug("rutaTrustore --> " + rutaTrustore);
               if (rutaTrustore!=null){+
                    ficheroTruststore = new File(rutaTrustore);
          URL url = null;
               if(ficheroTruststore == null || !ficheroTruststore.exists()){
                    url = Localizador.getResource(Propiedades.getProperty(KEY_SERVICIO_WEB_NOMBRE_TRUSTSTORE));
                    ficheroTruststore = new File(url.getPath());
                    truststore.load(url.openStream(), contrasenia.toCharArray());
               }else{
                    truststore.load(new FileInputStream(ficheroTruststore), contrasenia.toCharArray());
               LOGGER.info("[ServicioWSBuzonAPESNEImpl.configuraConexion] Fichero truststore.pks recuperado de "+ficheroTruststore.getPath());
               trustFactory.init(truststore);
               TrustManager[] tm = trustFactory.getTrustManagers();
               tlsParams.setTrustManagers(tm);
               //Cargamos el Keystore de base de datos
               KeyStore keyStore = KeyStore.getInstance(Propiedades.getProperty(KEY_SERVICIO_WEB_TIPO_ALMACEN_KEYSTORE));
               keyStore.load(null, certificado.getContrasenia().toCharArray());
               keyStore.setKeyEntry(certificado.getAlias(), certSerializado.getClavePrivada(), certificado.getContrasenia().toCharArray(), certSerializado.getCadena());
               // set our key store+
               // (used to authenticate the local SSLSocket to its peer)
               KeyManagerFactory keyFactory = KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm());
               keyFactory.init(keyStore, certificado.getContrasenia().toCharArray());
               KeyManager[] km = keyFactory.getKeyManagers();
               tlsParams.setKeyManagers(km);
               httpConduit.setTlsClientParameters(tlsParams);
               LOGGER.debug("Conexión configurada satisfactoriamente");
          }catch (Exception e) {
               LOGGER.error("Error al configurar la conexión del servicio Web", e);
               throw new WSBuzonException("Error al configurar la conexión del servicio Web: " + e.getMessage());
We don't know how to solve this issue? Please, could you help us?
Thanks in advance,
Jaime.
Edited by: j2eedevelopment on 10-jul-2012 10:05

Hi Zack, thanks for the answer.
I've cleaned the code below.
Our problem is the following: we wan't to use many keystores, in function the user who is connected in the application. For that reason, we wan't to give the keyStore from Java Client, because we've saw that, in WebLogic, you can select one keystore, but only one. For that reason, we wantto change the keystore in run time execution, dinamically.
The problem we have found are the following:
1) If we configure WebLogic with the correct keystore and trustore, we are not able to change keysotre and trustore in runtime execution, so we have to us always the same keystore and we don't want this.
2) Also, I'm trying now to use JaxWS instead Apache Cxf, and I've tried to put the ssl properties of the system with the following code:
System.setProperty(JAVAXNETSSLTRUST_STORE, trustore);
System.setProperty(JAVAXNETSSLTRUST_STORE_PASSWORD, trustStorePassword);
System.setProperty(JAVAXNETSSLKEY_STORE, keyStore);
System.setProperty(JAVAXNETSSLKEY_STORE_PASSWORD, keyStorePassword);
System.setProperty(JAVAXNETSSLKEY_STORE_TYPE, keyStoreType);
Thanks in advance,
Jaime.

Problem with keystore

Similar Messages

Maybe you are looking for