EJB deployment issue in websphere

EJB deployment issue in websphere
I have created an EJB project in eclipse and created a stateless session bean successfully.
I created Enterprise application project and added the EJB project.
I tried to check it using Universal test client.
When I click the JNDI explorer>>sample.HelloWorldEJBHome
I get error IWAD0401E Unknown type of JNDI object
But when I install an EJB jar using administrator console after exporting the jar file for the EJB project
It is working file
I like to reduce the number of steps by right clicking the server publish and test.
Do any one have come across the same issue please help me
Thanks in advance.

Hi,
i have not done any changes to any process. I have created new DC and created new process.
new DC is not getting deployed with error "Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration". If you will check error log above then you will find it their.

Similar Messages

OIA - Clustered deployment issue in Websphere

Hi,
In our environment, we have OIA 11g BP6 11.1.1.3.6 to be deployed in a clustered environment. The deployment is completed successfully but only one of the instance is accessible, the other instance is failing to connect to the database. But when I deploy it as a standalone, instances on both the nodes work properly. Did anyone face such issue in Websphere? Were you able to resolve this through a workaround? pls let me know.
Below is my software versions
OIA 11g BP6 11.1.1.3.6
Oracle 11.2.0
Websphere 7.0.0,.7
Thanks,
Jaya

Hi Sam
1. Just curious, for ReDeployment, why are you UnDeploying existing process and application. This sounds little scary specially the undeploying of process. Because if process is undeployed from EM Console, it is supposed to remove the instances of that process and clean up the soa_infra database. Ideally speaking say we deployed HelloWorld Process, we did testing and once undeployed we expect all the instances to be removed. It may not be doing that right now, but still it sounds scary. We never did Undeployment. We just keep redeploying the process. Sometimes, if there are major changes, we change the version number and deploy the new version of process. We are using BPM 11.5 + FP.
2. Coming to your issue with Task not going to next state, I would say first look into the logs for any errors or exceptions. Then look into EM Console, the FlowTrace and see the task flow. Generally this happens, if there are any errors. Also from JDeveloper, select your TaskForms project, right click -> Project Properties -> Deployment -> Select your deployment profile and see what is the WebApplications Context Root. There are 2 options. One is default out of box which is something like "MyApp-MyTaskForms-context-root" and the other is "/workflow/MyTaskForms". See which radio button is checked. I use, the second more user friendly one. Go to your EM Console, select your Process. Click on any of the tasks included in that process. Go to Administration tab. Look the values for Host, port and mainly for URI which in my case is: /workflow/MyTaskForms/faces/adf.task-flow?xxxxxxxx
3. Where exactly are you changing the context root to fix this. We don't have to do this everytime we redeploy. It may be working due to some other reasons.
Thanks
Ravi Jegga

ZipFile closed: EJB Deployment Issue

Hi all,
I am facing problems in the Ejb deployment. Please read the following
V r using Weblogic 7.0 with jdk1.4
Just take a luk at steps performed
1. V compiled all the source code, the ejbc compilation and the .ear generation thru ant(v 1.5) build scripts with JDK1.4.1
2. When v tried deployin the .ear file, it gave the error in the particular EJB jar file stating
"unable to deply Ejb bean, Error: ZipFile Closed"
however, if the 1st step is performed using JDK1.4.0_02-b02 version of JDK1.4, the deployment goes on pretty fine. I just wonna know if u or any of your colleague have faced similar problems, the cause of it and the workarounds.
Cheers,
Manjunath Rane

Don't scratch ur head guys....i found the solution. Just apply Weblogic 7.0 sp1. Couldn't find the cause though. There is one potential possiblity.
I was using <ZipFileSet> task of Ant 1.5 to build the EJb Jar File. The Ant documents clearly says that using the above task would cause the generation of .java file thur <javac> would lock up the .class files. I presume that these locked file were being jarred. The deployment thus would have failed due to unability to open the closed files. hence the error.....
Cheers,
Manja

Ejb deployment issue

Hello,
I am trying to deploy an ejb to a cluster. It deployes fine on primary node (where I am running the dcmctl deployapplication command). However, on the secondary node it fails. It can't find generated classes. When I am looking at the server, all the generated classes are present at the root of the home container (I am deploying to a different container amd NOT in home container). I am not sure why the generated classes are in home, and why it can't find it...
So the overall deployment fails with resync error. When I look at dcmctl getsate, primary node is all ok, however secondary node is not in synch.
By generated means wrapper classes like this -
UpdateEngineLocal_StatelessSessionBeanWrapper6.class
InsertEngine_StatelessSessionBeanWrapper4.class
UpdateEngine_StatelessSessionBeanWrapper8.class
thanks
Shailesh

I have the same error. I am trying to call a EJB from a client serval times. the first times it goes well but after a while I get this error on the client side:
Cannot access remote service [no.norgesgruppen.b2b.ejb.varebok.VareBokEJB]; nested exception is com.evermind.server.rmi.OrionRemoteException: Disconnected: Unknown command: 2
And this error on the server side:
06/12/04 15:46:54 INFO: RMIProtocol.readConnectionHeader Local ORMI version = 1.3 different from remote version 1.0 will use 1.0
04.des.2006 15:46:54 com.evermind.server.rmi.RMIProtocol readConnectionHeader
INFO: Local ORMI version = 1.3 different from remote version 1.0 will use 1.0

Can't lookup an EJB deployed in Orion AS rom JDeveloper 10.1.3

Everything was OK when the EJB has been looked up from a standalone application. But when it hang up when the lookup was done from a web application .
Please help me,
          Hashtable environment = new Hashtable();
          // Specify the emd-rmi SPI
          environment.put("java.naming.factory.initial", "com.evermind.server.rmi.RMIInitialContextFactory");
          // Specify the host
          environment.put("java.naming.provider.url", "ormi://localhost:23791/appname");
          // Specify username - this must be an admin account on the remote server
          environment.put("java.naming.security.principal", "admin");
          // Password
          environment.put("java.naming.security.credentials", "admin");
          InitialContext context = new InitialContext(environment);
//Context ctx = new InitialContext();
Object obj = context.lookup("ejbname");
Error message.
2006-02-07 15:46:48.541 NOTIFICATION Industrial Telnet Server version: Version 10.1.3.0.0 started-up successfully.
06/02/07 15:49:21 INFO: RMIProtocol.readConnectionHeader Local ORMI version = 1.3 different from remote version 1.0 will use 1.0
07.feb.2006 15:49:20 com.evermind.server.rmi.RMIProtocol readConnectionHeader
INFO: Local ORMI version = 1.3 different from remote version 1.0 will use 1.0

I guess you are facing the same problem as I am:
ADF-EJB deployment issue (urgent)
Too new ormi protocol for older Application Servers.

Issues in looking up a ejb deployed on glassfish from tomcat.

Hi all,
I have followed the steps mentioned in the EJB FAQ in the glassfish site and was able to lookup a remote ejb deployed in glassfish from a standalone client.
In case of standalone client, i set the appropriate jndi properties in the initial context as mentioned in the FAQ and added the 4 jars specified to the classpath of the application.
It all worked perfectly well.
But I attempted to do the same from a servlet running under tomcat.
I set the appropriate jndi properties in the intial context and added 4 jars specified in the lib directory of the war file.
But this did not turn out well and tomcat complained me with some servlet init errors.
Then i searched through the web and found this posting from you:
http://www.archivesat.com/GlassFish_Enterprise_JavaBeans_Developers/thread1399339.htm
Then i created a folder called "shared/lib" under TOMCAT_HOME directory in my machine and ran the same example. Wow.....miraculously the application ran well.
But i found that the "index.jsp" which i configured in the welcome file list does not appear now. But i was able to access the servlet without any problem. And the servlet was able to successfully lookup the ejb deployed in glassfish.
Then i thought, let me try to access the ejb from a jsf application.
Then i created a jsf application in netbeans 5.5.1 and tried to access the bean deployed in glassfish.
(Note: the jsf application runs in tomcat 5.5.17 which is bundled with netbeans)
OOPSS....
Tomcat now complains me that it cannot compile the jsp page..
This is the error i got...
org.apache.jasper.JasperException: Unable to compile class for JSP
Generated servlet error:
C:\Documents and Settings\james\.netbeans\5.5.1\apache-tomcat-5.5.17_base\work\Catalina\localhost\CityExplorer-WebClient1\org\apache\jsp\index_jsp.java:7: org.apache.jsp.index_jsp is not abstract and does not override abstract method getDependants() in org.apache.jasper.runtime.JspSourceDependent
public final class index_jsp extends org.apache.jasper.runtime.HttpJspBase
^
Generated servlet error:
C:\Documents and Settings\james\.netbeans\5.5.1\apache-tomcat-5.5.17_base\work\Catalina\localhost\CityExplorer-WebClient1\org\apache\jsp\index_jsp.java:12: getDependants() in org.apache.jsp.index_jsp cannot implement getDependants() in org.apache.jasper.runtime.JspSourceDependent; attempting to use incompatible return type
found : java.lang.Object
required: java.util.List
public Object getDependants() {
^
2 errors
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)
Any ideas...
Can you please help me.
I've noticed that you were eagerly answering questions related to ejb lookup in many places.
I feel there is some potential compatability issue between tomcat and glassfish...
I request you to investigate on this and clarify the community with your response.
Thanks in advance,
James Selvakumar

Thank you guys!
I've found the answer myself.

How to call EJB deployed on websphere from JSP running on Tomcat?

I am trying to establish communication between two app servers. I have a sample EJB deployed on Websphere and wish to call its business methods from a JSP page which is running on Apache Tomcat server. (ie) Tomcat is client to websphere. Is it possible to do? If so, what are the client Jar files of websphere that I should make available to JSP page on Tomcat? Do I need to set any Jars in Tomcat environment variables? Lood forward for your immediate help. Thanks in advance

Please see the thread
http://forum.java.sun.com/thread.jspa?threadID=514536.
Hope that helps..

Problem running Java client of EJB deployed on WebSphere

Hi,
I am using websphere studio 5.1.2 with fix pack 3. I have a sample Stateless Session Bean (EJB) deployed and running on websphere.
I wrote a small Java client program as below.
import java.util.Hashtable;
import HelloJavaHome;
import HelloJava;
import javax.naming.InitialContext;
import javax.naming.Context;
import javax.ejb.EJBHome;
import javax.ejb.EJBObject;
public class RemoteConn {
public static void main(String[] ar) throws Exception{
String greeting = "";
try{
Hashtable env = new Hashtable();
//env.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
//env.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.ejs.ns.jndi.CNInitialContextFactory");
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.ws.naming.util.WsnInitCtxFactory");
//env.put(Context.PROVIDER_URL, "corbaloc:iiop:myhost.mycompany.com:2809/NameServiceCellPersistentRoot");
env.put(Context.PROVIDER_URL, "iiop://localhost:2809");
System.out.println("Before creating context ");
InitialContext initContext = new InitialContext(env);
System.out.println("Before looking up HelloJavaHome.");
//Object obj = initContext.lookup("java:comp/env/ejb/HelloJavaHome");
Object obj = initContext.lookup("ejb/HelloJavaHome");
System.out.println("After lookup javahome.");
HelloJavaHome home = (HelloJavaHome) javax.rmi.PortableRemoteObject.narrow(obj, HelloJavaHome.class);
HelloJava remote = home.create();
greeting = remote.getGreeting("John");
catch(Exception e){
e.printStackTrace();
System.out.println("Greeting::"+ greeting);
I did not have any problem if I write and run this client from Websphere studio environment..
However its giving lot of compilation and runtime errors when I tried to run from command line.
I could eliminated compilation errors by setting the below jar files in the classpath.
testclient.jar; (client jar of my EJB)
j2ee.jar;
naming.jar;ras.jar;
wsexception.jar;
bootstrap.jar;
namingclient.jar;
websphere.jar;server.jar;
ejbcontainer.jar;
ecutils.jar;
Now it is throwing runtime error after the statement, "Before looking up HelloJavaHome.", has printed. Here is the stack trace of exception ..
Exception in thread "main" java.lang.NoClassDefFoundError: com.ibm.CORBA.iiop.GlobalORBFactory
at com.ibm.ejs.oa.EJSORBImpl.class$(EJSORBImpl.java:44)
at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:195)
at com.ibm.ejs.oa.EJSClientORBImpl.(EJSClientORBImpl.java:93)
at com.ibm.ejs.oa.EJSClientORBImpl.(EJSClientORBImpl.java:65)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:385)
at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:284)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:369)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:112)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:422)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:143)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at RemoteEJBConn.main(RemoteEJBConn.java:38)
I appreciate if sombody could help me ASAP fixing this problem.
Thanks in advance.

Try using the IBM JVM (theres one shipped with WebSphere in websphere_home\AppServer\java
Also include idl.jar and ffdc.jar on the classpath

Deployment issues, how is weblogic-ejb-jar.xml linked to ejb-jar.xml

Hey guys,
I'm getting the following error I think because i have something configured incorrectly in my xml files. Instead of yousing activationConfig properties in my MDB I wanted to set them in the ejb-jar.xml file manually. The following error I'm getting is...
Unable to deploy EJB: MyMDB from MDBtest2:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'inQueue' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
 at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:641)
 at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:330)
 at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1097)
 at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:991)
 at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
 at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
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>MDBtest2</display-name>
 <enterprise-beans>
 <message-driven>
 <ejb-name>MyMDB</ejb-name>
 <ejb-class>cms.crown.mdb.MyMDB</ejb-class>
 <transaction-type>Container</transaction-type>
 <message-destination-link>omg</message-destination-link>
 <resource-ref>
 <res-ref-name>weblogic.jms.XAConnectionFactory</res-ref-name>
 <res-type>javax.jms.XAConnectionFactory</res-type>
 <res-auth>Container</res-auth>
 </resource-ref>
 <resource-env-ref>
 <resource-env-ref-name>inQueue</resource-env-ref-name>
 <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
 </resource-env-ref>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <container-transaction>
 <method>
 <ejb-name>MyMDB</ejb-name>
 <method-name>onMessage</method-name>
 <method-params>
 <method-param>javax.jms.Message</method-param>
 </method-params>
 </method>
 <trans-attribute>Required</trans-attribute>
 </container-transaction>
 </assembly-descriptor>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-ejb-jar xmlns:wls="http://www.bea.com/ns/weblogic/10.0" 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 http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">

<wls:message-destination-descriptor>

<wls:message-destination-name>omg</wls:message-destination-name>
<wls:destination-jndi-name>inQueue</wls:destination-jndi-name>
<wls:initial-context-factory>weblogic.jms.XAConnectionFactory</wls:initial-context-factory>
<wls:provider-url>http://localhost:8010</wls:provider-url>
</wls:message-destination-descriptor>
</wls:weblogic-ejb-jar>
Hope this is readable, thanks for any assistance

Hi,
It looks like first thing you are using EJB3 but your XML files are still pointing to version="2.1" and very old.

<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">
 
*try this: In below "ejb-jar.xml" file*
QCF = your Connection factory JNDI Name
TestQ = your Queue JNDI Name
Transaction Attribute is ByDefault = Required ...so no need to add it here.
<?xml version='1.0' encoding='UTF-8'?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" metadata-complete="true">
<enterprise-beans>
<message-driven>
<ejb-name>MyMDB</ejb-name>
<mapped-name>TestQ</mapped-name>
<ejb-class>cms.crown.mdb.MyMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Container</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>connectionFactoryJndiName</activation-config-property-name>
<activation-config-property-value>QCF</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>destinationJndiName</activation-config-property-name>
<activation-config-property-value>TestQ</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>
</enterprise-beans>
<assembly-descriptor></assembly-descriptor>
</ejb-jar>
"weblogic-ejb-jar.xml":
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd">
 Now u need to Just define the Provider URL here...if you want a remote provider...else not required JNDI names are already defined in the ejb-jar.xml file 
</weblogic-ejb-jar>
Some Links which you can refer:
To Generate the Deployment Descriptors ...in case of EJB3 Applications: *http://jaysensharma.wordpress.com/2010/04/02/generating-ejb3-clientjar/*
MDB3.0 Sample: *http://jaysensharma.wordpress.com/2009/08/17/mdb3-0-sample-for-weblogic-application-server/*
Thanks
Jay SenSharma

EJB deployment aborted : UnsupportedClassVersionError

Hi All,
I am working on ejb project , i have created entity , session bean build it successfully. even i hv created EJB application Dc , which also deployed successfully. Then i createde webservice for session bean and tried to deploy , but deployment aborted and i am getting following error.
Mar 12, 2008 3:31:49 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [ThreadDeploy Thread,5,main] INFO:
004Additional log information about the deployment
<!LOGHEADERSTART/>
<!HELPManual modification of the header may cause parsing problem!/>
<!LOGGINGVERSIONhttp://1.5.3.7186 - 630/>
<!NAME[/usr/sap/J2E/JC00/SDM/program/log/sdmcl20080312081657.log]/>
<!PATTERNhttp://sdmcl20080312081657.log/>
<!FORMATTERcom.sap.tc.logging.TraceFormatter(%24d %s: %m)/>
<!ENCODINGISO8859_1/>
<!LOGHEADEREND/>
Mar 12, 2008 1:46:58 PM Info:
Starting deployment
Mar 12, 2008 1:46:58 PM Info: Error handling strategy: OnErrorStop
Mar 12, 2008 1:46:58 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Mar 12, 2008 1:46:58 PM Info: Update strategy: UpdateAllVersions
Mar 12, 2008 1:46:58 PM Info: Starting deployment prerequisites:
Mar 12, 2008 1:46:58 PM Info: Loading selected archives...
Mar 12, 2008 1:46:58 PM Info: Loading archive '/usr/sap/J2E/JC00/SDM/program/temp/temp37374asianpaints.com~probsEA.ear'
Mar 12, 2008 1:47:10 PM Info: Selected archives successfully loaded.
Mar 12, 2008 1:47:10 PM Info: Actions per selected component:
Mar 12, 2008 1:47:10 PM Info: Initial deployment: Selected development component 'probsEA'/'asianpaints.com'/'J2E_BODYSHOP_D'/'20080312153111' will be deployed.
Mar 12, 2008 1:47:11 PM Info: Ending deployment prerequisites. All items are correct.
Mar 12, 2008 1:47:11 PM Info: Saved current Engine state.
Mar 12, 2008 1:47:11 PM Info: Starting: Initial deployment: Selected development component 'probsEA'/'asianpaints.com'/'J2E_BODYSHOP_D'/'20080312153111' will be deployed.
Mar 12, 2008 1:47:11 PM Info: SDA to be deployed: /usr/sap/J2E/JC00/SDM/root/origin/asianpaints.com/probsEA/J2E_BODYSHOP_D/20080312153111/temp37374asianpaints.com~probsEA.ear
Mar 12, 2008 1:47:11 PM Info: Software type of SDA: J2EE
Mar 12, 2008 1:47:11 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2008 1:47:14 PM Info: Begin of log messages of the target system:
08/03/12 13:47:11 - ***********************************************************
08/03/12 13:47:12 - Start updating EAR file...
08/03/12 13:47:12 - start-up mode is lazy
08/03/12 13:47:12 - EAR file updated successfully for 256ms.
08/03/12 13:47:12 - Start deploying ...
08/03/12 13:47:13 - EAR file uploaded to server for 391ms.
08/03/12 13:47:14 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application asianpaints.com/probsEA..
Reason: Exception during generation of components of application asianpaints.com/probsEA in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application asianpaints.com/probsEA in container EJBContainer.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application asianpaints.com/probsEA in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3139)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:539)
... 10 more
Caused by: java.lang.UnsupportedClassVersionError: com/apil/Userdetails/UserdetailsBean (Unsupported major.minor version 50.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at com.sap.engine.frame.core.load.ResourceLoader.loadLocalClass(ResourceLoader.java:262)
at com.sap.engine.frame.core.load.ResourceLoader.loadClass(ResourceLoader.java:127)
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:353)
at com.sap.engine.services.ejb.deploy.xml.CMPParser.parseFields(CMPParser.java:116)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:174)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:297)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:247)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2144)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 16 more
For detailed information see the log file of the Deploy Service.
08/03/12 13:47:14 - ***********************************************************
Mar 12, 2008 1:47:14 PM Info: End of log messages of the target system.
Mar 12, 2008 1:47:14 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Mar 12, 2008 1:47:14 PM Error: Aborted: development component 'probsEA'/'asianpaints.com'/'J2E_BODYSHOP_D'/'20080312153111':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application asianpaints.com/probsEA..
Reason: Exception during generation of components of application asianpaints.com/probsEA in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application asianpaints.com/probsEA in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Mar 12, 2008 1:47:27 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Mar 12, 2008 1:47:27 PM Error:
At least one of the Deployments failed
Please help me to resolve this issue
Regards
Ravi

Hi
see whether j2ee engine started or not?
Hazrath

Is it possible to monitor all calls into all EJBs deployed on a server?

Is there any way of monitoring all calls into the EJBs deployed in a server?
I'd like to be able to externally log the calls, and perhaps do some monitoring at the call level, without modifying the EJBs themselves. Something along the lines of servlet filters for servlets, but for EJBs instead..
JBoss has a nice plugin interface, and one could either extend the Logging plugin, or write another one, that can do this.
But is there an analog in other J2EE servers (e.g. weblogic and websphere)? Or is that a standard or clever way of intercepting all calls? (I suppose one could use Ethereal, but I was hoping for a higher-level solution).
Duke dollars available!

Hi,
In JBoss they use Log4J to log and intercept the Bean calls and JDBC calls. You can use Log4J to do the same with other servers also, cause I configured OC4J(Oracle 9iAS) Server to use log4J and it worked for me. I think other servers can also be configured to use log4j. I've only tried this with JBoss and OC4J. I don't have much experience with other servers.
So, my advise is : try LOG4J and try to configure server to use LOG4J
Hope this works!
Indy.

Best place to put startup code in EJB deployment?

Hi,
I'm working on an application which involves timer services and JMX, and I'd like to ask for your opinion on how to deal with startup of those services in an EJB deployment. If you dealt with those issues before, I'd appreciate it if you could share your experiences/best practices on the subject.
Timer services need to be started, and MBeans need to be registered with the MBeanServer, so I'd like to see how can this be done upon application deployment.
I'm using Sun Server as an EJB server.
Thanks,
Mark

Since the ejb spec doesn't define an application initialization event, the only portable way of doing this that I've heard of is to use the ServletContextListener.contextInitialized() event to send a message to an MDB within the same application. Since EJB Timers are persistent and their identity is tied to a particular application component, the MDB's onMessage method can use getTimers() to see whether the timer already exists. If not, it's the first time the application has been deployed.
I agree the auto-creation of timers upon deployment would be a good addition to the spec :-)
--ken

Ear deployment issue.

Hi,
i am using jdev Studio Edition Version 11.1.1.4.0
I have created EAR of my application and trying to depoly it on Weblogic server.
I have following entry in weblogic-application.xml
<library-ref>
<library-name>adf.oracle.domain</library-name>
</library-ref>
[03:12:39 PM] ---- Deployment started. ----
[03:12:39 PM] Target platform is (Weblogic 10.3).
[03:13:07 PM] Retrieving existing application information
[03:13:07 PM] Running dependency analysis...
[03:13:07 PM] Building...
[03:13:28 PM] Deploying 3 profiles...
[03:13:29 PM] Moving WEB-INF/adfc-config.xml to META-INF/adfc-config.xml
[03:13:30 PM] Wrote Archive Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventoryManagerUi.jar
[03:13:38 PM] Wrote Web Application Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventory.war
*[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-api.jar*
*[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-impl.jar*
[03:13:38 PM] removed bundleresolver.jar from lib because it cannot be part of an EJB deployment
[03:13:54 PM] Wrote Enterprise Application Module to /home/kpophale/CDMR/13June/frontend/deploy/AppsInventoryManager.ear
[03:13:55 PM] Entering Oracle Deployment Plan Editor
[03:15:53 PM] Deploying Application...
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'bam_server1'. Deployment is deferred until 'bam_server1' becomes available.; nested exception is:
 java.rmi.UnknownHostException: Could not discover administration URL for server 'bam_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'osb_server1'. Deployment is deferred until 'osb_server1' becomes available.; nested exception is:
 java.rmi.UnknownHostException: Could not discover administration URL for server 'osb_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'soa_server1'. Deployment is deferred until 'soa_server1' becomes available.; nested exception is:
 java.rmi.UnknownHostException: Could not discover administration URL for server 'soa_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'adf_server1'. Deployment is deferred until 'adf_server1' becomes available.; nested exception is:
 java.rmi.UnknownHostException: Could not discover administration URL for server 'adf_server1'.
[03:16:41 PM] [Deployer:149193]Operation 'deploy' on application 'AppsInventoryManager' has failed on 'AdminServer'
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'.
[03:16:41 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
*[03:16:41 PM] Caused by: java.lang.NoClassDefFoundError: org/apache/myfaces/trinidad/webapp/UIXComponentELTag*
[03:16:41 PM] See server logs or server console for more details.
[03:16:41 PM] weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
[03:16:41 PM] #### Deployment incomplete. ####
[03:16:41 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
I am getting above exception while i am trying to depoly the my ear. please see bold lines.
Please give me some guide line .
Regards,
Kiran.

Hi John,
Yes I have. I even tried on two seperate WebLogic installations. I noticed, even when I create just an ear file (not deploy to server), it gives me the same warnings about removing trinidad. Is there something i'm missing in JDeveloper?
For my installations:
On one Middleware home: I installed: WLS 10.3.5, ADF 11.1.1.5, then ADF 11.1.2 Patch 12611176. configured domain with all ADF/JRF libraries, followed by upgradeADF WLST command. I got same deployment issue.
On another middleware home: I even just installed JDeveloper 11.1.2, configured a new domain with all librearies. I got same deployment issue.
FYI: I also added the two Trinidad JSP Tag Libraries to my View Controller Project. I got same error.
Thank you,
Gavin
Edited by: GavinWoods on Feb 14, 2012 6:25 AM

IO error writing cache during ejb deployment

I am getting this error a lot when I deploy an ear to standalone oc4j. This happens when I run from the command line or from jdeveloper. Retrying it eventually works, sometimes to speed things up I shutdown oc4j and remove the file. Is there some way to prevent this from happening.
com.evermind.compiler.CompilationException: Error instantiating compiler: IO error writing cache: D:\oc4j\j2ee\home\application-deployments\WebTSApp\WebTSejb.jar\deployment.cache
at com.evermind.server.ejb.compilation.Compilation.compileClasses(Compilation.java:500)

This was a known issue before the preview release.
Workaround for the problem would be to change the Application name and EAR file name.
If you have the EJB deployment profile, Right mouse on it and choose Settings.
Change the name of the EAR file and the Application name and redeploy.
raghu
JDev Team

EJB Deployment - NoClassDefFoundError

Dear Gurus,
I am using Visual Age for Java 3.5.3 and WebSpehere 3.5.
I have create a EJB which throws a Custom Exception. It works fine in Visual Age for Java Test Environment. I created a Deployed JAR to deploy it in WebSphere App Server.
Custom Exception class package is inside a jar and command line arguments "-classpath " is set in the Web Sphere.
While deploying this WebSphere the following Exception is thrown.
java.lang.NoClassDefFoundError: packagename/classname
In addition to this exception there is some other dependant classes are also available in the same package. There is no exception thrown for those classes. I dont know why.
Please help me as this is blocking us to move forward.
Thanks in advance,
Goudham

Its problem with classpath . check it up the location of classfiles and the package. Set your classpath to that specific classfiles path. This solves your problem

EJB deployment issue in websphere

Similar Messages

Maybe you are looking for