which tag do you mean? It looks like the forum software swallowed it.
Where do you deploy the web app to (which directory)?
The swallowed tag is "distributable".
... and all our webapps are deployed in the "deploy" directory. All our webapps match the "jboss.management.local:J2EEApplication=null,J2EEServer=Local,j2eeType=WebModule,name=..." pattern in the jmx-console (even those with the distributable tag), but we can see only 12 out of our 14 webapps.
PLEASE HELP !!!!
Another information : the DeploymentUtility.getVhosts returns the list of the mbeans corresponding to the pattern : "jboss.web:host=%host%,path=" + WarDiscoveryHelper.getContextPath(contextRoot)
There is no clustered webapp corresponding to this pattern.
Eg : in the jboss.web domain, we have
bsweb-siren is distributable and there is no "host=localhost,path=/bsweb-siren,type=Manager". So, getVHosts returns an empty list.
Any idea ?
I have the impression that this may be fixed in HEAD already (you can use Jopr 2.2 beta 1 to test this).
I will attach a test-war to JOPR-90 -- can you please try this on your Jopr 2.1 instances?
We have this problem with JOPR 2.2 Beta1 (downloaded at the beginnig of march using the download link....not the HEAD version) monitoring a JBoss EAP 4.3.
But we have the WAR-file embedded in an EAR.
Ah, war within ear seems to be the interesting hint. Thanks.
Heiko wrote in JOPR-90 that it is probably a problem of JBossAs.
Is it intended to provide a solution within Jopr or do we have to wait for a patch of JBossAs?
I have the same problem (EAP 4.3 CP02, distributable WAR archive)
I need your help
I've just commited rev 631 to the AS plugin to do some more processing here.
Can you check that out, build and deploy it and then tell me if it helps.
If this does not help, then please report
- what jboss as version, configuration, jvm, deployment directory
- go to jmx-console, search for the MainDeployer Mbean and invoke the listDeployedModules() method. Tell me if your war can be found in there or not.
If the war is found in this output, but not by Jopr, please attach this part of the output to this thread or JOPR-90
If the war is not in the output, report this, perhaps with web.xml and jboss-web.xml and the war name
Also have a look at the agent.log and send me lines related to WarDiscoveryHelper or other *war* classes.
Rev 664 adds code to check for this missing manager (as jprio indicated) - now that I finally was able to reliably reproduce the issue.
For me this was on 4.0.3.sp1, all configuration - the default configuration did not expose the issue.
Can you please test ?
Sorry, but at the moment I have no time to test this issue. I will be back in the middle of july.
Thanks a lot for your help.