Considering the full path name for the shared object mentioned in the error message, I would guess that there is a configuration file somewhere that indicates where the shared object can be found. Change that configuration file.
the strange thing is that the file is there, and is readable and executable.
the instance of jboss also keeps running. The only thing that the queue is not bound to the oracle advanced Queueing.
The 2 other instances which uses also the same file are running fine on the machine, but they do not use the advanced queueing mechanism
You really should be asking Oracle about this because it is not a JBoss issue (it was Oracle code that attempted to access the shared object, couldn't, and issued the error).