Weblogic.jws.Policies.class is missing in weblogic.jar and wlfullclient.jar

Hi,
I am trying to upgrade Weblogic from 9.1 to 10.3.2 or 10.3.3
In Weblogic 9.1, our application used weblogic.jar in our classpath.
After we installed Weblogic 10.3.3, the new weblogic.jar can be found in: <WLS_HOME>\wlserver_10.3\server\lib
However, some class files are missing and we realized we need to manually generate wlfullclient.jar and use this jar file instead.
Reference: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/client/jarbuilder.html
The problem is that in Weblogic 10.3.3, the following class files are missing inside weblogic.jar and wlfullclient.jar
- import weblogic.jws.Policies
- import weblogic.jws.Policy
Hence, our application is getting an "The import weblogic.jws.Policies cannot be resolved" error in our code.
I look inside both weblogic.jar and wlfullclient.jar, weblogic.jws.Policies and weblogic.jws.Policy cannot be found.
This is not an issue in Weblogic 10.3.2. These two classes can be found in wlfullclient.jar
Any idea where I can find these class files for Weblogic 10.3.3 or something we are doing is incorrectly?
Thanks
Toan

Hi,
This missing classes can be found inside the JAR : *"E:\bea10_3_3\wlserver_10.3\server\lib\wseeclient.jar"* As well as inside *"E:\bea10_3_3\wlserver_10.3\server\lib\wls-api.jar"*
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic/webservices/ (WebLogic Wonders Are Here)

Similar Messages

Can anyone tell me which jar contain weblogic.jws.WLJmsTransport class

Hi All,
Can anyone tell me which jar contain weblogic.jws.WLJmsTransport class
Thanks in advance?

Hi,
You can find that in the "*weblogic.jar*", "*wls-api.jar*" and "*wseeclient.jar*" which can be found in the below directory
Path:
wlserver_10.3/server/lib/
Also you can have a look at the below link which shows you how to find any CLASS present inside your file system.
Topic: Finding Classes using JAR SCANNER
http://middlewaremagic.com/weblogic/?page_id=241#comment-3621
Regards,
Ravish Mody

How to use both ojdbc14.jar and ojdbc6.jar in same weblogic domain(weblogic12C)

Hi all,
I 'm having issue of using both ojdbc14.jar and ojdbc6.jar in same weblogic application and same weblogic domain in weblogic 12C environment.
how can i do that?
i'm currently having application developed using jdk 1.6 and ojdbc6.jar, application developed using jdk 1.4 and ojdbc14.jar.both are currently installed at same domain.
i want to use the both ojdbc14.jar and ojdbc6.jar in same domain.
what i previously did was renaming /usr/weblogic/wls_server10.3.4/lib/ojdbc6.jar to /usr/weblogic/wls_server10.3.4/lib/ojdbc6.jar.bak and put ojdbc14.jar in the same path when i wanna use ojdbc14.jar.
i haven't use both in same environment before, but to go live i wanna match about requirement.pls help.
i know the way use this by having two domains, but in the same domain i could not find a solution yet.
Please help

Hey
I have the similar requirement.. Did you managed to get an option of doing it? If yes, please provide some insights
Thanks in Advance

Where to download wlst.jar and python.jar for weblogic 10

where to download wlst.jar and python.jar for weblogic 10 ? I am unable to find the links ..most of the prevoius ones point to dev2dev which are no longer valid

Hi,
I have written the below python script to list the user ,that was created in realms->myrealms->users.
It's not working it.
Kindly help to in this python script.
from weblogic.management.security.authentication import UserReaderMBean
from weblogic.management.security.authentication import GroupReaderMBean
file_loc='MbeanValues.properties'
file=java.io.File(file_loc)
if file.exists():
loadProperties(file_loc)
connect(dwlusr,dwlspwd,dwlsurl)
domain_name = cmo.getName()
print 'UserName='+dwlusr
print 'URL='+dwlsurl
print 'DomainName='+ domain_name
print 'welcome'
print 'Checking if isMember of a group'realm=cmo.getSecurityConfiguration().getDefaultRealm()
atns = realm.getAuthenticationProviders()
for i in atns:
if isinstance(i,UserReaderMBean):
userReader = i cursor = i.listUsers("*",0)
print 'Users in realm '+realm.getName()+' are: '
while userReader.haveCurrent(cursor):
print userReader.getCurrentName(cursor)
userReader.advance(cursor)
userReader.close(cursor)for i in atns:
if isinstance(i,GroupReaderMBean):
groupReader = i
cursor = i.listGroups("*",0)
print 'Groups in realm are: '
while groupReader.haveCurrent(cursor):
print groupReader.getCurrentName(cursor)
groupReader.advance(cursor)
groupReader.close(cursor)
disconnect()

Com.sap.portal.runtime.logon_api.jar and umelogonbase.jar missing

Hi All,
I am trying to customize the portal login page . and i got the steps how to do it. But when i import the par file com.sap.portal.runtime.logon.par into NWDS , i could not find com.sap.portal.runtime.logon_api.jar and umelogonbase.jar jar files under dist\PORTAL-INF\lib . These files are missing.
Where could i retreive these files . I checked all the other subfolders i am unable to find these files.
Can anyone please guide me
That would be great.
Thanks
Sowmya

Hello,
Can u tell me how to import that .par file in nwds ,
mean i want to know the procedure
1)which project is to pe created in Nwds
2)how and wher to import that .jar file
3) in some sap blocks i read that convert that .par file to zip n then extract it is this really to be done
Would really appreciate your reply!!
Thanks In advance!

Files missing in the ear and client jar

Hi,
I'm following the examples to build a web service using ANT servicegen task. My
web service calls a lot of other java classes, and those java classes in turn
call other classes. When I used the following taskes to generate the service and
client code, I found the generated ear, war and client jar files only contain
the compiled classes which are used directly by the web service class. Those classes
called indirectly by web service are missing.
<target name="ear">
<servicegen
destEar="${build}/${ear_file}"
warName="${war_file}">
<service
javaClassComponents="com.iit.integration.txlife.txlife28.txlifeProcessor.TxlifeProcessor"
targetNamespace="${namespace}"
serviceName="TxlifeWebService"
serviceURI="/txlifews"
generateTypes="True"
expandMethods="True">
<client
packageName="com.iit.integration.txlife.txlife28.client"
clientJarName="${client_jar_file}"
/>
</service>
<classpath>
<pathelement path="${build}"/>
<pathelement path="${java.class.path}"/>
</classpath>
</servicegen>
</target>

<target name="client" depends="ear">
<clientgen
ear="${build}/${ear_file}"
warName="${war_file}"
packageName="com.iit.integration.txlife.txlife28.client"
clientJar="${client}/${client_jar_file}">
<classpath>
<pathelement path="${build}"/>
<pathelement path="${java.class.path}"/>
</classpath>
</clientgen>
So when I invoked the client code, I always got the class not found exception.
Not sure if I missed anything here.
Thanks a lot,
Henry
[build.xml]

Any required support classes have to be in the client's/server's classpath. Or
at least that's what I do.
"Henry Niu" <[email protected]> wrote:
>
>
>
Hi,
I'm following the examples to build a web service using ANT servicegen
task. My
web service calls a lot of other java classes, and those java classes
in turn
call other classes. When I used the following taskes to generate the
service and
client code, I found the generated ear, war and client jar files only
contain
the compiled classes which are used directly by the web service class.
Those classes
called indirectly by web service are missing.
<target name="ear">
<servicegen
destEar="${build}/${ear_file}"
warName="${war_file}">
<service
javaClassComponents="com.iit.integration.txlife.txlife28.txlifeProcessor.TxlifeProcessor"
targetNamespace="${namespace}"
serviceName="TxlifeWebService"
serviceURI="/txlifews"
generateTypes="True"
expandMethods="True">
<client
packageName="com.iit.integration.txlife.txlife28.client"
clientJarName="${client_jar_file}"
/>
</service>
<classpath>
<pathelement path="${build}"/>
<pathelement path="${java.class.path}"/>
</classpath>
</servicegen>
</target>

<target name="client" depends="ear">
<clientgen
ear="${build}/${ear_file}"
warName="${war_file}"
packageName="com.iit.integration.txlife.txlife28.client"
clientJar="${client}/${client_jar_file}">
<classpath>
<pathelement path="${build}"/>
<pathelement path="${java.class.path}"/>
</classpath>
</clientgen>
So when I invoked the client code, I always got the class not found exception.
Not sure if I missed anything here.
Thanks a lot,
Henry

How will be the weblogic-ejb-jar and ejb-jar xml for EJB Local Interface?

Hi,
I have one ear application which is using Stateless Session Beans. I don't have any Bean to Bean communication . At present, the client is invoking remote methods thro Home/Remote interfaces. My doubt is , shall I implement EJBLocal home/ local interface to obtain this same functionality cos, in this app, both client and EJb bean have been deployed in same JVM. Can Local interfaces only be applicable to Bean - Bean relation ship?If LocalHome/Local interfaces can be implemented in my scenario, then may I know how will be the ejb-jar.xml and weblogic-ejb-jar.xml?
thanks and regards,
Venkat.

Local interfaces are for communication between ejbs and their clients when both are in the same JVM. The clients can be normal clients, jsps, servlets, and other ejbs. If the client is not in the same JVM you cannot use local interfaces even though your client is another ejb.
Advantage of using local interface is it reduces the network overhead.
For more information you can download Mastering Enterprise Java Beans Third Edition by Ed Roman. You can go through 45
You can download pdf version from.
http://www.theserverside.com/books/wiley/masteringEJB/index.tss.
Let me know the URL of the ejb doc that you referred.
Thanks..

'java.lang.ClassNotFoundException: weblogic.jws.jaxws.client.async.AsyncTransportProvider'

When ı try to set up my project to other computer , my project takes error on build.
I m using eclipse Juno .I looked my weblogic.jar i didn't find weblogic.jws.jaxws.client.async.AsyncTransportProvider
class in it. What should i do ?
Stacktrace :
<Feb 14, 2014 2:28:30 PM PKT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1392370100493' for task '0'. Error is: 'java.lang.ClassNotFoundException: weblogic.jws.jaxws.client.async.AsyncTransportProvider'
java.lang.ClassNotFoundException: weblogic.jws.jaxws.client.async.AsyncTransportProvider
       at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
       at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
       at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
       Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: weblogic.jws.jaxws.client.async.AsyncTransportProvider
       at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
       at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
       at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
       Truncated. see log file for complete stacktrace
>
<Feb 14, 2014 2:28:30 PM PKT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating distribute task for application '_auto_generated_ear_'.>
<Feb 14, 2014 2:28:30 PM PKT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
java.lang.ClassNotFoundException: weblogic.jws.jaxws.client.async.AsyncTransportProvider
       at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
       at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
       at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
       Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: weblogic.jws.jaxws.client.async.AsyncTransportProvider
       at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
       at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
       at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
       Truncated. see log file for complete stacktrace
>

Is OEPE (Oracle Enterprise Pack for Eclipse) used?

Missing weblogic.security.spi. classes

Any idea what happened to these classes? Can't find the right jar file.
import weblogic.security.spi.AuthenticationProvider;
import weblogic.security.spi.IdentityAsserter;
import weblogic.security.spi.PrincipalValidator;
import weblogic.security.spi.SecurityServices;
import netscape.ldap.LDAPAttribute;
import netscape.ldap.LDAPEntry;
import netscape.ldap.LDAPException;
import netscape.ldap.LDAPSearchResults;
import netscape.ldap.LDAPv2

Glad, your issue is resolved. Also in case if you are using WLS 10.3.x, here is the link on how to generate a client jar file that has almost all the APIs from weblogic.jar and wls-api.jar etc etc. Most of the times, when we want to run WebServices, EJB clients etc as standalone, we need all these classes. So here is the link on how to generate something called "wlfullclient.jar" and put that in classpath or java build path etc.
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/client/jarbuilder.html (To create wlfullclient.jar)
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/client/t3.html
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/client/basics.html#wp1069994
HTH
Ravi Jegga

Class Loader Hierarchy in Weblogic 7.0

I have read the BEA documentation on the class loader hierarchy in Weblogic Server,
and I have some questions regarding some behavior I am seeing.
I am running Weblogic Server 7.0.
I have an ear file that contains 3 web apps (wars) and several utility jars. The
web apps' manifests contain the Class-Path entry for the utility jars. My understanding
of this is that each web app SHOULD have its own class loader. Also, the utility
jars will be scoped in a separate class loader and WILL NOT have visibility to
the web app classes. The web app classes should have visibility to the utility
jars.
Is this correct????
I added a static segment of code in each web app and printed the class loader
for each servlet when it was loaded. I also printed the class loader from a class
that is DEFINITELY contained in one of the utility jars. Here is the result:
Utility Class ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04 Utility Class
Parent ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
Servlet 1 ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04 Servlet 1 Parent
ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
Servlet 2 ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04 Servlet 2 Parent
ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
I'm a little confused.... I expected to see 3 different class loaders (i.e. one
for each class above). I believe the above printout says that all 3 classes are
being loaded by the SAME class loader instance (Launcher$AppClassLoader@b9d04).
Am I interpreting this correctly? If so, what's going on?

I rechecked the classpath for the user that starts Weblogic, and in the classpath
I found the project "src" directory (must have missed it earlier). When we did
our build, the classes are placed in the src structure then copied to the build
area. That's the reason I was not seeing the appropriate class loader hierarchy.
Thanks for all of the comments.
"Sanjeev Chopra" <[email protected]> wrote:
>
"Mark Cotherman" <[email protected]> wrote in message
news:[email protected]...
Thanks for your comments again Mark. I'm just trying to get a goodhandle
on how
this is working.
I'll assume that somehow my web app classes are being loaded into theroot
classloader.
The next question is... why??Just to be sure - is there any way these classes are sneaking into the
system classpath ?
My ear file contains the following:
a.war
b.war
c.war
lib/util1.jar
lib/util2.jar
lib/util3.jar
lib/util4.jar
The manifest in all three wars reference all util jars. This ear deployssuccessfully
on Weblogic with no errors.
How could these separate servlets (one in each war) not have seperateclass loaders
seperate from the root where the utils should reside. I don't thinkthat
I have
any control over where Weblogic loads the war classes, or do I?
See comments below....
Mark Spotswood <[email protected]> wrote:
Mark Cotherman wrote:
Thanks for the follow-up.
I want to make sure I follow what you are saying. All classes in
the
manifest
Class-Path of WARs are exported to the parent classloader.That's right.
To me this is the correct behavior since the manifest Class-Path
is
meant to provide
a way to share common utility classes among several web apps. AllEJB jars and
manifest Class-Path entries should be loaded by the same class loader.Its a way to share class definitions, but not necessarilly class
instances. I don't think that a web application should be extending
the classpath of its parent's classloader. This leads to namespace
problems as well as reloadability issues.
Ok, you lost me here. Shouldn't delegation handle the namespacecollisions??
If the web app class loader has a class definition (webapp:com.xyz.ClassA) with
exactly the same name in the same package as the root class loader(rootloader:
com.xyz.ClassA), I thought the web app would use (delegate loading)the
class
definition from the root class loader when PreferWebInf is set to false.
Isn't this why the PreferWebInf attribute, when set to true, can causeClassCastExceptions??
The web app when creating an instance of (webapp: com.xyz.ClassA)from
the web
app class loader can potentially pass a reference to this instanceto a
class
instance loaded from the root loader. The root class loader has adifferent class
definition for ClassA.
REALLY what makes since is that all common jar files be defined
in
the manifest
Class-Path OF THE ear FILE (if the WAR(s) are in an ear). These
jar
files should
then be loaded by the same class loader as the EJB jars. There shouldbe no need
for the WARs to have any reference to the utility jars since the
EJB
class loader
is the parent of the WAR class loaders.The ear file doesn't have a manifest classpath, but what you are getting
at makes sense. If you add a manifest to any EJBs in your app, theall
webapps (as well as all other EJBs) will be able to see it, sincewith
our structure, EJBs are loaded into the application's root classloader.
My problem is that the ACTUAL SERVLET classes are NOT being loadedby a separate
class loader from the EJB and common jar class loader. This is
completely
against
what is being said in the Weblogic documentation. The Manifest
Class-Path
should
have nothing to do with where the classes that reside in
WEB-INF/classes
of my
servlet are loaded.Classloaders will ask their parent for the class first before loading
it
themselves. So if the parent classloader somehow has visibility to
classes that your webpapp references, then it will get loaded by the
parent classloader.
I am in the middle of migrating an app from an older version of
Weblogic,
and
it would be helpful to have the ACTUAL class loading hierarchy welldocumented.
The basic hierarchy is all EJBs are in a root shared classloader and
each web application is loaded by a classloader that is a child of
that root.
Again, am I missing something here???My suspicion is that somehow these servlets are in the classpath ofthe
root classloader, so when the webapp classloaders delegate to thatone,
it will come up with the class.
mark
Mark Spotswood <[email protected]> wrote:
I believe what you are seeing is a bug in the servlet container.
The classloader organization is what you expect, but each webapp
is exporting the classpath information from its manifest to the
classloader above its classloader (which is common to all
three webapps) rather than to its own classloader. So because
of the delegation that happens with classloading, the common
parent classloader is the one that loads the class.
I believe that this behavior exists as an attempt to avoid
ClassCastExceptions, but I don't think that it is the right
solution to this problem. In our 8.1 release, this behavior
has been changed. That is, web applications no longer export
manifest classpath information to the parent of their classloader.
This change has not been ported back to the 7.x line, but a bug
report has been created (CR099889). You should be able to follow
up with support with this CR number.
mark
Mark Cotherman wrote:
I have read the BEA documentation on the class loader hierarchy
in
Weblogic Server,
and I have some questions regarding some behavior I am seeing.
I am running Weblogic Server 7.0.
I have an ear file that contains 3 web apps (wars) and several
utility
jars. The
web apps' manifests contain the Class-Path entry for the utility
jars.
My understanding
of this is that each web app SHOULD have its own class loader.
Also,
the utility
jars will be scoped in a separate class loader and WILL NOT have
visibility
to
the web app classes. The web app classes should have visibility
to
the utility
jars.
Is this correct????
I added a static segment of code in each web app and printed the
class
loader
for each servlet when it was loaded. I also printed the class loaderfrom a class
that is DEFINITELY contained in one of the utility jars. Here is
the
result:
Utility Class ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04
Utility
Class
Parent ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
Servlet 1 ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04 Servlet1 Parent
ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
Servlet 2 ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04 Servlet2 Parent
ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
I'm a little confused.... I expected to see 3 different class loaders(i.e. one
for each class above). I believe the above printout says that all
3
classes are
being loaded by the SAME class loader instance
(Launcher$AppClassLoader@b9d04).
Am I interpreting this correctly? If so, what's going on?

WS Client:ClassNotFoundException: weblogic.jws.jaxws.AggregatePolicyFeature

Dear Java Experts,
I have made a web service client and managed successfully compile it on AIX after a lot of effort. I have used jsxws 2.1.7 to generate the class files from wsdl and then made a client using those classes.
When I run it, I am getting a weblogic.jws.jaxws.AggregatePolicyFeature exception. Problem is, I have no link with Web Logic either on Web Service side or on its client side. I am puzzled why I am getting this web logic exception.
Would you please help in resolving this issue. Thanks. Ahsan
Exception trace pasted below:
====================================
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic.jws.jaxws.AggregatePolicyFeature
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:69)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:131)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1328)
at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:36)
at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:95)
at javax.xml.ws.spi.Provider.provider(Provider.java:83)
at javax.xml.ws.Service.<init>(Service.java:56)
at complaintrectification.ComplaintRectification_Service.<init>(ComplaintRectification_Service.java:46)
at ibmclientcr.IBMClientCRwithMain.complaintRectification(IBMClientCRwithMain.java:66)
at ibmclientcr.IBMClientCRwithMain.main(IBMClientCRwithMain.java:34)
Caused by: java.lang.ClassNotFoundException: weblogic.jws.jaxws.AggregatePolicyFeature
at java.net.URLClassLoader.findClass(URLClassLoader.java:497)
at java.lang.ClassLoader.loadClass(ClassLoader.java:640)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:606)
... 12 more
====================================

weblogic.jws.jaxws.AggregatePolicyFeature class should be present in ws.api_1.1.0.0.jar, add this jar in the classpath for resolving the issue.

URG! problem with wls 9.2. DynamicMBeanImpl Class no exists in weblogic.jar

Hi all,
I have a problem instalating in startupclass and shutdownclass to uses jolt connections.
Theses classes are PoolManagerStartUp and PoolManagerShutdown.
it looks like the problem is in the joltwls.jar library (it contains the classes previously mentioned, bea.jolt.pool.servlet.weblogic.PoolManagerStartUp and bea.jolt.pool.servlet.weblogic.PoolManagerShutdown)
These classes uses a method that is in weblogic.jar version 7.0 but not in weblogic.jar version 9.2.
the class that hasn´t been found is weblogic/management/internal/DynamicMBeanImpl
this is the log :
<Dec 20, 2008 6:29:27 PM CET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NoClassDefFoundError: weblogic/management/internal/DynamicMBeanImpl
java.lang.NoClassDefFoundError: weblogic/management/internal/DynamicMBeanImpl
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:246)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:253)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:205)
Truncated. see log file for complete stacktrace
thanks in advance!!
Edited by: user5481292 on 20-dic-2008 10:21
Edited by: user5481292 on 20-dic-2008 10:37

Hi,
This missing classes can be found inside the JAR : *"E:\bea10_3_3\wlserver_10.3\server\lib\wseeclient.jar"* As well as inside *"E:\bea10_3_3\wlserver_10.3\server\lib\wls-api.jar"*
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic/webservices/ (WebLogic Wonders Are Here)

Calling a java class in JSP in Weblogic 5.1

Hi
I am trying to call a java class in a jsp page. But it is giving an error:
Compilation of 'C:\weblogic\myserver\classfiles\jsp_servlet\_knet\_buy.java' failed:
C:\weblogic\myserver\classfiles\jsp_servlet\_knet\_buy.java:79: cannot access jsp_servlet._knet.e24PaymentPipe
probably occurred due to an error in /knet/buy.jsp line 25:
e24PaymentPipe pipe = new e24PaymentPipe();
Is this a problem bcos of the wrong path of the class file which i am calling?
Please help this is urgent

Hello All
As I tried to deploy the easiest project (dummy.war) on WebLogic 8.1.5, There is only one class (without package) Login.class
*********** Listing of the dummy WAR ***********
META-INF/
META-INF/MANIFEST.MF
WEB-INF/
WEB-INF/classes/
WEB-INF/classes/Login.class
WEB-INF/web.xml
index.jsp
login.jsp
************ Output of deployment from Admin Console****************
Log:
A log of the task's activities.
[Deployer:149033]preparing application dummy on intranetAdmin
[Deployer:149033]prepared application dummy on intranetAdmin
[Deployer:149033]activating application dummy on intranetAdmin
[Deployer:149033]failed application dummy on intranetAdmin
[Deployer:149034]An exception occurred for task [Deployer:149026]
Deploy application dummy on intranetAdmin.:
Exception:weblogic.management.ApplicationException: start() failed.
Module: dummy Error: weblogic.management.DeploymentException:
[HTTP:101216]Servlet: "index" failed to preload on startup in Web application:
" dummy ".
weblogic.servlet.jsp.CompilationException: Compilation of D:\apps\wlsapp\
INTRAN~1\.\intranetAdmin\.wlnotdelete\extract\intranetAdmin_ dummy _ dummy
\jsp_servlet\__index.java failed.
D:\apps\wlsapp\INTRAN~1\.\intranetAdmin\.wlnotdelete\extract\
intranetAdmin_dummy_dummy\jsp_servlet\__index.java:22: '.' expected
import Login; //[ /login.jsp; Line: 8]
^
1 error
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:478)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:246)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:196)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.
java:3430)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.
java:3387)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext
.java:3373)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3356)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:
6208)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:864)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2134)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2175)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.
activateContainer(SlaveDeployer.java:2520)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer
.java:2438)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2155)
at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2254)
at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2149)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.
java:2401)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:
883)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: java.io.IOException: Compiler failed executable.exec
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:470)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:321)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:451)
... 22 more
- with nested exception:
[java.io.IOException: Compiler failed executable.exec]
I put this class into a dummy package named sample, changed package declaration within this class and changed import statement within jsp pages like this :
<%@ page import="sample.Login " %>
<jsp:useBean id="logUsr" scope="session" class="sample.Login" />
When I did like this, everything is ok. No more exception.
If my application has so many java classes under WEB-INF/classes/ without creating package, it may be so inconvenience.
Please kindly let me know why this exception (class not found exception) occurred.
And what is the solution? I cannot deploy the application successfully yet.
many thanks,
Zin Ko Win

(Help) system classpath -Vs- the place where weblogic looks for classes

The following is my app's hierarchy.
myapp
|
|__myjsp.jsp
|
|__WEB-INF
|
|__classes
|_ MyClass.class
I am not able to use MyClass within myjsp.jsp
i.e. a scriplet like that shown below gives an error stating that MyClass isnt found
<% MyClass obj; %>
I've tried setting the system classpath, but to no avail.
Is there a difference between the system classpath and the place where weblogic looks for classes?
(I am running my app by creating a myapp.war file and placing it in autodeploy folder)

Try moving your class to a named package and use the appropriate import statement in your JSP. Loading it from WEB-INF/classes/packagename should be fine so you might want to remove the other classpath mods you made to eliminate that uncertainty.
Here's a snippet from http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rweb_jsp_migration.html:
"As of JSP 2.0, referring to any classes from the unnamed or default package is not allowed. This can result in a translation error on some containers, specifically those that run in a JDK 1.4 or greater environment which will also break compatibility with some older JSP applications. However, as of JDK 1.4, importing classes from the unnamed package is not valid. See Java 2 Platform, Standard Edition Version 1.4.2 Compatibility with Previous Releases for details. Therefore, for forwards compatibility, applications must not rely on the unnamed package. This restriction also applies for all other cases where classes are referenced, such as when specifying the class name for a tag in a Tag Library Descriptor (TLD) file."
HTH,
Mike
Weblogic/J2EE Security Blog: http://monduke.com

WebLogic looking for class file using the wrong case

During my ant build, I precompile my JSPs using weblogic.jspc. All of the jars and wars are packaged into an ear and deployed to WebLogic 8.1 on Linux. When I access one of our normal screens, everything is good. Things go wrong when I try to access one of our help screens. We have a base help file that includes another file based on the screen code passed to it. The screen code is used in combination with a HashMap to look up the correct JSP to include. This part goes fine. But when the JSP is included, I get the following error. The best I can figure is that the class file is in mixed case (i.e., SampleHelp00.jsp and SampleHelp00.class), but Weblogic is looking for samplehelp00.class.
I'm not even where I should begin looking to solve this. Anyone have any ideas?
----- BEGIN STACKTRACE -----
javax.servlet.jsp.JspException:
[HTTP:101249][ServletContext(id=70634941,name=grp,context-path=/grp)]:
Servlet class jsp_servlet._help.__samplehelp00 for servlet
/help/SampleHelp00.jsp could not be loaded because the requested class was not found in the classpath
/usr/share/weblogic/weblogic81/config/wftesttest/webSysServer02/.wlnotdelete/extract/webSysServer02_wf-web-sys.wftesttest_grp/wf-web-sys.wftesttest.war:
/weblogic81sp5/weblogic81sp5/config/wftesttest/webSysServer02/.wlnotdelete/extract/webSysServer02_wf-web-sys.wftesttest_grp/jarfiles/WEB-INF/lib/Struts_Validator-20010702.jar:
/weblogic81sp5/weblogic81sp5/config/wftesttest/webSysServer02/.wlnotdelete/extract/webSysServer02_wf-web-sys.wftesttest_grp/jarfiles/WEB-INF/lib/struts.jar:
/weblogic81sp5/weblogic81sp5/config/wftesttest/webSysServer02/.wlnotdelete/extract/webSysServer02_wf-web-sys.wftesttest_grp/jarfiles/WEB-INF/lib/taglibs-session.jar:
/weblogic81sp5/weblogic81sp5/config/wftesttest/webSysServer02/.wlnotdelete/extract/webSysServer02_wf-web-sys.wftesttest_grp/jarfiles/WEB-INF/lib/wf.wftesttest.jar:
/weblogic81sp5/weblogic81sp5/config/wftesttest/webSysServer02/.wlnotdelete/extract/webSysServer02_wf-web-sys.wftesttest_grp/jarfiles/_wl_cls_gen.jar:
/weblogic81sp5/weblogic81sp5/config/wftesttest/webSysServer02/.wlnotdelete/extract/webSysServer02_wf-web-sys.wftesttest_grp.
java.lang.ClassNotFoundException:
jsp_servlet._help.__samplehelp00.
at org.apache.struts.taglib.template.InsertTag.doEndTag()I(InsertTag.java:149)
at jsp_servlet.__su_hl0._jspService(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse; )V(__su_hl0.java:289)
at weblogic.servlet.jsp.JspBase.service(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse; )V(JspBase.java:33)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava/lang/Object;(ServletStubImpl.java:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Lweblogic/servlet/internal/FilterChainImpl; )V(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse; )V(ServletStubImpl.java:348)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse; )V(RequestDispatcherImpl.java:328)
at org.apache.struts.action.ActionServlet.processForward(Lorg/apache/struts/action/ActionMapping;Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse; )Z(ActionServlet.java:1847)
at org.apache.struts.action.ActionServlet.process(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse; )V(ActionServlet.java:1568)
at org.apache.struts.action.ActionServlet.doGet(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse; )V(ActionServlet.java:491)
at javax.servlet.http.HttpServlet.service(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse; )V(HttpServlet.java:740)
at com.clear2pay.ppp.util.ui.struts.ActionServlet.service(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse; )V(ActionServlet.java:138)
at javax.servlet.http.HttpServlet.service(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse; )V(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava/lang/Object;(ServletStubImpl.java:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Lweblogic/servlet/internal/FilterChainImpl; )V(ServletStubImpl.java:465)
at weblogic.servlet.internal.TailFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain; )V(TailFilter.java:28)
at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse; )V(FilterChainImpl.java:27)
at com.clear2pay.ppp.util.ui.SetCharacterEncodingFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain; )V(SetCharacterEncodingFilter.java:150)
at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse; )V(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava/lang/Object;(WebAppServletContext.java:6987)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction; )Ljava/lang/Object;(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction; )Ljava/lang/Object;(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic/servlet/internal/ServletRequestImpl;Lweblogic/servlet/internal/ServletResponseImpl; )V(WebAppServletContext.java:3892)
at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic/kernel/ExecuteThread; )V(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest; )V(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:183)
at java.lang.Thread.startThreadFromVM(Ljava/lang/Thread; )V(Unknown Source)
----- END STACKTRACE -----
Message was edited by:
cabuki

Ignore the part about precompiled JSPs being ignored on my development server. Turns out I had a stale cache. I cleared that out and now it recognizes the files.
The problem with that, is now I'm getting an Error 500 when I try to access the page.
----- BEGIN STACKTRACE -----
javax.servlet.jsp.JspException
     at org.apache.struts.taglib.template.InsertTag.doEndTag()I(InsertTag.java:149)
     at jsp_servlet.__su_h0._jspService(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse; )V(__su_h0.java:316)
     at weblogic.servlet.jsp.JspBase.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse; )V(JspBase.java:33)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object; (ServletStubImpl.java:996)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl; )V(ServletStubImpl.java:419)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse; )V(ServletStubImpl.java:315)
     at weblogic.servlet.internal.RequestDispatcherImpl.forward(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse; )V(RequestDispatcherImpl.java:318 )
     at org.apache.struts.action.ActionServlet.processForward(Lorg.apache.struts.action.ActionMapping;Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse; )Z(ActionServlet.java:1847)
     at org.apache.struts.action.ActionServlet.process(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse; )V(ActionServlet.java:1568 )
     at org.apache.struts.action.ActionServlet.doGet(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse; )V(ActionServlet.java:491)
     at javax.servlet.http.HttpServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse; )V(HttpServlet.java:740)
     at com.clear2pay.ppp.util.ui.struts.ActionServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse; )V(ActionServlet.java:138 )
     at javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse; )V(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:996)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl; )V(ServletStubImpl.java:419)
     at weblogic.servlet.internal.TailFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain; )V(TailFilter.java:28 )
     at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse; )V(FilterChainImpl.java:27)
     at com.clear2pay.ppp.util.ui.SetCharacterEncodingFilter.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Ljavax.servlet.FilterChain; )V(SetCharacterEncodingFilter.java:150)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse; )V(FilterChainImpl.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6458 )
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction; )Ljava.lang.Object;(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction; )Ljava.lang.Object;(SecurityManager.java:118 )
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl; )V(WebAppServletContext.java:3661)
     at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread; )V(ServletRequestImpl.java:2630)
     at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest; )V(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178 )
     at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread; )V(Unknown Source)
----- END STACKTRACE -----
The page in question is just a simple JSP using Struts (v 1.0.2) to call in a template.
----- BEGIN JSP -----
<%@ page language="java" contentType="text/html; charset=UTF-8" %>
<%@ taglib uri="/WEB-INF/lib/struts.tld" prefix="struts" %>
<%@ taglib uri="/WEB-INF/lib/struts-bean.tld" prefix="bean" %>
<%@ taglib uri='/WEB-INF/lib/struts-template.tld' prefix='template' %>
<template:insert template='/t/system.jsp'>
<template:put name='title'><bean:message key="tit_su_h0"/></template:put>
<template:put name='sidenav' content='/t/su_snv.jsp'/>
<template:put name='content' content='/c/su_h0_c.jsp'/>
<template:put name='footer' content='/t/su_ftr.jsp' />
</template:insert>
----- END JSP -----
I passed the -keepGenerated flag to the precompile task in my Ant build so I could look at the line it's choking on, but it's not very helpful. I'm stuck. I can set up the build so it doesn't precompile the JSPs, but then the QA team wouldn't like me very much.

Weblogic.jws.Policies.class is missing in weblogic.jar and wlfullclient.jar

Similar Messages

Maybe you are looking for