Classloading func evolution btw WLS7 SP2 et WL7SP3

Hi,
I migrate an application from WebLogic Server 7.0 SP2 to WLS 7.0 SP3 and a classloading
issue appears (wo ear evolution)
*** short ***
In an EAR, a webapp servlet cannot see the appropriate classes stored in jars
contains in EAR despite Manifest.mf classpath. This appears in the WL7SP3 and
works fine in SP2
*** long ****
Let's desribe the structure
EAR
- commons-validator.jar
- META-INF
blah...
- webapp (exploded version of my webapp.war
- WEB-INF
- lib
- struts.jar
- META-INF
- Manifest.mf (include commons-validator.jar in the ClassPath)
During the init of a servlet class (in struts.jar), there is need of some commons-validator.jar
classes.
In wlsSP2, this works fine
In wls SP3, the class isn't found NoClassDefFoundException
Note: I used the same JVM (Sun 1.3.1_06), but it's pretty much the same with the
_08
Does anybody knows why and how the classloading strategy evolved ? Is It a bug

Nagesh Susarla wrote:
Emmanuel Bernard wrote:
Hi,
I migrate an application from WebLogic Server 7.0 SP2 to WLS 7.0 SP3
and a classloading
issue appears (wo ear evolution)
*** short ***
In an EAR, a webapp servlet cannot see the appropriate classes stored
in jars
contains in EAR despite Manifest.mf classpath. This appears in the
WL7SP3 and
works fine in SP2
*** long ****
Let's desribe the structure
EAR
- commons-validator.jar
- META-INF
blah...
- webapp (exploded version of my webapp.war
- WEB-INF
- lib
- struts.jar
- META-INF
- Manifest.mf (include commons-validator.jar in the ClassPath)
During the init of a servlet class (in struts.jar), there is need of
some commons-validator.jar
classes.
In wlsSP2, this works fine
In wls SP3, the class isn't found NoClassDefFoundException
Note: I used the same JVM (Sun 1.3.1_06), but it's pretty much the
same with the
_08
Does anybody knows why and how the classloading strategy evolved ? Is
It a bugIs this an exploded ear?
--Nagesh
I think this happens for an exploded war only and you can contact
[email protected] and ask for a patch to CR120228
hope that helps
--Nagesh

Similar Messages

Attachment in WLS 7 sp2 Web Service

Hi, I'm trying to send to a Web Service in WLS7 sp2 SOAP message with attachments. My problem: when I don't add any attachment to SOAP message all go OK, but when I add an attachment with the "href" attribute in an element of the message (I need do it because I use the MM7 protocol of 3GPP), WLS7 donÂ´t accept my message and tell me: "The ID referenced by ..... is unknow". The Content-ID of attachment is equal to value of the href attribute.
Please, I need help with this!! If anyone knows any URL or sample code that can help me, please, reply to this post.
Thanks and sorry, my english is not very well.

Currently there is no option to turn off security check.
I think you can use a servlet filter mapped to the URL
of your service, instead of a proxy servlet?
Regards,
-manoj
http://manojc.com
"Toni Nykanen" <[email protected]> wrote in message
news:3ef1577b$[email protected]..
>
Hi!
We need to implement authentication using our own methods, and theauthentication
information is provided to the web service implementation in a basicauthentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles webservices
in
wls 7.0.sp2, always attempts to perform authentication, if the header ispresent.
Is there any way to circumvent this, because we want to implementauthentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for ourown
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet,which
would
remove the basic authentication header, and put the authentication info incustom
headers, such as x-auth: <user:password>, or smthng similar, and aftersuccessful
authentication, make a call to bea's servletweblogic.webservice.server.servlet.WebServiceServlet.
>
But still, I'd like to know if there is any way to tell bea's servlet toignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

WLS7 Deploy on startup works, redeploy gets ClassNotFoundExceptions

Hello
We are using WLS7 SP2 on our local pcs. We package our app as an EAR that contains
several libraries, a war, and several EJB jars. When we put it in the applications
folder and start the server, it deploys fine, works fine. In WLS6.1SP3, when
we used hot deploy to redeploy the app, it would load (although we saw the memory
leak happen). But now in WLS7, we frequently (but not consistently) get error
messages that there are classes that cannot be found.
I have tried fiddling with the deployment order in application.xml, and that didn't
seem to help consistently. I also modified the ant script to call weblogic.Deployer
to -remove the application prior to copying the ear to the applications directory,
and still no real difference.
The thing that's frustrating is that it deploys at startup with no trouble at
all. Is it possible that on redeply there's some lingering references to the
old ear that don't get cleared when it's undeployed? Is the server maybe caching
something?
Has anyone else out there experienced the same problem with hot-deploy in WL7SP2?
Did you resolve the problem? If so, how? Arrrrgghh!!!!!!!

Matt:
Sorry for your frustrations! This is (and I know you don't want to hear
this probably) something that we worked very hard on for the 8.1 release,
ironed out all the bugs in hot deploy. Cleaned up memory leaks and made it
so you don't have to restart the server. We found additionally that the
applications directory is a bit of a hack useful for toy demo's but not real
development. (i.e. you are constantly either archiving and copying or copy
files from your pcs to the directory). So we introduced an approach that
allows you to check your application's src files (jsp, descriptors, .java
files, thirdparty libs) into pcs in exploded ear format and then introduced
a set of ant tasks to help you build and deploy.
So if you can upgrade...... check out:
http://google.bea.com/search?q=split+directory&ie=&site=bea&output=xml_no_dtd&client=bea&lr=&proxystylesheet=http%3A%2F%2Fdev2dev.bea.com%2Fimages%2Fdev2dev.xsl&oe=
Otherwise we go down the road of having a reproducible test case and
oppening a ticket with support.
Cheers
mbg
"Matt Harrah" <[email protected]> wrote in message
news:[email protected]...
>
Hello
We are using WLS7 SP2 on our local pcs. We package our app as an EAR thatcontains
several libraries, a war, and several EJB jars. When we put it in theapplications
folder and start the server, it deploys fine, works fine. In WLS6.1SP3,when
we used hot deploy to redeploy the app, it would load (although we saw thememory
leak happen). But now in WLS7, we frequently (but not consistently) geterror
messages that there are classes that cannot be found.
I have tried fiddling with the deployment order in application.xml, andthat didn't
seem to help consistently. I also modified the ant script to callweblogic.Deployer
to -remove the application prior to copying the ear to the applicationsdirectory,
and still no real difference.
The thing that's frustrating is that it deploys at startup with no troubleat
all. Is it possible that on redeply there's some lingering references tothe
old ear that don't get cleared when it's undeployed? Is the server maybecaching
something?
Has anyone else out there experienced the same problem with hot-deploy inWL7SP2?
Did you resolve the problem? If so, how? Arrrrgghh!!!!!!!

Remote Start classpath

          Hi,
          I have installed an admin server, a managed server and a node manager on a single
          machine. (btw, I'm using WLS7 sp2)
          With the default config, the managed server starts and stops successfully from
          the console. However, I need to specify a classpath for this server to locate
          my log4j configuration file. I've used the "Class Path" field of the "Remote Start"
          tab of my managed server. As soon as a classpath is specified, the managed server
          doesn't start anymore, and I get the following log :
          29 juil. 03 12:22:01 CEST> <Info> <NodeManager@mymachine:5555> <Starting Server
          mydomain::managedserver ...>
          java.lang.NoClassDefFoundError: weblogic/Server
          Exception in thread "main"
          <29 juil. 03 12:22:02 CEST> <Info> <NodeManager@mymachine:5555> <Server mydomain::managedserver
          started, process id = 72 040>
          I've tried different formats for my classpath (c:\mydir, c:/mydir ...), but I
          always get the same error.
          Any clue?


          The classpath from the console actually overrides the default classpath (I thought
          it was just appended).
          Adding weblogic.jar solved the problem.

Document style Problem

We have three issues when trying to implement a document-style service. I will
document them all but I'd suggest you go through them all before attempting to
answer any of them.
We are trying to implement a service that has the following signature:
public void echoDom(Document doc)
We want the delivery of our message to be of style ("document"). Therefore, we
modified our servicegen entry to include the style="document" under the service.
It looks like the following:
<servicegen
destEar="${appDir}/dom.ear"
warName="dom.war">
<service
javaClassComponents="examples.dom.EchoDom"
targetNamespace="http://examples.org"
serviceName="dom"
serviceURI="/EchoDomService"
generateTypes="True"
expandMethods="True"
style="document">
<client
packageName="examples.dom"
clientJarName="client.jar"
/>
</service>
<classpath>
<pathelement path="${temp_dir}"/>
<pathelement path="${java.class.path}"/>
</classpath>
</servicegen>
1. FIRST PROBLEM:
The first problem we're having is that it does not compile with the combination
of our signature being of type void (as shown above) and the style="document"
in build.xml.
The error is the following:
[servicegen] Generating service "dom" ...
[servicegen] Generating XML types and serializers from java classes (examples.do
m.EchoDom) ...
[servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ void:
null ]
[servicegen] at weblogic.utils.Debug.assertion(Debug.java:84)
[servicegen] at weblogic.xml.schema.binding.internal.codegen.Compiler.compile
(Compiler.java:111)
[servicegen] at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
pClass(XSDTypeMappingBuilder.java:88)
[servicegen] at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
ddMapping(TypeMappingBuilderBase.java:183)
[servicegen] at weblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper
.mapComponent(ComponentAutoTyper.java:155)
[servicegen] at weblogic.ant.taskdefs.webservices.autotype.JavaAutoTyper.run(
JavaAutoTyper.java:80)
[servicegen] at weblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execu
te(AutoTypeTask.java:353)
[servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g
enerateService(ServiceGenTask.java:251)
[servicegen] at weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e
xecute(ServiceGenTask.java:146)
[servicegen] at org.apache.tools.ant.Task.perform(Task.java:217)
[servicegen] at org.apache.tools.ant.Target.execute(Target.java:164)
[servicegen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[servicegen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[servicegen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[servicegen] at org.apache.tools.ant.Main.start(Main.java:153)
[servicegen] at org.apache.tools.ant.Main.main(Main.java:176)
2. SECOND PROBLEM
If we change the signature to become:
public Document echoDom(Document doc)
then the build works but when we try to test our service, it gives us the following:
[java] java.rmi.RemoteException: web service invoke failed; nested exceptio
n is:
[java] javax.xml.soap.SOAPException: failed to serialize xml:weblogic.
xml.schema.binding.SerializationException: type mapping lookup failure on class=
class weblogic.apache.xerces.dom.DocumentImpl TypeMapping=TYPEMAPPING SIZE=6
[java] ENTRY 1:
[java] class: org.w3c.dom.Document
[java] xsd_type: ['http://examples.org']:p3:echoDom
[java] ser: weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@5973ea
[java] deser: weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@49131c
[java] ENTRY 2:
[java] class: java.lang.Object
[java] xsd_type: ['http://examples.org']:p1:echoDomResponse
[java] ser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
5b99f
[java] deser: weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
3. THIRD PROBLEM:
Now, when we revert back to style="rpc" and everything works fine and dandy (although
not as we want it because, as I mentioned above, we want a void signature and
a document style), we get the following added tag around our body content, which
we did not add ourselves, nor are we sure yet why it shows up:
We pass it the following argument:
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
We get the following (notice the <document> tag around it):
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
4. PROBLEM FOUR (just remembered this one):
If we use the standard test page (provided with WLS), with (3) above, it chops
off the "those" and it still wraps it within this new <document> element as show
below:

<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
</env:Header>
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
We're not so worried about the fourth because it seems like a bug but the first
three (especially the first) are most important. Any ideas would be appreciated.
Thanks
sami

Ok I tried it out, DOM with document style web
service is not working in WLS 7.0.2. I filed
CR104719. Please contact support with this case
number to get a patch.
Sorry for the trouble.
http://manojc.com
"sami titi" <[email protected]> wrote in message
news:[email protected]...
>
We're using WLS7 SP2, patch: CR102544_70sp2_v2.jar
thanks
"manoj cheenath" <[email protected]> wrote:
Quick question, before i try this out.
Which version of WLS? SP?
http://manojc.com
"sami titi" <[email protected]> wrote in message
news:[email protected]...
We have three issues when trying to implement a document-style service.I
will
document them all but I'd suggest you go through them all beforeattempting to
answer any of them.
We are trying to implement a service that has the following signature:
public void echoDom(Document doc)
We want the delivery of our message to be of style ("document").Therefore, we
modified our servicegen entry to include the style="document" underthe
service.
It looks like the following:
<servicegen
destEar="${appDir}/dom.ear"
warName="dom.war">
<service
javaClassComponents="examples.dom.EchoDom"
targetNamespace="http://examples.org"
serviceName="dom"
serviceURI="/EchoDomService"
generateTypes="True"
expandMethods="True"
style="document">
<client
packageName="examples.dom"
clientJarName="client.jar"
/>
</service>
<classpath>
<pathelement path="${temp_dir}"/>
<pathelement path="${java.class.path}"/>
</classpath>
</servicegen>
1. FIRST PROBLEM:
The first problem we're having is that it does not compile with thecombination
of our signature being of type void (as shown above) and thestyle="document"
in build.xml.
The error is the following:
[servicegen] Generating service "dom" ...
[servicegen] Generating XML types and serializers from java classes(examples.do
m.EchoDom) ...
[servicegen] weblogic.utils.AssertionError: ***** ASSERTION FAILED*****[ void:
null ]
[servicegen] at weblogic.utils.Debug.assertion(Debug.java:84)
[servicegen] atweblogic.xml.schema.binding.internal.codegen.Compiler.compile
(Compiler.java:111)
[servicegen] atweblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.ma
pClass(XSDTypeMappingBuilder.java:88)
[servicegen] atweblogic.xml.schema.binding.internal.TypeMappingBuilderBase.a
ddMapping(TypeMappingBuilderBase.java:183)
[servicegen] atweblogic.ant.taskdefs.webservices.autotype.ComponentAutoTyper
mapComponent(ComponentAutoTyper.java:155)
[servicegen] atweblogic.ant.taskdefs.webservices.autotype.JavaAutoTyper.run(
JavaAutoTyper.java:80)
[servicegen] atweblogic.ant.taskdefs.webservices.autotype.AutoTypeTask.execu
te(AutoTypeTask.java:353)
[servicegen] atweblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.g
enerateService(ServiceGenTask.java:251)
[servicegen] atweblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask.e
xecute(ServiceGenTask.java:146)
[servicegen] at org.apache.tools.ant.Task.perform(Task.java:217)
[servicegen] at org.apache.tools.ant.Target.execute(Target.java:164)
[servicegen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[servicegen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[servicegen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[servicegen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[servicegen] at org.apache.tools.ant.Main.start(Main.java:153)
[servicegen] at org.apache.tools.ant.Main.main(Main.java:176)
2. SECOND PROBLEM
If we change the signature to become:
public Document echoDom(Document doc)
then the build works but when we try to test our service, it givesus the
following:
[java] java.rmi.RemoteException: web service invoke failed; nestedexceptio
n is:
[java] javax.xml.soap.SOAPException: failed to serializexml:weblogic.
xml.schema.binding.SerializationException: type mapping lookup failureon
class=
class weblogic.apache.xerces.dom.DocumentImpl TypeMapping=TYPEMAPPINGSIZE=6
[java] ENTRY 1:
[java] class: org.w3c.dom.Document
[java] xsd_type: ['http://examples.org']:p3:echoDom
[java] ser:weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@5973ea
[java] deser:weblogic.xml.schema.binding.internal.builtin.DocumentCode
c@49131c
[java] ENTRY 2:
[java] class: java.lang.Object
[java] xsd_type: ['http://examples.org']:p1:echoDomResponse
[java] ser:weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
5b99f
[java] deser:weblogic.xml.schema.binding.internal.builtin.XSDAnyCodec@
3. THIRD PROBLEM:
Now, when we revert back to style="rpc" and everything works fine anddandy (although
not as we want it because, as I mentioned above, we want a void
signature
and
a document style), we get the following added tag around our body
content,
which
we did not add ourselves, nor are we sure yet why it shows up:
We pass it the following argument:
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
We get the following (notice the <document> tag around it):
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<those dummy="hi">
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</those>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
4. PROBLEM FOUR (just remembered this one):
If we use the standard test page (provided with WLS), with (3) above,it
chops
off the "those" and it still wraps it within this new <document>
element
as show
below:

<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
</env:Header>
<env:Body>
<m:echoDom xmlns:m="http://examples.org"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<document>
<this xmlns="mynamespace">
<f:that xmlns:f="yournamespace">
<or> a lot of random < </or>
<f:the>
</f:the>
<f:other> foo bar blaz</f:other>
</f:that>
</this>
</document>
</m:echoDom>
</env:Body>
</env:Envelope>
We're not so worried about the fourth because it seems like a bug butthe
first
three (especially the first) are most important. Any ideas would beappreciated.
Thanks
sami

Mod_wl_20.so, apache-2.0.45 with MPM worker

Hi,
we currently are using apache-2.0.45 with MPM prefork on Solaris 9. We plan to
use MPM worker in the future. apache uses mod_wl_20.so to proxy requests for the
Backend (WLS7 SP2). On http://httpd.apache.org/docs-2.0/misc/perf-tuning.html#compiletime
they say "prefork:...it can be used with non-thread-safe third-party modules,...".
As I understand it, this means: If using MPM worker, every module have to be thread-safe.
The Question is: is mod_wl_20.so thread-safe or not, so that we can use MPM worker?
Thanks
Andreas

Yes, actually what happened is that I was using WL 6.1SP2, and the plugin
did work for releases lower or equal than version 2.0.44, now the problem is
fixed with the last available plugin.
Thanks for your support
Luis
"Eric Gross" <[email protected]> wrote in message
news:3ebacf38$[email protected]..
That should not be correct.
Are you sure you are using the same plugin? You would get this message if
you used any plugin prior to 6.1 SP4 or 7.0 SP2.
Otherwise you should not get this error message when using the plugin from
either of the above releases.
Regards,
Eric
"Luis Esteban" <[email protected]> wrote in message
news:3eb8d994$[email protected]..
Here, with apache 2.0.44 it works fine, and we have no problem, but whenwe upgrade
apache from 2.0.44 to 2.0.45 we get the following error
httpd: module "mod_weblogic.c" is not compatible with this version ofApache (found
20020612, need 20020903).
Please contact the vendor for the correct version.
Could you tell please me where to find a plugin suitable for the newapache version,
or in the other hand, could you tell me how to workaround this problem.
Thanks.

HTTPs webservice

Hi,
I am doing test on a webservice. It's running on WLS7 SP2. The webservice implementation
is a java class in a web application. The web application runs on http.
Q: 1. Can I apply for https protocol on web service in this case?
2. I tried to add security constraints to the URL of web service and everything
looks fine. However, I still can use HTTP to access the web service.
Any point is helpful.
Thanks.

Yes, you need to set up the server to
do https.
Regards,
-manoj
http://manojc.com
"Peter Wang" <[email protected]> wrote in message
news:3f5f44d2$[email protected]..
>
Thanks Manoj,
I used that task to generate the web-service.xml and I checked in that xmlit
has "protocol='https'". The problem is that the weblogic server is notconfigured
using SSL.
I want to know if it's the requirement to configure the server by usingSSL.
>
>
"manoj cheenath" <[email protected]> wrote:
Are you generating the service using servicegen?
If so check out edocs at:
http://edocs.bea.com/wls/docs70/webserv/anttasks.html#1063540
I think you need to set the porotcol attribute to "https" in
the servicegen ant task.
Regards,
-manoj
http://manojc.com
"Peter Wang" <[email protected]> wrote in message
news:3f5e4fe1$[email protected]..
Hi,
I am doing test on a webservice. It's running on WLS7 SP2. The
webservice
implementation
is a java class in a web application. The web application runs on http.
Q: 1. Can I apply for https protocol on web service in this case?
2. I tried to add security constraints to the URL of web service andeverything
looks fine. However, I still can use HTTP to access the web service.
Any point is helpful.
Thanks.

Problem updating CA root certificates in cacerts file

I've searched all over for this problem, and none of the posting seems to apply
to my situation. Hope this is not a repeat post.
I'm running WLS7 SP2 on W2K AS. I had SSL configured and working properly, until
1/7/2004 came along, of course. I followed the directions in http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert/57436
to update the Verisign Class2 and 3 root certificates in the cacerts file without
any problem. I also verified from the WL log that the server is reading the "cacerts"
file located in <bea_home>\server\lib. However, when I pulled up my website using
https://, I still get the "...security certificate has expired ..." message.
Why is my browser not getting the updated CA certificates from WLS?
Any help you can provide is much appreciated.
Michael An

Is the server's identity certificate issued by Verisign? Have you updated it? Does
the identity certificate chain include the root CA certificate? It might be that
the browser contains the expired certs among its trusted ca certificates, uses
them to complete the chain and then complains about it.
Pavel.
"Michael An" <[email protected]> wrote:
>
I've searched all over for this problem, and none of the posting seems
to apply
to my situation. Hope this is not a repeat post.
I'm running WLS7 SP2 on W2K AS. I had SSL configured and working properly,
until
1/7/2004 came along, of course. I followed the directions in http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert/57436
to update the Verisign Class2 and 3 root certificates in the cacerts
file without
any problem. I also verified from the WL log that the server is reading
the "cacerts"
file located in <bea_home>\server\lib. However, when I pulled up my
website using
https://, I still get the "...security certificate has expired ..." message.
Why is my browser not getting the updated CA certificates from WLS?
Any help you can provide is much appreciated.
Michael An

CORBA error when looking up Home on WLS7sp2

Hi,
I've just upgraded to WLS7 sp2.
I get the following error when trying to access a session bean from a remote client
<exceptionStackTrace>
java.lang.ExceptionInInitializerError:
org.omg.CORBA.INITIALIZE: cannot instantiate
com.sun.corba.se.internal.javax.rmi.CORBA.Util
minor code: 0 completed: No
at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:303)
at javax.rmi.CORBA.Util.<clinit>(Util.java:48)
at javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:177)
at javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:56)
etc... (my app's classes here)
</exceptionStackTrace>
I use the default EJBC options when deploying my JAR.
Is this familiar to anyone?
Olivier

Found the bug.
My java client was called thru the <java> task in ANT.
Apparently this was causing a conflict.
I turned the "fork" property to "true" and now everything works
fine.
"Olivier" <[email protected]> wrote:
>
Hi,
I've just upgraded to WLS7 sp2.
I get the following error when trying to access a session bean from a
remote client
<exceptionStackTrace>
java.lang.ExceptionInInitializerError:
org.omg.CORBA.INITIALIZE: cannot instantiate
com.sun.corba.se.internal.javax.rmi.CORBA.Util
minor code: 0 completed: No
at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:303)
at javax.rmi.CORBA.Util.<clinit>(Util.java:48)
at javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:177)
at javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:56)
etc... (my app's classes here)
</exceptionStackTrace>
I use the default EJBC options when deploying my JAR.
Is this familiar to anyone?
Olivier

NullPointerException at WLS7.0 sp2 Startup with encripted Credential

I have a development cluster configured on a RedHat 7.3 Sun 1.3.x JVM. I can start
the cluster if I set the SecurityConfiguration Credential with cleartext. When
the cluster shuts down config.xml is rewritten, the Credential is encrypted.
The next time I attempt to start the cluster I get the following:
<Jul 3, 2003 10:44:49 AM MDT> <Notice> <Management> <140005> <Loading configuration
/home/doug/mycluster/dougscluster/./config.xml>
<Jul 3, 2003 10:44:52 AM MDT> <Critical> <WebLogicServer> <000364> <Server failed
during initialization. Exception:weblogic.management.configuration.ConfigurationException:
Error parsing the configuration file: null - with nested exception:
[java.lang.NullPointerException]
java.lang.NullPointerException
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.resolveMBeanAttributes(ConfigurationParser.java:871)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.endDocument(ConfigurationParser.java:339)
at weblogic.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1235)
at weblogic.apache.xerces.validators.common.XMLValidator.callEndDocument(XMLValidator.java:1159)
at weblogic.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatcher.dispatch(XMLDocumentScanner.java:1531)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:227)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: Error parsing the configuration
file: null - with nested exception:
[java.lang.NullPointerException]
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:243)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NullPointerException
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.resolveMBeanAttributes(ConfigurationParser.java:871)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.endDocument(ConfigurationParser.java:339)
at weblogic.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1235)
at weblogic.apache.xerces.validators.common.XMLValidator.callEndDocument(XMLValidator.java:1159)
at weblogic.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatcher.dispatch(XMLDocumentScanner.java:1531)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:227)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: Error parsing the configuration
file: null - with nested exception:
[java.lang.NullPointerException]
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:243)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
Reason: Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: Error parsing
the configuration file: null - with nested exception:
[java.lang.NullPointerException]
java.lang.NullPointerException
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.resolveMBeanAttributes(ConfigurationParser.java:871)
at weblogic.management.internal.xml.ConfigurationParser$ConfigurationHandler.endDocument(ConfigurationParser.java:339)
at weblogic.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1235)
at weblogic.apache.xerces.validators.common.XMLValidator.callEndDocument(XMLValidator.java:1159)
at weblogic.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatcher.dispatch(XMLDocumentScanner.java:1531)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:399)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:1138)
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:227)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: Error parsing the configuration
file: null - with nested exception:
[java.lang.NullPointerException]
at weblogic.management.internal.xml.ConfigurationParser.parse(ConfigurationParser.java:243)
at weblogic.management.internal.xml.XmlFileRepository.createOrLoadDomain(XmlFileRepository.java:483)
at weblogic.management.internal.xml.XmlFileRepository.bootStrapAndLoadActiveDomain(XmlFileRepository.java:354)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:217)
at weblogic.management.AdminServer.configureFromRepository(AdminServer.java:202)
at weblogic.management.AdminServer.configure(AdminServer.java:196)
at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:111)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
Any help is much appreciated

Hi Even i am getting the same issue, I upgarded the server from 7.0 sp1 to sp6. I have 6 managed instances running on 2 boxes. But i am facing this problem with only one managed instance. This problem i am facing when i start the 2nd instance of the managed instance where my Webservice component is running.

Using log4j with WLS7.0 SP2

Hello,
I'm trying to start using log4j. It seems to work fine initially after the
server starts up. But if I make a modification to any of the logged classes
and recompile them, log4j errors out saying it cannot find an appender for
the category specified. log4j.jar is in the classpath of the WLS startup
script. Has anyone come across this problem? I'm not quite sure what the
source of problem is. And it is not really productive to restart the server
every time anything changes in one class...any insight is appreciated!
Thank you,
Makoto

Oops. I solved my own problem. I turned off "Prefer WEB-INF classes" in the
console and the problem went away.
mk.
"Makoto Suzuki" <[email protected]> wrote in message
news:3f034462$[email protected]..
Hello,
I'm trying to start using log4j. It seems to work fine initially after the
server starts up. But if I make a modification to any of the loggedclasses
and recompile them, log4j errors out saying it cannot find an appender for
the category specified. log4j.jar is in the classpath of the WLS startup
script. Has anyone come across this problem? I'm not quite sure what the
source of problem is. And it is not really productive to restart theserver
every time anything changes in one class...any insight is appreciated!
Thank you,
Makoto

"HowTo" Call EJB from different EAR in WLS7

Hi,
Im trying to deploy two EAR application modules, both on same WLS7.0 SP2 server
. I have several problems to give visibility between EAR applications. There is
dependences between both applications ( I will call them FirstEAR and SecondEAR)
. A FirstEAR EJB ( FirstEAREJB) uses an EJB from the SecondEAR ( SecondEAREJB
The deployment result is a "Unable to initialize method info for remote or home
interface The error is java.lang.NoClassDefFoundError: myPackage.myPackage.SECONDEAREJB"
when deploy the FirstEAREJB. I try the deployment of both using -iiop ejbc option.
Which is the way to allow my FirstEAREJB to use SECONDEAREJB?
I have try
- to set the manifest Class-Path property for FirstEAREJB with no results.
- to set the descriptor ejb-jar properties for EJBRefs with no results.
- to set the SecondEAREJB path in the weblogic start script classpath, with no
results.
- to set the SecondEAR classpath at the ejbc -cp option for FirstEAREJB ejbc
compile, with no results again.
Is there another way to allow my FirstEAREJB to use SecondEAREJB ?

Take a look at this documentation on WebLogic Server Application
Classloading.
It might be helpful.
http://edocs.bea.com/wls/docs70/programming/classloading.html
/k
"Adolfo Cortés" <[email protected]> wrote in message
news:[email protected]..
>
Hi,
Im trying to deploy two EAR application modules, both on same WLS7.0 SP2server
I have several problems to give visibility between EAR applications.There is
dependences between both applications ( I will call them FirstEAR andSecondEAR)
A FirstEAR EJB ( FirstEAREJB) uses an EJB from the SecondEAR (SecondEAREJB
The deployment result is a "Unable to initialize method info for remote orhome
interface The error is java.lang.NoClassDefFoundError:myPackage.myPackage.SECONDEAREJB"
when deploy the FirstEAREJB. I try the deployment of both using -iiop ejbcoption.
>
Which is the way to allow my FirstEAREJB to use SECONDEAREJB?
I have try
- to set the manifest Class-Path property for FirstEAREJB with noresults.
- to set the descriptor ejb-jar properties for EJBRefs with no results.
- to set the SecondEAREJB path in the weblogic start script classpath,with no
results.
- to set the SecondEAR classpath at the ejbc -cp option for FirstEAREJBejbc
compile, with no results again.
Is there another way to allow my FirstEAREJB to use SecondEAREJB ?

Weblogic 6.0 sp2: War deployment not working !!

Hi,
I'm using weblogic 6.0 sp2, and it seems as though the war deployment is not
working. My war consists of jsps, images, and under the WEB-INF/classes
directory, Struts classes (i.e. Form and Action classes). When I try to run
a jsp, i get the following error :
<Jul 30, 2001 11:48:10 AM PDT> <Error> <HTTP>
<[WebAppServletContext(4655498,ati
nera)] Root cause of ServletException
javax.servlet.jsp.JspException: Exception creating bean of class
com.atinera.log
in.web.LoginForm: java.lang.ClassNotFoundException:
com.atinera.login.web.LoginF
orm
But if you look in the war, that class is in there.
What gives ?
Thanks,
Jamie

That's right - ActionServlet does Class.forName(actionClass) to load action
class, and this uses ClassLoader which loaded the current class (ActionServlet)
ClassLoaders always delegate to their parent before attempting to load
the class themselves, so it wasn't working until you moved struts.jar to your
WEB-INF/lib.
BTW, Struts doc mentions this problem:
lib/struts.jar - This JAR file contains all of the Java classes included
in Struts. It should be copied into the WEB-INF/lib directory of your web
application. WARNING - If you are going to be hosting multiple Struts based
applications on the same servlet container, you will be tempted to place the
struts.jar file into the shared repository supported by your container. Be
advised that this will like cause you to encounter ClassNotFoundException
problems unless all of your application classes are stored in the shared
repository.
Jamie Tsao <[email protected]> wrote:
So I found the solution to this problem, but it doesn't really make sense to
me.
I originally had struts.jar outside of the WAR file, but in my CLASSPATH.
Weblogic was able to load Strut's ActionServlet (controller), but when the
ActionServlet was looking for the LoginForm (which was inside the WAR), it
couldn't find it.
I solved the problem by putting struts.jar inside the WAR (under
WEB-INF/lib) instead that other directory. Now it works cause apparently
ActionServlet is now in the same classloader as LoginForm, the classloader
which loaded the WAR.
I'm confused because original way should have worked since the classloader
that loaded struts.jar from outside the war is the parent classloader for
the classloader that loaded the WAR. did that make any sense ?
anyone know why ?
thanks,
jamie
"Jamie Tsao" <[email protected]> wrote in message
news:[email protected]...
Hi,
I'm using weblogic 6.0 sp2, and it seems as though the war deployment isnot
working. My war consists of jsps, images, and under the WEB-INF/classes
directory, Struts classes (i.e. Form and Action classes). When I try torun
a jsp, i get the following error :
<Jul 30, 2001 11:48:10 AM PDT> <Error> <HTTP>
<[WebAppServletContext(4655498,ati
nera)] Root cause of ServletException
javax.servlet.jsp.JspException: Exception creating bean of class
com.atinera.log
in.web.LoginForm: java.lang.ClassNotFoundException:
com.atinera.login.web.LoginF
orm
But if you look in the war, that class is in there.
What gives ?
Thanks,
Jamie
Dimitri

Installing SQL Server 2012 Developer Edition or wait for SP2?

Hi everyone,
I just received my copy of SQL Server 2012 Developer Edition I ordered. As usual, before installing, I searched the web for any hint or other stuff on the subject.
I first found that SP1 was already available. Honestly I prefer installing using the last version available instead of upgrading. I found the SP1 install package using the following web address:
http://www.microsoft.com/fr-ca/download/details.aspx?id=35575
Is this the right install package to use?
Now, still reading everything I could find on that SP1, I found stories about major issues with SP1.
Two examples I remember:
http://connect.microsoft.com/SQLServer/feedback/details/770630
http://support.microsoft.com/kb/2793634/en-us?wa=wsignin1.0
Two others (not specifically related to SP1):
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/a0da3372-ab3d-4af0-b4c4-0d47163e0e03/
http://www.sqlperformance.com/2012/11/system-configuration/2012-cal-problems
My question. Should I wait for SP2? If so, any target date when it should be available?
If not, what would you recommend as the logic install sequence? Should I look for any cumulative update(s)? Any other "manual settings" I should consider?
Finally, can someone guide me regarding what options I should choose while installing. My main goal is to program/build C++, C# applications using VS2010 that will interface with SQL Server for data storage purposes (add/update/delete,
batch update/delete) and reports.
Hope to hear from someone.
Stephane
BTW: My current setup is the following:
Intel(R) Core(TM)2 CPU [email protected]
3.00 Go
Vista Ultimate SP2 32bits
Visual Studio 2010 Professional Edition (which will be upgraded to last SP once installed)

Hi again,
I proceeded with download of CU7. On Microsoft's webpage, there are several files we can download:
2012_SP1_DAC_CU7_2894115_11_0_3393_x86
2012_SP1_AOrcleDes_CU7_2894115_11_0_3393_x86
2012_SP1_AOrcleSer_CU7_2894115_11_0_3393_x86
2012_SP1_PPExcel_CU7_2894115_11_0_3393_x86
SQLServer2012_SP1_CU7_2894115_11_0_3393_x86
Which one I should choose?
Also, some people reported having problems installing this update.
http://blogs.msdn.com/b/sqlreleaseservices/archive/2013/11/19/cumulative-update-7-for-sql-server-2012-sp1.aspx
Can you comment?
Thanks again for helping,
Stéphane

Crystal Reports Runtime 13 not found in sequence on App-V 5.0 SP2 Hotfix 5 client

My application uses a VFS installation of Crystal Reports Runtime 13. (i.e., the path to CR13 isn't specified as the Primary directory during sequencing, as my app uses that particular path)
On a test VM with an old App-V client (5.0.285.0) the application launches and can locate CR components successfully.
However, when we upgrade to the latest App-V client (SP2 HF5) the application fails to find CR.
The original application was sequenced with App-V 5.0 RTM (5.0.285.0). I've re-sequenced the app with the latest sequencer (SP2 HF4) but the error persists.
There is literally nothing in the Event Log and the app doesn't appear to report the error to Windows (it pops up a UI message saying CR 13 can't be located).
Procmon doesn't show anything meaningful, although I could have missed something whilst trawling through 16,000 lines of processes.
I enabled all App-V logs and nothing relating to an error can be found there.
I tried disabling DEP and following other advice in this earlier thread:
virtualizing-business-objects-crystal-reports-pro-110
OS: Windows 7 SP1, patched up to date.
App-V client: 5.0.3404 (SP2 Hotfix 5)
Anyone seen an issue like this?
I'm about to open a case with Microsoft Support, just thought I'd ask here first.
Regards.

Hi.
We raised a support ticket with Microsoft and with their help, found that the path length to the VFS installation of Crystal Reports was the issue.
I created an MST (btw, Crystal Reports MSI has numerous directory and registry entries that don't use best practice, so this took a while..) to reduce the path lengths.
As to why the RTM version of the client works (from our Microsoft support engineer):
"Regarding the “why”, between RTM and the next versions, lots of issues were corrected.
In this particular situation, the issue was related with the fact that the application stopped extending the buffer. Probably what happened was that a COM or Object Bug was corrected between RTM and SP2 and this had a negative effect on the application. What
this means is that, in fact, the application was not supposed to work in RTM as well, due to buffer being extended."
So in summary, if you have an application with a particularly long path structure, you may need to re-sequence for the SP2 version of the client.

Classloading func evolution btw WLS7 SP2 et WL7SP3

Similar Messages

Maybe you are looking for