Weblogic optional package deployment issue

Hi All,
I am using WLS 10.3.4. I have an J2EE web application which references a JAR library as an optional package. Here is my definition of JAR file in the library MANIFEST.MF,
Manifest-Version: 1.0
Extension-Name: PCGCommon2.0
Specification-Version: 1.0.0.0
Implementation-Version: common055jkp
Here is my definition of JAR file reference in the application MANIFEST.MF,
Manifest-Version: 1.0
Extension-List: pcgcommon2
pcgcommon2-Extension-Name: PCGCommon2.0
pcgcommon2-Specification-Version: 1.0.0.0
pcgcommon2-Implementation-Version: common055jkp
I deployed the JAR library first successfully. Then I tried to deploy the application. It throws me this error as follows,
+[J2EE:160149]Error while processing library references. Unresolved Optional Package references (in META-INF/MANIFEST.MF): [Extension-Name: PCGCommon2.0, Specification-Version: 1, Implementation-Version: common055jkp , referenced from: /opt/oracle/Oracle/Middleware/user_projects/domains/Pinellas1qDomain/servers/Pinellas1qMS3/tmp/_WL_user/ppa/cwbd0p/war].+
Can anyone have an idea what I am missing here?
Thanks in advance,
-John
Edited by: john wang on Mar 9, 2011 8:44 AM
Edited by: john wang on Mar 9, 2011 8:58 AM

Hi John,
Please find the working TestCase in the following Location:
http://middlewaremagic.com/weblogic/?p=231#comment-3144
I am copying and pasting the README.txt file here which i attached in the TestCase:
README.txt
Step1). Make Sure that the Hello.java is compiled properly like following:
javac -d . Hello.java<font color=red>Actual Trick is Making the JAR using 'M' option..... :) </font><br>
Step2). The Most important step to Make the "HelloWorld.jar" along with the MANIFEST.MF file which is present inside "HelloWorld\META-INF\MANIFEST.MF"
Use the below command with *'M'* as a Flag while making JAR file so that the Jar utility will not overrite the MANIFEST.MF on it's own rather it will place our own MANIFEST.MF inside the Jar.
C:\OptionalPackageDemo\HelloWorld\> jar -cvfM  HelloWorld.jar META-INF\MANIFEST.MF Hello.java com
Step3). Deploy the HelloWorld.jar and the TestWebApp
<b><font color=red>NOTE: </font></b> I just now tested the attached TestCase in WLS10.3.0 And it perfectly worked for me. So if it's not working for you in WLS10.3.4 then i would request you to please open a Support Ticket with Oracle WebLogic Support Team because ideally the same test case is supposed to work fine in that version as well.
Thanks
Jay SenSharma

Similar Messages

  • Weblogic Optional Packages - Permgen Memory Space

    Hi,
    We are packaging some common jars as Optional Packages in weblogic and using them from different EAR files.We know for classes in side the EAR, each classloader creates individual clazz objects in the permgen space.
    For classes inside the Optional packages and which are referenced in multiple EAR,does weblogic create seperate clazz instances in the permgen space for each classloader? If so then it would mean that classes inside the Optional Package will be created multiple times in the permgen space (attributed to different classloaders)
    Any idea on the behaviour will be highly appreciated.Is the situation same with shared libraries ?

    Depends on where your optinal classes are located.
    If you insert them in the system (or server) classloader they will be loaded once, by the system
    classloader. You can use the ${DOMAIN_HOME}/lib directory for this purpose. The jars located in
    this directory will be picked up and added to the end of the server classpath at server startup.
    The jars will be ordered lexically in the classpath.
    If you are using shared libraries, these shared libraries will be merged at runtime with the
    applications referencing them, so they will be local to the application and to my knowledge
    loaded by the classloader of the application and not a separate shared library classloader. Thus
    if you reference the shared library from multiple applications, the shared libraries get merged
    multiple times and loaded multiple times. The reason is that WebLogic uses classloading
    isolation between the deployed applications, so that from a classloading perspective
    other applications do not bother other applications.

  • Package deployment issues

    We are experiencing some issues when we deploy our packages. We bundle our java classes in to a JAR which is deployed as part of our component package in the /app/webiste-name/install folder.
    As we increment the version number for our deployment packages a new JAR is added to the install folder when it is installed, so we end up with a number of JAR files in the install folder...
    /app/website-name/install/
    - core-1.0.1.jar
    - core-1.0.2.jar
    - core-1.0.3.jar
    - core-1.0.4.jar
    - core-1.0.5.jar
    Each time we deploy the package the server creashes. Also, in our previous package installation it appears the class in 1.0.4 was being referenced instead of the latest 1.0.5 core JAR file. We removed all JAR files from the install folder, re-installed the package and the error went away.
    Should we be removing all JAR files from the install directory before installing a new package version? or should we just have the name of the JAR file as core.jar without a version number? or, something else?

    put "public" in this line:
    public class Test extends MovieClip{

  • Weblogic Eclipse JAR Deployment Issue

    Hi,
    We're deploying from Eclipse project directly to Oracle Weblogic Server v10.3 via WLS Adapter.
    Result*
    NoClassDefFound exceptions for JARs included via Maven Dependencies (in "Project > Properties > Java EE Module Dependencies") errors in Weblogic AdminServer.log.
    Cause*
    JARs that should be accessible under /WEB-INF/lib do not appear to be getting deployed properly.
    Environment*
    Oracle Weblogic Server Support 1.0.0.20080808135653 from OEPE 1.0 on Eclipse Web Tools Project (WTP) 3.0.2 & Eclipse J2EE Ganymede SR1.
    Temporary Workaround
    We have to copy all the generated jar files manually from the generated target lib directory (e.g. D:\xx\xx-src\xx-web\target\xx-web-0.0.1-A-SNAPSHOT\WEB-INF\lib) to the source WEB-INF/lib directory (e.g. D:\xx\xx-src\xx-web\src\main\webapp\WEB-INF\lib)
    There is this bug CR305233 appeared in Workshop for Weblogic, but we can't find any references to a resolution of bug CR305233 in later Workshop for Weblogic versions, and can't locate release notes for OEPE 1.0. (Unfortunately the BEA bugzilla site seems to have disappeared).
    Have you got any idea to solve this problem?
    Thanks

    Hi! I'm experiencing the same problem with both jars and dependent projects.
    My enviroment is composed of Weblogic Server Support 1.0.0.20080808135653 from OEPE 1.0 & Eclipse J2EE Ganymede SR2 & Weblogic 8.1.
    The contents of my project files are:
    .project
    <?xml version="1.0" encoding="UTF-8"?>
    <projectDescription>
         <name>MetasSemanales</name>
         <comment></comment>
         <projects>
              <project>MarcoFVG</project>
         </projects>
         <buildSpec>
              <buildCommand>
                   <name>org.eclipse.wst.jsdt.core.javascriptValidator</name>
                   <arguments>
                   </arguments>
              </buildCommand>
              <buildCommand>
                   <name>org.eclipse.jdt.core.javabuilder</name>
                   <arguments>
                   </arguments>
              </buildCommand>
              <buildCommand>
                   <name>org.eclipse.wst.common.project.facet.core.builder</name>
                   <arguments>
                   </arguments>
              </buildCommand>
              <buildCommand>
                   <name>org.eclipse.wst.validation.validationbuilder</name>
                   <arguments>
                   </arguments>
              </buildCommand>
         </buildSpec>
         <natures>
              <nature>org.eclipse.jem.workbench.JavaEMFNature</nature>
              <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature>
              <nature>org.eclipse.wst.common.project.facet.core.nature</nature>
              <nature>org.eclipse.jdt.core.javanature</nature>
              <nature>org.eclipse.wst.jsdt.core.jsNature</nature>
         </natures>
    </projectDescription>
    .classpath
    <?xml version="1.0" encoding="UTF-8"?>
    <classpath>
         <classpathentry kind="src" path="src"/>
         <classpathentry combineaccessrules="false" exported="true" kind="src" path="/MarcoFVG"/>
         <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/jrockit81sp3_142_04"/>
         <classpathentry kind="con" path="org.eclipse.jst.server.core.container/org.eclipse.jst.server.generic.runtimeTarget/BEA WebLogic Server v8.1"/>
         <classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.web.container"/>
         <classpathentry kind="con" path="org.eclipse.jst.j2ee.internal.module.container"/>
         <classpathentry exported="true" kind="con" path="org.eclipse.jdt.USER_LIBRARY/FiltroSeguridad">
              <attributes>
                   <attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/>
              </attributes>
         </classpathentry>
         <classpathentry exported="true" kind="con" path="org.eclipse.jdt.USER_LIBRARY/JasperReports">
              <attributes>
                   <attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/>
              </attributes>
         </classpathentry>
         <classpathentry exported="true" kind="con" path="org.eclipse.jdt.USER_LIBRARY/log4j">
              <attributes>
                   <attribute name="org.eclipse.jst.component.dependency" value="/WEB-INF/lib"/>
              </attributes>
         </classpathentry>
         <classpathentry kind="output" path="build/classes"/>
    </classpath>
    .settings/org.eclipse.wst.common.component
    <?xml version="1.0" encoding="UTF-8"?>
    <project-modules id="moduleCoreId" project-version="1.5.0">
    <wb-module deploy-name="MetasSemanales">
    <wb-resource deploy-path="/" source-path="/MetasSemanales"/>
    <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/>
    <dependent-module archiveName="MarcoFVG.jar" deploy-path="/WEB-INF/lib" handle="module:/resource/MarcoFVG/MarcoFVG">
    <dependency-type>uses</dependency-type>
    </dependent-module>
    <property name="context-root" value="MetasSemanales"/>
    <property name="java-output-path"/>
    </wb-module>
    </project-modules>
    .settings/org.eclipse.wst.common.project.facet.core.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <faceted-project>
    <runtime name="BEA WebLogic Server v8.1"/>
    <fixed facet="jst.web"/>
    <fixed facet="jst.java"/>
    <installed facet="jst.java" version="1.4"/>
    <installed facet="jst.web" version="2.3"/>
    </faceted-project>
    Thanks
    Edited by: user5830067 on 13/04/2009 10:20 AM
    Edited by: user5830067 on 13/04/2009 10:21 AM

  • Business package deployment issue EP 7.3

    Hi all,
    I am deploying business packages in my portal, but i am getting validation error with 3 packages..
    SAP ESS 633
    SAP MSS 630
    SAP_ESS_LGP 6.33
    But i have deployed the below packages:
    SAP PCUI_GP 633
    UTXSSLGP 633
    BP ERP05 MSS 1.51
    BP ERP UT XSS 1.51
    BP ERP05 SELF-SERV ADMIN 1.3
    Kindly suggest the relevant package needs to deploy for EP.
    Details:
    EP 7.3, Release 720, sup_pckg 68
    BR,
    Kutty

    Hi Kutty,
    Looks like your using correct packages, Do you have XML file from the Solution manager Maintenance Optimizer ? if not, try to download the relevant packages and XML from Maintenance optimizer (Solman) and try again.
    Refer to below link and check the section - Upgrade to EHP5 and/or NW7.3
    http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES
    Thanks,
    Arjun

  • ADF BC 11g, Weblogic 10.3 - Deployment Issue with ADF Security

    Hi all,
    I know there are many many blogs about deployment of an 11g app using ADF Security to a WLS 10.3 server, however, none appear to be working for me.. or I'm not working with them! :P
    I've deployed an .ear file to the WLS 10.3 and this works fine - after following these steps
    http://www.freewebalbum.com/blogs/faces/bjanko/blogs.jsp?blog=bjanko20090127130431
    I then followed Steve's migration technique
    http://www.oracle.com/technology/products/jdev/tips/muench/credmig111100/index.html
    That all built correctly.
    I then tried to access the app via browser, entered in the user cred (created under Security Realms in WLS 10.3 admin console - user and groups).
    I attempted to login, and received an "Error 401--Unauthorized" error.
    I'll that I see in the server log is:
    [JpsWlsFilter.doFilter] setContextID to testApp
    I'm totally stuck, so any ideas would be awesome.
    Cheers,
    chris

    Just gave that a shot.. No dice unfortunately.
    Steve Muench wrote:
    You can omit -DdstApp=DEPLOYAPPNAME if the deployed application name is the same as the source application name you supplied in the -DsrcApp=APPNAME argument.I hate massive code dumping... but this is my jazn-data.xml
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <jazn-data>
       <jazn-realm default="jazn.com">
          <realm>
             <name>jazn.com</name>
             <users>
                <user>
                   <name>system</name>
                   <guid>0300AED0A9A411DD8F304FB2D3E85932</guid>
                   <credentials>{903}G5cbldq4HwMVt/gQpv1lXuNdLYbSu20y</credentials>
                </user>
             </users>
             <roles>
                <role>
                   <name>PlusAdmin</name>
                   <guid>0300AED1A9A411DD8F304FB2D3E85932</guid>
                   <members>
                      <member>
                         <type>user</type>
                         <name>system</name>
                      </member>
                   </members>
                </role>
                <role>
                   <name>PlusUser</name>
                   <guid>0300AED2A9A411DD8F304FB2D3E85932</guid>
                   <members>
                      <member>
                         <type>user</type>
                         <name>system</name>
                      </member>
                   </members>
                </role>
             </roles>
          </realm>
       </jazn-realm>
       <policy-store>
          <applications>
             <application>
                <name>TestApp</name>
                <app-roles>
                   <app-role>
                      <name>PlusAdmin</name>
                      <class>oracle.security.jps.service.policystore.ApplicationRole</class>
                      <members>
                         <member>
                            <class>oracle.security.jps.internal.core.principals.JpsXmlUserImpl</class>
                            <name>system</name>
                         </member>
                      </members>
                   </app-role>
                   <app-role>
                      <name>PlusUser</name>
                      <class>oracle.security.jps.service.policystore.ApplicationRole</class>
                      <members>
                         <member>
                            <class>oracle.security.jps.internal.core.principals.JpsXmlUserImpl</class>
                            <name>system</name>
                         </member>
                      </members>
                   </app-role>
                </app-roles>
                <jazn-policy>
                   <grant>
                      <grantee>
                         <principals>
                            <principal>
                               <class>oracle.security.jps.internal.core.principals.JpsAnonymousRoleImpl</class>
                               <name>anonymous-role</name>
                            </principal>
                         </principals>
                      </grantee>
                      <permissions>
                         <permission>
                            <class>oracle.adf.share.security.authorization.RegionPermission</class>
                            <name>com.delexian.plus.ui.pageDefs.LogonPageDef</name>
                            <actions>view</actions>
                         </permission>
                         <permission>
                            <class>oracle.adf.share.security.authorization.RegionPermission</class>
                            <name>com.delexian.plus.ui.pageDefs.LogonErrorPageDef</name>
                            <actions>view</actions>
                         </permission>
                      </permissions>
                   </grant>
                   <grant>
                      <grantee>
                         <principals>
                            <principal>
                               <class>oracle.security.jps.service.policystore.ApplicationRole</class>
                               <name>PlusAdmin</name>
                            </principal>
                         </principals>
                      </grantee>
                      <permissions>
                         <permission>
                            <class>oracle.adf.share.security.authorization.RegionPermission</class>
                            <name>com.delexian.plus.ui.pageDefs.HomePageDef</name>
                            <actions>customize,edit,grant,personalize,view</actions>
                         </permission>
                      </permissions>
                   </grant>
                   <grant>
                      <grantee>
                         <principals>
                            <principal>
                               <class>oracle.security.jps.service.policystore.ApplicationRole</class>
                               <name>PlusUser</name>
                            </principal>
                         </principals>
                      </grantee>
                      <permissions>
                         <permission>
                            <class>oracle.adf.share.security.authorization.RegionPermission</class>
                            <name>com.delexian.plus.ui.pageDefs.HomePageDef</name>
                            <actions>customize,edit,grant,personalize,view</actions>
                         </permission>
                      </permissions>
                   </grant>
                </jazn-policy>
             </application>
          </applications>
       </policy-store>
       <jazn-policy/>
    </jazn-data>

  • SCCM Package Deployment issue

    Hi All,
    I have created one Application package in SCCM 2012, this package has been successfully distributed  in DP servers. Some of my client still this package is not showing. I have updated clients side policy as well. I want to check client side logs. So
    please suggest which log file I have to check for track down this package progress.
    Nirmal Singh IT Administrator

    Hi,
    Please make sure Application Catalog web service point and Application Catalog website point are installed successfully.(ServicePortalWebService.log and ServicePortalWebSite.log) 
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Restart deployment (.ear) does not load optional package

    Hello everybody,
    In our 10.3.5 WLS domains, we are using optional packages for sharing libraries between applications see [http://docs.oracle.com/cd/E24329_01/web.1211/e24368/libraries.htm|Creating Shared Java EE Libraries and Optional Packages]
    The problem is that if I redeploy the library I have to redeploy the deployment. This issue only happens with the applications packaged as *.ear*. If the application has been deployed as a .war, with restarting the deployment is enough.
    Would be possible to load the referenced library from an *.ear* just restarting the deployment?
    Thanks in advance,
    Luis

    Thanks Vimala,
    I have 1 ear project and 1 web service project.
    Attached my ant output when I run the build.xml.
    C:\wivWorkSpace\wivApp>ant build -Dworkspace=C:/wivWorkSpace
    Buildfile: build.xml
    init.env:
    init.typedefs:
    init:
    build:
    [echo] project.name = wivApp
    init:
    build:
    [echo] wivWS: C:\wivWorkSpace\wivWS\build.xml
    BUILD SUCCESSFUL
    Total time: 23 seconds
    C:\wivWorkSpace\wivApp>ant build -Dworkspace=C:/wivWorkSpace archive
    Buildfile: build.xml
    init.env:
    init.typedefs:
    init:
    build:
    [echo] project.name = wivApp
    init:
    build:
    [echo] wivWS: C:\wivWorkSpace\wivWS\build.xml
    init.env:
    init.typedefs:
    init:
    stage:
    [delete] Deleting directory C:\wivWorkSpace\wivApp\.staging
    [mkdir] Created dir: C:\wivWorkSpace\wivApp\.staging
    [copy] Copying 13 files to C:\wivWorkSpace\wivApp\.staging
    BUILD FAILED
    C:\wivWorkSpace\wivApp\build.xml:192: The following error occurred while executing this line:
    jar:file:/C:/BEAPLA%7e1/WEBLOG%7e1/workshop/lib/wlw-antlib.jar!/com/bea/wlw/antlib/antlib.xml:91: The follow
    ng this line:
    C:\wivWorkSpace\wivApp\build.xml:204: The following error occurred while executing this line:
    Target `stage.to.ear' does not exist in this project.
    Total time: 15 seconds

  • Persistence Layer deployed as Optional Package

    Environment:
    - WebLogic 11g which consequently means EJB 3.0
    - Application has 3 modules: Web (referencing EJB and Persistence), EJB (referencing Persistence) and Persistence
    Could I deploy my persistence layer as an Optional Package or does it have to be a Shared Library?
    The reason I'm asking is that when I try to deploy my EJB module, WLS can't find the persistence unit being inject to it:
    Unable to deploy EJB: StocksBean from BLayer-1.0.0-SNAPSHOT.jar: No persistence unit named 'internalAppsPU' is available in scope BLayer-1.0.0-SNAPSHOT.jar. Available persistence units: []
    Persistence module is basically a JAR file deployed as an Optional Package with following in its Manifest:
    Extension-Name: PersistenceLayer
    Implementation-Version: 1.0.0-SNAPSHOT
    Specification-Version: 1.6
    in EJB's code I have:
    @Stateless(name="StocksBean", mappedName="StocksBean")
    public class StocksBean implements Stocks {
         @PersistenceContext(unitName = "internalAppsPU")
         private EntityManager em;
    and in EJB's JAR file I have:
    pLayer-Extension-Name: PersistenceLayer
    pLayer-Implementation-Version: 1.0.0-SNAPSHOT
    pLayer-Specification-Version: 1.6
    I'm deploying these one by one and not as an Application.

    Hi Arun,
    Thank you so much for taking time and responding. I'm still having the same issue.
    You see, I had the exact same problem when my persistence Entities were in the same Jar file as EJBs and I found out the problem was the name of the persistence.xml file (which was "Persistence.xml") and also the version of the namespace used in the XML file which conflicted with version of JPA's spi (version of JPA's spi in JEE1.6 is 1.0 and I was using version 2.0 of the namespace).
    However, I got that fixed and now I'm trying to separate the layers (just moved the files around and didn't change the content). Here is what I have so far:
    Name of Persistence Layer's JAR file: PLayer.jar
    Manifest of Persistence Layer's JAR file:
    Manifest-Version: 1.0
    Archiver-Version: Plexus Archiver
    Created-By: Apache Maven
    Built-By: bm03043
    Build-Jdk: 1.6.0_18
    Extension-Name: PersistenceLayer
    Implementation-Version: 1.0.0-SNAPSHOT
    Specification-Version: 1.6
    Name of EJB's JAR file: BLayer-1.0.0-SNAPSHOT.jar
    Manifest of EJB's JAR file:
    Manifest-Version: 1.0
    Archiver-Version: Plexus Archiver
    Created-By: Apache Maven
    Built-By: bm03043
    Build-Jdk: 1.6.0_18
    Extension-List: PLayer
    PLayer-Extension-Name: PersistenceLayer
    PLayer-Implementation-Version: 1.0.0-SNAPSHOT
    PLayer-Specification-Version: 1.6
    I didn't know that Extension-List entry in EJB's jar file should match with the name of Persistence layer's jar file.
    As for deployment, I deploy the Player and then EJB.
    Appreciate any input.
    Edited by: Keibi on Apr 26, 2012 11:30 AM

  • Problem in deploying EJBs (More than 390) in weblogic-BEA says JDK issue!!!

    Our application had 390 EJBs before the current build. It was running fine on Weblogic 6.1-SP4 with JDK 1.3.1_08.
    In the current build, 3 EJBs were introduced and the Weblogic server started giving deployment problems. We then came across the Weblogic Bug stating the magic Number of 390 and delegating it to a SUN Bug. But, contrary to the SUN bug which says of a OutofMemory issue, we were not getting any OutOfMemory error.
    Then, just to test the 390 number, we cut downed on the number of EJBs reducing the number to 388, in a test environment. EJBs got deployed without problem. Then we added 3 EJBs (increasing the EJB count to 391), and Weblogic server started giving Deployment problem in a EJB which was one of the 388 that were running fine earlier.But, now also there was no OutOfMemory error. Then we removed one of the newly added EJBs to bring the EJB count to 390. The Weblogic deployed the EJBs without error(even the one which was giving problem when EJB count was 391).
    So, 390 seems to be the number but, contrary to BEA problem ID: 035884 which delegates the problem to SUN Bug ID:4390238 (Incidentally SUN has closed this bug as Non-reproducable), we are not getting any OutOfMemory error.
    My questions to the JAVA community are:
    1)Is the problem really related to JDK or Weblogic?
    2)If it's a problem with JDK, then what should be done to fix it?
    ==========================================
    A deployment error generated is pasted below:
    ==========================================
    java.lang.reflect.InvocationTargetException: weblogic.management.DistributedManagementException: Distributed Management [1 exceptions]
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:559)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy14.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy11.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
    at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
    at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
    at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Distributed update exception
    - remote object: stellar:Location=primary-server,Name=primary-server,Type=ServerConfig
    - remote server: weblogic.management.internal.RemoteMBeanServerImpl@1d5ebc
    - actionName: addDeployment
    - params: [Ljava.lang.Object;@5f97ae
    - signature: [Ljava.lang.String;@5f28a6
    Distributed update exception
    - remote object: stellar:Location=primary-server,Name=primary-server,Type=ServerConfig
    - remote server: weblogic.management.internal.RemoteMBeanServerImpl@1d5ebc
    Unable to deploy EJB: STTaskPrivilegeLinkEntity from Entities.jar:
    java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:165)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
    at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:307)
    at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:362)
    at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
    at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
    at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
    at weblogic.j2ee.Application.addComponent(Application.java:174)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy14.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy11.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
    at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
    at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
    at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
    [java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS]
    at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:367)
    at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
    at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
    at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
    at weblogic.j2ee.Application.addComponent(Application.java:174)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy14.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy11.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
    at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
    at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
    at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1087)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
    at weblogic.j2ee.Application.addComponent(Application.java:174)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy14.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy11.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
    at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
    at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
    at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Unable to deploy EJB: STTaskPrivilegeLinkEntity from Entities.jar:
    java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:165)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
    at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:307)
    at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:362)
    at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
    at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
    at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
    at weblogic.j2ee.Application.addComponent(Application.java:174)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy14.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy11.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
    at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
    at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
    at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
    [java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS]
    at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:367)
    at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
    at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
    at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
    at weblogic.j2ee.Application.addComponent(Application.java:174)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy14.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy11.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
    at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
    at weblogic.management.console.info.MBeanReferenceAttribute.doSet(MBeanReferenceAttribute.java:124)
    at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
    at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
    at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    --------------- nested within: ------------------
    weblogic.management.DistributedOperationUpdateException:
    Unable to deploy EJB: STTaskPrivilegeLinkEntity from Entities.jar:
    java.lang.ClassNotFoundException: Class bytes found but defineClass() failed with java.lang.ClassFormatError: com/c4/stellar/server/ejbs/entities/STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS (Illegal Method name "Exception in 'findBySTTaskEntity_3v8zjr__WebLogic_CMP_RDBMS_taskPrivilegeLinkEntity__WL_' while usi") for com.c4.stellar.server.ejbs.entities.STTaskPrivilegeLinkEntity_apfxaw__WebLogic_CMP_RDBMS
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:165)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
    at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:307)
    at weblogic.ejb20.deployer.EntityBeanInfoImpl.getGeneratedBeanClass(EntityBeanInfoImpl.java:362)
    at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:114)
    at weblogic.ejb20.manager.DBManager.setup(DBManager.java:123)
    at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.deploy(ClientDrivenBeanInfoImpl.java:817)
    at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1299)
    at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1005)
    at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:33)
    at weblogic.j2ee.Application.addComponent(Application.java:174)
    at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:364)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:150)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:374)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:507)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:376)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
    at $Proxy14.addDeployment(Unknown Source)
    at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1545)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:908)
    at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
    at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:310)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
    at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
    at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
    at $Proxy11.setTargets(Unknown Source)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.management.console.info.MBeanAttribute.doSet(MBeanAttribute.java:84)
    at weblogic.management.console.info.MBeanReferenceAttribute.addToArrayAttribute(MBeanReferenceAttribute.java:254)
    at weblogic.management.console.info.MB

    So, 390 seems to be the number but, contrary to BEA
    problem ID: 035884 which delegates the problem to SUN
    Bug ID:4390238 (Incidentally SUN has closed this bug
    as Non-reproducable), we are not getting any
    OutOfMemory error.Did you check the server logs? There might be an OutOfMemoryError logged.
    My questions to the JAVA community are:
    1)Is the problem really related to JDK or Weblogic?Apparently, the problem is with the Weblogic. Did you try deploying the same number on some higher version of Weblogic? (7.0 for instance)
    2)If it's a problem with JDK, then what should be
    done to fix it?Check the bug database for the same bug id. There is a workaround posted. The evaluation comments are also hinting at using the suggested VM options.
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4390238

  • Weblogic 10 - application deployment error: Exception is: "File too large"

    I posted this in Weblogic -> general but realise is should have really gone here as it's about admin server/deployment services setup / configuration.
    I am using weblogic application server 10 in a weblogic clustered enviornment.
    I am trying to deploy an application to a managed server when it starts up, all goes well and I can see it deploying the war files to the managed server.
    It hits a certain war and panics with the exception
    ####<Nov 19, 2011 2:03:59 PM BRST> <Error> <Deployer> <devnode01> <managedserver2> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1321718639109> <BEA-149205> <Failed to initialize the application 'test_war' due to error weblogic.management.DeploymentException: Exception occured while downloading files.
    weblogic.management.DeploymentException: Exception occured while downloading files
    at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
    at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
    at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
    at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
    at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
    at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from admin server for deployment request "0". Underlying error is: "[DeploymentService:290065]Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "0" from server "managedserver2". Exception is: "File too large"."
    at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:86)
    at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
    at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
    at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
    at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
    at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
    at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:725)
    at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:104)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
    at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
    at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    The error appears to be stating the physical file is too big to be deployed
    I'm running the managed servers with a heap size of 3GB and the managed server is running with 2GB - I know these are large but they where being used for debugging
    I can't find any documentation on the file size too large error, or how to resolve it
    DeploymentService:290065 says to look in the log (details are above) and DeploymentService:290066 says the error will be explained in it's description, which it is, "file size too big", it doesn't say where to see/set the max file size, there is plenty of disk space so I can only assume it's setting for the deployment service that needs to be increase, but I cannot find info on this.

    I don't think this would help, but would using the nostage option for deployment change this behaviour.
    I don't think it would as this is for disk based problems rather than transfer size issues.

  • Is it possible to redeploy Optional Package(J2EELibrary)without versioning?

    Currently, I decided to use Optional Package feature for one of our common shared jar file as it is referenced by our multiple applications (ear files). I can understand, how I can deploy multiple version of the optional package in order for the referencing application to use it. I am planning to use this version feature for optional package in our Production Environment. However, my issue is I don't want to use this version feature in our development environment as it involves more work for the developers (overhead on the developers to specify the optional package version in their referencing application). Is there any way I can redeploy optional package in development environment? I can only redeploy only after undeploying all my 6 referencing applications, which is taking more time.

    Does any one have an example to implement Optional Package and versioning it?

  • Packaging/deploying a webapp client to already deployed EJBs

    I have a webapp/ejb deployed on WLS 6.1. If it matters, the EJBs are
    deployed in jar files but the webapp component is deployed in exploded
    directory format.
    Now I want to deploy another webapp that uses the same EJBs. At this
    point in development, I am attempting to deploy this in exploded
    directory format as well. I have run ejbc manually against the original
    jars to create the EJB deployable units containing generated WL classes.
    This also created a ejb-client.jar, but it does not contain any impl
    classes for the home or remoted interfaces.
    I tried placing the ejb-client.jar in my WEB-INF/lib but it doesn't seem
    to be able to find the interface classes. Perhaps the exception I'm
    getting does not mean what I think it does. It is included below.
    I also tried adding the generated impl classes to the ejb-client.jar
    manually, but this didn't work either. I have read the
    packaging/deploying docs but don't seem to find this issue addressed
    directly. From all I know, I have done this correctly, but obviously I
    am missing something somewhere.
    Thanks in advance for your consideration.
    <May 10, 2002 1:53:57 PM CDT> <Error> <HTTP>
    <[WebAppServletContext(9605583,adminApp,/adminApp)] Servlet failed with
    Exception
    java.lang.ExceptionInInitializerError
    at
    sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at
    sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:42)
    at
    sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:30)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:277)
    at java.lang.Class.newInstance0(Class.java:301)
    at java.lang.Class.newInstance(Class.java:254)
    at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:342)
    at javax.rmi.CORBA.Util.<clinit>(Util.java:54)
    at
    javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:182)
    at
    javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:61)
    at
    net.verizon.storm.util.DataBroker.initialize(DataBroker.java:102)
    at
    net.verizon.storm.util.DataBroker.getInstance(DataBroker.java:158)
    at
    net.verizon.storm.util.OrderDispatcher.<init>(OrderDispatcher.java:70)
    at
    net.verizon.storm.admin.OrderService.startOD(OrderService.java:159)
    at
    net.verizon.storm.admin.OrderService.processRequest(OrderService.java:104)
    at
    net.verizon.storm.admin.OrderService.doPost(OrderService.java:266)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
    at
    weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
    at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
    at
    weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Caused by: java.lang.RuntimeException: could not find or instantiate any
    UtilDelegate class
    at
    weblogic.iiop.UtilDelegateImpl.<clinit>(UtilDelegateImpl.java:72)
    ... 24 more

    Hi.
    I tried placing the ejb-client.jar in my WEB-INF/lib but it >>doesn't seem to beable to
    find the interface classes. Perhaps
    the exception I'm getting does not mean what I think it does. >>It is includedbelow.
    It seems fine since it is the way your webapp always to use its EJB client jar.
    I also tried adding the generated impl classes to the ejb-
    client.jar manually, but this didn't work either.Nope, you should never do this since Impl classes are used on Server Side ( webapp
    treated as client of EJB in this case ) only.
    It is so hard for us to analyze the problems without a test case, I would suggest
    you to create a support case via http://support.bea.com/welcome.jsp to BEA support
    for detailed work.
    Thanks.
    Ji Zhang
    Developer Relations Engineer
    BEA Support

  • Referencing an optional package in a jar inside an ear

    UPDATE: We no longer need this as the third-party will change their shared-library ear to a jar for use on other application servers.
    We have no trouble deploying an ear containing a jar as a shared library, and then referencing the classes in it from another application by specifying the appropriate <library-ref> in weblogic-application.xml.
    In some installations, that shared library is not required, and indeed may not be present. In that case, the <library-ref> is unresolved, and the application will not deploy. We would like to avoid having two versions of our application - one with the <library-ref> and one without.
    If we add the Extension-Name property to the manifest of the jar mentioned above, and deploy the jar (not the ear) as a shared library, our application can reference classes in that jar. The problem is that the library ear (containing the jar) comes from a third party, and we cannot extract out the jar. And the "optional package" mechanism does not appear to work for jars within ears. We've specified the Extension-Name from the library ear ( the one from the library jar is not visible) in the Extension-List of the application. There is no complaint that the optional package is unresolved, but accessing the classes gives ClassNotFoundException.
    I did not find any documentation that optional package jars within an ear should be visible to other deployment units, but it seems odd that the third party would package them such that they can only be referenced with the <library-ref> (i.e. on WLS).
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/programming/libraries.html
    http://java.sun.com/j2ee/verified/packaging.html
    Edited by: mikereiche on Nov 11, 2011 4:34 PM

    The JarInputStream class is used to read the contents of a JAR file from any input stream.
    InputStream input=getResourceAsStream("/input.xml");
    JarInputStream jis
    =new JarInputStream(input);

  • [原创]在WLS9中使用J2EE Libraries 和 Optional Packages

    J2EE Libraries 和 Optional Packages
    概述
         J2EE Shared Libraries是Diablo的一个新特性。可以将一个J2EE模块共享给其他EAR类型的J2EE模块。你不能从非EAR访问J2EE Shared Library。J2EE Shared Library可以是任何类型的J2EE模块,但推荐打包成EAR。此外还有一种J2EE 1.4的标准共享库方式,称为 Optional Packages。区别在于 Optional Packages是基于标准的,而且不被当作J2EE模块使用。 Optional Packages提供和J2EE Libraries类似的方式将一个JAR文件被多个应用分享。optional packages必须通过部署对应的JAR文件方式先被注册到WLS。注册好后可以部署J2EE模块,通过manifest files来引用这些包。Optional packages和J2EE libraries的区别在于optional packages可以被任何J2EE模块(EAR, JAR, WAR, or RAR 文档)或扩展的目录结构引用。而J2EE libraries只能被EAR引用。
         本文附件exercise包括J2EE Libraries 和 Optional Packages的练习代码,可解压到任意位置。配置一个WLS Domain,记得用户名和密码要都设为weblogic,端口为7001。启动该Domain,并启动相应的Console。使用Domain/bin/setDomainEnv.cmd打开一个Prompt窗口。并把目录切换到你解压的文件的位置。然后就可以按照第五节和六节所述完成练习。如果想快速看一下练习结果,在solution中有已经配置好的两个练习的代码,部署后就可以测试。
    一。将一个应用作为J2EE Libraries或Optional Packages。
         你可以在该应用的META-INF目录下创建一个MANIFEST.MF文件,指定自己的版本。
         Extension-Name:可选。表示该库或包的名字。主调应用调用这个应用时需要匹配这个值。如果你不设置这个值,系统将自动使用部署名。
         Specification-Version:可选。定义这个库或包的规格版本。主调应用可以为共享模块随便指定一个规格版本。如果这个规格版本不可用,则主调应用不能被部署。规格参数可以有两种格式。第一种使用主从版本格式,大小版本号用点分割,如"9.0.1.1"。第二种使用文本格式,如 "9011Beta"。如果使用主从版本号格式,主调应用可以配置为共享的模块吻合一个特定版本,或者一个最小版本,或者一个最新的版本额。如果使用文本格式,主调应用必须和共享模块的版本号严格吻合。
         Implementation-Version:可选。定义这个库或包代码的执行版本号。必须在已经定义了规格版本的情况下才能定义执行版本。执行版本使用和规格版本相同的格式。
         如果你不使用MANIFEST.MF文件或者有些条目没有指定,可以在命令行中通过weblogic.Deploy进行部署的时候由参数来设置。
    二。J2EE Libraries and Optional Packages比较:
         Optional packages和J2EE Libraries有如下共同点:
         1。在部署的时候都注册到WLS上。
         2。都支持可选执行版本和特定版本字符串。
         3。引用J2EE libraries and optional packages的应用可以指定共享文件的版本。
         Optional packages和J2EE Libraries有如下区别:
         1。Optional package是普通的JAR文件,而 J2EE libraries可以是普通JAR文件,或J2EE应用,或独立的J2EE模块。J2EE libraries可以包括有效地J2EE或WLS部署描述符,而optional package JAR中的任何部署描述符都被忽略了。
         2。任何J2EE应用或模块可以通过META-INF/MANIFEST.MF引用 optional package。而只有企业应用可以通过weblogic-application.xml引用J2EE library 。
         3。Optional packages可以引用其他Optional packages,而J2EE libraries不能引用其他J2EE libraries。
    三。最佳实践:
         1。如果需要共享J2EE模块给多个企业应用。使用J2EE Libraries。
         2。如果要部署独立的J2EE模块作为共享库,应该把模块打包到企业应用中。这样可以防止潜在的URI冲突。因为独立模块库的URI来源于不署名。所以在部署时指定一个部署名,当其他应用引用它时作为URI。
         3。如果多个J2EE压缩文件需要共享一些JAVA类,则应该用optional packages。
         4。如果有一些类在本Domain中需要被其他应用调用,而你又不经常省级这些类(比如第三方类),则最好把它们放在Domain的 /lib目录下,而不是使用J2EE libraries或optional packages机制。在/lib子目录下的类会在Server启动时候自动装载到系统环境变量中。
         5。通常指定一个规范版本和一个执行版本。即使你不打算使用版本需要功能。为库指定版本可以在做测试时为共享的文件部署多个版本。
         6。通常为每个库指定一个扩展名,如果你不指定扩展名那系统会自动使用库的部署名作为扩展名。
         7。当开发了一个Web应用要部署成J2EE应用,应该使用唯一的上下文目录。如果它的上下文目录和他依赖的应用的上下文目录冲突,应该使用EAR的weblogic-application.xml中context-root元素来覆盖库的上下文目录。
    四。组装共享的J2EE Library 文件:
         几乎所有独立的J2EE模块或EA可以被部署成shareable J2EE library,但有如下限制:
         1。不能在一个J2EE library中引用另一个J2EE library.
         2。共享库不能嵌套。如果你不属一个EAR作为共享库,那整个这个EAR必须被作为一个库,而不能指定这个EAR中的某个独立J2EE模块为一个独立的库。
         3。像其他J2EE模块和企业应用一样,J2EE library必须被部署到目标Server或Cluster上去。这意味着库需要一个有效的J2EE部署描述符和WLS指定的部署描述符。
         4。推荐把J2EE libraries打包成企业应用,而不是独立的J2EE模块。因为独立模块的URI来自于部署名。默认WLS使用部署压缩文件的文件名或展开的目录名作为部署名。
         5。如果你选择把库部署成独立的J2EE模块,通常应该指定一个部署名并把这个名字作为被应用引用的URI。
    五。练习开发和部署Shared J2EE Library
         本练习在J2EEShared目录下。可以看到有两个目录,其中SharedLibraryEAR是被调用的shareable J2EE library,CallingLibraryEAR是调用该库的企业应用。通过把SharedLibraryEAR配置成共享库,CallingLibraryEAR可以访问LoanEJB就像打包在自己的EAR中。
         1.我们先来开发一个库应用。观察一下SharedLibraryEAR下面的目录结构和文件。
         目录LoanEJB是一个EJB结构。包括一个空的目录META-INF和一个包含一个JAVA文件Simple.java的目录data。LoanEJB\data目录是放EJB的源代码,Simple.java是我手写的。在LoanEJB下执行java com.bea.wls.ejbgen.EJBGen -descriptorDir META-INF data\Simple.java就会在生成SimpleHome.java,SimpleRemote.java,ejb-jar.xml,weblogic-ejb-jar.xml和ejbgen-build.xml。然后到LoanEJB编译这几个CLASS:javac data\*.java,生成根和桩文件。最后执行jar cvf ..\LoanEJB.jar *,打包我们需要的EJB LoanEJB.jar到SharedLibraryEAR目录。
         目录APP-INF是一个空的目录,可以放入当前这个应用需要的第三方包。
         目录META-INF下包括application.xml和weblogic-application.xml。application.xml指定了这个应用所包含的只有一个EAR模块:LoanEJB.jar,以及这个应用的部署名。为了把这个应用做成共享库,现在我们创建一个MANIFEST.MF文件,并在里面写入如下信息:
              Extension-Name: myLib
              Specification-Version: 1.0
              Implementation-Version: 1.0
         然后在J2EEShared下执行java weblogic.appc SharedLibraryEAR,生成可部署的企业应用。
         2.配置 CallingLibraryEAR来引用SharedLibraryEAR模块。观察一下CallingLibraryEAR下面的目录结构和文件。
         目录APP-INF是放EAR内部公用的类和库的目录。在这个练习中不需要使用。
         目录LoanApproval是一个Web应用。index.jsp用于调用EJB LoanEJB的getString方法,而没有指定这个EJB是来自本企业应用还是其他库。如果调用成功,则把在LoanEJB中设置的一个字符串显示在浏览器上。
         目录META-INF中包括application.xml和weblogic-application.xml。application.xml指定了这个应用所包含的只有一个Web模块LoanApproval。在weblogic-application.xml中除了编码方式,我们还要指定使用的共享库的名称。能看到在library-ref中我们指向了SharedLibraryEAR这个库myLib。同时在这个文件中我们还能指定库的规格版本和执行版本,以及是否需要严格匹配等。
         在J2EEShared目录下执行 java weblogic.appc -library SharedLibraryEAR CallingLibraryEAR来预编译JSP。执行后会看到在LoanApproval\WEB-INF\classes下面会生成一个目录jsp_servlet包含JSP被编译成的Servlet__index.class和__error.class。由于在weblogic-application.xml中指定了使用的共享库,所以appc在调用jspc来编译JSP的时候能找到调用的EJB LoanEJB的命名空间以及对应类。
         3。部署共享库和前端企业应用并测试。
         确保你的Server运行的情况下,在J2EEShared下执行下面两个命令来部署SharedLibraryEAR和CallingLibraryEAR。注意执行以前Console不能使被Look状态的。
              java weblogic.Deployer -adminurl t3://localhost:7001 -user weblogic -password weblogic -deploy -library SharedLibraryEAR
         执行之后在Console的Deployments部分能看到新添加了一个名为myLib(1.0)的库,状态为Installed。
              java weblogic.Deployer -adminurl t3://localhost:7001 -user weblogic -password weblogic -deploy CallingLibraryEAR
         执行之后在Console的Deployments部分能看到新添加了一个名为CallingLibraryEAR的应用,状态为Active。
         如果部署成功,在Console和Prompt都不会有报错。打开一个浏览器测试一下:http://localhost:7001/LoanApproval。如果一切正常,会显示在EJB中设置的那行字符串。
         注意,当需要卸载库的时候,必须先卸载引用这个包的所有应用,然后Activate Change,然后再Look,并且卸载库。
    六。练习开发和部署optional packages
         本练习在OptionalPackages目录下。可以看到两个目录,其中SimpappOptionalPackage是被调用的Optional Packages,SimpappEAR是调用该包的企业应用。通过把SimpappEAR配制成共享包,SimpappOptionalPackage可以访问Simpapp类就像打包在自己的EAR中。
         1。我们先来开发一个Optional Packages。观察一下SimpappOptionalPackage下面的目录结构和文件。
         目录META-INF中现在是空的。需要创建一个MANIFEST.MF文件,包括如下内容:
              Extension-Name: myOptionalPackage
              Specification-Version: 0.9
              Implementation-Version: 1
         目录simp下面包含一个源代码文件Simpapp.java。在OptionalPackages\SimpappOptionalPackage\下执行javac simp/Simple.java,会在simp目录下编译出Simple.class。然后执行 jar cvfm simpapp.jar META-INF/MANIFEST.MF *,把这个类打成一个名为simpapp.jar的JAR包。
         2。配置SimpappEAR来引用SimpappOptionalPackage模块。观察一下SimpappEAR下面的目录结构和文件。
         目录APP-INF和我们前面说的一样,就不赘述。
         目录META-INF下包括application.xml和weblogic-application.xml。application.xml指定了这个应用所包含的只有一个Web模块SimpappWebAp。为了把这个应用做成Optional Packages,现在我们创建一个MANIFEST.MF文件,并在里面写入如下信息:
              Extension-List: simpapp
              simpapp-Extension-Name: myOptionalPackage
              simpapp-Extension-Specification-Version: 0.9
         然后在OptionalPackages下执行java weblogic.appc -classpath SimpappOptionalPackage/simpapp.jar SimpappEAR, 生成可部署的企业应用。注意这次我们没在appc中使用-library,因为使用 optional packages的时候不需要获得它的部署描述符。但我们需要指定optional packages模块的位置放到classpath里编译JSP。
         3。部署OptionalPackages和前端企业应用并测试。
         确保你的Server运行的情况下,在OptionalPackages下执行下面两个命令来部署SimpappOptionalPackage和SimpappEAR。注意执行以前Console不能使被Look状态的。
              java weblogic.Deployer -adminurl t3://localhost:7001 -user weblogic -password weblogic -deploy -library SimpappOptionalPackage\simpapp.jar
              java weblogic.Deployer -adminurl t3://localhost:7001 -user weblogic -password weblogic -deploy SimpappEAR
         如果部署成功,在Console和Prompt都不会有报错。打开一个浏览器测试一下:http://localhost:7001/SimpappWebApp/。如果一切正常,会显示在Simple.java中设置的那行字符串。
    七。相关资源。
         http://e-docs.bea.com/wls/docs90/notes/new.html
    该帖由 goblinize 在 Nov 4, 2005 5:43 PM 编辑过

    另外谢谢支持征文活动,让大家先看一下,然后再考虑奖励的事情。希望大家积极参与。
    有什么问题在此积极留言,希望作者给以解答。

Maybe you are looking for

  • Help! Split and Design modes in Dreamweaver CS5 is disabled.

    The first time I launched Dreamweaver CS5 I didn't like the default code / design view my files appeared in. So I choose a preference setting where files appear in a single pane in code view. Unfortunately I don't remember where this setting is locat

  • GMS2: Sync errors after restarting datasync-connectors

    System: SLES11SP3 fresh install, GMS 2.0.0 Build 429 Groupwise 2012sp2 GMS is working fine till restarting the connectors in a ssh shell or restarting the whole GMS service (rcgms restart) after that, mail without attachment are working fine but mail

  • Lightroom 4.3 installation doesnt start

    I downloaded LR 4.3, but installation doesn' start.

  • F60DESM core dumps on execution

    I am using Developer 6.0 on HP-UX 11.00. While trying to run f60desm i am getting core dump error Assertion failed: status == ClipboardSuccess, file uicl.c, line 985 Abort(coredump) Executables relevant to Reports and Graphics are working with out co

  • INSERT PICTURE / LOGO

    sir, how we insert picture or logo in abap programm with in module pool. by oops method thankx in advance