Tasja Mango

Greenhorn
+ Follow
since Mar 03, 2004
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
1
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Tasja Mango

Hey,

there are some profilers on the market, which you can download and test during 20 days. I think, this is enough time to find your bug.


A simple but handy tool for memory leak detection is http://www.jb2works.com/.

Download it, modify your script startWebLogic.cmd:

a) set CLASSPATH=%WEBLOGIC_CLASSPATH%;...;%CLASSPATH%;D:\Tools\Jb2Works\jb2refscan-XXXXXX.jar

b) Add the Reference Scanner class path argument just before "weblogic.Server":
%JAVA_HOME%\bin\java –Xms128m –Xmx512m … com.jb2works.reference.Launcher weblogic.Server

Restart the server, open a browser window to this address: http://localhost:4040/

Good Luck
Tasja
15 years ago
I have made quite good experiences with Hybersonic/HSQL (as say above).

Alternatively, there is
http://db.apache.org/derby/
which I don't know in pratice.
17 years ago
You may use

System.setProperty("javax.net.debug", "all");

before starting a test...

by this, the soft shows which certificate store file is loaded. So you can check if your setting is taken into account.

In fact, there are 3 properties that should be used (and they are taken into account by/via AXIS).
System.setProperty("javax.net.ssl.keyStore", "...ty\\cacerts");
System.setProperty("javax.net.ssl.keyStorePassword", "");
System.setProperty("javax.net.ssl.trustStore", "...curity\\cacerts");

Alternatively, you can disable certificate checking with

AxisProperties.setProperty("axis.socketSecureFactory","org.apache.axis.components.net.SunFakeTrustSocketFactory");

(of interrest only when it doesnt matter to ensure the servers identity, when e.g. when only the SSL encryption itself is of importance).

Hope this helps
Tasha
18 years ago
Hello,

I had serious problems making work AXIS over SSL (1.1, JDK14). All the time, I got "javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found".

The first thing to try was the well known solution:

TrustManager[] tm = new TrustManager[ 1 ];
tm[0]=new NaiveTrustManager( ); // accepts all
context.init(null, tm, new SecureRandom());
HttpsURLConnection.setDefaultSSLSocketFactory(context.getSocketFactory());

But AXIS absolutely refused to take setting this into account, the SUN default class got called every time.

On the net, google, AXIS mailing lists, etc no one had really a solution. Either there was never an answer, "use CommonsHttpSender & config HttpClient" (too complicated since need to rebuild AXIS), or "import server certs to your keyring" (not a acceptable solution for me)...

After some hours in the AXIS source codes, I stumbled over the SocketFactoryFactory...

All what's needed is provided by AXIS:

AxisProperties.setProperty("axis.socketSecureFactory","org.apache.axis.components.net.SunFakeTrustSocketFactory");

et voila...

This post just to share a useful information...
Natasha
18 years ago
FYI, problem solved by updating to JDK 1.4 ... yeah!
18 years ago
Hello,
I have some stress with my webservice client implementation.
I do the following (I can post source code if needed):
- As usual:
System.setProperty("java.protocol.handler.pkgs","com.sun.net.ssl.internal.www.protocol");
Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
- Install my TrustManager
- Install my DefaultHostnameVerifier
- Register a custom type
- Make a javax.xml.rpc.Call to access a webservice
My observations:
The code works well when using an HTTP URL, just changing the target URL to HTTPS causes the problem.
The HTTPS web service (on server) works well seeing a HTTPS client using the weblogic SSL implementation can easily connect.
When I use a simple and direct "Open HttpsURLConnection on URL("https://xxx.service?WSDL"); print-out-all-that's-coming-in", it works well. I think my SSL access is made correctly.
The client does not complain about not-installed SSL things, all certificates are accepted, etc. No problem at this part.
System.setProperty("javax.net.debug", "all") is set, but i dont see anything of interrest.
I use the packages contained in 'java_xml_pack-summer-02_01' of SUN (jaxm-1.1_01, jaxp-1.2_01,jaxr-1.0_02 etc and the jsse 1.0.3). No weblogic SSL stuff used.
The server is weblogic 7.
Calling
call.setTargetEndpointAddress("http://arakis:7001/traces_ws/searchCertificate");
works well while
call.setTargetEndpointAddress("https://arakis:7002/traces_ws/searchCertificate");
causes (after 2 minutes):
HTTP transport error: java.net.SocketException: Unexpected end of file from server
at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpClientTransport.java:189)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:73)
at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:54)
at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:279)
at SSLSOAPClient.main(SSLSOAPClient.java:264)
CAUSE:
java.net.SocketException: Unexpected end of file from server
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:699)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:604)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:697)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:604)
at com.sun.xml.rpc.client.http.handler.HttpURLConnection.getInputStream(HttpURLConnection.java:543)
at com.sun.xml.rpc.client.http.handler.HttpURLConnection.getResponseCode(HttpURLConnection.java:920)
at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpClientTransport.java:123)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:73)
at com.sun.xml.rpc.client.dii.CallInvokerImpl.doInvoke(CallInvokerImpl.java:54)
at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:279)
at SSLSOAPClient.main(SSLSOAPClient.java:264)
Exception in thread "main"
What I note is that the call is using a HttpURLConnection object and NOT a HttpsURLConnection object (so problems are 'normal' i guess), but I dont have any clue what I have to do to instruct the client to use HTTPS other than specifying HTTPS in the target.
Hope someone has an idea
Tasha
18 years ago