PK84189: FFDC ERROR: JAVA.LANG.UNSUPPORTEDOPERATIONEXCEPTION: HARDWARE ERROR, FUNCTION ENGINEGENERATESEED HAS NO MEANING IN HARDWARE

Fixes are available

APAR status

Closed as program error.

Error description

If a hardware JCE provider is being used, such as IBMJCECCA, the
following FFDC error may be seen during server startup (see
below). No external symptoms have been noticed as a consequence
of this error.

Here is the message in the Joblog showing the FFDC file being
generated:
Trace: 2009/02/10 18:28:25.909 01 t=8C2B58 c=UNK key=S2
(13007002)
   ThreadId: 00000019
   FunctionName: com.ibm.ws.ffdc.impl.FfdcProvider.logIncident
   SourceId: com.ibm.ws.ffdc.impl.FfdcProvider
   Category: INFO
   ExtendedMessage: FFDC1003I: FFDC Incident emitted on
/WebSphere/AppServer/profiles/default/logs/ffdc/PLEX1_SY1_
nodeagent_BBON001_STC59650_0000044800000001_2f352f35_09.02.10_18
.28.25.8856442126091946325279.txt com.ibm.ws.security.auth.rsato
ken.RSAPropagationManager.createSecretKeyToken 185

--
[2/10/09 18:28:25:891 CET]     FFDC
Exception:java.lang.UnsupportedOperationException
SourceId:com.ibm.ws.security.auth.rsatoken.RSAPropagationManager
.createSecretKeyToken ProbeId:185
Reporter:com.ibm.ws.security.auth.rsatoken.RSAPropagationManager
@32463246
java.lang.UnsupportedOperationException: Hardware error,
function engineGenerateSeed has no meaning in hardware
 at
com.ibm.crypto.hdwrCCA.provider.SecureRandom.engineGenerateSeed(
SecureRandom.java:44)
 at
java.security.SecureRandom.generateSeed(SecureRandom.java:343)
 at
com.ibm.ws.security.auth.rsatoken.RSAPropagationManager.createSe
cretKeyToken(RSAPropagationManager.java:205)
 at
com.ibm.ws.security.auth.rsatoken.RSAPropagationManager.<init>(R
SAPropagationManager.java:96)
 at
com.ibm.ws.security.auth.rsatoken.RSAPropagationManager.getInsta
nce(RSAPropagationManager.java:81)
 at
com.ibm.ws.management.util.AdminCertificateHelper.isRSAPropagati
onEnabled(AdminCertificateHelper.java:51)
 at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconne
ct(SOAPConnectorClient.java:319)
 at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(
SOAPConnectorClient.java:211)
 at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
 at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeCons
tructorAccessorImpl.java:45)
 at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Delega
tingConstructorAccessorImpl.java:39)
 at
java.lang.reflect.Constructor.newInstance(Constructor.java:515)
 at
com.ibm.websphere.management.AdminClientFactory.createAdminClien
t(AdminClientFactory.java:358)
 at
com.ibm.ws.management.RoutingTable$Accessor.getConnector(Routing
Table.java:1076)
 at
com.ibm.ws.management.RoutingTable$Accessor.getConnector(Routing
Table.java:1174)
 at
com.ibm.ws.management.RoutingTable$Accessor.resetSession(Routing
Table.java:1220)
 at
com.ibm.ws.management.RoutingTable.addParent(RoutingTable.java:6
49)
 at
com.ibm.ws.management.discovery.NADiscoveryAdapter.updateRouting
Table(NADiscoveryAdapter.java:65)
 at
com.ibm.ws.management.discovery.DiscoveryAdapter.event(Discovery
Adapter.java:261)
 at
com.ibm.ws.management.discovery.DiscoveryService.processQuery(Di
scoveryService.java:320)
 at
com.ibm.ws.management.discovery.DiscoveryService.demux(Discovery
Service.java:517)
 at
com.ibm.ws.management.discovery.Endpoint.demux(Endpoint.java:196
)
 at
com.ibm.ws.management.discovery.transport.TcpConnection.run(TcpC
onnection.java:146)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1527)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server*
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: Hardware JCE provider                   *
*                      IBMJCECCA throws an exception when      *
*                      trying to use generateSeed method       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Since method generateSeed is not supported for
hardware JCE providers such as IBMJCECCA, it throws an
exception when trying to call this method. So, instead of
calling generateSeed method, the supported method nextBytes
is used to generate the random number.

Problem conclusion

The code was fixed so that when the provider is IBMJCECCA, the
correct method is used to generate the random number.

APAR PK84189 is currently targeted for inclusion in Service
Level (Fix Pack) 7.0.0.5 of WebSphere Application Server V7.0.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK84189
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-06
Closed date
2009-05-15
Last modified date
2009-08-03

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 FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK48200
UP09/07/27 P F907

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK84189: FFDC ERROR: JAVA.LANG.UNSUPPORTEDOPERATIONEXCEPTION: HARDWARE ERROR, FUNCTION ENGINEGENERATESEED HAS NO MEANING IN HARDWARE

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

R700 PSY UK48200

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?