EJB deployment problems using ear

Hi,
I am able to deploy the ejbs in exploded format, but when I deploy
them in an ear, I see 'EJB Deployed message' on the start up console.
But when my servlet is trying to create the EJB, I am getting
CreateException. What is the reason for that?
Thanks,
Mark Pluta

Mark
You'll probably receive more help if you print out the stack trace... in the meanwhile..
there are some things to make sure.. verify that in the application.xml of your
ear file you have your ejb's declared, in the console view the JNDI tree and make
sure that the ejb's are on there as well.. viewing the stacktrace might be able
to get you more help though
Chris
Mark Pluta <[email protected]> wrote:
Hi,
I am able to deploy the ejbs in exploded format, but when I deploy
them in an ear, I see 'EJB Deployed message' on the start up console.
But when my servlet is trying to create the EJB, I am getting
CreateException. What is the reason for that?
Thanks,
Mark Pluta

Similar Messages

EJB deployment problems

I'm trying to deploy my business component as an EJB to Oracle 8.1.7. Actually, it deploys with no errors. When I test the module by setting the middle tier type to Local, it works fine. But, when I set the middle tier type to EJB, I can't see any data when I try to show my business component view.
So, I tried to deploy my applet and run it against the EJB, but I get an error in a Panic dialog box that says "Unknown service::session0". The details say
"DAC-405: SessionInfo:Application module creation failed; className: MyBcModule
Unknown service::session0
At the same time, the message view shows the following:
oracle.dacf.dataset.DataSourceOperationException: SessionInfo: Application module creation failed; className: MyBcModule
void oracle.dacf.dataset.ProducerObject.open(boolean)
void oracle.dacf.dataset.SessionInfo.publishSession()
void EISGui2.EISGuiApplet2.init()
void sun.applet.AppletPanel.run()
void java.lang.Thread.run()
The applet will run just fine when I set the session object to a local deployment type. I went through the trouble shooting stuff in the online help made sure my java_pool_size was set to at least 50MB, and that I have no unresolved java classes on the server. But, it still won't work. Are there any suggestions on what else I can try?

Of course, now I have other problems. After successfully redeploying my new business component as an EJB, and testing the application module successfully as an EJB middle tier server type, I created a new project as described in the online help under "Testing a Business Components EJB Deployed to Oracle8i with a Code Client." I followed the online help's instructions dilligently. Does it work? Of couse not. I'm turning on debugoutput with -Djbo.debugoutput=console so I can get more information, but that information isn't helping me. Refering back to the online help's code, it's crashing on the "ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup(DeployedMod)" line. Here's my exception stack:
[00] Diagnostic Properties: Timing:false Functions:false Linecount:true Threshold:6
[01] CommonMessageBundle (language base) being initialized
[02] Stringmanager using default locale: 'null'
[03] BC4JDeployPlatform: Ejb
[04] Connected to Service:sess_iiop://fredws:2481:ORCL
[05] Logging in...
javax.naming.NamingException: Unknown reasons. Root exception is
java.lang.ClassNotFoundException: EisBc.common.ejb.EisBcModuleHomeHelper
void oracle.jbo.client.remote.ejb.aurora.AuroraEJBAmHomeImpl.initRemoteHome()
void oracle.jbo.client.remote.ejb.aurora.AuroraEJBAmHomeImpl.<init>(oracle.jbo.JboContext, java.lang.String)
oracle.jbo.common.JboHome oracle.jbo.client.remote.ejb.aurora.AuroraEJBInitialContext.createJboHome(java.lang.String)
java.lang.Object oracle.jbo.common.JboInitialContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
void tester.EisBcTester.main(java.lang.String[])
Now, how can the EJB tester work, but my code can't find the helper class? I know my JNDI path is correct. I've checked to make sure that the EisBc.common.ejb.EisBcModuleHomeHelper class actually exists in the database and is valid. I've run java2perm.sql to grant permissions to my user. And, my java_pool_size is over 60MB.
This is frustrating. Did I see a thread about someone wanting to go back to VB...

JDev 3.0/Oracle8i EJB deployment problems

When trying to deploy a simple EJB generated with the JDev 3
wizards, I get the following errors:
*** Executing deployment profile E:\Program
Files\Oracle\JDeveloper 3.0\myprojects\queueRemote.prf ***
*** Generating archive file E:\Program Files\Oracle\JDeveloper
3.0\myprojects\queueRemoteSource.jar ***
Compiling the project...done
Validating the profile...done
Initializing deployment...done
Scanning project files...done
Generating classpath dependencies...done
Generating archive entries table...done
*** Archive generation completed ***
*** Deploying the EJB to JServer ***
EJB deployment argument list:
"E:\Program Files\Oracle\JDeveloper 3.0\java\bin\javaw"
"-DPATH=E:\Program Files\Oracle\JDeveloper 3.0\bin;E:\Program
Files\Oracle\JDeveloper 3.0\java\bin"
-classpath
"E:\Program Files\Oracle\JDeveloper 3.0
\java\lib\classes.zip;E:\Program Files\Oracle\JDeveloper 3.0
\lib\jdeveloper.zip;E:\Program Files\Oracle\JDeveloper 3.0
\myclasses;E:\Program Files\Oracle\JDeveloper 3.0\lib\jdev-
rt.zip;E:\Program Files\Oracle\JDeveloper 3.0
\jdbc\lib\oracle8.1.5\classes111.zip;E:\Program
Files\Oracle\JDeveloper 3.0\lib\connectionmanager.zip;E:\Program
Files\Oracle\JDeveloper 3.0\lib\javax_ejb.zip;E:\Program
Files\Oracle\JDeveloper 3.0
\aurora\lib\aurora_client.jar;E:\Program Files\Oracle\JDeveloper
3.0\aurora\lib\vbjorb.jar;E:\Program Files\Oracle\JDeveloper 3.0
\aurora\lib\vbjapp.jar;E:\Program Files\Oracle\JDeveloper 3.0
\aurora\lib\vbjtools.jar;E:\Program Files\Oracle\JDeveloper 3.0
\aurora\lib\vbj30ssl.jar;E:\Program Files\Oracle\JDeveloper 3.0
\java1.2\jre\lib\rt.jar;E:\Program Files\Oracle\JDeveloper 3.0
\aurora\lib\aurora_client.jar;E:\Program Files\Oracle\JDeveloper
3.0\aurora\lib\vbjorb.jar;E:\Program Files\Oracle\JDeveloper 3.0
\aurora\lib\vbjapp.jar;E:\Program Files\Oracle\JDeveloper 3.0
\aurora\lib\vbjtools.jar;E:\Program Files\Oracle\JDeveloper 3.0
\aurora\lib\vbj30ssl.jar;E:\Program Files\Oracle\JDeveloper 3.0
\jdbc\lib\oracle8.1.5\classes111.zip"
oracle.aurora.ejb.deployment.GenerateEjb
-u
sys
-p
sys
-s
sess_iiop://localhost:2481:ORCL
-republish
-keep
-temp
TEMP
-descriptor
"E:\Program Files\Oracle\JDeveloper 3.0
\myprojects\queueRemote.dd"
-generated
"E:\Program Files\Oracle\JDeveloper 3.0
\myprojects\queueRemoteGenerated.jar"
"E:\Program Files\Oracle\JDeveloper 3.0
\myprojects\queueRemoteSource.jar"
org.omg.CORBA.INTERNAL[completed=MAYBE]
at
com.visigenic.vbroker.orb.GiopConnectionFactoryImpl.destroy
(GiopConnectionFactoryImpl.java:209)
at com.visigenic.vbroker.orb.GiopConnectionImpl.close
(GiopConnectionImpl.java:544)
at com.visigenic.vbroker.orb.GiopStubDelegate.invoke
(GiopStubDelegate.java:609)
at com.visigenic.vbroker.orb.GiopStubDelegate.invoke
(GiopStubDelegate.java:466)
at org.omg.CORBA.portable.ObjectImpl._invoke
(ObjectImpl.java:141)
at oracle.aurora.AuroraServices._st_LoginServer.O3Logon_B
(_st_LoginServer.java:194)
at oracle.aurora.client.Login.authenticate
(Login.java:143)
at oracle.aurora.jndi.sess_iiop.SessionCtx.login
(SessionCtx.java:574)
at oracle.aurora.jndi.sess_iiop.SessionCtx.login
(SessionCtx.java:568)
at oracle.aurora.jndi.sess_iiop.ServiceCtx.login
(ServiceCtx.java:299)
at
oracle.aurora.server.tools.sess_iiop.ToolImpl.initializeSession
(ToolImpl.java:101)
at
oracle.aurora.server.tools.sess_iiop.ToolImpl.parseStdArgs
(ToolImpl.java:213)
at oracle.aurora.server.tools.sess_iiop.ToolImpl.invoke
(ToolImpl.java:121)
at oracle.aurora.ejb.deployment.GenerateEjb.main
(GenerateEjb.java:509)
*** Errors occurred while deploying the EJB to JServer ***
*** Deployment completed ***
Any suggestions as to what is happening would be greatly
appreciated.
Sean
null

Assuming that you have done the 'right' tinkg and changed the
password for the user SYS, then you are running into a JServer
bug. When the password file on the server and the user SYS
password in the rdbms get out of synch, this bug crops up (the
instance will be killed, immediately and with prejudice). The
solution is to:
-shut down the rdbms
-disable the password file in the INIT.ORA by setting the
parameter to EXCLUSIVE. Sorry the exact parameter change escapes
me at the moment, I have posted it earlier in this forum so you
can probably find it there if you don't already know it.
-restart the rdbms and change the sys password (again)
-you can then re-enable the password file if you need.
That's it. You will now be able to connect as SYS either via the
deployejb utility or session shell w/o bringing down the
database.
null

EJB deployment problem --New remote interface class files are not loaded

Hi, I face a problem while deploying an ear file in oc4j. I basically get some problems like the method in the remote interface is not implemented in the EJB class. But the implementation is actually available in the EJB class.
We get this problem when we actually change the signature of the EJB remote methods. The new methods are not referenced by oc4j. Only the old version of remote interface is referenced by oc4j. But the latest version of EJB class is taken. I am using 9.0.3 version of the oc4j. Could you pls help me regarding this problem ?
Regards
Solomon

I have found the solution :-)
You must add to the ejbCreate() method of the bean class throws javax.ejb.CreateException

EJB deployment problem

I am trying to deploy a simple EJB Wrapper of an application module onto OAS right now. I have followed the procedures listed in the JDeveloper online help, but after shooting down several other problems, I got the following error:
JBO-25222: Unable to create application module.
javax.ejb.CreateException: JBO-25222: Unable to create application module.
According to the online help, I am supposed to create the application module and initialize the database connection in the EJB's ejbCreate() method. To accomplish that, I need to call create() in the ApplicationModuleHome retrieved by the lookup() call in the InitialContext. The create() method, however, is throwing exception saying that application modules cannot be created. Just wondering if I have done something incorrect, and if there are other alternatives for making connections to the database and creating application modules. Any help is deeply appreciated. Thanks.

I came through the same problem when I wanted to directly access a BC4J from a servlet. It took me a week to find out why - What happens is that the BC4J class looks for the XML-files and class of its entities and it directly accesses it without a given path. What you would expect is that those files have to be in the same directory as the other classes. No - you have to put the class in a directory which the OAS accesses when no directory is given.
How do you find out? Write a class which writes a file and look where the file is created. Then put your BC4J-package (including xmls) into that directory (in my case orant\bin and at myfriends oas' orant\ows\4.0\admin\cgi --- with the OAS 4.0.8.1 it seems not be deterministic - even the hotline has confirmed that).
To be honest,i think it is a problem of the OAS not using the right path but this is it. Since then my servlet runs and I will soon try out what you are already doing.
Can you do me a favour and send me your example-EJB to further work on that topic?
([email protected]).
Regards,
Stefan

EJB Deployment Problem for Stateless Session with Multiple ejbCreate

In weblogic server if I use multiple ejbCreate with different parameters it is found
to raise error with error message :
<Error deploying application cart:
Unable to deploy EJB: cart.jar from cart.jar:
     In EJB CartBean, the stateless session bean class must define a single ejbCreate
method that takes no parameters.
     at weblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:256)
     at weblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:220)
     at weblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:453)
     at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:410)
     at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:203)
     at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
     at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:676)
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:843)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.addComponent(Application.java:160)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at ......
Code example...
public void ejbCreate() throws CreateException {}
public void ejbCreate(String person) throws CreateException {
// code here
public void ejbCreate(String person, String id) throws CreateException {
// code here
the code above is found ok in J2ee Ref. Implementation and able to deploy. Why this
is not deployable in Weblogic(tried in 6.1).is it a required condition for stateless
session bean
to have only single ejbcreate with no parameters ?
Can somebody explain? and is there a way out to overcome this constraint if so in
weblogic
with regards
Ganeshan Kalembeth

Stateless session beans may define only a single create() method with no
suffix
and no arguments.
Michael Jouravlev wrote:
"Ganeshan Kalembeth" <[email protected]> wrote in message
news:3ce28a88$[email protected]..
In weblogic server if I use multiple ejbCreate with different parametersit is found
to raise error with error message :
<Error deploying application cart:
Unable to deploy EJB: cart.jar from cart.jar:
In EJB CartBean, the stateless session bean class must define a singleejbCreate
method that takes no parameters.
atweblogic.ejb20.compliance.EJBComplianceChecker.check(EJBComplianceChecker.ja
va:256)
atweblogic.ejb20.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBCompli
anceChecker.java:220)
atweblogic.ejb20.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:453)
at weblogic.ejb20.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:410)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:203)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:676)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:843)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:160)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at ......
Code example...
public void ejbCreate() throws CreateException {}
public void ejbCreate(String person) throws CreateException {
// code here
public void ejbCreate(String person, String id) throws CreateException {
// code here
the code above is found ok in J2ee Ref. Implementation and able to deploy.Why this
is not deployable in Weblogic(tried in 6.1).is it a required condition forstateless
session bean
to have only single ejbcreate with no parameters ?
Can somebody explain? and is there a way out to overcome this constraintif so in
weblogic
with regards
Ganeshan KalembethRTFM EJB 2.0 Spec, chapter 7.8

EJB Deployment Error using JDeveloper3.1

While deploying a session bean (in which I am instantiating a user defined class) to the Oracle Server 8.1.6 using JDeveloper 3.1, I am getting the following error -
"Class not found during deserialization of descriptor".
Why is this error coming?
Do i need to change anything like setting any permissions to the oracle schema which i am using?
Thanks in Advance.
null

When I install the same standalone OC4J version via:
1. setting JAVA_HOME to JDK 1.4.2
2. unpacking the OC4J zip-file
3. running oc4j -start
The application can be deployed.
Does this mean that the default JDK at the time OC4J is installed can not be changed later on?!
Regards, Ronald

HTC PDA deployment problem using Mobile Module

Hi all,
I am trying to connect my HTC PDA Kaiser (TyTN II) to a customized device using the miniUSB port. This PDA runs Windows Mobile 6, I am using Labview 8.6 (and I am using the Mobile Module - former PDA module) on Windows Vista.
However, I am having a couple of issues trying to do this. Initially I am trying to discover, if the application deployed on the PDA using Mobile Module sees the miniUSB port as a virtual COM port (or serial). This would make my job much easier.
Nevertheless, way before that, I simply cannot deploy my application on the PDA because there are two files missing during the building process(attached file): windows.h and commctrl.lib, according to the message error.
I was trying to follow the simple tutorial on http://www.ni.com/pdf/manuals/371296d.pdf but the deployment process stops when I get this message. I installed all the necessary files (Virtual PC 2007, Windows Mobile Device Center and I think LV does the rest) and of course the mobile module. I read about the installation known issues, uninstalling Visual Studio 2008, reinstalling Labview like some of the threads suggested (http://forums.ni.com/ni/board/message?board.id=170&requireLogin=False&thread.id=132656) and still didn't work. I wouldn't go that far to reinstall Windows, would I?
I know that it might be something related to a wrong path according to the attached log error file during the C generation code, however I am still not sure what's the path supposed to be!
Does anyone could give any suggestions?
Kind regards,
Edgar Charry
Attachments:
Error Msg.jpg ‏166 KB
BuildReport.txt ‏1 KB

Hi Anna,
Thanks for the reply. Yes, it is Windows Vista 32-bit Home.
Certainly the reason is that the builder looks after these two files, that simply doesn't exist. I know it, because I looked for them, and found on the PocketPC2003 - smartphone folder (..\Labview 8.6\PDA\Utilities\VC\Smartdevices\SDK\PocketPC2003\include and lib). And the only one I can at least emulate is indeed the PocketPC2003 SmartPhone!
So, if your emulator for the Windows Mobile 6 platform works (emulates any VI), could you please give me the correct path of the Windows Mobile 6 and also the files? Here I have: ..\Labview 8.6\PDA\Utilities\VC\Windows Mobile 6 SDK\PocketPC\Deviceemulation\Pocket_PC (and a couple of others, which are pretty much empty - no header files or libraries there, just the PNG files of the figures of the emulators). That's it.
I tried copying the lib and the include folders there, but also didn't work....
Thanks Anna,
Edgar Charry

Ejb deploying problem

weblogic.management.DeploymentException: Error while loading descriptors: Error processing file 'META-INF/application.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear to contain a properly formed DOCTYPE header - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header]

javax.xml.stream.XMLStreamException: javax.xml.stream.XMLStreamException: Premature end of file encountered
at weblogic.xml.stax.XMLStreamReaderBase.prime(XMLStreamReaderBase.java:80)
at weblogic.xml.stax.XMLStreamReaderBase.setInput(XMLStreamReaderBase.java:99)
at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:316)
at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:49)
at weblogic.application.descriptor.BasicMunger2.<init>(BasicMunger2.java:110)
at weblogic.application.descriptor.BasicMunger2.<init>(BasicMunger2.java:128)
at weblogic.application.descriptor.VersionMunger.<init>(VersionMunger.java:74)
at weblogic.application.descriptor.VersionMunger.<init>(VersionMunger.java:63)
at weblogic.servlet.internal.WlsWebAppReader2.<init>(WlsWebAppReader2.java:59)
at weblogic.servlet.internal.WebAppDescriptor$MyWlsWebAppDescriptor.createXMLStreamReader(WebAppDescriptor.java:316)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:402)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
Any Suggestions plz???
Thanks

Ejb and jsproc deployment problems

Am trying to deploy the java stored procedure (jsp) example
(jsproc subdirectory in acmevideo directory) and the enterprise
java bean (ejb) example (ejb subdirectory in acmevideo
directory). Both use the business and util subdirectries of
acmevideo directory. These examples are provided with
JDeveloper.
In the case of the jsp example, the files compile fine in
JDeveloper. The deployment profile file is created okay using
the Stored Procedure Profile Wizard. But when the jsp is
attempted to be deployed by right clicking the deployment
profile file menu in JDeveloper, the following errors appear:
SQL error during creation of acmevideo/util/DataWrapper
ORA-00922 - missing or invalid option
SQL error during creation of acmevideo/business/TitleQueries
ORA-00922 - missing or invalid option
Is there a corrective action for these errors? Are the details
recorded in any log so that these errors can be troubleshooted?
In the case of the jbe example, the files compile fine in
JDeveloper. The deployment profile file is created okay using
the EJB Profile Wizard. But when the jsp is attempted to be
deployed by right clicking the deployment profile file menu in
JDeveloper, the following happens:
The message indicating that the deployment will take a few
minues continues to show forever. There is no completion,
and one is forced to cancel the process.
This happens when using the port settings of 1521, 1526 (Oracle
listener ports) or 2651 (OAS ORB port). Specifying the service
or omitting it yeilds the same results.
Is there a corrective action for this? Are the details recorded
in any log so that these errors can be troubleshooted?
For both the situations, is the classpath variable need to set
outside the JDeveloper environment?
Also am not able to locate the Oracle 8i CORBA and Enterprise
Java Beans Developer's Guide and the Oracle 8i Java Stored
Procedure Developer's Guide referenced in Building Java
Applications for Oracle 8i anywhere.
Would appreciate any help in this area.
null

: Has anyone been able to deploy an ejb from JDeveloper2 (Beta)?
We have ;) But I guess that doesn't count... Please have a look
at the online demo for Enterprise JavaBeans on this technet
website. You can get there through the JDeveloper Tech Info page.
Please open a new thread if that doesn't help you.
Thanks,
-Roel.
phil gulesian (guest) wrote:
: mark tomlinson (guest) wrote:
: : pretty sure the first one is a bug that is fixed in a later
: : build of JDeveloper (JSP deployment problem).
: : As for the EJB deployment problem, here is the way to catch
: what
: : is really going on (in the Beta build -- this will be done
much
: : better in the production build):
: : -edit the jdeveloper.ini (in the BIN directory), in the
: : [environment] section add:
: : LogConsole=1
: : -edit the jdeveloper.properties file (in the LIB directory)
: : change the line :
: : jdeveloper.logOutput=nul
: : to
: : jdeveloper.logOutput=-
: : Now when you run JDeveloper, you will get an output onsole
: : window for the JVM running JDeveloper. You will be able to
see
: : the deployment messages for the EJB wizard being sent to this
: : console. This will allow you to troubleshoot what is
happening.
: I had the same experience as Bansi (above) when I tried to
deploy
: a simple ejb. Following your suggestions about looking in the
: output console window for the JVM, I observed the message
: "PropertyEditor for borland.sql.dataset.ProcedureDescriptor
could
: not be registered ........" A subsequent search found no
: ProcedureDescriptor in the borland.sql.dataset package.
: Has anyone been able to deploy an ejb from JDeveloper2 (Beta)?
null

Deployment problems EAR & WAR

I have serious problems deploying an EAR, containing 25 ejb-jars and 3 wars.
The history of the project is that it was first developed on WLS 4.5 & 5.1. We
have later moved to Orion were the actual development takes place. Now we can
run the application on Orion and WLS 5.1. We now want to deploy the application
on WLS 6.1 sp 2. We have setup the whole application to be deployed as one EAR,
this works fine with Orion. The whole building is made in Ant.
I'm new on WLS 6.1 but have worked a lot on WLS 5.1 and 4.5 (I think it was).
I might have missed something but the documentation on EAR is very short.
When I first deploy the EAR, it seemed to work fine according to the console,
however when I tried to access servlets or JSPs, they simply weren't there (Error
404--Not Found). When I deployed the EAR from the console I got a number of zipexceptions.
After asking around, I was recommended to remove the compression in the jar,war
& earfiles. When I did that I got a number of errors in static initializers in
EJBs, which indicated that the EJBs actually were deployed. I fixed those and
the application was deployed without errors (when I start WLS and the EAR is deployed
by being in the config.xml file). Still when I deploy it from the console it still
throws ZipExceptions.
Anyway now I can access one of the war files but the other is not there. The deployed
war file is a lot smaller than the one not being deployed.
I think that all settings in application.xml, web.xml etc is correct. I'm also
confident that modules are correct, it does work in Orion, which has similar classloading.
From other developers, I have heard that I need to use WLS 6.1 sp 2, no compression
and that I have to break up large EARs in smaller (my EAR is 6,5 MB) files.
What really annoys me that I do not seem to get any errors, logs or anything.
The console indicates that everything is deployed even if apparently is not.
And I can deploy PerStore and everything works. If I deploy the wars, and ejbs
from the console (one at a time), it works.
I would appreciate any help on this subject any workarounds etc. I think that
I have to skip my first intent and deploy an exploded EAR instead of having (almost)
the same deployement as in Orion, which kind of pisses me of. I am also disappointed
that BEA has apperantly skipped java-modules all together. It is after all in
the specification.
I have talked to a number of people and they say that the whole EAR deployment
in WLS is very shaky. Is this true?
Thanks in advance,
Erik Romson

EAR deployment works fine from my own experience. Use JAR and turn off
compression for the WARs and JARs and the EAR itself, although I've never
seen a ZIP exception and I use JAR and ZIP and Winzip and whatever else I
can grab to muck with the files. 6.5MB is not tiny, but it isn't very large
either -- WL can handle much bigger EARs. Normally we don't suggest having
so many JARs and WARs in the EAR, but that is more preference ... are you
using manifest class path? ... are you referring to any of the files in the
WARs from any of the classes in the JARs?
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Erik Romson" <[email protected]> wrote in message
news:[email protected]...
>
I have serious problems deploying an EAR, containing 25 ejb-jars and 3wars.
The history of the project is that it was first developed on WLS 4.5 &5.1. We
have later moved to Orion were the actual development takes place. Now wecan
run the application on Orion and WLS 5.1. We now want to deploy theapplication
on WLS 6.1 sp 2. We have setup the whole application to be deployed as oneEAR,
this works fine with Orion. The whole building is made in Ant.
I'm new on WLS 6.1 but have worked a lot on WLS 5.1 and 4.5 (I think itwas).
I might have missed something but the documentation on EAR is very short.
When I first deploy the EAR, it seemed to work fine according to theconsole,
however when I tried to access servlets or JSPs, they simply weren't there(Error
404--Not Found). When I deployed the EAR from the console I got a numberof zipexceptions.
After asking around, I was recommended to remove the compression in thejar,war
& earfiles. When I did that I got a number of errors in staticinitializers in
EJBs, which indicated that the EJBs actually were deployed. I fixed thoseand
the application was deployed without errors (when I start WLS and the EARis deployed
by being in the config.xml file). Still when I deploy it from the consoleit still
throws ZipExceptions.
Anyway now I can access one of the war files but the other is not there.The deployed
war file is a lot smaller than the one not being deployed.
I think that all settings in application.xml, web.xml etc is correct. I'malso
confident that modules are correct, it does work in Orion, which hassimilar classloading.
>
From other developers, I have heard that I need to use WLS 6.1 sp 2, nocompression
and that I have to break up large EARs in smaller (my EAR is 6,5 MB)files.
>
What really annoys me that I do not seem to get any errors, logs oranything.
The console indicates that everything is deployed even if apparently isnot.
>
And I can deploy PerStore and everything works. If I deploy the wars, andejbs
from the console (one at a time), it works.
I would appreciate any help on this subject any workarounds etc. I thinkthat
I have to skip my first intent and deploy an exploded EAR instead ofhaving (almost)
the same deployement as in Orion, which kind of pisses me of. I am alsodisappointed
that BEA has apperantly skipped java-modules all together. It is after allin
the specification.
I have talked to a number of people and they say that the whole EARdeployment
in WLS is very shaky. Is this true?
Thanks in advance,
Erik Romson

Deploying EJB JAR and Application EAR, META-INF directory name

To all:
I had a problem the last couple of days with deploying an EJB and application.
I'm new to WebLogic, maybe this is common knowledge, but I researched it and
didn't find any reference to what I discovered.
I'm using WebLogic Server 7 Service Pack 2 (7.02), on Windows 2000.
My problem was that the application that I was trying to deploy would not deploy
successfully, because a dependent class was not found for the EJB. I tried everything,
but the only thing I could get to work was placing the dependent jar files in
the classpath of the WebLogic server, within the start script. I correctly had
the Class-Path manifest line correct, but the dependent classes were not being
found.
Through trial and error I discovered that the META-INF directory within the JAR
and EAR archives HAS TO BE ALL UPPERCASE for the app server to successfully find
the manifest.mf file and the application.xml file.
As soon as I changed the directory name in both the EJB JAR file and the application
EAR file, the EJB deployed successfully, all dependent classes were then found.
I'm posting this here to help anybody that might have the same problem. There
is not any documentation that I could find that had this directory name requirement
explicitly stated.
Regards,
JD

What does the manual for the OC4J application server have to say about it all?

Memory leak in a client using EJBs deployed in a Bea Weblogic 10.0.0 cluste

Hi all,
We are having a memory leak in a client using stateless EJBs deployed in cluster. The client is a Tomcat 6.0.18 with java 6 but it is reproduced using Tomcat 5 with java 5. The client is calling a Weblogic Server 10.0 making
calls to an EJB deployed in cluster that has two instances installed in two different machines.
The client works fine if we shutdown one of the server instances and so when the client is using only one instance.
Resuming the environment:
Client Side:
1 HP-Itanium machine with HP-UX.
1 Tomcat 6 with java 6 (reproduced with java 5)
Bea Weblogic client (wlclient.jar) for Weblogic 10.0.0
Server Side:
2 HP-Itanium machines with HP-UX
Bea Weblogic Server 10.0.0 installed in both machines
An unique domain
Two Bea instances (one per machines) associated to a Bea Cluster
EJBs deployed in both instances
We have monitored the memory consumed in Tomcat and we have noticed that the VM memory PS OLD GEN grows up permanently when we make tests having the two server side Bea Instances up. We have extended
the memory VM parameters in Tomcat client till 1G and it's only a way to delay the end: the free memory is empty, the GC is not able to free no more byte and the CPU is 100% consumed by the GC work. At the end Tomcat Client
doesn't accept more http petitions and must be restarted.
Besides, we have studied the VM memory in Tomcat using jmap and importing it using Eclipse Memory Analyzer. We have seen some strange memory blocks of several Mbytes that are always growing up and that are stored
under data structures in the package com.sun.corba:
com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl (4.5Mb)
|
-> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl
|
-> java.util.Hashtable
|
-> java.util.Hashtable$Entry
|
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
Has anybody any idea about this problem?
Thanks in advance.

Hi all,
We are having a memory leak in a client using stateless EJBs deployed in cluster. The client is a Tomcat 6.0.18 with java 6 but it is reproduced using Tomcat 5 with java 5. The client is calling a Weblogic Server 10.0 making
calls to an EJB deployed in cluster that has two instances installed in two different machines.
The client works fine if we shutdown one of the server instances and so when the client is using only one instance.
Resuming the environment:
Client Side:
1 HP-Itanium machine with HP-UX.
1 Tomcat 6 with java 6 (reproduced with java 5)
Bea Weblogic client (wlclient.jar) for Weblogic 10.0.0
Server Side:
2 HP-Itanium machines with HP-UX
Bea Weblogic Server 10.0.0 installed in both machines
An unique domain
Two Bea instances (one per machines) associated to a Bea Cluster
EJBs deployed in both instances
We have monitored the memory consumed in Tomcat and we have noticed that the VM memory PS OLD GEN grows up permanently when we make tests having the two server side Bea Instances up. We have extended
the memory VM parameters in Tomcat client till 1G and it's only a way to delay the end: the free memory is empty, the GC is not able to free no more byte and the CPU is 100% consumed by the GC work. At the end Tomcat Client
doesn't accept more http petitions and must be restarted.
Besides, we have studied the VM memory in Tomcat using jmap and importing it using Eclipse Memory Analyzer. We have seen some strange memory blocks of several Mbytes that are always growing up and that are stored
under data structures in the package com.sun.corba:
com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl (4.5Mb)
|
-> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl
|
-> java.util.Hashtable
|
-> java.util.Hashtable$Entry
|
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
Has anybody any idea about this problem?
Thanks in advance.

Problem using a library with an EAR file (ServletNotFoundException)

Hello
I'm trying to use a library (J2EE library project) an associated it to an Enterprise Application Project.
The application was built using the Spring MVC framework.
When I did deploy I got the following warning:
Apr 25, 2006 9:44:17 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[004]Finished Deployment
And when I try to run the application I got the following error:
404 Not Found
The request cannot be processed.
Details:   com.sap.engine.services.servlets_jsp.server.exceptions.ServletNotFoundException: Cannot load the requested servlet [data-entryLib/servlet/data-entry]. The ID of this error is
Exception id: [00306E5DA8D2004E00000068000052550004124234F31271].
The application run properly when I use the jars file in the WEB-INF/lib folder.
I have been reading some recomendations in this forum, but nobody tell me how to solve this problem
Thanks
Adriana.

Hi Rajesh
Thanks for your answer.
Yes, I deployed the .sda file, add the jars file in the archive server/provider.xml and I checked this: (Problem with EAR referencing a library DC)
The type of reference that I gave in the EAR file was in the archive application-j2EE-engine.xml:
<reference
    reference-type="hard">
    <reference-target
      provider-name="sap.com"
    target-type="library">LibreriaDataEntry</reference-target>
</reference>
<provider-name>sap.com</provider-name>
   <fail-over-enable
   mode="disable"/>
Thanks
Adriana

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

EJB deployment problems using ear

Similar Messages

Maybe you are looking for