NOTICE: Significant community changes coming soon
The header menu and the home page on our community will be changing soon. Get more information HERE.
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..
316 views

IBM Websphere discovery problem

I have problem with discovering BPM Cluster resources on IBM Websphere platform. 

The ps command gets process parameters from /proc/<PID>/cmdline. The kernel proc filesystem reads the command line for a process into a  single page of memory, due to which the limit for the command line is  the size of a page, which is 4K or 4096 bytes. There is an known issue in Linux OS that the ps command can only display 4096 characters, but the WebSphere process' length is more than 4096 ,so the process was truncated, that is why we failed to discover it. There are 2 options:

So i did this:

A new feature has been added in RHEL-6.8 and RHEL-7.2 where the /proc/pid/cmdline file length is now unlimited. So i update the kernel to kernel-2.6.32-642.el6 or later.

After all that i still have problems:

Executing plug-in with ID 'websphere_server_domain_unix'
<2016-07-28 08:36:04,344> [DEBUG] [JobExecuterWorker-65:MZ_IPAS_Basic_SW_ADM_Host Resources and Applications by Shell_10.122.32.138] - For process id 24410 found original command line /opt/was/IBM/WebSphere/AppServer/java_1.7.1_64/bin/java -Declipse.security -Dwas.status.socket=43700 -Dosgi.install.area=/opt/was/IBM/WebSphere/AppServer -Dosgi.configuration.area=/opt/was/IBM/WebSphere/Profiles/BPM_SB1_PS/servers/SB1.AppCluster_server1/configuration -Dosgi.framework.extensions=com.ibm.cds,com.ibm.ws.eclipse.adaptors -Xshareclasses:name=webspherev85_1.7.1_64_%g,nonFatal -Dcom.ibm.xtq.processor.overrideSecureProcessing=true -Xcheck:dump -Xbootclasspath/p:/opt/was/IBM/WebSphere/AppServer/java_1.7.1_64/jre/lib/ibmorb.jar:/opt/hpDiag/JavaAgent/DiagnosticsAgent/classes/IBM/1.7.0/instr.jre -Dorg.osgi.framework.bootdelegation=* -classpath /opt/was/IBM/WebSphere/Profiles/BPM_SB1_PS/properties:/opt/was/IBM/WebSphere/AppServer/properties:/opt/was/IBM/WebSphere/AppServer/lib/startup.jar:/opt/was/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/was/IBM/WebSphere/AppServer/lib/jsf-nls.jar:/opt/was/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/was/IBM/WebSphere/AppServer/lib/urlprotocols.jar:/opt/was/IBM/WebSphere/AppServer/deploytool/itp/batchboot.jar:/opt/was/IBM/WebSphere/AppServer/deploytool/itp/batch2.jar:/opt/was/IBM/WebSphere/AppServer/java_1.7.1_64/lib/tools.jar -Dibm.websphere.internalClassAccessMode=allow -verbose:gc -Xms1536m -Xmx10240m -Xcompressedrefs -Xscmaxaot4M -Dws.ext.dirs=/opt/was/IBM/WebSphere/AppServer/java_1.7.1_64/lib:/opt/was/IBM/WebSphere/Profiles/BPM_SB1_PS/classes:/opt/was/IBM/WebSphere/AppServer/classes:/opt/was/IBM/WebSphere/AppServer/lib:/opt/was/IBM/WebSphere/AppServer/installedChannels:/opt/was/IBM/WebSphere/AppServer/lib/ext:/opt/was/IBM/WebSphere/AppServer/web/help:/opt/was/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime -Dderby.system.home=/opt/was/IBM/WebSphere/AppServer/derby -Dcom.ibm.itp.location=/opt/was/IBM/WebSphere/AppServer/bin -Djava.util.logging.configureByServer=true -Duser.install.root=/opt/was/IBM/WebSphere/Profiles/BPM_SB1_PS -Djava.ext.dirs=/opt/was/IBM/WebSphere/AppServer/tivoli/tam:/opt/was/IBM/WebSphere/AppServer/java_1.7.1_64/jre/lib/ext -Djavax.management.builder.initial=com.ibm.ws.management.PlatformMBeanServerBuilder -Dpython.cachedir=/opt/was/IBM/WebSphere/Profiles/BPM_SB1_PS/temp/cachedir -Dwas.install.root=/opt/was/IBM/WebSphere/AppServer -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Dserver.root=/opt/was/IBM/WebSphere/Profiles/BPM_SB1_PS -Dcom.ibm.security.jgss.debug=off -Dcom.ibm.security.krb5.Krb5Debug=off -Dcom.ibm.ws.webservices.startup.wsdl.suppressMessages=INFO -Dcom.ibm.ejs.j2c.J2CServerListener.deferEndpointActivation=true -Dcom.ibm.ws.runtime.enableRestartableCULibraries=true -DHttpSessionIdReuse=true -Dteamworks.tester.appServerPort=9084 -Dteamworks.applicationServerPlatform=WebSphere 6.1 -Dteamworks.server.home=/opt/was/IBM/WebSphere/Profiles/BPM_SB1_PS/config/cells/BPM_SB1_11426539173797/nodes/BPM_SB1_PS_11426539173798/servers/SB1.AppCluster_server1/process-server -Dorg.apache.axis.EngineConfigurationFactory=com.lombardisoftware.core.axis.configuration.EngineConfigurationFactoryProxy -Daxis.Compiler=org.apache.axis.components.compiler.Javac -Djava.awt.headless=true -Dclient.encoding.override=UTF-8 -Dcom.ibm.websphere.naming.jndi.security.jndionly=true -Dorg.eclipse.emf.common.util.URI.archiveSchemes=archive jar zip wsjar -Dcom.ibm.websphere.webservices.attachment.tempfile.expiration=600 -Dcom.ibm.ws.cdi.immediate.ejb.start=true -Dcom.ibm.websphere.webservices.http.maxConnection=100 -Dcom.ibm.ws.websvcs.transport.outbound.connection.forceCleanUpPoolTimeSec=1000 -Xscmx120m -Xgcpolicy:gencon -Xjit:iprofilerMemoryConsumptionLimit=67108864 -Xmns256m -Xmnx768m -Xgc:preferredHeapBase=0x100000000 -Xverify:none -Dsun.net.http.allowRestrictedHeaders=true -Declipse.bundle.setTCCL=false -Duser.language=en -Duser.region=US -javaagent:/opt/hpDiag/JavaAgent/DiagnosticsAgent/lib/probeagent.jar -Xshareclasses:none -Dprobe.id=BPMSB1PS1_APP -Dcom.ibm.ws.wspolicy.ignoreWSP12inPackagedWSDL=true -Dprobe.log.dir=/gpfs/TSProdFS/TSCommonShare/CustomScripts/hpDiag/logs -Djava.library.pa
<2016-07-28 08:36:04,344> [DEBUG] [JobExecuterWorker-65:MZ_IPAS_Basic_SW_ADM_Host Resources and Applications by Shell_10.122.32.138] - Failed to parse out cell name and server name from command line
<2016-07-28 08:36:04,344> [WARN ] [JobExecuterWorker-65:MZ_IPAS_Basic_SW_ADM_Host Resources and Applications by Shell_10.122.32.138] - Instance of application 'WebSphere on Unix' is ignored, reason: WebSphere details cannot be acquired, ignoring the application

 It looks like that some scripts for parsing and discovery are not ok? Any idea?

For HP support guys if you are reading this...i have SR opened with this issue - ID: 5309905660. SR is opened from April 22 with no resolution  yet. This is taking too long....

0 Likes
1 Reply
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Hello Mafna ,

I really suggest to continue the ticket process to get a complete investigation of your issue .

 

Best Regards,

Melissa Carranza Mejias
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation. “
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.