Applet -ejb ; weblogic.jar

Hi,
<b>I am trying to access EJB from an applet thro' ejb-client.jar. It works fine if I include weblogic.jar in the applet archive but it throws a corba exception if I use wlclient.jar and wljmsclient.jar instead of weblogic.jar in the archive. As weblogic.jar is too huge <b>I want to use thin clients</b>. Could someone help me with this exception. I am using WLS8.1_sp4; jdk 1.4.2_05 and ie6 with latest jvm. Both applet and ejb are deployed in same localhost</b>
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = localhost port = 7001
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
te_host=localhost remote_port=7001 state=ESTABLISHED]
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Reading the mess
age fully, size =1204
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Handling GIOP 1.
0 LocateReply
com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Constructing IIO
PInputStream object
com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Setting the time
stamp
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = 172.16.65.14 port = 7001
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
te_host=172.16.65.14 remote_port=7001 state=ESTABLISHED]
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for 172.16.65.14:7001,4,ORB ThreadGroup]): Creating mess
age from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): getEndpoint(IIOP_CLEAR_TEXT, 0, null)
com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): createListener( socketType = IIOP_CLEAR_TEXT port = 0 )
javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.MARSHAL:   vmcid: SUN  minor cod
e: 217 completed: Maybe]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:237)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at informatics.inventory.plates.editor.EJBPlateMapDAO.<init>(Unknown Source)
at informatics.inventory.plates.editor.PlateMapEditor.init(Unknown Source)
at sun.applet.AppletPanel.run(AppletPanel.java:353)
at java.lang.Thread.run(Thread.java:534)
Caused by: org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 217 completed: Maybe
at com.sun.corba.se.internal.iiop.CDROutputStream_1_0.write_wstring(CDROutputStream_1_0.java:464)
at com.sun.corba.se.internal.iiop.CDROutputStream.write_wstring(CDROutputStream.java:189)
at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameComponentHelper.write(WNameComponentHelper.java:79)
at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameHelper.write(WNameHelper.java:59)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:79)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
... 6 more

Hi,
<b>I am trying to access EJB from an applet thro' ejb-client.jar. It works fine if I include weblogic.jar in the applet archive but it throws a corba exception if I use wlclient.jar and wljmsclient.jar instead of weblogic.jar in the archive. As weblogic.jar is too huge <b>I want to use thin clients</b>. Could someone help me with this exception. I am using WLS8.1_sp4; jdk 1.4.2_05 and ie6 with latest jvm. Both applet and ejb are deployed in same localhost</b>
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = localhost port = 7001
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
te_host=localhost remote_port=7001 state=ESTABLISHED]
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Reading the mess
age fully, size =1204
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Handling GIOP 1.
0 LocateReply
com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Constructing IIO
PInputStream object
com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Setting the time
stamp
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message
from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = 172.16.65.14 port = 7001
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo
te_host=172.16.65.14 remote_port=7001 state=ESTABLISHED]
com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for 172.16.65.14:7001,4,ORB ThreadGroup]): Creating mess
age from stream
com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,
4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection
com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): getEndpoint(IIOP_CLEAR_TEXT, 0, null)
com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file:
/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): createListener( socketType = IIOP_CLEAR_TEXT port = 0 )
javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.MARSHAL:   vmcid: SUN  minor cod
e: 217 completed: Maybe]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:237)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at informatics.inventory.plates.editor.EJBPlateMapDAO.<init>(Unknown Source)
at informatics.inventory.plates.editor.PlateMapEditor.init(Unknown Source)
at sun.applet.AppletPanel.run(AppletPanel.java:353)
at java.lang.Thread.run(Thread.java:534)
Caused by: org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 217 completed: Maybe
at com.sun.corba.se.internal.iiop.CDROutputStream_1_0.write_wstring(CDROutputStream_1_0.java:464)
at com.sun.corba.se.internal.iiop.CDROutputStream.write_wstring(CDROutputStream.java:189)
at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameComponentHelper.write(WNameComponentHelper.java:79)
at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameHelper.write(WNameHelper.java:59)
at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:79)
at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
... 6 more

Similar Messages

  • Bug: weblogic.jar doesn't include the javax.ejb classes

    In the
    Oracle WebLogic Server 11gR1 (10.3.6) + Coherence -
    Package Installer
    the C:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar doesn't include the javax.ejb package classes. The javax.ejb package is empty.

    This is the correct behavior, stub and skeleton classes are generated at deployment time by WebLogic server and stored in a server internal location.
    In case you are interested, it is something like: ...\samples\domains\medrec\servers\MedRecServer\cache\EJBCompilerCache\ with file named like HelloSession_gjfaqw_Intf.java., etc.
    -danny

  • In applet,how can i got the thin client jar for JMS from weblogic.jar?

    who can give it to me?
    and,when i used the weblogic.jar coming from weblogic 7sp2 for linux advance server
    2.1 as the client jar,i still got a error message that Class (.....Stub.class)is
    not found,why?What should i do?

    That approach is a hack and an absolute nightmare. It never worked
    completely. I could not get any support for durable subscriptions etc. You
    can add this (Thin JMS client) as a request for new feature (but it should
    have been available long time ago).
    -- Vish Magapu
    "Bruce Stephens" <[email protected]> wrote in message
    news:[email protected]..
    Hello,
    You might want to take a look at the JMS white paper and asociated
    discussion for supporting thin clients: check the reference on:
    http://e-docs.bea.com/wls/docs70/faq/jms.html#252418
    HTHs,
    Bruce
    jerry8006 wrote:
    who can give it to me?
    and,when i used the weblogic.jar coming from weblogic 7sp2 for linux advance
    server
    2.1 as the client jar,i still got a error message that Class
    (.....Stub.class)is
    not found,why?What should i do?

  • Weblogic.jar not found

    Hi,
    Going throu' a strange problem. I am calling an applet method from javascript. This applet method in turn access certain ejb methods which needs the class files of weblogic.jar. I have this weblogic.jar in the classpath, applet archive and both application and applet.jar reside in the same server. Obviously weblogic.jar is also in the server classpath. But when I call the applet method from javascript it is not able to find the classes in weblogic.jar. I am not sure what the problem is. Could somebody help. Thank You.
    - Vik

    did you resolve the issue ? If so, let me know.

  • Applet-ejb; corba exception

    Hi, I am trying to access EJB from an applet thro' ejb-client.jar. It works fine if I include weblogic.jar in the applet archive but it throws a corba exception if I use wlclient.jar and wljmsclient.jar instead of weblogic.jar in the archive. As weblogic.jar is too huge I want to use thin clients. Could someone help me with this exception. I am using WLS8.1_sp4; jdk 1.4.2_05 and ie6 with latest jvm. Both applet and ejb are deployed in same localhost com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class, 4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = localhost port = 7001 com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class, 4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo te_host=localhost remote_port=7001 state=ESTABLISHED] com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message from stream com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class, 4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Reading the mess age fully, size =1204 com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Handling GIOP 1. 0 LocateReply com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Constructing IIO PInputStream object com.sun.corba.se.internal.iiop.IIOPInputStream(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Setting the time stamp com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for localhost:7001,4,ORB ThreadGroup]): Creating message from stream com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class, 4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Client get called: host = 172.16.65.14 port = 7001 com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class, 4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Creating new connection Connection[type=IIOP_CLEAR_TEXT remo te_host=172.16.65.14 remote_port=7001 state=ESTABLISHED] com.sun.corba.se.internal.iiop.MessageMediator(Thread[JavaIDL Reader for 172.16.65.14:7001,4,ORB ThreadGroup]): Creating mess age from stream com.sun.corba.se.internal.iiop.ConnectionTable(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class, 4,file:/C:/projects/perforce/java/PlateMapViewer/-threadGroup]): Succesfully created socket for new connection com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file: /C:/projects/perforce/java/PlateMapViewer/-threadGroup]): getEndpoint(IIOP_CLEAR_TEXT, 0, null) com.sun.corba.se.internal.iiop.GIOPImpl(Thread[thread applet-informatics.inventory.plates.editor.PlateMapEditor.class,4,file: /C:/projects/perforce/java/PlateMapViewer/-threadGroup]): createListener( socketType = IIOP_CLEAR_TEXT port = 0 ) javax.naming.NamingException: Unhandled exception in lookup [Root exception is org.omg.CORBA.MARSHAL: vmcid: SUN minor cod e: 217 completed: Maybe] at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81) at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:237) at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171) at javax.naming.InitialContext.lookup(InitialContext.java:347) at informatics.inventory.plates.editor.EJBPlateMapDAO.<init>(Unknown Source) at informatics.inventory.plates.editor.PlateMapEditor.init(Unknown Source) at sun.applet.AppletPanel.run(AppletPanel.java:353) at java.lang.Thread.run(Thread.java:534) Caused by: org.omg.CORBA.MARSHAL: vmcid: SUN minor code: 217 completed: Maybe at com.sun.corba.se.internal.iiop.CDROutputStream_1_0.write_wstring(CDROutputStream_1_0.java:464) at com.sun.corba.se.internal.iiop.CDROutputStream.write_wstring(CDROutputStream.java:189) at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameComponentHelper.write(WNameComponentHelper.java:79) at weblogic.corba.cos.naming.NamingContextAnyPackage.WNameHelper.write(WNameHelper.java:59) at weblogic.corba.cos.naming._NamingContextAnyStub.resolve_any(_NamingContextAnyStub.java:79) at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213) ... 6 more

    I had the same problem and finally caught a statement in one of the docs: "To facilitate the use of IIOP, always specify a valid IP address or DNS name for the Listen Address attribute in the configuration file (config.xml) to listen for connections." I edited my config.xml file and put in the ip address of the machine running my WLS and things started working. Hope this works for you.
    Regards,
    Ron

  • Applet EJB Coomunication

    Hi,
    I am trying the applet ejb communication .
    I am very comfortable if I do the same with applet servlet communication but the problem is with the applet calling the ejb directly, i mean to say that can applet can directly lookup the EJB ?
    I had tried on the intranet but we are supposed to give the HOme and remote files to the client also the ejb.jar has to be given as the JVM of the clinet doesnot have the javax.ejb package and all relevant pacakages are to be given,
    There is no meaning of making the client EJB compitable.
    Also what about the security ?
    So can any body help me how to do the same.
    Thanks in advance.
    Milind

    Remove ur applet ejb communication by
    applet to servlet/serverside class then from that servlet/serverside clas to ejb..
    This concept is done by a pattern called 'business delegate'.
    By using this approach u need not give the stub and skull to the front end side (jsp/applet/or anything like that).
    just call the servlet/class from the applet by keeping that class as passover and thereby the lookup details are moved to that servlet/class that could resolve your problem..
    does my answer make any sense to u..

  • Minimizing size of weblogic.jar for JavaWebStart

    We have a number of in-house client-server Swing applications. They run through
    JavaWebStart and talk to WebLogic EJB's on the backend. I'm working on a new app,
    the first on WL7, and the sheer mass of weblogic.jar is a big problem: close to
    40MB! It's so big that when I made the JWS web client into a WAR inside our app's
    ear, I got an OutOfMemoryError deploying unless I gave the weblogic.Deployer at
    least 256mb of memory! It also takes a long time to download, a long time to deploy,
    etc.. I imagine only a fraction of those classes are actually needed at runtime,
    but which ones?!? I have found nothing on Google or dev2dev, because I guess this
    sort of config is a lot less common than a JSP/servlet type set-up. Help!
    --kd

    I guess you should search for VerboseToZip utility in WLS. Search on dev2dev
    site. I saw a white paper. Title is something like "thin client jar..."
    "Kyle Downey" <[email protected]> wrote in message
    news:[email protected]..
    >
    We have a number of in-house client-server Swing applications. They runthrough
    JavaWebStart and talk to WebLogic EJB's on the backend. I'm working on anew app,
    the first on WL7, and the sheer mass of weblogic.jar is a big problem:close to
    40MB! It's so big that when I made the JWS web client into a WAR insideour app's
    ear, I got an OutOfMemoryError deploying unless I gave theweblogic.Deployer at
    least 256mb of memory! It also takes a long time to download, a long timeto deploy,
    etc.. I imagine only a fraction of those classes are actually needed atruntime,
    but which ones?!? I have found nothing on Google or dev2dev, because Iguess this
    sort of config is a lot less common than a JSP/servlet type set-up. Help!
    --kd

  • Ejb-client.jar

    Hi,
    I've got an EJB system that until now have been packaging as just a
    bean jar and not bothering with a ejb-client.jar. I now want to
    package as follows
    a). A bean EAR file (containing bean jar, and dependency jars) - for
    deploying on EJB server.
    b). An app EAR file (containing WAR, containing ejb-client.jar).
    The first part is done. The second raised questions about the contents
    of the ejb-client.jar. I have packaged the Home/Remote interfaces and
    all necessary utility classes (i.e omitting the Local/LocalHome/EJB
    classes). What I need to know is what goes in there in terms of
    descriptors.
    Do I just package the exact same ejb-jar.xml, jboss.xml,
    jbosscmp-jdbc.xml, weblogic-ejb-jar.xml, weblogic-cmp-rdbms-jar.xml ?
    or do I have to change these in some way ?
    Do I also add the ejb-client-jar tag to the ejb-jar.xml ? (would this
    also go in the ejb-jar.xml that goes in the bean jar ?) ... and indeed
    what would I put in there ... just the name of ejb-client-jar file
    even though its only being packaged into any application WAR (what
    purpose does it serve) ?
    TIA

    The ejb-link value should include pathnames relative to the top level of the EAR
    file.
    <ejb-link>../my_beans-client.jar#CurrencyExchange</ejb-link>
    Andy Jefferson <[email protected]> wrote:
    Deepak Vohra wrote:
    An ejb-client.jar contains the class files, the home and remote interfaces
    and the primary key class, a client program needs to call the EJBs
    contained in the ejb-jar file.
    Also, ejb-client.jar contains a copy of any classes from the ejb-jarfile
    that
    are referenced by the home and remote interfaces and the primary key
    class. Deployment descriptors are not required in the ejb-client.jar.
    ejb-client-jar element is not a required element in ejb-jar.xml. If
    ejb-client-jar.xml is specified in ejb-jar.xml ejbc generates the
    ejb-clent.jar file.
    Thx. I'm not interested in using any server-specific tools (like ejbc)
    since
    I'm deploying to multiple servers and so am generating the ejb-client
    jar
    myself in my build process. In this context, what purpose does the
    <ejb-client-jar> tag in the ejb-jar.xml descriptor have ? Why does the
    beans jar need to know anything about where the client stubs are ?
    As far as I can tell I'm including the right things in my ejb-client.jar,
    and I've tried deploying my web-app EAR to WebLogic 7.0 and I always
    get
    that it can't find the ejb-link elements. What i've got in my EAR is
    my_app.war
    META-INF/application.xml
    and in the WAR
    my JSP files
    WEB-INF/web.xml
    WEB-INF/jboss-web.xml
    lib/my_beans-client.jar
    In the WEB-INF I have ejb-ref's like the following
    <ejb-ref >
    <ejb-ref-name>ejb/CurrencyExchangeHome</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <home>my_domain.CurrencyExchangeHome</home>
    <remote>my_domain.CurrencyExchangeRemote</remote>
    <ejb-link>my_beans-client.jar#CurrencyExchange</ejb-link>
    </ejb-ref>
    Should I be putting the my_beans-client.jar in the EAR and not the WAR
    Seems I am missing something, but not sure what exactly.

  • EJB Client JAR project produces empty JAR

    I've built an EJB module in WorkSpace Studio using the "WebLogic EJB Project" type, which is part of an EAR. I created a couple stateless session beans within this project, and then created an EJB Client JAR project using the "EJB Client JAR-->Create EJB Client Jar" menu item on the EJB project's hidden menu.
    According to the documentation, exporting an EAR file from the EAR project will cause the client JAR to be generated. I exported the EAR file from the EAR project, and sure enough, it included the client JAR (in /APP-INF/lib/). I extracted the client JAR from the EAR and opened it up to make sure it contained all of the client-side classes. I discovered that the client JAR was empty, the only contents being the MANIFEST.MF file. The interface classes were instead contained in the EJB JAR itself.
    How can I get the EJB client code to actually be included in the EJB client JAR?
    Thanks,
    Eric

    Well I have tried this with 6.1 and first
    1. One would expect the jar name to be the name in the ejb-jar.xml -
    ejb-client-jar section
    2. It outputs the file XXXEJB_Compiled.jar but it is same size as base jar
    this is 6.1 sp3
    whats up?
    Matthew Shinn wrote:
    Hi Sanjay,
    There is a bug in the documentation. The client-jar name should never be part of the
    ejbc command line. Step 3 below should be something like:
    java weblogic.ejbc xxxEJB.jar xxxEJB_Compiled.jar
    If you have an ejb-client-jar entry in your ejb-jar.xml, the client jar should be placed
    in the directory from which you ran ejbc. Make sure that the classes that you want to be
    put in the client-jar are not loaded from the classpath. This is very important or your
    client-jar won't be created correctly. The client-jar will only contain classes loaded
    from the input jar to ejbc. A bug for the incorrect documentation has already been filed
    and should be fixed soon.
    - Matt
    Sanjay Dwivedi wrote:
    Hi,
    I am trying to use the
    <ejb-client-jar> sub-element of the Sun's <ejb-jar> (EB 2.0 DTD) element of the
    ejb-jar.xml to generate the ejb-client.jar. I followed the step as documented
    by WebLogic but the files in EJB jars and ejb-client jars are identical. Here
    is what I am doing:
    1. Build the xxxEJB.jar for my EJB by running the WebLogic.ejbc on the standard
    EJB jar file.
    2. My ejb-jar.xml file has following line:
    <ejb-jar>
    <ejb-client-jar>xxxEJBClient.jar</ejb-client-jar>
    </ejb-jar>
    3. Next I used the following command to generate the ejb-client.jar file
    java weblogic.ejbc xxxEJB.jar xxxEJBClient.jar
    My xxxEJBClient.jar files consists of exactly same files (with same sizes) as
    the xxxEJB.jar file. Only difference is that the xxxEJB.jar file includes generated
    java source files for the bean implementation class and home/remote classes.
    In my opinion the xxxEJBClient.jar should not contain the EJB implementation classes.
    Any experience using the ejb-client-jar for generating the ejb-client.jar?
    Thanks,
    Sanjay.
    [att1.html]

  • Unable to deploy EJB - weblogic,management.ApplicationException

    I am getting the following error when i deploy an ear file in WL 7.0 with MySQL
    at the backend
    There is one entity bean and one servlet in the application.
    can any body tell what mistake i could be making ?
    thanks in advance
    -vasanth
    error log
    =====
    weblogic.management.ApplicationException: Prepare failed. Task Id = null
    Module Name: titan_ejbs.jar, Error: Exception preparing module: EJBModule(titan_ejbs.jar,status=NEW)
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
    TargetException:
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:744)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)

    Add a <persistence-use> element to weblogic-ejb-jar.xml deployment descriptor.
    <persistence>
    <persistence-use>     
    <type-identifier>WebLogic_CMP_RDBMS</type-identifier>     
    <type-version>5.1.0</type-version>     
    <type-storage>META-INF/weblogic-cmp-jar.xml</type-storage>
    </persistence-use>
    </persistence>
    "vasanth" <[email protected]> wrote:
    >
    I am getting the following error when i deploy an ear file in WL 7.0
    with MySQL
    at the backend
    There is one entity bean and one servlet in the application.
    can any body tell what mistake i could be making ?
    thanks in advance
    -vasanth
    error log
    =====
    weblogic.management.ApplicationException: Prepare failed. Task Id = null
    Module Name: titan_ejbs.jar, Error: Exception preparing module: EJBModule(titan_ejbs.jar,status=NEW)
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
    TargetException:
    Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
    java.lang.NullPointerException
         at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
         at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
         at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
         at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
         at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
         at weblogic.Server.main(Server.java:32)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:744)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
         at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
         at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
         at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
         at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
         at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)

  • Encoding with weblogic.jar or wlclient.jar

    I am using weblogic 9.0 on jrockit 1.5.0_03 I have an application deployed using stateless session EJB’s.
    I have a webstart client that runs on jdk1.5.0_03. When using weblogic.jar on the client side, everything runs fine.
    When using wlclient.jar on the client side, I don’t get data from the server which contains umlauts. The data are lost on the client side.
    In the direction to the server I have no problems, I can store data with umlaut. I tried already setting the default encoding on server (-Dweblogic.webservice.i18n.charset=utf-16) and client (-Dfile.encoding=utf-16), with no success.
    Any help will be appreciated.
    Thanks in advance!

    Hello Sir
    Did u solve the problem
    i am also getting the same problem
    please help me if u found the solution

  • Stripping weblogic.jar???

    Hi all.
              During our development/testing cycle of our application, we sticked with both wlclient.jar and wljmsclient.jar and sometimes we found strange behavior in terms of Exception handling (through ExceptionListener), reconnection (not automatic but through our own code), and several issues which led us to take the decision to use the full weblogic.jar.
              Although I am authorized to send the full weblogic.jar I would like to find a way to strip weblogic.jar without touching any of the functionality I'm looking for.
              For example, I already stripped off servlet, ejb, some ant stuff, but there are other packages that are not as clear as the ones I mentioned before.
              Could you lead me in a way that could be safe to remove classes, and help shrink the jar?
              Thank you in advance, I appreciate much your answers.
              Greetings
              P.S. The wls version we're using right now is 9.2
              Message was edited by:
              carlos.navarro

    Hi, as that document said, I tried using the verboseToZip utility, but it fails to work, as it's searching for InnerClasses implementations that it fails to find. From the log generated by the -verbose option, I manually deleted all the files that were causing conflict, but in the end, the client jar lacked of vital JMS Classes (like javax.jms.Topic).
              I'm trying the other options considered there....will let you know the output...
              Also, if you have any thoughts on what I just did, please let me know!
              Greetings.

  • Weblogic.jar problems

    Hi,
    I am hosting an ejb web service on a different J2EE complaint application server and my security subject is coming from weblogic 10.3. When I use weblogic.jar in my application server classpath and try to start the serverr it throws the following exceptions:
    Exception occured in J2EEC Phase
    com.sun.enterprise.deployment.backend.IASDeploymentException:
    Exception occured in the wsgen process java.lang.ClassCastException:
    com.sun.xml.ws.api.server.Container$1 cannot be cast to
    weblogic.wsee.jaxws.WLSContainer
    at com.sun.enterprise.webservice.WsUtil.runWsGen(WsUtil.java:1848)
    at com.sun.enterprise.webservice.WsUtil.genWSInfo(WsUtil.java:2249)
    at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:359)
    at com.sun.enterprise.deployment.backend.AppDeployer.explodeArchive(AppDeployer.java:294)
    at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:207)
    at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)
    at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:276)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:294)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:555)
    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:597)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:564)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployJavaEEArchive(AutoDeployer.java:545)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:492)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:267)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:374)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)
    |#]
    [#|2008-06-29T18:45:24.172-0700|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=15;_ThreadName=Timer-9;Exception
    occured in the wsgen process java.lang.ClassCastException:
    com.sun.xml.ws.api.server.Container$1 cannot be cast to
    weblogic.wsee.jaxws.WLSContainer
    ;_RequestID=7cfc908b-f335-439c-b9e8-ac83c5f744b3;|"DPL8011:
    autodeployment failure while deploying the application : Exception
    occured in the wsgen process java.lang.ClassCastException:
    com.sun.xml.ws.api.server.Container$1 cannot be cast to
    weblogic.wsee.jaxws.WLSContainer
    "|#]
    It seems that weblogic.jar contains lot of files which either I don't need it or have some problems. I also tried using wlclient.jar instead of weblogic.jar but I am getting different exceptions related to missing class files. Is there a true .jar file from weblogic that I (as a client application) could use to access the weblogic server from a different application server using t3:// protocol.
    Any help would be really appreciated.
    john

    Hello Sir
    Did u solve the problem
    i am also getting the same problem
    please help me if u found the solution

  • Weblogic.jar and jdk1.5 compatible issues

    Hi
    Weblogic 9.1 and JDK 1.5
    I am using Eclipse 3.1 IDE.
    I have imported weblogic.jar to my application. When i open the jar, i dont see the ejb and Jms packages. I get compilation error in Eclipse.
    When i change the compiler to Jdk 1.4 and expand the jar, I see the packages.
    What is wrong here?
    Thanks in Anticipation

    Hi Rob,
    I am trying to run the weblogic 8.1 with JDK 1.5?
    Is it possible?
    I am getting the following exception at start up... I had changed the start up files to point to JDK 1.5.
    java.io.InvalidClassException: javax.management.MBeanAttributeInfo; local class incompatible: stream classdesc serialVersionUI
    D = 7043855487133450673, local class serialVersionUID = 8644704819898565848
    at java.io.ObjectStreamClass.initNonProxy(Ljava.io.ObjectStreamClass;Ljava.lang.Class;Ljava.lang.ClassNotFoundExceptio
    n;Ljava.io.ObjectStreamClass;)V(Unknown Source)
    at java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
    at java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
    at java.io.ObjectInputStream.readNonProxyDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
    at java.io.ObjectInputStream.readClassDesc(Z)Ljava.io.ObjectStreamClass;(Unknown Source)
    at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
    at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
    at java.io.ObjectInputStream.readArray(Z)Ljava.lang.Object;(Unknown Source)
    at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
    at java.io.ObjectInputStream.defaultReadFields(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
    at java.io.ObjectInputStream.readSerialData(Ljava.lang.Object;Ljava.io.ObjectStreamClass;)V(Unknown Source)
    at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
    at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
    at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
    at weblogic.management.internal.TypesHelper.getMBeanInfo(TypesHelper.java:261)
    at weblogic.management.internal.TypesHelper.getAdminOrConfigMBeanInfo(TypesHelper.java:366)
    at weblogic.management.internal.ConfigurationMBeanImpl.<init>(ConfigurationMBeanImpl.java:130)
    at weblogic.management.AdminServer.<init>(AdminServer.java:59)
    at weblogic.management.AdminServerAdmin.initialize(AdminServerAdmin.java:245)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:771)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
    at weblogic.Server.main(Server.java:32)
    Is weblogic 8.1 not compatible with JDK 1.5?
    Thanks in advance,
    Binu

  • Weblogic.jar file location in  CC&B Media

    Hi Guys
    Can anyone let me know the weblogic.jar file location in CC&B 2.2 media.
    Thanks
    Aleem

    vinod hadlee wrote:
    Hi,
    We use weblogic 8.1 for our development purpose... and mostly work on ejb's. Every time a new ear file is created and deployed we need to specify the jar files needed to run that application in server classpath.... is there any alternate way so that v can avoid specifying these jar files in server classpath...One alternative is you could bundle the jars in the EAR itself in APP-INF/lib.
    Gerald

Maybe you are looking for

  • New to the Mac World

    I am tired of just all the problems that windows brings and will be going to the apple store and buying an iMac. I need some help though. I know this has probably been answered alot but I have searched and have only really found one thread asking thi

  • File Location in UTL_FILE

    Hi, I'm using UTL_FILE and I've asked my DBA to configure a location on the network as UTL_FILE's default file location, say, "c:\utl" on oraserver. Now, how do I pass this to UTL_FILE.FOPEN ? Do I say : X := UTL_FILE.FOPEN( 'C:\UTL', 'TEST', 'w' );

  • Imac won't start up because of a kernel panic version 10.8.0

    my 2009 intel iMac came on today with a panic error. have not been able to start up with Data Rescue. Instructions just say to restart, but I get the same thing over and over. Get the chimes and then the wjite apple screen, and then what looks like t

  • Who change format date?

    hi, who i can change format date in servidor ORACLE for all client? Thank´s

  • [SOLVED]Cannot install programs

    I really need help. I'm getting very upset with myself as I can't install any application. I've tried the Wiki and AUR with no luck. I'm using LXDE with PCManfm I need to install some kind of text editor and hopefully a torrent client. I don't know h