Multi-Foundation Pkg Build Issue

I'm trying to build a package for the first time for our Dev environments using the new port number and have encountered an issue that's new for me. I'm using the correct INI values on the DEP server as far as the new port number goes and as soon as the Server build starts I'm getting a ton of zombie's and then I'm seeing the following errors in the logs:

139561/144WRK:eNetKernelIdle Tue Jul 15 11:33:50.601848ipcmisc.c299
ipcSawRenameCurrentThreadV6: Error: invalid thread SHM index 2

And I am also seeing the following errors for the JDENET_N logs:

147959/334 MAIN_THREAD Tue Jul 15 10:15:44.746944 ipcmisc.c299
process 147959 &ltE812SYS/JDENET_N> registered in entry 4

147959/334 MAIN_THREAD Tue Jul 15 10:15:44.748224 ipcmisc.c299
thread table full for thread 334

147959/334 MAIN_THREAD Tue Jul 15 10:15:44.748400 ipcmisc.c299
API ipcSawImpRegisterProcV6 : main thread for process 147959 failed to register. This thread will not be visible to SAW.


Initially I thought it was somehow an IPC resource issue but I have those ranges separate in the INI files. It acts as though it's a resource conflict of some kind but I can't find what is causing it.

Both of the foundations are currently 8.96C, since I haven't moved to 8.97 on the Dev one yet. I've got the Dev environments running on the new port without a problem so this is the first issue I've seen since setting up the Multi-foundations. Has anyone seen this before? I'll attach the Dev and Prod INI's for comparison if that helps any.

I've been troubleshooting this some more and it looks like UBE's build ok but any BSFN does not. Although when different BSFN's are building they don't all get "stuck" in the same place. This would usually make me lean towards building a Full Pkg, except that if I build the same BSFN on the original port, it works fine.

Hi,

Multifoundation pathcodes should be different.
You can't have a single pathcode (DV811) on two
different foundations.

[ QUOTE ]
Hi,

Multifoundation pathcodes should be different.
You can't have a single pathcode (DV811) on two
different foundations.

[/ QUOTE ]

I have our DV811 and TS811 pathcodes running on port 6113 and our PD811 pathcode running on the original port 6013. I'm trying to build the BSFN for the TS811 pathcode when getting these errors.

Do you recall what the fix was for this particular issue? We seem to be experiencing the exact same thing. Oddly enough, we are in the process of updating our TR (8.96.G1 -> 8.98.3.4) but have not yet done it. In preparation for the activity, we have changed the service port and installed the SM console and agent. Services start clean and users can access the system, but as soon as we kick off a package build, we see these same errors.

Any insight would be greatly appreciated.


8.11SP1 8.96.G1 (preparing for 8.98.3.4 TR update)
iSeries v5r4
WebSphere 5.0