Clobbered manifest when editing deployment descriptors

I'm running WebLogic server 6.1. I deploy an ear file that consists of one EJB
module (a session bean) and several extra jars, which contain client classes to
other beans and some utility classes. The session bean jar's manifest file includes
a classpath entry listing the extra jars in the ear. However, when I edit some
environment variables in the EJB's deployment descriptors through the console,
this manifest file is replaced and the classpath entry does not appear in the
new manifest. This makes the ear file undeployable. Is this a documented bug?
Is there a fix or workaround?

Similar Messages

How to edit deployment descriptor in weblogic 9.0?

Hi ,
I need to edit the values of certain environment variables mentioned in the deployment descriptor of a ejb module.
In weblogic 7,its a straight forward method in which we have the option to edit the deployment descriptor in weblogic console.
But I'm not sure how the same can be done in weblogic 9.0.
Please guide me..!!! its urgent...
Thanks,
Smita

If you want to edit the actual deployment descriptor (ie as a developer) than using any text editor or using an IDE like WebLogic Workshop/Eclipse etc would be the way to go.
If you're trying to change values in an already deployed application, then configuration and tunables can be changed in the admin console. These write the changes to a separate file called a deployment plan. It allows you to change performance and environment settings without disturbing the original EAR file.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Unable to Edit Deployment Descriptor

Hi,
I am currently using weblogic 6.1 sp4 and am having some problem while trying
to edit the deployment descriptors through the weblogic console.
I get the following error message:
There was an error while loading the descriptor for component:
UserRegistrationMDB
Please fix the error in the component descriptor file(s), redeploy the component
and then press continue to attempt to edit this components descriptor.
The following error(s) occurred:
String index out of range: -1
I dont get this error with weblogic 6.1 sp3.
Please let me know what the reason might be.
Thanks,
JS.

I have attached the ejb jar xml and the weblogic ejb jar xml
Thanks!
- JS
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>UserRegistrationBean</ejb-name>
<ejb-class>UserRegistrationTopicListenerBean</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>dups-ok-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>UserRegistrationBean</ejb-name>
<method-intf>Remote</method-intf>
<method-name>onMessage</method-name>
<method-params>
<method-param>javax.jms.Message</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN"
"http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd" >
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>UserRegistrationBean</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>200</max-beans-in-free-pool>
<initial-beans-in-free-pool>20</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>dss.UserRegistrationTopic</destination-jndi-name>
     <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
     <provider-url>t3://localhost:7000</provider-url>
     <connection-factory-jndi-name>iag.jms.billing.TopicConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
"SP" <[email protected]> wrote:
It seems that the deployment descriptor has a value less than 3 chars
or
more than the maximum chars.
If I can see the deployment descriptor, then I may tell exactly what
the
reason is
SP
"JS" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am currently using weblogic 6.1 sp4 and am having some problem whiletrying
to edit the deployment descriptors through the weblogic console.
I get the following error message:
There was an error while loading the descriptor for component:
UserRegistrationMDB
Please fix the error in the component descriptor file(s), redeploythe
component
and then press continue to attempt to edit this components descriptor.
The following error(s) occurred:
String index out of range: -1
I dont get this error with weblogic 6.1 sp3.
Please let me know what the reason might be.
Thanks,
JS.

Deployment descriptor file(portalapp.xml)

Hi All,
Can you tell me why portalapp.xml is a xml file why cannot it be a .txt or any other ?

In java enterprise edition deployment descriptor denotes how the web or enterprise application should be deployed. It is a directive to the deployment tool regarding the specific configuration requirements that a deployer must fulfill.
XML allows developers to set standards,helps in defining the configurations and the required information and the sequence as well and easy to parse also.
portalapp.xml ,the deployment descriptor of a PAR file defines the components and services contained in the PAR, including the initial configuration and the parameters that can be modified by administrators and users. The descriptor also contains configuration information for the entire application.
So considering the close relationship between java and xml,it makes sense to have the deployment descriptors, be it portalapp or ejb-jar.xml or any other deployment descriptor, as xml , as
these parameters and sequence becomes rather unlikely to be maintained as a text file as there has always been a .

Problem: Editing a deployment descriptor of an EJB or WAR inside of an EAR sends things to hell

Hello,
I've got an EAR with utility classes in lib/ (like log4j and some other
goodies).
Inside my EJBs, I have manifests that have class-path entries that reference
this and they all work upon initial load (I when they don't work because my
beans don't load).
When I edit my descriptors using the WebLogic console and persist my
changes, my EJBs crap out because they can no longer load log4j. When I
shutdown WebLogic and looked at the manifest inside the EJB inside of the
EAR, sure enough, the class-path entry that kept the whole thing working was
gone. WebLogic decided to instead detail a bunch of classes.
Any workaround for this (other than to include all classes in all EJBs)?
This prevents customers and deployers from doing their jobs. :(
How do I report this to BEA? I poked around the website and could nary find
a "report bug" link.
thanks,
greg

Yes - getting to support should be easier ...
www.bea.com -> Services -> Customer Support Services -> Learn More about WebSupport
-> Register for Web Account
Then you can follow the WebSupport link at the bottom of any page.
Mike
"Gregory Gerard" <[email protected]> wrote:
Hello,
I've got an EAR with utility classes in lib/ (like log4j and some other
goodies).
Inside my EJBs, I have manifests that have class-path entries that reference
this and they all work upon initial load (I when they don't work because
my
beans don't load).
When I edit my descriptors using the WebLogic console and persist my
changes, my EJBs crap out because they can no longer load log4j. When
I
shutdown WebLogic and looked at the manifest inside the EJB inside of
the
EAR, sure enough, the class-path entry that kept the whole thing working
was
gone. WebLogic decided to instead detail a bunch of classes.
Any workaround for this (other than to include all classes in all EJBs)?
This prevents customers and deployers from doing their jobs. :(
How do I report this to BEA? I poked around the website and could nary
find
a "report bug" link.
thanks,
greg

How to edit web.xml deployment descriptor from console in weblogic 8.1?

In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
console, but on weblogic 8.1 I can't find a way to do so.
Is this function taken out? Why is it taken out? Do I have an alternative to edit
it without unpacking and packing the EAR or WAR?
Thanks in advance.
Bill

In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
console, but on weblogic 8.1 I can't find a way to do so.
Is this function taken out? Why is it taken out? Do I have an alternative to edit
it without unpacking and packing the EAR or WAR?
Thanks in advance.
Bill

Oracle-specific deployment descriptor

Hi all
does anybody know how i can edit the oracle deployment descriptor while using JDeveloper 3.2 to deploy. I need to add an ejb-reference, wich has to be mapped in the oracle specific descriptor. I tried to do it manually but everytime when i depoly, jdeveloper overwrites my changes during the deployment.
thanks for help...

Hello!
I4m just trying to do the same thing: including ejb references in the oracle descriptor, but it erases any line I include as soon as I start deploying.
Have you solved the problem?.If so, could you give me a clue?.
By the way, I imagine that the references have to be included in the EJB which is calling, and not in the one that is to be called.But I don4t really understand how is the name of the ejb to be called introduced in that enviroment directory.
Thanks in advance!!!
Pepa.

"Edit EJB Descriptor..." Not working

Hi
When i press the "Edit EJB Descriptor..." in a EJB under Deployments in the web-logic
6.1 console, I get this Error:
Error Start -
"There was an error while loading the descriptor for component:
EnvelopeEntityBeans
Please fix the error in the component descriptor file(s), redeploy the component
and then press continue to attempt to edit this components descriptor.
The following error(s) occurred:
error in finding weblogic.Home"
Error end
I deploy a EAR File containing 2 EJB's - one of them have entity beans in it, and
it is the one that have the error.
Thanks
Gal

Just so everyone knows, I was on hold with Adobe tech support for ALMOST TWO HOURS despite the 2-minute wait time they estimated at the beginning of my call. I really don't know how else to describe how I feel, except:
Clearly Adobe gives zero f*cks, even though I pay $40 per month for the creative cloud membership.
Adobe, if you were a person (which you are, because now corporations are people in the USA), I would wish upon you the most severe case of herpes-slash-genital-rot the world has ever seen. I hope that the discomfort of this particular ailment results in your inability to participate in even the shortest meetings or conference calls, due to the fiery burning pain in your nether regions. Then perhaps maybe a more competent and ethical software company could assume your role in the marketplace.
I will be especially amused if an Adherpe forum moderator has time to delete my post and/or ban me forever from the Adobe community, given that a tech support person has no time to answer my call. The plot thickens.
Toodle-loo.
PS: I am extremely sleep deprived, so I refuse to be held accountable for any offense taken to any of the statements set forth above.

About EJB deployment descriptor

Hello. I am developing EJB3 with glassfish and weblogic 10. I know I can use annotations to simplify
deployment without using ejb-jar.xml , sun-ejb-jar.xml, weblogic-ejb-jar.xml. However, I do want to know
how to write these files correctly because they have higher priority when used.
Somebody may give me a template about writing these files? (ejb 3 specification, for ejb2, I can
use xdoclet to generate them).Thanks a lot.

Hi Martin,
you're are right, XDoclet support for OC4J is lacking the most important stuff. In my case I needed explicit mapping of CMR-fields. Of course, manually editing orion-ejb-jar.xml either by using a text editor or JDeveloper is no option at all.
So I've added support for explicit CMR-mapping to the OC4J XDoclet templates. It works but wasn't fun to do as Oracle's documentation of CMR-mapping is highly inconsistent (e.g. text, figures, and example code are not in sync).
As I've done this as part of a services contract, I cannot easily publish the results. I'll ask my client and let you know.
Anyway, orion-ejb-jar.xml will be obsolete by default in OC4J 10.x as Oracle switches to Toplink as the default persistence manager. So again, XDoclet support is needed for generating the Toplink-specific deployment descriptor.
I'd really appreciate Oracle to provide OC4J-specific XDoclet enhancements. This would help OC4J in gaining wider acceptance.
Stefan

JMS Deployment Descriptor Error

Hi,
I am using Netbeans 6.0 and the Sun Application Server 9.1. I have an Enterprise project which includes an application client, and a message bean.
When I attempt to run the project the following error crops up,
Referencing error: this bundle has no message destination of name: jms/DesignQueue
"DPL8007: Invalid Deployment Descriptors element jndi-name value jms/DesignQueue"
In sun-application-client.xml I have the following (which clearly doesn't work)
<message-destination>
<message-destination-name>jms/DesignQueue</message-destination-name>
<jndi-name>jms/DesignQueue</jndi-name>
</message-destination>
<message-destination-ref>
<message-destination-ref-name>jms/DesignQueue</message-destination-ref-name>
<jndi-name>jms/DesignQueue</jndi-name>
</message-destination-ref>
Any suggestions as to what I might be doing wrong? The program stops when it attempts to send a message so this is clearly whats wrong and I cant figure out how to fix it,
Thanks for your time,
atreides7887
Edited by: atreides7887 on Apr 15, 2008 7:07 AM

Back to basics here.
1.Do you have something in the broker logs?
2.Is there a connection attempt?
3.In imqadmin, do you see an added queue (one that you would not have created?)
For reference here (from the app server docs)
DPL8007 Failed to find the resource specified in the deployment descriptor.
Cause: May be because of wrong specification in the descriptor.
Solution: Ensure that the resource specified is present, and that there is no typo in the resource specified in the descriptor.And a [bug that looks|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6583734] like what you are seeing.
4. Are all the names the same?
5. Also, I found that when I change the descriptors (and not the code) in netbeans, you need to do a clean and build, not only a build. And, if the application has been deployed, you may have to stop the app server depending on the model you used for the deployment.
TE
Edited by: TravelEntity on 15-Apr-2008 1:58 PM
Edited by: TravelEntity on 15-Apr-2008 2:06 PM

Custom Deployment Descriptors?

Hey all! I'm coming from Eclipse and am loving all the features JDeveloper brings!
This is a really stupid question, but where does JDeveloper store it's deployment descriptors, and how can you create a custom deployment descriptor such as "persistence.xml" which JBoss uses for customizing it's EJB3 entity handling?
One thing I've noticed, is that JDeveloper does NOT give me the ability to create folders, to create my J2EE structure.
Normally, in Eclipse, I build my project with a folder called 'dd' to house all my deployment descriptors such as:
dd/web/web.xml
dd/web/faces-config.xml
dd/web/jboss-web.xml
dd/ear/application.xml
dd/ear/jboss.xml
dd/par/persistence.xml
etc.........
Then, I just configure ant to include the deployment descriptor, depending on what portion of the project I'm building. Then, I create a 'build' folder, to house my compiled jars, war, and ear files.
How do you all create your project structure when you can't create folders?
I've moved to JDeveloper because it is the only IDE that allows me to build drag-and-drop Faces projects while still allowing me to compile against EJB3.0 libraries.
I'd really like to be able to make this work. Obviously there is a better way, so I'm asking for everyone's expertise on how YOU create your J2EE structures with JDeveloper.
Thanks in advance!! Great product. I just need to get over my initial Eclipse-mode of thinking.
~~Aaron

Hmmmmm.
I'm building my ant build.xml files now. But I've run into a hitch, and am curious on how the other JDevelopers get around it.
JDeveloper splits my application up into Projects. So, I now have two projects: My Model project and my ViewController project for my entity/session beans and my web files respectively.
I can create a build.xml file for my entity (jar files) and a build.xml file for my web (war files), but normally, most people put a build.xml file in the root of the project to merge the web and J2EE files into an EAR.
JDeveloper won't allow me to put a build.xml file in the root of my Application to jar up all my project files into an EAR.
I found a really good article on Oracle's website, but it mainly dealt with Maven, and not Ant.
Could someone give me their experience on how you create your Ant structure? Granted, I could just add everything into a single build.xml file in my model project, but then, that could get confusing to other developers using my code, as well as, in a team environment, where each developer has their own build.xml file for the project they are responsible for.
Thanks!
Message was edited by:
Neelixx

EJB Deployment Descriptors not deploying to WLS

Hi,
We're using Eclipse 3.4.1 with the OEPE to target WLS 10.3 with Java 6/JEE 1.4 on a Windows XP Professional development machine.
We have an EJB 2.1 project as part of a larger EAR. The beans (all stateless session beans) and associated interfaces and deployment descriptors within are maintained manually for internal reasons; we do not rely on EJBGen or XDoclet or anything like that to manage these. We are NOT using any annotations in these EJBs, as is the default when you create a bean. Instead we rely on weblogic-ejb-jar.xml and ejb-jar.xml.
We're having an issue where deploying to the local Weblogic server instance fails with the following error displaying in the Eclipse console:
<Dec 19, 2008 9:21:13 AM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'xxxxxxx'.>
<Dec 19, 2008 9:21:13 AM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(xxxxxxxEJB.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation..
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     Truncated. see log file for complete stacktrace
java.io.IOException: No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:199)
     at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
     at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     Truncated. see log file for complete stacktrace
We DO have multiple beans defined, but it seems that WLS just isn't aware of them due to the lack of a deployment descriptor. It appears that Eclipse/OEPE is not copying the ejb-jar.xml and weblogic-ejb-jar.xml files to the build directory when the project is build:
xxxxxEJB
|-- ejbModule
|.....|-- META-INF
|.....|.....|-- ejb-jar.xml
|.....|.....|-- MANIFEST.MF
|.....|.....|-- weblogic-ejb-jar.xml
|.....|-- com (etc., .java files)
|-- build
......|-- classes
............|-- META-INF
............|......|-- MANIFEST.MF
............|-- com (etc, .class files)
Other notes:
- Cleaning the project does not help.
- Starting a new workspace does not help.
- It works under Eclipse 3.3.2 with the Europa version of OEPE.
- Explicitly exporting an EJB Jar file DOES include the two deployment descriptors (just not deploying to the embedded test server we've defined in our Servers view)
Any ideas? This seems like either a bug in the OEPE, or maybe WTP.

Yes, I have a simple EJB2.1 project with hand-crafted EJB remote/home interfaces/classes and deployment descriptors. Also tried Clean/Rebuild and manually delete
files under /build/classes.
Here are my descriptors files:
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
     <display-name>TestEJB</display-name>
<enterprise-beans>
<session>
<display-name>HelloSessioin</display-name>
<ejb-name>HelloSession</ejb-name>
<home>sessions.HelloSessionHome</home>
<remote>sessions.HelloSession</remote>
<ejb-class>sessions.HelloSessionBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
<security-identity>
<use-caller-identity/>
</security-identity>
</session>
</enterprise-beans>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloSession</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<jndi-name>ejb.HelloSessionRemoteHome</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Did you check if there is any error/warning in Error Log view?

Persistence provider declared in the deployment descriptor is not supported

Hi,
When I try to deploy an entity bean (using JDev 3.2 and Oracle 8.1.7) I got this message:
"Persistence provider declared in the deployment descriptor is not supported".
Should I change something in the "..._oracle.xml" file generated by JDev?
Anyway the xlm part, regarding the persistence provider, is:
<persistence-provider>
<description> specifies a type of persistence manager </description>
<persistence-name>BC4J</persistence-name>
<persistence-deployer> bcdom.DomejbViewDeployer</persistence-deployer>
</persistence-provider>
Anybody knows what is this about?
Thanks,
Gabi Rosu

Hi,
I've already deployed the CMPRuntime library, and I followed the cmpdemo demo step by step and this xml file is the result of the Jdev wizard. But I still got the same error message.
I even edit the ..._oracle.xml file, changing the persistance provider into "oracle.aurora.ejb.persistence.ocmp.OcmpEntityDeployer", the way is in the online documentation, but it keeps saying that this class (OcmpEntityDeployer) is not found.
So, what should I do?
Thanks in advance,
Gabi

Weblogic console Edit EJB Descriptor link missing

Hi..
I am running weblogic 6.1 sp1. And I have a set of EJB's deployed. But when I click
on any ejb in the tree view in console, i can not see the Edit EJB Descriptor link
on the right hand side screen.
I have two server instances running with the same set of EJB's deployed. And I can
get this link on one console and do not get it on the other console.
Can anyone tell me what is wrong with it ? Or is there any setting using which we
can disable the access to Edit EJB Descriptor link ?
Thanks in advance..
Mandar

hi..
I have NOT disabled the link myself.... but for some reasons, the link is not available.
I also checked the right click menu (right click on the deployed ejb in the tree
view) and i didnt get the Edit EJB Descriptor option there also... I have two server
instances running in Development mode and one console is not showing the link while
the other is showing the link..
I am attaching a screenshot to explain the situation. Can anyone has experienced
this before ? Please help me..
Regards
Mandar
"Mihir Kulkarni" <[email protected]> wrote:
I am running weblogic 6.1 sp1. And I have a set of EJB's deployed. Butwhen I click
on any ejb in the tree view in console, i can not see the Edit EJBDescriptor link
on the right hand side screen.
I have two server instances running with the same set of EJB's deployed.And I can
get this link on one console and do not get it on the other console.
Can anyone tell me what is wrong with it ? Or is there any setting usingwhich we
can disable the access to Edit EJB Descriptor link ?No there is no such option to disable the access to edit the EJB
Descriptors - its present both in the Dev and the Prod mode.
Besides the link in the right frame, you can also right click on the EJB
Name in the navigation tree to edit the descriptors ....
cheers,
Mihir
Thanks in advance..
Mandar
[Ejb Descriptor missing.JPG]

Error when ejb deployment in WLS 9.1 clustered environment

Hello,
We have a WLS 9.1 cluster consisting of one admin server and two managed servers. we are deploying ejb jar,It is succeed on the first managed server but fail on the second managed server. The admin console and for the second managed server contains the following log(below given). I checked the classpath of two managed servers, It is same in two servers. when i restarted the two managed servers, application is in active state but not running in second managed sever complining for one ejb class that the jndi-name in the weblogic-ejb-jar.xml is not correct. If it is not correct it should not run in first managed server also right.
please help me whether Am I doing something wrong or is this a bug?
below given the log when i deployed the ejb.
####<May 18, 2007 9:49:22 AM GMT> <Error> <Deployer> <tool2> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1179481762802> <BEA-149265> <Failure occured in the execution of deployment request with ID '1179481757718' for task '8'. Error is: 'java.lang.AssertionError: Assertion violated'
java.lang.AssertionError: Assertion violated
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.cluster.migration.MigrationManager.unregister(MigrationManager.java:246)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onUndeploy(MessageDrivenBeanInfoImpl.java:999)
at weblogic.ejb.container.manager.BaseEJBManager.undeploy(BaseEJBManager.java:467)
at weblogic.ejb.container.manager.MessageDrivenManager.undeploy(MessageDrivenManager.java:570)
at weblogic.ejb.container.deployer.EJBDeployer.deactivate(EJBDeployer.java:1817)
at weblogic.ejb.container.deployer.EJBModule.doDeactivate(EJBModule.java:1041)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:420)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:60)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:567)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:131)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:101)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:126)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:329)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:845)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1246)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:432)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
java.lang.AssertionError: Assertion violated
at weblogic.utils.Debug.assertion(Debug.java:57)
at weblogic.cluster.migration.MigrationManager.unregister(MigrationManager.java:246)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.onUndeploy(MessageDrivenBeanInfoImpl.java:999)
at weblogic.ejb.container.manager.BaseEJBManager.undeploy(BaseEJBManager.java:467)
at weblogic.ejb.container.manager.MessageDrivenManager.undeploy(MessageDrivenManager.java:570)
at weblogic.ejb.container.deployer.EJBDeployer.deactivate(EJBDeployer.java:1817)
at weblogic.ejb.container.deployer.EJBModule.doDeactivate(EJBModule.java:1041)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:420)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:104)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:339)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:68)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:60)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:640)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:252)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:567)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:131)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:101)
at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:126)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:329)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:845)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1246)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:432)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
>
####<May 18, 2007 9:49:22 AM GMT> <Error> <Deployer> <tool2> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1179481762823> <BEA-149202> <Encountered an exception while attempting to commit the 7 task for the application 'MyEJB'.
Regards,
mohan
Edited by raj_bea_raj at 05/29/2007 1:35 AM
Edited by raj_bea_raj at 05/29/2007 1:41 AM

If you're using OC4J standalone, use the latest available OC4J, 10.1.3.3.
If you're using a manage OC4J, ie. Application Server, upgrade to the latest available version and upgrade your JDK. The provided JDK might be outdated.
--olaf

Clobbered manifest when editing deployment descriptors

Similar Messages

Maybe you are looking for