Troubleshooting
Problem
You have created a Service Integration Bus and configured the messaging engine to use a filestore.The filestore is located on NFS v3 file system. After restarting WebSphere Application server, the messaging engine fails to start and java.io.IOException is written to the SystemOut.log.
Symptom
The following errors are logged in the SystemOut.log:
Exception in thread "SIB Activation Thread" java.lang.Error: java.lang.reflect.InvocationTargetException
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorA
ccessorImpl.java:44)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingCons
tructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:516)
at
com.ibm.ws.objectManager.utils.Utils.getImpl(Utils.java:44)
at
com.ibm.ws.objectManager.utils.FileLock.getFileLock(FileLock.java:41)
at
com.ibm.ws.objectManager.ObjectManagerState.<init>(ObjectManagerState.ja
va:408)
at
com.ibm.ws.objectManager.ObjectManager.createObjectManagerState(ObjectMa
nager.java:293)
at
com.ibm.ws.objectManager.ObjectManager.initialise(ObjectManager.java:237
)
at
com.ibm.ws.objectManager.ObjectManager.<init>(ObjectManager.java:197)
at
com.ibm.ws.sib.msgstore.persistence.objectManager.PersistentMessageStore
Impl.start(PersistentMessageStoreImpl.java:354)
at
com.ibm.ws.sib.msgstore.impl.MessageStoreImpl.start(MessageStoreImpl.jav
a:1518)
at
com.ibm.ws.sib.admin.impl.JsMessagingEngineImpl.start(JsMessagingEngineI
mpl.java:609)
at
com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.activate(HAManage
rMessagingEngineImpl.java:995)
at
com.ibm.ws.sib.admin.impl.JsActivationThread.run(JsActivationThread.java
:92)
Caused by:
java.io.IOException: No locks available
at
sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:902)
at
java.nio.channels.FileChannel.tryLock(FileChannel.java:974)
at
java.util.logging.FileHandler.initOutputFiles(FileHandler.java:218)
at
java.util.logging.FileHandler.init(FileHandler.java:180)
at
java.util.logging.FileHandler.<init>(FileHandler.java:545)
Cause
NFS locking was disabled
Resolving The Problem
Enable NFS locking by running the following command:
'/sbin/service nfslock start'
Product Synonym
WebSphere Application Server WAS SIB SIBUS SI BUS
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21628926