Topic
  • 8 replies
  • Latest Post - ‏2013-08-06T06:16:50Z by SantoshKumarDubey
SystemAdmin
SystemAdmin
938 Posts

Pinned topic Unable to Invoke MDM deployment on AIX box

‏2012-04-18T10:16:15Z |
Hi,

I am trying to deploy OOTB MDM EAR version 9.0.2 on WAS Server on a AIX box. THe deployment is successful.
When i try executing a simple getParty transaction. I am getting the below error.

The following three entries are the higlight from the trace,

java.lang.NoClassDefFoundError: com.dwl.management.config.client.Configuration

java.lang.NoClassDefFoundError: com.dwl.management.BootstrapConfig

Can't find resource for bundle config.bootstrap, key en_US

I have checked that the jars ConfigurationClient.jar and ManagementCommon.jar are present in the EAR and in the DWLCommonEJB path

Please suggest what might be the problem
faultString: java.lang.NoClassDefFoundError: com.dwl.management.config.client.Configuration (initialization failure)
faultActor: null
faultDetail:

java.lang.NoClassDefFoundError: com.dwl.management.config.client.Configuration (initialization failure)
at com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServicesFault.java:282)
at com.ibm.ws.webservices.dispatchers.ejb.J2ee14EJBDispatcher.invoke(J2ee14EJBDispatcher.java:205)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:262)
at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler.invoke(JAXRPCHandler.java:148)
at com.ibm.ws.webservices.engine.handlers.WrappedHandler.invoke(WrappedHandler.java:64)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:262)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:262)
at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:336)
at com.ibm.ws.webservices.engine.transport.http.WebServicesServlet.doPost(WebServicesServlet.java:1131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
at com.ibm.ws.webservices.engine.transport.http.WebServicesServletBase.service(WebServicesServletBase.java:344)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:939)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Caused by: java.lang.NoClassDefFoundError: com.dwl.management.config.client.Configuration (initialization failure)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:140)
at com.dwl.base.util.ServiceLocator.getInstance(ServiceLocator.java:174)
at com.ibm.wcc.service.BaseServiceBean.performTransaction(BaseServiceBean.java:279)
at com.ibm.wcc.service.BaseServiceBean.performServiceOperation(BaseServiceBean.java:118)
at com.ibm.wcc.party.service.PartyServiceBean.getParty(PartyServiceBean.java:328)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at com.ibm.ws.webservices.engine.dispatchers.java.JavaDispatcher.invokeMethod(JavaDispatcher.java:178)
at com.ibm.ws.webservices.dispatchers.ejb.J2ee14EJBDispatcher.invokeMethod(J2ee14EJBDispatcher.java:269)
at com.ibm.ws.webservices.engine.dispatchers.java.JavaDispatcher.invokeOperation(JavaDispatcher.java:141)
at com.ibm.ws.webservices.engine.dispatchers.SoapRPCProcessor.processRequestResponse(SoapRPCProcessor.java:481)
at com.ibm.ws.webservices.engine.dispatchers.SoapRPCProcessor.processMessage(SoapRPCProcessor.java:427)
at com.ibm.ws.webservices.engine.dispatchers.BasicDispatcher.processMessage(BasicDispatcher.java:134)
at com.ibm.ws.webservices.dispatchers.ejb.J2ee14EJBDispatcher.invoke(J2ee14EJBDispatcher.java:168)
... 32 more
Caused by: java.lang.NoClassDefFoundError: com.dwl.management.BootstrapConfig (initialization failure)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:140)
at com.dwl.management.config.client.ConfigurationClientConstants.init(ConfigurationClientConstants.java:55)
at com.dwl.management.config.client.ConfigurationClientConstants.<clinit>(ConfigurationClientConstants.java:51)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at com.dwl.management.config.client.Configuration.<clinit>(Configuration.java:210)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at com.dwl.base.util.ServiceLocator.getInstance(ServiceLocator.java:174)
at com.ibm.wcc.service.BaseServiceBean.performTransaction(BaseServiceBean.java:279)
at com.ibm.wcc.service.BaseServiceBean.performServiceOperation(BaseServiceBean.java:118)
at com.ibm.wcc.party.service.PartyServiceBean.getParty(PartyServiceBean.java:328)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at com.ibm.ws.webservices.engine.dispatchers.java.JavaDispatcher.invokeMethod(JavaDispatcher.java:178)
at com.ibm.ws.webservices.dispatchers.ejb.J2ee14EJBDispatcher.invokeMethod(J2ee14EJBDispatcher.java:269)
at com.ibm.ws.webservices.engine.dispatchers.java.JavaDispatcher.invokeOperation(JavaDispatcher.java:141)
at com.ibm.ws.webservices.engine.dispatchers.SoapRPCProcessor.processRequestResponse(SoapRPCProcessor.java:481)
at com.ibm.ws.webservices.engine.dispatchers.SoapRPCProcessor.processMessage(SoapRPCProcessor.java:427)
at com.ibm.ws.webservices.engine.dispatchers.BasicDispatcher.processMessage(BasicDispatcher.java:134)
at com.ibm.ws.webservices.dispatchers.ejb.J2ee14EJBDispatcher.invoke(J2ee14EJBDispatcher.java:168)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:262)
at com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler.invoke(JAXRPCHandler.java:148)
at com.ibm.ws.webservices.engine.handlers.WrappedHandler.invoke(WrappedHandler.java:64)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:262)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:262)
at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:336)
at com.ibm.ws.webservices.engine.transport.http.WebServicesServlet.doPost(WebServicesServlet.java:1131)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
at com.ibm.ws.webservices.engine.transport.http.WebServicesServletBase.service(WebServicesServletBase.java:344)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:939)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3933)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931)
... 16 more
Caused by: java.util.MissingResourceException: Can't find resource for bundle config.bootstrap, key en_US
at java.util.ResourceBundle.getBundleImpl(Unknown Source)
at java.util.ResourceBundle.getBundle(Unknown Source)
at com.dwl.management.BootstrapConfig.<clinit>(BootstrapConfig.java:39)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at com.dwl.management.config.cache.ConfigurationClientConstants.init(ConfigurationClientConstants.java:55)
at com.dwl.management.config.cache.ConfigurationClientConstants.<clinit>(ConfigurationClientConstants.java:51)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at com.dwl.management.config.cache.CachingLoaderHelperImpl.readManifestFile(CachingLoaderHelperImpl.java:179)
at com.dwl.management.config.cache.CachingLoaderHelperImpl.getApplicationName(CachingLoaderHelperImpl.java:367)
at com.dwl.management.config.cache.TopologySessionCacheLoader.loadData(TopologySessionCacheLoader.java:44)
at com.ibm.mdm.cache.generic.impl.CacheManagerImpl.getCache(CacheManagerImpl.java:232)
at com.dwl.management.config.cache.GenericCacheImpl.<init>(GenericCacheImpl.java:56)
at com.dwl.management.config.cache.CacheFactory.getCache(CacheFactory.java:58)
at com.dwl.management.config.client.Configuration.<clinit>(Configuration.java:185)
... 50 more
Updated on 2012-04-19T16:58:55Z at 2012-04-19T16:58:55Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    938 Posts

    Re: Unable to Invoke MDM deployment on AIX box

    ‏2012-04-18T10:41:14Z  
    Hi,

    I would guess the problem is with the properties.jar in the MDM EAR. This contains the file config/bootstrap.properties.

    The MDM EAR which is in the install tar.gz archive is modified by the product installer before it is deployed to the application server. In particular, the properties.jar is repackaged. If this isn't done, the server can't load the properties files.
    You need to either use the product installer, or make sure you are using the EAR that was modified by the product installer.

    If you are exporting the EAR from the workbench, you need to repackage the properties.jar and the DWLSchemas.jar. However, not all the properties that are set in the workspace files are appropriate outside the development environment. See the Workbench user guide and the Workbench white paper (it's the first post in this newsgroup) for more information.

    Hope that helps, Catherine.
  • SystemAdmin
    SystemAdmin
    938 Posts

    Re: Unable to Invoke MDM deployment on AIX box

    ‏2012-04-18T11:05:20Z  
    Hi,

    I would guess the problem is with the properties.jar in the MDM EAR. This contains the file config/bootstrap.properties.

    The MDM EAR which is in the install tar.gz archive is modified by the product installer before it is deployed to the application server. In particular, the properties.jar is repackaged. If this isn't done, the server can't load the properties files.
    You need to either use the product installer, or make sure you are using the EAR that was modified by the product installer.

    If you are exporting the EAR from the workbench, you need to repackage the properties.jar and the DWLSchemas.jar. However, not all the properties that are set in the workspace files are appropriate outside the development environment. See the Workbench user guide and the Workbench white paper (it's the first post in this newsgroup) for more information.

    Hope that helps, Catherine.
    Hi Catherine,

    Just like you mentioned, I have exported the OOTB EAR from the workspace and created properties.jar and DWLSchema.jar from the files in the customerResources folder and packaged them with the EAR and deployed them on WAS.

    However in the development env we give the classpath entries in the WAS JVM.
    I've not given any entries in the JVM classpath on the WAS server on AIX since properties.jar is bundeled in the MDM EAR. I believe this is the way.

    How ever don't you any problem with the classNotFound exception with the below 2 entries:

    java.lang.NoClassDefFoundError: com.dwl.management.BootstrapConfig

    com.dwl.management.config.client.Configuration

    Thanks for looking into this!
  • SystemAdmin
    SystemAdmin
    938 Posts

    Re: Unable to Invoke MDM deployment on AIX box

    ‏2012-04-18T18:15:21Z  
    Hi Catherine,

    Just like you mentioned, I have exported the OOTB EAR from the workspace and created properties.jar and DWLSchema.jar from the files in the customerResources folder and packaged them with the EAR and deployed them on WAS.

    However in the development env we give the classpath entries in the WAS JVM.
    I've not given any entries in the JVM classpath on the WAS server on AIX since properties.jar is bundeled in the MDM EAR. I believe this is the way.

    How ever don't you any problem with the classNotFound exception with the below 2 entries:

    java.lang.NoClassDefFoundError: com.dwl.management.BootstrapConfig

    com.dwl.management.config.client.Configuration

    Thanks for looking into this!
    Catherine,

    We haven't been able to resolve the issue with the properties.jar. Please let me know if see any thing with the steps in the below post.
    Also, Can you please help with the part number for product installer. Is is something available for AIX?

    Thanks!
  • SystemAdmin
    SystemAdmin
    938 Posts

    Re: Unable to Invoke MDM deployment on AIX box

    ‏2012-04-19T09:08:43Z  
    Catherine,

    We haven't been able to resolve the issue with the properties.jar. Please let me know if see any thing with the steps in the below post.
    Also, Can you please help with the part number for product installer. Is is something available for AIX?

    Thanks!
    Hi,

    The MDM installer is included with MDM: you should already have used it to install MDM on AIX originally.

    Open the properties.jar and make sure that it has all the properties files in the root, not in a folder. The folder config should be at the root of the jar file, and contain the bootstrap.properties file.

    The error message that indicates the cause of the problem is:

    Can't find resource for bundle config.bootstrap, key en_US

    java.lang.NoClassDefFoundError: com.dwl.management.BootstrapConfig (initialization failure)

    This looks like the class isn't found, but what is actually happening is that the class BootstrapConfig tries to load the file config/bootstrap.properties - it failed to do so, and as a result couldn't be initialized by the class loader.

    So the problem is that the file config/bootstrap.properties cannot be loaded. It is in the properties.jar file inside the MDM.ear. The jar file might be corrupt, or the file may not be in the right place inside the jar.

    Hope that helps, Catherine.
  • SystemAdmin
    SystemAdmin
    938 Posts

    Re: Unable to Invoke MDM deployment on AIX box

    ‏2012-04-19T15:34:28Z  
    Hi,

    The MDM installer is included with MDM: you should already have used it to install MDM on AIX originally.

    Open the properties.jar and make sure that it has all the properties files in the root, not in a folder. The folder config should be at the root of the jar file, and contain the bootstrap.properties file.

    The error message that indicates the cause of the problem is:

    Can't find resource for bundle config.bootstrap, key en_US

    java.lang.NoClassDefFoundError: com.dwl.management.BootstrapConfig (initialization failure)

    This looks like the class isn't found, but what is actually happening is that the class BootstrapConfig tries to load the file config/bootstrap.properties - it failed to do so, and as a result couldn't be initialized by the class loader.

    So the problem is that the file config/bootstrap.properties cannot be loaded. It is in the properties.jar file inside the MDM.ear. The jar file might be corrupt, or the file may not be in the right place inside the jar.

    Hope that helps, Catherine.
    Catherine,

    We would need to give the the complete path where the properties.jar file is placed on the server.
    I didn't mention the file name rather just gave the path in the JVM class path.

    This solved the problem.

    Also we haven't used any installer to install MDM. But did a manual installation of DB and config.
    I believe you are mentioning the install.bin file in the tar extract.

    Thanks
  • SystemAdmin
    SystemAdmin
    938 Posts

    Re: Unable to Invoke MDM deployment on AIX box

    ‏2012-04-19T16:31:06Z  
    Catherine,

    We would need to give the the complete path where the properties.jar file is placed on the server.
    I didn't mention the file name rather just gave the path in the JVM class path.

    This solved the problem.

    Also we haven't used any installer to install MDM. But did a manual installation of DB and config.
    I believe you are mentioning the install.bin file in the tar extract.

    Thanks
    Hi,

    The properties files are normally loaded from the properties.jar file which is inside the MDM ear. It is not usually necessary to set the JVM class path. This is done in the development environment so that the properties files can be picked up directly from the workspace and not re-packaged every time they are changed.

    Thanks, Catherine.
  • SystemAdmin
    SystemAdmin
    938 Posts

    Re: Unable to Invoke MDM deployment on AIX box

    ‏2012-04-19T16:58:55Z  
    Hi,

    The properties files are normally loaded from the properties.jar file which is inside the MDM ear. It is not usually necessary to set the JVM class path. This is done in the development environment so that the properties files can be picked up directly from the workspace and not re-packaged every time they are changed.

    Thanks, Catherine.
    Yes Catherine. Agree with you. But verified this today, all of our env's have an entry in class path to get things working.
  • SantoshKumarDubey
    SantoshKumarDubey
    2 Posts

    Re: Unable to Invoke MDM deployment on AIX box

    ‏2013-08-06T06:16:50Z  
    Yes Catherine. Agree with you. But verified this today, all of our env's have an entry in class path to get things working.

    I was getting the exact same issue in my windows machine. The solution turns out to be wrong entry in bootstrap.properties file where i was entring wrong 'application.manifest.location' detail.