Partition workshop hangs

I posted this problem a couple of months ago & then didn't really have time
to look into it, so I'm posting it again. A couple of months ago we started
having problems running applications from the partition workshop. Sometime
they work & sometimes they don't & there isn't any repeatable pattern that
happened when they do work??
Once you get into the partition workshop & click the running man, it churns
for awhile & then we get a "loading partition into server" message & then it
goes off into no mans land. If I look at the task manager on the client
that's trying to run it, the ftexec isn't even getting cpu cycles, although
it starts out getting cycles, & then all of a sudden, it just stops?? When I
try to start Econsole to see what's happening, it won't even come up?? IF it
does run, I can exit out, shutdown the partition workshop, go right back
into the partition workshop, click the running man & this time, it doesn't
run!! No errors are generated either. Once it "goes into no mans land", the
only way to stop it is to do an "end task" from task manager. A cancel run
from the workshop doesn't even work?
I've played around with increasing the memory settings on the ftexec that
starts when you start Forte Distributed, I've tried different workspaces,
some with a shadow, others without. I've even tried uninstalling & reloading
Forte on the machine, all to no avail. We're running NT 4.0 clients, Forte
3.0.J.1, Digital Unix 4.0.D .
Does anybody have any ideas or suggestions on what to do/try?? Any help
would be greatly appreciated!!
Doug Scurr
HealthPartners
8100 34th Avenue South
Minneapolis, MN 55440-1309
(612)883-7317
[email protected] <[email protected]>

Similar Messages

RE: Partition workshop hangs

Sounds ugly. Couple of thoughts.
I assume you've created a test harness to load seperate partitions to ensure
the basics are working?
Check it out on fscript ( findproj badname, removeconf, findact, partition 0
, showplan ). Maybe showplan
will identify a hole in your repository.
If you have multiple services in seperate partitions, try swapping in dummy
noop classes for each. Could
be you have a failed autostart plan you didn't expect.
If that all fails, use the test harness to preload ftexec partitions in your
environment and crank up the
Trace flags on them and leaf through the output...
trc:c4:5:5 info mssgs
trc:c4:9:10 Traces all notifications sent
trc:do:10-11 Partition manager( 10 for header, 11 for partition
detail)
Good luck
-----Original Message-----
From: [email protected]
[SMTP:[email protected]]
Sent: Monday, April 12, 1999 9:50 AM
To: [email protected]
Subject: Partition workshop hangs
I posted this problem a couple of months ago & then didn't really have
time to look into it, so I'm posting it again. A couple of months ago we
started having problems running applications from the partition workshop.
Sometime they work & sometimes they don't & there isn't any repeatable
pattern that happened when they do work??
Once you get into the partition workshop & click the running man, it
churns for awhile & then we get a "loading partition into server" message
& then it goes off into no mans land. If I look at the task manager on the
client that's trying to run it, the ftexec isn't even getting cpu cycles,
although it starts out getting cycles, & then all of a sudden, it just
stops?? When I try to start Econsole to see what's happening, it won't
even come up?? IF it does run, I can exit out, shutdown the partition
workshop, go right back into the partition workshop, click the running man
& this time, it doesn't run!! No errors are generated either. Once it
"goes into no mans land", the only way to stop it is to do an "end task"
from task manager. A cancel run from the workshop doesn't even work?
I've played around with increasing the memory settings on the ftexec that
starts when you start Forte Distributed, I've tried different workspaces,
some with a shadow, others without. I've even tried uninstalling &
reloading Forte on the machine, all to no avail. We're running NT 4.0
clients, Forte 3.0.J.1, Digital Unix 4.0.D .
Does anybody have any ideas or suggestions on what to do/try?? Any help
would be greatly appreciated!!
Doug Scurr
HealthPartners
8100 34th Avenue South
Minneapolis, MN 55440-1309
(612)883-7317
<[email protected]>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi,
Try to increase the FORTE_STACK_SIZE. I think the recommended setting for
Digital UNIX is 60000 which is about 60k per thread.
I encountered similar problem before on connecting to Ingres. The problem
may be that the default is too low, so on some library calls, the thread
just hangs. You will encounter the same problem again when trying
distributed run because the same ftexec is being used. Sometime it works
because maybe by chance your run fall into another ftexec.
I handle such situation by browsing into the ftexec using Econsole or
escript. If Econsole/escript can't get into it, that means the ftexec run
away or hanged. I will kill -9 the ftexec and try distributed run again.
Best regards,
Peter Sham.
-----Original Message-----
From: [email protected]
[SMTP:[email protected]]
Sent: Monday, April 12, 1999 9:50 PM
To: [email protected]
Subject: Partition workshop hangs
I posted this problem a couple of months ago & then didn't
really have time to look into it, so I'm posting it again. A couple of
months ago we started having problems running applications from the
partition workshop. Sometime they work & sometimes they don't & there isn't
any repeatable pattern that happened when they do work??
Once you get into the partition workshop & click the running
man, it churns for awhile & then we get a "loading partition into server"
message & then it goes off into no mans land. If I look at the task manager
on the client that's trying to run it, the ftexec isn't even getting cpu
cycles, although it starts out getting cycles, & then all of a sudden, it
just stops?? When I try to start Econsole to see what's happening, it won't
even come up?? IF it does run, I can exit out, shutdown the partition
workshop, go right back into the partition workshop, click the running man &
this time, it doesn't run!! No errors are generated either. Once it "goes
into no mans land", the only way to stop it is to do an "end task" from task
manager. A cancel run from the workshop doesn't even work?
I've played around with increasing the memory settings on
the ftexec that starts when you start Forte Distributed, I've tried
different workspaces, some with a shadow, others without. I've even tried
uninstalling & reloading Forte on the machine, all to no avail. We're
running NT 4.0 clients, Forte 3.0.J.1, Digital Unix 4.0.D .
Does anybody have any ideas or suggestions on what to
do/try?? Any help would be greatly appreciated!!
Doug Scurr
HealthPartners
8100 34th Avenue South
Minneapolis, MN 55440-1309
(612)883-7317
[email protected]
<[email protected]>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Partition workshop hang - more info

I tried something today that seems to have "fixed" this hanging problem.
We're using the Forte keep alive processing for a couple of lock manager
partitions that we were having problems with. We have forte_keep_count at 1,
forte_keep_cycle at 30 & forte_keep_interval at 10. We've had a ton of
trouble with clients at 1st Trust in St. Paul getting their connections
terminated by the communications manager since then. I'm not sure if they're
related or not, but what I did was on my 2nd pc were I haven't been able to
run from the partition workshop, I turned off the keep alive settings,
shutdown all ftexecs on the server, restarted my workspace & ran from the
partition workshop & it fired right up!!! Just to test it again, I shutdown
my workspace, shutdown all of the ftexecs on the server, turned the keep
alive stuff back on & tried running from the partition workshop & it went
off into lala land again!!
From what we got out of the Forte documentation about the keep aliveprocessing is that BOTH the client & the server partition must have those 3
keep alive setting turned on for the keep alive processing to be "active".
My little test seems to indicate that by only having one side set, in this
case the client, that the keep alive processing is still active?? Is anybody
using the keep alive stuff?? Am I on the right track?? Any info would be
greatly appreciated!!
Doug Scurr
HealthPartners
8100 34th Avenue South
Minneapolis, MN 55440-1309
(612)883-7317
[email protected] <[email protected]>

I tried something today that seems to have "fixed" this hanging problem.
We're using the Forte keep alive processing for a couple of lock manager
partitions that we were having problems with. We have forte_keep_count at 1,
forte_keep_cycle at 30 & forte_keep_interval at 10. We've had a ton of
trouble with clients at 1st Trust in St. Paul getting their connections
terminated by the communications manager since then. I'm not sure if they're
related or not, but what I did was on my 2nd pc were I haven't been able to
run from the partition workshop, I turned off the keep alive settings,
shutdown all ftexecs on the server, restarted my workspace & ran from the
partition workshop & it fired right up!!! Just to test it again, I shutdown
my workspace, shutdown all of the ftexecs on the server, turned the keep
alive stuff back on & tried running from the partition workshop & it went
off into lala land again!!
From what we got out of the Forte documentation about the keep aliveprocessing is that BOTH the client & the server partition must have those 3
keep alive setting turned on for the keep alive processing to be "active".
My little test seems to indicate that by only having one side set, in this
case the client, that the keep alive processing is still active?? Is anybody
using the keep alive stuff?? Am I on the right track?? Any info would be
greatly appreciated!!
Doug Scurr
HealthPartners
8100 34th Avenue South
Minneapolis, MN 55440-1309
(612)883-7317
[email protected] <[email protected]>

Workshop hangs in classes inherited fromPageFlowController

hi group
i have a really strange problem which seems to be project specific. i already recreated the project several times, re-installed workshop, switched/created new workspace, disabled autonomy services and validation...
when i edit a file containing a class inherited from PageFlowController, the whole workshop hangs periodically for several seconds. it's not possible to work anymore, when I type, it displays max. 10 characters and then the system hangs for about 10 seconds. i suspect it could be some kind of encoding stuff because i once saw a message about encoding cant be saved, but now i dont have that message anymore and it still freezes. one other thing could be the "updating property editor" which appears shortly before the freeze, but i am not sure about that...
any ideas ?
best wishes
-ToM-

hi group
i have a really strange problem which seems to be project specific. i already recreated the project several times, re-installed workshop, switched/created new workspace, disabled autonomy services and validation...
when i edit a file containing a class inherited from PageFlowController, the whole workshop hangs periodically for several seconds. it's not possible to work anymore, when I type, it displays max. 10 characters and then the system hangs for about 10 seconds. i suspect it could be some kind of encoding stuff because i once saw a message about encoding cant be saved, but now i dont have that message anymore and it still freezes. one other thing could be the "updating property editor" which appears shortly before the freeze, but i am not sure about that...
any ideas ?
best wishes
-ToM-

Disk utility-erasing a HD, creating partition map hanging

Hi all,
I have been given an external Maxtor USB drive, 120 BG, with the need to securely wipe the old information on it. I have used Disk Utility, and zeroed the HD with a 7 times pass. This took 17 hours, and it moved to the "create partition map" stage. It's been doing that for 24 hours and still the progress bar is rolling. All other options are greyed out and nothing can be selected in Disk Utility. I have chosen to format it in Mac OS X Extended, Journaled. There was about 45 GB data on the drive.
Would this amount of time be expected, or has something gone wrong? I hesitate to force quit DU, in case I render the drive unusable. If I do that or shut down the computer, what's likely to happen to the HD? Will I be able to mount it again and start over. Any tips much appreciated.
Frances

Hi Frances,
17 hours for the 7-times pass is normal (and usually completely unnecessary unless you work for the CIA). However, the hang at the "create partition map" stage is not normal. I would interrupt it and reformat the drive, since the zeroing is finished anyway.
If this answered your question please consider granting some stars: Why reward points?

Hanging Save in partition workspace.

I have my workspace preferences set to "save before running"
Now when I run in the partition workshop, I get the message "Saving
Workspace" in the
Workshop status line, and then it saves.... And saves..... and saves until
finally I have to
Kill forte by going to the forte menu and selecting launch server shutdown.
Anyone else been having this problem with forte 3.5 on NT?

There should be a file named: <reposname>.rop in the repos directory of your
Forte environment. It is a log of the repository operations. You may get some
clue as to what is happening there.
Thanks
Amos.G.Radfordbankofamerica.com wrote:
Do you do rpcleans on your reposity on a regular basis. It sounds like your
repository is starting to roll over. Check it's size, right before it's
ready to blow it will start to grow abnormally.
"Jones, Kerreck" <Kerreck.JonesGD-ES.COM> on 03/07/2001 07:31:28 AM
To: forte-users-digestlists.xpedior.com
cc:
Subject: (forte-users) Hanging Save in partition workspace.
I have my workspace preferences set to "save before running"
Now when I run in the partition workshop, I get the message "Saving
Workspace" in the
Workshop status line, and then it saves.... And saves..... and saves until
finally I have to
Kill forte by going to the forte menu and selecting launch server shutdown.
Anyone else been having this problem with forte 3.5 on NT?
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

Mac partition becomes laggy after dual boot windows 7

Hi all,
Last week I dual boot my Windows 7 again to make larger memory space for Windows partition. However after the dual boot, everytime when I first log in my Mac partition, it hangs and I need to restart to get it back to normal, Even though is back to normal, I still notice it takes longer time to open my documents compared to last time. I have roughly 10Gb for my Mac storage, I wonder is it because of the low memory space that makes this happens. Please advice!

Lack of harddisk space can indeed be the cause for the problems you have.
Have a read here http://www.thexlab.com/faqs/lackofram.html
Stefan

Windows 7 hangs from boot menu

Hi,
my Windows 7 partition refuses to start from boot menu, system just hangs and does nothing. I've not made any changes to the disk layout, only thing I can think of is the upgrade to 10.9.4 which probably changed the recovery partition.
History:
- iMac Mavericks 10.9.3 with boot camp 5.1.2 and Windows 7, used to start into Windows by pressing Alt on start up, then reboot from Windows menu or from Windows boot camp application into OS X and back without problems
- installed the 10.9.4 Build 13E28 upgrade some days ago
- Change today: rebooted from the boot camp system tray app into OS X, worked without a problem
- reboot from OS X into boot menu, select Windows 7 partition, system hangs
I've found this thread, describing a similar problem Repairing Boot Camp after creating new partition I think, however since my Index output only lists 4 partitions I think my problem might be a bit different.
Here's the output from: sudo gpt -r -vv show disk0
gpt show: disk0: mediasize=500107862016; sectorsize=512; blocks=976773168
gpt show: disk0: Suspicious MBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 976773167
      start       size index contents
          0          1         MBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6
         40     409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640 816890832      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
817300472    1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
818570008       1256
818571264 158201856      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
976773120         15
976773135         32         Sec GPT table
976773167          1         Sec GPT header
and this one is from: sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 60801/255/63 [976773168 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [    409640 - 816890832] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 817300472 -    1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 818571264 - 158201856] HPFS/QNX/AUX
and, just in case: diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Calimera                418.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data Windows 7               81.0 GB    disk0s4
I guess something mixed up the MBR since I would have expected line 4 of the fdisk output to show something 'Windows' like instead of HPFS/QNX/AUX, but even if that is correct, the question is how can the boot problem be fixed?
The Windows partition is accessible from OS X, so copying the data is not a problem if everything else fails. As far as I remember, the boot camp version in windows is 3.3 (it's an older iMac model).
GDisk is available, command line not a problem, if you need any further info let me know, any help appreciated.
thanks,
jk

Hi,
> Does the Bootcamp partition show up in Finder and can you see files in it?
Yes, the partition shows up in Finder and I can see and copy files.
> In Disk Utility, does the Bootcamp partition report as NTFS?
Yes it does, "Get Info" from Finder also reports it as a NTFS volume.
> Do you have any third party NTFS drivers?
Yes I have, Paragon NTFS tools.
> If you hold the ALT key can you boot into Windows?
No, system just hangs and needs to be rebooted via power-off.
> If you came from 10.9.3 to 10.9.4, the Recovery HD should have existed under 10.9.3.
Yes it did, I did a clean install from USB media when Mavericks came out, the Recovery HD is also visible - and has been - in the boot menu.
> The one strange part is that your volume says "Windows 7". Were any diskutil commands run to change volume names?
No, just a left click on the Volume Name in Finder and then change Bootcamp to Windows 7.
Output of dd:
00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS    .....|
00000010 00 00 00 00 00 f8 00 00 3f 00 ff 00 00 68 ca 30 |........?....h.0|
00000020 00 00 00 00 80 00 80 00 ff f7 6d 09 00 00 00 00 |..........m.....|
00000030 00 00 0c 00 00 00 00 00 02 00 00 00 00 00 00 00 |................|
00000040 f6 00 00 00 01 00 00 00 d7 f9 07 a2 27 08 a2 26 |............'..&|
00000050 16 1d 72 73 fa 33 c0 8e d0 bc 00 7c fb 68 c0 07 |..rs.3.....|.h..|
00000060 1f 1e 68 66 00 cb 88 16 0e 00 66 81 3e 03 00 4e |..hf......f.>..N|
00000070 54 46 53 75 15 b4 41 bb aa 55 cd 13 72 0c 81 fb |TFSu..A..U..r...|
00000080 55 aa 75 06 f7 c1 01 00 75 03 e9 dd 00 1e 83 ec |U.u.....u.......|
00000090 18 68 1a 00 b4 48 8a 16 0e 00 8b f4 16 1f cd 13 |.h...H..........|
000000a0 9f 83 c4 18 9e 58 1f 72 e1 3b 06 0b 00 75 db a3 |.....X.r.;...u..|
000000b0 0f 00 c1 2e 0f 00 04 1e 5a 33 db b9 00 20 2b c8 |........Z3... +.|
000000c0 66 ff 06 11 00 03 16 0f 00 8e c2 ff 06 16 00 e8 |f...............|
000000d0 4b 00 2b c8 77 ef b8 00 bb cd 1a 66 23 c0 75 2d |K.+.w......f#.u-|
000000e0 66 81 fb 54 43 50 41 75 24 81 f9 02 01 72 1e 16 |f..TCPAu$....r..|
000000f0 68 07 bb 16 68 70 0e 16 68 09 00 66 53 66 53 66 |h...hp..h..fSfSf|
00000100 55 16 16 16 68 b8 01 66 61 0e 07 cd 1a 33 c0 bf |U...h..fa....3..|
00000110 28 10 b9 d8 0f fc f3 aa e9 5f 01 90 90 66 60 1e |(........_...f`.|
00000120 06 66 a1 11 00 66 03 06 1c 00 1e 66 68 00 00 00 |.f...f.....fh...|
00000130 00 66 50 06 53 68 01 00 68 10 00 b4 42 8a 16 0e |.fP.Sh..h...B...|
00000140 00 16 1f 8b f4 cd 13 66 59 5b 5a 66 59 66 59 1f |.......fY[ZfYfY.|
00000150 0f 82 16 00 66 ff 06 11 00 03 16 0f 00 8e c2 ff |....f...........|
00000160 0e 16 00 75 bc 07 1f 66 61 c3 a0 f8 01 e8 09 00 |...u...fa.......|
00000170 a0 fb 01 e8 03 00 f4 eb fd b4 01 8b f0 ac 3c 00 |..............<.|
00000180 74 09 b4 0e bb 07 00 cd 10 eb f2 c3 0d 0a 41 20 |t.............A |
00000190 64 69 73 6b 20 72 65 61 64 20 65 72 72 6f 72 20 |disk read error |
000001a0 6f 63 63 75 72 72 65 64 00 0d 0a 42 4f 4f 54 4d |occurred...BOOTM|
000001b0 47 52 20 69 73 20 6d 69 73 73 69 6e 67 00 0d 0a |GR is missing...|
000001c0 42 4f 4f 54 4d 47 52 20 69 73 20 63 6f 6d 70 72 |BOOTMGR is compr|
000001d0 65 73 73 65 64 00 0d 0a 50 72 65 73 73 20 43 74 |essed...Press Ct|
000001e0 72 6c 2b 41 6c 74 2b 44 65 6c 20 74 6f 20 72 65 |rl+Alt+Del to re|
000001f0 73 74 61 72 74 0d 0a 00 8c a9 be d6 00 00 55 aa |start.........U.|
00000200
So, you think running the Windows startup repair will fix the problem? Is there something that I should be aware of in terms of interfering with the OS X partition?
jk

Re: (forte-users) No response from Router partition

Sounds like what we have been experiencing here, on Unix.
According to Forté, upgrading to 3M should resolve it. Unfortunately, we
can't
confirm it yet, as we are in the process of upgrading and testing.
I believe this is documented as an "internal" Forté bug report.
Hope this hels.
Daniel Désy
BORN
----- Original Message -----
From: "Pabbaraju, Ramarao (EXP N-IONIDEA)" <ramarao.pabbarajulmco.com>
To: "Forte-Users (E-mail)" <forte-userslists.xpedior.com>
Sent: Tuesday, November 14, 2000 10:46 AM
Subject: (forte-users) No response from Router partition
Hi All,
One of the router partitions on NT server stops responding once in awhile. We can not get to it through escript or econsole and the only
solution we have is to shutdown the ftexec using task manager and start
the partition again. We don't see any error messages in the log except
this line "LbRouter::AttachToRouter - Ignoring DOM version: -1 obj
version: 0". Does anyone have any idea what this means? Is there any way
to figure out the problem? We are using Forte 3L3. Thanks in advance.
Thanks
Ramarao--
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

My guess is, your third service object is not referenced.
-----Original Message-----
From: Forte App [mailto:forteapphotmail.com]
Sent: Wednesday, May 17, 2000 3:08 PM
To: kamranaminyahoo.com
Subject: (forte-users) Partition problem
Hello Everyone,
I have three (3) service objects in my project and when i went into
partition workshop i can only see two service objects instead of three and
all the three service objects properties settings are same
iam using Forte 3.0L2.
Thanks in Advance
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

UV-SO when partitioned and deployed

Hi there,
I have a question related to User-Visible Service
Object(UV-SO) when partitioned and deployed.
According to TechNote 9674:Service Object Visibility,
"if a partition only contains UV-SOs, there will be
one of these partitions per user". This means, if a
partition only contains a UV-SO, this UV-SO is reachable
outside its partition.
I did some tests. I let an EV-SO call a UV-SO. When I
ran it in partition workshop(EV-SO and UV-SO are in
separate server partitions), I got exception raised
complaining "Cannot resolve the distributed reference
for the UV-SO". Then I deployed this project with the
same partition configuration, and it works without any
error. It looks like there is difference between
partitioning and deploying. What the TechNote(9674)
mentions is correct for deployment, but not for
partition workshop.
Does anybody have any idea about this?

It would appear that the error has now been corrected. There were three things I changed: the startup.aliases file in the startup directory on the target (home:/lvuser/natinst/bin) had "localhost" set as the alias for the controller. I changed this to the controller's IP address. Next, I had some file I/O functions in my RT application which used paths relative to the path obtained with the "Current VI's Path" VI. As this path changes depending on location / execution system, I had to create a VI which used the Application:Kind property with a case structure to appropriately strip / build the desired data file paths regardless of execution system. This may have broken my RT application. Finally, I had a property node in one of my RT SubVIs which attempted to modify an indicator in the SubVI, which is not supported in a compiled RT executable. I may have done this for debugging purposes somewhere along the way, but in any case, I removed it, and after recompiling and deploying the RT executable, everything seems to be working as intended now. The host VI on the desktop computer can connect to the RT application through the project, and when compiled into an executable, that works too.

Deploy project from Workshop onto production server

Hi all,
How do I deploy a project I made in the workshop to a remote production
server?
I 've tried several ways:
- With application settings in workshop: hangs (even when I copied the
domain from the server and used that)
- From weblogic builder: hangs
- Building an ear with weblogic builder and deploying that from console.
I get this exception with the last one:
Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
application DeleteApp on portalServer.:
Exception:weblogic.management.ApplicationException: [J2EE:160079]There is no
module defined with the uri .workshop/DeletedWEb/EJB/ProjectBeans which is
used in the classloader-structure declaration in weblogic-application.xml
for DeleteApp.
Thank you for any and all help,
Geoffrey

How about Build > Build EAR menu in WLW? And then deploy the EAR?
"Geoffrey" <[email protected]> wrote in message
news:[email protected]..
Hi all,
How do I deploy a project I made in the workshop to a remote production
server?
I 've tried several ways:
- With application settings in workshop: hangs (even when I copied the
domain from the server and used that)
- From weblogic builder: hangs
- Building an ear with weblogic builder and deploying that from console.
I get this exception with the last one:
Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
application DeleteApp on portalServer.:
Exception:weblogic.management.ApplicationException: [J2EE:160079]There isno
module defined with the uri .workshop/DeletedWEb/EJB/ProjectBeans which is
used in the classloader-structure declaration in weblogic-application.xml
for DeleteApp.
Thank you for any and all help,
Geoffrey

Slow response and access of Weblogic Portal Workshop 8.1 sp3

Hi All,
Environement : Weblogic Portal 8.1 sp3
Weblogic Portal Workshop 8.1 sp3
Windows XP
Problem:
When the application initially opens up in Weblogic Portal Workshop , the scanning takes too much time.At that time CPU usage is almost 100% with only Weblogic Portal Workshop running. Our application has a webapplication module whose build also takes almost 20 mins. After a build , the workshop hangs with 'Out of memory' error.
Size of our application is almost 200 MB (source code with library files). The application also uses almost 60 .JCS and .JCX files.
Solutions we tried.
1. The RAM memory was upgraded to 2GB with a processor speed of 3.3 GHz
2. We have updated the workshop.cfg with the parameter of -XX:-UseThreadPriorities -Xmx768m
Thanks a lot in advance

We have had some of the same problems with our 8.1.3 portal. The performance is terrible in Workshop.
Unfortunally i dont have that much more advice then that you could try to split your application into several projects to reduce the strain on Workshop and hopefully reduce the build time.
Edited by: user10429043 on 2008-okt-23 01:29

Exporting/Importing partition schema

Hi,
We are trying to manage multiple repositories for a project and in
particular we use a devopment/test rep and a production rep ( containing a
production plans snapshot ).
When a plan is moved from a development repository to the production one,
the partitioning previously done is lost. In this case developers have to
partition from scratch.
Moreover in our repository management policy ( apart clean up ) , we
destroy periodically development repository and import saved plans in a new
created one. This procedure causes the same problem described before.
Is there any chance to export the partition schema done in development
repository in order to re-apply the partitioning to the same plan in new
one, using fscript ?
Is there any other way to do it ( maybe via repository hooks and a tool
application ) ?
Thanx
Fab

Fabrizio,
We have a tool that will do this, and a number of other things for you. It
not only saves partitioning information, but it also:
* Reads your application defintion, along with the partitioning information
from the repository,
* Creates deployment and installation scripts,
* Analyzes your application for over 20 different performance and
scalability problems,
* Captures the supplier plan relationships for each partition as well as
for the entire application,
* Graphically shows partitioning structure, similar to partition workshop,
along with all partition and service object properties,
* Has Web and IIOP property sheets which are read from the application,
* Saves operational information, such as outage schedules and external
interfaces,
* Records special runtime properties of classes in your system
We offer this as part of our "Designing for Deployment" workshop. You can
send me a separate message for information about the workshop and the tool.
Don
At 06:35 PM 4/10/98 +0200, Fabrizio Barbero wrote:
Hi,
We are trying to manage multiple repositories for a project and in
particular we use a devopment/test rep and a production rep ( containing a
production plans snapshot ).
When a plan is moved from a development repository to the production one,
the partitioning previously done is lost. In this case developers have to
partition from scratch.
Moreover in our repository management policy ( apart clean up ) , we
destroy periodically development repository and import saved plans in a new
created one. This procedure causes the same problem described before.
Is there any chance to export the partition schema done in development
repository in order to re-apply the partitioning to the same plan in new
one, using fscript ?
Is there any other way to do it ( maybe via repository hooks and a tool
application ) ?
Thanx
Fab
============================================
Don Nelson
Regional Consulting Manager - Rocky Mountain Region
Forte Software, Inc.
Denver, CO
Phone: 303-265-7709
Corporate voice mail: 510-986-3810
aka: [email protected]
============================================
"Until you learn to stalk and overrun, you can't devour anyone" - Hobbes

Recreate JUST x86boot partition

How can I recreate just my x86boot partition, without reinstalling all of solais 8 x86?
I managed to nuke the info in that partition. sigh.

To: [email protected]
Subject: Re: [solarisx86] Re: mboot doesn't show x86 partitions and hangs
I got it working with additional steps and information source (
http://forum.sun.com/thread.jsp?forum=11&thread=2558 ) documented
below. Thanks for your help!!
Juergen Keil wrote:
To reinstall the boot manager in the x86 Boot fdisk partition
mkfs -F pcfs -o b=BOOT,B=/boot/mdbootbp,s,i=/boot/strap.com
/dev/rdsk/c0d0p0:boot
I found another reference which suggested having a 'S'. I don't know
what it does but I used it and it worked out. Perhaps it calls the
DCA? I'm not sure.
mkfs -F pcfs -o b=BOOT,B=/boot/mdbootbp,S,s,i=/boot/strap.com
/dev/rdsk/c0d0p0:boot
>>>
>>>
I'm not sure about the difference between /boot/mdboot and the
/boot/mdbootbp file. I copied that command from Mariuz'
multiboot.solaris-x86.org site.
I guess one version is intended to boot from a FAT12 pcfs filesystem
inside an fdisk partition (X86 Boot fdisk partition), and the other
one tries to boot from a FAT12 pcfs filesystem that is not contained
inside an fdisk partition (floppy media does not use fdisk partition
tables).
Btw. running strings on /boot/mdboot and /boot/mdbootbp reveals that
mdboot contains the string "Solaris Boot Sector Version 1" while
mdbootbp contains "Solaris Boot Sector Version 2" !
If you're sure that the system reported "Version 2" before
HDD booting stopped working, then mdbootbp appears to be correct.
Is it possible that
<URL:http://docs.sun.com/db/doc/817-1658/6mhcgstor?a=view> has
the descriptions for the /boot/mdboot and /boot/mdbootbp file
swapped?
You are right, they have it wrong. mdbootbp is correct, because I now
have it working with mdbootbp!
>
>
>
Then mount the FAT filesystem and copy the /boot files from the
CD to it:
mount -F pcfs /dev/dsk/c0d0p0:boot /mnt
cp -r /boot/* /mnt
Do not overwrite strap.com!
I think this is the likely reason I had trouble before when following
the directions at http://multiboot.solaris-x86.org/iii/1.html .
I created a /tmp/boot.copy directory with everything in /boot except
'strap.com'.
cp -r /boot.CopyWithoutStrap.com/* /mnt
echo "/boot/ / p"> /mnt/solaris.map
It depends on the fdisk partition type you're booting from:
booting from X86BOOT fdisk partition
====================================
1. master boot record (MBR, sector #0) is loaded (contains mboot)
2. mboot looks at the fdisk partition table and loads the first
sector from the active fdisk partition (partition boot record, PBR)
With an X86BOOT fdisk partition this is the mdbootbp (or mdboot?)
code.
3. mdbootbp loads the hidden system file "strap.com" from the
FAT12 pcfs filesystem
4. strap.com shows the fdisk partition boot selector menu, if there
are two or more fdisk partitions on the disk
5. if you continue to boot from the x86boot fdisk partition, then
strap.com loads and runs boot.bin from the FAT12 pcfs filesystem.
6. boot.bin mounts the FAT12 pcfs filesystem from the X86Boot fdisk
partition to get access to the rest of the files under /boot
(it seems your system stops/hangs at step 3. or 4.)
booting from SOLARIS fdisk partition
====================================
1. master boot record (MBR, sector #0) is loaded (contains mboot)
2. mboot looks at the fdisk partition table and loads the first
sector from the active fdisk partition (partition boot record, PBR)
With an active SOLARIS fdisk partition this is the pboot code.
3. pboot loads the rest of the boot code from the solaris fdisk
partition (bootblk)
4. bootblk loads and runs boot.bin from the ufs partition that is
tagged as "root" (see format command: partition -> print)
5. boot.bin mounts the UFS filesystem from the "root" tagged slice
inside the Solaris fdisk partition to get access to the rest of
the files under /boot
Should I also be using intallboot? The docs only give
examples for use on a solaris partition, not on a X86 boot partition.
For example:
installboot /usr/platform/`uname -i`/lib/fs/ufs/pboot \
/usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0d0s2
installboot is not needed when you boot from an X86BOOT partition.
installboot is needed when you boot from a SOLARIS fdisk partition.
It does not hurt to have valid bootcode on the solaris fdisk
partition installed by installboot, when your system is using
an X86BOOT partition. Think of it as some kind of backup boot code,
in case the X86BOOT partition is damaged :-) This needs a copy
of the the /boot/* files installed on the "root" ufs filesystem to
be usable.
But this would likely destroy my Solaris partition!
No, it shouldn't destroy the Solaris partition. If you look at the
solaris slice table from the partition submenu of format
you should see a small slice tagged "boot" (typically slice s8),
right at the start of the solaris fdisk partition on cylinder 0.
This is where installboot writes the pboot and bootblk code.
Filesystems / swap space should start at cylinders > 0 so nothing
gets destroyed by writing the boot code to cylinder 0.
I did it and it did not destroy the partition! I'll use it later if
needed. Thanks!
Here's an example: Note the boot slice s8:
partition> print
Current partition table (original):
Total disk cylinders available: 524 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 1 - 490 3.75GB (490/0/0) 7871850
1 swap wu 491 - 523 258.86MB (33/0/0) 530145
2 backup wm 0 - 523 4.01GB (524/0/0) 8418060
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
9 unassigned wm 0 0 (0/0/0) 0
pboot is written to sector #0 of slice 8.
sector #1 contains the SunOS disk label.
sector #2 is unused (?)
bootblk is written to sectors #3 and following on slice 8.
On a HDD that can boot from the Solaris fdisk partition, the
following commands should report no cmp differences:
# dd if=/dev/rdsk/c0d0s8 count=1 | cmp /usr/platform/`uname
-i`/lib/fs/ufs/pboot -
1+0 records in
1+0 records out
# dd if=/dev/rdsk/c0d0s8 skip=3 | cmp /usr/platform/`uname
-i`/lib/fs/ufs/bootblk -
cmp: EOF on /usr/platform/i86pc/lib/fs/ufs/bootblk

Re: (forte-users) Hi - Query on XML Import document -Hang

Double check that your XML is valid. I've seen
importDocument hang when I'm missing an end tag.
I don't think it's a validating parser.
Of course, there's no documentation, so.... :)
Chris
--- "Saravanan, Lakshmi N." <lnarayanoxhp.com> wrote:
Hi guys,
I am trying to import an XML document from a
Memory stream object. I
got the example
from this group ( It was very helpful ).
Sample Code :
l_MemStr : MemoryStream = new;
l_MemStr.Open( SP_AM_READ_WRITE );
l_MemStr.WriteText( source = l_XMLData );
l_MemStr.Seek( position=0 );
-- Create a Document object from the memory stream
myDoc : Document = new;
myDoc.importdocument( l_MemStr );
After this line nothing seems to happen.. the
partition just hangs... keeps
the CPU busy.
If i deploy the same in a NT or on a IBM box it
works fine. The problem is
with the Sequent box..( i guess ).
Did any of you guys face a problem like this...
Please let us know..
I would really appreciate it.
Thanks
Laks
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
http://mail.yahoo.com/

Well, Forte have agreed to release a patch for the XML bug on DG Unix with
Forte Version 3.0.M.2. I've attached a related mail with this.
- Charu.
-----Original Message-----
From: Epari, Madhusudhan [mailto:meparioxhp.com]
Sent: Friday, September 01, 2000 7:59 AM
To: 'Amin, Kamran'
Cc: 'forte-userslists.xpedior.com'
Subject: RE: (forte-users) Hi - Query on XML Import document - Hang
I did check the xml by opening it in IE 5.0 for it's well-formedness. Still
it's failing on sequent box.
-----Original Message-----
From: Amin, Kamran [mailto:kamran.aminlendware.com]
Sent: Friday, September 01, 2000 10:55 AM
To: 'Epari, Madhusudhan'
Subject: RE: (forte-users) Hi - Query on XML Import document - Hang
Well not really. One way to check if the xml is valid is to open it in IE
5.0. If its well formed then it will show up otherwise it will give you an
error. Also the document object is not the best code that came out of Forte
and has errors, so this might be a bug you will have to report. And they
are not giving any new patches until 3.5 comes out in 2 months.
ka
-----Original Message-----
From: Epari, Madhusudhan [mailto:meparioxhp.com]
Sent: Friday, September 01, 2000 10:52 AM
To: 'Christopher Fury'
Cc: 'forte-userslists.xpedior.com'
Subject: RE: (forte-users) Hi - Query on XML Import document - Hang
If the XML is invalid it should fail on all boxes. This should be a sequent
specific problem.
Madhu
-----Original Message-----
From: Christopher Fury [mailto:cfuryyahoo.com]
Sent: Friday, September 01, 2000 9:37 AM
To: 'forte-userslists.xpedior.com'
Subject: Re: (forte-users) Hi - Query on XML Import document - Hang
Double check that your XML is valid. I've seen
importDocument hang when I'm missing an end tag.
I don't think it's a validating parser.
Of course, there's no documentation, so.... :)
Chris
--- "Saravanan, Lakshmi N." <lnarayanoxhp.com> wrote:
Hi guys,
I am trying to import an XML document from a
Memory stream object. I
got the example
from this group ( It was very helpful ).
Sample Code :
l_MemStr : MemoryStream = new;
l_MemStr.Open( SP_AM_READ_WRITE );
l_MemStr.WriteText( source = l_XMLData );
l_MemStr.Seek( position=0 );
-- Create a Document object from the memory stream
myDoc : Document = new;
myDoc.importdocument( l_MemStr );
After this line nothing seems to happen.. the
partition just hangs... keeps
the CPU busy.
If i deploy the same in a NT or on a IBM box it
works fine. The problem is
with the Sequent box..( i guess ).
Did any of you guys face a problem like this...
Please let us know..
I would really appreciate it.
Thanks
Laks
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
http://mail.yahoo.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
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

Partition workshop hangs

Similar Messages

Maybe you are looking for