Debugging in Workshop

I have a project that I am building using ant build based on the split development
diretory structure. I am able to build the application from within Workshop.
I can set breakpoints within Java but the debug menus are never enabled. I saw
the post about setting breakpoints from within JSPs; however, I haven't been able
to set a breakpoint in a JSP. I've not found any documentation that walks me
through the nuts and bolts of getting debugging going in Workshop. Can I do what
I'm trying to do and is there any doc that might help me move forward?

My guess is that your project isn't a Web Project, but is instead a Java
Project or something similar. You can quickly determine the type of
the project by right clicking on it in the Application tree and
selecting Properties. The dialog's title shows the type. It needs to be
"Web" in order to debug JSPs.
To change project types, you can right click on the project in the
Application tree and select Remove from Application. This will not
delete the files. Then, go to File->Import Project, browse to the
correct directory, and select Web Project from the list of project types.
Note that Workshop may automatically detect the project type if it
contains a Java Control. In that case, you'll need to separate the JSPs
into a different project.
Josh
Jill Nabonsal wrote:
I have a project that I am building using ant build based on the split development
diretory structure. I am able to build the application from within Workshop.
I can set breakpoints within Java but the debug menus are never enabled. I saw
the post about setting breakpoints from within JSPs; however, I haven't been able
to set a breakpoint in a JSP. I've not found any documentation that walks me
through the nuts and bolts of getting debugging going in Workshop. Can I do what
I'm trying to do and is there any doc that might help me move forward?

Similar Messages

Error trying to debug in workshop

I am using 8.1 SP4 on Windows XP Pro in Development mode
When I start debugging my web service in workshop, I get an error that says: Unable to enable debugging. Verify that your webapp deployed correctly.
I did verify that the web service is deployed, and I am able to send messages to it. I am using the stopweblogic.cmd script to stop my instance.

Any ideas?

Solution 1
%userprofile%\Local Settings\Application Data\Adobe folder does not exist
Solution 2
Already tried this
Solution 3
Tried disabling antivirus

"Unable to enable debugging" within Workshop 8.1

I'm testing a portal application with workshop 8.1. When I started the .portal, I got this error "Unable to enable debugging. Verify that you webapp deployed correctly". If I choose to start without debugging it's OK.
The deployment was successfully done without error. Is there anything else I can check?
Thanks

Thanks.
One of my concerns is that this change will update the .work file with some local values such as host name and port number, etc. For some reason we could not use a generic name such as "localhost" in our development. This causes a little problem since the .work file contains some hard coded parameters can not be shared amoung other developers.
Hopefully there is another better solution.
Thanks again for the help!

No System.out or System.err when Debugging in workshop

I'm running workshop 8.1.3. When I debug my application I can see it process several lines with System.out and System.err. However I can not find the ouput anywhere. I've checked the Build window, output window among others but cannot find any of the output. What am I doing wrong ?

Probably the output is going to the WebLogic window. On Windows, it would be the command prompt window where the server instance is launched.
I'm running workshop 8.1.3. When I debug my
application I can see it process several lines with
System.out and System.err. However I can not find the
ouput anywhere. I've checked the Build window, output
window among others but cannot find any of the
output. What am I doing wrong ?

Hotswap debugging in workshop 9

Hi,
I remember that in Eclipse 2 [with Weblogic 8.1 being launched from the IDE through a plugin] & Visual age (before I used Eclipse) I used to debug web applications in a very productive manner. When the application was being debugged I could fix the code and the debugger would start from the beginning of the current method and continue without me having to restart my web app right from the login screen all over again. From what I know it is a JDK1.4 feature.
I guess this is the functionality I am talking about -
1) http://java.sun.com/j2se/1.4.2/docs/guide/jpda/enhancements.html#hotswap
2)http://www-128.ibm.com/developerworks/library/os-ecbug/#N1015F
Look under the section "Hotswap Bug Fixing: On-the-fly" code fixing
Now why isn't this possible with workshop 9 ? What extra configurations need to be done to be able to do this?
regards
Srini

This seems strange; hotswap debugging should work with Workshop 9 (i.e. Eclipse-based Workshop). It's a low-level JVM feature; I have used it in Workshop before without problems. Do you have a specific use case for which it's failing? (Be aware that hotswap debugging only works if you change code inside the body a method; if you change the shape of a type (not just the public shape -- if you add a field or method you are changing the shape) the change can't be hot swapped).
-Gary Horen

Debug information can't be recognized by gcc

After compiled by acc -c -g. the debug information can't be recognized by gcc
For example, two files a.c and b.cc
acc -c -g a.c
gcc -c -g b.cc or gcc -c -gstabs b.cc
gcc -o ab a.o b.o
Debug with workshop, DBX can't know b's debug information.
so, my question is:
1. why the debug infomation ( I guess is stabs) produced by acc can't work with gcc
2. Is it possible for me to debug b's source code?
Thanks in advance

2. Is it possible for me to debug b's source code?Yes, of course. But consider this: stabs generated by gcc are not compatible with dbx (only gdb), so you should use -gdwarf-2 gcc option and latest dbx, which can be downloaded here http://developers.sun.com/prodtech/cc/downloads/index.jsp

Integrating an existing struts application

Sorry if this has been discussed before but I tried searching the newsgroup with
no success. tia.
I am trying to integrate the struts application found in the struts-example.war
file that I extracted from the jakarta-struts-1.1.zip file from jakarta.apache.org.
(I have successfully deployed and tested this war file to the weblogic server
so I know the application works.)
I unzip the war file into a temp directory and follow the instructions found in
"e-docs.bea.com/workshop/docs81/doc/en/portal/buildportals/appIntegratingStruts.html"
After creating a struts portlet using the wizard and putting the portlet into
my test portal, when I try to run the portal using debug in Workshop, I get:
<Error> <netuix> <BEA-420599> <Unable to perform action [example/begin] for Struts
module [example]. Please ensure that both module and action are correct.>
<Error> <netuix> <BEA-420037> <There was an error loading the requested URI /example/mainMenu.jsp.>
<Error> <netuix> <BEA-423012> <There was an error while running a lifecycle stage
Lifecycle: UIControl.render :: for the control :: null ::.com.bea.netuix.nf.UIControlException:
No ActionResult returned for action [example/begin] in Struts module [example].
Please ensure that both module and action are correct in portlet StrutsContent
element.
at com.bea.netuix.servlets.controls.content.StrutsContent.preRender(StrutsContent.java:399)
at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:388)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:619)
I've tried changing the struts action and content uri with no success. I've tried
changing the
struts-auto-config-<module name>.xml file with even less success.
Help would be greatly appreciated. tia.

Have anyone got the answer from BEA ...
I am also having the same problem.
Pl. post if you have any answers.
Thanks
Kicha
"Julien De Santis-Caron" <[email protected]> wrote:
>
Hi,
I have the same problem and I can't find any way for correcting this.
Please, help-us with this issue because integration of existing Struts
applications
into a portlet is a critical issue for choosing a Portal solution.
thanks
Julien De Santis-Caron
"Dean Saiki" <[email protected]> wrote:
Sorry if this has been discussed before but I tried searching the newsgroup
with
no success. tia.
I am trying to integrate the struts application found in the struts-example.war
file that I extracted from the jakarta-struts-1.1.zip file from jakarta.apache.org.
(I have successfully deployed and tested this war file to the weblogic
server
so I know the application works.)
I unzip the war file into a temp directory and follow the instructions
found in
"e-docs.bea.com/workshop/docs81/doc/en/portal/buildportals/appIntegratingStruts.html"
After creating a struts portlet using the wizard and putting the portlet
into
my test portal, when I try to run the portal using debug in Workshop,
I get:
<Error> <netuix> <BEA-420599> <Unable to perform action [example/begin]
for Struts
module [example]. Please ensure that both module and action are correct.>
<Error> <netuix> <BEA-420037> <There was an error loading the requested
URI /example/mainMenu.jsp.>
<Error> <netuix> <BEA-423012> <There was an error while running a lifecycle
stage
Lifecycle: UIControl.render :: for the control :: null ::.com.bea.netuix.nf.UIControlException:
No ActionResult returned for action [example/begin] in Struts module
[example].
Please ensure that both module and action are correct in portlet StrutsContent
element.
at com.bea.netuix.servlets.controls.content.StrutsContent.preRender(StrutsContent.java:399)
at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:388)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:619)
I've tried changing the struts action and content uri with no success.
I've tried
changing the
struts-auto-config-<module name>.xml file with even less success.
Help would be greatly appreciated. tia.

How to deploy/debug maven project in workshop?

I've installed m2eclipse in Workshop 10.0. I'm able to download maven projects from a subversion repository. m2eclipse allows right-clicking for maven-install, maven-build, maven-package. Build generates a proper war file.
But Workshop does not recognize it as a web project so it will not allow me to deploy it to my local server. Anyway to get this to work?
I know in the past, checkouting out source from SVN/CVS, a project wizard pops up and allows you to set the project type.
Right now, I'm manually installing my war file to the app server. If I want to do any debugging it will have to be remote debugging. But that requires a few more steps to deal with. A productivity killer.

The File->import->WAR option might solve your problem.
See:
http://helponline.oracle.com/jdeveloper/help?topic=ide_pfilesimportingexistingintojdev_html

Breakpoints not caught during debugging in BEA Workshop 8.1 (Win7 Pro OS)

Hi all,
As of the moment, we're slowly making our migration from our existing WebLogic 8.1 Platform to the newer WebLogic 12c. Some people in my team are starting to use Windows 7 Professional for the WL8.1 (which includes the application server and the developer IDE, "Workshop").
Been using and debugging myself on my own Windows 7 Home Edition laptop. Haven't been encountering problems, but lately, those of us using Windows 7 Pro are not able to catch breakpoints during debugging. I tried it on a separate machine running Win 7 Pro as well with my same domain settings and all, and I confirm that the breakpoints aren't caught. How is this so? If I recall, the latest service pack for WL8.1 is SP6; are there any other patches that we need to install to resolve this?
I'm looking at the possibility of having to use Win7's "XP mode" if there are no options. But it'd be better if we can avoid that altogether... Thanks!

David,
Can you try passing in the 1.5 VM location manually as listed below
WorkshopInstaller.exe LAX_VM d:\bea\9server\jdk150_04\bin\java.exe
Can you also make sure that the 1.5 JVM value entry is the first entry in the PATH environment variable.
cheers
Raj

BEA Workshop Studio 3.2: Server classpath customization & Remote Debugging

BEA Workshop Studio 3.2:
The server classpath customization and remote debugging issues have been fixed in the 3.2 release, which is now available for download at http://workshopstudio.bea.com/download.do.
Workround for the 3.1 release:
By switching to war deployment mode the server classpath can be customized in the launch configuration.
You can see the complete list of new features in 3.2 at:
http://e-docs.bea.com/workshop/docs92/studio32/WhatsNew.htm

Thanks Ram,as you said i server runtime i pointed to jdk1.5,that error has been resolved.
Now i'm getting the parsing config.xml file.
My server is Test9.
C:\bea\jdk150_04\bin\java -classpath C:\bea\weblogic91\server\lib\weblogic_sp.jar;C:\bea\weblogic91\server\lib\weblogic.jar;C:\bea\weblogic91\server\lib\webservices.jar;C:\bea\jdk150_04\lib\tools.jar -Dbea.home=C:/bea -Dweblogic.ConfigFile=config/config.xml -Dweblogic.Name=Test9 -Dweblogic.ListenAddress=localhost -Dweblogic.ListenPort=7002 -Djava.library.path=C:\bea\weblogic91\server\bin -Djava.security.policy=C:\bea\weblogic91\server\lib\weblogic.policy -Dweblogic.management.discover=false -Dweblogic.ProductionModeEnabled=false -Dweblogic.management.password=weblogic -Dweblogic.management.username=weblogic weblogic.Server
<Aug 17, 2006 8:27:05 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.5.0_04-b05 from Sun Microsystems Inc.>
<Aug 17, 2006 8:27:06 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.1 Mon Dec 12 19:26:33 EST 2005 689178 >
<Aug 17, 2006 8:27:08 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141266]Parsing Failure in config.xml: The following failures occurred:
-- Unresolved reference to Test9 by [Test9]/AppDeployments[__wstudio_autoconfig_deployment__]/Targets
 at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:118)
 at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:38)
 at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:365)
 at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:116)
 at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:630)
 at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:402)
 at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
 at weblogic.Server.main(Server.java:67)
Caused by: weblogic.descriptor.DescriptorValidateException: The following failures occurred:
-- Unresolved reference to Test9 by [Test9]/AppDeployments[__wstudio_autoconfig_deployment__]/Targets
 at weblogic.descriptor.internal.ReferenceManager.resolveReferences(ReferenceManager.java:265)
 at weblogic.descriptor.internal.DescriptorImpl.validate(DescriptorImpl.java:285)
 at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)
 at weblogic.management.provider.internal.DescriptorManagerHelper.loadDescriptor(DescriptorManagerHelper.java:52)
 at weblogic.management.provider.internal.RuntimeAccessImpl$IOHelperImpl.parseXML(RuntimeAccessImpl.java:576)
 at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:220)
 at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:106)
 ... 7 more
>
<Aug 17, 2006 8:27:08 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Aug 17, 2006 8:27:08 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Aug 17, 2006 8:27:08 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Thanks
Ram

Generating Debug Info Setting in Weblogic Workshop (.work)

Hi,
I am using Weblogic Workshop ver 8.1.3. I need to set
-g option during java compilation. I am using weblogic workshop (.work) file) for compilation. Could any one tell me what are the setting required for generating debug info while compilation.
Thanx,
Cleophus P.

Hello Cleophus,
What debug information are you looking for ?
In 8.1, Workshop uses a proprietary compiler to compile Workshop resources.
Cheers
Raj
BTW: the latest SP for Workshop 8.1 is Service pack 6

Can't debug in Sun Workshop 6.2 anymore

Hi,
Yesterday, we could not longer debug any of our C++ source code in Sun Workshop 6.2 on Solaris 8. We receive the following message when loading a program:
Reading <executable>
There might be too many LWP's in this process.
See `help dbxenv' under mt_scalable.
dbx: Cannot open lwpstatus.
dbx: warning: process initialization failed
This always occurs on:
C++ source
C source
code with 1 LWP
code with >1 LWPs
The same error occurs when we run dbx by itself.
This error is not occuring on Sun Workshop 6.2 on our Solaris 9 development server.
Any help, hints are most appreciated.
Thanks,
Tom

Was the application built on Solaris 8 or Solaris 9? An application built on Solaris 9 will not in general run correctly on Solaris 8.
Solaris 9 uses a different thread library than the default library on Solaris 8. Try re-linking on Solaris 8 (assuming the application was built on Solaris 8) using the optional thread library (which is the only thread library on Solaris 9).
You don`t have to recompile anything. In each link step, add the options
-L/usr/lib/lwp -R/usr/lib/lwp
to the command line (in addition to all existing options).
Finally, WS6.2 is End Of Life, and little support is available for it. Try using Sun Studio 11 instead. You can use the new debugger on old code, and you can switch to the new compilers when convenient. Studio 11 is free, and supports Solaris 8, 9, and 10. (Studio 12 is the current release, but does not support Solaris 8, which is End Of Life.)
http://developers.sun.com/sunstudio

Workshop 6U2 debug problem

After debugging for a while the dbx shell that workshop uses becomes unstable. I have to restart the whole environment
This also is produced on the console:
workshop: warning: MsgSnd::snd_via(): no socket -- msg 'DBX_KSH_CMD' dropped
Has anyone got a workaround for this ?

This error message means that the dbx binary running inside
workshop is crashing. If you can go to the machine where
the tool is running, and copy the /tmp/core file and
compress it and then mail it to me ([email protected])
then I'll file a bug for you.
You can check the core file to make sure it's from dbx:
% file /tmp/core
/tmp/core: ELF 32-bit MSB core file SPARC Version 1, from 'dbx'
The output should look something like that.
Also, if you have more questions or problems related
to the debugging tools there is now a separate forum
just for topics related to the debugging tools.
--chris

Solaris 2.5.1 Workshop 5.0 Debug Problem

I've posted this on comp.unix.solaris and haven't received any answers, so I thought this might work.
I was having trouble with a C++ system I'm wrapping up where a third
party library was requiring that I compile with the -mt flag for
multi-threading. This was causing iostreams in my program (which is
not multi-threaded) to hang on mutex locks. I was told this was a
known problem and to load all of the latest OS and Workshop patches.
So, I loaded the following patches and patch clusters:
Workshop
107311-17
107355-07
107357-11
107390-16
p-15569
p-15577
p-15589
p-15595
OS
2.5.1_Recommended
Now, I can't test the mutex problem because before I can get there, I
get the following message from the Teamware Debugger while stepping
through my program:
"Cannot resume process -- continue failed -- Device busy"
I am running Workshop 5.0 Dated 12/15/98.
Unfortunately, upgrading is not a possibility as the third party
software will not work on anything else. Also, the work I'm currently
doing is some touch-up before we port the whole thing to Java in a
couple of months.
If anyone has any ideas, I would be greatly appreciative.

When the keyboard is disconnected...display automatically goes to the serial port. If your keyboard is connected, reboot and make sure you have a video card installed. The onboard one may not have the vsimm(video memory) option, in which case you will have to get memory for it(very, very expensive) or get a separate sbus video card(these can be had very cheap on ebay). Let us know how it works out for you.

Can't Run program in Debug Mode

To: [email protected]
cc:
Subject: Can't Run program in Debug Mode
Has anyone else experienced this problem? We have written a non-express
program that uses the Express generated services project as a supplier
plan. However, when we try running this program in debug mode about 50%
(or more) of the time we abend while Forte is trying to partition the
application. Since we have many database classes in our Business Model we
are wondering if Forte is timing out during the partition phase or if the
server partition is running out of memory . The following error messages
are produced by Forte. Any suggestions???
=======================
Error messages on client:
=======================
SYSTEM ERROR: Unable to start the partition testacadprogoffer_CL0_Part1 on
any
of the nodes to which it has been assigned. See the remainder of the
error
stack for more information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on node
admin2.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
testacadprogoffer_CL0_Part1. Check server log file for more information
about
the specific problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Tue Dec 02 12:56:00
Distributed method called: qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor", (partitionId =
F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment CentralEnv
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Network partner closed connection. This usually means the
process at the other end of the wire failed. Please go look there and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Received close: Connection aborted (10053).
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
=======================
Log messages on server:
=======================
Attached to manager for node admin2.
aud Tue Dec 2 09:34:36 : Loading partition testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
aud Tue Dec 2 09:41:59 : Unloaded partition testacadprogoffer_cl0_Part2.
aud Tue Dec 2 09:49:44 : Loading partition testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
aud Tue Dec 2 10:00:12 : Unloaded partition testacadprogoffer_cl0_Part2.
aud Tue Dec 2 10:18:34 : Loading partition testacadprogoffer_cl0_Part3
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
aud Tue Dec 2 10:27:00 : Unloaded partition testacadprogoffer_cl0_Part3.
aud Tue Dec 2 10:47:03 : Loading partition
EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of agent
owner's partition.
aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
aud Tue Dec 2 11:09:26 : Unloaded partition
EvaluateApplRequirementsBO_CL0_Part1.
aud Tue Dec 2 12:36:14 : Loading partition testacadprogoffer_CL0_Part1
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
aud Tue Dec 2 12:45:17 : Unloaded partition testacadprogoffer_CL0_Part1.
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:49:01
Exception occurred (locally) on partition "Forte_Executor",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in application
"Forte Runtime", pid 14020 on node admin2 in environ
ment CentralEnv.
FATAL ERROR: ************* Out of Memory, requested (1K) available (0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:48:57
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
ERROR: TMgr.RunThread: task cm.Recv failed terminating.
Probably caused by a FATAL exception.
David Wilbur email: [email protected]
University of Windsor phone: 519-253-3000 ext. 2779
Windsor, Ontario Canada
-----------------------------------------------

Hi,
We have had the same problem in a non-express application
with a heavy server partition. In our case, the error was not
systematic, depending on the server workload at the time we
tried to partition and run.
The work-around we're using is to put the -fm flags (increasing the x
parameter to say 30000) in the 'server arguments' of your server
partition
properties in the partition workshop. Note that if your server is a Unix
platform,
you need to put double-quotes before and after the parenthesis in the -fm
syntax.
Hope this helps,
Vincent Figari
BTW, what Forte version are you using ?
On Tue, 2 Dec 1997 13:44:24 -0500 "David Wilbur"<[email protected]>
writes:
>
>
>
>
>
To: [email protected]
cc:
Subject: Can't Run program in Debug Mode
Has anyone else experienced this problem? We have written a
non-express
program that uses the Express generated services project as a supplier
plan. However, when we try running this program in debug mode about
50%
(or more) of the time we abend while Forte is trying to partition the
application. Since we have many database classes in our Business
Model we
are wondering if Forte is timing out during the partition phase or if
the
server partition is running out of memory . The following error
messages
are produced by Forte. Any suggestions???
=======================
Error messages on client:
=======================
SYSTEM ERROR: Unable to start the partition
testacadprogoffer_CL0_Part1 on
any
of the nodes to which it has been assigned. See the remainder of
the
error
stack for more information.
Class: qqsp_ResourceException
Error #: [1602, 593]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 5
Last TOOL statement: method overview.StartApplication
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Unable to start partition testacadprogoffer_CL0_Part1 on
node
admin2.
Class: qqsp_ErrorDescriptor
Error #: [1602, 592]
Detected at: qqcf_StandardConfig::LoadRemotePartition at 3
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
SYSTEM ERROR: Lost contact with remote server while trying to load
partition
testacadprogoffer_CL0_Part1. Check server log file for more
information
about
the specific problem.
Class: qqsp_ResourceException
Error #: [1301, 102]
Detected at: qqem_IPartitionAgent::Startup at 5
Error Time: Tue Dec 02 12:56:01
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: The connection to the partner was terminated by the
Communication
Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Tue Dec 02 12:56:00
Distributed method called:
qqrt_ForteExecAgentProxy.LoadPartition!6
(object name Unnamed) from partition "Forte_Executor",
(partitionId =
F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9, taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9.229]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Network partner closed connection. This usually means
the
process at the other end of the wire failed. Please go look there
and
find
out why.
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 2
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
INFORMATION: Received close: Connection aborted (10053).
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::ReceivedClose at 1
Error Time: Tue Dec 02 12:56:00
Exception occurred (locally) on partition "Express_cl7_Client",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3,
taskId =
[F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10e9:0x3.226]) in
application
"FTLaunch_cl0", pid 65 on node DWILBUR_NTWS in environment
CentralEnv.
=======================
Log messages on server:
=======================
Attached to manager for node admin2.
aud Tue Dec 2 09:34:36 : Loading partition
testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 09:41:58 : Shutting down partition as requested.
aud Tue Dec 2 09:41:59 : Unloaded partition
testacadprogoffer_cl0_Part2.
aud Tue Dec 2 09:49:44 : Loading partition
testacadprogoffer_cl0_Part2
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:00:11 : Shutting down partition as requested.
aud Tue Dec 2 10:00:12 : Unloaded partition
testacadprogoffer_cl0_Part2.
aud Tue Dec 2 10:18:34 : Loading partition
testacadprogoffer_cl0_Part3
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 10:27:00 : Shutting down partition as requested.
aud Tue Dec 2 10:27:00 : Unloaded partition
testacadprogoffer_cl0_Part3.
aud Tue Dec 2 10:47:03 : Loading partition
EvaluateApplRequirementsBO_CL0_Part1 built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 11:09:26 : Shutting down partition due to failure of
agent
owner's partition.
aud Tue Dec 2 11:09:26 : Shutting down partition as requested.
aud Tue Dec 2 11:09:26 : Unloaded partition
EvaluateApplRequirementsBO_CL0_Part1.
aud Tue Dec 2 12:36:14 : Loading partition
testacadprogoffer_CL0_Part1
built on <unknown>.
Attached to manager for node admin2.
aud Tue Dec 2 12:45:17 : Shutting down partition as requested.
aud Tue Dec 2 12:45:17 : Unloaded partition
testacadprogoffer_CL0_Part1.
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
Task 11: qqcm_HoseRecvServiceTask::Run: Caught unexpected exception
FATAL ERROR: ************* Out of Memory, requested (1K) available
(0K)
Class: qqsp_ResourceException with ReasonCode: SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:49:01
Exception occurred (locally) on partition "Forte_Executor",
(partitionId = F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3, t
askId = [F88CCF80-FA5D-11D0-A2F1-DA164885AA77:0x10f3.11]) in
application
"Forte Runtime", pid 14020 on node admin2 in environ
ment CentralEnv.
FATAL ERROR: ************* Out of Memory, requested (1K) available
(0K)
Class: qqsp_ResourceException with ReasonCode:
SP_ER_OUTOFMEMORY
Detected at: qqos_MemoryManager
Error Time: Tue Dec 2 12:48:57
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
FATAL ERROR: Out of Memory (reason = qqOS_MM_EX_OUT_OF_MEMORY)
ERROR: TMgr.RunThread: task cm.Recv failed terminating.
Probably caused by a FATAL exception.
David Wilbur email: [email protected]
University of Windsor phone: 519-253-3000 ext. 2779
Windsor, Ontario Canada

Debugging in Workshop

Similar Messages

Maybe you are looking for