| Author |
Message
|
| Shalini |
 Posted: Thu Jun 10, 2004 1:26 am Post subject: Channel exit prog in Solaris |
 |
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
Hi,
We are having the problem in exit prog. Please find the log and FDC file report for Solaris 5.8
--------------------------------------------------------
06/05/04 04:47:59 PM
AMQ6175: The system could not dynamically load the library
/var/mqm/exits/priority. The error message was ld.so.1: amqzlaa0: fatal:
relocation error: file /var/mqm/exits/priority: symbol MQXCLWLN: referenced
symbol not found. The queue manager will continue without this module.
EXPLANATION:
This message applies to UNIX systems. The dynamically loadable file
/var/mqm/exits/priority failed to load correctly due to an internal error. and
the MQ error recording routine has been called.
ACTION:
Check that the file has not been corrupted then use the standard facilities
supplied with your system to record the problem identifier, and to save the
generated output files. Contact your IBM support center. Do not discard these
files until the problem has been resolved.
----- amqxufnx.c : 739 --------------------------------------------------------
06/05/04 04:47:59 PM
AMQ7210: The Cluster Workload exit module could not be loaded.
EXPLANATION:
The Cluster Workload exit module '/var/mqm/exits/priority' could not be loaded
for reason xecU_S_LOAD_FAILED.
ACTION:
Correct the problem with the Cluster Workload exit module
'/var/mqm/exits/priority'
----- amqkcona.c : 438 --------------------------------------------------------
WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday June 03 20:24:11 GMT 2004 |
| Host Name :- FR100TF2C4NDS49 (SunOS 5. |
| PIDS :- 5724B4103 |
| LVLS :- 530.5 CSD05 |
| Product Long Name :- WebSphere MQ for Sun Solaris |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Sep 27 2003 |
| CMVC level :- p530-05-L030926 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000100 (mqm) |
| Program Name :- runmqlsr_nd |
| Process :- 00005334 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 1 1 |
| Arith2 :- 5334 14d6 |
| Comment1 :- SIGHUP
Can any one help me on the same
 |
|
| Back to top |
|
 |
| kevint |
| Posted: Thu Jun 10, 2004 2:11 am Post subject: |
|
|
Newbie
Joined: 25 Aug 2001
Posts: 8
Location: Software Group Services
|
Does your channel exit require any other libraries? If so - have you set up the environment for those libraries to be found?
Also i suggest you check permissions on the channel exit library!
Kevin |
|
| Back to top |
|
|
| Shalini |
| Posted: Thu Jun 10, 2004 10:36 pm Post subject: |
|
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
Hi,
Our real requirment is to configure cluster workload exit (sample priority exit).
This dll works fine in windows environment but in solaris we get the the error 8db while starting the command server.
Can you let me know the names of libraries to load @ runtime and options while compiling.
 |
|
| Back to top |
|
|
| kevint |
| Posted: Thu Jun 10, 2004 11:22 pm Post subject: |
|
|
Newbie
Joined: 25 Aug 2001
Posts: 8
Location: Software Group Services
|
Can you also check if the entry point MQStart function is defined/compiled in your code?
void MQStart()
{
;
} |
|
| Back to top |
|
|
| kevint |
| Posted: Thu Jun 10, 2004 11:50 pm Post subject: |
|
|
Newbie
Joined: 25 Aug 2001
Posts: 8
Location: Software Group Services
|
| Can you also show me how you are compiling/linking? |
|
| Back to top |
|
|
| Shalini |
| Posted: Fri Jun 11, 2004 2:56 am Post subject: |
|
|
Master
Joined: 30 Apr 2002
Posts: 224
Location: India
|
Hai,
These are the steps I followed to compile and link my priority cluster workload exit
cc -c priority.c
ld -G priority.o -o priority -lmqm -lmqmzf
cp priority /var/mqm/exits/
let me know that if u can give me your valuable reply.
 |
|
| Back to top |
|
|
| kevint |
| Posted: Fri Jun 11, 2004 5:58 pm Post subject: |
|
|
Newbie
Joined: 25 Aug 2001
Posts: 8
Location: Software Group Services
|
I have a feeling that you need a ".so" extension on your workload exit library.
Creating and Loading Shared Libraries
Procedures for creating and loading shared libraries are platform dependent. This page provides some answers regarding naming conventions for shared libraries and locating shared libraries.
Naming Conventions
Each Java runtime environment provides a platform-dependent mechanism for mapping between the actual file name of a shared library and the name string that you pass as an argument to the System.loadLibrary method.
Solaris:
The shared library file name requires a "lib" prefix and a ".so" extension. Do not include the "lib" prefix or the ".so" extension for the argument that you pass to the System.loadLibrary method.
Microsoft Windows:
The shared library file name requires a ".dll" extension. Do not include the ".dll" extension for the System.loadLibrary method argument.
MacOS:
No special conventions.
Search Mechanisms
Each Java runtime environment provides its own mechanism that indicates where to find shared libraries for native method implementations. The platform-dependent wrapper script or application shell can use the appropriate mechanism to indicate where shared libraries are located.
Solaris:
The LD_LIBRARY_PATH environment variable defines a list of directories that the Solaris VM searches for shared libraries.
Microsoft Windows:
The Microsoft Windows VM uses a search path that includes the current directory for the process or one of the directories listed in the PATH environment variable.
MacOS:
The Code Fragment Manager provides the search mechanism used by the MRJ VM to find and load a shared library. This search path includes the application folder that contains the Macintosh Java application shell generated by JBindery.
Avoiding Name Conflicts
To avoid file name conflicts, it is best to prepend directories or folders containing shared libraries to search paths, such as the LD_LIBRARY_PATH or PATH environment variables.
Supporting Multiple Platforms
Because a Java application with native methods may support multiple platforms, it helps to organize multiple shared libraries into sub-directories by platform, such as <app-dir>/lib/<platform>. |
|
| Back to top |
|
|
| kevint |
| Posted: Fri Jun 11, 2004 9:30 pm Post subject: Compiler option.. |
|
|
Newbie
Joined: 25 Aug 2001
Posts: 8
Location: Software Group Services
|
Also try the -KPIC option on the compiler line.
e.g.
cc -c -KPIC priority.c
If all of this fails please send me your code.
Cheers
Kevin |
|
| Back to top |
|
|
|
|
