Author Archives: Admin

com.ibm.ws.jsf.configuration.FacesConfigParser parseShared unable to locate : Warning messages

Server console filling with WAS warning messages –

Warning messages on the System out:

[18/05/14 21:42:50:230 BST] 00000029 jsf           W com.ibm.ws.jsf.configuration.FacesConfigParser parseShared FacesConfigParser.parseShared(): unable to locate : [preferred]
[18/05/14 21:42:50:245 BST] 00000029 jsf           W com.ibm.ws.jsf.configuration.FacesConfigParser parseShared FacesConfigParser.parseShared(): unable to locate : [property-metadata]
[18/05/14 21:42:50:245 BST] 00000029 jsf           W com.ibm.ws.jsf.configuration.FacesConfigParser parseShared FacesConfigParser.parseShared(): unable to locate : [favorite-property]
[18/05/14 21:42:50:261 BST] 00000029 jsf           W com.ibm.ws.jsf.configuration.FacesConfigParser parseShared FacesConfigParser.parseShared(): unable to locate : [preferred-children]
[18/05/14 21:42:50:261 BST] 00000029 jsf           W com.ibm.ws.jsf.configuration.FacesConfigParser parseShared FacesConfigParser.parseShared(): unable to locate : [component-metadata]
[18/05/14 21:42:50:339 BST] 00000029 jsf           W com.ibm.ws.jsf.configuration.FacesConfigParser parseShared FacesConfigParser.parseShared(): unable to locate : [unsupported-agents

Solution:
WebSphere server has the IBM version of JSF implementation at the server level. It loads those classes first unless otherwise we specify PARENT_LAST in the deployment descriptor of our web module.

Please check the deployment descriptor of your project web module.


Registering WebSphere MQ JMS client with the application server due to exception

Websphere MQ JMS Client registering error on the application start up

Error:
[8/31/13 22:04:57:897 BST] 0000000e JMSRegistrati E   WMSG1603E: An internal error occurred. It was not possible to register the WebSphere MQ JMS client with the application server due to exception org.osgi.framework.BundleException: An error occurred trying to read the bundle
	at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:94)
	at org.eclipse.osgi.framework.internal.core.Framework.installWorkerPrivileged(Framework.java:823)
	at org.eclipse.osgi.framework.internal.core.Framework$2.run(Framework.java:739)
	at java.security.AccessController.doPrivileged(AccessController.java:241)
	at org.eclipse.osgi.framework.internal.core.Framework.installWorker(Framework.java:790)
	at org.eclipse.osgi.framework.internal.core.Framework.installBundle(Framework.java:734)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.installBundle(BundleContextImpl.java:221)
	at com.ibm.ejs.jms.JMSRegistration.installBundle(JMSRegistration.java:860)
	at com.ibm.ejs.jms.JMSRegistration.destroy(JMSRegistration.java:1031)
	at com.ibm.ws.runtime.component.ContainerImpl.destroyComponents(ContainerImpl.java:1070)
	at com.ibm.ws.runtime.component.ContainerImpl.destroy(ContainerImpl.java:662)
	at com.ibm.ws.runtime.component.ServerImpl.destroy(ServerImpl.java:480)
	at com.ibm.ws.runtime.component.ServerCollaborator$ShutdownHook$1.run(ServerCollaborator.java:688)
	at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4276)
	at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4373)
	at com.ibm.ws.runtime.component.ServerCollaborator$ShutdownHook.run(ServerCollaborator.java:677)
	at com.ibm.ws.runtime.component.ServerCollaborator$StopAction.alarm(ServerCollaborator.java:641)
	at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:91)
	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1593)
Caused by: java.io.IOException: The directory "/usr/websphere6/was61_A2/AppServer/configuration/org.eclipse.osgi/bundles/65/1" could not be created
	at org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(BundleInstall.java:68)
	... 18 more

Solution

Check the permissions on the file system for “org.eclipse.osgi” and
make sure the ownership is set to the “wasdmin”.
this should resolve this error.