Deploying sampleplugin-ejb.jar  ...

WLI has provided sampleplugin-ejb.jar with WLI 2.0. I tried to deploy it on our
WLS 6SP2 instance + WLPI 2.0 instance.
At the time of startup, i am getting following error .
<Jul 30, 2001 5:23:20 PM EDT> <Info> <WebLogicServer> <com.bea.wlpi.server.wlpiinit.WLPIInit
reports: WebLogic Process Integrator is starting.>
[SerializationTester] : isSerializable(class javax.naming.Binding)
java.io.NotSerializableException: javax.mail.Session
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at weblogic.jndi.internal.SerializationTester.isSerializable(SerializationTester.java:36)
at weblogic.jndi.internal.BindingEnumeration.fixNonSerializableBindings(BindingEnumeration.java:29)
Any Idea ?
Thanks
JIgnesh Patel

There is nothing wrong with the plugin. Error turns out to be because of following lines
in config.xml file which enable Java Mail Session.
<MailSession JNDIName="com.bea.wlpi.MailSession"
Name="wlpiMailSession"
Properties="[email protected];mail.host=mail.domain.com" Targets="myserver"/>
Because of these lines, Mail Session is started and added to JNDI; and then for some
reason PluginManager's initialization process tries to serialize it, causing this error.
If you do not plan to use "Send Email" action in WLPI, you can comment out these
lines above in your config.xml and error will disappear.
Followup can be carried in weblogic.developer.interest.jndi newsgroup.
-Kuntal Shah
Arsin Corporation
Jignesh Patel wrote:
I agree with you. I'd like to know about this jar file. Why BEA has provided
? javax.mail.Session doesn't implement serializble. Why they are using it in
this sample plugin ?
Thanks
Jignesh Patel
Kuntal Shah <[email protected]> wrote:
We got this error too, but it did not seem to break anything...
Jignesh Patel wrote:
WLI has provided sampleplugin-ejb.jar with WLI 2.0. I tried to deployit on our
WLS 6SP2 instance + WLPI 2.0 instance.
At the time of startup, i am getting following error .
<Jul 30, 2001 5:23:20 PM EDT> <Info> <WebLogicServer> <com.bea.wlpi.server.wlpiinit.WLPIInit
reports: WebLogic Process Integrator is starting.>
[SerializationTester] : isSerializable(class javax.naming.Binding)
java.io.NotSerializableException: javax.mail.Session
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1148)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1841)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:480)
at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1214)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:366)
at weblogic.jndi.internal.SerializationTester.isSerializable(SerializationTester.java:36)
at weblogic.jndi.internal.BindingEnumeration.fixNonSerializableBindings(BindingEnumeration.java:29)
Any Idea ?
Thanks
JIgnesh Patel

Similar Messages

  • 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

  • Deploying an EJB Jar on weblogic

    Hi
    i have an ear file which contains two components
    1. JAR file contains EJB's
    2. WAR file contains JSP's and servlets
    when i try to deply this ear on weblogic
    the JAR file succesfully deploy but on deploying WAR file
    it throws error
    Context path is already in use
    Kindly help me to solve this problem
    Puneet

    The Web application that is being deployed has been assigned a context path that is already in use.

  • Error on deploying an ejb jar......................any ideas?

    <Aug 5, 2004 3:51:27 PM PDT> <Warning> <DRS> <BEA-002506> <The current version 0 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 10 for a one-phase update.>
    EJB name : entity
    EJB name : loss
    EJB name : policy
    EJB name : lossUM
    EJB name : claim
    EJB name : stakeholderClaim
    EJB name : liabilityGroupForClaim
    <Aug 5, 2004 3:51:51 PM PDT> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 10 for the application IQ.
    weblogic.management.NoAccessRuntimeException: Access not allowed for subject: principals=[], on ResourceType: ApplicationConfig Action: execute, Target: notifyDeployment
         at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:611)
         at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:499)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:393)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:984)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:943)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.configuration.ApplicationMBean_Stub.notifyDeployment(ApplicationMBean_Stub.java:1797)
         at weblogic.management.deploy.slave.SlaveDeployer$Task.notifyDeployment(SlaveDeployer.java:2166)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2323)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Aug 5, 2004 3:51:51 PM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating Deploy task for application IQ.>
    <Aug 5, 2004 3:51:51 PM PDT> <Debug> <Deployer> <BEA-149078> <Stack trace for message 149004
    java.lang.Exception: Delta :11 ErrorMessage :Access not allowed for subject: principals=[], on ResourceType: ApplicationConfig Action: execute, Target: notifyDeployment
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:524)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Aug 5, 2004 3:51:51 PM PDT> <Error> <Management> <BEA-149306> <Deployment update failed. Update Failed due to any one of the servers not up
    Server CIQServer failed in respond>

    You are correct. Closing the context solves this problem. Totally non-obvious!
    <b>Thank you so much for taking the time to write your solution!!!!</b> :-)

  • Deploying persistence.xml in ejb-jar componts

    Hi,
    If you are deploying ejb-jar components which are packaged independently and are remote components but they all access the same database, do you put the persistence.xml in the META-INF of each component (ejb-jar). If not, where would it go?
    I can find lots of references to having a single persistence.xml with many configurations but if (theoretically) each bean is deployed on a separate JVM/Container how would it access the persistence.xml?
    Thanks.

    If you are deploying the EJB JARs to different Java EE servers, then yes, each EJB JAR needs its own persistence.xml. You would configure each Java EE server to point to the same JDBC resource.
    If you are deploying them all to the same server, you should package the entity classes into a single JAR file, and include that JAR file in an EAR with the other EJB JARs. In that scenario, persistence.xml is in the JAR's META-INF directory. The JAR file can either be in the top-level of the EAR, or in the EAR's library directory. In this case, the scope of the persistence unit is the entire EAR.
    -ian

  • Ejb-ref-mapping in orion-ejb.jar missing location attribute after deployment

    I have noticed that on several of my entity beans that after deployment the <ebj-ref-mapping location="JNDIName" name="LocalName"/> is missing the location attribute. This causes any attempts to lookup the EJBHome for that EJB to fail because the path to the EJBHome in JNDI cannot be found (obviously!). The problem is that this causes me to manually edit the application-deployment/<app>/<ejb.jar>/orion-ejb.zml after each deployment via the admin.jar. This seems like a bug with OC4J and I am wondering if Oracle is aware/doing something to fix this?
    I have noticed that the same problem exists for session beans, however, for some strange reason the EJBHomes can still be resolved in JNDI. In all cases the location in JNDI is different then the <ejb-ref-name> I used in the client EJB.
    Example being I have an entity bean at com.foo.Foo and the session bean uses lookup("java:comp/env/ejb/Foo") it is still able to find the EJB even though the orion-ejb.xml looses the location attribute. If the case is an entity bean referencing another entity bean in the same fashion I get an error because the location attribute is missing.

    If the 'location' value is same as the 'name' value, then even though the location attribute is missing, it is ok and should work. If they are not the same, then you should have defined the ejb-link element in your ejb-jar.xml when defining this ejb-ref and that would make the location attribute appear in the generated orion-ejb-jar.xml.
    If the referenced bean is from a different application (EAR), then you should have used the -parent option when deploying the application.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Kris Trujillo ([email protected]):
    I have noticed that on several of my entity beans that after deployment the <ebj-ref-mapping location="JNDIName" name="LocalName"/> is missing the location attribute. This causes any attempts to lookup the EJBHome for that EJB to fail because the path to the EJBHome in JNDI cannot be found (obviously!). The problem is that this causes me to manually edit the application-deployment/<app>/<ejb.jar>/orion-ejb.zml after each deployment via the admin.jar. This seems like a bug with OC4J and I am wondering if Oracle is aware/doing something to fix this?
    I have noticed that the same problem exists for session beans, however, for some strange reason the EJBHomes can still be resolved in JNDI. In all cases the location in JNDI is different then the <ejb-ref-name> I used in the client EJB.
    Example being I have an entity bean at com.foo.Foo and the session bean uses lookup("java:comp/env/ejb/Foo") it is still able to find the EJB even though the orion-ejb.xml looses the location attribute. If the case is an entity bean referencing another entity bean in the same fashion I get an error because the location attribute is missing.<HR></BLOCKQUOTE>
    null

  • Orion-ejb-jar ignored by JDeveloper deploying to OC4J

    orion-ejb-jar.xml is ignored by JDeveloper 903 when deploying to external OC4J 903. Specific mappings like those below are lost:
    <entity-deployment name="RequestEJB" copy-by-value="false" data-source="jdbc/OracleDS" exclusive-write-access="false" table="REQUEST">
    <primkey-mapping>
    <cmp-field-mapping name="requestid" persistence-name="REQUESTID" persistence-type="NUMBER(9)"/>
    </primkey-mapping>
    <cmp-field-mapping name="requestid" persistence-name="REQUESTID" persistence-type="NUMBER(9)"/>
    <cmp-field-mapping name="requestuser" persistence-name="REQUESTUSER" persistence-type="VARCHAR2(30)"/>
    <cmp-field-mapping name="requestlabel" persistence-name="REQUESTLABEL" persistence-type="VARCHAR2(12)"/>
    <cmp-field-mapping name="requestdate" persistence-name="REQUESTDATE" persistence-type="DATE"/>
    <cmp-field-mapping name="isurgent" persistence-name="ISURGENT" persistence-type="VARCHAR2(1)"/>
    </entity-deployment>
    Instead, JDeveloper creates a new orion-ejb-jar.xml with different table name:
              <entity-deployment name="RequestEJB" location="RequestEJB" local-wrapper="RequestHome_EntityHomeWrapper421" table="RequestEJB_modulab_Proj_n76ccv" data-source="jdbc/OracleDS" exclusive-write-access="false" locking-mode="optimistic" update-changed-fields-only="true" delay-updates-until-commit="true" min-instances-per-pk="0" max-instances-per-pk="50" disable-wrapper-cache="true">
                   <primkey-mapping>
                        <cmp-field-mapping name="requestid" persistence-name="requestid" />
                   </primkey-mapping>
                   <cmp-field-mapping name="requestuser" persistence-name="requestuser" />
                   <cmp-field-mapping name="requestlabel" persistence-name="requestlabel" />
                   <cmp-field-mapping name="requestdate" persistence-name="requestdate" />
                   <cmp-field-mapping name="isurgent" persistence-name="isurgent" />
                   <finder-method query="">
                        <!-- Generated SQL: "select RequestEJB_modulab_Proj_n76ccv.requestid from RequestEJB_modulab_Proj_n76ccv -->
                        <method>
                             <ejb-name>RequestEJB</ejb-name>
                             <method-name>findAll</method-name>
                             <method-params>
                             </method-params>
                        </method>
                   </finder-method>
              </entity-deployment>
    orion-ejb-jar is placed at the META-INF folder. Why does JDeveloper ignore it? It does not ignore orion-application.xml nor orion-web.xml. Must I configure project or deployment profiles not to overwrite orion-ejb-jar?

    I believe that it is not JDeveloper issue but OC4J one. It does not pick up new orion-ejb-jar.xml if you re-deploy bean(s). It should deploy your orion-ejb-jar.xml when you're deploying yor application for the first time (so there is not orion-ejb-jar.xml in deployments directory). If you want OC4J to pick changes up remove orion-ejb-jar.xml from $OC4J_HOME/application-deployments/<application>/<Bean>.jar/ and then deploy it either manually or with JDeveloper. I hope it will help.

  • 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.

  • OC4J9.0.4 generates orion-ejb-jar.xml instead of using mine !!!

    META-INF directory of my EJB module of the EAR archive contains two descriptors: ejb-jar.xml and orion-ejb-jar.xml. But when I deploy the application OC4J generates its own orion-ejb-jar.xml and replaces mine with it. How it could be ?

    Hi Avi,
    I assume you are talking about your development
    environment (as opposed to your production
    environment). You do know that if you edit the
    deployed "orion-ejb-jar.xml" file, OC4J will pick
    that up and automatically re-deploy, don't you? Or
    simply copy your new "orion-ejb-jar.xml" file to the
    same directory as the deployed one (thus overwriting
    it) -- same effect.This is exactly what I end up doing. Are you saying that
    (a) the production environment will not suffer from this problem? (if so, how?)
    (b) I will have to edit the deployed orion-ejb-jar.xml file every time I deploy to production (admittedly, not too frequently)?
    regards
    George

  • Does TopLink 10g generate toplink-ejb-jar.xml and weblogic-ejb-jar.xml?

    Also, does it have the ability to deploy an EJB JAR to an app server of choice?
    Thanks in advance.

    TopLink's Mapping Workbench will generate the toplink-ejb-jar.xml file for use in CMP and will augment the base ejb-jar.xml file.
    http://download-west.oracle.com/docs/cd/B10464_04/web.904/b10313/pkg_depl.htm#1132804
    TopLink does not generate the container specific file for WebLogic. More details available at:
    http://download-west.oracle.com/docs/cd/B10464_04/web.904/b10313/pkg_depl.htm#1124592
    TopLink does not include any deployment capabilities. This is the roll of yor IDE or scripts.
    Doug

  • Include reference to ejb-jar in config.xml

    Hi
    I am deploying an ejb-jar to WLS and everything is fine. But when I try to
    run the ejb I get NoClassDefFoundError. As far as I can see the only
    solution to this problem is to add a reference to the jar-file in the
    command file used to start WLS. Is this true or are there smarter ways to do
    this?
    Regards
    Morten Salomonsen
    [email protected]

    You mean you get the exception when you access the EJB from the client? Is
    the exception a client side exception?
    see if this helps
    http://e-docs.bea.com/wls/docs61/programming/packaging.html
    "Morten S." <[email protected]> wrote in message
    news:[email protected]..
    Hi
    I am deploying an ejb-jar to WLS and everything is fine. But when I try to
    run the ejb I get NoClassDefFoundError. As far as I can see the only
    solution to this problem is to add a reference to the jar-file in the
    command file used to start WLS. Is this true or are there smarter ways todo
    this?
    Regards
    Morten Salomonsen
    [email protected]

  • HELP...HELP..Deployment of EJB with JDeveloper

    where do the JDeveloper deploy, its EJB jar file, before starting the application?I searched a lot, but couldn't find.

    JDeveloper has an in built OC4J(an servlet and EJB container). It deploys in this app server.

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

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

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

  • Weblogic 10.3.0 Deployment error when using ejb-jar.xml

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

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

  • How to deploy 2 EJB's in separate jars

    Hi,
    I have successfully deployed 2 session ejb's in the same jar file, i.e. with one ejb-jar.xml and one weblog-ejb-jar.xml. And get get the ejb's to communicate with each other.
    Now I want to be able to compile and deploy the 2 ejb's in separate jar files as part of an ear file.
    My method so far is this:
    I have split the ejb-jar.xml file into two, for each ejb, and also the weblogic-ejb-jar.xml file into two for each ejb.
    I then compiled the ejb source files and packaged each ejb up with its respective deployment descriptors into two separate .jar files.
    I then want to run weblogics ejbc on each .jar file in turn so that the resultant .jar files (with newly created stubs/skels) can be packaged into an .ear to be easily deployed into weblogic.
    I try and run the ejbc command on the first of the .jar files and i get the error:
    ERROR: Error from ejbc:
    In ejb-jar.xml, the EJB 'SessClient' contains an invalid ejb-link in ejb
    -ref 'ejb/SessLogHome'. No EJB with ejb-name 'IntellectStateless.jar#SessLog' co
    uld be found.
    ERROR: ejbc found errors
    My ejb-jar.xml file for this ejb is:
    <ejb-jar>
      <enterprise-beans>
        <session>
          <ejb-name>SessClient</ejb-name>
          <home>intellectsession.sessiontwo.SessClientEntHome</home>
          <remote>intellectsession.sessiontwo.SessClientEnt</remote>
          <ejb-class>intellectsession.sessiontwo.SessClientEntBean</ejb-class>
          <session-type>Stateless</session-type>
          <transaction-type>Container</transaction-type>
          <ejb-ref>
            <ejb-ref-name>ejb/SessLogHome</ejb-ref-name>
            <ejb-ref-type>Session</ejb-ref-type>
            <home>intellectsession.stateless.SessLogHome</home>
            <remote>intellectsession.stateless.SessLog</remote>
            <ejb-link>IntellectStateless.jar#SessLog</ejb-link>
          </ejb-ref>
        </session>
      </enterprise-beans>
      <assembly-descriptor>
        <container-transaction>
          <method>
         <ejb-name>SessClient</ejb-name>
         <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
        </container-transaction>
      </assembly-descriptor>
    </ejb-jar>and both of my .jar files are in the same directory when I run the ejbc command.
    I'm sure this can be done but I just think i'm not doing it in the right order maybe??
    Anyway pointers will be gr8ly appreciated.
    Cheers
    T

    Okay here is the solution to how to achieve the problem I encountered above:
    I am compiling my ejb.jar files using the weblogic.ejbc compiler, obviously I am deploying on weblogic here.
    This section:
    <ejb-ref>
      <ejb-ref-name>ejb/SessLogHome</ejb-ref-name>
      <ejb-ref-type>Session</ejb-ref-type>
    <home>intellectsession.stateless.SessLogHome</home>
      <remote>intellectsession.stateless.SessLog</remote>
      <ejb-link>IntellectStateless.jar#SessLog</ejb-link>
    </ejb-ref>must have JUST the <ejb-link/> tag removed from the ejb-jar.xml file. And then the weblogic-ejb-jar.xml file MUST look like this:
    <weblogic-ejb-jar>
        <weblogic-enterprise-bean>
            <ejb-name>SessClient</ejb-name>
            <reference-descriptor>
              <ejb-reference-description>
                <ejb-ref-name>ejb/SessLogHome</ejb-ref-name>
                <jndi-name>SessLog</jndi-name>
              </ejb-reference-description>
            </reference-descriptor>
            <jndi-name>SessClient</jndi-name>
        </weblogic-enterprise-bean>
    </weblogic-ejb-jar>Note the <refererence-descriptor> tag as the important part.
    After these changes, the 2 ejb.jar files can be compiled using the weblogic.ejbc tool, thus supplying the stubs/skels, and then the resultant two ejb.jar files can be added to the EAR file and deployed to weblogic.
    Result: 2 ejb's in separate jars, in one EAR file, talking to each other.
    T

Maybe you are looking for

  • Can applet access oracleDB which not on the Web server

    can anyone tell me if I could use applet come from a Web server to access oracle DB on the other workstation, how to do it

  • How do I configure my Mbpro Mid 2012 to shutdown on UPS ?

    I have a MacBook Pro Mid 2012 with OSX 10.10 connected to an older APC UPS via USB. On my MacBook I also have a WD myBook ext. Harddrive. In Settings I see the UPS but I have no settings to activate a shutdown process - I only can dim the monitor. Un

  • How to check IBAN activation?

    Hi all! I have to modify a program which is quite old and which used table TIBAN_ACTIVE in order to check the IBAN activation. Today table TIBAN_ACTIVE does no more exist. Then how to check that an IBAN has been activated? Using the date "VALID_FROM"

  • Balance Sheet in SE71

    In se71, I just see only heads of the balance sheet, I want to see sub heads description in the balance sheet( classical reports), pls suggest me to solve the problem

  • Updating Oracle 8i database from SQLServ 7

    Hi, I have successfully migrated data from sqlServ 7 to Oracle 8i. The SQLServ is constantly updated. Using OMWB, how do I update the data/tables in Oracle without recreating the schema/repository? Thanks.