|
Problem |
Resource attributes changed on an enterprise archive
(.ear) file using the Application Assembly Tool (AAT) will not save. |
|
Solution |
Scenario:
After checking the IBM-generated deployment descriptor files contained
within an enterprise application .ear file, you see that it does not
reflect the changes just made. This scenario can be confusing as it
suggests a problem with the AAT tool.
Cause:
The most common cause of this problem is a corruption in the deployment
descriptor of the xml with the modified attributes (i.e., by directly
editing the file instead of through the console). AAT runs a validation
process that tests for known problems. If the xml doesn't match a pattern
of known problems, then there's no error reported. In a case like this,
corrupted xml that matches no known errors can pass inadvertently. This
causes the old attirbutes to either persist or be replaced by default
values during application runtime.
Example case:
In a particular problem, Enterprise Java™ Beans (EJBs) were not being
passivated and discarded which caused the tranlogs to fill up. The
customer was instructed to set a lower EJB timeout value than that seen in
the traces. The application was redployed with the new settings
succesfully but the problem persisted. After further testing, we found
that the ibm-ejb-jar-ext.xmi file was missing a few parameters (among
them, the session bean's timeout parameter). In order to resolve this
problem, the currupted file was the .ear redeployed without it. The AAT
tool then generated a fresh one with the missing timeout parameter that
had been configured in the console and the beans then behaved as
expected. |
|
|
|
|
|
|