Debugging WLS 4.5.1 with Symantech VCafe

Hi,
If anybody knows how to debug EJBs running in WLS remotely from Visual
Cafe 3.0, will you please describe how you do it?
Config: WLS 4.5.1, Cafe 3.0, Oracle 8i, NT 4.0 & Solaris
Thanks!!!!
[eytan.vcf]

This was posted in the product support group:
Hi Andrew. You are not alone. Upgrading to 4.5.1 and the multiple
classloaders caused similar problems for everyone. Here's how to get Cafe
and WebLogic 4.5.1 to play nice together.
1. Set the startup class in your project to the class the loads
weblogic. In this class, set -Dclasspath, -Dweblogic.class.path and
-Dweblogic.system.home variables.
2 Compile your entire project.
3. Go to Tools -> Env. options -> Debugging ->Run-Time Editing and check
the radio button that says 'Prompt before compiling ...'
4. Go to Project -> Options ->Directories and uncheck 'Append class path'
and 'Auto-generate class path'
Now you are ready to debug. Try it and let me know if you have any
problems. Hope this helps.
--Vinny
Eytan Ben-Meir wrote:
Hi,
If anybody knows how to debug EJBs running in WLS remotely from Visual
Cafe 3.0, will you please describe how you do it?
Config: WLS 4.5.1, Cafe 3.0, Oracle 8i, NT 4.0 & Solaris
Thanks!!!!

Similar Messages

Debugging WLS remotelly

I would like to debug WLS (running on Linux) from MS Windows, without changing the code itself. I want to stop the execution (I can stop the whole WLS, also not neccessary to restrict stoping to a certain thread) at certain methode of class xxx. I have the sourcecode / classfiles also locally (Windows) they are identical with classes running on Linux. Is there any way for remote debugging ?
I don't need very confortable debugging. I need only to see, what methodes were executed. I have a hang-problem (a method "never comes back"). Because in this method are called a lot of methodes with access to host, etc. is also helpful to know, where it hangs.
Thank you in advance.

You'll need to start your WLS with the correct JPDA (Java Platform Debugger Architecture) parameters. If the server is set up correctly, you can connect from any JPDA-based debugger on any host (assuming your firewall lets you reach it).
If your Linux server is running in development mode, it probably already has the correct startup parameters, which defaults to sockets, and port 8453, most likely.
That should get you started on your research.

Eclipse - debug step is not synchronise with source code.

Hi,
I have an web application witch run on tomcat, when Idebug the application, the debug steps are not synchronize with the source code. Same thing when I change the code , after making the jar file and putting it in the WEB-INF/lib of the web application, the modifications didn't take place. It seem that the old code always remains. I looked at the compile class in the jar file and the modifications have been taken in to account.
what can cause this kind of behavior ? I relaunch tomcat many times without succes ?
any help ? thanks a lot.

Can it be the case that you compile your JAR optimized, i.e. without debug information? Then your classes are also without debug information.
This sounds very likely as a refresh problem. Be sure that both source files in Eclipse and class files in Tomcat have the same version (e.g. with simple system.out).

How can I enable remote debug in weblogic to use with Rational RSA IDE?

How can I enable the remote debugging technique so that I can work with my IDE.
I use RSA by IBM as the IDE
What should be the changes in the setdomainenv or startweblogic?
I use 10.3
Please help.. ur help is appreciable...

Hi,
I did not make any console adjustments for debugging on my WebLogic 10.3.2.0 - however I am running in development mode on an "adminServer" (an option during the install)
In the console there is a debug setup page - that seems to have no effect for me (I can always debug) - so either it is a combination of development mode and/or the startWeblogic script from the Eclipse plugin.
However, these debug settings are likely for debugging into the server - you only want to debug your own app code right?
On the console page goto
http://localhost:7001/console/console.portal?_nfpb=true&_pageLabel=ServerDebugPage
servers | AdminServer | configuration-debug | expand weblogic
I see...
"Use this page to define debug settings for this server.
Debug settings for this Server
EnableDisableClear Showing 1 to 2 of 2 Previous Next
Debug Scopes and Attributes State
default Disabled
weblogic Disabled
EnableDisableClear Showing 1 to 2 of 2 Previous Next
Try expanding the whole tree and selecting the root to enable everything.
You will see the following
10-Dec-2009 11:53:46 o'clock AM EST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute DebugAbbreviation on weblogic.management.configuration.ServerDebugMBeanImpl@47a32e1b([base_domain]/Servers[AdminServer]/ServerDebug[AdminServer]) has been changed. This may require redeploying or rebooting configured entities>
<10-Dec-2009 11:53:46 o'clock AM EST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server AdminServer. This server must be rebooted in order to consume this change.>
<10-Dec-2009 11:53:46 o'clock AM EST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=ServerDebugPage.>
When I debug WebLogic 10.3.2.0 from Eclipse 3.5 EE - I see the following in my server startup log which includes the "-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453" you mentioned.
Starting WLS with line:
c:\opt\wls10320\JROCKI~1.5-3\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\opt\wls10320\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\opt\wls10320\WLSERV~1.3 -Dwls.home=C:\opt\wls10320\WLSERV~1.3\server -Dweblogic.home=C:\opt\wls10320\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=c:\opt\wls10320\patch_wls1032\profiles\default\sysext_manifest_classpath weblogic.Server
Listening for transport dt_socket at address: 8453
The server process listening on debug portl 8453 ooks like this
Oracle WebLogic Server 11gR1 PatchSet 1 at localhost [Oracle WebLogic Launch Configuration]
     BEA JRockit(R)[localhost:8453]
          Thread [Main Thread] (Running)
          Daemon Thread [Timer-0] (Running)
          Daemon Thread [Timer-1] (Running)
          Daemon Thread [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] (Running)
          Daemon Thread [weblogic.time.TimeEventGenerator] (Running)
          Daemon Thread [JMAPI event thread] (Running)
          Daemon Thread [weblogic.timers.TimerThread] (Running)
          Daemon Thread [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] (Running)
          Daemon Thread [Thread-7] (Running)
          Daemon Thread [ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'] (Running)
          Daemon Thread [ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'] (Running)
I hit a breakpoint and see
Daemon Thread [[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'] (Suspended (breakpoint at line 56 in ApplicationService))
     ApplicationService_5ptwty_Impl(ApplicationService).insertObjects(List<Cell>) line: 56
     NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
     NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39
     DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
     Method.invoke(Object, Object...) line: 597
     AopUtils.invokeJoinpointUsingReflection(Object, Method, Object[]) line: 310
     ReflectiveMethodInvocation.invokeJoinpoint() line: 182
     ReflectiveMethodInvocation.proceed() line: 149
     DelegatingIntroductionInterceptor.doProceed(MethodInvocation) line: 131
     DelegatingIntroductionInterceptor.invoke(MethodInvocation) line: 119
     ReflectiveMethodInvocation.proceed() line: 171
     MethodInvocationVisitorImpl.visit() line: 37
     EnvironmentInterceptorCallbackImpl.callback(MethodInvocationVisitor) line: 55
     EnvironmentInterceptor.invoke(MethodInvocation) line: 50
     ReflectiveMethodInvocation.proceed() line: 171
     ExposeInvocationInterceptor.invoke(MethodInvocation) line: 89
     ReflectiveMethodInvocation.proceed() line: 171
     DelegatingIntroductionInterceptor.doProceed(MethodInvocation) line: 131
     DelegatingIntroductionInterceptor.invoke(MethodInvocation) line: 119
     ReflectiveMethodInvocation.proceed() line: 171
     JdkDynamicAopProxy.invoke(Object, Method, Object[]) line: 204
     $Proxy68.insertObjects(List) line: not available
     ApplicationService_5ptwty_ApplicationServiceLocalImpl.insertObjects(List<Cell>) line: 306
     FrontController.generateGlider(PrintWriter) line: 240
thank you
/michael
http://www.eclipselink.org

WLS 10.3.4 with ADF - Performance issues

Hi,
I'm doing some performance tuning on our ADF app on WLS 10.3.4. I ran JRockit Mission Control for 1 minute and it's telling me that 113,503 exceptions were thrown! 70,000 ClassNotFoundException, 27,000 NoSuchMethodException etc.
Stupid question maybe, but is this normal? Debugging shows no particular class is missing, there are many.
Thanks.
Edited by: 918121 on 01-Mar-2012 06:05

I'd try posting this in the ADF forum, perhaps with some examples of the observations you are seeing.
-steve-

Remote Debugging WLS v. 8.1/ Windows: How to set JAVA_OPTIONS?

How does one set JAVA_OPTIONS with no "startWebLogic.bat" supplied with WLS v. 8.1, for remote debugging?
          (Note: Prefer to not have to run in unix emulation.)


          WebLogic 8.1 has the startWebLogic script file in user_projects/domains/<WLS_Domain>
          directory. <WLS_Domain> is the WebLogic Server Domain directory.
          Marvin Toll <[email protected]> wrote:
          >How does one set JAVA_OPTIONS with no "startWebLogic.bat" supplied with
          >WLS v. 8.1, for remote debugging?
          >
          >(Note: Prefer to not have to run in unix emulation.)

Remote Debugging WLS

Has anyone set up a script (Windows) to run WLS in debug mode (-Xdebug)
according to the JPDA spec using JDK1.2.2? I want to step into EJB from
JBuilder.
Thanks, Jon

Hi.
I modified one of our standard start scripts for WL 4.5.1 to do this. The
server does start with this script, but I haven't used it to step into an
EJB from an IDE.
Hope this helps,
Michael Young
BEA Systems
levyjj wrote:
Has anyone set up a script (Windows) to run WLS in debug mode (-Xdebug)
according to the JPDA spec using JDK1.2.2? I want to step into EJB from
JBuilder.
Thanks, Jon[startdebug12.cmd]

Remote debugging wls 7

I'm having a problem trying to debug a WLS application. Using intellij to attach
to the WLS 7 instance it takes an infinitely long time to remote process.
i had a similar problem in v6 that was solved by changing the VM from hotspot to
classic.
Any help
Simon

          WebLogic 8.1 has the startWebLogic script file in user_projects/domains/<WLS_Domain>
          directory. <WLS_Domain> is the WebLogic Server Domain directory.
          Marvin Toll <[email protected]> wrote:
          >How does one set JAVA_OPTIONS with no "startWebLogic.bat" supplied with
          >WLS v. 8.1, for remote debugging?
          >
          >(Note: Prefer to not have to run in unix emulation.)

How to debug standard report that starts with a transaction?

I want to run a report in debug mode. The report name is RFFMEPGAX, which
is normally run using transaction FMRP_RFFMEP1AX.
I want to start the transaction, fill in the form with the values I need, then
hopefully the report code pops up in a debug window......
Is there a way to do this? I know how to open the debugger, but have not
yet figured out a way to get the initial transaction to open in debug mode.

If the transaction starts with a pop-up message, you can create a text file with this...
[System]
Name=R/3
Client=
Description=
[User]
Name=
Language=
Password=
[Function]
Command=/H
Title=Title
Type=SystemCommand
Name it <b>Debug</b> and just drag it to the pop-up window...The debugger is going to start after a single Enter button...
Greetings,
Blag.

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.

Windows Kernel Debbuging: Debug over virtual serial port with WDK 8.1

I'm currently having some issues doing kernel debugging of a Windows 7 x64 target from my Windows 8.1 x64 host machine. I'm running Visual Studio 2013 with WDK 8.1 on my host and have provisioned my target machine running in VMWare.
Here are my configurations for the target machine. It was configured by reading mostly from here - http://www.codeproject.com/Tips/545835/Kernel-Mode-Debugging-in-a-VM-using-Visual-Studio :
    Windows 7 x64
    Serial port COM2 with VMWare with name \\.\pipe\com2. All proper options in VMWare are checked
    Debug flag for OS enabled through msconfig. Debug port is COM2 running at 115200 baud.
    I ran the test target client "WDK Test Target Setup x64-x64_en-us.exe" on the machine before provisioning the computer
I was able to provision the computer properly -- it created the WDK Remove User account. However, I'm running into some issues actually debugging. Below are the steps
    Launch the Windows 7 x64 target image in VMWare and wait on the boot menu
    In Visual Studio (host machine), go to Debug -> Attach to process -> Select my computer -> Select process "Kernel" -> Attach
    In VMWare, press enter to boot Windows
    It takes a while, but on my host machine, Visual Studio eventually connects. I can choose to "Break All" and actually use the debugger.
However, I can't seem to connect to the debugger if I don't do it before booting the kernel. And I can only attach once. For example, I can't let Windows initialize to the desktop and then build my driver and begin debugging. The debugger will always hang on
"Waiting to reconnect...". The same goes for if I begin debugging on kernel initialization, decide to stop debugging, then try to reconnect or reattach; it will hang on "Waiting to reconnect..." indefinitely as well.

Follow the directions here: https://msdn.microsoft.com/en-us/library/windows/hardware/jj200334%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
You are using user mode debug setup menus, that won't work.
Mark Roddy Windows Driver and OS consultant www.hollistech.com

WLS Proxy in Cluster with Firewall

We are currently setting up a system that has a DMZ with Netscape inside
          the DMZ proxying a WLS cluster that is behind the DMZ. When a cookie
          based session is started a cookie is returned successfully, but it looks
          like the physical address versuses a firewalled(NATed) address is placed
          in the cookie. This in turn causes a failure on accessing the WLS
          server. The firewall rejects future requests due to the use of the
          physical instead of the NATed address.
          If you understand the above and can help I would appreciate it.
          Don Davis
          D3, Inc.


Just wanted to let you know that everything is working with the latest patches for
          4.5.1 and 5.1.
          Thanks for the help
          Don Davis
          Prasad Peddada wrote:
          > You might have to wait for the service pack. In the mean time I can give you a one
          > of patch for testing.
          >
          > - Prasad
          >
          > Don Davis wrote:
          >
          > > Thanks for the help Prasad,
          > >
          > > I have migrated to 5.1 and set the DNSName property.
          > >
          > > I will let you know if all goes well.
          > >
          > > Don Davis
          > >
          > > Prasad Peddada wrote:
          > >
          > > > The problem has been fixed.
          > > >
          > > > Prasad Peddada wrote:
          > > >
          > > > > I assume you are using 451. WLS proxy with firewall was not behaving right.
          > > > > Either you can wait for the next service pack or contact
          > > > > [email protected] for a one of patch.
          > > > >
          > > > > Remember to set weblogic.system.DNSName in the properties file for each
          > > > > server.
          > > > >
          > > > > - Prasad
          > > > >
          > > > > Don Davis wrote:
          > > > >
          > > > > > We are currently setting up a system that has a DMZ with Netscape inside
          > > > > > the DMZ proxying a WLS cluster that is behind the DMZ. When a cookie
          > > > > > based session is started a cookie is returned successfully, but it looks
          > > > > > like the physical address versuses a firewalled(NATed) address is placed
          > > > > > in the cookie. This in turn causes a failure on accessing the WLS
          > > > > > server. The firewall rejects future requests due to the use of the
          > > > > > physical instead of the NATed address.
          > > > > >
          > > > > > If you understand the above and can help I would appreciate it.
          > > > > >
          > > > > > Don Davis
          > > > > > D3, Inc.

WLS 9.1 bug with WebLogic Plug-In Enabled?

We are currently upgrading from WLS 8.1 to WLS 9.1. We use Apache HTTP Server 2.0 on Red Hat Enterprise 4 with the weblogic plugin. We have the plugin configured properly as the application functions properly except for calls to request.getRemoteAddr(). We have WebLogic Plug-In Enabled enabled at the cluster and server level. We verified MBeans reported true using the weblogic scripting tool in interactive mode. We see the WL-Client-Proxy-IP header in the request as expected. We've searched the newsgroups and BEA site and they mention setting the WebLogic Plug-In Enabled option as the problem. It doesn't appear to be ours.
Is there a bug or are we missing something else? If it is a bug, is there a patch? We have a workaround in place which gets the WL-Client-Proxy-IP header directly, but obviously this isn't the optimal solution for something that was working properly in 8.1.
Thank you in advance,
Daniel

Sure! Calling directly a server is more fast then pass through a load balancer and through a webserver and through (again?) the weblogic plugin (even if it's only a lib!!!)...
          Moreover you could have performance problem if you use hostname instead of IP address, cause for every client call a DNS query must be executed.
          One more thing... The only one load balancer algorithm you must use is the round robin, I'm not speaking about weblogic load balancing algorithm... But about hardware load balancer above the webserver.
          Regards
          Antenore Gatta
          Middleware Specialist
          Hequa S.r.l
          C.so Buenos Aires 77
          20124 Milano
          http://www.Hequa.it
          Tel +39(0)267493078
          Fax +39(0)267493079
          Mobile +39 3481537897
          ______________________________________

WLS 5.1 SP6 with JRE 1.3 - Cannot start server from Start Menu or as NT service

Hi:
I am trying to setup WLS 5.1 SP6 runing with JRE 1.3 on Windows 2000 Server to
run as an NT Service or from the start menu. The wlserver program is invoked the
following error message is returned. (A similar error is returned when starting
as an NT Service)
=====================================================
D:\weblogic>bin\wlserver
Java dll not found. Bad value for JAVA_HOME.
The system cannot find the path specified.
Java dll not found. Bad value for JAVA_HOME.
The system cannot find the path specified.
loadIt: Java DLL not found.
The Windows registry is misconfigured
for the WebLogic Server
JAVA dll not found: d:\jre1.3.0_02\jre\bin\javai.dll:
The Windows registry is misconfigured
for the WebLogic Server
Can't start WebLogic Server: (Can't start Java VM) err=0x2000001
D:\weblogic>
=========================================================
I found old messages in the newsgroups indicating that there have been issues
with WLS 5.1 and Java 1.3 on NT running as a service or from the start menu.
But there does not seem to be a resolution to this problem yet.
Is there a workaround to this issue. Is there a new wlserver that supports 1.3
for WLS 5.1. I am running with SP6 because we need to run with WLCS 3.2 also.
WLS 5.1 starts up fine as a service or from the start menu with the JRE 1.2 shipped
with the product or from a command window with startWeblogic running SDK 1.3
Thanks in advance for any help to clear this up.
-William

Thanks for the suggestion... the registry already has this setting... that does
not seem to be it.
From looking closer at what is installed with the 1.3 JRE versus the 1.2 JRE packaged
with the 5.1 server... it seems to me that the issue has to do with support for
the Hotspot VM.
The 1.3 JRE has a hotspot subdirectory under the bin, there is no classic subdirectory,
as is the case with the 1.2 JRE in the 5.1 package or even with a standard SDK
1.3 installation.
Does 5.1 support the hotspot vm. How can I switch it to use the 'older' JVM instead?
If I copy the 'classic' jvm.dll from the sdk 1.3 installation into the bin\classic
directory of the 1.3 JRE, the server does start, but an error message indicating
that the javai.dll was not found still comes up. Followed by the following error:
Warning: JIT compiler "symcjit" not found. Will use interpreter.
The server startup output then comes up ... Please help, anyone?
"Jcmuppy" <[email protected]> wrote:
Registry key 'Software\JavaSoft\Java Runtime Environment\CurrentVersion'
has value '1.1', but '1.3' is required.
If the value is "1.1", chage the value into "1.3"
"William Rojas" <[email protected]> wrote:
>
Hi:
I am trying to setup WLS 5.1 SP6 runing with JRE 1.3 on Windows 2000
Server to
run as an NT Service or from the start menu. The wlserver program is
invoked the
following error message is returned. (A similar error is returned when
starting
as an NT Service)
=====================================================
D:\weblogic>bin\wlserver
Java dll not found. Bad value for JAVA_HOME.
The system cannot find the path specified.
Java dll not found. Bad value for JAVA_HOME.
The system cannot find the path specified.
loadIt: Java DLL not found.
The Windows registry is misconfigured
for the WebLogic Server
JAVA dll not found: d:\jre1.3.0_02\jre\bin\javai.dll:
The Windows registry is misconfigured
for the WebLogic Server
Can't start WebLogic Server: (Can't start Java VM) err=0x2000001
D:\weblogic>
=========================================================
I found old messages in the newsgroups indicating that there have been
issues
with WLS 5.1 and Java 1.3 on NT running as a service or from the start
menu.
But there does not seem to be a resolution to this problem yet.
Is there a workaround to this issue. Is there a new wlserver that supports
1.3
for WLS 5.1. I am running with SP6 because we need to run with WLCS
3.2 also.
WLS 5.1 starts up fine as a service or from the start menu with the JRE
1.2 shipped
with the product or from a command window with startWeblogic running
SDK 1.3
Thanks in advance for any help to clear this up.
-William

Debugging WLS 4.5.1 with Symantech VCafe

Similar Messages

Maybe you are looking for