This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Product Version: NetBeans IDE Dev (Build 200802191203) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) - create any SOA sample - try to deploy it run-jbi-deploy: [deploy-service-assembly] Deploying a service assembly... host=localhost port=4848 file=C:\...\SynchronousSampleApplication/dist/SynchronousSampleApplication.zip C:\...\SynchronousSample\SynchronousSampleApplication\nbproject\build-impl.xml:211: Failed execution of Deploy: C:\...\SynchronousSample\SynchronousSampleApplication/dist/SynchronousSampleApplication.zip ERROR: (JBIMA1408) Required component sun-bpel-engine is not started on instance server. BUILD FAILED (total time: 0 seconds)
Created attachment 56919 [details] server log
murali, can you check why bpel engine is not started in this case?
I tried to reproduce the error with today's build. I am not able to. Based on the server log it is failing due to non availability of engine configuration (config.properties), name of this file changed beginning of this week. User would encounter this issue if they are using upgrade. Workaround is uninstall and install the latest component. Caused by: javax.jbi.JBIException: QOS-6016:Failed to load configuration C:\Program Files\glassfish-v2ur1\domains\domain1\jbi\components\sun-bpel-engine\install_root\workspace\config.properties: C:\Program Files\glassfish-v2ur1\domains\domain1\jbi\components\sun-bpel-engine\install_root\workspace\config.properties (The system cannot find the file specified) at com.sun.jbi.common.qos.config.ConfigPersistence.loadConfig(ConfigPersistence.java:80) at com.sun.jbi.common.qos.config.ConfigPersistence.loadConfig(ConfigPersistence.java:61) at com.sun.jbi.engine.bpel.BPELSERuntimeConfiguration.restore(BPELSERuntimeConfiguration.java:327) at com.sun.jbi.engine.bpel.BPELSERuntimeConfiguration.<init>(BPELSERuntimeConfiguration.java:103) at com.sun.jbi.engine.bpel.BPELSELifeCycle.init(BPELSELifeCycle.java:132) ... 103 more Caused by: java.io.FileNotFoundException: C:\Program Files\glassfish-v2ur1\domains\domain1\jbi\components\sun-bpel-engine\install_root\workspace\config.properties (The system cannot find the file specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:106) at com.sun.jbi.common.qos.config.ConfigPersistence.loadConfig(ConfigPersistence.java:71) ... 107 more
mpottlapelli, which build you use?
200802191203 is a latest available build for this moment
reopen issue since no answer from developer for long time and it was reproduced on two different computers
still reproducible with NetBeans IDE Dev (Build 200802250003)
Jeff, please verify addon installer is fixed and inform dmitry.
I have just fixed the JBI components Addon installer to rename the bpelse's config property file. I verified and tested that the bpelse can be installed and started in AS. I integrated around 13:30 PST. If you get the Addon installer build after that you should have a good installer.
Dima, In the latest NB 6.1 M2 build (200802251204), the JBI runtime is not the latest version. SOA-BI team fixed their issue today. Please rebuild the installer with the latest JBI runtime.
6.1 M2 build? Hong, are you joking ;) There is no M2 build yet. It is not yet the time to speak about M2. The first M2 build could happen no earlier than March, 3. As for the JBI runtime, we always bundle the latest JBI in the NetBeans installer (both JBI core and JBI components). It is automatically picked up and we do no manual steps to get or to update.
*** Issue 127306 has been marked as a duplicate of this issue. ***
The issue is fixed in build 200802270005. Deployed Sync sample, TRS sample and BluePrint1 sample app with out error. But Sync sample and TRS sample test failed with "junit.framework.AssertionFailedError". Need SOA-BI team to give it a check tomorrow to see if this issue is really fixed.
Tried nightly build 200802270005 and I was able to deploy and test Sync|Async|TRS sample projects without any problem.
verified with Build 200802290610