Deployment of Ejb on OAS-4.0.8

****** error message got on deploying the jar file ********
Oracle Application Server Release 4.0.8.0.0 Standard Edition
Copyright (c) Oracle Corporation 1998. All rights reserved.
java.lang.ClassFormatError: Wrong name
at java.lang.ClassLoader.defineClass(Compiled Code)
at oracle.oas.tools.util.DefaultClassLoader.loadClass
(Compiled Code)
at oracle.oas.tools.util.DefaultClassLoader.loadClass
(Compiled Code)
at oracle.oas.tools.codegen.BeanInterfaceStruct.initNames
(BeanInterfaceStruct.java:472)
at oracle.oas.tools.codegen.BeanInterfaceStruct.
(Compiled Code)
at oracle.oas.tools.codegen.InputJarAnalyzer.getTargets
(Compiled Code)
at oracle.oas.tools.codegen.CodeGenerator.main(Compiled
Code)
Code generation for G:\\ORAAPP\\ows\\upload\\serverJar.jar
failed!
Creating registration files...
Unable to expand attribute Unable to load from
c:\temp\src\oasbae.properties
c:\temp\src\oasbae.properties
java.io.FileNotFoundException: c:\temp\src\oasbae.properties
at java.lang.Throwable.(Compiled Code)
at java.io.FileInputStream.(Compiled Code)
at
oracle.oas.tools.config.BeanAttributeExpander.getHomeClassName
(BeanAttributeExpander.java:215)
at oracle.oas.templates.MacroDefs.evaluate(Compiled Code)
at oracle.oas.templates.SimpleNode.expand(Compiled Code)
at oracle.oas.templates.SimpleNode.expand(Compiled Code)
at oracle.oas.templates.Processor.expand(Compiled Code)
at oracle.oas.templates.Processor.expand(Compiled Code)
at
oracle.oas.tools.config.OASConfigFileGenerator.genConfigFromTempl
ate(Compiled Code)
at
oracle.oas.tools.config.OASConfigFileGenerator.genConfigForEachBe
an(Compiled Code)
at oracle.oas.tools.config.OASConfigFileGenerator.pass2
(OASConfigFileGenerator.java:80)
at oracle.oas.tools.config.OASInstaller.generate
(OASInstaller.java:47)
at oracle.oas.tools.config.OASInstaller.main
(OASInstaller.java:24)
Deployment failed!

OK! Fixed that one myself - for now. I had used some wrong jar:s in my libraries.
There are still some problems.
If I use JDK 1.1.8, I get the following trace when trying to run my client:
java.lang.NoSuchMethodError: java.lang.System: method setProperty(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String; not found
at
at javax.naming.spi.NamingManager.getDefaultInitialContextFactory(NamingManager.java:696)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:744)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:181)
at javax.naming.InitialContext.<init>(InitialContext.java:158)
at test.BCEJBClient.main(BCEJBClient.java:32)
The problem goes away if I instead use JDK 1.2.2. But in the project I'm working on we are usng JDK 1.1.8. How can this problem be solved?

Similar Messages

FileNotFoundException thrown during deployment of EJB onto OAS

During the deployment of an EJB onto OAS, I got the following error messages:
<snipped>
Processing jar...
Analyzing Beans...
AppTierEJBClass
Code generation for E:\\Oracle\\OASHome\\ows\\upload\\242TestOASAppSource.jar has been completed.
Compiling generated code...
Creating client jar...
java.io.FileNotFoundException: E:\Oracle\OASHome\ows\4.0\..\apps\ejb\TestOASApp\_client.jar
at java.lang.Throwable.<init>(Compiled Code)
at java.io.FileNotFoundException.<init>(Compiled Code)
at java.io.FileOutputStream.<init>(FileOutputStream.java:69)
at sun.tools.jar.Main.run(Main.java:76)
at sun.tools.jar.Main.main(Main.java:524)
at oracle.oas.tools.util.JarGenerator.createJar(Compiled Code)
at oracle.oas.tools.util.CreateJars.main(Compiled Code)
Creation of client jar for E:\\Oracle\\OASHome\\ows\\upload\\242TestOASAppSource.jar failed!
Creating registration files...
Deployment information for application successfully generated.
<snipped>
Just wondering what is that file not found error? And what is the cause of that?
null

I guess that might be trying to redeploy the same EJB again onto OAS.
If that is the case you can try the following
cd to OAS_HOME/ows/admin/website40/httpd_machinename/admin/svadmin.cfg
and turn "FileCaching = OFF"
OAS_HOME/ows/admin/website40/httpd_machinename/www/svadmin.cfg
and turn "FileCaching = OFF"
Once you change the settings , you would need to shutdown OAS and restart it again.
the other workaroung would be to restart the appserver before the redeployment so that it would release the lock.
raghu

Invalid username/password connecting to deployed session EJB (to OAS)

Hello,
OAS version : 9.0.4.0.0
JDeveloper version : 10.1.2.0.0 (Build 1811)
I have generated a very simple session EJB with the EJB
Diagram : business logic is only a method returning a
"hello world" String (no DB connection).
Next i have generated a "New Sample Java Client" to test
that, first connecting to the Embedded OC4J and it worked
very well.
Then i wanted to deploy this small example to my OAS
server, so i created a new session EJB deployment profile.
Deployment worked very well too.
To test this, i generated another "New Sample Java
Client", but that time i choosed "Connect to Remote App
Server", with adequate J2EE application and App Server
Connection names.
I took note of the new context lines. Login/password
strings were automatically filled with the ones i use to
connect to OEM Website (lets say the_login/the_password).
But unfortunately, when i launch the client, it doesn't
work. Here is the error stack :
C:\jdev1012\jdk\bin\javaw.exe -ojvm -classpath C:\dev\jdev\mywork\DarkWork\DarkProject\classes;C:\jdev1012\jdev\lib\jdev-rt.jar;C:\jdev1012\j2ee\home\lib\activation.jar;C:\jdev1012\j2ee\home\lib\ejb.jar;C:\jdev1012\j2ee\home\lib\jaas.jar;C:\jdev1012\j2ee\home\lib\jaxp.jar;C:\jdev1012\j2ee\home\lib\jcert.jar;C:\jdev1012\j2ee\home\lib\jdbc.jar;C:\jdev1012\j2ee\home\lib\jms.jar;C:\jdev1012\j2ee\home\lib\jndi.jar;C:\jdev1012\j2ee\home\lib\jnet.jar;C:\jdev1012\j2ee\home\lib\jsse.jar;C:\jdev1012\j2ee\home\lib\jta.jar;C:\jdev1012\j2ee\home\lib\mail.jar;C:\jdev1012\j2ee\home\lib\servlet.jar;C:\jdev1012\j2ee\home\oc4j.jar;C:\jdev1012\opmn\lib\optic.jar;C:\jdev1012\lib\xmlparserv2.jar;C:\jdev1012\lib\xmlcomp.jar mypackage1.SessionEJBClient
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Invalid username/password for DarkEJB (the_login); nested exception is:
     javax.naming.AuthenticationException: Invalid username/password for DarkEJB (the_login) [Root exception is javax.naming.AuthenticationException: Invalid username/password for DarkEJB (the_login)]
     at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:168)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at mypackage1.SessionEJBClient.main(SessionEJBClient.java:18)
Caused by: javax.naming.AuthenticationException: Invalid username/password for DarkEJB (the_login)
     at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java:2523)
     at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java:2339)
     at com.evermind.server.rmi.RMIConnection.lookup(RMIConnection.java:1781)
     at com.evermind.server.rmi.RMIServer.lookup(RMIServer.java:663)
     at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:149)
     ... 2 more
Process exited with exit code 0.
Do you know what i can do to solve this problem ?
I saw several posts on this forum about that problem,
mostly in 2003, so perhaps it has been solved now.
I tried the solutions and workarounds mentioned in those
post, but the error is still there...
Thank you for your help ! :-)

When you are connecting through a hotels WiFi like this they may occasionally require you to login via a home web page, this is quite normal. In many cases the password for this will be provided at checkin and with this being the case it would be worth speaking with the front desk to see if they can assist you with this.
What are your thoughts about this forum? Let us know by doing this short survey.
- Official Sony Xperia Support Staff
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page.

Cannot deploy a EJB 3.0 Session bean to the OAS 10.1.3.4

Hi All,
I am unable to deploy a EJB 3.0 Session bean with no deployment descriptors to OAS 10.1.3.4 App server.This Session bean is also exposed as a web service using annotations. I am able to deploy this bean to a standalone oc4j 10.1.3.x containers and test it successfully.
i have written a simple stateless session bean ( exposed as webservice) and every bean is having issues with deployment having the same exception stated below
Can some one please help as i need to deploy this urgently.
below is the session bean code:
import javax.ejb.Stateless;
@Stateless(name="SiebelQuoteEJB")
public class SiebelQuoteEJBBean implements SiebelQuoteEJBLocal,
SiebelQuoteEJBWebService {
public SiebelQuoteEJBBean() {
public String publishMessage(String message,String type) throws java.rmi.RemoteException {
client.publishMessage(message,type);
return "SUCCESS";
Below is the error while deploying:
11/01/06 15:03:49 WARNING: Application.setConfig Application: javasso is in failed state as initialization failed.
java.lang.NullPointerException
11/01/06 15:03:50 WARNING: Application.setConfig Application: SiebelQuoteEJB is in failed state as initialization failed.
java.lang.InstantiationException: Error initializing ejb-modules: null Error parsing application-server config file: null
11/01/06 15:03:50 java.lang.NullPointerException
at com.evermind.server.ObjectReferenceCleaner.cleanupApplicationLogLevels(ObjectReferenceCleaner.java:166)
at com.evermind.server.ObjectReferenceCleaner.loaderDestroyed(ObjectReferenceCleaner.java:88)
at oracle.classloader.EventDispatcher.loaderDestroyed(EventDispatcher.java:248)
at oracle.classloader.PolicyClassLoader.close(PolicyClassLoader.java:1113)
at oracle.classloader.PolicyClassLoader.close(PolicyClassLoader.java:1041)
at com.evermind.server.ApplicationStateRunning.destroyClassLoaders(ApplicationStateRunning.java:1171)
at com.evermind.server.Application.stateCleanUp(Application.java:3635)
at com.evermind.server.Application.setConfig(Application.java:506)
at com.evermind.server.Application.setConfig(Application.java:355)
at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1895)
at com.evermind.server.ApplicationServer.initializeDeployedApplications(ApplicationServer.java:1651)
at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1034)
at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:131)
at java.lang.Thread.run(Thread.java:736)

which jdk version? Had this with 1.6 and had to install an up-to-date jdbc.

Error while deploying EJB on OAS 4.0.8.1

I have installed OAS 4.0.8.1 on Windows NT 4.0 with Support Pack 6a. The java compiler used is from JDK 1.1.6 provided with OAS.
The following error occurs while deploying EJB on OAS. The error is the same while deploying through the node manager or by using oasdeploy command line utility.
java.lang.NoClassDefFound Error
Code generation for
D:\\orant\\ows\\upload\\425BrowserBean.jar failed!
Creating registration files.....
Unable to expand attribute Unable to load from C:\temp\src425\oasbae.properties
Please let me know the possible causes for non deployment of the bean on OAS.
null

With JDev 3.1, we only support deployment to OAS 4.0.8.2.
JDev 3.0 supported deployment to OAS 4.0.8.1.
I believe most of this restriction is due to internal changes in OAS that we were only able to integrate with 3.1.

A simple EJB in OAS 4081

We failthfully followed the procedure given in technet.oracle.com/products/jdev (JDeveloper 3.0 Technical Information - Developing and Deploying EJBs using JDeveloper 3.0 and running the deployed EJB from a client application) to create an EJB.
We got the following error when we tried to run the client from JDeveloper.
"D:\jdeveloper\java1.2\jre\bin\javaw.exe" -mx50m -classpath "D:\jdeveloper\myclasses;D:\jdeveloper\lib\ejbapi.jar;D:\jdeveloper\lib\oasoorb.jar;D:\jdeveloper\myprojects\jayEJBCl.jar;D:\jdeveloper\lib\jdev-rt.zip;D:\jdeveloper\jdbc\lib\oracl e8.1.5\classes111.zip;D:\jdeveloper\lib\connectionmanager.zip;D:\jdeveloper\lib\javax_ejb.zip;D:\jdeveloper\java1.2\jre\lib\rt.jar" jayEJB.jayEJBClient
Creating an initial context
Looking for the EJB published as 'jayEJB/HelloEJB'
Naming exception occurred!
Cause: This may be an unknown URL, or some classes required by the EJB are missing from your classpath, or your OAS host is short of resources
Suggestion: Check the components of the URL, and make sure your project includes a library containing the EJB .jar files generated by the deployment utility.
[Root exception is org.omg.CORBA.NO_IMPLEMENT: minor code: 0 completed: No]javax.naming.ServiceUnavailableException
java.lang.Object oracle.oas.jndi.oas.SecCosNamingContext.resolve(javax.naming.Name, java.util.Hashtable)
java.lang.Object oracle.oas.jndi.oas.BeanContext.lookup(javax.naming.Name, java.util.Hashtable)
java.lang.Object oracle.oas.jndi.oas.BeanInitialContext.resolve(javax.naming.Name, java.util.Hashtable)
java.lang.Object oracle.oas.jndi.oas.BeanContext.lookup(javax.naming.Name, java.util.Hashtable)
java.lang.Object oracle.oas.jndi.oas.BeanInitialContext.lookup(javax.naming.Name, java.util.Hashtable)
java.lang.Object oracle.oas.jndi.oas.WrapperContext.lookup(javax.naming.Name)
java.lang.Object oracle.oas.jndi.oas.BeanContext.lookup(java.lang.String)
java.lang.Object javax.naming.InitialContext.lookup(java.lang.String)
void jayEJB.jayEJBClient.main(java.lang.String[])
Can anyone suggest the remedy ?
null

I don't know if this applies for you but this may help you:
"I am running OAS on Windows NT, and my client hangs during the JNDI home interface lookup. What can I do ?
If your OAS EJB client hangs, and then throws an exception similar to the one below during the JNDI home interface lookup, this is
probably due to the fact that the java process in which your application is supposed to run cannot be started.
[Root exception is org.omg.CORBA.NO_RESOURCES:
]javax.naming.InsufficientResourcesException
at oracle.oas.jndi.oas.SecCosNamingContext.resolve(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanInitialContext.resolve(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanInitialContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.WrapperContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at javax.naming.InitialContext.lookup(Compiled Code)
at appPackage.BeanClient.main(Compiled Code)
You can verify that by looking at the wrb.log file (located in ows/admin/website40/log). It should report that it failed to get the cartridge for your
application (yourAppName__) by a message similar to the one below:
12-01-1999 09:43:10 0 plemouel-pc `RM Proxy` 301 0 0x1200fff `OWS-25010:
Failed to get cartridge 'appPackage/__' for '360' times.
If your EJB is deployed in OAS on NT, and you have installed the JDK 1.2, or JRE1.2 on your machine don't look further. Even if your path and
classpath are set to use the correct 1.x JDK, OAS EJBs runtime uses the createProcess system command, which will cause the JDK1.2 JVM
to be loaded. This version of the JVM is not supported at the moment by OAS.
The reason behind this unfortunate behavior is twofold:
When you install JDK 1.2, the java.exe executable is also copied in the Windows system32 directory.
The system command we are using (createProcess) to start the JVM looks there first (MS design) before looking in the PATH
environment variable.
Therefore OAS tries to start your EJB application in JDK1.2 JVM, which is not supported at the moment.
We will fix this problem, but in the meantime, if you need to have the JDK1.2 on the same machine as your OAS installation. You will need to
edit the wrb.app (this file is located in directory ows\admin\website40\wrb) file after deploying your EJB.
In the wrb.app file look for:
[APPLICATION.myAppName]
where myAppName is the name of your EJB application. Below this tag, you should have the following line:
ExecString = javaw -mx64M oracle.oas.container.Main
Edit this line to add the javaw path. This should look something like this:
ExecString = c:\orant\ows\4.0\jdk\bin\javaw -mx64M oracle.oas.container.Main
Save the wrb.app file and then reload OAS.
If you have not installed the JDK1.2 or JRE1.2, your EJB has probably been deployed incorrectly. Check in directory
ows/apps/ejb/yourAppName to make sure that the following three files are present: _application.jar; _client.jar; and _server.jar."
null

Urgent!! Errors during one EJB calling other EJB in OAS

Hi, I got the following errors when I try to
use one Session EJB to call another Session EJB in OAS 4.0.8.1, the EJB is deployed to OAS from JDeveloper 3.0. The code I used to call other EJB is the same as the code in client side:
public String callAnotherEJB(String strXML)
throws RemoteException, CreateException {
String ejbUrl = "oas://scott:8889/Mapping3/Mapping3";
String result;
// Setup the environment
Hashtable environment = new Hashtable();
// Turn JNDI on to OAS
environment.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "oracle.oas.naming.jndi.RemoteInitCtxFactory");
// Lookup the URL
Mapping3Home homeInterface = null;
try {
Context ic = new InitialContext(environment);
homeInterface = (Mapping3Home)javax.rmi.PortableRemoteObject.narrow(ic.lookup(ejbUrl), Mapping3Home.class);;
result = remoteInterface.responseEJBCall(strXML);
return result;
catch (Exception e) {
e.printStackTrace();
return "error during invoking responseEJBCall: "+e.getMessage();
=====
The error is as follows:
Creating an initial context
CORBA: org.omg.CORBA.BAD_OPERATION: ; nested exception is:
org.omg.CORBA.BAD_OPERATION:
java.rmi.ServerException: CORBA: org.omg.CORBA.BAD_OPERATION: ; nested exception is:
org.omg.CORBA.BAD_OPERATION:
at javax.rmi.oas.corba.CorbaRemoteExceptionHelperValue.OBVObjFrom(Compiled Code)
at TwoEJB2._stub_APP_T2.callEJBMapping(Compiled Code)
at TwoEJB2.TwoEJB2Client.main(Compiled Code)
Can anyone help me?
Thanks!1
Scott
null

Using arrays instead of vectors, the Oracle WSDL toolkit was able to generate stubs/serializers for all my objects. Thanks for the tip! :)
For future reference though, is there any way at all for the Oracle WSDL toolkit to auto-generate stubs/serializers for objects wrapped inside a Vector?

[Jeveloper + EJB client - EJB on OAS] Problem connecting

I having problems getting a simple client from within JDeveloper 3.0(Code snippet - OAS/EJB Client) talking to a simple EJB on OAS 4.0.8.
I have deployed OK (red flag against status?) but when I run the client using port - 5512(ORB port)I get the message below
Anybody any ideas?
Creating an initial context
Looking for the EJB published as 'MyOASApp/MyEJB'
Naming exception occurred!
Cause: This may be an unknown URL, or some classes required by the EJB are missing from your classpath, or your OAS host is short of resources
Suggestion: Check the components of the URL, and make sure your project includes a library containing the EJB .jar files generated by the deployment utility.
[Root exception is java.net.UnknownServiceException: no content-type]javax.naming.NamingException: Failure to access http://hfxcap4:5512/ows-bin/rmproxy.ior; listener inaccessible or configured wrongly
at oracle.oas.jndi.oas.SiteResolver.getIOR(Compiled Code)
at oracle.oas.jndi.oas.SiteResolver.resolveListenerURL(Compiled Code)
at oracle.oas.jndi.oas.SiteResolver.resolveSiteContact(Compiled Code)
at oracle.oas.jndi.oas.SiteResolver.resolveSiteContact(Compiled Code)
at oracle.oas.jndi.oas.SiteResolver.resolveSiteObject(Compiled Code)
at oracle.oas.jndi.oas.BeanInitialContext.resolve(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanInitialContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.WrapperContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at javax.naming.InitialContext.lookup(Compiled Code)
at package1.MyOASAppClient.main(Compiled Code)
**************

HI, I have the same problem that you had, maybe did you manage through ?? Thanks for all the help you could bring me.
Nico
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by pFrooney:
Back Again ...
I have tried all ao the above
now using this code below but it fails on the lookup with the error message below:
..created library with client stub, using 1.1.8, moved OASRuntime to top of included libraries
Any suggestions
String oasUrl = "oas://hfxcap4:80";
String oasEJB = "MyOASApp/MyEJB" ;
// Setup the environment
Hashtable environment = new Hashtable();
// Turn JNDI on to OAS
environment.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "oracle.oas.naming.jndi.RemoteInitCtxFactory");
// Lookup the URL
conv_package.MyEJBHome homeInterface = null;
try {
System.out.println("Creating an initial context");
// Get initial JNDI context
Context site = (Context) ((new InitialContext(environment)).lookup(oasUrl));
org.omg.CORBA.COMM_FAILURE:
at oracle.oas.orb.CORBA.Request._invoke(Compiled Code)
at oracle.oas.orb.CORBA.Delegate._invoke(Compiled Code)
at org.omg.CORBA.portable.ObjectImpl._invoke(Compiled Code)
at oracle.oas.orb.CORBA.Delegate.is_a(Compiled Code)
at org.omg.CORBA.portable.ObjectImpl._is_a(Compiled Code)
at oracle.oas.jndi.oas.BeanInitialContext.resolve(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanInitialContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.WrapperContext.lookup(Compiled Code)
at oracle.oas.jndi.oas.BeanContext.lookup(Compiled Code)
at javax.naming.InitialContext.lookup(Compiled Code)
at CClient_package.MyOASAppClient.main(Compiled Code)<HR></BLOCKQUOTE>
null

Getting error while deploying the ejb in jboss3.2.3

i m getting following error msg while deploying my ejb in jboss-3.2.3. i m deploying the same code available at
http://www.ftponline.com/javapro/2003_01/online/j2ee_bkurniawan_01_09_03/
04:30:48,955 INFO [MainDeployer] Starting deployment of package: file:/home/ami
tt/jboss-3.2.3/server/default/deploy/StringProcessor.jar
04:30:48,972 ERROR [MainDeployer] could not create deployment: file:/home/amitt/
jboss-3.2.3/server/default/deploy/StringProcessor.jar
org.jboss.deployment.DeploymentException: ejb-jar.xml must define a valid DOCTYP
E!
at org.jboss.metadata.ApplicationMetaData.importEjbJarXml(ApplicationMet
aData.java:206)
at org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:141)
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:436)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:786)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea nDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy6.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen tScanner.java:302)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS canner.java:476)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. doScan(AbstractDeploymentScanner.java:201)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. loop(AbstractDeploymentScanner.java:212)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. run(AbstractDeploymentScanner.java:191)
Please reply me bak the required solution.......

looks like your xml files are not done.

Steps to deploy an ejb application and running an ejb client in weblogic server6.1

steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
if the client is an simple java application and if the client is a servlet

Hi.
Check out the beanManaged example that ships with WLS and read the accompanying docs. This
is a simple EJB with a servlet that invokes it.
Michael
shekhar sachdev wrote:
steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
if the client is an simple java application and if the client is a servlet--
Michael Young
Developer Relations Engineer
BEA Support

How deploy the EJB in security on the Sun Java System Application Server 9?

I hava deploied a simple Hello EJB Object on PE 9(Sun Java System Application Server Platform Edition 9). I can use this EJB object without user name an password On any client. See the following code section:
     public static void main(String[] args) {
          try{
               Properties props = System.getProperties();
               props.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.enterprise.naming.SerialInitContextFactory");
               props.put(Context.PROVIDER_URL,"iiop://localhost:3700");
               Context ctx = new InitialContext(props);
               Hello h = (Hello) ctx.lookup("ejb/test/Hello");
               System.out.println(h.sayHello());
          }catch(Exception e){
               e.printStackTrace();
Please tell me how deploy the EJB in security on the Sun Java System Application Server 9? So that, The client must set the user name and password when lookup the ejb object. Like the following:
props.put(Context.SECURITY_PRINCIPAL,"admin")
props.put(Context.SECURITY_CREDENTIALS,"1234");

Guys,
I too have the same issue. If anyone has an answer, please let me know.
Is this GlassFish problem? or Prgram issue?
Find below the source code
package TransactionSecurity.bean;
import javax.annotation.Resource;
import javax.annotation.security.DeclareRoles;
import javax.annotation.security.PermitAll;
import javax.annotation.security.RolesAllowed;
import javax.ejb.Remote;
import javax.ejb.SessionContext;
import javax.ejb.Stateless;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
@Stateless
@Remote(TSCalculator.class)
@DeclareRoles({"student", "teacher"})
public class TSCalculatorBean implements TSCalculator {
     private @Resource SessionContext ctx;
     @PermitAll
//     @TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
     public int add(int x, int y) {
          System.out.println("CalculatorBean.add Caller Principal:" + ctx.getCallerPrincipal().getName());
          return x + y;
     @RolesAllowed( { "student" })
     public int subtract(int x, int y) {
          System.out.println("CalculatorBean.subtract Caller Principal:" + ctx.getCallerPrincipal().getName());
          System.out.println("CalculatorBean.subtract isCallerInRole:" + ctx.isCallerInRole("student"));
          return x - y;
     @RolesAllowed( { "teacher" })
     public int divide(int x, int y) {
          System.out.println("CalculatorBean.divide Caller Principal:" + ctx.getCallerPrincipal().getName());
          System.out.println("CalculatorBean.divide isCallerInRole:" + ctx.isCallerInRole("teacher"));
          return x / y;
package TransactionSecurity.bean;
import javax.ejb.Remote;
@Remote
public interface TSCalculator {
        public int add(int x, int y);
        public int subtract(int x, int y);
        public int divide(int x, int y);
package TransactionSecurity.client;
import java.util.Properties;
import javax.ejb.EJBAccessException;
import javax.naming.Context;
import javax.naming.InitialContext;
import TransactionSecurity.bean.TSCalculator;
public class TSCalculatorClient {
     public static void main(String[] args) throws Exception {
          // Establish the proxy with an incorrect security identity
          Properties env = new Properties();
          env.setProperty(Context.SECURITY_PRINCIPAL, "kabir");
          env.setProperty(Context.SECURITY_CREDENTIALS, "validpassword");
        env.setProperty(Context.INITIAL_CONTEXT_FACTORY,"com.sun.appserv.naming.S1ASCtxFactory");
        env.setProperty(Context.PROVIDER_URL,"iiop://127.0.0.1:3700");
        env.setProperty("java.naming.factory.initial","com.sun.enterprise.naming.SerialInitContextFactory");
        env.setProperty("java.naming.factory.url.pkgs","com.sun.enterprise.naming");
        env.setProperty("java.naming.factory.state","com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl");
        env.setProperty("org.omg.CORBA.ORBInitialHost", "127.0.0.1");
        env.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
          InitialContext ctx = new InitialContext(env);
          TSCalculator calculator = null;
          try {
               calculator = (TSCalculator) ctx.lookup(TSCalculator.class.getName());
          } catch (Exception e) {
               System.out.println ("Error in Lookup");
               e.printStackTrace();
               System.exit(1);
          System.out.println("Kabir is a student.");
          System.out.println("Kabir types in the wrong password");
          try {
               System.out.println("1 + 1 = " + calculator.add(1, 1));
          } catch (EJBAccessException ex) {
               System.out.println("Saw expected SecurityException: "
                         + ex.getMessage());
          System.out.println("Kabir types in correct password.");
          System.out.println("Kabir does unchecked addition.");
          // Re-establish the proxy with the correct security identity
          env.setProperty(Context.SECURITY_CREDENTIALS, "validpassword");
          ctx = new InitialContext(env);
          calculator = (TSCalculator) ctx.lookup(TSCalculator.class.getName());
          System.out.println("1 + 1 = " + calculator.add(1, 1));
          System.out.println("Kabir is not a teacher so he cannot do division");
          try {
               calculator.divide(16, 4);
          } catch (javax.ejb.EJBAccessException ex) {
               System.out.println(ex.getMessage());
          System.out.println("Students are allowed to do subtraction");
          System.out.println("1 - 1 = " + calculator.subtract(1, 1));
}The user kabir is created in the server and this user belongs to the group student.
Also, I have enabled the "Default Principal To Role Mapping"
BTW, I'm able to run other EJB3 examples [that does'nt involve any
security features] without any problems.
Below is the ERROR
Error in Lookupjavax.naming.NamingException: ejb ref resolution error for remote business interfaceTransactionSecurity.bean.TSCalculator [Root exception is java.rmi.AccessException: CORBA NO_PERMISSION 0 No; nested exception is:
     org.omg.CORBA.NO_PERMISSION: ----------BEGIN server-side stack trace----------
org.omg.CORBA.NO_PERMISSION:   vmcid: 0x0 minor code: 0 completed: No
     at com.sun.enterprise.iiop.security.SecServerRequestInterceptor.handle_null_service_context(SecServerRequestInterceptor.java:407)
     at com.sun.enterprise.iiop.security.SecServerRequestInterceptor.receive_request(SecServerRequestInterceptor.java:429)
     at com.sun.corba.ee.impl.interceptors.InterceptorInvoker.invokeServerInterceptorIntermediatePoint(InterceptorInvoker.java:627)
     at com.sun.corba.ee.impl.interceptors.PIHandlerImpl.invokeServerPIIntermediatePoint(PIHandlerImpl.java:530)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.getServantWithPI(CorbaServerRequestDispatcherImpl.java:406)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:224)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1846)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1706)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:1088)
     at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:223)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:806)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.dispatch(CorbaMessageMediatorImpl.java:563)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.doWork(CorbaMessageMediatorImpl.java:2567)
     at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
----------END server-side stack trace---------- vmcid: 0x0 minor code: 0 completed: No]
     at com.sun.ejb.EJBUtils.lookupRemote30BusinessObject(EJBUtils.java:425)
     at com.sun.ejb.containers.RemoteBusinessObjectFactory.getObjectInstance(RemoteBusinessObjectFactory.java:74)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
     at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:403)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at TransactionSecurity.client.TSCalculatorClient.main(TSCalculatorClient.java:35)
Caused by: java.rmi.AccessException: CORBA NO_PERMISSION 0 No; nested exception is:
     org.omg.CORBA.NO_PERMISSION: ----------BEGIN server-side stack trace----------
org.omg.CORBA.NO_PERMISSION:   vmcid: 0x0 minor code: 0 completed: No
     at com.sun.enterprise.iiop.security.SecServerRequestInterceptor.handle_null_service_context(SecServerRequestInterceptor.java:407)
     at com.sun.enterprise.iiop.security.SecServerRequestInterceptor.receive_request(SecServerRequestInterceptor.java:429)
     at com.sun.corba.ee.impl.interceptors.InterceptorInvoker.invokeServerInterceptorIntermediatePoint(InterceptorInvoker.java:627)
     at com.sun.corba.ee.impl.interceptors.PIHandlerImpl.invokeServerPIIntermediatePoint(PIHandlerImpl.java:530)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.getServantWithPI(CorbaServerRequestDispatcherImpl.java:406)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:224)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1846)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1706)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:1088)
     at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:223)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:806)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.dispatch(CorbaMessageMediatorImpl.java:563)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.doWork(CorbaMessageMediatorImpl.java:2567)
     at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
----------END server-side stack trace---------- vmcid: 0x0 minor code: 0 completed: No
     at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:277)
     at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:205)
     at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:152)
     at com.sun.corba.ee.impl.presentation.rmi.bcel.BCELStubBase.invoke(BCELStubBase.java:225)
     at com.sun.ejb.codegen._GenericEJBHome_Generated_DynamicStub.create(com/sun/ejb/codegen/_GenericEJBHome_Generated_DynamicStub.java)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.sun.ejb.EJBUtils.lookupRemote30BusinessObject(EJBUtils.java:372)
     ... 5 more
Caused by: org.omg.CORBA.NO_PERMISSION: ----------BEGIN server-side stack trace----------
org.omg.CORBA.NO_PERMISSION:   vmcid: 0x0 minor code: 0 completed: No
     at com.sun.enterprise.iiop.security.SecServerRequestInterceptor.handle_null_service_context(SecServerRequestInterceptor.java:407)
     at com.sun.enterprise.iiop.security.SecServerRequestInterceptor.receive_request(SecServerRequestInterceptor.java:429)
     at com.sun.corba.ee.impl.interceptors.InterceptorInvoker.invokeServerInterceptorIntermediatePoint(InterceptorInvoker.java:627)
     at com.sun.corba.ee.impl.interceptors.PIHandlerImpl.invokeServerPIIntermediatePoint(PIHandlerImpl.java:530)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.getServantWithPI(CorbaServerRequestDispatcherImpl.java:406)
     at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:224)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1846)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1706)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:1088)
     at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:223)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:806)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.dispatch(CorbaMessageMediatorImpl.java:563)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.doWork(CorbaMessageMediatorImpl.java:2567)
     at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
----------END server-side stack trace---------- vmcid: 0x0 minor code: 0 completed: No
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
     at com.sun.corba.ee.impl.protocol.giopmsgheaders.MessageBase.getSystemException(MessageBase.java:913)
     at com.sun.corba.ee.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSystemException(ReplyMessage_1_2.java:131)
     at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(CorbaMessageMediatorImpl.java:685)
     at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(CorbaClientRequestDispatcherImpl.java:472)
     at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:363)
     at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:219)
     at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:192)
     ... 13 moreAny help is appreciated.
Regards!
Nithi.
Edited by: EJB3 on Aug 17, 2008 8:17 PM

Problem deploying entity ejb CMP

hello
when i deploy CMP entity bean in weblogic 5.1
i get an error "could not make connection to pool"
i am using oracle thin driver. connection pool
is created when i start the server but bean could not deploy
please help
thanx

First, set the server to display all logging messages (not just errors), then when you deploy the ejb see what messages happen. I had similar problems when we were deploying on Weblogic 7.0 (with thin Oracle driver).
Also, be sure you have downloaded the latest Oracle driver classes12.zip file and put it into the weblogic server directory - that can cause problems too.

Problem deploying related EJBs in separate JARs

I have 2 entity EJBs, User and Address, in separate JAR files. The User bean
has business methods to get and set its related address as follows:
void setAddressPK(AddressPK newAddress) throws java.rmi.RemoteException;
AddressPK getAddressPK() java.rmi.RemoteException;
When I try and load User.jar in the EJB Deployment tool it complains that it
can't find the AddressPK class. However, I can get round this by explicitly
adding Address.jar to the classpath.
When I actually deploy and use the User bean I do NOT need Address.jar on
the classpath, although I do get warnings during deployment.
So my question is how do I package and deploy related EJBs. I don't want to
have to have all my EJBs in the same JAR, nor do I want to have the same
classes in more than one JAR. Is what I'm doing correct - am I supposed to
have Address.jar on the classpath? And what about an utility classes that
are shared between EJBs - where do I put those?
Thanks in advance,
Steve.

I resolved the problem be making sure that my deployment
jars don't appear in my servlet classpath....
Jason
Jeff Wang <[email protected]> wrote in message news:[email protected]...
In general, if two beans are related (i.e. you can not compile one
without the other being on the classpath) and they are both deployed
they should be in the same jar file. If you do not deploy one of them,
then the undeployed bean can be in the weblogic.class.path with no
problem.
I suspect that you are getting a ClassCastException because you have the
deployment jars in your weblogic.class.path (or java classpath.) Remove
them, and see if the error is resolved.
Jeff Wang
WLCS 2.0 Software Engineer
Jason Rosenberg wrote:
Does the same apply for beans of different types? In other words, do
I need to have an entity bean and a session bean which wraps the entity
bean in the same jar file?
I am having a problem accessing a session bean from a JSP servlet. I get
the dreaded ClassCastException. I don't get this problem, however, if
I access the session bean directly from a stand-alone java client. It's
only when I access the session bean via JSP....
Any ideas?
Jason
Jeff Wang <[email protected]> wrote in message news:[email protected]...
What you should have in the .jar files are:
the home (say it is called <bean>home.class)
the remote (say it is called <bean>.class)
the impl (say it is called <bean>impl.class)
These are the only ones that should be in the .jar file. (not even the
PK should be there, for an entity bean.) All the support classes should
be in weblogic.class.path If you have cross jar dependencies,
unfortunately, you will have to specify the jar in the
weblogic.class.path... However, this is not a good idea, as you will
have 2 class files in memory. At the very least, you will not be able
to do hot deploy. Depending on your code, you'll have a "class cast
exception <bean> can not be casted to an object of <bean>" (Something
like that, I don't have the exact error in front of me.) In your
example it is probably better to put User and Address in the same jar.
Jeff Wang
WLCS 2.0 Software Engineer
Steve Ward wrote:
I have 2 entity EJBs, User and Address, in separate JAR files. The User bean
has business methods to get and set its related address as follows:
void setAddressPK(AddressPK newAddress) throws java.rmi.RemoteException;
AddressPK getAddressPK() java.rmi.RemoteException;
When I try and load User.jar in the EJB Deployment tool it complains that it
can't find the AddressPK class. However, I can get round this by explicitly
adding Address.jar to the classpath.
When I actually deploy and use the User bean I do NOT need Address.jar on
the classpath, although I do get warnings during deployment.
So my question is how do I package and deploy related EJBs. I don't want to
have to have all my EJBs in the same JAR, nor do I want to have the same
classes in more than one JAR. Is what I'm doing correct - am I supposed to
have Address.jar on the classpath? And what about an utility classes that
are shared between EJBs - where do I put those?
Thanks in advance,
Steve.

I need help for deploy an EJB to Oracle 8i

I want to deploy an EJB on Oracle8i, but my JDeveloper 3.2
doesn't have the option "Enterprise Java Bean to Oracle8i", it
has only the option "CORBA to Oracle8i" in the deploy wizard. Is
this correct?
JDeveloper 3.1 has the option "Enterprise Java Bean to Oracle8i"
in the deploy wizard. why doesn't Jdeveloper appear this option?
I need help or information about this.
thank you.

To copy the data of one account to another one, you can use the Shared folder, stored in /Users. You have to log in this user in order to copy the files to the folder, and then, log in the new user and copy the files to the folders where you want to store your files. Another option is to use an external drive.
To start by default with one account, open System Preferences > Login Options, and choose your old account next to "Automatic login"

Problem regarding Deployment of EJB jar file

I am getting the following problem when i am trying to deploy my EJB on to the Weblogic 8.1 using the EjbModules option.
Please help me
Exception:weblogic.management.ApplicationException: prepare failed for mybank Module: mybank Error: Exception preparing module: EJBModule(mybank,status=NEW) Unable to deploy EJB: E:\OnlineBanking\mybank\mybank.jar from mybank.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: Class bytes found but defineClass()failed for: 'mybankEJB' at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Lweblogic.utils.classloaders.GenericClassLoader;)V(MBeanDeploymentInfoImpl.java:550) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Lweblogic.utils.classloaders.GenericClassLoader;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Lweblogic.utils.jars.VirtualJarFile;)V(MBeanDeploymentInfoImpl.java:232) at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1302) at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3101) at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1560) at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1208) at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.management.configuration.ComponentMBean;[Ljava.lang.String;)V(J2EEApplicationContainer.java:1051) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer()V(SlaveDeployer.java:2444) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2394) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2310) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178) at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)

In addition to the JavaEE Tutorial link above, Sun Java System Application Server 9.0 Documentation is here:
http://docs.sun.com/app/docs/coll/1343.3
-cheng

Deployment of Ejb on OAS-4.0.8

Similar Messages

Maybe you are looking for