APAR status |
Closed as program error.
| Error description
Customer created a new AppServer with one EJB container and one
EJB. They created, then, a model from this AppServer (recursive
and made the AS a clone).
Running an xmlconfig full export works fine and doesn't produce
any error message.
Then, they created another EJB in the AS model EJB Container mod
el.
When they run an Xmlconfig export command, they get following
exceptions:
Unable to populate Element from Attributes com.ibm.ejs.sm.except
ion.AttributeNotSetException: PrimaryKeyCheck
.
The xmlfile is created but there are two attributes missing for
the EJB that was created in the model.
Anyway, the newly created EJB works fine and can be accessed. exceptions:Unable to populate Element from Attributes com.ibm.ejs.sm.exception.AttributeNotSetException: PrimaryKeyCheck.The xmlfile is created but there are two attributes missing forthe EJB that was created in the model.Anyway, the newly created EJB works fine and can be accessed. Local fixProblem summary
Here is a full description of my test under NT with WAS
3.5.3:
1) Start websphere with default configuration (default
server).
2) Remove BeanThereBean in default container.
3) Create a model of default server. Make it a clone (set
checkbox
to create automatically the clone).
4) Export XMLConfig (my export file is test1.xml).
The export works without error.
5) Select the model and create Model of enterprise bean.
Select the BeanThere jar file.
The enterprise bean is created in the model and into the
default
container of the clone (that is normal).
6) Export XMLConfig (my result file is test2.xml)
In this case, XMLConfig return an error but can generate
the xml file
If you look at the test2.xml, we can see that there is no
<primary-key-check> and <db-exclusive-access> of the
EJB Bean
There in the model.
The missing parameters do not influence the functionality
because the
clones are correctly set with the default value. 3.5.3:1) Start websphere with default configuration (defaultserver).2) Remove BeanThereBean in default container.3) Create a model of default server. Make it a clone (setcheckboxto create automatically the clone).4) Export XMLConfig (my export file is test1.xml).The export works without error.5) Select the model and create Model of enterprise bean.Select the BeanThere jar file.The enterprise bean is created in the model and into thedefaultcontainer of the clone (that is normal).6) Export XMLConfig (my result file is test2.xml)In this case, XMLConfig return an error but can generatethe xml fileIf you look at the test2.xml, we can see that there is no, and, of theEJB BeanThere in the model.The missing parameters do not influence the functionalitybecause theclones are correctly set with the default value. Problem conclusion
Adding error message that is more appropriate for this
situation, that is only shown when error condition is
encountered. Temporary fixComments
APAR information | APAR number | PQ49528 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-06-13 | Closed date | 2001-07-10 | Last modified date | 2001-07-10 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|