Weblogic 10.3.0 Deployment error when using ejb-jar.xml

Hi,
I am getting the following error while deploying my EJB3 application on Weblogic 10.3.0. This is happening only if I include ejb-jar.xml.
As per the EJB3 descriptor spec, Remote Home or Local home are not exists.
Is this a issue in Weblogic 10.3.0 or am I missing any special setup ?
Please help.
weblogic.application.ModuleException: Exception preparing module: EJBModule(egm-poc.jar)
Unable to deploy EJB: C:\appsrv\domains\WeblogicRS1.1-domain\servers\admin\tmp\_WL_user\_appsdir_egmear_ear\ot2591\egm-poc.
jar from egm-poc.jar:
In EJB JPATestBean, both the remote home and remote component interface must be specified. Currently, only one of them is spec
ified.
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)
My ejb-jar.xml is
- <ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
<description>JPA Test Application</description>
<display-name>JPATest</display-name>
- <enterprise-beans>
- <session>
<ejb-name>JPATestBean</ejb-name>
<remote>egm.poc.jpa.JPATestBeanRemote</remote>
<local>egm.poc.jpa.JPATestBeanLocal</local>
<ejb-class>egm.poc.jpa.JPATestBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
- <session>
<ejb-name>AuditInfoDAOH</ejb-name>
<local>egm.poc.jpa.Audit</local>
<ejb-class>egm.poc.jpa.AuditInfoDAOH</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
- <assembly-descriptor>
- <container-transaction>
- <method>
<ejb-name>JPATestBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>RequiresNew</trans-attribute>
</container-transaction>
- <container-transaction>
- <method>
<ejb-name>AuditInfoDAOH</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
Regards
Saji

Hi,
Seems the issue is not common. Can anyone throw some light on this ?
Regards
Saji

Similar Messages

Deploy Error when using Stateful Session Bean inside Webdynpro

Hi,
I'm trying to create a webdynpro project that uses a stateful session bean
I have created DC's for a EJB Module project, Enterprise Application and Webdynpro component. Created the bean, built it, added it's package to the public part, added the EJB Module to the EAR project. Built the EAR project. Added the EJB Module project and Enterprise Application project as a used DC in the Webdynpro DC.
In the Webdynpro DC I added com.sap.archive-packaging.default.update-descriptors=true in the build.properties file of the cfg directory. (using the navigator view) That resolved an error while building it.
Deployed the Enterprise Application DC without problems.
Tried to deploy the Webdynpro DC but I get the following error:
Jun 16, 2008 9:40:46 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] WARNING:
[012]Deployment finished with warning
Settings
SDM host : 10.64.36.74
SDM port : 50018
URL to deploy : file:/C:/DOCUME~1/JESCHA~1/LOCALS~1/Temp/temp59822company.nl~projempactcmp.ear
Result
=> deployed with warning : file:/C:/DOCUME~1/JESCHA~1/LOCALS~1/Temp/temp59822company.nl~projempactcmp.ear
Finished with warnings: development component 'projempactcmp'/'company.nl'/'local'/'20080616094022':Caught exception during application startup from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Error occurred while starting application company.nl/projempactcmp and wait. Reason: Clusterwide execption: server ID 6060950:<--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed implicit start for company.nl/projempejb : Unknown state(5)', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed implicit start for company.nl/projempejb : Unknown state(5)', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Failed implicit start for company.nl/projempejb : Unknown state(5)', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Failed implicit start for company.nl/projempejb : Unknown state(5) (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : Got problems during deployment
Does anyone know what this error means and how to resolve it. I searched the forum but only found errors that look like this relating to XI not to Webdynpro.......
Thansk,
Jeschael
Edited by: J.V. Lebbink on Jun 17, 2008 6:52 AM

Default is 30mts.
This is done as a parameter in orion-ejb-jar.xml. Please look at the EJB Guide at http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/a97677/dtdxml.htm#634197 for details
regards
Debu

Problem deploying connector: META-INF/ejb-jar.xml not found in jar file

          Has anyone seen this problem:
          I built Sun's Blackbox implementation and packaged
          it identical to the BlackBoxNoTx.rar included with
          Weblogic's 'jconnector' sample (even using the same
          ra.xml and weblogic-ra.xml). When I try to deploy
          it, the server reports:
          java.io.FileNotFoundException:
          META-INF/ejb-jar.xml not found in jar file
          I have no idea why the server thinks my connector
          is an EJB. If I deploy the BlackBoxNoTx.rar included
          with the sample, everything works without a hitch.
          The only variable that I'm changing in my BlackBoxNoTx.rar
          is that I build the Blackbox classes myself--otherwise,
          the RAR packagings are identical. Any assistance is
          greatly appreciated since I'm banging my head against
          a wall...
          Thanks,
          -jason


          I was finally able to resolve this one. On the odd chance that someone else encounters
          the same problem, here's what went wrong:
          My RAR file had two directories: 'META-INF' and 'meta-inf'. The first was created
          by the jar tool and contained the manifest.mf file. The second I created manually
          and it contained my ra.xml and weblogic-ra.xml. When I examined the RAR using
          any tools or I extracted the contents, it looked like it only contained one directory:
          META-INF (because NT is case-insensitive).
          "Jason L" <[email protected]> wrote:
          >
          >Has anyone seen this problem:
          >
          >I built Sun's Blackbox implementation and packaged
          >it identical to the BlackBoxNoTx.rar included with
          >Weblogic's 'jconnector' sample (even using the same
          >ra.xml and weblogic-ra.xml). When I try to deploy
          >it, the server reports:
          >
          >java.io.FileNotFoundException:
          >META-INF/ejb-jar.xml not found in jar file
          >
          >I have no idea why the server thinks my connector
          >is an EJB. If I deploy the BlackBoxNoTx.rar included
          >with the sample, everything works without a hitch.
          >The only variable that I'm changing in my BlackBoxNoTx.rar
          >is that I build the Blackbox classes myself--otherwise,
          >the RAR packagings are identical. Any assistance is
          >greatly appreciated since I'm banging my head against
          >a wall...
          >
          >Thanks,
          >
          >-jason

Getting Deploy Error when using the WebDynpro Compiler

Hi,
I have a VC application which uses the RFC from R/3.
When i am using the Compiler as WEBDYNPRO, it is giving me Deploy Error as:
WebDynpro Compiler:
Portal request failed
(Model properties Namespace and Vendor are not specified for source archieve generator)
Also,
I checked the Iview property in the Portal but i am unable to find this properties.
Guide me when and where this Complier type is uesd..?
Thanks & Regards,
Dhruv Shah

Hi,
I am unable to find this properties.
In the Model View i searched a lot.
I have another question also.
Do you know how to refresh the table from the RFC.
Thanks& regards,
Dhruv Shah

Deployment error when using several ejb-jar files

Hello All,
I am having problems with deployment of my J2EE application. My EAR file has several EJB-JARs, one for each entity bean. However I refer to the other EJBs in one EJB. Hence I included the <ejb-ref> element in the deployment descriptor of the entity bean. But I am getting the deployment error that "the bundle does not contain the bean name". I tried to change the <ejb-name> value (within the <ejb-ref> element) to the JNDI name of the EJB I am referring to, and also added the <ejb-link> tag specifying the location of the JAR file that has the EJB. None of the attempts worked.
Can someone help me out on how I am supposed to go about when I have several ejb-jar files as opposed to a single one? I am deploying my app on Sun ONE AS 7.0.
Thank you,
PS: I am posting this message on several forum topics. Please disregard this message if you have seen/answered this message. Thanks.

Hello,
Thanks for the response. I have got both Local and Remote EJB References, but for the JAR (where the ejbc compiler stopped) that I have an error, it is the local reference.

Hello REST web service example deployment fails when using EJB

I was able to successfully deploy the hello REST web service example. But when I attempted to lookup an EJB via the following code I get an error message.
try {
ic = new InitialContext();
DirectoryBean db = (DirectoryBean)ic.lookup("java:comp/env/ejb/DirectoryBean");
} catch (NamingException ex) {
ex.printStackTrace();
Here is the error message in the NetBeans console window:
Deploying application in domain failed; Error loading deployment descriptors for module [hello] -- com.sun.enterprise.deployment.annotation.context.WebBundleContext cannot be cast to com.sun.enterprise.deployment.annotation.context.EjbContextat com.sun.enterprise.deployment.annotation.AnnotationInfo@15f1fa0
D:\java\Sun\swdp-tutorial-1.0\examples\rest\hello\nbproject\build-impl.xml:450: Deployment error:

I think the problem may be that the SimpleServlet example uses an apt feature to generate a web.xml which will replace any web.xml you already have in the project (and lose any references etc you might have in it). To work around this problem first copy the necessary lines from the web.xml in the generates .war file - they should look something like this:
<servlet>
<servlet-name>RESTBeans Application</servlet-name>
<servlet-class>com.sun.ws.rest.impl.container.servlet.ServletAdaptor</servlet-class>
<init-param>
<param-name>resourcebean</param-name>
<param-value>com.sun.ws.rest.samples.servlet.resources.RESTBeansResources</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>RESTBeans Application</servlet-name>
<url-pattern>/restbean/*</url-pattern>
</servlet-mapping>
Add these to your project web.xml, replacing any lines that look similar (the web.xml in the sample project has these lines that you'll need to replace:
<servlet>
<servlet-name>ServletAdaptor</servlet-name>
<servlet-class>com.sun.ws.rest.impl.servlet.ServletAdaptor</servlet-class>
<init-param>
<param-name>resources</param-name>
<param-value>test1</param-value>
</init-param>
</servlet>
<servlet-mapping>

<servlet-name>ServletAdaptor</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
Now you need to turn off automatic web.xml generation by adding <option key="noservlet"/> to the apt task option in build.xml (look for the apt child of the -pre-compile task in build.xml).
Clean and rebuild and make sure that the web.xml in the generated .war file now matches the project web.xml file.
Marc.

URGENT! SEGV-errors when using Oracle C XML Parser for Solaris

I often (not always) got SEGV-error with core dump when I use Oracle Oracle C XML Parser for Solaris. This Error is always got in the call of the the function xmlinit(...) with all params as NULL but the first required for the error code and the second which i assign a macro that evaluates to "US-ASCII". Does anyone knows about this problem?
I am using a very short, wellformed and validated XML document.
I would be very glad for some help about this!
null

Please provide a sample program along with the version number of the XML parser.

Error when using WebServicesAssembler.jar!!!

I download Web Service sample hotel_reservation on OTN and follow the guide in README file but when I package the Web Services Archieve file by the command:
java -jar $ORACLE_HOME/webservices/lib/WebServicesAssembler.jar -config ./config.xml
This generated:
Please wait ...
Exception in thread "main" java.lang.NullPointerException: class com.oracle.demo.Hotel not found
at oracle.j2ee.ws.tools.WsAssemblerConfig.toEAR(WsAssemblerConfig.java:5
19)
at oracle.j2ee.ws.tools.WsAssembler.assemble(WsAssembler.java:92)
at oracle.j2ee.ws.tools.WsAssembler.main(WsAssembler.java:66)
Please help me to overcome it. Thanks a lot.

Make sure your Java files, Hello.java presumbly, can be found under the directory specified by <java-resource/>:
<java-resource>./src</java-resource>

Weblogic 9.2 error when using spring framework and taglibs.

I am getting the following error when using spring binding for a command form class.
Class ExCommandForm
private String firmCode;
public String getFirmCode ()
public void setFirmCode ()
In my jsp I have the following
<spring:bind path="exCommandForm.firmCode">
<input name="<c:out value="${status.expression}"/>" type="text" value="<c:out value="${status.value}"/>" >
</spring:bind>
Ps. exCommandForm is the commandForm declaration in my SiimpleFormController.
When I deploy the application to weblogic 9.2 I get the following error :
<Apr 26, 2007 4:34:44 PM BST> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.int
ernal.WebAppServletContext@1f601c6 - appName: 'BDRui', name: 'BDRui', context-pa
th: '/BDRui'] Root cause of ServletException.
java.lang.ClassCastException: javax.servlet.jsp.jstl.core.LoopTagSupport$1Status
at jsp_servlet._web_45_inf._jsp.__tradesearch._jspService(__tradesearch.
java:1075)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run
(StubSecurityHelper.java:225)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecuri
tyHelper.java:127)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.jav
a:283)
Ps. Deploying application on Tomcat 5.23 works.
Can anyone help on this ?
cheers in advance.
More Info - Using Weblogic 9.2 on UNIX, servlet 2.4, jstl 1.1
regards
Edited by kings_citi at 04/26/2007 9:03 AM
Edited by kings_citi at 04/26/2007 10:35 AM
Edited by kings_citi at 04/26/2007 10:36 AM

The problem doesn't look like it has anything to do with wappers per se. The stack indicates that the JVM died when the persistent store tried to invoke a standard Java synchronize operation. JVM crashes need to be analyzed by a JVM expert, so I second the suggestion to solicit help from JVM experts and/or filing a case with customer support. In the mean-time, you can probably work-around the issue by either (A) ensuring you have a recent version of the JVM installed, or (B) temporarily switching to the Sun JVM.
Regards,
tom
Edited by: TomB on Sep 17, 2010 2:33 PM

Java Heap Error when using Stateless Session Timer Bean deployed in Oracle

Hi,
Am getting following Java Heap Error when using Stateless Session Timer Bean deployed in Oracle 10g AS R3 (Oracle Containers for J2EE 10g (10.1.3.0.0) (build 060119.1546.05277) ):
06/08/02 14:58:43 javax.ejb.EJBException: java.lang.OutOfMemoryError: Java heap space
06/08/02 14:58:43 at com.evermind.server.ejb.EJBUtils.getLocalUserException(EJBUtils.java:304)
06/08/02 14:58:43 at com.evermind.server.ejb.interceptor.system.AbstractTxInterceptor.convertAndHandleMethodException(AbstractTxInterceptor.java:67)
06/08/02 14:58:43 at com.evermind.server.ejb.interceptor.system.TxNotSupportedInterceptor.invoke(TxNotSupportedInterceptor.java:45)
06/08/02 14:58:43 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/08/02 14:58:43 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:86)
06/08/02 14:58:43 at com.evermind.server.ejb.StatelessSessionEJBHome.invokeTimer(StatelessSessionEJBHome.java:71)
06/08/02 14:58:43 at com.evermind.server.ejb.EJBContainer.invokeTimer(EJBContainer.java:1624)
06/08/02 14:58:43 at oracle.ias.container.scheduler.TimerTask.runBeanTimer(TimerTask.java:92)
06/08/02 14:58:43 at oracle.ias.container.scheduler.TimerTask.run(TimerTask.java:184)
06/08/02 14:58:43 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819)
06/08/02 14:58:43 at java.lang.Thread.run(Thread.java:595)
06/08/02 14:58:43 Caused by: java.lang.OutOfMemoryError: Java heap space
I had tried using -Xms / -Xmx options (upto 1 GB).
The trace of exception gets delayed (from being displayed on the console) as the memory size is increased; but after sometime it starts getting displayed on the console.
Even though this exception is displayed on the console, the Timer Bean continues to execute upto sometime before it finally crashes!
If anyone has encountered such problem; would appreciate if you could share the solution.
Regards, Vidyadhar

Hi guys, I have the same problem. I have an application EAR file with two modules (EJB and WAR starting in this order). The application can schedule a process via EJB timer. In this case restarting the server I receive the error above. If I change the modules start order --> WAR - EJB the server start correctly, but the application scheduler fails (the persistency is not working) with this error:
07/10/09 10:30:54 FINISSIMO: TimerTask.runBeanTimer java.lang.NullPointerException; nested exception is: java.lang.NullPointerExceptionjavax.ejb.TransactionRolledbackLocalException: java.lang.NullPointerException; nested exception is: java.lang.NullPointerException
java.lang.NullPointerException
     at java.util.ListResourceBundle.handleGetObject(ListResourceBundle.java:107)
     at java.util.ResourceBundle.getObject(ResourceBundle.java:319)
     at java.util.ResourceBundle.getString(ResourceBundle.java:285)
     at java.util.logging.Formatter.formatMessage(Formatter.java:108)
     at oracle.j2ee.util.TraceLogFormatter.format(TraceLogger.java:124)
     at oracle.j2ee.util.TraceLogger$TraceLoggerHandler.publish(TraceLogger.java:105)
     at java.util.logging.Logger.log(Logger.java:428)
     at java.util.logging.Logger.doLog(Logger.java:450)
     at java.util.logging.Logger.log(Logger.java:539)
     at oracle.ias.container.timer.TimerEntry.readObjFromBytes(TimerEntry.java:308)
     at oracle.ias.container.timer.TimerEntry.getInfo(TimerEntry.java:107)
     at oracle.ias.container.timer.Timer.getInfo(Timer.java:367)
     at oracle.ias.container.timer.EJBTimerImpl.getInfo(EJBTimerImpl.java:89)
     at com.finantix.foundation.integration.ejbtimer.EJBTimerServiceExecutorBean.ejbTimeout(EJBTimerServiceExecutorBean.java:42)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBTimeoutJoinPoint.invoke(EJBTimeoutJoinPoint.java:20)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:53)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at com.evermind.server.ejb.StatelessSessionEJBHome.invokeTimer(StatelessSessionEJBHome.java:38)
     at com.evermind.server.ejb.EJBContainer.invokeTimer(EJBContainer.java:1714)
     at oracle.ias.container.scheduler.TimerTask.runBeanTimer(TimerTask.java:106)
     at oracle.ias.container.scheduler.TimerTask.run(TimerTask.java:220)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
javax.ejb.TransactionRolledbackLocalException: java.lang.NullPointerException; nested exception is: java.lang.NullPointerException
     at com.evermind.server.ejb.EJBUtils.getLocalUserException(EJBUtils.java:309)
     at com.evermind.server.ejb.interceptor.system.AbstractTxInterceptor.convertAndHandleMethodException(AbstractTxInterceptor.java:73)
     at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:55)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at com.evermind.server.ejb.StatelessSessionEJBHome.invokeTimer(StatelessSessionEJBHome.java:38)
     at com.evermind.server.ejb.EJBContainer.invokeTimer(EJBContainer.java:1714)
     at oracle.ias.container.scheduler.TimerTask.runBeanTimer(TimerTask.java:106)
     at oracle.ias.container.scheduler.TimerTask.run(TimerTask.java:220)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
     at java.util.ListResourceBundle.handleGetObject(ListResourceBundle.java:107)
     at java.util.ResourceBundle.getObject(ResourceBundle.java:319)
     at java.util.ResourceBundle.getString(ResourceBundle.java:285)
     at java.util.logging.Formatter.formatMessage(Formatter.java:108)
     at oracle.j2ee.util.TraceLogFormatter.format(TraceLogger.java:124)
     at oracle.j2ee.util.TraceLogger$TraceLoggerHandler.publish(TraceLogger.java:105)
     at java.util.logging.Logger.log(Logger.java:428)
     at java.util.logging.Logger.doLog(Logger.java:450)
     at java.util.logging.Logger.log(Logger.java:539)
     at oracle.ias.container.timer.TimerEntry.readObjFromBytes(TimerEntry.java:308)
     at oracle.ias.container.timer.TimerEntry.getInfo(TimerEntry.java:107)
     at oracle.ias.container.timer.Timer.getInfo(Timer.java:367)
     at oracle.ias.container.timer.EJBTimerImpl.getInfo(EJBTimerImpl.java:89)
     at com.finantix.foundation.integration.ejbtimer.EJBTimerServiceExecutorBean.ejbTimeout(EJBTimerServiceExecutorBean.java:42)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBTimeoutJoinPoint.invoke(EJBTimeoutJoinPoint.java:20)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxBeanManagedInterceptor.invoke(TxBeanManagedInterceptor.java:53)
     ... 9 more
Any idea?
Thx Auro

Errors when using source2wsdd

Any help will be greatly appreciated.
I got the following errors when using the ant task source2wsdd:
[source2wsdd] classpath C:\bea\weblogic81\server\lib\weblogic.jar;C:\bea\weblogi
c81\server\lib\webservices.jar
[source2wsdd] source2wsdd: Cannot find doclet class weblogic.webservice.tools.dd
gen.ServiceGen
[source2wsdd] 1 error
[ant] Exiting C:\project\DCII\ant\batch-build.xml.
BUILD FAILED
C:\project\ant\build.xml:67: The following error occurred while executing this l
ine:
C:\project\DCII\ant\batch-build.xml:326: javadoc execution failed
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(Projec
tHelper.java:539)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:388)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.Main.runBuild(Main.java:673)
at org.apache.tools.ant.Main.startAnt(Main.java:188)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:196)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:55)
Caused by: C:\project\DCII\ant\batch-build.xml:326: javadoc execution failed
at weblogic.ant.taskdefs.webservices.autotype.JavaSource2DD.runJavadoc(J
avaSource2DD.java:297)
at weblogic.ant.taskdefs.webservices.autotype.JavaSource2DD.execute(Java
Source2DD.java:150)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at ise.antelope.tasks.Call.execute(Call.java:17)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at ise.antelope.tasks.IfTask.doIf(IfTask.java:298)
at ise.antelope.tasks.IfTask.execute(IfTask.java:267)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:386)
... 10 more
--- Nested Exception ---
C:\project\DCII\ant\batch-build.xml:326: javadoc execution failed
at weblogic.ant.taskdefs.webservices.autotype.JavaSource2DD.runJavadoc(J
avaSource2DD.java:297)
at weblogic.ant.taskdefs.webservices.autotype.JavaSource2DD.execute(Java
Source2DD.java:150)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at ise.antelope.tasks.Call.execute(Call.java:17)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at ise.antelope.tasks.IfTask.doIf(IfTask.java:298)
at ise.antelope.tasks.IfTask.execute(IfTask.java:267)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:386)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
at org.apache.tools.ant.Project.executeTargets(Project.java:1062)
at org.apache.tools.ant.Main.runBuild(Main.java:673)
at org.apache.tools.ant.Main.startAnt(Main.java:188)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:196)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:55)
Total time: 8 seconds
The following is the major parts from my ant build file:
<path id="webservice.classpath">
<pathelement location="${wls.home.dir}/server/lib/weblogic.jar"/>
<pathelement location="${wls.home.dir}/server/lib/webservices.jar"/>
</path>
<target name = "initialize">
<mkdir dir="${build.dir}"/>
<mkdir dir="${class.dir}"/>
<mkdir dir="${dist.dir}/${deploy.env}"/>
<mkdir dir="${jdocs.dir}"/>
<mkdir dir="${weblogic.application.dir}"/>
<taskdef name="call"
classpathref="antelope.classpath"
classname="ise.antelope.tasks.Call"/>
<taskdef name="if"
classpathref="antelope.classpath"
classname="ise.antelope.tasks.IfTask"/>
<taskdef name="servicegen"
classpathref="webservice.classpath"
classname="weblogic.ant.taskdefs.webservices.servicegen.ServiceGenTask"/>
<taskdef name="clientgen"
classpathref="webservice.classpath"
classname="weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask"/>
<taskdef name="source2wsdd"
classpathref="webservice.classpath"
classname="weblogic.ant.taskdefs.webservices.autotype.JavaSource2DD"/>
<taskdef name="wldeploy"
classpathref="webservice.classpath"
classname="weblogic.ant.taskdefs.management.WLDeploy"/>
</target>
<target name="buildEar"
depends="buildCommonJar, ejbc">
<echo message ="[${module.name}] Checking to see if ${ear.file} is up to date...[${appc.classpath}]" />
<source2wsdd
javaSource="${webserviceServer_src_dir}/HelloWorld.java"
ddFile="${descriptor.dir}/webservice/web-services.xml"
serviceUri="/HelloWorld">
<classpath refid="webservice.classpath" />
</source2wsdd>
<echo message ="[Done with buildEar]" />
</target>

Did you ever resolve this?

Error when using PPR in the OA page developed.

HI,
We are encountering an error when using PPR for the custom OA page being developed. I am using JDeveloper version 9.0.3.5(Build 1437) and Oracle Applications version 11.5.10.CU2. The scenario we are using PPR and the steps to reproduce the issue is mentioned below,
Scenario:
1) PPR is enabled for a custom OA page that is developed.
2) The PPR is being used to enable or disable a particular field based on the
selection of a value in a poplist in the same OA Page.
Error replication steps:
1) The user enters a value in the primary mandatory field which has to have
unique value.
2) The user selects a value from the poplist of a field which has PPR associated.
3) The user enters data in all other mandatory fields in the OA page except one
and tries to save the form and is shown a error message saying that all
mandatory fields are not entered(This is correct). Now the page gets
automatically refreshed and so the entered values are wiped off.
4) Now if the user again enters a value in the primary mandatory field (as in
step1) and if that value happens to be already existing value and then select
a value from the poplist which has PPR enabled then immediately the error
"Please enter a unique value" is entered, though we did not save the record.
The unique record validation would happen only at the time of saving the
record as per out business logic.
5) But if in Step 4 if i had entered a unique value again then the above said error
does not happen. There are few more similar kind of issues happening in the
same page because PPR is enabled.
Please note that this issue happens only when the page is deployed in a oracle
applications instance and not in JDeveloper.
Would this issue because of some cacheing problem? If Yes then how do we resolve it? Or would it be some other problem caused by our internal coding.
Any inputs for resolving this issue would be highly appreciated.
Thanks, Raja.

What works in Jdeveloper should work when deployed in iAS as well.
And PPR is an old feature given quite enough time to mature, so before we suspect OA we should investigate the code. What I do not understand is how the page refreshes in Step 3 and why does the user have to re-enter the fields just because he missed entering one mandatory field the last time.
Mandatory field validations are client validations set by making the fields 'Required'. You obviously have client validations turned off on your PPR, otherwise you would be stuck with a javascript popup on PPR. The only way you can get the "Please enter unique..." error on PPR is Server Validation. So where have you placed this validation? If it is not in the EO, is it in the AM? And are you unconditionally calling the AM validation method in your processFormRequest? The PPR will also go through processFormRequest so I hope the PPR event is in a different if-else block.

Deployment Error when transporting to TEST server

Hi experts,
I'm having a deployment error when transporting my dc from development server to test server using the Change Management Service - Transport Studio.
In the error message, there is the mention of the following sentence:
=============================================
Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine ?
=============================================
But the dc is using only the standard default dcs like:
com.sap.aii.proxy.framework (default)
com.sap.aii.util.misc (default)
com.sap.exception (default)
com.sap.mw.jco (default)
tc/cmi (default)
tc/ddic/ddicruntime (default)
td/ddic/metamodel/content (default)
tc/logging (default)
tc/wd/webdynpro (default)
tc/wdp/metamodel/content (default)
So could these dcs not have been deployed on the test server ?
How do we confirm this ?
Thanks in advance.
Rgds,
Daniel

A dump of the exception i m getting.
Anyone has a clue or advice of how to overcome this problem ?
20081107165952 Info   :Nov 7, 2008 4:46:03 PM   Info: Starting: Update: Selected development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0' updates currently deployed development component 'appl/main'/'com.diagonal'/'LOKAL'/'0.2006.01.12.14.18.23'/'0'.
20081107165952 Info   :Nov 7, 2008 4:46:03 PM   Info: SDA to be deployed: /usr/sap/WS5/JC00/SDM/root/origin/com.diagonal/appl/main/dev_devcias_C/0/823/appl~main.sda
20081107165952 Info   :Nov 7, 2008 4:46:03 PM   Info: Software type of SDA: J2EE
20081107165952 Info   :Nov 7, 2008 4:46:03 PM   Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: Begin of log messages of the target system:
20081107165952 Info   :08/11/07 16:46:03 - ***********************************************************
20081107165952 Info   :08/11/07 16:46:04 - Start updating EAR file...
20081107165952 Info   :08/11/07 16:46:04 - start-up mode is lazy
20081107165952 Info   :08/11/07 16:46:04 - EAR file updated successfully for 70ms.
20081107165952 Info   :08/11/07 16:46:04 - Start updating...
20081107165952 Info   :08/11/07 16:46:06 - EAR file uploaded to server for 861ms.
20081107165952 Info   :08/11/07 16:46:07 - ERROR: Not updated. Deploy Service returned ERROR:
20081107165952 Info   :                     java.rmi.RemoteException: Cannot deploy application com.diagonal/appl~main..
20081107165952 Info   :                     Reason: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
20081107165952 Info   :                          com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
20081107165952 Info   :                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:681)
20081107165952 Info   :                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
20081107165952 Info   :                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:313)
20081107165952 Info   :                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:199)
20081107165952 Info   :                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
20081107165952 Info   :                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
20081107165952 Info   :                          at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
20081107165952 Info   :                          at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
20081107165952 Info   :                          at java.security.AccessController.doPrivileged(AccessController.java:215)
20081107165952 Info   :                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
20081107165952 Info   :                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
20081107165952 Info   :                     Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
20081107165952 Info   :                          at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1050)
20081107165952 Info   :                          at com.sap.engine.services.webdynpro.WebDynproContainer.makeUpdate(WebDynproContainer.java:1281)
20081107165952 Info   :                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
20081107165952 Info   :                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
20081107165952 Info   :                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
20081107165952 Info   :                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
20081107165952 Info   :                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
20081107165952 Info   :                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
20081107165952 Info   :                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)
20081107165952 Info   :                          ... 10 more
20081107165952 Info   :                     For detailed information see the log file of the Deploy Service.
20081107165952 Info   :08/11/07 16:46:07 - ***********************************************************
20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: End of log messages of the target system.
20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Error: Aborted: development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0', grouped by :
20081107165952 Info   :Caught exception during application deployment from SAP J2EE Engine's deploy service:
20081107165952 Info   :java.rmi.RemoteException: Cannot deploy application com.diagonal/appl~main..
20081107165952 Info   :Reason: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is:
20081107165952 Info   :     com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application com.diagonal/appl~main. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
20081107165952 Info   : (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: Starting to save the repository
20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: Finished saving the repository
20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: Starting: Update: Selected software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.6.0.20081107075633''/'0' updates currently deployed software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.0.0.20061122075934''/'1'.
20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Error: Aborted: software component 'CIAS_WD_APPLICATIONS'/'diagonal.com'/'dev_devcias_C'/'1000.1.0.6.0.20081107075633''/'0':
20081107165952 Info   :Failed deployment of SDAs:
20081107165952 Info   :development component 'appl/main'/'com.diagonal'/'dev_devcias_C'/'823'/'0' : aborted
20081107165952 Info   :Please, look at error logs above for more information!
20081107165952 Info   :Nov 7, 2008 4:46:07 PM   Info: Starting to save the repository
20081107165952 Info   :Nov 7, 2008 4:46:08 PM   Info: Finished saving the repository
20081107165952 Info   :Nov 7, 2008 4:46:08 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
20081107165952 Info   :Nov 7, 2008 4:46:08 PM   Error: -
At least one of the Deployments failed -
20081107165952 Info   :end of log
20081107165952 Info   :RC of deployment: 12
20081107165952 Info   :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2008-11-07 16:59:52.0155 +9:00

"caching-descriptor" must be declared error when using ejbc on WLS6.0 with EJB 1.1

I'm compiling with ejbc an entity bean .jar. Using WLS 6.0. In the ejb-jar.xml,
I've set version to EJB 1.1. I've made sure the weblogic-ejb-jar.xml has the caching-descriptor
element defined (used to work with WLS 5.1).
Thanks.
Sayid
Error is : org.xml.sax.SAXParseException: Element type "caching-descriptor" must
be declare d. at weblogic.apache.xerces.framework.XMLParser.reportError(XMLParser.java
:1008) at weblogic.apache.xerces.validators.common.XMLValidator.reportRecoverab
leXMLError(XMLValidator.java:1236) at weblogic.apache.xerces.validators.common.XMLValidator.validateElement
AndAttributes(XMLValidator.java:2673) at weblogic.apache.xerces.validators.common.XMLValidator.callStartElemen
t(XMLValidator.java:818) at weblogic.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher
.dispatch(XMLDocumentScanner.java:1222) at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
mentScanner.java:380) at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:128 ) at
weblogic.ejb20.dd.xml.WebLogicEjbJarLoader_WLS600.process(WebLogicEjb JarLoader_WLS600.java:455)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:9 3) at
weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:4 7) at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:3
8) at weblogic.ejbc20.runBody(ejbc20.java:665) at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.ejbc.main(ejbc.java:20) --------------- nested within: ------------------
weblogic.xml.process.XMLParsingException: Element type "caching-descriptor" must
be declared. - with nested exception: [org.xml.sax.SAXParseException: Element
type "caching-descriptor" must be declar ed.] Line: 8 Column: 27 at weblogic.xml.process.ProcessorDriver.process(ProcessorDriver.java:132
) at weblogic.ejb20.dd.xml.WebLogicEjbJarLoader_WLS600.process(WebLogicEjb JarLoader_WLS600.java:455)
at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:9 3) at
weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:4 7) at weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:3
8) at weblogic.ejbc20.runBody(ejbc20.java:665) at weblogic.utils.compiler.Tool.run(Tool.java:81)
at weblogic.ejbc.main(ejbc.java:20) ERROR: weblogic.xml.process.XMLParsingException:
Element type "caching-descripto r" must be declared. - with nested exception:
[org.xml.sax.SAXParseException: Element type "caching-descriptor" must be declar
ed.] Line: 8 Column: 27

but a bean's deployment descriptor lies in the
meta-inf folder, right?Sorry, my mistake. I was thinking of WAR files while writing. Thanks for pointing out.
Regards,
$ Carol.

Deployment problems when using several ejb-jar files

Hello All,
I am having problems with deployment of my J2EE application. My EAR file has several EJB-JARs, one for each entity bean. However I refer to the other EJBs in one EJB. Hence I included the <ejb-ref> element in the deployment descriptor of the entity bean. But I am getting the deployment error that "the bundle does not contain the bean name". I tried to change the <ejb-name> value (within the <ejb-ref> element) to the JNDI name of the EJB I am referring to, and also added the <ejb-link> tag specifying the location of the JAR file that has the EJB. None of the attempts worked.
Can someone help me out on how I am supposed to go about when I have several ejb-jar files as opposed to a single one? I am deploying my app on Sun ONE AS 7.0.
Thank you,
PS: I am posting this message on several forum topics. Please disregard this message if you have seen/answered this message. Thanks.

Hi ,
It would help if you could post the relevant snippets of your
ejb-jar.xml. In general, you definitely shouldn't use jndi-name
for any of the linking information. jndi-name is not part of the
standard deployment descriptor. The syntax for the ejb-link is
[ejb-jar uri]#ejb-name
K

Weblogic 10.3.0 Deployment error when using ejb-jar.xml

Similar Messages

Maybe you are looking for