PI08242: SCA OASIS APPLICATION IS UNABLE TO START DUE TO UNRESOLVED IMPOR TS

Fixes are available

APAR status

Closed as program error.

Error description

SCA OASIS application is unable to start due to unresolved
import

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V8.5.5.1                             *
****************************************************************
* PROBLEM DESCRIPTION: SCA OASIS application fails to start    *
*                      with                                    *
*                      ValidationException due to unresolved   *
*                      imports                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
SCA runtime is unable to resolve java package or namespace
imports recursively between dependent contributions, if the
contributions are packaged in separate jars.
Usecase is contribution1 --> imports namespace/java package
from --> contribution2 --> imports namespace/java package from
--> contribution3. In this case, when contribution1 is
starting, SCA runtime fails with the following validation
exception trying to resolve it's dependent contribution,
contribution2's imports.
Caused &#130; &#160;by: &#130; &#160;org.apache.tuscany.sca.monitor.ValidationExcept
 &#130; &#160; &#130; &#160;
[Contribution: &#130; &#160;contribution2.jar] &#130; &#160;-
 &#130; &#160;Unresolved &#130; &#160;import: &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160;
Import &#130; &#160;= &#130; &#160;nm1:test:c1 &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160;
 &#130; &#160;at &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130;
 &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160;
org.apache.tuscany.sca.monitor.Monitor.analyzeProblems(Monitor.j
ava:356)
 &#130; &#160;at &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130;
 &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160;
org.apache.tuscany.sca.impl.NodeImpl.validateContribution(NodeIm
pl.java:
351) &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160;
 &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160;
 &#130; &#160;at &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130;
 &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160;
com.ibm.ws.soa.sca.admin.oasis.runtime.tuscany.SCATuscanyOasisRu
ntimeHandlerImpl.startModule(SCATuscanyOasisRuntimeHandlerImpl.j
ava:192) &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160;
 &#130; &#160;at &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130;
 &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160; &#130; &#160;
com.ibm.ws.soa.sca.admin.runtime.impl.SCARuntimeImpl.start(SCARu
ntimeImpl.java:481)

Problem conclusion

Service Component Architecture(SCA) OASIS runtime code is
fixed to support processing of dependent contributions imports
recursively.

The fix for this APAR is currently targeted for inclusion in
fix pack 8.5.5.2.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PI08242
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-12-16
Closed date
2014-01-02
Last modified date
2014-01-02

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI08242: SCA OASIS APPLICATION IS UNABLE TO START DUE TO UNRESOLVED IMPOR TS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R850 PSY

Document Information

Share your feedback

Need support?