Running project in TIBCO BusinessEvents (BE) 5.2.2 Studio fails with UnSatisfiedLink Error
Article ID: KB0087038
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Description:
This was a brand new installation of BE 5.2.2. The application was run in the Studio debugger and gave the error stack as given in "Symptoms".
Symptoms:
2016 Mar 14 14:25:45:221 GMT -5 WN-MOA6FBY6Q275.us.bank-dns.com Fatal [main] - [container.standalone] null
java.lang.ExceptionInInitializerError
at com.tibco.as.space.ASCommon.setFileLogging(ASCommon.java:160)
at com.tibco.cep.runtime.service.dao.impl.tibas.ASDaoProvider.initHook(SourceFile:229)
at com.tibco.cep.runtime.service.om.impl.AbstractDaoProvider.init(AbstractDaoProvider.java:71)
at com.tibco.cep.runtime.service.cluster.MultiAgentCluster.init(MultiAgentCluster.java:109)
at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initCluster(RuleServiceProviderImpl.java:763)
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)
Caused by: com.tibco.as.space.RuntimeASException: java.lang.UnsatisfiedLinkError: C:\TIBCO_NEWBE5.2.2\as\2.1\lib\as-common.dll: %1 is not a valid Win32 application
at com.tibco.as.space.impl.NativeImpl.loadLibrary(NativeImpl.java:47)
at com.tibco.as.space.impl.NativeImpl.init(NativeImpl.java:31)
at com.tibco.as.space.impl.NativeImpl.<clinit>(NativeImpl.java:23)
... 8 more
Caused by: java.lang.UnsatisfiedLinkError: C:\TIBCO_NEWBE5.2.2\as\2.1\lib\as-common.dll: %1 is not a valid Win32 application
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary1(Unknown Source)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at com.tibco.as.space.impl.NativeImpl.loadLibrary(NativeImpl.java:39)
... 10 more
System exit requested by thread [main] with status: -1
System.exit(..) will be invoked now with status: -1
2016 Mar 14 14:25:45:221 GMT -5 WN-MOA6FBY6Q275.us.bank-dns.com Info [CTRL-C] - [runtime.session] Shutting down service provider: WN-MOA6FBY6Q275.us.bank-dns.com
com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl@627582034 is being shutdown by thread [CTRL-C]. Trace follows.
com.tibco.cep.runtime.session.RuleServiceProviderManager$ShutdownThread.run(RuleServiceProviderManager.java:297)
Cause:
Run Configuration in the debugger had a bad PATH statement and is either picking up a wrong version of as-common.dll or not picking it up at all.
This was a brand new installation of BE 5.2.2. The application was run in the Studio debugger and gave the error stack as given in "Symptoms".
Symptoms:
The full error stack follows:
2016 Mar 14 14:25:45:221 GMT -5 WN-MOA6FBY6Q275.us.bank-dns.com Fatal [main] - [container.standalone] null
java.lang.ExceptionInInitializerError
at com.tibco.as.space.ASCommon.setFileLogging(ASCommon.java:160)
at com.tibco.cep.runtime.service.dao.impl.tibas.ASDaoProvider.initHook(SourceFile:229)
at com.tibco.cep.runtime.service.om.impl.AbstractDaoProvider.init(AbstractDaoProvider.java:71)
at com.tibco.cep.runtime.service.cluster.MultiAgentCluster.init(MultiAgentCluster.java:109)
at com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl.initCluster(RuleServiceProviderImpl.java:763)
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)
Caused by: com.tibco.as.space.RuntimeASException: java.lang.UnsatisfiedLinkError: C:\TIBCO_NEWBE5.2.2\as\2.1\lib\as-common.dll: %1 is not a valid Win32 application
at com.tibco.as.space.impl.NativeImpl.loadLibrary(NativeImpl.java:47)
at com.tibco.as.space.impl.NativeImpl.init(NativeImpl.java:31)
at com.tibco.as.space.impl.NativeImpl.<clinit>(NativeImpl.java:23)
... 8 more
Caused by: java.lang.UnsatisfiedLinkError: C:\TIBCO_NEWBE5.2.2\as\2.1\lib\as-common.dll: %1 is not a valid Win32 application
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary1(Unknown Source)
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at com.tibco.as.space.impl.NativeImpl.loadLibrary(NativeImpl.java:39)
... 10 more
System exit requested by thread [main] with status: -1
System.exit(..) will be invoked now with status: -1
2016 Mar 14 14:25:45:221 GMT -5 WN-MOA6FBY6Q275.us.bank-dns.com Info [CTRL-C] - [runtime.session] Shutting down service provider: WN-MOA6FBY6Q275.us.bank-dns.com
com.tibco.cep.runtime.session.impl.RuleServiceProviderImpl@627582034 is being shutdown by thread [CTRL-C]. Trace follows.
com.tibco.cep.runtime.session.RuleServiceProviderManager$ShutdownThread.run(RuleServiceProviderManager.java:297)
Cause:
Run Configuration in the debugger had a bad PATH statement and is either picking up a wrong version of as-common.dll or not picking it up at all.
Issue/Introduction
Running project in TIBCO BusinessEvents (BE) 5.2.2 Studio fails with UnSatisfiedLink Error
Resolution
Go to 'Run Configurations' > 'Environment' and verify that the PATH setting is correct. It must include the full path to the as/lib. For instance: "c:/tibco/BE522/be/5.2/hotfix/bin;c:/tibco/BE522/be/5.2/bin;c:/tibco/BE522/as/2.1/lib".
Feedback
Yes
No
Powered by
