An AS instance running on HP-UX 11i fails to be discovered when its command line contains 1050 characters. If the command-line arguments are omitted from the AS instance, discovery can be successful but when all necessary arguments are present on the command-line of the AS instance, the instance is not auto-discovered. The same command-line for an AS instance seems to work just fine on Windows or Linux platforms. This is most likely a limitation of the OS. The pstat function that is used to obtain the command-line seems to have a limit of 1020 characters. It appears Sigar uses the pstat_getcommandline function to obtain the processes command-line and the HP documentation indicates that this function is capable of returning up to 1020 characters (http://search.hp.com/redirect.html?type=REG&qt=pstat_getcommandline&url=http%3A//h20000.www2.hp.com/bc/docs/support/SupportManual/c01921366/c01921366.pdf%3Fjumpid%3Dreg_R1002_USEN&pos=1).
Do we have alternative methods of detecting process information or server information that does not rely on Sigar or the native methods provided by the OS? Possibly a fall-back option?
Larry, still an issue?
I am sure this is still an issue. However, from the downstream perspective, HP-UX support was officially dropped in JBoss ON 3.0. As JBoss ON 2.4 is now end-of-life there auto-discovery is not supported on HP-UX. My question in comment 1 still applies but I fear the answer is probably no. However, it does seem that we might be able to at least determine JBOSS_HOME in this case and from that get the rest of the discovery information from the file-system as a fall-back measure.
Larry, thanks for the info. Given what you say I'm closing this as won't fix. But clearly this is something that may be useful as a reference for anyone on HP-UX. And we of course would welcome any submission that helps resolve the issue.