History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RHQ-687
Type: Bug Bug
Status: Closed Closed
Resolution: Not An Issue
Priority: Major Major
Assignee: Jason Dobies
Reporter: Jay Shaughnessy
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
RHQ Project

Webapp (.WAR) delete failing with JBoss EAP 4.3

Created: 17/Jul/08 03:52 PM   Updated: Monday 01:47 AM
Component/s: FX - Content, FX - Inventory
Affects Version/s: 1.1pre
Fix Version/s: 1.1

Time Tracking:
Not Specified

File Attachments: 1. File test1.war (70 kb)

Environment:
recreated with 2.0.0.GA and EAP 4.3.0.GA-CP01
reported in issue #191990 against 2.0.1 and EAP 4.3.0.GA-CP01


Resolution Date: 22/Jul/08 12:46 PM
Date of First Response: 18/Jul/08 03:35 PM


 Description  « Hide

I have seen this so far only with the production EAP configuration but the problem does not always occur, so I don't think we can assume the problem only happens in this configuration. I did not see it happen against JBoss 4.0.4.

1) Unzip EAP
2) Edit jboss-eap-4.3\jboss-as\server\production\conf\jmx-console-users.properties and uncomment the admin=admin line
3) start the EAP server with run.bat (this will invoke the production configuration)
4) Let JON discover and import the server
5) Update the connection properties setting admin:admin credentials
- Avail should go green
6) Create New webapp using the attached webapp (test1.war). Use the "Inventory -> Create New -> WebApp" feature (I used resource name, Test1, package name test1.war)
7) After clicking Create wait for The Resource to show up in the inventory list. Note that this can happen while the status for the create operation still shows "In Progress"

Note, in the agent log I see the following during this process:

2008-07-17 16:40:11,603 ERROR [InventoryManager.discovery-1] (rhq.plugins.jbossas.util.WarDiscoveryHelper)- The deployed WAR 'test1.war' does not have a jboss.web MBean (i.e. context root) associated with it; it will not be added to inventory.

8) Try deleting the webapp from he inventory list:

org.rhq.core.clientapi.agent.PluginContainerException:Resource component container could not be retrieved for resource: 503061

This error usually occurs but not always. It seems the longer you wait the better the chance of success. Note also that despite the ERROR in the agent log the request does result in a Success status.

Finally, If you wait some time and try again sometimes the delete will be successful.





 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jay Shaughnessy - 17/Jul/08 04:08 PM
the jboss servlets-example.war renamed

Jay Shaughnessy - 18/Jul/08 02:51 PM
If the delete operation fails repeatedly, even after a fairly long waiting period after deployment, the workaround is to undeploy/remove the WebApp outside of RHQ and then uninventory the WebApp resource.

Jason Dobies - 18/Jul/08 03:35 PM
This doesn't seem to be related to the EAP in particular. In fact, I believe this is only for WARs deployed through RHQ. More specifically, I think the bug is in the WAR deployment itself.

In any event, the component isn't starting (evidenced by the connection error message if you navigate to the resource itself), which means there is no resource component available to do the delete (this may be a much bigger design issue in and of itself).

I'll keep looking. The next step is to determine if it is just the RHQ-deployed WARs that are failing to start or if some other element is causing any WAR to fail.

Jason Dobies - 21/Jul/08 01:34 PM
I believe this is specific to WARs and actually the issue is in the deployment/discovery of them in the first place. Closing this out to track as JBNADM-3451.