Bug in WLS 8.1

Hi,
I enable JCOM in WLS 8.1.2 and once awhile I would see the following error message
throw by WLS Server. I assuming it's a bug within weblogic.
<May 4, 2004 8:49:31 AM CDT> <Error> <Kernel> <BEA-000802> <ExecuteRequest faile
d
java.lang.NullPointerException.
java.lang.NullPointerException
at java.util.Hashtable.get(Ljava.lang.Object;)Ljava.lang.Object;(Optimiz
ed Method)
at weblogic.com.COMService.getSubjectFromCache(Ljava.lang.Object;)Lweblo
gic.security.acl.internal.AuthenticatedSubject;(COMService.java:133)
at weblogic.com.COMExecuteRequest.execute(Lweblogic.kernel.ExecuteThread
;)V(COMExecuteRequest.java:67)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest
;)V(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Sourc
e)
>

Hello,
In general, JNDI clients should assume the correct environment is already configured so there is no need to explicitly set property values and pass them to the InitialContext constructor. However, a JNDI client may need to access a name space other than the one identified in its environment. In this case, it is necessary to explicitly set the java.naming.provider.url (provider URL) property used by the InitialContext constructor. A provider URL contains bootstrap server information that the initial context factory can use to obtain an initial context. Any property values passed in directly to the InitialContext constructor take precedence over settings of those same properties found elsewhere in the environment.
Context.PROVIDER_URL— specifies the URL of the WebLogic Server that provides the name service. The default is t3://localhost:7001. So that you are getting the following result:
ProviderURL=t3://localhost:7001
Regards,
Kuldeep Singh.

Similar Messages

  • Bug in WLS 9.1 clustering?

    I am in the process of testing WLS 9.1, and I'm seeing some strange behavior in a clustered environment. Since we are only in development, I've been performing in-place redeployments for the various EARs that we're testing. Sometimes this works fine, but other times it appears to corrupt the deployment on one of the managed servers. If I look at the server logs I can see that the applications are being redeployed on both managed servers, but when I look at the actual application logs it appears that the MDBs on one of the servers are not getting destroyed and recreated properly. As a result, when we attempt to perform some processing and a JMS message happens to go to the "corrupted" server, strange "NoClassDefFoundError" exceptions and other errors are thrown. However, the EAR seems to work properly on the other managed server as well as on my local machine so I know that there is no problem with it. This only happens sporadically; I cannot recreate it "on demand". Is this a bug? (By the way, we had no trouble running our cluster in WLS 9.0 so I assume that the cluster configuration is not the problem.)
              Regards,
              Sabrina

    I have a similar problem with WLS 9.1. When I deploy an ear file, i can see the login page, but, when I login it throws an error saying "internal server error". When I check my stage folder, entire ear file is copied there, its not expanded. I dont have any problem with 9.0. Is this a bug in 9.1?
              when i deploy a .war file it says "Cannot set web app root system property when WAR file is not expanded". but, when i expand it and deploy, it works fine.
              I have already opened a case on this. I did not get any response from BEA. Its urgent for us. Did anyone of you solve this issue. If yes, please let me know the resolution.
              I really appreciate any help on this.
              Thanks a bunch
              Sarat

  • Bug in WLS 6.1 DataSource + Oracle Pool

    Does any one has arrived to execute an Oracle Stored procedure which
    return a CURSOR in response with JDBC through the DataSource?
    It's working perfectly with WLS 5.1sp9 to 6.0sp2
    and NOT with the 6.1 (even sp1) ...
    Exception : weblogic.jdbc.rmi.internal.ResultSetImpl
    Any idea ?
    Best regards.

    Does any one has arrived to execute an Oracle Stored procedure which
    return a CURSOR in response with JDBC through the DataSource?
    It's working perfectly with WLS 5.1sp9 to 6.0sp2
    and NOT with the 6.1 (even sp1) ...
    Exception : weblogic.jdbc.rmi.internal.ResultSetImpl
    Any idea ?
    Best regards.

  • How do i make wls 9.2 stop shutting itself down within eclipse 3.2.2?

    after starting weblogic server 9.2 mp1 from within eclipse
    sdk 3.2.2 build M20070212-1330 for solaris gtk, something
    programatically requests weblogic server 9.2 to shut
    itself down only seconds after the server has started.
    steps to reproduce:
    1. download & install [url http://download.eclipse.org/eclipse/downloads/drops/R-3.2.2-200702121330/]eclipse sdk 3.2.2 build M20070212-1330 for solaris
    (eclipse-SDK-3.2.2-solaris-gtk.zip)
    2. update eclipse sdk with the [url http://download.eclipse.org/webtools/downloads/drops/R1.5/R-1.5.3-200702082048/]Web Tools Platform (WTP)
    1.5.3 plus all of the WTP 1.5.3 pre-reqs
    3. download & install [url http://commerce.bea.com/showallversions.jsp?family=WLS]bea weblogic server 9.2 mp1 binary
    package installer for solaris 9 sparc
    4. confirm that bea weblogic server's sample domain can
    be started from the solaris 9's shell
    $ $BEA_HOME/weblogic92/samples/domains/workshop/startWebLogic.sh
    5. create a j2ee enterprise application by following the
    instructions in [url http://www.eclipse.org/webtools/community/tutorials/BuildJ2EEWebApp/BuildJ2EEWebApp.html]this WTP tutorial
    a. in the "Choose a Server Runtime Environment" step,
    choose BEA WebLogic 9.2 server instead of Tomcat.
    6. start the generic bea weblogic server v9.2.1 from the
    servers view as instructed in the tutorial.
    the eclipse status bar in the bottom right hand corner of
    eclipse indicates that weblogic server 9.2 is starting.
    eclipse then switches focus from the servers view to the
    console view. the console view lists the typical weblogic
    server startup console entries:
    ...<Server state changed to STANDBY>
    ...<Server state changed to STARTING>
    ...<No test table set up for pool "cgDataSource". Connections will not be
    tested.>
    ...<No test table set up for pool "cgDataSource-nonXA". Connections will not be
    tested.>
    ...<No test table set up for pool "samplesDataSource". Connections will not be
    tested.>
    ...[see 13_05_07_eclipse_wls_startup.txt in [url https://bugs.eclipse.org/bugs/attachment.cgi?id=66989]comment #1 attachment of [url https://bugs.eclipse.org/bugs/show_bug.cgi?id=186716]eclipse bug #186716  for full
    console output]
    eventually - but only for a few seconds - the servers view indicates the state
    of the weblogic server as "Started". the following log entries snipped from
    weblogic server 9.2's filesystem logs confirm that the wls did actually start
    at some point:
    ...<Server state changed to RUNNING>
    ...<Server started in RUNNING mode>
    ...<78% of the total memory in the server is free>
    ...[see cgServer.log in  [url https://bugs.eclipse.org/bugs/attachment.cgi?id=66989]comment #1 attachment of [url https://bugs.eclipse.org/bugs/show_bug.cgi?id=186716]eclipse bug #186716  for full log output]
    then eclipse automatically switches focus to the console view again; displaying
    the following:
    $BEA_HOME/weblogic92/samples/domains/workshop/bin/stopWebLogic.sh: 
    Stopping Weblogic Server...
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    Connecting to t3://localhost:7001 with userid weblogic ...
    This Exception occured at Sun May 13 12:35:42 BST 2007.
    javax.naming.CommunicationException [Root exception is
    java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested
    exception is:
            java.net.ConnectException: Connection refused; No available router to
    destination]
    ...[see 13_05_07_eclipse_wls_shutdown.txt in [url https://bugs.eclipse.org/bugs/attachment.cgi?id=66989]comment #1 attachment of [url https://bugs.eclipse.org/bugs/show_bug.cgi?id=186716]eclipse bug #186716  for full
    stack trace]
    the servers view eventually indicates the server has transitioned to the
    "Stopped" state. the problem is, i never commanded neither eclipse or wls to
    shutdown the wls server.
    since the wls server can be successfully started outside of eclipse from the
    shell, and since - once it is successfully started outside of eclipse - wls
    doesn't automatically shutdown as soon as it starts; i suspect there is
    something in eclipse|wtp that is triggering the automatic
    shutdown. but of course, i could be wrong. maybe something
    in wls itself is at fault.
    i encountered this exact same bug in wls 9.0 with eclipse 3.2.2/wtp 1.5.3 on
    solaris 9 sparc (which is what prompted me to upgrade to wls 9.2 on solaris 9
    sparc; see [url https://bugs.eclipse.org/bugs/show_bug.cgi?id=169197]eclipse bug #169197); and i encounter this exact same bug with wls 9.2 with
    eclipse 3.2.2/wtp 1.5.3 in mac os x 10.4.9! there is a
    slight difference in what happens in solaris vs what happens on the mac. on the mac, the exception appears to
    be thrown at a different point (when a wldeploy.xml script
    is executed; not at the point of "Initializing WebLogic
    Scripting Tool (WLST)" like in the solaris installation):
    Buildfile: /Applications/eclipse/plugins/org.eclipse.jst.server.generic.weblogic_1.5.1.v200609141504/buildfiles/wldeploy.xml
    init:
    deploy:
         [echo] Deploying module WTP_WebApp_Tutorial
    [wldeploy] weblogic.Deployer -debug -verbose -noexit -name WTP_WebApp_Tutorial -source /Users/bilbo/development/projects/eclipse_3.2.2_tutorial/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/WTP_WebApp_Tutorial -adminurl t3://localhost:7001 -user weblogic -password ******** -deploy
    [wldeploy] weblogic.Deployer invoked with options:  -debug -verbose -noexit -name WTP_WebApp_Tutorial -source /Users/bilbo/development/projects/eclipse_3.2.2_tutorial/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/WTP_WebApp_Tutorial -adminurl t3://localhost:7001 -user weblogic -deploy
    [wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at localhost:7001, as user weblogic
    [wldeploy] [ServerConnectionImpl.getEnvironment():288] : setting environment
    [wldeploy] [ServerConnectionImpl.getEnvironment():291] : getting context using t3://localhost:7001
    [wldeploy] [ServerConnectionImpl.close():334] : Closing DM connection
    [wldeploy] [ServerConnectionImpl.close():354] : Unregistered all listeners
    [wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://localhost:7001': Destination unreachable; nested exception is:
    [wldeploy] java.net.ConnectException: Connection refused; No available router to destination. Ensure the url represents a running admin
    ... also, on the mac the cgServer.log has the following additional log entries:
    ...<Graceful shutdown of cgServer was issued remotely from 10.0.0.9>
    ...<Server shutdown has been requested by weblogic>
    ...<Server state changed to SUSPENDING>
    ... <Server state changed to ADMIN>
    ...<Server state changed to SHUTTING_DOWN>
    ...<Channel "Default[2]" listening on 127.0.0.1:7001 was shutdown.>
    ...in all cases, i have done nothing
    more and nothing less than what the eclipse/wtp and weblogic documentation has
    instructed me to do.
    please, can anybody suggest a fix or a workaround. thanks in advance.
    Edited by wboyd at 05/13/2007 7:48 AM

    thanks rob,
    please, can you clarify what bearing the global system properties mentioned in CR299479 at the bottom of [url http://e-docs.bea.com/workshop/docs92/relnotes/relnotes.html#wp1139954]this page of 9.2.1 release notes have on the timeout value discussed in [url https://bugs.eclipse.org/bugs/show_bug.cgi?id=186902]this eclipse wtp bug report?
    many thanks,
    wboyd

  • WLS 8.1 sp1 with Struts 1.1 JSP with bean tag won't compile

              Hello,
              We are currently porting our application which uses struts 1.1 to WLS 8.1 sp1
              from another app server. Everything seems to deploy correctly and pages which
              use struts tags appear to compile and run fine. However, the pages with struts
              <bean:define> tags are not compiling.
              Example JSP Code:
              <bean:define id="userForm" name="userForm" scope="session" toScope="page" type="UserFormBean"/>
              <% if (userForm.hasUserData()) {hasUser=true;} %>
              WLS Console Output:
              ..jsp_servlet\_jsp\_sailor\__home.java:493: cannot resolve symbol
              symbol : variable userForm
              location: class jsp_servlet._jsp._sailor.__home
              if (userForm.hasUserData()) { //[ /jsp/sailor/home.jsp; Line: 38]
              When I look at the JSP's parsed java code (__home.java:493) I find that nowhere
              in the class is the variable userForm declared.
              Is this a bug in WLS? Does anyone know of a workaround?
              Thanks,
              Scott
              

    Please contact customer support [email protected] and request a patch for
              CR112789. AT_END tags do not work correctly in 81sp1
              --Nagesh
              "Scott Fleming" <[email protected]> wrote in message
              news:3f734c0d$[email protected]..
              >
              > Hello,
              >
              > We are currently porting our application which uses struts 1.1 to WLS 8.1
              sp1
              > from another app server. Everything seems to deploy correctly and pages
              which
              > use struts tags appear to compile and run fine. However, the pages with
              struts
              > <bean:define> tags are not compiling.
              >
              > Example JSP Code:
              >
              > <bean:define id="userForm" name="userForm" scope="session" toScope="page"
              type="UserFormBean"/>
              >
              > <% if (userForm.hasUserData()) {hasUser=true;} %>
              >
              > WLS Console Output:
              >
              > ..jsp_servlet\_jsp\_sailor\__home.java:493: cannot resolve symbol
              > symbol : variable userForm
              > location: class jsp_servlet._jsp._sailor.__home
              > if (userForm.hasUserData()) { //[ /jsp/sailor/home.jsp; Line:
              38]
              >
              > When I look at the JSP's parsed java code (__home.java:493) I find that
              nowhere
              > in the class is the variable userForm declared.
              >
              > Is this a bug in WLS? Does anyone know of a workaround?
              >
              > Thanks,
              > Scott
              

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

  • Error in body tag handling in WLS 7.0

              Hi,
              I've tried to port an Web Application to WLS 7.0. This app was originally developed
              under 5.1, and was later on ported to WLS 6.1. In all WLS versions the behaviour
              of our custom tags seems to be equal. But on WLS 7.0 I've found out, that tags, implemented
              as body tags (in my special case the bodycontent was declared as "tagdependent")
              are completely ignored when no body is given. For example if the tag is used in an
              JSP like
              <prefix:mytag>
              </prefix:mytag>
              the tag works. If the tag is used like
              <prefix:mytag/>
              It is completely ignored. The resulting HTML page still contains <prefix:mytag/>.
              Because the behaviour was different in releases pre 7.0 i assume this is a new bug
              in WLS 7.0.
              Regards,
              Christian
              

              I've found out, that BodyTags which are declared as "tagdependent" in the tld file
              are completely ignored if no body is given. You can see this if you take a look at
              the generated servlet class.
              BodyTags which are declared as "JSP" do work with empty body.
              Regards,
              Christian
              "Christian Lauer" <[email protected]> wrote:
              >
              >Hi,
              >
              >I've tried to port an Web Application to WLS 7.0. This app was originally
              >developed
              >under 5.1, and was later on ported to WLS 6.1. In all WLS versions the behaviour
              >of our custom tags seems to be equal. But on WLS 7.0 I've found out, that
              >tags, implemented
              >as body tags (in my special case the bodycontent was declared as "tagdependent")
              >are completely ignored when no body is given. For example if the tag is
              >used in an
              >JSP like
              >
              > <prefix:mytag>
              > ...
              > </prefix:mytag>
              >
              >the tag works. If the tag is used like
              >
              > <prefix:mytag/>
              >
              >It is completely ignored. The resulting HTML page still contains <prefix:mytag/>.
              >
              >Because the behaviour was different in releases pre 7.0 i assume this is
              >a new bug
              >in WLS 7.0.
              >
              >Regards,
              >Christian
              

  • BasicRealm getUser() bug in WL5.1?

    Hi,
    I am facing a weird problem with authentication using a custom realm in WLS5.1.
    I have written a custom security realm which implements the BasicRealm and ListableRealm
    interfaces (the realm it does not extend Weblogic's AbstractListableRealm).
    I have my own implementation of the User object within my realm package (call
    it MyUser),
    which extends weblogic's User object and provides the following behavior: MyUser
    instances
    contain a ticket if they have been successfully authenticated. This ticket is
    available
    through MyUser.getCredential() method.
    Now, to the problem: Weblogic stores the wrong User object in the thread after
    authentication.
    The realm authentication sequence goes as follows:
    1. WLS calls the BasicRealm.getUser(String userName) method on my realm.
    2. The realm returns a MyUser object with a null ticket (since the user hasn't
    been
    authenticated). Let's call this user object myuser1.
    3. WLS then calls the BasicRealm.getUser(UserInfo userInfo) method on my realm.
    4. The realm authenticates the credentials and returns another MyUser object,
    this one
    with a valid ticket. Call this myuser2.
    The problem is, WLS seems to discard myuser2, and store myuser1 in the thread-specific
    authentication context. So, when an EJB method executing within that thread calls
    Security.getCurrentUser(), it gets back myuser1. Since myuser1.getCredential()
    returns null,
    the EJB is not able to fetch the authentication ticket.
    Is this a bug in WLS? If so, is there a patch available? Failing that, is there
    any way to
    make WLS store the second user object?
    Thanks
    Ravi

    Hi,
    I think your problem is that your first returned user object ( MyUser ) is stored
    in a caching realm, and it is this user that is returned when using Security.getCurrentUser().
    Instead of creating av new user object when authenticating ( authUserPassword
    ), just modify the user object already stored in the cache realm.
    The code for getting the user object from the cache could look something like
    this:
    User user = null;
    BasicRealm basicRealm = Security.getRealm();
    if (basicRealm != null && basicRealm instanceof CachingRealm)
    CachingRealm cachingRealm = (CachingRealm)basicRealm;
    if (cachingRealm != null)
    user = cachingRealm.getUser(name);
    user.setTicket(ticket);
    Now you can set your ticket attribute on this object and return it as the user
    object.
    Security.getCurrentUser() should now return a user object with a valid ticket.
    Yngve.
    "Ravi Shankar" <[email protected]> wrote:
    >
    Hi,
    I am facing a weird problem with authentication using a custom realm
    in WLS5.1.
    I have written a custom security realm which implements the BasicRealm
    and ListableRealm
    interfaces (the realm it does not extend Weblogic's AbstractListableRealm).
    I have my own implementation of the User object within my realm package
    (call
    it MyUser),
    which extends weblogic's User object and provides the following behavior:
    MyUser
    instances
    contain a ticket if they have been successfully authenticated. This ticket
    is
    available
    through MyUser.getCredential() method.
    Now, to the problem: Weblogic stores the wrong User object in the thread
    after
    authentication.
    The realm authentication sequence goes as follows:
    1. WLS calls the BasicRealm.getUser(String userName) method on my realm.
    2. The realm returns a MyUser object with a null ticket (since the user
    hasn't
    been
    authenticated). Let's call this user object myuser1.
    3. WLS then calls the BasicRealm.getUser(UserInfo userInfo) method on
    my realm.
    4. The realm authenticates the credentials and returns another MyUser
    object,
    this one
    with a valid ticket. Call this myuser2.
    The problem is, WLS seems to discard myuser2, and store myuser1 in the
    thread-specific
    authentication context. So, when an EJB method executing within that
    thread calls
    Security.getCurrentUser(), it gets back myuser1. Since myuser1.getCredential()
    returns null,
    the EJB is not able to fetch the authentication ticket.
    Is this a bug in WLS? If so, is there a patch available? Failing that,
    is there
    any way to
    make WLS store the second user object?
    Thanks
    Ravi

  • AccessControlException WLS 6.1 and RMI

    I have just upgraded to WLS 6.1 and an existing RMI application runs fine.
    I then converted it from using the WebLogic RMI classes to the standard Sun ones,
    as recommended at a recent course at BEA, and as per the 6.1 documentation. Now
    my RMI Server, which is in the &#8220;Startup Application&#8221; for WLS gives
    an &#8220;AccessControlException&#8221; access denied in the server console.
    I aware that &#8220;rmid&#8221; now requires a security policy file and I added
    what I thought was the correct line, after looking Esmond Pitt&#8217;s excellent
    &#8220;The RMI Guide&#8221; to the java.policy file.
    Scouring the newsgroups I saw a reference to this being a bug in WLS 6.1 Can any
    confirm this or suggest where I might be going wrong.
    Regards,
    Roger Lee, NOTiFY. UK

    Problem with weblogic.policy file.
    "Roger Lee" <[email protected]> wrote:
    >
    I have just upgraded to WLS 6.1 and an existing RMI application runs
    fine.
    I then converted it from using the WebLogic RMI classes to the standard
    Sun ones,
    as recommended at a recent course at BEA, and as per the 6.1 documentation.
    Now
    my RMI Server, which is in the &#8220;Startup Application&#8221; for
    WLS gives
    an &#8220;AccessControlException&#8221; access denied in the server console.
    I aware that &#8220;rmid&#8221; now requires a security policy file and
    I added
    what I thought was the correct line, after looking Esmond Pitt&#8217;s
    excellent
    &#8220;The RMI Guide&#8221; to the java.policy file.
    Scouring the newsgroups I saw a reference to this being a bug in WLS
    6.1 Can any
    confirm this or suggest where I might be going wrong.
    Regards,
    Roger Lee, NOTiFY. UK

  • EJB 3.0 Dependency Injection and reentrant Calls on SFSB

    Hi there
    I have a SFSB (Bean A) that injects another SFSB (Bean B) with the @EJB annotation. Now Bean A does reentrant-calls on Bean B, which is ok, because it just asks for the current state.
    This results in a "javax.ejb.EJBTransactionRolledbackException: Illegal attempt to make a reentrant call to a stateful session bean from home: .....; nested exception is: javax.ejb.ConcurrentAccessException: Illegal attempt to make a reentrant call to a stateful session bean: ....."
    Now I added a weblogic-ejb-jar.xml with the section:
    <stateful-session-descriptor>
      <allow-concurrent-calls>true</allow-concurrent-calls>
    </stateful-session-descriptor>to enable reentrant calls on my SFSB. Unfortunatly this leads to problems with the DI, it simply doesnt work anymore!!! The message now is " java.lang.IllegalStateException: Cannot find object BeanBInterface with java:comp/env/ejb/BeanBInterface". Obviously the DI didn't work, the local variable isn't filled anmyore.
    Is this a bug of WLS 10.0 MP1 or a feature? Should I open a bug report? Any tips a welcome!
    Stephan

    There is currently no possiblity in Weblogic 10 server web layer to use Dependency Injection on any other component than the ones defined in web.xml s.a.:
    - servlets
    - listeners
    - filters
    See here:
    http://e-docs.bea.com/wls/docs100/webapp/annotateservlet.html
    A simple POJO class part of the web application (such as a Backing Bean in JSF or an Action in Struts for example) is not benefiting from DI.
    Doesn't this make Weblogic 10 a NON JEE 5 compliant server?
    Why was this restriction imposed?
    And how is one supposed to use DI with a simple POJO class? Why this huge inconvenience?

  • Re: Describe input xml

    Anamitra,
    I didn't get a chance to work on this issue.
    From my understanding I have quickly created a test wsdl and test xsd.
    I don't know whether it will work. I have not tested it. It needs many
    corrections.
    Take a look at the attached wsdl and xsd and let me know your suggestion.
    Scenario:
    1. Exposed method:
    public String requestPurchaseOrder(String poXML)
    2. poXML should be of type po.xsd
    3. Validation - ?? No Idea. For now manual validation.
    I guess we both have similar requirement, if you get it working before me,
    please post your finding.
    Thanks,
    Karthik.
    "Anamitra" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hi karthik
    I still dont get how the poXML can be represented by a schema in a WSDL.Can you
    give me a sample wsdl for that?
    Thanks
    Anamitra
    "Karthik V" <[email protected]> wrote:
    Manoj:
    Sorry, I got confused when you said, "the runtime will strip the xml
    tags".
    After your explanation, I understand that the runtime is actually going
    to
    perform some conversion without any loss of data.
    To conclude, logically,
    public void test(String poXML) is valid, and poXML can be represented
    by
    a schema definition.
    When I get a chance, I'm going to create a quick example of this use
    case
    and post it.
    Thanks,
    /k
    "manoj cheenath" <[email protected]> wrote in message
    news:[email protected]...
    java.lang.String is mapped to xsd:string which means the xml
    should look like:
    <foo xsi:type=xsd:string >sometext without any xml tags</foo>
    So if there are xml tags inside the string you passed
    in, runtime need to replace the tags with > and
    <.
    On the other end the runtime will again replace
    etc back to < or >. So you will get back theright XML. But on the wire it will be plain text
    not XML.
    So, if you dont want to convert to string, then you should use
    javax.xml.soap.SOAPElement or org.w3c.Element as
    your parameter type instead of java.lang.String.
    http://manojc.com
    "Karthik V" <[email protected]> wrote in message
    news:[email protected]...
    Manoj:
    I do not understand how the runtime will strip the xml.
    I think Anamitra's requirement of:
    public void test(String poXML)
    is very valid and a simple requirement.
    Infact, my requirement too is similar..
    1. Expose a method which takes in a String object.
    2. Define how the String is going to look like (using xsd).
    3. Instead of defining the schema in WSDL, we would like to import
    the
    schema and use it.
    4. Later use the schema to validate the incoming request.
    In real time most of us would like to work with String because ofits
    simplicity.
    Is there any reason why the implementation for such a simple usecase is
    so
    confusing?
    /k
    "manoj cheenath" <[email protected]> wrote in message
    news:[email protected]...
    public void test( String poXML )
    is not the best solution for you, i think, because
    in this case the runtime will strip the xml tags
    inside poXML. so the envelope will look like:
    <m:my-method>
    <poXML>sdfjds >some thing < something else...</poXML>
    </m:my-method>
    instead of:
    <m:my-method>
    <poXML>some thing <foo> something else</foo></poXML>
    </m:my-method>
    Will that be ok for you? Else, you can use DOM or
    javax.xml.soap.SOAPElement:
    public void test( org.w3c.Dom poXML );
    It looks like there is bug in WLS 7.0.2. The CR for this
    is CR104719. Please contact support if you need a patch.
    If you do clientgen on the WSDL, it is going to generate
    the classes (value types) for you. It looks like you do not
    want to do data binding. Take a look at DII client with generic
    type-mapping. Will this help you?
    package examples.jaxrpc.call5;
    import java.net.URL;
    import javax.xml.soap.SOAPConstants;
    import javax.xml.rpc.ServiceFactory;
    import javax.xml.rpc.Service;
    import javax.xml.rpc.Call;
    import javax.xml.rpc.ParameterMode;
    import javax.xml.namespace.QName;
    import javax.xml.rpc.encoding.TypeMapping;
    import javax.xml.rpc.encoding.TypeMappingRegistry;
    import javax.xml.soap.SOAPElement;
    import weblogic.webservice.encoding.GenericTypeMapping;
    import weblogic.webservice.core.soap.SOAPElementImpl;
    public class MSInterop{
    public static void main( String[] args ) throws Exception{
    //dont parse wsdl till we set the typemapping
    System.setProperty( "weblogic.webservice.servicenamechecking",
    "false" );
    //create service factory
    ServiceFactory factory = ServiceFactory.newInstance();
    //define qnames
    String targetNamespace = "http://soapinterop.org/";
    QName serviceName = new QName( targetNamespace, "SimpleTest"
    QName portName = new QName( targetNamespace, "SimpleTestSoap");
    QName operationName = new QName( "http://soapinterop.org/",
    "echoStruct" );
    URL wsdlLocation = new URL(
    "http://www.mssoapinterop.org/asmx/simple.asmx?WSDL" );
    //create service
    Service service = factory.createService( wsdlLocation,serviceName );
    TypeMappingRegistry registry =
    service.getTypeMappingRegistry();
    >>>>>
    registry.register( SOAPConstants.URI_NS_SOAP_ENCODING,
    new GenericTypeMapping() );
    //create call
    Call call = service.createCall( portName, operationName );
    //construct struct
    SOAPElement elem = new SOAPElementImpl( "inputStruct", null,null );
    elem.addChildElement( "varInt" ).addTextNode( "1" );
    elem.addChildElement( "varString" ).addTextNode( "samplestring" );
    elem.addChildElement( "varFloat" ).addTextNode( "2.2" );
    System.out.println( elem );
    try{
    SOAPElement res = (SOAPElement)call.invoke(new Object[]{elem } );
    System.out.println( res );
    }catch( javax.xml.rpc.JAXRPCException e ){
    e.printStackTrace();
    e.getLinkedCause().printStackTrace();
    Call echoFloat = service.createCall( portName,
    new QName( "http://soapinterop.org/", "echoFloat" ) );
    System.out.println( echoFloat.invoke( new Object[]{new
    Float(100.0)} ) );
    http://manojc.com
    "Anamitra" <[email protected]> wrote in message
    news:[email protected]...
    Hi Bruce
    I think the wsdl that you sent was very near to what I was
    looking
    for.
    But I
    would try to make the requirement more clear: The points below
    are
    listed
    in order
    of priority:
    1>First and foremost I am looking to create a Webservice such
    that
    it
    exposes
    a method which takes in a java.lang.String
    public void test(String poXML)
    But in the WSDL I want to show the user the schema definition
    for
    the
    po
    XML.
    And would desire that the Webservices framework do the schema
    validation
    of the
    incoming xml. But I dont thing this works as the wsdl generated
    always
    says the
    type is "xsd:string". So I started looking into the 2nd option:
    2>Create a doc/literal type service and expose that method as:
    public void test(POXMLBean poXML)
    This generated the reqd schema in the wsdl level but the client
    is
    being
    forced
    to use the POXMLBean to invoke the method. I would ideally want
    the
    client
    to
    just deal with the XML of the pobean as described in the
    generated
    schema
    definition.
    For example the client using JAXRPC should be say doing the code
    like
    this:
    String poXML = "<po> <order>000</order> </po>"
    call.invoke(poXML").
    Is this possible? I am not able to do this. My primary important
    thing
    is
    that
    the client has to deal with XML and not with anything else. The
    client
    shouldnot
    have to deal with POXMLBean. This is what I am trying to acheive
    and
    not
    able
    to.
    3> So that leaves me to the last option which is not that good:
    ie I keep my original approach:
    public void test(String poXML)
    and somehow via wsdl:documentation say that the schema for this
    poXML
    is
    this...
    But I cannot change the type in the parameter poXML from
    xs:string
    right?
    Bottom line is there any way for the client to pass string/byte[]
    xml
    data
    to
    the webservice - but still be able to look into the WSDL and
    see
    what
    the
    reqd
    XML structure should be? I thought doc/literal should do it -
    but
    using
    weblogic
    I am not able to do it. Can u help me with this pls.
    thanks
    Anamitra
    Bruce Stephens <[email protected]> wrote:
    Hello,
    See what you think of this example of using import. It seems
    to
    describe your exact use case:
    http://www.ws-i.org/SampleApplications/SupplyChainManagement/2002-08/Retai
    l
    er.wsdl
    (Disclaimer, anyone could have found this via public UDDI.)
    The issue I believe that Anamitra sees is the gap between the
    runtime
    and the toolset.
    Bruce
    Anamitra wrote:
    Hi Karthik
    I am a bit confused as to what you mean when u say "import".
    The
    generated
    webservices.xml
    contains a <types> and a <type-mapping> element. I suppose
    u r
    asking
    me to put
    the xsd definition in the <types> section - right?
    If the method is like this:
    public String doit(String msg)
    How do I attach the <xs:string> type "msg" to the actual
    XML
    schema
    that I just
    imported?
    I dont know whether I am asking stupid questions or not -
    but I
    would
    have ideall
    liked to see my "msg" of type say "PurchaseOrder" which is
    the
    schema
    that I imported.
    And the external client should just be able to give the
    "PurchaseOrder"
    xml to
    the Webservice and invoke the "doit" method.
    Am I making any sense?
    thanks
    Anamitra
    "Karthik V" <[email protected]> wrote:
    I doubt if servicegen has any option for doing it
    automatically.
    You should manually edit web-services.xml and import thexsd.
    /k
    "Anamitra" <[email protected]> wrote in message
    news:[email protected]...
    Hi Karthik/Bruce
    Can you pls explain to me how using weblogic tools
    [servicegen]
    one
    can
    include
    the xsd pointers in the WSDL file.
    We have a similar kind of requirement where we have
    webservices
    which
    take
    in
    string [XML data] as a parameter and the WSDL only shows
    method
    parameter
    types
    as xsd:string - but we want to show something like a schema
    definition.
    So
    if
    there is anyway to put the schema definition in the WSDL
    - pls
    let
    me know
    that
    would be very very helpful.
    thanks
    Anamitra
    "Karthik V" <[email protected]> wrote:
    Bruce,
    Thanks for your response. That helped.
    I have another question for you.
    I know this would sound strange.
    But my requirement is to expose a session bean method
    that
    could
    take
    different xml inputs.
    For example:
    TestBean exposes testMethod(String xmlstr)
    xmlstr could be of schema xmlSchema1.xsd
    or xmlstr could be of schema xmlSchema2.xsd
    In future it could also represent xmlSchema3.xsd... and
    so
    on.
    What is the right approach in this scenario?
    I was thinking to create a different web service fordifferent
    xsd.
    Say, webservice1 imports xmlSchema1.xsd, webservice2
    imports
    xmlSchema2.xsd...
    Un fortunately due to some design restrictions, I cannotcreate
    different
    methods in my session bean like testMethod1,
    testMethod2....
    Is there any other better way to do this in one webservice?
    >>>>>>>>>>>
    Thanks in advance for any suggestions. And excuse myunusual
    requirement.
    /k
    "Bruce Stephens" <[email protected]> wrote in message
    news:[email protected]...
    Hello,
    Personally I like to see everything in one place, i.e.
    in
    the
    WSDL,
    however everyone else :-) uses the import. The
    SOAPBuilders
    round
    3
    have several tests showing imports. Also WSI Basic
    profile
    has
    some
    helpful guidelines on using import:
    http://www.ws-i.org/Profiles/Basic/2003-03/BasicProfile-1.0-BdAD.html
    >>>>>>>>>>>>
    HTHs,
    Bruce
    Karthik V wrote:
    Hi,
    I have created few doc style web services, with a
    very
    complex
    xml
    input
    and
    output. (1200 lines of xsd)
    Input and out put are xml as java.lang.String.
    What would be the best practice to represent this
    in the
    WSDL?
    Just
    a
    reference to the xsd file is good, or should it be
    completely
    presented
    within the WSDL? I'm not sure how my wsdl should look
    like...
    I will be using the same schema (xsd) in other web
    services
    too
    to
    perform
    different functions.
    Any suggestions would be greatly appreciated.
    Thanks
    /k
    [testWSDL.wsdl]
    [PO.xsd]

    Hello Karthik/Anamitra,
    i have the same requirements in my webservices:
    1) Expose the Handler method receiving String
    public String runRequest(String poXML)
    2) On the other hand - the message (the poXML string) should be in XML format according to some XSD file.
    Have you got this working already?
    If so, please explain what the WSDL looks like.
    Thanks in advance,
    Orly

  • Weblogic Server 6.1 Service Pack 2

    Hi !
    Is there any major difference between wl6.1 sp1 and wl6.1 sp2 ?
    My applications which otherwise work fine on former, now are not even loading
    at the start of wl 6.1 sp2 . They give a error java.lang.String index out of range
    -1
    Any ideas on what to do next ?
    Thanks
    Lalitha

    hi.
    The only differences between sp1 and sp2 on WLS 6.1 are bug fixes as spelled out
    here: http://edocs.bea.com/wls/docs61/notes/bugfixes2.html#1121521.
    Take a look at the exceptions and corresponding stack traces - are these exceptions
    being thrown by WebLogic code or your own application code? It is possible that a bug
    fix in sp2 exposed a bug in your application, or maybe introduced a new bug in wls.
    Perhaps you can post the exception(s) here if you don't think they are coming from
    your code.
    Regards,
    Michael
    Lalitha wrote:
    Hi !
    Is there any major difference between wl6.1 sp1 and wl6.1 sp2 ?
    My applications which otherwise work fine on former, now are not even loading
    at the start of wl 6.1 sp2 . They give a error java.lang.String index out of range
    -1
    Any ideas on what to do next ?
    Thanks
    Lalitha--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Query Strings in Request Dispatcher Paths (PLT.16.1.1)

    I'm having trouble using query strings in a request dispatcher include to a servlet.
    I'm spitting debug out, and it looks like I'm calling:
    PortletRequestDispatcher rd = getPortletContext().getRequestDispatcher("/myServlet?myparam=myparamValue");
    And myparam isn't being set for myServlet.
    The same URL ("http://myhost:myport/myPortal/myServlet?mayparam=mayparamValue)
    runs fine standalone....

    I'm not sure of the exact dates (either this month or the next). But
    JSR168 will be supported in the service pack.
    Subbu
    T-Bone said the following on 11/18/2003 09:23 AM:
    Subbu Allamaraju <[email protected]> wrote:
    There is a known bug in WLS's servlet container that results in this
    behavior. Please contact support if you need an expedited solution.Thanks, they said to wait for SP2 sometime end of November.
    Can you tell me when it will be available?
    Also, when will JSR-168 v1.0 be supported?
    Subbu
    T-Bone said the following on 10/26/2003 03:14 PM:
    I'm having trouble using query strings in a request dispatcher includeto a servlet.
    I'm spitting debug out, and it looks like I'm calling:
    PortletRequestDispatcher rd = getPortletContext().getRequestDispatcher("/myServlet?myparam=myparamValue");
    And myparam isn't being set for myServlet.
    The same URL ("http://myhost:myport/myPortal/myServlet?mayparam=mayparamValue)
    runs fine standalone....

  • Upgrade 10.3.5.0 -- 10.3.6.0.8?

    I've been applying patches individually as they become available rather than waiting
    for the cumulative patch updates to become available since installing in 2012.
    Hence right now we are at a patched 10.3.5.0.
    For the April release I am told there is a security vulnerability available that isn't
    available as an individual patch.
    Questions:
    Will this Patch Update to 10.3.6.0.8 work without problems for my
    system?
    If not is the problem that I am at 10.3.5.0 or that I did individual patches?
    Also if so, what can I do to most painlessly get this patch applied?
    Thanks in advance to anyone who can help.

    Patch Set Updates (PSUs) are proactive cumulative patches containing recommended bug fixes that are released on a regular and predictable schedule. PSUs are on the same quarterly schedule as the Critical Patch Updates (CPU)
    -You need to first upgrade from WLS 10.3.5 to WLS 10.3.6
    Have a look at the following Note :
    README File Included with WebLogic Server 10.3.x Upgrade Installers: Instructions for Upgrade Installer in Graphical, Console, or Silent Mode (Doc ID 1064633.1)
    To download the upgrade installer for Weblogic 10.3.6 :
    How Can I Download Upgrade Installers for Oracle WebLogic Server (WLS)? (Doc ID 1074946.1)
    To Summarize :
    - First uninstall all the patches applied in WLS 1035
    - Upgrade WLS 1035 to WLS 1036 using an upgrade installer
    - Now apply the PSU 10.3.6.0.8 patch on top of WLS 1036. ( BUG 18040640 ).
    Below are the fixed BUGs in WLS 10.3.6.0.8 :
    New DocumentOracle WebLogic Server Patch Set Update 10.3.6.0.8 Fixed Bugs List (Doc ID 1645823.1)
    If the PSU is missing any patch that you need in your environment then try to find the patch in your support portal and apply it manually.
    -- Puneeth

  • Resource Allocation Issue in Weblogic messaging bridges

    Hi,
    We are using
    Weblogic version à WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 WebLogic Temporary Patch for CR250915 04/18/2006 22:21:33
    Java JDK version à 1.4.2_11
    Oracle version à 9.2.08
    Solaris version à Solaris 5.8
    The weblogic application is deployed on Unix Solaris.
    We have configured 8 message bridges within weblogic between the 8 Topics in weblogic (source JMS destination) and 8 topics in the External EMS server (Target JMS destination) .
    The properties set for the message bridges are
    1] AsyncEnabled ="true"
    2] DurabilityEnabled ="true"
    3] QualityOfService="Exactly-once"TransactionTimeout="10"
    4] TransactionTimeout="10"
    The source and target JMS destinations are bridge using the resource adapter of jms-xa-adp (connector module)
    The properties for the Source JMS Destination are
    1] ConnectionFactory = weblogic.jms.client.JMSXAConnectionFactory
    The properties for the Target JMS Destination are
    1] InitialContextFactory = com.tibco.tibjms.naming.TibjmsInitialContextFactory
    2] ConnectionFactory = XATopicConnectionFactory
    The EMS client version library is EMS version client library à 4.2.0
    The message Bridge Thread Pool Size is à 12
    When the weblogic is started, all the bridges comes up properly and are forwarding message to the target, however after some time (1 to 2 days) we observe some that some of the bridges are going down and we get see following error in the weblogic logs
    ####<May 26, 2010 12:00:56 AM GMT> <Warning> <Connector> <ngun015> <zlw1rdbs12-a> <ExecuteThread: '6' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-190032> << Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>
    ####<May 26, 2010 12:00:56 AM GMT> <Info> <MessagingBridge> <ngun015> <zlw1rdbs12-a> <ExecuteThread: '6' for queue: 'MessagingBridge'> <<WLS Kernel>> <> <BEA-200042> <Bridge RefDataCompanyBridge failed to connect to the source destination and will try again in 60 seconds. (javax.resource.ResourceException: Failed to start the connection)>
    Can you please help us resolve the above issue?
    Thanks,
    Mohanraj

    There seems to be couple of known issues with WLS 8.1 and Tibco EMS.. Check with support whether your issue is related to any of the below:
    Message bridge will stop responding and WLS has to be restarted to overcome this.
    There is a known bug on WLS 8.1. Bug 8062571 is for the issue.
    Should the connection be interrupted by a problem on the Tibco side, the messaging bridge never tries to reconnect. the problem can be that Tibco EMS is restarted for some reason or that the maximum number of messages that Tibco EMS can handle is reached.
    Unpublished bug8066979 is available for WebLogic Server 8.1 SP6 and later
    Unpublished bug8172940 is available for WebLogic Server 9.2 MP2 and later
    Note you can get more info about bridge problems by following the below steps:
    To debug the bridge you can enable debugging for the messaging bridge using either of the followings methods:
    * Add the following lines to your WebLogic start script (before the weblogic.Server line):
    -Dweblogic.debug.DebugMessagingBridgeStartup=true
    -Dweblogic.debug.DebugMessagingBridgeRuntime=true
    * Add the following statements to the ServerDebug entry in your configuration file (config.xml) for the server that the messaging bridge is running on:
    DebugMessagingBridgeStartup="true"
    DebugMessagingBridgeRuntime="true"
    Once debugging is enabled for the messaging bridge, the debugging messages are sent to the server log by default. However, if you want them to appear in the Administration Console, add “DumpToConsole” to the statements show above. For example:
    -Dweblogic.debug.DebugMessagingBridgeStartupDumpToConsole=true
    Edited by: atheek1 on May 30, 2010 5:19 AM

Maybe you are looking for

  • Iphone 5 IOS 8.1.1 videos won't play on windows 8.1

    Hi, I have recently come across a problem with transferring over videos to my PC from my iphone 5 since installing the recent update 8.1.1. Prior to this last IOS update, I have always been able to transfer my videos across to my PC and play them usi

  • Sequence will not validate with run time prompts in business rules

    I am in Hyperion Planning v 1.1.1.3, with Workforce initialized. I am creating a sequence of business rules. The rules use run time prompts within them and validate when used on their own. However, when I insert them in a sequence the sequence will n

  • Unable to use RAS SDK for server-side printing for XI 3.1

    Hi all, I am using RAS SDK for server-side printing.  Here are my codes: ISessionMgr sessionMgr = CrystalEnterprise.getSessionMgr(); IEnterpriseSession enterpriseSession = sessionMgr.logon("Administrator", "", "cdi5boe", "secEnterprise"); IInfoStore

  • How do I add a video time trigger to control other symbols?

    I would like to use a video to trigger when other Symbols appear on the Stage at different times in the video. I've used the following code:        var vid = sym.$("VideoSymbolName")[0];        vid.addEventListener("timeupdate", function() {         

  • Memory & Export & Media Encoder

    Problem 1: Is there in CS4 a way to export a standard DV AVI file (standard DV 4:3 source material) without having to use Media Encoder?   In older versions of Premiere (CS2 for example) all I had to do was "Export to Movie" which created an AVI file