Debug mode - NATIVE_POPUP_LOV - Fallback to legacy LOV support.

Hi,
When I consult the debug logs of my pages, I see the rendering of my items.
Following the NATIVE_POPUP_LOV items, I see 2 processes.
1- Rewrite SQL to: ...
2- Fallback to legacy LOV support. Please check your SQL statement.
I have a question regarding the second process. What does it do? What do I have to modify in my SQL statement to avoid the "*Fallback to legacy LOV support*"?
Note: I am using the table function in my SQL statement.
Louis-Guillaume
http://www.lgcarrier.com
http://www.apexframework.com

Hi Patrick,
The LOV SQL statement is based on a table function. I am using aliases on my 2 columns. I can edit the page item without error. I didn't check the page with Advisor.
Example of the query:
select dimns_name d,
dimns_value r
from table(my_pkg.get_lov_dimns('param1','param2','param3','param4'))
When using table function to generate my data, I can't use the search functionnality of the popup lov item. The search returns zero rows. I went into the v$sqlarea table to make sure that my query is executed. And it is executed.
Thanks.
Louis-Guillaume Carrier-Bédard
http://www.lgcarrier.com
http://www.apexquebec.com
http://www.apexframework.com
Edited by: Louis-Guillaume on Feb 2, 2011 2:32 PM

Similar Messages

NWDS debug mode can only be supported by one client ?

Hi all.
We are 4 persons who are developing webdynpro application together.
However, when we are using NWDS debug mode, we found that only one client debug is supported, when the second person want to debug, the first person have to exit debug mode.
Can WAS support for more debug mode ?

Hi Jianhong,
Right now you have only one instance of your server,so only one debug port is available.Hence only one person at a time can debug.
If you need to debug in development environment with more people then you have to create as many instance of server as you need.
Recently i have seen some forum/webblog here about it.

Devloper system configuration (weblogic in debug mode on Eclipse/windows)

Hi,
I work on a project, which we may consider as big. Couple of thousads of java files, muilti-tired. We use, weblogic in eclipse on widows for development. Curreltly we have 1G ram on each of developer mechines. But most of us are complaining that, system is running slow in debug mode. Sometimes, we can't even work.
I greatly appreciate if somebody can point me to the URL or suggestion for good system configuration, so that we can work comfortably.
Just asking to increase the RAM may not help me in convencing the business/management. If there any specific recommandations by either by BEA or IBM (eclipse), that helps me a lot in raising the same to our buisness.
Greatly appricate your suggestions
Reg,
Mahi

Hi Bigmachini,
According to my solution, what about your issue now?
If you have been solved the issue, would you mind sharing us the solution here? So it would be helpful for other members who get the same issue.
If not, please let us know the latest information about it.
@Malik, could you please tell me if you try to check your issue by the above suggestion as I said?
If no, please try the above suggestions to check this issue and then tell me the latest message about this issue.
>>The error mostly occurs when debugging ADO.NET or database function calls. If code is run without debugging then there is no issue at all.
You could also try to copy your project and then debug your project in debug mode on a another machine you install same Windows 10 OS check this issue again.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Project runs Ok in debug mode but not in release mode

I have an application developed with VC++ 6.0 and measurement studio. The application controls SCXI-1161/1166 relay boards to connect the UUT. The application runs ok in debug mode, but in release mode the application can't drive the relay boards. I have tried to change optimizations mode, it didn't work. Who can tell me how to solve the problem? Thanks!

It sounds like you have an older version of our SWITCH driver which relies on our DAQ driver. I would recommend uninstalling the Traditional DAQ, DAQmx, and SWITCH drivers and then installing the newest version. At this point you have 2 options:
1) You can download Traditional DAQ 7.4, DAQmx 7.4, and NI-SWITCH 2.4 drivers bundled together here: ftp://ftp.ni.com/support/daq/pc/ni-daq/7.4/
2) You can install the latest version: NI-DAQmx 7.5 here: http://digital.ni.com/softlib.nsf/websearch/CF7ECCEA4C4CC7DE86257038004D88AE?opendocument&node=13206... This has support for all of our USB DAQ devices (if you're not using them then you may not want to worry about installing this now) and then install Traditional DAQ 7.4 here: http://digital.ni.com/softlib.nsf/websearch/C36A54ADDA3DC33D86257038004E55E6?opendocument&node=13206... and NI-SWITCH 2.4 here: http://digital.ni.com/softlib.nsf/websearch/9D6B8C7FD41BF3D08625702E0072E294?opendocument&node=13206...
This should solve your problem.

Lm3s8962 cannot enter debug mode

Hello,
I am developing an application on my luminary lm3s8962 with labview for ARM, I have an home made PCB with this ARM and sensors.
I have 2 PCB's of the same.
My problem is,
instead of a 8 MHz crystal I have a 8 MHz oscillator (single ended) so I see that my RTC is not good, I can see this with GPS timing.
but using timer0 with interval 1 sec and update a counter works good!?
I tried to make some changes in the startup file with the clock configuration:
        ; set the system clock to run at 50 MHz
        ; SysCtlClockSet(SYSCTL_SYSDIV_4 | SYSCTL_USE_PLL |
        ;                SYSCTL_XTAL_8MHZ | SYSCTL_OSC_MAIN);
        LDR        R0, =0x01C00380
        BL        SysCtlClockSet
Looking in the SysCTL I see other crystal values, like 16 MHz. used value: #define SYSCTL_RCC_XTAL_16MHZ   0x00000540 // 16.0 MHz (USB), instead of 0x380
I know this is not supported, but I want it to give it a try.
I build it and flash it, but now my debugger says:
Cannot enter memory and cannot enter debug mode.
I did some reading on the internet and it says that because 16 MHz is not supported it goes into deep sleep.
I don't know if this true..
My other PCB works fine, this one is not flashed with the wrong clock.
my question is:
first priority:
Can I prevent that my program starts up in my arm, so I can flash it with the good clock configuration. OR
Can I erase the flash (with out ULINK2) in some way, so that no program starts up and I can flash my ARM.
second priority:
Maybe someone knows how I can get the right RTC with my 8 MHz oscillator, I need a correct clock in ms.
Thank you in advance,
Wouter
Wouter.
"LabVIEW for ARM guru and bug destroyer"

Hi Wouter,
The questions about the flashing can be found via the following link.
http://www.keil.com/support/man/docs/ulink2/ulink2_su_flashdownloadcfg.htm
(right click on the target and click on Show Keil uVision)
About the hardware configuration you can better ask uVision, since they know more about Hardware.
Maybe this link helps.
http://www.keil.com/support/man/docs/rlarm/rlarm_ar_config.htm
Regards,
Bas van Dijke
NI Netherlands

Running AMIE in debug mode

How is it possible to activate debug mode for AMIE (Asset Management Integration Engine) ?

davidcacioli,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Weblogic service pack 4 debug mode, for remote debugging

Hi there,
I am using WebLogic Enterprise 5.1 Service Pack 4 on NT. I would
like to launch it in debug mode, so that I can debug some EJBs
using JBuilder4. JBuilder supports WL SP 4 only.
I installed JPDA and it is in path. When I try this command:
java
-ms64m
-mx64m
-classpath d:\weblogic\lib\weblogic510sp4boot.jar;.\classes\boot;
.\eval\cloudscape\lib\cloudscape.jar;
-Dweblogic.class.path=d:\weblogic\lib\weblogic510sp4.jar;.\lib\weblogicaux.jar;
.\license;.\classes;.\myserver\serverclasses;d:\weblogic\lib\jConnect.jar
-Dweblogic.home=.
-Djava.security.manager
-Djava.security.policy==.\weblogic.policy
-Xdebug
-Xnoagent
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=7001,suspend=y,server=y
weblogic.Server
the process hangs and nothing happens.
I included other newsgroup postings on the same subject below.
Thanks,
Ramesh
Subject: Re: Remote Debugging with WLE (JPDA)
Date: Wed, 16 Aug 2000 08:54:36 -0300
From: Wendell MacKenzie <[email protected]>
Newsgroups: weblogic.developer.interest.weblogicenterprise
I made a mistake. BEA's JavaServer DOES NOT today support the
JPDA debugger platform. Only the "old" Sun one which uses the agent
password stuff.
Sorry to have mislead you.
unless of course a BEA WLE guru in engineering has a trick that
allows this to work...?
Wendell MacKenzie wrote:
This works under Solaris7 using jpda1_0.
LD_LIBRARY_PATH=/opt/wle/5.1/lib:/usr/Solaris_JDK_1.2.2_05a/jre/lib/sparc:/usr/jpda1_0/lib/sparc>
export LD_LIBRARY_PATH
edit according to your host's installation dirs
get the startup args to your JavaServer's boot requirementsvia:
>
tmboot -n -d1 -i <ID> (where ID is the numeric id ofthe Java Server you want
to debug)
and then launch the process from the shell as in:
JavaServer -C dom=<DOMAIN> -i 6 -i 81 -u nodename -U<ULOG_PATH_PREFIX> -m 0
-A --
-Xbootclasspath:/usr/Solaris_JDK_1.2.2_05a/lib/tools.jar:/usr/Solaris_JDK_1.2.2_05a/jre/lib/rt.jar
-Xrunjdwp:transport=dt_socket,address=<PORT>,server=y,suspend=n-Xdebug
<SERVERIMPL>.jar <SERVER_SPECIFIC_ARGS>
Change each <XXXXX> as appropriate for your configuration.
Be sure to check your ULOG for the password generated, you'llneed it when
you launch your client
that will connect to the Java server at debug time.
Hope this helps.
Wendell
Scott Jones wrote:
Help,
Need to information on connecting TogetherJ or VisualCafe
to WLE. I have
been told to install JavaTM Platform Debugger Architecture,version 1.0
(JPDA 1.0).
Has anyone done this?
Any pointers,
Thanks,
[email protected]

WLE does not have service packs, you must be using WLS - you should post this in a WLS newsgroup. WLE
and WLS are 2 separate products.
Ramesh Babu wrote:
Hi there,
I am using WebLogic Enterprise 5.1 Service Pack 4 on NT. I would
like to launch it in debug mode, so that I can debug some EJBs
using JBuilder4. JBuilder supports WL SP 4 only.
I installed JPDA and it is in path. When I try this command:
java
-ms64m
-mx64m
-classpath d:\weblogic\lib\weblogic510sp4boot.jar;.\classes\boot;
.\eval\cloudscape\lib\cloudscape.jar;
-Dweblogic.class.path=d:\weblogic\lib\weblogic510sp4.jar;.\lib\weblogicaux.jar;
.\license;.\classes;.\myserver\serverclasses;d:\weblogic\lib\jConnect.jar
-Dweblogic.home=.
-Djava.security.manager
-Djava.security.policy==.\weblogic.policy
-Xdebug
-Xnoagent
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=7001,suspend=y,server=y
weblogic.Server
the process hangs and nothing happens.
I included other newsgroup postings on the same subject below.
Thanks,
Ramesh
Subject: Re: Remote Debugging with WLE (JPDA)
Date: Wed, 16 Aug 2000 08:54:36 -0300
From: Wendell MacKenzie <[email protected]>
Newsgroups: weblogic.developer.interest.weblogicenterprise
I made a mistake. BEA's JavaServer DOES NOT today support the
JPDA debugger platform. Only the "old" Sun one which uses the agent
password stuff.
Sorry to have mislead you.
unless of course a BEA WLE guru in engineering has a trick that
allows this to work...?
Wendell MacKenzie wrote:
This works under Solaris7 using jpda1_0.
LD_LIBRARY_PATH=/opt/wle/5.1/lib:/usr/Solaris_JDK_1.2.2_05a/jre/lib/sparc:/usr/jpda1_0/lib/sparc
export LD_LIBRARY_PATH
edit according to your host's installation dirs
get the startup args to your JavaServer's boot requirementsvia:
tmboot -n -d1 -i <ID> (where ID is the numeric id ofthe Java Server you want
to debug)
and then launch the process from the shell as in:
JavaServer -C dom=<DOMAIN> -i 6 -i 81 -u nodename -U<ULOG_PATH_PREFIX> -m 0
-A --
-Xbootclasspath:/usr/Solaris_JDK_1.2.2_05a/lib/tools.jar:/usr/Solaris_JDK_1.2.2_05a/jre/lib/rt.jar
-Xrunjdwp:transport=dt_socket,address=<PORT>,server=y,suspend=n-Xdebug
<SERVERIMPL>.jar <SERVER_SPECIFIC_ARGS>
Change each <XXXXX> as appropriate for your configuration.
Be sure to check your ULOG for the password generated, you'llneed it when
you launch your client
that will connect to the Java server at debug time.
Hope this helps.
Wendell
Scott Jones wrote:
Help,
Need to information on connecting TogetherJ or VisualCafe
to WLE. I have
been told to install JavaTM Platform Debugger Architecture,version 1.0
(JPDA 1.0).
Has anyone done this?
Any pointers,
Thanks,
[email protected]

Building to Devices in Debug mode, Error.

Hi All,
We are having an issue building my app in Debug mode to my physical devices, the error is posted below.
The device is dev unlocked and was working, but stopped with no warning. We can still work on the emulator and build in release mode to the device.
We have tried:
Reassociating it with the Windows Phone store.
Cleaning the solution.
Deleting obj and bin folders.
Rebuilding solutions
Running VS in admin mode.
Restarting the system.
Does anyone please have advice on how to resolve this issue as it is hurting our beta testing.
Error:
"Unable to activate Windows Store app 'App Name'. The Process started, but the activation request failed with error 'The app didn't start'"

Hi Tyroneallen281,
I found there is one similar question about the same problem. Please try the solution and let me know the result.
https://social.msdn.microsoft.com/Forums/en-US/fd4163fe-41c1-4c23-bc8d-be20cc5a70c3/error-code-the-app-didnt-start?forum=winappswithcsharp.
If it doesn’t work, please post more information about your scenario.
Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate
the survey.

VS2013 not running in debug mode on Windows 10 Technical Preview Build 10041

am getting the following errors every time i try to run my projects in debug mode what can be the issue.
Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem in 'C:\Program Files (x86)\IIS Express\iisexpress.exe'.
Additional information: The runtime has encountered a fatal error. The address of the error was at 0x73c0d5a5, on thread 0x1a0c. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user
code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.
Then when I continue the following appears
An unhandled exception of type 'System.AccessViolationException' occurred in System.Data.dll
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Then it stops..
This happens when a database call is made and only does this when debug, when I run it using the browser link all is good. The applications work well.

Hi Bigmachini,
According to my solution, what about your issue now?
If you have been solved the issue, would you mind sharing us the solution here? So it would be helpful for other members who get the same issue.
If not, please let us know the latest information about it.
@Malik, could you please tell me if you try to check your issue by the above suggestion as I said?
If no, please try the above suggestions to check this issue and then tell me the latest message about this issue.
>>The error mostly occurs when debugging ADO.NET or database function calls. If code is run without debugging then there is no issue at all.
You could also try to copy your project and then debug your project in debug mode on a another machine you install same Windows 10 OS check this issue again.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Problem connecting to Realtime system to download or run in debug mode

I have updated my LabWindows\CVI to 2013. I have a PXI system with a PXIe-8101 controller. The PXIe-controller has a real-time OS installed. I have been programming this system for a while now so I am not exactly a novice anymore. The first time I tried to install the program to my real-time target I got a message which said "LabWindows/CVI cannot connect to the real-time target." It also said " .... The version of the LabWindows/CVI Run-Time Engine for RT must be compatible with the version of the LabWindows/CVI development environment."
So I figured that was the problem. My next step was to go into MAX and sure enough was getting all sorts of flags and errors when I used the real-time software Wizard in MAX by right clicking on the Remote software and clicking on Add/Remove Software. And like I suspected there were several flags indicating a software differences. My next step was to update the software in my real-time target to resolve the problem. After I did that I compiled the code and installed it on my remote system. Everything seemed OK.
The following Monday I restarted LabWindows/CVI and made a couple of changes and tried to build and install to my real-time target. I get that same message as in the first paragraph. So I thought I might not have real-time system booted up correctly or something like that so I checked all of that and it looked OK. Next I opened up MAX and it could see my real-time target just fine.
When I had my LabWindows/CVI 2012 I did not have this problem. I think maybe there is some incompatibliity issues with my LabWindows 2013; has anyone had a similar problem? I am able to get around the problem by building the release version and copying it to the PXI with CuteFTP V9.0 but I cannot do run my program in debug mode with my LabWindows/CVI and if you may have noticed I have other problems which is in another post I put in next week. I am hoping the problems are connected and I can kill two birds with one stone LOL.
I appreciate any suggestions.
Thanks,
Don Pearce

Hello,
I want to make sure I'm understanding what you are doing in the LabVIEW project. According to the Getting Started with the LabWindows /CVI Real-Time Module manual, these are the steps to install software on the RT target:
1. Launch MAX.
2. Find and expand your RT target under the Remote Systems item in the MAX configuration tree, right-click Software, and select Add/Remove Software. When you select Add/Remove Software, MAX launches the LabVIEW Real-Time Software Wizard. This displays all the National Instruments software and drivers installed on the host computer that you can install on a selected RT target.
3. Select the software you want to install on the RT target, click the icon next to the software, and select Install the feature.
You need to install LabWindows/CVI Run-Time Engine for RT to add support for LabWindows/CVI RT applications on the RT target. This component is required for all LabWindows/CVI RT applications.
The forum post here solved this same issue by installing missing drivers based on this KnowledgeBase article.
Also, LabWindows/CVI 2013 SP1 has been released. Service Pack 1 (SP1) has many useful bug fixes (listed here), so I recommend upgrading to LabWindows/CVI 2013 SP1 if possible.
Taylor B.
National Instruments

[WPSL]Windows App Certification Kit Test Fails, binary is built in debug mode

Hi,
Windows phone 8.1 App fails Windows App Certification Kit test (WACK Test).
It is producing below error in Debug configuration test,
The debug configuration test detected the following errors:
1)The binary Phone.Controls.dll is built in debug mode.
Impact if not fixed: Windows Phone Store doesn’t allow a debug version of an app.
How to fix: Please make sure the app isn't linking to any debug versions of a framework and it is built with the release configuration
And i got a solution like,
Universal Apps (And Silverlight 8.1 Apps) have a different certification requirement. You cannot publish assemblies built in debug mode.
You'll need to contact the NuGet authors of ICSharpCode and ImageTools and have them provide you with a version built in release mode.
How to proceed with this solution. I'm very help full if any solution provided.
Thanks and Regards,
Ranjit.

Hi Franklin,
Thanks for your replay. I created my package in 'Release' mode only.
Actually my project in windows phone 7.1 and i upgraded it to windows phone 8.1. In "Release" mode i created my build, but i'm having this error in WACK(Windows
App Certification Kit) test.
I'm able to run my App in windows phone 8.1, but if i submit it to store then will be rejected definitely.
The debug configuration test detected the following errors:
1)The binary Phone.Controls.dll is built in debug mode.
The WACK test fails in debug configuration test, for "Phone.Controls.dll "
it is built in debug mode.
There should be a solution like, how to convert .dll to release mode.
Please help me in this.
Thanks
Ranjit.
Hi ranjit,
>>Actually my project in windows phone 7.1 and i upgraded it to windows phone 8.1
Okay, this may be due to the upgrading process, could you tell us what the detailed version of your Visual Studio is(for example: Visual Studio 2013 Update 4)?
You may need to create a new Windows Phone 8.1 Silverlight project and try to upload it to Store, if this problem can be resolved, I think this should be related to the upgrading process, you may need to start from scratch by recreating a WP8.1 SL project.
To exclude environment facts, I would also suggest you retesting it on a new machine with the latest IDE.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Help debug mode: Stops at breakpoint, but line is not highligted, no actions selectable

I just reinstalled Pydev and now debug mode no longer works.
I run a program in debug mode. Without a breakpoint, the program runs through. When I set a breakpoint, the program pauses, as it should, but the code line is not highlighted. This also means that none of the debug actions are selectable (step into, etc.), although they are visible. I only have one breakpoint.
The 'debug' option (next to pydev and java options) is selected.

On 08/09/2015 02:31 PM, ttt bbb wrote:
> I just reinstalled Pydev and now debug mode no longer works.
>
> I run a program in debug mode. Without a breakpoint, the program runs
> through. When I set a breakpoint, the program pauses, as it should, but
> the code line is not highlighted. This also means that none of the debug
> actions are selectable (step into, etc.), although they are visible. I
> only have one breakpoint.
>
> The 'debug' option (next to pydev and java options) is selected.
Unfortunately, PyDev isn't Eclipse. It's a set of third-party plug-ins
you'll have to get support for in another forum.

Error when starting Weblogic in debug mode

Hi there
Has anyone experienced any difficulties when starting weblogic in debug mode.
More specifically, it cannot start correctly because it thinks that another instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unable to create
a server socket for port: 8320. java.net.BindException: Address already in use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <The WebLogic
Server is no longer listening for connections. You should probably restart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Server shutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdown sequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Server shutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unable to load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)

Thanks for the suggestion.
Unfortunatley the port is definately free/available during startup.
Stephane Kergozien <[email protected]> wrote:
Maark,
Before starting your server, please could you check that the port is
not used by one
other process. You can use the netstat command to do this.
Regards
Stephane
Mark wrote:
Hi there
Has anyone experienced any difficulties when starting weblogic in debugmode.
More specifically, it cannot start correctly because it thinks thatanother instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unableto create
a server socket for port: 8320. java.net.BindException: Address alreadyin use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <TheWebLogic
Server is no longer listening for connections. You should probablyrestart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Servershutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdownsequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Servershutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unableto load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)--
Regards,
Stephane Kergozien
BEA Support

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

Can not view contents of variable in debug mode (version 1.1.1.5.0)

Hi
I am running on WebLogic 11R1 and using OEPE 1.1.1.5.0.
When Fast swap is enabled and I run WebLogic in debug mode using OEPE I can not view the contents of variables with the Eclipse debugger. I get the message "Expressions must contain either an expression or a block containing a well formed statement"
However, if I disable Fast swap, i can view the variable within the Eclipse debugger
Has anyone else had this problem?
Regards
Steve H

Small correction... the soon-to-be-released version of WebLogic Server that Danny was referring to is 11gR1 PatchSet 2 or 10.3.3.

Debug mode - NATIVE_POPUP_LOV - Fallback to legacy LOV support.

Similar Messages

Maybe you are looking for