|
This
table lists the enhancements and fixes
in fix pack version 7.0.0.1.
|
|
Enhancements
|
|
There are no
enhancements in this fix pack.
|
|
Fixes
|
|
1
|
77930
|
|
Printing out the
AdapterFoundationClasses version in the
Logs/traces.
|
|
Symptom:
Currently with all the
adapters , The AFC version
is not printed out in the
logs/traces. It would be
really helpful to have this
information printed out to
the logs/traces especially
in debugging issues due to
conflicting AFC being
loaded at runtime.
|
|
Resolution:
print AFC version in the
trace
|
|
|
2
|
99888
|
|
Change to use
PmiRmJmxService MBean to get arm
transaction factory name.
|
|
Symptom: When
adapter gets ARM
transaction factory name to
process ARM transaction, a
WAS internal private API is
used for it, which need to
be replaced with public
interfaces.
|
|
Resolution:
Switched to Invoke
PmiRmJmxService MBean, a
set of public interfaces
exposed by WAS to get ARM
transaction fatory
name.
|
|
|
3
|
100262
|
|
Ambiguous semantics of
the max connection number in the event
delivery config
|
|
Symptom: Adapter
will not use connection
pool for event delivery if
max connection number is 1
and delivery mode is
"UNORDERED". In this
situation, multiple thread
will share one connection
without thread safe
mechanism, which will cause
exception.
|
|
Resolution: The
fix makes connection pool
be used when max connection
number is 1, connection
pool keep thread safe and
thus is recommended to use
under "UNORDERED" and
"ORDERED BY KEY" delivery
mode; If user preferred not
to use connection pool,
he/she could set max
connection number to 0,
while thread safe will not
be guaranteed.
|
|
|
4
|
100356
|
|
When BO name is same
and BO namespace is different, inbound
work may be failed.
|
|
Symptom: When
adapter creates 2 or more
different modules with BO
having same name but
different namespace and
structure, inbound and
outbound operations of
those modules will throw
NullPointerException.
|
|
Resolution:
Redefined the methods of
"hashCode()" and "equals()"
in the SDOV1Type class.
Then individual adapter can
distinguish those BO
correctly by "namespace +
name" if those BOs name are
equal.
|
|
|
5
|
100406
|
|
Adapter will encoutner
NPE after restart the app on
server!
|
|
Symptom: For
Adapter inbound and
outbound
operation(standalone
deployment), after the
application is restarted,
the NullPointerException
will appear when the
adapter tries to query the
ASI Infor from cache.
|
|
Resolution: The
BO's namespace and name has
been preserved as BO
instance's fields. After
the application is
restarted, adapter can
still get them from those
instance's field rather
than the stale data
cache.
|
|
|
6
|
100419
|
|
BS shortname: If the
name of IO and IC is the same, one xsd
will be overwritten.
|
|
Symptom: When
the name of Integration
object (IO) and Integration
Component (IC), the schema
file for service binding
will missed after EMD.
|
|
Resolution: Add
a prefix "BS" for schema
file if generated file has
same file name.
|
|
|
7
|
100420
|
|
NPE will be thrown if
we choose same inputs across different
method in EMD.
|
|
Symptom: During
EMD, NullPointerException
will ocurr if an
integration object (IO) has
been chosen as input for
several times.
|
|
Resolution: Add
a filter to handle
duplicated IO
selections.
|
|
|
8
|
100421
|
|
If the primary key in
Legacy adapter is not "Id", runtime
will fail.
|
|
Symptom: If
primary key field in WBIA
adapter project is not the
same as EIS side, runtime
will have error after
migration to JCA.
|
|
Resolution:
Retrieve the name of
primary key field from ASI,
just like normal fields
do.
|
|
|
9
|
100430
|
|
Memory leak in WAS
Inbound with BeanType.
|
|
Symptom: When
adapter caches some
BeanTypes that have a great
deal of properties, java
OutOfMemmory Exception be
thrown during performing
inbound and outbound
operation with some events
(persisting 20-50 times in
WAS broker).
|
|
Resolution:
When adapter creates 2 or
more different modules with
BO having same name but
different namespace and
structure, inbound and
outbound operations of
those modules will throw
NullPointerException.
|
|