'signal' in forte

Have a look at the ExternalRef class. This class allows you to cleanup
resources when a partition shutsdown for whatever reason (failure or
e-console).
It is primarily used for closing connections to external programs but we use
it to free named anchored objects as well
Be aware that there can be limits to what you can do when this class is
called. In the event of a failure of the partition a service object may not
be in a valid state. It is probably best to have a subclass of ExternalRef
completely manage the resource you want to free. That way you do not rely
on other service classes being available.
Cheers
David McPaul
Lumley Technology
-----Original Message-----
From: Shahnawaz Mohammed [mailto:smohammehomeaccount.com]
Sent: Thursday, April 27, 2000 4:20 AM
To: forte
Subject: (forte-users) 'signal' in forte
Hi All,
Is there a way some kind of 'signal' be detected by a program when it is
brought down through env console. I have to do some cleanup whenever a
program is brought down. Any comments or help is appreciated.
Thanks
Shahnawaz
Software Engineer
Home Account Network Inc
Phone (843) 805-5259
Fax (843) 722-7082
http://www.homeaccount.com <<a
href=
"http://www.homeaccount.com">http://www.homeaccount.com</a>>
This e-mail message has been scanned and cleared by MailMarshal
http://www.marshalsoftware.com
######################################################################

Similar Messages

Forte's benchmark

Hi,
I'm looking for some benckmarks of Forte architecture
on 2-tier and 3-tier C/S.
And where can I find articles or whitepapers about
load balancing and transactional locking in Forte.
Many thanks
Herve
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

George,
I'm rusty with Forte and I'm not sure about signals on Solaris
but the mention of threads on Solaris brought to mind a couple
points that you should know. This was true as far as I can
tell in 3.0.E.0 on Solaris 2.6.
1. By default in interpreted partitions FTEXEC does not use
solaris threads, it uses Forte threads. You must tell it
to use DCE threads.
Once you're in the partition workshop you can bring up the
partition properties for the server partition that you want
Sun threads for. In the properties dialog there is an option
called "Thread Package". If you choose DCE then it'll use
Sun threads.
2. Compiled partitions require yet another trick.
You must add the flag "-tlpt" which I believe stands
for "thread library posix threads", meaning DCE threads,
meaning native threads.
Turn on trace flag "trc:os:14" on your Solaris box before
starting up the compiled partiton. This will show all
the shared libraries getting loaded into the partition.
install/lib/libqqptli.so is the posix thread library.
Regards, and good luck.
[email protected]
Hi there,
Could somebody please tell me which signals does Forte use to
schedule thread-switching on Solaris 2.5? or does Forte catch
the following two signals, SIGSEGV and SIGBUS?
Thanks a lot.
George
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>------------------------------------------------------------------------
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
Reuters Ltd.
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Signal ILL trying to debug java process with dbx

Hello,
I'm trying to debug a java process to find an error in JNI code. I get this message when dbx stops in a C breakpoint:
t@18 (l@19) signal ILL (illegal trap) in (unknown) t@18 (l@19) signal ILL (illegal trap) in (unknown) at 0xf848ed28
0xf848ed28:     tne     0x12This signal is not launched when running application without debugger, and after launching this exception and exiting dbx, the java process generates a core.
I've tried to find out unsuccessfully whether my dbx version is compatible with my Java version, but it seems this could be the problem.
This is my current configuration:
java �version:
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode)
opt/SUNWspro/bin/version:
Machine hardware:   sun4u
OS version:         5.8
Processor type:     sparc
Hardware:           SUNW,Sun-Blade-2500
The following components are installed on your system:
Forte C++ 6 update 2
        Sun WorkShop 6 update 2 Compilers C
        Sun WorkShop 6 update 2 Compilers C++
        Sun WorkShop 6 update 2 Tools.h++ 7.1
        Sun WorkShop 6 update 2 Standard 64-bit Class Library for C++
        Sun WorkShop 6 update 2 Memory Monitor for C++
        Sun WorkShop 6 update 2 Visual
        Sun WorkShop 6 update 2 Development Environment
        Sun WorkShop 6 update 2 TeamWare
        Sun WorkShop 6 update 2 FileMerge
        Sun WorkShop 6 update 2 DBX Debugging Tools
        Sun WorkShop 6 update 2 Performance Analyzer
        Sun WorkShop 6 update 2 LockLint
        XEmacs 20.4 Source Distribution
        Sun WorkShop 6 update 2 Documentation Set
Sun WorkShop 6 update 2 Building SoftwareAnd this is how I launch java application:
java -Djava.compiler=NONE -Xdebug -Xnoagent -Xrundbx_agent -jar jarname.jar -mainOptionsDid I miss something important? Does anyone know if it is possible debugging with this configuration?
Best Regards,
Alberto

- Native code has been compiled with -g option.
- It fails in my code, but only when debugging.
- Stack trace (executing "where" in dbx):
(dbx) where
current thread: t@18
[1] 0xf848ef68(0xf01537d8, 0xf443b7b0, 0x0, 0xf84181b0, 0x21e9, 0xef581050), at 0xf848ef68
[2] 0xf8458354(0xf15faea8, 0xf01537d8, 0xf0151a88, 0xf8419368, 0x21e8, 0x0), at 0xf8458354
[3] 0xf848c9a0(0xf15faea8, 0xf01537d8, 0xf0151a58, 0xf0151a38, 0xf0153830, 0x0), at 0xf848c9a0
[4] 0xf84577c8(0xf15faea8, 0xb6, 0x0, 0xf84181b0, 0xf0158f80, 0xef581118), at 0xf84577c8
[5] 0xf8405764(0xf15faea8, 0xb6, 0x0, 0xf8419320, 0xf0158f80, 0xef5811c8), at 0xf8405764
[6] 0xf8405764(0xf15faea8, 0xb6, 0x0, 0xf84195a0, 0xf0158f80, 0xef581250), at 0xf8405764
[7] 0xf8405764(0xf0151a38, 0xb8, 0x0, 0xf8419320, 0xf0125258, 0xef5812d8), at 0xf8405764
[8] 0xf8405874(0xf15fb6c8, 0xb8, 0x0, 0xf8419720, 0xf0125258, 0xef581360), at 0xf8405874
[9] 0xf8405764(0xf15fae98, 0xb6, 0x0, 0xf8419770, 0xf00f0088, 0xef5813f0), at 0xf8405764
[10] 0xf8405874(0xf15fae98, 0xb6, 0x0, 0xf8419320, 0x1465, 0xef581478), at 0xf8405874
[11] 0xf8405874(0xf16315b0, 0xb6, 0x0, 0xf8419320, 0xf00f0088, 0xef581500), at 0xf8405874
[12] 0xf8405764(0xf16315b0, 0xf45744c0, 0x0, 0xf8419320, 0xf45744c0, 0xef581588), at 0xf8405764
[13] 0xf8405c2c(0xf16315d0, 0xb7, 0x0, 0xf84198a0, 0xf00f0088, 0xef581618), at 0xf8405c2c
[14] 0xf8405764(0xf009c018, 0xf402c8b8, 0x0, 0xf84195a0, 0x8800, 0xef5816a8), at 0xf8405764
[15] 0xf8405c2c(0x2000, 0x2, 0x0, 0xf84198f0, 0xef50e0f8, 0xef581720), at 0xf8405c2c
[16] 0xf8400218(0xef581808, 0xef581a08, 0xa, 0xf402dae8, 0xf840ba20, 0xef581920), at 0xf8400218
[17] JavaCalls::call_helper(0x1, 0x65d188, 0xef581918, 0xef581818, 0x4, 0xef581a08), at 0xfdd9a808
[18] JavaCalls::call_virtual(0x7a9c, 0x65d188, 0x3570f8, 0x357104, 0x357100, 0xf00bc770), at 0xfdec319c
[19] thread_entry(0xf402fc58, 0x65d188, 0x3574e4, 0xfe424640, 0xfe424710, 0xfe424130), at 0xfdee2700
[20] JavaThread::run(0x65d188, 0x18, 0xfe40c790, 0x6c00, 0x7dd4, 0x7c00), at 0xfdede29c
[21] _start(0x65d188, 0x3b62, 0xfe3be000, 0x0, 0x4f24, 0x4c00), at 0xfe264240 - Stack trace (obtained from core generated after ILL signal):
----------------- lwp# 19 / thread# 18 --------------------
ff3791f0 __sigprocmask (ff37b7f4, 0, 0, ef581d98, ff38c000, 0) + 8
ff36dd0c _sigon   (ef581d98, ff3938a8, 6, ef58083c, ef581d98, ff39321c) + d0
ff370d4c _thrp_kill (0, 12, 6, ff38c000, 12, ff2c0458) + f8
ff24bce0 raise    (6, 0, 0, ffffffff, ff2c03c4, 8400) + 40
ff235984 abort    (ff2bc008, fe3be000, fe26a8e0, fe4133c4, 0, 331c8) + 100
fe264724 __1cCosFabort6Fi_v_ (1, 0, fe3f2614, fe3be000, 73b4, 7000) + 58
fe2f08f0 __1cHVMErrorOreport_and_die6M_v_ (0, fe419ad8, fe41339c, 1, fe268a14, fe41339c) + c84
fde76878 JVM_handle_solaris_signal (4, ef580fd8, ef580d20, 7800, 11, 65d188) + aac
ff37b118 __sighndlr (4, ef580fd8, ef580d20, fde75d94, ef581e40, ef581e30) + c
ff37811c sigacthandler (4, ef581d98, 0, 0, 0, ff38c000) + 708
--- called from signal handler with signal 4 (SIGILL) ---
f848ef68 ???????? (f15faea8, f01537d8, f0151a88, f8419368, 21e8, 0)
f848c9a0 ???????? (f15faea8, f01537d8, f0151a58, f0151a38, f0153830, 0)
f84577c8 ???????? (f15faea8, b6, 0, f84181b0, f0158f80, ef581118)
f8405764 ???????? (f15faea8, b6, 0, f8419320, f0158f80, ef5811c8)
f8405764 ???????? (f15faea8, b6, 0, f84195a0, f0158f80, ef581250)
f8405764 ???????? (f0151a38, b8, 0, f8419320, f0125258, ef5812d8)
f8405874 ???????? (f15fb6c8, b8, 0, f8419720, f0125258, ef581360)
f8405764 ???????? (f15fae98, b6, 0, f8419770, f00f0088, ef5813f0)
f8405874 ???????? (f15fae98, b6, 0, f8419320, 1465, ef581478)
f8405874 ???????? (f16315b0, b6, 0, f8419320, f00f0088, ef581500)
f8405764 ???????? (f16315b0, f45744c0, 0, f8419320, f45744c0, ef581588)
f8405c2c ???????? (f16315d0, b7, 0, f84198a0, f00f0088, ef581618)
f8405764 ???????? (f009c018, f402c8b8, 0, f84195a0, 8800, ef5816a8)
f8405c2c ???????? (2000, 2, 0, f84198f0, ef50e0f8, ef581720)
f8400218 ???????? (ef581808, ef581a08, a, f402dae8, f840ba20, ef581920)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 65d188, ef581918, ef581818, 4, ef581a08) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 65d188, 3570f8, 357104, 357100, f00bc770) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 65d188, 3574e4, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (65d188, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (65d188, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (65d188, 0, 0, 0, 0, 0) + 40
----------------- lwp# 20 / thread# 19 --------------------
ff29f474 _lwp_sema_wait (ff3934c8, ff392e40, 0, 1, 0, 0) + c
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 21 --------------------------------
ff379200 private___lwp_cond_wait (fa5a3d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa5a3d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 22 --------------------------------
ff379200 private___lwp_cond_wait (fa4d3d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa4d3d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 23 --------------------------------
ff379200 private___lwp_cond_wait (fa4c3d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa4c3d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 24 --------------------------------
ff379200 private___lwp_cond_wait (fa493d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa493d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 25 --------------------------------
ff379200 private___lwp_cond_wait (fa483d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa483d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 26 --------------------------------
ff379200 private___lwp_cond_wait (fa473d98, ff38cd6c, ff38c000, 3, ff38c000, 1) + 8
ff36a358 _lwp_start (fa473d98, 0, 4000, fb28162c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 1 / thread# 1 --------------------
ff29d600 _poll    (fe4124d8, 0, 1, 18e, 37020, fe3be000) + 8
fdd90cd0 __1cCosFsleep6FpnGThread_xi_i_ (6e58, 6c00, fdf04534, 1, 7, 4) + 25c
fdf0ca4c JVM_Sleep (1c08, fe406e44, 37020, fe412d84, 38680, fe3be000) + 260
f840e22c ???????? (b9, ffbee73c, ffbee6b8, ffffff80, 0, 0)
f840e1d0 ???????? (0, b8, 0, 8, f402fc58, ffbee6d0)
f8405764 ???????? (f15996c8, fe4163d4, 0, f8419770, 8800, ffbee768)
f8405764 ???????? (f01778f8, fe4163d4, 0, f8419370, 8800, ffbee820)
f8405764 ???????? (2000, 2, 0, f8419320, ffb7c110, ffbee8b8)
f8400218 ???????? (ffbee9a0, ffbeeb00, a, f41c4038, f840ba20, ffbeea88)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 37020, ffbeea80, ffbee9b0, 4, ffbeeb00) + 5a0
fdedea14 jni_CallStaticVoidMethod (fe412d84, 381ec, 36750, 37020, 36748, 37cb8) + 500
000121fc main     (38648, 1e7fa2, fe40a630, 1d8, fded413c, 1) + 115c
00011088 _start   (0, 0, 0, 0, 0, 0) + 108
----------------- lwp# 2 / thread# 2 --------------------
ff29edc4 _signotifywait (ff38c000, 0, 0, 0, 0, 0) + 8
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 3 --------------------------------
ff379200 private___lwp_cond_wait (ff325d98, ff38cd6c, ff38c000, 0, 0, 4) + 8
ff29c9c0 _door_return (ff325cd8, ff36a358, 0, 0, 0, 0) + 68
----------------- lwp# 4 / thread# 4 --------------------
ff29f428 ___lwp_cond_wait (35d68, 35d50, fdb81978, 0, 0, fdb81970) + 8
ff296a7c _lwp_cond_timedwait (2958790, 44b36755, fdb81a50, 35d50, 35d68, a95a) + 98
fddc3258 __1cHMonitorEwait6Mil_i_ (35cf8, 11dce0, fff0bc00, fe3be000, 6000, 35d28) + 328
fdf6b4fc __1cIVMThreadDrun6M_v_ (fe4124d8, fe420c84, 0, fe420c70, fe420c80, 1) + 1b4
fe264240 __1cG_start6Fpv_0_ (11dce0, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (11dce0, 0, 0, 0, 0, 0) + 40
----------------- lwp# 5 --------------------------------
ff29c968 _door_return (4, ff38d658, ff38d670, 3, ff38c000, 1) + 10
ff36a358 _lwp_start (fe785d98, 0, 6000, ff325b9c, 0, 0) + 18
ff371c2c thr_yield (0, 0, 0, 0, 0, 0) + 8c
----------------- lwp# 6 / thread# 5 --------------------
ff29f428 ___lwp_cond_wait (120148, 120130, 0, ff2968f0, 0, 1) + 8
fdeb4768 __1cNObjectMonitorEwait6MxipnGThread__v_ (120370, 9408, 8c00, fe3be000, 11fdc0, 120390) + 59c
fdeb5978 __1cSObjectSynchronizerEwait6FnGHandle_xpnGThread__v_ (120372, 86d4, 0, 11fdc0, 8400, fe3be000) + e8
fdeb5628 JVM_MonitorWait (0, e7a14, 11fdc0, fe412d84, 0, 1) + 31c
f840e22c ???????? (51, fda816ec, fda81670, ffffff80, fdd2e808, 0)
f840e1d0 ???????? (f15817e0, b6, 0, c, 0, fda81688)
f8405764 ???????? (f15817e0, b6, 0, f8419354, 80000000, fda81708)
f8405764 ???????? (0, fe411508, 0, f8419770, 7bac, fda817a0)
f8400218 ???????? (fda81888, fda81a88, a, f40901d0, f840ba20, fda819a0)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 11fdc0, fda81998, fda81898, 4, fda81a88) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 11fdc0, e7a00, e7a0c, e7a08, f0000760) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 11fdc0, e7dec, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (11fdc0, 0, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (11fdc0, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (11fdc0, 0, 0, 0, 0, 0) + 40
----------------- lwp# 7 / thread# 6 --------------------
ff29f428 ___lwp_cond_wait (121cc8, 121cb0, 0, ff2968f0, 0, 1) + 8
fdeb4768 __1cNObjectMonitorEwait6MxipnGThread__v_ (1203b8, 9408, 8c00, fe3be000, 121530, 1203d8) + 59c
fdeb5978 __1cSObjectSynchronizerEwait6FnGHandle_xpnGThread__v_ (1203ba, 86d4, 0, 121530, 8400, fe3be000) + e8
fdeb5628 JVM_MonitorWait (0, 121714, 121530, fe412d84, 0, 1) + 31c
f840e22c ???????? (59, fb3817ec, fb381768, ffffff80, 0, 0)
f840e1d0 ???????? (f1581760, b6, 0, c, 80000000, fb381780)
f8405764 ???????? (f1581768, b6, 0, f8419354, 8800, fb381820)
f8405874 ???????? (f1581768, b6, 0, f8419354, f402af58, fb3818a0)
f8405874 ???????? (0, fe411508, 0, f8419720, 7bac, fb381920)
f8400218 ???????? (fb381a08, fb381c08, a, f4090ab8, f840ba20, fb381b20)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 121530, fb381b18, fb381a18, 4, fb381c08) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 121530, 121700, 12170c, 121708, f0000858) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 121530, 121aec, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (121530, 0, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (121530, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (121530, 0, 0, 0, 0, 0) + 40
----------------- lwp# 8 / thread# 7 --------------------
ff29f428 ___lwp_cond_wait (1b65f0, 1b65d8, fb281890, ff296918, ff29691c, fb281888) + 8
ff296a7c _lwp_cond_timedwait (2964ae0, 44b36756, fb281910, 1b65d8, 1b65f0, 153180) + 98
fe2606e0 __1cCosHSolarisFEventEpark6Mx_i_ (1b65b0, 6a60, fe4238d8, 1b65f0, fe406ef0, fb281910) + 1bc
fe25ff28 __1cNObjectMonitorIraw_wait6MxipnGThread__i_ (1b65b0, fe214b70, 7bac, 0, 1b59e8, 12a188) + 20c
fe1f4b8c __1cIJvmtiEnvORawMonitorWait6MpnPJvmtiRawMonitor_x_nKjvmtiError__ (fb2, 12a188, 0, 7d0, 4, 1b59e8) + a8
fe7d87ec process_next_event (fe40b864, 10000, fe7f24a0, fe7f4b90, fe7f25f0, fe7f25ec) + 108
fe7c7630 agent_bar (1b5aa4, fe7f2ae8, ff38c000, fe7f24c8, 0, 0) + 1c
fe7c7bc4 jvmti_debug_agent (fe7f2400, 1b5aa4, 0, 1678, 1, fe7f252c) + d4
fe211c74 __1cQJvmtiAgentThreadTcall_start_function6M_v_ (1b59e8, 7800, 8c94, fe3be000, fe4123c4, fe4163d4) + 150
fdede29c __1cKJavaThreadDrun6M_v_ (1b59e8, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1b59e8, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1b59e8, 0, 0, 0, 0, 0) + 40
----------------- lwp# 9 / thread# 8 --------------------
ff29f474 _lwp_sema_wait (fb181e60, ff38c000, 0, fb181d98, 0, 0) + c
ff3690d8 _swtch   (fb181d98, ffffffff, ff38c000, 5, 1000, fe4170c4) + 158
ff36c860 sema_wait (fe4217e8, ff39785c, 5000, 10000, 534d, 1) + bc
fdf61dc0 __1cVcheck_pending_signals6Fi_i_ (1, fe4124d8, fe4123c0, 1b6ab8, fe3be000, a) + 254
fdf58ec8 __1cTsignal_thread_entry6FpnKJavaThread_pnGThread__v_ (7428, 1b6ab8, 1b7088, fe3be000, 4ff61c, 1b7080) + 34
fdede29c __1cKJavaThreadDrun6M_v_ (1b6ab8, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1b6ab8, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1b6ab8, 0, 0, 0, 0, 0) + 40
----------------- lwp# 10 / thread# 9 --------------------
ff29f428 ___lwp_cond_wait (36548, 36530, fe423d60, 0, 0, ff29695c) + 8
fddc33ec __1cHMonitorEwait6Mil_i_ (364d8, 1b7998, 1b8510, fe3be000, 1b7998, 36508) + 4bc
fdf35d00 __1cNCompileBrokerUcompiler_thread_loop6F_v_ (fe4124d8, 1b54c0, 1b7998, fe407360, 8c00, 364d8) + 22c
fdede29c __1cKJavaThreadDrun6M_v_ (1b7998, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1b7998, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1b7998, 0, 0, 0, 0, 0) + 40
----------------- lwp# 11 / thread# 10 --------------------
fdd0c200 __1cENodeSremove_dead_region6MpnIPhaseGVN_i_i_ (9132d4, fa6809f4, 1, 9132d4, 9132f4, 68ad00) + 2c
fdd3332c __1cHMemNodeMIdeal_common6MpnIPhaseGVN_i_pnENode__ (fa6809f4, fa6809f4, 1, 800, 9132d4, 9132f4) + 3c
fdd68a78 __1cJStoreNodeFIdeal6MpnIPhaseGVN_i_pnENode__ (9132d4, fa6809f4, 1, 0, fdd4be74, fe3fbb44) + c
fdcf887c __1cMPhaseIterGVNNtransform_old6MpnENode__2_ (fa6809f4, 9132d4, 89e938, fdd68a6c, 20000000, c7) + 28
fdde3b98 __1cMPhaseIterGVNIoptimize6M_v_ (fa6809f4, 14, 9132d4, 0, fa680b44, ffffffff) + ac
fde048d8 __1cOPhaseIdealLoop2t6MrnMPhaseIterGVN_pk0i_v_ (fa68087c, ffffffff, fa680fb0, 2, 0, fa680880) + c34
fde7fb28 __1cHCompileIOptimize6M_v_ (fa680fb0, 1b55b0, 0, 0, fe3be000, 1000) + 200
fde82740 __1cHCompile2t6MpnFciEnv_pnKC2Compiler_pnIciMethod_ii_v_ (fa680fb0, 0, 36ee0, 0, fe3384f8, fa680fb0) + be8
fde786f8 __1cKC2CompilerOcompile_method6MpnFciEnv_pnIciMethod_i_v_ (fa6818ac, fe324608, 9269b8, ffffffff, 36ee0, 1000001) + b0
fde793b4 __1cNCompileBrokerZinvoke_compiler_on_method6FpnLCompileTask__v_ (597690, 1b8eb4, 1b55b0, 1b88d8, fe338ea7, fa6818ac) + 4cc
fdf35f20 __1cNCompileBrokerUcompiler_thread_loop6F_v_ (fe4124d8, 1b5550, 1b88d8, f4368380, 1b8eb0, 0) + 44c
fdede29c __1cKJavaThreadDrun6M_v_ (1b88d8, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1b88d8, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1b88d8, 0, 0, 0, 0, 0) + 40
----------------- lwp# 12 / thread# 11 --------------------
ff29f428 ___lwp_cond_wait (365d8, 365c0, fe423d60, 0, 0, ff29695c) + 8
fddc33ec __1cHMonitorEwait6Mil_i_ (36568, 1b9818, 1ba390, fe3be000, 1b9818, 36598) + 4bc
fdf35d00 __1cNCompileBrokerUcompiler_thread_loop6F_v_ (fe4124d8, 1b5550, 1b9818, fe407360, 1b9df0, 36568) + 22c
fdede29c __1cKJavaThreadDrun6M_v_ (1b9818, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1b9818, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1b9818, 0, 0, 0, 0, 0) + 40
----------------- lwp# 13 / thread# 12 --------------------
ff29f428 ___lwp_cond_wait (34858, 34840, 1, 0, 1, 1bb248) + 8
fddc309c __1cHMonitorEwait6Mil_i_ (347e8, 1bb1a0, fff0bc00, fe3be000, f4000, 34818) + 16c
fdf64b44 __1cRLowMemoryDetectorbGlow_memory_detector_thread_entry6FpnKJavaThread_pnGThread__v_ (1bb1a0, 347e8, 9000, fe411604, fe3be000, 1) + 2ec
fdede29c __1cKJavaThreadDrun6M_v_ (1bb1a0, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (1bb1a0, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1bb1a0, 0, 0, 0, 0, 0) + 40
----------------- lwp# 14 / thread# 13 --------------------
ff29d600 _poll    (fe4124d8, 32, 0, 0, 8400, fe3be000) + 8
fdd90cd0 __1cCosFsleep6FpnGThread_xi_i_ (6e58, 6c00, 1, 0, 2, 4) + 25c
fdfa5194 __1cNWatcherThreadDrun6M_v_ (1bc4c8, 1b5460, 32, fe3be000, fe417db8, 0) + e8
fe264240 __1cG_start6Fpv_0_ (1bc4c8, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (1bc4c8, 0, 0, 0, 0, 0) + 40
----------------- lwp# 15 / thread# 14 --------------------
ff29d600 _poll    (fe4124d8, 0, 1, f1, 3baea0, fe3be000) + 8
fdd90cd0 __1cCosFsleep6FpnGThread_xi_i_ (6e58, 6c00, fdf04534, 1, 7, 4) + 25c
fdf0ca4c JVM_Sleep (ba8, fe406e44, 3baea0, fe412d84, 3bb180, fe3be000) + 260
f840e22c ???????? (c9, eff818f4, eff81870, ffffff80, f00e5250, 0)
f840e1d0 ???????? (0, b8, 0, 8, f00e5250, eff81888)
f8405764 ???????? (2000, 2, 0, f8419754, eff0e110, eff81920)
f8400218 ???????? (eff81a08, eff81c08, a, f423b868, f840ba20, eff81b20)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 3baea0, eff81b18, eff81a18, 4, eff81c08) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 3baea0, 254948, 254954, 254950, f01aaaf8) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 3baea0, 254d34, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (3baea0, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (3baea0, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (3baea0, 0, 0, 0, 0, 0) + 40
----------------- lwp# 16 / thread# 15 --------------------
ff29d600 _poll    (fe4124d8, 0, 1, f0, 358da0, fe3be000) + 8
fdd90cd0 __1cCosFsleep6FpnGThread_xi_i_ (6e58, 6c00, fdf04534, 1, 7, 4) + 25c
fdf0ca4c JVM_Sleep (368, fe406e44, 358da0, fe412d84, 358f98, fe3be000) + 260
f840e22c ???????? (91, efe81874, efe817f0, ffffff80, f00dfeb0, 0)
f840e1d0 ???????? (0, b8, 0, 8, f00dfeb0, efe81808)
f8405764 ???????? (2000, 2, 0, f8419754, efe0e110, efe818a0)
f8400218 ???????? (efe81988, efe81b88, a, f423b868, f840ba20, efe81aa0)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 358da0, efe81a98, efe81998, 4, efe81b88) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 358da0, 254d48, 254d54, 254d50, f01b4270) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 358da0, 255134, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (358da0, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (358da0, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (358da0, 0, 0, 0, 0, 0) + 40
----------------- lwp# 17 / thread# 16 --------------------
ff29d600 _poll    (fe4124d8, 0, 1, f5, 3dd8a8, fe3be000) + 8
fdd90cd0 __1cCosFsleep6FpnGThread_xi_i_ (6e58, 6c00, fdf04534, 1, 7, 4) + 25c
fdf0ca4c JVM_Sleep (1628, fe406e44, 3dd8a8, fe412d84, 3c5f98, fe3be000) + 260
f840e22c ???????? (c1, efb015fc, efb01570, ffffff80, efb, 0)
f840e1d0 ???????? (0, b8, 0, 8, 8800, efb01588)
f8405764 ???????? (2000, 2, 0, f8419770, efa8e110, efb01620)
f8400218 ???????? (efb01708, efb01908, a, f422e650, f840ba20, efb01820)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 3dd8a8, efb01818, efb01718, 4, efb01908) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 3dd8a8, 3568f8, 356904, 356900, f007a910) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 3dd8a8, 356ce4, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (3dd8a8, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (3dd8a8, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (3dd8a8, 0, 0, 0, 0, 0) + 40
----------------- lwp# 18 / thread# 17 --------------------
ff29f428 ___lwp_cond_wait (65b7a0, 65b788, ef681128, fe4123c4, ff2968f4, ef681120) + 8
ff296a7c _lwp_cond_timedwait (2ea2b88, 44b36759, ef681248, 65b788, 65b7a0, ff2969e4) + 98
fdeb4974 __1cNObjectMonitorEwait6MxipnGThread__v_ (120400, fe406ef0, fe4238d8, fe3be000, 65b550, 120420) + 7a8
fdeb5978 __1cSObjectSynchronizerEwait6FnGHandle_xpnGThread__v_ (120402, 86d4, 0, 65b550, 8400, fe3be000) + e8
fdeb5628 JVM_MonitorWait (0, 3dcdb4, 65b550, fe412d84, 0, 1) + 31c
f840e22c ???????? (91, ef6814b4, ef681430, ffffff80, ef6, 0)
f840e1d0 ???????? (f1631648, b6, 0, c, f00d7f28, ef681448)
f8405764 ???????? (f007ea58, fe4163d4, 0, f8419354, 8800, ef681508)
f8405764 ???????? (2000, 2, 0, f84195a0, ef60e110, ef6815a0)
f8400218 ???????? (ef681688, ef681888, a, f456d6b8, f840ba20, ef6817a0)
fdd9a808 __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (1, 65b550, ef681798, ef681698, 4, ef681888) + 5a0
fdec319c __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (7a9c, 65b550, 3dcda0, 3dcdac, 3dcda8, f007ea58) + 188
fdee2700 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (f402fc58, 65b550, 3dd18c, fe424640, fe424710, fe424130) + 134
fdede29c __1cKJavaThreadDrun6M_v_ (65b550, 18, fe40c790, 6c00, 7dd4, 7c00) + 1d8
fe264240 __1cG_start6Fpv_0_ (65b550, 3b62, fe3be000, 0, 4f24, 4c00) + 208
ff37b01c _thread_start (65b550, 0, 0, 0, 0, 0) + 40
-------------------------- thread# 3 --------------------
ff36d9b8 _reap_wait (ff390980, 1e924, 0, ff38c000, 0, 0) + 38
ff36d710 _reaper (ff38ce00, ff392708, ff390980, ff38cdd8, 1, fe400000) + 38
ff37b01c _thread_start (0, 0, 0, 0, 0, 0) + 40

Re: Native Language Support in Forte

[email protected] wrote:
I've been posed a question in the abstract about Forte's native language
support. Does Forte support any languages other than C/C++? And if so,
what are the limitations or caveats?
Native Language Support could also mean the NLS standard which Forte supports. This
provides for Internationalization (I18N) of a Forte application. This means a client
application deployed in french, german, and english (for example), could all be making
requests of the same Forte shared service and getting responses in the native language.
We provide for changing the language/character set displayed both statically before the
application starts, and dynamically change it while the application is running.
If support native language support means ability for Forte to call existing application
logic written in C/C++, then today you can "wrapper" C functions in a Forte Class,
instantiate the class and "call-out" to the member functions (your c functions) directly
from the 4GL object.
C++ functions are a challenge due to cross platform C++ compiler issues which at a
minimum include "name mangling" being non-standard for all the C++ compilers.
However, you can "export" C++ class member functions as external "C" functions so that C
code can call the function as if it was regular K&R or ANSI C.
If other language support is required, I have customers on the East Coast which have
successfully wrappered MicroFocus Cobol on HP-UX, and the ADA language. This is due to
the concept of all 3GL languages today support the concept of allowing for their
language to be called from 'C' (other possibilities are Pascal, Fortran, etc).
Here the only caveat is you need to be aware of the other language's "boot-code" may be
registering for operating system "signals" and not handling them appropriately. This
rarely is an issue these days.
If other language support means do we code generate our 4GL language to any language
other than 'C++', the answer is currently "no".
However, we do support exporting Service object definitions to environments like DCE,
CORBA, Encinca (a TP monitor), and the WWW. In our next release we will complete our
support for exporting services objects to Java. This will allow for Java applications to
call upon the power of Forte's Shared Services architecture. Using this exporting
concept, applications written in various other languages would be able to "call-in" to
the Forte shared service from the ourside world.
Didn't know what you were looking for. Hope the above hit the mark. If not, write me, or
give me a call.
Regards,
jim

Not exactly sure what you are asking. Can you rephrase your question?
If your other server's locale is same as the one you configured then it should be ok.

SIGSEGV signal (no mapping at the fault address) : in _XmAddHashEntry

I have ported a motif based program from Compaq Tru 64(in Tru 64 program is running without any problem) to Solaris 8. I have used Forte developer 6 C++ compiler. Program compiled & linked successsfull. But during runtime 'XmCreateMainWindow' method call generating SIGSEGV signal. Debugger says 'signal SEGV (no mapping at the fault address) in _XmAddHashEntry at 0xfee79ff0
0xfee79ff0'.
Program :
Widget children[6]; /* Children to manage */
Arg al[64]; /* Arg List */
register int ac = 0; /* Count */
XtPointer tmp_value; /* ditto */
if ( !widget_name )
widget_name = (char *)"mainWindow1";
XtSetArg(al[ac], XmNscrollingPolicy, XmAUTOMATIC);
mainWindow1 = XmCreateMainWindow ( parent, widget_name, al, ac );
Stack :
main(argc = 11, argv = 0xffbef1c4)
mMainAppShell_c::create(this = 0xef508, display =
0xeaf70, app_name = 0xeeae8 "IP AGENT- QNR002",
app_argc = 11, app_argv = 0xffbef1c4,
app_class_name = 0xc3a49 "XApplication")
mainWindow1_c::create(this = 0xef520, parent =
0xe9b08, widget_name = 0xc1d81 "mainWindow1")
XtCreateWidget(0xc1d81, 0x0, 0xe9b08, 0xffbee12c,
0x0, 0xfef0e768)
_XtCreateWidget(0xc1d81, 0xfef0e768, 0xff0f7c74,
0xffbee12c, 0x0, 0x0)
XtInitializeWidgetClass(0xfef0e768, 0x4925c,
0xff0f4000, 0x1f, 0xfef0e768, 0xfed1b86b)
XtInitializeWidgetClass(0xfef10dbc, 0x2afe,
0xff0f4000, 0x1f, 0xfef10dbc, 0xff094ae2)
XtInitializeWidgetClass(0xfef14290, 0x2afe,
0xff0f4000, 0x1f, 0xfef14290, 0x0)
ClassPartInitialize(0xfef14354, 0xfef14350,
0xfef1434c, 0xfef04000, 0xfef14290, 0xff0f787c)
XmeTraitSet(0xfef14290, 0x0, 0xe78a8, 0xfef19934,
0xfef04000, 0xfef1434c)
_XmAddHashEntry(0x0, 0xe78a8, 0xfef19934, 0xd,
0xf541c, 0xc)
Error :
t@1 (l@1) signal SEGV (no mapping at the fault address) in _XmAddHashEntry at 0xfee79ff0
0xfee79ff0: _XmAddHashEntry+0x0004:     ld      [%i0 + 0xc], %l0
Current function is mainWindow1_c::create
0xfee79ff0: _XmAddHashEntry+0x0004:     ld      [%i0 + 0xc], %l0
0xfee79ff0: _XmAddHashEntry+0x0004:     ld      [%i0 + 0xc], %l0
(dbx) (dbx)

Tough to debug this from the information that you posted but it appears that _XmAddHashEntry is being called with NULL (0x0) as the first parameter and the instruction that is causing problems is the load at 0xfee79ff0 that is trying to use the first parameter (%i0) with the offset of 0xc. This address is going to be in the kernel space somewhere and the segmentation violation is pointing out that the kernel isn't happy about you peeking at it's unders.
Perhaps you can backtrack from the call to XmAddHashEntry to see what object or class is expected as the first parameter and deduce how that parameter might be getting set (or not set as it were) to NULL.
Also, you mentioned that you're moving from a 64-bit OS. Did you compile your program with the -xarch=v9 flag?
Another thing to check is your stacksize variables. There are two which control the size of various aspects of the stack.
from the C-shell you should type:
unlimit stacksize
and
setenv STACKSIZE 40000
The first sets the overall process stacksize to whatever the system will allow (unlimited). The second, controls how much any individual thread can take for its stack. The second won't effect your application unless it's multi-threaded.

RE: (forte-users) Phantom Nodes

Yes both the client and server have to have the same setting and it does not
work all the time.
-----Original Message-----
From: Samer Kanjo [mailto:[email protected]]
Sent: Thursday, May 10, 2001 11:33 PM
To: Amin, Kamran; Forte Users
Subject: RE: (forte-users) Phantom Nodes
Kamran,
Just so I am clear on the use of keep alive settings,
the settings are required on both the server and the
client, correct? If so then should the settings on
both client and server nodes be equal?
Again to be clear, are you saying that the keep alive
settings alone will prevent phantom nodes?
Kelsey & Pascal, do you still have the problem even
though you are using keep alive settings?
Samer Kanjo
--- "Amin, Kamran" <[email protected]> wrote:
The socket time is an OS level setting and is
different on each OS. I had
open up a ticket with Forte 2 years ago and the only
quick solution was to
change the name of the client computer which faked
Forte into thinking its a
different node. This way the client was able to get
back into their
application quickly. The only problem was that the
clients had to reboot
their computer. The other way to prevent this was
to use the keep alive
settings to force a clean up on the Forte central
environment side.
ka
-----Original Message-----
From: Samer Kanjo [mailto:[email protected]]
Sent: Thursday, May 10, 2001 6:26 PM
To: [email protected]; Forte Users
Subject: RE: (forte-users) Phantom Nodes
Kelsey,
We use model nodes exclusively. Occasionally, a
client
node would crash and would be inaccessbile for two
hours but would still appear active under the model
node. After two hours the client could access the
environment again. My only option thus far has been
to
bounce the environment but that can only be done
after
work hours, which may not be convenient for the
affected user.
Kamran Amin just wrote me to say that the two hour
delay is the result of the default socket timeout
setting on UNIX boxes. Perhaps reducing the socket
timeout from two hours to something more reasonable
would fix the problem without manipulating the
environment configuration.
I am not sure how I would determine a good socket
timeout setting for my application. Does anyone have
any ideas? Is my assumption about reducing the
socket
timeout to avoid manipulating the environment
configuration to remove the phantom nodes in a more
timely fashion correct?
Samer Kanjo
--- [email protected] wrote:
"... have you reported this to Forte as a bug or
looked through the defect
reports?..."
No and No. I just kind of "stumbled" upon this
solution this week. I just
opened the properties windows when it just all ofa
suddened dawned on me:
"Maybe, if none of the boxes are checked then the
node effectively serves
no usefull purpose in the environment. Therefore,
maybe Forte will be more
apt to release it - like the garbage collectordoes
with an object that is
not referenced".
" ... Have you tried this technique when usingmodel
nodes? ..."
No I haven't. So far our model nodes have beenwell
behaved. If a member
was online the node was online, otherwise, if "no
one was home" then it was
off-line. Model nodes aren't real nodes; I viewthem
as a sort of virtual
node. Only real nodes have ocassionally behaved
goofy. I think what happens
is either the user's machine is improperlyshutdown
or they just all of
sudden loose connection to the network. Exception
handling was never Forte
ADE's forte.
Kelsey Petrychyn, P. Eng. SaskTel TechnicalAnalyst
ITM - Technology Solutions - Distributed Computing
Tel (306) 777 - 4906, Fax (306) 359 - 0857
Internet:[email protected]
Quality is not job 1. It is the only job!
Samer Kanjo
<skanjo@yahoo To:
"Forte Users" <[email protected]>
.com> cc:
Subject:
RE: (forte-users) Phantom Nodes
05/10/2001
01:57 PM
Pascal,
This is very inetresting. I have experienced the
same
problem and have noted the mysterious two hourdelay
in getting the client node back up and running. I
thought it may have had something to do with the
keepalive settings, which seem to work otherwise.
Kelsey, have you reported this to Forte as a bugor
looked through the defect reports? Have you tried
this
technique when using model nodes? I will give your
fix
of reconfiguring the node a try the next time I
encounter the problem. However, I use model nodesso
perhaps it may not have the same effect.
Samer Kanjo
--- "Rottier, Pascal" <[email protected]>
wrote:
I've seen this problem many times myself and the
cause was always the same.
The nodemanager of the phantom node was notproperly
shutdown. Usually,
because this node was running on NT and somebody
simply shutdown the
machine. A "kill -9" on unix will also have thesame
effect.
Part of the shutdown process of a node, which
you
should always invoke from
e-console or e-script, is to inform theenvironment
that it's going away.
Then Forte will mark it as offline, rather then
online. However, it the
nodemgr suddenly dies, there is no such signal.
=== message truncated ===

Therefore, how to remotely start a node manager ? :-p
j-p
-----Message d'origine-----
De: John Parks [mailto:jparkss1.com]
Date: vendredi 15 septembre 2000 20:07
À: Jean-Paul.Gabriellisema.fr
Cc: 'Forte Users'
Objet: Re: (forte-users) [Model Nodes] What prevents Server Parts to be
assigned there ?!:?
Jean-Paul,
The ModelNode is a client node by definiton, no matter what properties you
change. I've previously asked for an enhancement to allow a
model node to be a
server node, but I don't expect much to happen. To install
server applications
to several nodes, you have to make sure that the node manager on
each node is
active. There really is no built-in support for distributing
applications in
mass to servers like there is for clients (using the model node feature).
Regards,
John Parks
S1 Corporation
Jean-Paul Gabrielli wrote:
Hi,
I want to have a separate node to provide a dedicated service,
and therefore when I start my environment server and declared that
node as ModelNode, with 'client' disabled, i still can't assign to it
my server partition.
And if I declare it as regular node, the installation of the application
failed if the node is not online.
What choice do I have ?
What prevents that ModelNode, client disabled, to host serverpartition ?!,
j-paul gabrielli
sema dts
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe,send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com--
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

3GS Signal Strength Reduction

First of all I've searched this forum and have seen some having the same issues. But I've really noticed it in the past couple of weeks even more. I only get one to two bars..sometimes three...even when I'm at home and used to get all bars. I work 20 miles away and the 3G signal is down pretty much all day. The calls I'm on have been skippy and sometimes we get dropped altogether. I'm in the Dallas/Fort Worth, TX Metroplex area...HOME to AT&T...LOL. It should be blazin' like it was before.
Is this the result of the most recent OS update? I've seen some users are having no problems whatsoever, while others are experiencing the same thing I am.
Suggestions? Already did the reboot thing several times this week alone. Just wait for another OS update and hope it gets fixed?

My iPhone 3GS has been dropping calls constantly over the past 2 weeks. I have gone to AT&T and they switched out my sim card, now its worse! Its driving me crazy! What is going on with the 3GS model? Also my alarm clock is going off and hour earlier than it is supposed to. Someone please help! I am seriously considering getting a Droid phone.

Sending POSIX signal to an external subprocess from a java program

I'm programing in forte for java under linux-mandrake, I've execute an external subprocess with the runtime and Process clases, I need to send the 2� POSIX signal to this external subprocess, I mean de SIGINT signal, I know that you can send a signal from a shell just doing:
Kill -2 pid // the SIGINT signal is the 2 POSIX signal
I know that there is another system-call like : kill(int signal, int pid) that any one can send from a c program.
Althought I don't know how can I get the pid of a suprocess, because I Know that there is the systemcall in c like:
int getpid() wich gives the pid of the current process, but I need to have the pid of a subprocess not the current one.
The thing is that I do not know how can I do it from a java program, I mean that to send a signal to a subprocess it will work using system-calls, but I do not know if I can insert system call in a java program, I've been thinking about doing it using a linux script like:
#!bin/bash
$a = pidof /home/maude-linux/bin/maude.linux
# this is the path of the process wich is running
kill -2 a$
and the run this script from a java program doing an exec(sh script.bin)
but by the moment I must be doing something wrong in the script because I find mistake in it, it gives me mistake in the assign sentence , I mean:
$a = pidof /home/maude-linux/bin/maude.linux
# this is the path of the process wich is running
I'm not used to program shell scripts, perhaps I'm doing something wrong, is there something wrong in this sentence?.
I would aprecciate some help about this, or if somebody have some idea how to do it in java, I repeat I need to send a signal to a external subprocess wich is launched from a java program by the process and runtime clases, and I need to send a SIGINT signal to the subprocess, I hope that some body can give some suggestion or some code explaining the situation

Are the portions of bash-code verbatim in your post?
When yes, they look suspicious!
Instead of
#!bin/bash
#!/bin/bash
would be better.
$a = pidof /home/maude-linux/bin/maude.linux
does not look good either.
If you have command "pidof" telling the pid based on the path name of the executable passed to it as its argument, you can have the output of this program in a shell script like this:
a=$( pidof /home/maude-linux/bin/maude.linux )
Then through $a you will refer to the value of the variable "a":
kill -SIGINT $a
A pidof script could look like this (apart from error handling):
ps -ef|awk '{if (NF>=8 && $8=="'"$1"'") print $2;}'
This works for me; your mileage may vary.

Affichages multiples temps-réel d'un signal

Je dispose d'un vi d'acquisition d'un signal (+s voies et 2 cartes PCI-4472 et PCI-4474) qui me génère un tableau de waveforms en sortie (DAQmx).
Je veux écrire différents vis d'affichage (f(t), FFT, XY,...) de ce signal et qui devront être en temps réel. (sachant que d'autres affichages de post-traitements seront ensuite faits à partir d'un fichier de sauvegarde des données). Cette solution a été retenue car je ne vois pas comment faire de multi-fenêtrage sans ça... (mais on peut peut-être !). Cependant, à l'affichage, j'ai l'impression de perdre des informations ??
Voici en pièce jointe, un vi simple qui reprends plus ou moins mon problème (décalage de la courbe simulée dans le graphe déroulant).
Quelle architect
ure me conseillez vous ?
Attachments:
test.vi ‏174 KB

Bonjour,
Il est fortement déconseillé d'utiliser plusieurs boucles While en parallèle.
En effet, dans votre exemple, vous perdez plusieurs données lors de l'exécution.
Je vous propose une solution à votre exemple : Utiliser une seule boucle While pour les 3 affichage.
Cf. Fichier joint.
Sanaa TAZI
Application Engineer
National Instruments
Attachments:
Exemple.vi ‏161 KB

Enlever la composante continue d'un signal dans la FPGA

Bonjours,
Je cherche à enelever la composante continue d'un signal dans ma FPGA, pour cela j'ai essayé d'utiliser un filtre butterworth passe haut d'ordre deux avec fc= 20Hz, celui-ci m'enlève bien la composante continue mais il me laisse un offset à la sortie, certe petit mais un offset quand même et vu qu'après cela j'ai besoin d'intégrer mon signal cette offset est très embêtant. J'ai essayé avec d'autre filtre créer avec le IP core generator mais le problème reste le même.
Avez vous une idée de comment procéder pour enlver la composante continue d'un signal avant de l'intégrer avec Normalized Discret integrator.vi?
Cordialement
Sébastien Kuenlin

Bonjour Skuenlin,
Avez-vous essayé d'augmenter la fréquence de coupure de votre filtre de manière à atténuer plus fortement les basses fréquence?
Quelle est la fréquence minimum du signal que vous souhaitez récupérer?
Si cette fréquence est proche du DC avez-vous pensé à utiliser un autre type de filtre "tchebycheff" ou autre, ou simplement augmenter l'ordre de votre filtre?
Cordialement,
Rémi D.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Les rencontres techniques de NI - Mesures et acquisition de données : de la théorie à la mise en ...

Simulations de signaux et comptage de franges

Bonjour à tous,
Je suis actuellement en stage dans un labo d'instrumentation spatiale et je dois développer un code qui simule deux signaux sinusoïdaux en quadrature de phase pour ensuite faire du comptage de frange. La fréquence des deux signaux est de 289 Hz. Et dans mon cas une frange correspondant à une période, je devrai donc obtenir pour un temps de 10s 2890 franges. Or entre deux execution ce nombre varie fortement (plus ou moins 100 franges). Et encore plus troublant, lorsque je fais varier le nombre d'échantillons par seconde dans les paramètres des signaux simulés, ce nombre passe d'environ 2000 à 3000! Je veux bien qu'il y ait un petit problème dans mon programme de comptage de frange, mais je ne comprend pas pourquoi en faisant varier le nombre d'échantillon je fais varier la fréquence, pourtant celle-ci est bien fixe (j'ai mis un indicateur).
Je vous remercie d'avance pour ceux qui peuvent m'aider, je suis vraiment en grosse galère!

Hello,
And thank you for posting here. Please post in english on this english forum. If you want, you have a French community on this link:
forum
Could you post your VI in order to help you.
Regards
Samuel G. | Application Engineer Team Leader
Certified LabVIEW Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Été de LabVIEW 2014
12 présentations en ligne, du 30 juin au 18 juillet

NI-DAQMX Problème d'acquisition d'un signal courant

Bonjour,
J'utilise une carte PCI XXX,
Je crée une nouvelle tâches NI-DAQMX,
en entrée j'ai un courant 4 ... 20 mA, en sortie je veux visualiser 0 ... 1 bar.
Lorsque je créer une nouvelle échelle, et que je visualise le signal, celui-ci sature à 10 mA.
Lorsque je sélection " pas d'échelle " le signal ne sature plus, pourquoi ? et que doi je faire pour remedier a ceci ??

Bonjour,
Je vous invite en premier lieu à consulter ces KB forts utiles :
Custom Scale Only Returns My Prescaled Values
How do I Configure Custom Scales for Analog Outputs in Measurement & Automation Explorer (MAX)
Changing the Values of a Custom Scale Programmatically
Cordialement,
Steve M.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Vidéo-t'chats de l'été : présentations techniques et ingénieurs pour répondre à vos questions

Signal Handler

hi all.
I encountered a very strange problem recently on Solaris 8 and forte C++ 6.2.
#include "signal.h"
extern "C" sig_handler(int)
// do something
if (signal(SIGUSR1, sig_handler) == SIG_ERR) {
cerr << "Errors aborting!" << endl;
else{
cout << "OK" << endl;
First, it is compiled and gives me OK when I start the program.
but when SIGUSR1 is used, nothing happens.
I change signal(SIGUSR1, sig_handler) to sigset(SIGUSR1, sig_handler) ,
then it is working.
Any idea?
Thanks
CC

So what? How should iPlanet or any other product be able to change signal handlers in other processes? That's simply impossible.
When using the old (obsolete?) signal() call the signal handler must reestablish itself via signal() after it got called.
signal() has severe problems that's why sigaction() was introduced. I'd recommend to use sigaction()...

Fort Wayne, In. HTC Thunderbolt no 4G connection all day

Hey when I first bought my Thunderbolt I was in 4G connection at all times nearly, but today for some odd reason it has only been in 3G connection. I have tried hard resetting/ pulling the battery and also I have checked the settings to make sure they were correct. I have even put it in lte mode only and all I got was 1x bars. I guess I'm really curious as to why this has happened today.
Any answers are greatly appreciated,
Jimmy

Hi Jimmyfb55,
I would also be curious as to why you could not pick up the 4G signal on the 14th when you posted.I competely understand your frustration. I want you to know that I have checked my references and I do not show any reported outages for the Fort Wayne, IN area on that day. I am, however, glad that you were able to connect to a 3G signal, so you could still use data on the Thunderbolt.
Since posting, has the issue been resolved? Are you now able to pick up a 4G signal?
Please post back and let us know, thanks!

UNEXPECTED SYSTEM SIGNAL "6"

Dear All,
We are using Forte version 2.0.F.2 with Informix and on one table ( out
of 250 ) we get a message back from the database "UNEXPECTED SYSTEM
SIGNAL '6' caught ".
The table appears fine from the database end.
Any idea what the problem is ?
Regards
Ceri Davies.

That is interesting. I actually sent some of my pages documents to a friend who has a MacBoook Pro fully loaded and as soon as she opened my pages she experienced my same issues. She works in pages on large image documents also but has not had these problems.
Maybe it is something about Macbook compatibility?

'signal' in forte

Similar Messages

Maybe you are looking for