Error: "java.io.IOException: Archive entry not found archive:jar:file".

Error: "java.io.IOException: Archive entry not found archive:jar:file".

book

Article ID: KB0094084

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Description:
Issue Summary:
The exception was caused by the selection of the project library resource in the Channel Resource, where the project library name is contained in the path.

Example:
The Project FraudDetectionCache> Channels >SHM >ShipmentEvent.channel has resources defined as 
/SharedConnections-1.08.projlib/SharedConnections/EMSPROD3 JMS Connection.sharedjmscon

It is including "SharedConnections-1.08.projlib" as part of the resource path. It should not include this as part of the path and it should be /SharedConnections/EMSPROD3 JMS Connection.sharedjmscon

Error message:
java.io.IOException: Archive entry not found archive:jar:file:/C:/temp/FraudDetectionCache.ear!/Shared%20Archive.sar!/SharedConnections-1.08.projlib/SharedConnections/EMSPROD3 JMS Connection.sharedjmscon
       at org.eclipse.emf.common.archive.ArchiveURLConnection.getInputStream(ArchiveURLConnection.java:298)
       at org.eclipse.emf.ecore.resource.impl.ArchiveURIHandlerImpl.createInputStream(ArchiveURIHandlerImpl.java:53)
       at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:360)
       at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1269)
       at com.tibco.be.util.config.sharedresources.util.SharedResourcesHelper.loadSharedJmsConnectionDocRoot(SharedResourcesHelper.java:96)
       at com.tibco.be.util.config.sharedresources.util.SharedResourcesHelper.loadSharedJmsConnectionDocRoot(SharedResourcesHelper.java:71)
       at com.tibco.be.util.config.sharedresources.util.SharedResourcesHelper.loadSharedJmsConnectionConfig(SharedResourcesHelper.java:107)
       at com.tibco.cep.driver.jms.JMSChannelConfig.a(SourceFile:105)
       at com.tibco.cep.driver.jms.JMSChannelConfig.<init>(SourceFile:81)
       at com.tibco.cep.driver.jms.JMSDriver.createChannel(SourceFile:24)
       at com.tibco.cep.runtime.channel.impl.ChannelManagerImpl.registerChannel(ChannelManagerImpl.java:112)
       at com.tibco.cep.runtime.channel.impl.ChannelManagerImpl.init(ChannelManagerImpl.java:104)
       at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initChannels(RuleServiceProviderImpl.java:1096)
       at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initCluster(RuleServiceProviderImpl.java:772)
       at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.configure(RuleServiceProviderImpl.java:287)
       at com.tibco.cep.container.standalone.BEMain.jumpStart(SourceFile:163)
       at com.tibco.cep.container.standalone.BEMain.main(SourceFile:70)
2016 Jan 13 10:36:19:076 GMT -8 inferenceSea Debug [main] - [root] System exit requested by thread [main] with status: -1

Resolution

Workaround:
The simple workaround is to manually remove the "*.projlib" segment from the resource path in the Channel editor. For example, if after selecting the resource you see /SharedConnections-1.08.projlib/SharedConnections/EMSPROD3 JMS Connection.sharedjmscon, remove the first segment so that it is /SharedConnections/EMSPROD3 JMS Connection.sharedjmscon .

Note: This issue has been identified as Regression in 5.2.2 (BE-23155) internally by Tibco QA.


Permanent Fix:
BE 5.2.2 HF1 contains a fix for this issue.The project library name is no longer part of the resource path. For the channels that already contain invalid resource paths, they must be manually modified to re-select the shared resource. When you re-select the shared resource, the correct path will be referenced (/SharedConnections/EMSPROD3 JMS Connection.sharedjmscon). There is no fix to run the project with the invalid path; it must be fixed at designtime.



Issue/Introduction

Error: "java.io.IOException: Archive entry not found archive:jar:file".

Additional Information

BE-23155 and BE Engineering