Author |
Message
|
Hari |
Posted: Tue Sep 21, 2004 11:46 am Post subject: java.lang.UnsatisfiedLinkError |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
Hi all,
I have MQWF 3.4 SP5 installed on HP-UX, when i try connecting thru the webclient i get the following error:
[color=red]Error: java.lang.UnsatisfiedLinkError: /opt/fmc/lib/libfmcojprf.sl: insufficient room in the address space to load the library.[/color]
If i again try connecting i get the following error:
Error: java.beans.PropertyVetoException: FMC38002E Locator LOC_LOCATOR is not supported
I have gone thru solutions in the prev posts, and have found that everything is in place as suggested.
Please note i have been able to connect thru the webclient a couple of times then it goes booommmmm...just wondering what may be the problem.
Any help will be appreciated.
Rgds,
Hari |
|
Back to top |
|
 |
texan |
Posted: Tue Sep 21, 2004 12:40 pm Post subject: |
|
|
Acolyte
Joined: 25 Feb 2004 Posts: 74
|
When I got the error:
Error: java.beans.PropertyVetoException: FMC38002E Locator LOC_LOCATOR is not supported
I restarted the whole websphere app server (not just the workflow app server) and its gone.
Did you check the disk space on your unix (like df -k)? |
|
Back to top |
|
 |
Hari |
Posted: Tue Sep 21, 2004 12:55 pm Post subject: |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
Yeah i have restarted both the MQWF and WAS several times to no avail.
Also there is ample amount of space on the Unix box. |
|
Back to top |
|
 |
hos |
Posted: Tue Sep 21, 2004 11:36 pm Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002 Posts: 470
|
I think you must increase the heap size of your WAS JVM. You can specify JVM parameters in the admin console or during startup of WAS. |
|
Back to top |
|
 |
Hari |
Posted: Thu Sep 23, 2004 9:39 am Post subject: |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
I did increase the heap size of the WAS JVM, but still the problem persists. |
|
Back to top |
|
 |
trevor.johnson |
Posted: Thu Sep 30, 2004 5:57 am Post subject: |
|
|
Novice
Joined: 30 Sep 2004 Posts: 11
|
I am also getting this error on our new v3.4.0.5 environment running on AIX. I think it may have something to do with moving over some WF v3.3.2 J2EE 1.2 (WAS 4.0) code into our new WF v3.4.0.5 J2EE 1.3 (WAS 5.1) environment. Is that your situation as well? |
|
Back to top |
|
 |
Hari |
Posted: Thu Sep 30, 2004 10:24 am Post subject: |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
We have been using MQWF v3.4 sp5 & WAS v5.0 fp2 on HP-UX 11i all the way.
Its seems to be more like an issue which is specific to this box, since the same config works fine in the other boxes, which we have. Have an PMR opened with IBM on this one. |
|
Back to top |
|
 |
trevor.johnson |
Posted: Thu Sep 30, 2004 10:27 am Post subject: |
|
|
Novice
Joined: 30 Sep 2004 Posts: 11
|
Let me know what you find out I'd love to know how to fix this too! |
|
Back to top |
|
 |
|