JAXB/WLS 8.1 ISSUE

Hi,
We are trying to use JAXB 1.0.1 (JWSDP 1.2) as our binding framework, but we are
unable to compile the java code that uses JAXB functionality when we try to use
the ant build that comes with WLS 8.1. After comparing the distribution of WLS
8.1 and JWSDP, we found that there are lots of differences in terms of the ANT
distribution. JWSDP distribution has ANT 1.5.2 version.
Which ant version does Weblogic Server 8.1 use ? Please suggest us a solution
for this problem ?
Thanks,
Ganesh

Refer Bug ID 4376065 on java.sun.com (http://developer.java.sun.com/developer/bugParade/bugs/4376065.html
) , which seems to be related to what you are explaining here. Please contact
Sun Support for a follow up on this issue with regard to your specific case.
Regards
Shridhar
"Ganesh" <[email protected]> wrote:
>
Thanks Sridhar for the response. I tracked the version as you suggested.
It is
matched what you just responded. But, the issue is when I try to compile
some
classes that uses JAXB it is not complaining anything about JAXB classes,
but
rather complains about JDK 1.4.1_01 (Which comes with WLS 8.1 on HP-UX
11). I
am pasting the stack trace I got while trying to compile. Any ideas ?
[javac] An exception has occurred in the compiler (1.4.1.01). Please
file
a
bug at the Java Developer Connection (http://java.sun.com/cgi-bin/bugreport.cgi)
after checking the Bug Parade for duplicates. Include your program
and the fol
lowing diagnostic in your report. Thank you.
[javac] java.lang.ArrayIndexOutOfBoundsException: 3584
[javac] at com.sun.tools.javac.v8.code.ClassReader.readPool(ClassReader.
java:450)
[javac] at com.sun.tools.javac.v8.code.ClassReader.readName(ClassReader.
java:551)
[javac] at com.sun.tools.javac.v8.code.ClassReader.readClassAttrs(ClassR
eader.java:765)
[javac] at com.sun.tools.javac.v8.code.ClassReader.readClass(ClassReader
.java:859)
[javac] at com.sun.tools.javac.v8.code.ClassReader.readClassFile(ClassRe
ader.java:933)
[javac] at com.sun.tools.javac.v8.code.ClassReader.fillIn(ClassReader.ja
va:1088)
[javac] at com.sun.tools.javac.v8.code.ClassReader.complete(ClassReader.
java:1046)
[javac] at com.sun.tools.javac.v8.code.Symbol.complete(Symbol.java:332)
[javac] at com.sun.tools.javac.v8.code.Symbol$ClassSymbol.complete(Symbo
l.java:651)
[javac] at com.sun.tools.javac.v8.code.ClassReader.loadClass(ClassReader
.java:1113)
[javac] at com.sun.tools.javac.v8.comp.Resolve.loadClass(Resolve.java:48
5)
[javac] at com.sun.tools.javac.v8.comp.Resolve.findIdentInPackage(Resolv
e.java:660)
[javac] at com.sun.tools.javac.v8.comp.Attr.selectSym(Attr.java:1140)
[javac] at com.sun.tools.javac.v8.comp.Attr.visitSelect(Attr.java:1089)
[javac] at com.sun.tools.javac.v8.tree.Tree$Select.accept(Tree.java:1091
[javac] at com.sun.tools.javac.v8.comp.Attr.attribTree(Attr.java:256)
[javac] at com.sun.tools.javac.v8.comp.Attr.attribType(Attr.java:286)
[javac] at com.sun.tools.javac.v8.comp.Enter$MemberEnter.signature(Enter
.java:682)
[javac] at com.sun.tools.javac.v8.comp.Enter$MemberEnter.visitMethodDef(
Enter.java:770)
[javac] at com.sun.tools.javac.v8.tree.Tree$MethodDef.accept(Tree.java:4
82)
[javac] at com.sun.tools.javac.v8.comp.Enter$MemberEnter.memberEnter(Ent
er.java:707)
[javac] at com.sun.tools.javac.v8.comp.Enter$MemberEnter.memberEnter(Ent
er.java:719)
[javac] at com.sun.tools.javac.v8.comp.Enter$CompleteEnter.finish(Enter.
java:929)
[javac] at com.sun.tools.javac.v8.comp.Enter$CompleteEnter.complete(Ente
r.java:916)
[javac] at com.sun.tools.javac.v8.code.Symbol.complete(Symbol.java:332)
[javac] at com.sun.tools.javac.v8.code.Symbol$ClassSymbol.complete(Symbo
l.java:651)
[javac] at com.sun.tools.javac.v8.comp.Enter.complete(Enter.java:593)
[javac] at com.sun.tools.javac.v8.JavaCompiler.complete(JavaCompiler.jav
a:306)
[javac] at com.sun.tools.javac.v8.code.ClassReader.fillIn(ClassReader.ja
va:1090)
[javac] at com.sun.tools.javac.v8.code.ClassReader.complete(ClassReader.
java:1046)
[javac] at com.sun.tools.javac.v8.code.Symbol.complete(Symbol.java:332)
[javac] at com.sun.tools.javac.v8.code.Symbol$ClassSymbol.complete(Symbo
l.java:651)
[javac] at com.sun.tools.javac.v8.code.ClassReader.loadClass(ClassReader
.java:1113)
[javac] at com.sun.tools.javac.v8.comp.Resolve.loadClass(Resolve.java:48
5)
[javac] at com.sun.tools.javac.v8.comp.Resolve.findGlobalType(Resolve.ja
va:548)
[javac] at com.sun.tools.javac.v8.comp.Resolve.findType(Resolve.java:604
[javac] at com.sun.tools.javac.v8.comp.Resolve.findIdent(Resolve.java:63
1)
[javac] at com.sun.tools.javac.v8.comp.Resolve.resolveIdent(Resolve.java
:798)
[javac] at com.sun.tools.javac.v8.comp.Attr.visitIdent(Attr.java:1033)
[javac] at com.sun.tools.javac.v8.tree.Tree$Ident.accept(Tree.java:1111)
[javac] at com.sun.tools.javac.v8.comp.Attr.attribTree(Attr.java:256)
[javac] at com.sun.tools.javac.v8.comp.Attr.attribType(Attr.java:286)
[javac] at com.sun.tools.javac.v8.comp.Enter$MemberEnter.visitVarDef(Ent
er.java:780)
[javac] at com.sun.tools.javac.v8.tree.Tree$VarDef.accept(Tree.java:511)
[javac] at com.sun.tools.javac.v8.comp.Enter$MemberEnter.memberEnter(Ent
er.java:707)
[javac] at com.sun.tools.javac.v8.comp.Enter$MemberEnter.memberEnter(Ent
er.java:719)
[javac] at com.sun.tools.javac.v8.comp.Enter$CompleteEnter.finish(Enter.
java:929)
[javac] at com.sun.tools.javac.v8.comp.Enter$CompleteEnter.complete(Ente
r.java:916)
[javac] at com.sun.tools.javac.v8.code.Symbol.complete(Symbol.java:332)
[javac] at com.sun.tools.javac.v8.code.Symbol$ClassSymbol.complete(Symbo
l.java:651)
[javac] at com.sun.tools.javac.v8.comp.Enter.complete(Enter.java:593)
[javac] at com.sun.tools.javac.v8.comp.Enter.main(Enter.java:574)
[javac] at com.sun.tools.javac.v8.JavaCompiler.compile(JavaCompiler.java
:334)
[javac] at com.sun.tools.javac.v8.Main.compile(Main.java:520)
[javac] at com.sun.tools.javac.Main.compile(Main.java:36)
[javac] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[javac] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[javac] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[javac] at java.lang.reflect.Method.invoke(Method.java:324)
[javac] at org.apache.tools.ant.taskdefs.compilers.Javac13.execute(Javac
13.java:100)
[javac] at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:832)
[javac] at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:674)
[javac] at org.apache.tools.ant.Task.perform(Task.java:317)
[javac] at org.apache.tools.ant.Target.execute(Target.java:309)
[javac] at org.apache.tools.ant.Target.performTasks(Target.java:334)
[javac] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[javac] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
[javac] at org.apache.tools.ant.Main.runBuild(Main.java:610)
[javac] at org.apache.tools.ant.Main.start(Main.java:196)
[javac] at org.apache.tools.ant.Main.main(Main.java:235)
BUILD FAILED
Thanks,
Ganesh
"Shridhar Mysore" <[email protected]> wrote:
At the outset, WLS 8.1 doesn't support JAXB.
And the version of ant that comes with WLS 8.1 I think is :
Apache Ant version 1.5 compiled on July 30 2002
You can check this using "ant -version" against WLS 8.1 environment.
Regards
Shridhar
"Ganesh" <[email protected]> wrote:
Hi,
We are trying to use JAXB 1.0.1 (JWSDP 1.2) as our binding framework,ant
but we are
unable to compile the java code that uses JAXB functionality when we
try to use
the ant build that comes with WLS 8.1. After comparing the distribution
of WLS
8.1 and JWSDP, we found that there are lots of differences in termsof
the ANT
distribution. JWSDP distribution has ANT 1.5.2 version.
Which ant version does Weblogic Server 8.1 use ? Please suggest usa
solution
for this problem ?
Thanks,
Ganesh

Similar Messages

  • WLS 8.1 issue with .ear deployment ....

    I think the weblogic8.1 seems to have some NEW bug now. We have a .ear file that
    works just PERFECT in WLS6.1. But now when we try to DEPLOY this .ear file our
    WLS8.1 server(via the new look and feel of WLS8.1' console)....we are getting
    the Exception like ...."pl read inline below":
    ...All i know is that WLS 8.1 has introduced something like : "single J2EEC -
    EAR compiler, replacing the separate compilers in previous releases" ........is
    it may be because of this ????
    If somebody has any idea ....please let me know asap ...and just above the EXCEPTION
    we are also getting something like ...."Deployment descriptor "/WEB-INF/ups-html.tld"
    is malformed" ....what is going wrong now ?
    Please note again ....this .ear file just work PERFECT in WLS6.1+sp2.
    Read inline for the Exception:
    <Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
    Deployment descriptor "/WEB-INF/ups-html.tld" is malformed. Check against the
    DTD: Element type "info" must be declared. (line 334, column 9).>
    <Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
    Deployment descriptor "/WEB-INF/ups-html.tld" is malformed. Check against the
    DTD: The content of element type "tag" must match "(name,tag-class,tei-class?,body-content?,display-name?,small-icon?,large-icon?,description?,variable*,attribute*,example?)".
    (line 335, column 8).>
    MessageResourcesFactory.createFactory
    java.lang.NoClassDefFoundError: org/apache/struts/util/MessageResourcesFactory
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:431)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:169)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:292)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:140)
    at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:161)
    at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1029)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
    at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
    at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
    at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    <Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101046> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]
    service: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
    java.lang.NullPointerException
    at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1031)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
    at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
    at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
    at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    >
    <Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "service"
    failed to preload on startup in Web application: "ABL".
    javax.servlet.UnavailableException: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
    at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1043)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
    at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
    at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
    at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    thx, sangita

    Rob,
    These are the 3 files that you need:
    1) wlstart_cap (this is the start up script that we use to start the Managed server
    while on WLS6.1) ....please read inline:
    -----------Inline 1-----------------
    #!/bin/ksh
    # BEA WebLogic Start Script - Version 1.1
    # Add support for STARTMODE MKG 03/08/2002
    # Set user specified variables
    JAVA_HOME=/usr/j2sdk1_3_1_01
    JAVA_OPTIONS="-D$1 -ms128m -mx128m -noclassgc"
    BEA_HOME=/opt/bea
    WL_HOME=$BEA_HOME/wlserver6.1
    WL_SCRIPT=$WL_HOME/config/Subsidiary
    export WL_SCRIPT
    EXPORT_LIB=$WL_HOME/lib
    #### Set locale to US English MKG 2003/01/16
    LC_MESSAGES=C
    LC_TIME=en_US.ISO8859-1
    LC_NUMERIC=en_US.ISO8859-1
    LC_MONETARY=en_US.ISO8859-1
    LC_COLLATE=en_US.ISO8859-1
    LC_CTYPE=en_US.ISO8859-1
    export LC_MESSAGES LC_TIME LC_NUMERIC LC_MONETARY LC_COLLATE LC_CTYPE
    #### End locale settings
    #### UPSCAP-clientmanger App settings --- Begin
    # workaround for strange bug in code that requires an x-server
    # to be present when graph code is initialized.
    # Note that this is my sun workstation. MKG 05/16/2002
    DISPLAY=bluewolf.telecom.ups.com:0.0
    export DISPLAY
    #### UPSCAP-clientmanger App settings --- End
    #### EUP App settings --- Begin
    VANAPI_HOME=/opt/vanapi
    VANPATH=$VANPATH:$VANAPI_HOME/vanapi/share
    LD_LIBRARY_PATH=$VANAPI_HOME/vanapi:$VANAPI_HOME/vanapi/vanjavi:$LD_LIBRARY_PATH
    PATH=$VANAPI_HOME/perl_dir/bin:$PATH
    EUP_CLASSPATH=$WL_HOME/config/Subsidiary/serverclasses
    export VANPATH LD_LIBRARY_PATH VANAPI_HOME PATH EUP_CLASSPATH
    #### EUP App settings --- End
    CLASSPATH=$WL_HOME/lib/CR061106_61sp2.jar:$WL_HOME/lib/CR072612_61sp2.jar:$WL_HOME/lib/CR071109_610sp2.jar:$WL_
    HOME/lib/CR058352_61sp2.jar:$WL_HOME/lib/weblogic.jar:$BEA_HOME:$EUP_CLASSPATH
    if [ -n "$LD_LIBRARY_PATH" ]; then
    LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$WL_HOME/lib/solaris:
    else
    LD_LIBRARY_PATH=$WL_HOME/lib/solaris:
    fi
    export LD_LIBRARY_PATH
    ADMIN_URL=$(cat $WL_SCRIPT/config.weblogic|grep AdminServerURL|awk '{print  $2}')
    ADMIN_SERVER_NAME=$(cat $WL_SCRIPT/config.weblogic|grep AdminServerName|awk '{print
    $2}')
    DOMAIN_NAME=$(cat $WL_SCRIPT/config.weblogic|grep Domain|awk '{print  $2}')
    PATH=$WL_HOME/bin:$JAVA_HOME/bin:$PATH
    export PATH
    WLS_PW=$(cat $WL_SCRIPT/bea.check | awk '{print $1}')
    export $WLS_PW
    #################################export LOG_HOME=/export/bea/netsite/ext-admin/logs/bea
    export LOG_HOME=/export/bea/logs
    # echo all of the variable settings
    #echo
    #echo "BEA_HOME=$BEA_HOME"
    #echo "WL_HOME=$WL_HOME"
    echo "EXPORT_HOME=$EXPORT_HOME"
    echo "CLASSPATH=$CLASSPATH"
    #echo "LD_LIBRARY_PATH=$LD_LIBRARY_PATH"
    #echo "PATH=$PATH"
    #echo "JAVA_OPTIONS=$JAVA_OPTIONS"
    #echo "DOMAIN_NAME=$DOMAIN_NAME"
    #echo "ADMIN_URL=$ADMIN_URL"
    #echo "ADMIN_SERVER_NAME=$ADMIN_SERVER_NAME"
    #java -fullversion
    #echo
    #echo
    # Grab some file descriptors.
    maxfiles='ulimit -H -n'
    if [ ! $? -a "$maxfiles" != 1024 ]; then
    if [ "$maxfiles" = "unlimited" ]; then
    maxfiles=1025
    fi
    if [ "$maxfiles" -lt 1024 ]; then
    ulimit -n $maxfiles
    else
    ulimit -n 1024
    fi
    fi
    # Set Production Mode. When set to true, the server starts up
    # in production mode. When set to false, the server starts up
    # in development mode. The default is false.
    STARTMODE=true
    if [[ -n $1 ]]; then
    if [[ $1 = "admin" ]]; then
    echo "Starting admin server...."
    ###### echo "See /export/netsite/ext-admin/logs/bea/admin.start for more info"
    # Change to the WebLogic directory
    cd $WL_HOME
    echo nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
    -Dweblogic.Name=$ADM
    IN_SERVER_NAME -Dbea.home=$BEA_HOME -Djava.security.policy==$WL_HOME/lib/weblogic.policy
    -Dweblogic.Production
    ModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW -Dweblogic.management.discover=true
    -Dweblogic.ma
    nagement.discover.retries=6 -Dweblogic.management.discover.interval=90 weblogic.Server
    nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
    -Dweblogic.Name=$ADMIN_SE
    RVER_NAME -Dbea.home=$BEA_HOME -Djava.security.policy==$WL_HOME/lib/weblogic.policy
    -Dweblogic.ProductionModeE
    nabled=$STARTMODE -Dweblogic.management.password=$WLS_PW -Dweblogic.management.discover=true
    -Dweblogic.managem
    ent.discover.retries=6 -Dweblogic.management.discover.interval=90 weblogic.Server
    $LOG_HOME/admin.start 2>&1&
    echo
    shift
    # Change back to the domain directory
    cd config/$DOMAIN_NAME
    echo $! > admin.pid
    else
    while [[ $# -gt 0 ]];do
    SERVER_NAME=$(cat $WL_SCRIPT/config.weblogic|grep $1|awk '{print $2}')
    if [[ $SERVER_NAME = "" ]]; then
    echo "ERROR: unable to locate an entry for "$1" in config file"
    shift
    else
    echo "Starting server: "$SERVER_NAME
    ######### echo "See /export/netsite/ext-admin/logs/bea/$SERVER_NAME.start
    for more info"
    # Change to the WebLogic directory
    cd $WL_HOME
    echo nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
    -Dweblogic.Nam
    e=$SERVER_NAME -Dweblogic.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic.policy
    -Dw
    eblogic.ProductionModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW
    weblogic.Server
    nohup java $JAVA_OPTIONS -classpath $CLASSPATH -Dweblogic.Domain=$DOMAIN_NAME
    -Dweblogic.Name=$SE
    RVER_NAME -Dweblogic.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic.policy
    -Dweblog
    ic.ProductionModeEnabled=$STARTMODE -Dweblogic.management.password=$WLS_PW weblogic.Server
    $LOG_HOME/$SERVER_NAME.start 2>&1 &
    shift
    # Change back to the domain directory
    cd config/$DOMAIN_NAME
    echo $! > $SERVER_NAME".pid"
    fi
    done
    fi
    else
    echo ""
    echo ""
    echo "FATAL ERROR: You must specify the server to start. Either 'admin' or
    the server token"
    echo ""
    fi
    -----------Inline 1 ends-----------------
    2) startManagedWebLogic.sh(this is the Managed server start up script at wls8.1)
    ---------Inline 2 starts---------
    #!/bin/sh
    # This script is used to start a managed WebLogic Server for the domain in the
    # current working directory. This script reads in the SERVER_NAME and
    # ADMIN_URL as positional parameters, sets the SERVER_NAME variable, then
    # starts the server.
    # Other variables that startWLS takes are:
    # WLS_USER - cleartext user for server startup
    # WLS_PW - cleartext password for server startup
    # PRODUCTION_MODE - Set to true for production mode servers, false for
    # development mode
    # JAVA_OPTIONS - Java command-line options for running the server. (These
    # will be tagged on to the end of the JAVA_VM and MEM_ARGS)
    # JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
    # -hotspot, etc.)
    # MEM_ARGS - The variable to override the standard memory arguments
    # passed to java
    # For additional information, refer to the WebLogic Server Administration Guide
    # (http://e-docs.bea.com/wls/docs81/ConsoleHelp/startstop.html).
    #Set the New Java Path
    PATH=/opt/bea/jdk141_02/bin:$PATH
    # set up WL_HOME, the root directory of your WebLogic installation
    WL_HOME="/opt/bea/weblogic81"
    # set up common environment
    # Set Production Mode. When this is set to true, the server starts up in
    # production mode. When set to false, the server starts up in development
    # mode. If it is not set, it will default to false.
    PRODUCTION_MODE="true"
    # Set JAVA_VENDOR to java virtual machine you want to run on server side.
    JAVA_VENDOR="Sun"
    # Set JAVA_HOME to java virtual machine you want to run on server side.
    JAVA_HOME="/opt/bea/jdk141_02"
    set USE_CURRENT_JAVA_HOME "$@"
    . "${WL_HOME}/common/bin/commEnv.sh"
    shift 1
    # Set SERVER_NAME to the name of the server you wish to start up.
    ADMIN_URL=http://153.2.255.51:8001
    SERVER_NAME=
    # Set WLS_USER equal to your system username and WLS_PW equal
    # to your system password for no username and password prompt
    # during server startup. Both are required to bypass the startup
    # prompt.
    WLS_USER=
    WLS_PW=
    # Set JAVA_VM to java virtual machine you want to run on server side.
    # JAVA_VM="-server"
    # Set JAVA_OPTIONS to the java flags you want to pass to the vm. If there
    # are more than one, include quotes around them. For instance:
    # JAVA_OPTIONS="-Dweblogic.attribute=value -Djava.attribute=value"
    usage()
    echo "Need to set SERVER_NAME and ADMIN_URL environment variables or specify"
    echo "them in command line:"
    echo 'Usage: ./startManagedWebLogic.sh [SERVER_NAME] [ADMIN_URL]'
    echo "for example:"
    echo './startManagedWebLogic.sh managedserver1 http://localhost:7001'
    exit 1
    # Check for variables SERVER_NAME and ADMIN_URL
    # SERVER_NAME and ADMIN_URL must by specified before starting a managed server,
    # detailed information can be found at http://e-docs.bea.com/wls/docs81/adminguide/startstop.html.
    if [ ${#} = 0 ]; then
    if [ "x${SERVER_NAME}" = "x" -o "x${ADMIN_URL}" = "x" ]; then
    usage
    fi
    elif [ ${#} = 1 ]; then
    SERVER_NAME=${1}
    if [ "x${ADMIN_URL}" = "x" ]; then
    usage
    fi
    elif [ ${#} = 2 ]; then
    SERVER_NAME=${1}
    ADMIN_URL=${2}
    else
    usage
    fi
    # Start WebLogic server
    # Reset number of open file descriptors in the current process
    # This function is defined in commEnv.sh
    resetFd
    CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${CLASSPATH}"
    export CLASSPATH
    # Start WebLogic server
    echo CLASSPATH="${CLASSPATH}"
    echo
    echo PATH="${PATH}"
    echo
    echo "***************************************************"
    echo "* To start WebLogic Server, use a username and *"
    echo "* password assigned to an admin-level user. For *"
    echo "* server administration, use the WebLogic Server *"
    echo "* console at http://<hostname>:<port>/console *"
    echo "***************************************************"
    "$JAVA_HOME/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} \
    -Dweblogic.Name=${SERVER_NAME} \
    -Dweblogic.management.username=${WLS_USER} \
    -Dweblogic.management.password=${WLS_PW} \
    -Dweblogic.management.server=${ADMIN_URL} \
    -Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy" \
    weblogic.Server
    -------Inline 2 ends----------
    3) startWebLogic.sh(this is the Admin start up script at wls8.1)
    ---------Inline 3 starts-------
    #!/bin/sh
    # This script is used to start WebLogic Server for the domain in the current
    # working directory. This script simply sets the SERVER_NAME variable
    # and calls the startWLS.sh script under ${WL_HOME}/server/bin.
    # To create your own start script for your domain, all you need to set is
    # SERVER_NAME, then starts server.
    # Other variables that startWLS takes are:
    # WLS_USER - cleartext user for server startup
    # WLS_PW - cleartext password for server startup
    # PRODUCTION_MODE - Set to true for production mode servers, false for
    # development mode
    # JAVA_OPTIONS - Java command-line options for running the server. (These
    # will be tagged on to the end of the JAVA_VM and MEM_ARGS)
    # JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
    # -hotspot, etc.)
    # MEM_ARGS - The variable to override the standard memory arguments
    # passed to java
    # For additional information, refer to the WebLogic Server Administration
    # Console Online Help(http://e-docs.bea.com/wls/docs81/ConsoleHelp/startstop.html)
    #Set the New Java Path
    PATH=/opt/bea/jdk141_02/bin:$PATH
    # set up WL_HOME, the root directory of your WebLogic installation
    WL_HOME="/opt/bea/weblogic81"
    # set up common environment
    # Set Production Mode. When this is set to true, the server starts up in
    # production mode. When set to false, the server starts up in development
    # mode. If it is not set, it will default to false.
    PRODUCTION_MODE="true"
    # Set JAVA_VENDOR to java virtual machine you want to run on server side.
    JAVA_VENDOR="Sun"
    # Set JAVA_HOME to java virtual machine you want to run on server side.
    JAVA_HOME="/opt/bea/jdk141_02"
    set USE_CURRENT_JAVA_HOME "$@"
    . "${WL_HOME}/common/bin/commEnv.sh"
    shift 1
    # Set SERVER_NAME to the name of the server you wish to start up.
    SERVER_NAME=Admin
    # Set WLS_USER equal to your system username and WLS_PW equal
    # to your system password for no username and password prompt
    # during server startup. Both are required to bypass the startup
    # prompt.
    WLS_USER=
    WLS_PW=
    # Set JAVA_VM to java virtual machine you want to run on server side.
    # JAVA_VM="-server"
    # Set JAVA_OPTIONS to the java flags you want to pass to the vm. If there
    # are more than one, include quotes around them. For instance:
    # JAVA_OPTIONS="-Dweblogic.attribute=value -Djava.attribute=value"
    # Reset number of open file descriptors in the current process
    # This function is defined in commEnv.sh
    resetFd
    # Start WebLogic server
    CLASSPATH="${WEBLOGIC_CLASSPATH}${CLASSPATHSEP}${POINTBASE_CLASSPATH}${CLASSPATHSEP}${JAVA_HOME}/jre/lib/rt.jar${CLASSPATHSEP}${WL_HOME}/server/lib/webservices.jar${CLASSPATHSEP}${CLASSPATH}"
    export CLASSPATH
    "$JAVA_HOME/bin/java" ${JAVA_VM} ${MEM_ARGS} ${JAVA_OPTIONS} -Dweblogic.Name=${SERVER_NAME}
    -Dweblogic.management.username=${WLS_USER} -Dweblogic.management.password=${WLS_PW}
    -Dweblogic.ProductionModeEnabled=${PRODUCTION_MODE} -Djava.security.policy="${WL_HOME}/server/lib/weblogic.policy"
    weblogic.Server
    --------Inline 3 ends---------
    I think we are getting closer to a solution !
    thanks rob,
    Rob Woollen <[email protected]> wrote:
    Yes, your $CLASSPATH could be the issue. Can you show me the $CLASSPATH
    used in each version of the server?
    -- Rob
    sangita wrote:
    Thanks Rob, I understood changing the DOCTYPE ...and i will give ita try.
    And iam assuming you might have read my previous response in this chain,Iam using
    WLS6.1 & WLS8.1 BOTH on the same hardware unix server....iam just wonderingif
    there is any CLASSPATH issue that might have been causing this NoClassDefFoundError......?
    just wanted to let you know that iam running WLS6.1 + WLS8.1 on thesame BOX.
    I will try other options that you have suggested ....thanks again !
    Rob Woollen <[email protected]> wrote:
    sangita wrote:
    Rob,
    Right, you're referencing the Taglib 1.2 DTD, but your tld file conforms
    to the Taglib 1.1 DTD. You'll either need to change the DOCTYPE
    definition to the Taglib 1.1 DTD or change the tld file to conformto
    the 1.2 DTD. how do i do either of the 2 options ?To change your taglib to be the 1.1 DTD you just need to change the
    DOCTYPE header to be
    <!DOCTYPE taglib
    PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
    "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
    Otherwise, you'll need to change the tld file to be JSP 1.2 compliant.
    If you post your tld file here, then I can help.
    Iam just guessing here, is it may be due to this DTD/.tld issue thatiam not been
    able to DEPLOY the .ear file(now that wls8.1 checks the validity beforedeloying
    the app)....are the 2 errors that iam getting, in any ways inter-related?
    I'm not sure they're related. It is possible.
    i.e is it possible that due to DTD/.tld ....am i getting this NoClassDefFoundError
    JUST CURIOUS ???
    WELL THANKS FOR YOUR TIME ON THIS ...REALLY APPRECIATE IT !
    No problem.
    -- Rob
    Regards, sangita
    Rob Woollen <[email protected]> wrote:
    sangita wrote:
    1) This is how my .tld looks like:
    <?xml version="1.0" encoding="UTF-8" ?>^M
    <!DOCTYPE taglib^M
    PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.2//EN"^M
    "http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd">^M
    Right, you're referencing the Taglib 1.2 DTD, but your tld file conforms
    to the Taglib 1.1 DTD. You'll either need to change the DOCTYPE
    definition to the Taglib 1.1 DTD or change the tld file to conformto
    the 1.2 DTD. Unfortunately WLS 6.1 didn't validate the tld file
    against
    the DTD, but it should have, and you'll need to correct your application.
    <taglib>^M
    <tlib-version>1.0</tlib-version>^M
    <jsp-version>1.2</jsp-version>^M
    <short-name>html</short-name>^M
    2) the MANIFEST.MF file is located within the ABL.war.
    3) I will try placing the struts-util.jar in the WEB-INF/lib directoryof the
    ABL.war file. And I will let you if it works or not ?Right. My guess is this is a bug in WLS 8.1. I can see no reasonwhy
    the manifest class-path isn't working for you. That's why I askedif
    you could send the EAR file so I could investigate, but I understand
    that's not always possible.
    I suspect the WEB-INF/lib will work, but it's just a workaround.
    I'm
    not sure if you're using 8.1 or 8.1SP1, but if you're not using SP1,
    then you might consider trying that. (java weblogic.version willtell
    you.)
    Otherwise, I think you should open a case with [email protected]
    -- Rob
    thx, sangita
    Rob Woollen <[email protected]> wrote:
    sangita wrote:
    Rob, here is the information that you need: Please read inline:
    ---------------------------iam doing cut&paste
    <attribute>^M
    <name>styleClass</name>^M
    <required>false</required>^M
    </attribute>^M
    (this is the 334 line)<info>applys the style of
    the
    number text
    if it passes the conditional given</info>^M
    </tag>^M
    </taglib>^MWell, it looks like you have a JSP 1.1 tld, but it's being validated
    against the JSP 1.2 tld. I suspect that you have not declareda
    DOCTYPE
    and 6.1 defaulted to the older JSP spec.
    Anyway, check the first line of your tld file. It should look
    something
    like this:
    <!DOCTYPE taglib
    PUBLIC "-//Sun Microsystems, Inc.//DTD JSP Tag Library 1.1//EN"
         "http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd">
    I have an ABL.ear file and this is what it looks like:
    ABL.ear
    META-INF/
    META-INF/MANIFEST.MF
    ABL.jar
    ABL.war
    lib/
    lib/struts-util.jar
    META-INF/application.xml
    and in the ABL.war ...there is a META-INF/MANIFEST.MF file ...and
    when
    i open
    this file ...this is what it contains:Just to double-check, the MANIFEST.MF file is located within the
    ABL.war, right?
    Manifest-Version: 1.0
    Created-By: Ant 1.4.1
    Class-Path: lib/struts-util.jar
    there is nothing in the CLASSPATH that contains this application'sspecific .jar/.war
    ...or any classes specific to this application ........BOTH IN
    WLS6.1(and
    now
    in WLS8.1)Hmm, I'm not sure yet what the problem is here. Does it work ifyou
    place the struts-util.jar in the WEB-INF/lib directory of the ABL.war
    file? (I suspect it will.)
    This might be a WLS bug. If you can post your ear file here (oremail
    it to me rwoollen at bea dot com), then I can dig into it more.
    -- Rob
    thx, sangita
    Rob Woollen <[email protected]> wrote:
    It looks like there are 2 errors.
    The first error /WEB-INF/ups-html.tld is most likely the result
    of
    WLS
    8.1 doing more validation on your tld file. If you'd show us
    either
    the
    entire ups-html.tld or just the part around line 334, then wecan
    help.
    As for the NoClassDefFoundError, you'll have to provide some
    more
    details about your ear file and environment. Do you have anythingin
    the $CLASSPATH on either the 6.1 or 8.1 environments?
    -- Rob
    Sangita wrote:
    I think the weblogic8.1 seems to have some NEW bug now. We have
    a
    .ear
    file that
    works just PERFECT in WLS6.1. But now when we try to DEPLOY
    this
    .ear
    file our
    WLS8.1 server(via the new look and feel of WLS8.1' console)....we
    are
    getting
    the Exception like ...."pl read inline below":
    ...All i know is that WLS 8.1 has introduced something like
    "single
    J2EEC -
    EAR compiler, replacing the separate compilers in previous releases"........is
    it may be because of this ????
    If somebody has any idea ....please let me know asap ...and
    just
    above
    the EXCEPTION
    we are also getting something like ...."Deployment descriptor
    "/WEB-INF/ups-html.tld"
    is malformed" ....what is going wrong now ?
    Please note again ....this .ear file just work PERFECT in WLS6.1+sp2.
    Read inline for the Exception:
    <Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248>
    <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
    Deployment descriptor "/WEB-INF/ups-html.tld" is malformed.Check
    against
    the
    DTD: Element type "info" must be declared. (line 334, column
    9).>
    <Jul 16, 2003 11:15:14 AM EDT> <Warning> <HTTP> <BEA-101248><[ServletContext(id=4316640,name=ABL,context-path=/ABL)]:
    Deployment descriptor "/WEB-INF/ups-html.tld" is malformed.Check
    against
    the
    DTD: The content of element type "tag" must match "(name,tag-class,tei-class?,body-content?,display-name?,small-icon?,large-icon?,description?,variable*,attribute*,example?)".
    (line 335, column 8).>
    MessageResourcesFactory.createFactory
    java.lang.NoClassDefFoundError: org/apache/struts/util/MessageResourcesFactory
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:431)
    at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:169)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:292)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
    at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:41)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:140)
    at org.apache.struts.util.MessageResourcesFactory.createFactory(MessageResourcesFactory.java:161)
    at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1029)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5559)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:853)
    at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2012)
    at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2053)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2558)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2483)
    at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2308)
    at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:639)
    at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    <Jul 16, 2003 11:15:14 AM EDT> <Error> <HTTP> <BEA-101046> <[ServletContext(id=4316640,name=ABL,context-path=/ABL)]
    service: Cannot load application resources bundle com.ups.dfd.abl.prop.Constants
    java.lang.NullPointerException
    at org.apache.struts.action.ActionServlet.initApplication(ActionServlet.java:1031)
    at org.apache.struts.action.ActionServlet.init(ActionServlet.java:464)
    at javax.servlet.GenericServlet.init(GenericServlet.java:258)
    at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1070)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:893)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3191)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3136)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3109)
    at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.

  • Struts, JSP 1.1 spec and WLS 5.1 - issue with useBean and getProperty

    Hi there, I am attempting to compile a JSP page using Struts tag libraries and Weblogic 5.1 with Service Pack 9.I have defined the bean using <jsp:UseBean id="myBean" ... > and then attempt to access its methods using <jsp:getProperty name="myBean" ... > This fails with a 'myBean is not defined as bean' error. When I replace the <jsp:getProperty ...> with a scriptlet e.g. <%= myBean.getCustomerName()%> it compiles and runs just fine.I have read that the WLS server may be enforcing a strict implementation of JSP spec 1.1 which the Struts tags may not be adhering to (?).Oddly, when I start WLS without invoking the Service Pack, the error disappears and the <jsp:getProperty> works as expected!Any official reason for this strange behaviour? ... I'd like to avoid using scriptlets if possible.Thanks in advance,Rash
              

    Hi.
    The following link shows supported versions of apache:
    http://edocs.bea.com/wls/platforms/index.html#apach
    In short, WLS 5.1 does not support Apache 1.3.20. The latest supported version is
    1.3.19.
    Regards,
    Michael
    Mauricio Guerra wrote:
    Hello, i've read all the online documentation regarding the apache plug in for
    weblogic, and i haven't
    found an answer to my question:
    Does weblogic 5.1 sp8 works ok with apache 1.3.20/SSL?
    All the documentation talks mention apache 1.3.12 only...
    thanks,
    Mauricio--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • JAXB External Custom Bindings Issue

    I have a very large schema that I am trying to bind using JAXB. The naming in the schema is very good, nor is the structure, so I was hoping to do some custom binding. When I went to start the custom binding in an external file XJC returns an error saying that the target node is empty. It works fine if I give it the schema location and point it at the root of the schema, but trying to access the first complex type doesn't work. My external custom bindings file is below, an excerpt from the XSD Follows it, as well as my error. Please keep in mind that I cannot modify the schema in anyway.
    <?xml version="1.0" encoding="UTF-8"?>
    <jxb:bindings xmlns:jxb="http://java.sun.com/xml/ns/jaxb"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" jxb:version="1.0"
    schemaLocation="fgdc.xsd">
    <jxb:bindings node="/xsd:schema">
    <jxb:schemaBindings>
    <jxb:package name="gov.noaa.clas.neaat.schema.fgdc"/>
    </jxb:schemaBindings>
    </jxb:bindings>
    <jxb:bindings node="//xsd:complexType'@name=metadataType'">
    <jxb:class name="FgdcMetadataInterface" implClass="FgdcMetadata">
    <jxb:javadoc>Data about the content, quality, condition, and other
    characteristics of data.</jxb:javadoc>
    </jxb:class>
    </jxb:bindings>
    </jxb:bindings>
    <xsd:complexType name="metadataType">
    <xsd:sequence>
    <xsd:element ref="idinfo"/>
    <xsd:element ref="dataqual" minOccurs="0"/>
    <xsd:element ref="spdoinfo" minOccurs="0"/>
    <xsd:element ref="spref" minOccurs="0"/>
    <xsd:element ref="eainfo" minOccurs="0"/>
    <xsd:element ref="distinfo" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element ref="metainfo"/>
    </xsd:sequence>
    </xsd:complexType>[xjc] Compiling file:/C:/Joshua/trunk/schema/schema/data.xsd and others
    [xjc] [ERROR] XPath evaluation of "//xsd:complexType'@name=metadataType'" results in empty target node
    [xjc] line 10 of file:/C:/Joshua/trunk/schema/schema/fgdc.xjb

    I have a very large schema that I am trying to bind using JAXB. The naming in the schema is very good, nor is the structure, so I was hoping to do some custom binding. When I went to start the custom binding in an external file XJC returns an error saying that the target node is empty. It works fine if I give it the schema location and point it at the root of the schema, but trying to access the first complex type doesn't work. My external custom bindings file is below, an excerpt from the XSD Follows it, as well as my error. Please keep in mind that I cannot modify the schema in anyway.
    <?xml version="1.0" encoding="UTF-8"?>
    <jxb:bindings xmlns:jxb="http://java.sun.com/xml/ns/jaxb"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" jxb:version="1.0"
    schemaLocation="fgdc.xsd">
    <jxb:bindings node="/xsd:schema">
    <jxb:schemaBindings>
    <jxb:package name="gov.noaa.clas.neaat.schema.fgdc"/>
    </jxb:schemaBindings>
    </jxb:bindings>
    <jxb:bindings node="//xsd:complexType'@name=metadataType'">
    <jxb:class name="FgdcMetadataInterface" implClass="FgdcMetadata">
    <jxb:javadoc>Data about the content, quality, condition, and other
    characteristics of data.</jxb:javadoc>
    </jxb:class>
    </jxb:bindings>
    </jxb:bindings>
    <xsd:complexType name="metadataType">
    <xsd:sequence>
    <xsd:element ref="idinfo"/>
    <xsd:element ref="dataqual" minOccurs="0"/>
    <xsd:element ref="spdoinfo" minOccurs="0"/>
    <xsd:element ref="spref" minOccurs="0"/>
    <xsd:element ref="eainfo" minOccurs="0"/>
    <xsd:element ref="distinfo" minOccurs="0" maxOccurs="unbounded"/>
    <xsd:element ref="metainfo"/>
    </xsd:sequence>
    </xsd:complexType>[xjc] Compiling file:/C:/Joshua/trunk/schema/schema/data.xsd and others
    [xjc] [ERROR] XPath evaluation of "//xsd:complexType'@name=metadataType'" results in empty target node
    [xjc] line 10 of file:/C:/Joshua/trunk/schema/schema/fgdc.xjb

  • WLS 5.1 to 6.1 porting issue: RequiresNew & ORA-01002 error

    Repost from the EJB group
    Environment:
    WLS 6.1.2 on WINNT w/SP6a
    java: 1.3.1 that ships with WLS 6.1
    DB: Oracle 8.1.6 (using TRANSACTION_READ_COMMITTED exclusively)
    I'm currently upgrading our application from 5.1 (ejb 1.1) to
    6.1 (ejb 2.0). I've also consolidated our 55 separate ejb jars
    into a single jar (with all 55 ejbs). Because of 1.1 entity bean
    issues, currently all our ejbs are SessionBeans. Everything works
    under 5.1 with our test Oracle instance, the 6.1 test environment
    is using the same database instance.
    I'm seeing several problems.
    Here's #1
    With the same TCUSecurityDataAccessSessionBean::updateIfNeeded
    source code and same database instance. 5.1 updates correctly,
    6.1 throws this SQLException. So, I figure its got to be a WLS 6.1 issue or
    my configuration. - I alway suspect me ;)
    ERROR - ORA-01002: fetch out of sequence
    (com.eoriginal.engine.core.session.basicAccess.TCUSecurityDataAccessSessionB
    ean_ridhfi_Impl::updateIfNeeded)
    java.sql.SQLException: ORA-01002: fetch out of sequence
    This method should be configured with transaction context of: RequiresNew
    Has the 6.1 handling of RequiresNew changed that radically?
    I'm looking for suggestions on how to debug this further.
    TIA
    Gordon
    ------------- ejb-jar.xml (edited) ------------------------
    <ejb-jar>
    <small-icon>images/green-cube.gif</small-icon>
    <enterprise-beans>
    <!-- TCUSecurityDataAccessSession -->
    <session>
    <small-icon>images/orange-cube.gif</small-icon>
    <ejb-name>TCUSecurityDataAccessSession</ejb-name>
    <home>com.eoriginal.engine.core.session.basicAccess.TCUSecurityDataAccessSes
    sionHome</home>
    <remote>com.eoriginal.engine.core.session.basicAccess.TCUSecurityDataAccessS
    ession</remote>
    <ejb-class>com.eoriginal.engine.core.session.basicAccess.TCUSecurityDataAcce
    ssSessionBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <method-permission>
    <description></description>
    <role-name>****</role-name> <!-- deleted for security -->
    <method>
    <ejb-name>TCUSecurityDataAccessSession</ejb-name>
    <method-name>*</method-name>
    </method>
    </method-permission>
    <!-- TCUSecurityDataAccessSession -->
    <container-transaction>
    <method>
    <ejb-name>TCUSecurityDataAccessSession</ejb-name>
    <method-name>updateIfNeeded</method-name>
    </method>
    <trans-attribute>RequiresNew</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>TCUSecurityDataAccessSession</ejb-name>
    <method-name>peek</method-name>
    </method>
    <trans-attribute>Supports</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    ------------- weblogic-ejb-jar.xml (uninteresting) ------------------------
    ------------- config.xml (edited) ------------------------
    <JDBCConnectionPool CapacityIncrement="5"
    DriverName="oracle.jdbc.driver.OracleDriver"
    InitialCapacity="10" MaxCapacity="100" Name="d2Pool"
    Password="*****
    Properties="user=d2engine;STATEMENT_CACHE_SIZE=200"
    Targets="myserver" URL="jdbc:oracle:thin:@*****"/>
    <JDBCTxDataSource JNDIName="jdbc/d2Pool" Name="jdbc/d2Pool"
    PoolName="d2Pool" Targets="myserver"/>
    ORA-01002 fetch out of sequence
    Cause: In a host language program, a FETCH call was issued out of sequence.
    A successful parse-and-execute call must be issued before a fetch.
    This can occur if an attempt was made to FETCH from an active set after
    all records have been fetched.
    This may be caused by fetching from a SELECT FOR UPDATE cursor after a
    commit.
    A PL/SQL cursor loop implicitly does fetches and may also cause this error.
    Action: Parse and execute a SQL statement before attempting to fetch the
    data.

    Solved.
    The 8.1.6 driver wasn't the problem.
    It turned out that our ConnectionPool utility class wasn't configured
    properly
    and when I thought that I was going TxDatasource, I was actually only
    getting
    a straight Connection. No Tx, so Oracle didn't have one open for the "FOR
    UPDATE"
    clause. Now if someone could help on my classloader question in the EJB
    group ;)
    - Gordon
    "Slava Imeshev" <[email protected]> wrote in message
    news:[email protected]...
    Gordon,
    Oracle 8.1.6 driver proved to be buggy and unstable.
    Can you update your oracle thin driver to the newest
    one? It's available from the otn.oracle.com.
    Could you also post the questionable code here, especially
    in the part related to obtaining connection, executing
    stataments, fetching results and obtaining TXs, if any?
    Regards,
    Slava Imeshev
    "Gordon Twaddell" <[email protected]> wrote in message
    news:[email protected]...
    Sree,
    I didn't mention that I'm using the Oracle thin JDBC driver
    (8.1.6.1)
    and its in the CLASSPATH.
    Slava,
    I tried the stmt.setFetchSize(). I got the same result.
    Gordon
    "Sree Bodapati" <[email protected]> wrote in message
    news:[email protected]...
    Hi Gordon,
    One possibility is the environment variable PATH might be pointing to
    an
    older version of the library files for the WebLogic jDriver forOracle.
    Check if the PATH is set to point to the right weblogicoci37.dll (inthe
    <WL_HOME for 6.1>\bin\oci817_8) and make sure your oracle_home is setto
    point to the right folders as well.
    hth
    sree
    "Gordon Twaddell" <[email protected]> wrote in message
    news:[email protected]...
    Repost from the EJB group
    Environment:
    WLS 6.1.2 on WINNT w/SP6a
    java: 1.3.1 that ships with WLS 6.1
    DB: Oracle 8.1.6 (using TRANSACTION_READ_COMMITTED exclusively)
    I'm currently upgrading our application from 5.1 (ejb 1.1) to
    6.1 (ejb 2.0). I've also consolidated our 55 separate ejb jars
    into a single jar (with all 55 ejbs). Because of 1.1 entity bean
    issues, currently all our ejbs are SessionBeans. Everything works
    under 5.1 with our test Oracle instance, the 6.1 test environment
    is using the same database instance.
    I'm seeing several problems.
    Here's #1
    With the same TCUSecurityDataAccessSessionBean::updateIfNeeded
    source code and same database instance. 5.1 updates correctly,
    6.1 throws this SQLException. So, I figure its got to be a WLS 6.1
    issue
    or
    my configuration. - I alway suspect me ;)
    ERROR - ORA-01002: fetch out of sequence
    (com.eoriginal.engine.core.session.basicAccess.TCUSecurityDataAccessSessionB
    ean_ridhfi_Impl::updateIfNeeded)
    java.sql.SQLException: ORA-01002: fetch out of sequence
    This method should be configured with transaction context of:RequiresNew
    Has the 6.1 handling of RequiresNew changed that radically?
    I'm looking for suggestions on how to debug this further.
    TIA
    Gordon
    ------------- ejb-jar.xml (edited) ------------------------
    <ejb-jar>
    <small-icon>images/green-cube.gif</small-icon>
    <enterprise-beans>
    <!-- TCUSecurityDataAccessSession -->
    <session>
    <small-icon>images/orange-cube.gif</small-icon>
    <ejb-name>TCUSecurityDataAccessSession</ejb-name>
    <home>com.eoriginal.engine.core.session.basicAccess.TCUSecurityDataAccessSes
    sionHome</home>
    <remote>com.eoriginal.engine.core.session.basicAccess.TCUSecurityDataAccessS
    ession</remote>
    <ejb-class>com.eoriginal.engine.core.session.basicAccess.TCUSecurityDataAcce
    ssSessionBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <method-permission>
    <description></description>
    <role-name>****</role-name> <!-- deleted for security -->
    <method>
    <ejb-name>TCUSecurityDataAccessSession</ejb-name>
    <method-name>*</method-name>
    </method>
    </method-permission>
    <!-- TCUSecurityDataAccessSession -->
    <container-transaction>
    <method>
    <ejb-name>TCUSecurityDataAccessSession</ejb-name>
    <method-name>updateIfNeeded</method-name>
    </method>
    <trans-attribute>RequiresNew</trans-attribute>
    </container-transaction>
    <container-transaction>
    <method>
    <ejb-name>TCUSecurityDataAccessSession</ejb-name>
    <method-name>peek</method-name>
    </method>
    <trans-attribute>Supports</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    ------------- weblogic-ejb-jar.xml(uninteresting) ------------------------
    ------------- config.xml (edited) ------------------------
    <JDBCConnectionPool CapacityIncrement="5"
    DriverName="oracle.jdbc.driver.OracleDriver"
    InitialCapacity="10" MaxCapacity="100" Name="d2Pool"
    Password="*****
    Properties="user=d2engine;STATEMENT_CACHE_SIZE=200"
    Targets="myserver" URL="jdbc:oracle:thin:@*****"/>
    <JDBCTxDataSource JNDIName="jdbc/d2Pool" Name="jdbc/d2Pool"
    PoolName="d2Pool" Targets="myserver"/>
    ORA-01002 fetch out of sequence
    Cause: In a host language program, a FETCH call was issued out ofsequence.
    A successful parse-and-execute call must be issued before a fetch.
    This can occur if an attempt was made to FETCH from an active set
    after
    all records have been fetched.
    This may be caused by fetching from a SELECT FOR UPDATE cursor
    after
    a
    commit.
    A PL/SQL cursor loop implicitly does fetches and may also cause
    this
    error.
    Action: Parse and execute a SQL statement before attempting to fetch
    the
    data.

  • CR183190 in WLS 8.1 SP4

    Hi.
    I'm using WLS 8.1 SP4 (with CR132575) and just ran into a problem with my datasources using the BEA's DB2 driver(Type 4 XA). The error I receive is:
    [BEA][DB2 JDBC Driver]No more available statements. Please recreate your package with a larger dynamicSections value.
    When searching for this using Google I found out that this was a known issue in SP3 and SP4: CR183190 (http://e-docs.bea.com/wls/docs81/notes/issues.html#1293456). However, another page (http://e-docs.bea.com/wls/docs81/notes/resolved_sp04.html#1862094) says that it is resolved in SP4.
    Can anyone confirm whether or not it should be resolved? And if it is resolved, what else could be causing the error message I am receiving.
    /Michael

    garbage66 wrote:
    Hi,
    I would really appreciate if you could send me the CR.
    My specifications:
    WebLogic Temporary Patch for CR132575 01/05/2004 13:00:03
    WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
    Regards,
    MichaelHi. Contact support and get the very latest 3.4 driver package.
    There was a problem in the DB2 driver that could cause that.
    If that doesn't help, let me know and I'll have another
    suggestion.
    Joe
    j ----
    o ----
    e ----
    b
    e
    a
    c
    o
    m

  • EJB in WLS - CORBA and EJB on WLE

    I have a client who is looking to attach a C++ client to their WLE
    system, and, since
    they now have WLS and WLE thanks to v. 5.1, they want to start moving
    EJBs to the
    WLS platform. The issue is this.
    What if any are the issues regarding communicating between CORBA objects
    on WLE
    TO EJBs on WLS? I noticed that the illustrations always show the
    communication coming
    from the WLS side to the WLE side, but this client will be connected
    directly to the WLE
    platform, and wanting to access services on WLS.
    Any issues, directions to documentation, or other advice regarding this
    issue?
    Thanks in advance,
    Maffy
    [maffy.vcf]

    can anyone give code example for accessing WLS-EJB from WLE corba client.
    louc wrote:
    Interesting how things can be interpreted. What we need is direct input
    from engineering on this.
    In studying the only direct source of information we have... (the docs...
    and ass-u-me'ing that the docs are correct) it appears that we can have a
    CORBA object in WLE access a EJB in WLS through RMI/IIOP as long as the
    parameter passing is kept to primitive data types. Any attempt to use the
    'Object-by-Value' feature of CORBA 2.3 will result in a error because WLE
    5.1 does not support passing 'Object-by-Value' at this time.
    So to answer Maffy's question... yes a WLE CORBA client can access a WLS EJB
    service through RMI over IIOP.
    -- Lou Caraballo
    Sr. Systems Engineer
    BEA Systems Inc., Denver Telco Group
    719-332-0818 (cell)
    720-528-6073 (denver)
    Robert Patrick <[email protected]> wrote in message
    news:[email protected]...
    The issue is that WLE does not yet support the RMI/IIOP standard (since itdoes not yet support
    Objects by Value) not that the RMI/IIOP support in WLS 5.1 (as of SP3)does not support
    bi-directional communication.
    Papaya Head wrote:
    so, you are saying bi-directional communication is not supported... can
    you tell me what
    rmi/iiop is for?
    Thanks.
    Maffy Finnerty wrote:
    Okay, found a work around thanks to Deepak Sharma (THANK YOU,
    DEEPAK!!) in the BEA
    East office.
    What my customer is going to have to do for now - until, as Will Lyonspointed out, the
    bi-directional
    communication is supported - is to build a Java "client" process onWLE that communicates
    with the
    RMI/EJB/Servlet process on WLS.
    Deepak suggested that the best way, since they are a CORBA shop tryingto move to Java,
    would be to have the C++ client talking to a CORBA/C++ object on WLEthat calls
    a CORBA/Java object on WLE that acts as a client to WLS and accessesthe services of the
    Java object on that server.
    Another option would be to have the CORBA/C++ object on WLE use theJNI API to call a Java
    object
    on WLE that acts as a client to WLS and accesses the Java servicerunning there. There may
    be better
    performance from CORBA/C++ to CORBA/Java, though, so that was Deepak'sfirst choice.
    Maffy
    Papaya Head wrote:
    you can also find an example in the WLS5.1 docs that includes a code
    segment from C++
    client of the RMI-IIOP hello example.
    Will Lyons wrote:
    The example application with C++ CORBA objects calling EJBs on a
    Java Server refers
    to C++ CORBA objects on the WLE T-Engine calling EJBs on the WLET-Engine. That
    interoperability capability is supported, but it is not possibleto call the J-Engine
    from the T-Engine in WLE 5.1. The primary usage model assumed inWLE 5.1 is calling
    the WLE T-Engine from the J-Engine (or from WLS).
    Will
    Papaya Head wrote:
    my understanding of your question is: you want some feature that
    allows CORBA
    objects to talk to EJB objects on WLS.
    WLS5.1 has a new feature: RMI/IIOP, it's probably the featureyou want.
    before WLS5.1, CORBA components couldn't talk to EJB componentsdirectly, but you
    could make it happen by building a bridge from CORBA objects toEJB components on
    WLS. that's probably what the references you read are talkingabout...
    Maffy Finnerty wrote:
    We haven't even gotten that far yet, re: transactions. Right
    now the issue is
    having an
    in-house client (C++) connected to WLE but accessing services(EJBs) on WLS.
    No talk
    of transactions has occurred, yet.
    However, I just found some conflicting information. I found areference to
    building the
    simpapp application to connect C++ objects on a CORBA serverto EJBs on a Java
    Server,
    which, if I'm reading it correctly, translates to WLE to WLS.However, I also
    found a
    reference to bidirectional interoperability that said that,for now, the
    T-Engine could not
    (WLE) could NOT invoke services on the J-Engine (WLS) but thatservices on the
    T-Engine
    (WLE) could BE invoked from requesters on the J-Engine (WLS).So, color me
    confused.
    maffy
    Papaya Head wrote:
    the first question that comes to my mind is:
    can transaction run across components on WLE and components
    on WLS? I don't
    think it can...
    Maffy Finnerty wrote:
    I have a client who is looking to attach a C++ client to
    their WLE
    system, and, since
    they now have WLS and WLE thanks to v. 5.1, they want tostart moving
    EJBs to the
    WLS platform. The issue is this.
    What if any are the issues regarding communicating betweenCORBA objects
    on WLE
    TO EJBs on WLS? I noticed that the illustrations alwaysshow the
    communication coming
    from the WLS side to the WLE side, but this client will beconnected
    directly to the WLE
    platform, and wanting to access services on WLS.
    Any issues, directions to documentation, or other adviceregarding this
    issue?
    Thanks in advance,
    Maffy

  • Information transfer from J2ME client to WLS 8.1 sp3 thru' SSL

    Hi,
    We are planning to have a J2ME client (CLDC 1.0 and MIDP 2.0) to transfer information to Weblogic server 8.1 sp3 through SSL. We are planning to use Verisign certificate at the Weblogic server to implement the SSL communication. Could you please let me know if there is any issue?
    I came across from BEA web-site
    (http://e-docs.bea.com/wls/docs81/notes/issues.html#1278025)recently that J2ME clients have certain issues to talk to WLS. That page says:
    Web Services Known Issues
    Change Request Number CR107595
    Description
    SSL does not work for J2ME clients on WebLogic Server 8.1.
    Certicom SSL libraries require additional features that are not supported by J2ME. Therefore, SSL is not supported for J2ME clients on WebLogic Server 8.1.
    That is why I am little apprehensive. Please advise.
    Thanks,
    Goutam.

    1) sorry, there is no official solution of "1999 schema" problem that I know of.
    2) if the service is not changed, there is no need to re-create call or stub object for every invocation.

  • Getting WLS 7.0.0.1?

    I've seen references to a 7.0.0.1 version of WebLogic Server, but I
    can't seem to find where to download the patch on the website. I'm
    downloading the 133MB package installer, which might be it (the 7.0.0.0
    version I currently have is only 87MB)
    Is there a page somewhere that shows patches, which bugs were fixed, etc
    instead of relying on periodically downloading the huge installer file
    and seeing if the version has been updated?
    Thanks,
    -Paul

    Yes, that is exactly what I was looking for...thanks Glenn!
    -Paul
    Glenn Dougherty wrote:
    Paul,
    It looks like you were able to download 7.0.0.1 from the download site,
    based upon your other newsgroup posting. The following link to our online
    docs (release notes, etc.) may be what you're looking for in terms of bugs,
    etc.
    http://e-docs.bea.com/wls/docs70/notes/issues.html#1052042
    Regards,
    Glenn
    Developer Relations Engineer
    BEA Technical Support
    "Paul D. Schmidt" wrote:
    I've seen references to a 7.0.0.1 version of WebLogic Server, but I
    can't seem to find where to download the patch on the website. I'm
    downloading the 133MB package installer, which might be it (the 7.0.0.0
    version I currently have is only 87MB)
    Is there a page somewhere that shows patches, which bugs were fixed, etc
    instead of relying on periodically downloading the huge installer file
    and seeing if the version has been updated?
    Thanks,
    -Paul

  • WLS Architecture

    Can anyone tell me what the best system architecture for WebLogic
    Servers are?
    I've heard a lot of different things. One is that if you have a Solaris
    box with two processors, you should run with two instances on the same
    machine. That would be alright, but we plan on implementing a clustered
    environment in the future.
    Another is that we should have one WebLogic Server on our Solaris box.
    When we are doing load testing we are unable to saturate the CPU.
    When we run the load test our execution queue rapidly increases to 50 or
    60 and the response time gradually increases. Everything works fairly
    well when we test with 10 to 20 users. Any more than that our
    application becomes useless. Everything slows to almost a halt. If
    someone could tell me what an optimal setup would be for WLS in a single
    server environment is, that would be great. I've done everything by the
    book. I just want to hear it from someone with more experience. I'm
    hoping it's not the application that is doing this.
    thanks

    Chris
    First, I would suggest try to find the bottleneck - It can be client machine,
    the network, Database or maybe WLS. To detect it, some suggestions/pointers:
    0. Monotor the resource utilization on the client machine - CPU, memory,
    network etc.
    1. During your test, use the WLS console to monitor the # of requests in the
    input queue. On average, how many requests are there in the queue and how long
    does it takes to drain them off. If there a large number of request in the
    queue, it suggests that the requests are indeed arriving in the WLS otherwise
    the issue may be with your client machine or your network, TCP etc.
    2. Check the memory utilization. Is the system running out of memory. If so,
    increase the heap size.
    3. Use a profiler to detect where the bottleneck is - Database access,
    interface with other resources, contention for some resources etc. (You can
    monitor JDBC interaction with jdbc.log.)
    4. Set the ThreadCount and Connection pool in conjunction.
    Designing an optimal layout is an application specific issue.
    Cheers
    Venkatesh Iyer
    Robert Patrick schrieb:
    There are a lot of factors that go into tuning and load-testing your WLS
    application. First of all, we have found that it takes somewhere between 2
    and 5 times as much client hardware to drive the server to saturation. As
    Srikant mentioned, the TCP device driver parameters can play a significant
    role in throttling the client requests into the server(s). You might want
    to get someone from BEA involved in your testing to help you work through
    these issues.
    Robert
    Chris wrote:
    Can anyone tell me what the best system architecture for WebLogic
    Servers are?
    I've heard a lot of different things. One is that if you have a Solaris
    box with two processors, you should run with two instances on the same
    machine. That would be alright, but we plan on implementing a clustered
    environment in the future.
    Another is that we should have one WebLogic Server on our Solaris box.
    When we are doing load testing we are unable to saturate the CPU.
    When we run the load test our execution queue rapidly increases to 50 or
    60 and the response time gradually increases. Everything works fairly
    well when we test with 10 to 20 users. Any more than that our
    application becomes useless. Everything slows to almost a halt. If
    someone could tell me what an optimal setup would be for WLS in a single
    server environment is, that would be great. I've done everything by the
    book. I just want to hear it from someone with more experience. I'm
    hoping it's not the application that is doing this.
    thanks

  • Compatibility between Weblogic 8.1 and Broad Vision 7.0

    Can someone throw some lights on the issues and risks involved in Weblogic server 8.1 sp 4 running in Suse Linux 9.0 platform working with Broad Vision 7.0 running in Solaris platform. Would appreciate if you can post some links regarding this topic.

    Hi,
    the following links can help to you
    http://e-docs.bea.com/wls/docs81/notes/resolved_sp04.html
    http://e-docs.bea.com/wls/docs81/notes/issues.html#1293641
    Regards,
    Prasanna Yalam

  • Deprecation of time services

    Hi all,
    in WebLogic 6.1 time services are deprecated
    (http://e-docs.bea.com/wls/docs61/notes/issues.html#1031137). Own
    threads are not allowed by the specification. How can I correctly
    schedule items in WebLogic 6.1? Ideas?
    Thanks,
    Daniel

    I don't know what BEA's opinion is on the use of the standard JMX
    timer service (javax.management.timer) in WLS 6.1, but these
    interfaces are very nice to use, and they appear to function
    well.
    Perhaps one of the BEA folks might want to comment on this approach.
    Ben
    On Mon, 30 Jul 2001 13:08:26 -0700, Michael Girdley <----> wrote:
    You can still use 6.1 Time. It's only for client side. This will be fixed
    in the final docs.
    MG
    Michael Girdley
    BEA Systems
    Learning WebLogic? http://learnweblogic.com
    "Daniel Hoppe" <[email protected]> wrote in message
    news:[email protected]..
    Hi all,
    in WebLogic 6.1 time services are deprecated
    (http://e-docs.bea.com/wls/docs61/notes/issues.html#1031137). Own
    threads are not allowed by the specification. How can I correctly
    schedule items in WebLogic 6.1? Ideas?
    Thanks,
    Daniel

  • WL 7.0 jCom Compling

    Hello,
    I stubbed out my COM dll fine. But when I went to compile the .java files, it could
    not find the com.bea.jcom.Dispatch class. This class was not in weblogic.jar.
    Anybody know where it is?
    TIA,
    Jeff

    There are a whole bunch of objects besides the documented Dispatch that are missing
    from weblogic jar. I changed the locations to com.linar.jintegra and finally got
    it to compile, but could not make any invocations because I got Jintegra licensing
    error messages.
    My attempts to go in the COM-WLS direction have been equally unsuccessful. Using
    a late-bound client, binding with the jndi moniker does not seem to work. Also,
    attempting to obtain a jvm moniker results in the following error:
    U:\>java com.bea.jcom.GetJvmMoniker localhost 7001
    J-Integra 1.5.0 SB004 Copyright (C) 1999-2001 Intrinsyc Software Inc. http://www
    .intrinsyc.com/j-integra/
    java.lang.RuntimeException: No valid licensing information found.
    In order to use the J-Integra runtime a proper license file must be installed.
    If you have acquired a license, or if you are evaluating J-Integra or any
    J-Integra Integra products, then you should have received such a license file, t
    ogether
    with installation instructions by email when you downloaded the kit.
    If you are having trouble installing the license, please goto http://www.intrins
    yc.com
    or refer to your documetation in the section about Licensing
    Help!!
    "lars" <[email protected]> wrote:
    >
    To make the picture complete the typelibrary I used is based on a C# component.
    "lars" <[email protected]> wrote:
    I changed my code according to what you wrote but I still get compilererrors
    for
    "_Object" and "_ProxyObject" which can't be located.
    Is there a working example for communication from Java to Com?
    dan seeman <[email protected]> wrote:
    FYI - you'll find an equivalent issue documented in
    http://e-docs.bea.com/wls/docs70/notes/issues.html#1071850.
    dan
    dan seeman wrote:
    Hi,
    This is a known issue. The Dispatch class is located in com.linar.jintegra.Dispatch.
    For now you'll have to hand-edit your generated classes to import andreference this
    class location. If you have more than a few generated classes, a quickscript (perl,
    python, sed, awk) is probably best suited to this task.
    We apologize for the mistake. The issue will be resolved in a futurerelease.
    dan
    Jeff Blumenthal wrote:
    Hello,
    I stubbed out my COM dll fine. But when I went to compile the .java
    files, it could
    not find the com.bea.jcom.Dispatch class. This class was not in weblogic.jar.
    Anybody know where it is?
    TIA,
    Jeff

  • MappedSuperClass problem on Weblogic 12c

    Hello.
    I'm trying to use @MappedSuperClass in myApp.
    When I deploy my app to weblogic 12c, it gives me following error.
    in my experience it occures error when i write Country.class in the code.
    *[HTTP:101216]Servlet: "TestSuperService" failed to preload on startup in Web application: "MyApp". java.lang.NoSuchMethodError: data.GeneralEntity.pcGetManagedFieldCount()I at myApp.entity.Country.<clinit>(Country.java) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.eclipse.persistence.internal.security.PrivilegedAccessHelper.getClassForName(PrivilegedAccessHelper.java:119) at org.eclipse.persistence.mappings.foundation.AbstractCompositeCollectionMapping.convertClassNamesToClasses(AbstractCompositeCollectionMapping.java:352) at org.eclipse.persistence.descriptors.ClassDescriptor.convertClassNamesToClasses(ClassDescriptor.java:1534) at org.eclipse.persistence.sessions.Project.convertClassNamesToClasses(Project.java:432) at*
    Here is GeneralEntity class in data project :
    *@MappedSuperclass*
    *public abstract class GeneralEntity implements Serializable  {*
    *@Id*
    private BigDecimal pkId;
    *@Column*
    private String Id;
    *public void setPkId(BigDecimal pkId) {*
    this.pkId = pkId;
    *public BigDecimal getPkId() {*
    return pkId;
    *public void setId(String Id) {*
    this.Id = Id;
    *public String getId() {*
    return Id;
    Here is Country class in myApp.entity project :
    *@Entity*
    *public class Country extends GeneralEntity{*
    *public Country() {*       
    *@Column*
    private String region;
    *public void setRegion(String region) {*
    this.region = region;
    *public String getRegion() {*
    return region;
    Please everyone help me to solve this problem
    thanks
    Edited by: 896641 on Jan 2, 2012 12:20 PM

    There isn't much to go on. My first guess was that Country.class is in code that is run before the persistence unit is deployed causing a classloader issue. Googling the error brings up CR370788
    in : http://docs.oracle.com/cd/E15051_01/wls/docs103/pdf/issues.pdf
    which suggests this can occur in a particular situation that seems related - the modules you are using will need to be reordered.
    You can also try using static weaving as a workaround if the above does not work, described here:
    http://wiki.eclipse.org/Using_EclipseLink_JPA_Extensions_(ELUG)#How_to_Configure_Static_Weaving_for_JPA_Entities
    weaving is described here:
    http://wiki.eclipse.org/Using_EclipseLink_JPA_Extensions_(ELUG)#Using_EclipseLink_JPA_Weaving
    Static weaving may not work though as the pcGetManagedFieldCount method is not added by EclipseLink weaving anyway. If neither work, please post the application structure and the persistence.xml being used.
    Best Regards,
    Chris

  • SOA Suite 11g Admin console EM link

    I have installed SOA suite 11g onto a windows XP machine with a local loop back network adaptor. When I go to the WebLogic Server Administration Console home page the link for the Oracle Enterprise Manager is picking up the loop back network adaptors IP address (10.10.10.10). This results in the link not working when accessed over the network. I can replace the local IP address with the machine name or DHCP IP address within the browser to work round the issue. However, is there any way to correct this and re-configure the link to use the actual IP address like the other links?
    Regards
    Neil

    Another way is to get rid of the Loopback Adapter (ie unconfigure it) and just install it. WLS has no issues with DHCP environments.
    --olaf                                                                                                                                                                                                                                                                                           

Maybe you are looking for

  • Z77A-GD65 Multiple BIOS Issues - B4 Hang, Splash Screen Blinking

    Back in November 2012, I built a home server with a Z77A-GD65.  Lately, I've noticed some strange things happening that I've been trying to research but to no avail. First off, I get the B4 code hang-up whenever I'm booting.  This doesn't matter if i

  • Parent - Child Table Insert Trigger

    Hello, I need some help with an Insert Trigger. I want to Insert some field data from 'Table A' to 'Table B' based on a PK and FK. Does anyone have any sample code? <code> Table A SEQ_NO --PK FIELD A FIELD B FIELD C Table B FK_SEQ_NO FIELD B FIELD C

  • PDF save options missing

    I installed Visio 2010, activated it and it worked... it saved PDFs as expected and allowed us to select a page range to export as PDF. Then one day, it gave us a warning that we needed to activate. Oh well, I thought, and entered the activation info

  • Windows 7 64Bit - iPhone 3GS Driver needs constant reinstalling for photos

    This is a fairly fresh installation of windows 7 64bit, I can sync my iphone and apps and music work without issue, but the driver that lets me access the photos has recently started showing an "!" every time I connect, I can only access my photos by

  • Soundbooth CS4 released!

    Hi everyone, I wanted to let everyone know that Soundbooth CS4 has been released! We're very proud of the improvements and new features that have gone into this release, and want to thank our pre-release testers and public beta users who offered advi