In Progress

Closed topic not solved : JEE Project : error - Bizagi version could not be published ...

Hi,

previous topic here http://feedback.bizagi.com/suite/en/topic/reopen-closed-topic-jee-project-error-bizagi-version-could-not-be-published has been closed before I check the suggested solution.

As suggested, I installed version 10.7.0.2156 but I got exactly same behavior as detailled in previous topic

0e0118fdb8a22028fefc6f3fae2cd50f

occurs when I try to run the JEE project using the Run feature in Studio (from wheel or from toolbar) and then myPC:8080/BizAgi-war URL is not launched at all in my Web browser

However, once I get this mesage, as long as Java services are running, if I type manually the myPC:8080/BizAgi-war URL in my Web browser, the Work Portal starts an I can use it ...

Here atteched 3 log files from test with version 10.7.0.2156

C:\BizagiJEE\10.7.0.2156\BizagiBPMJEE\log\bizagi-bpm.log

C:\BizagiJEE\10.7.0.2156\jboss-eap-6.2\standalone\log\server.log

C:\BizagiJEE\10.7.0.2156\BizagiConsoleManagerJEE\log\console.log

In advance, thanks for solving it.

Regards,

Walter

Comments (10)

photo
1

I also have the same issue when running the script. I am not using the studio to deploy as studio is not available for linux. completed createproject step. Then when running predeploy step, got the exact same error. Any ideas?

[BizagiJEEConsole:PREDEPLOY] Bizagi version --> Generating entities...

[BizagiJEEConsole:PREDEPLOY] Begin: 22/04/2016 11:45:30

[BizagiJEEConsole:PREDEPLOY] ERROR: Bizagi version could not be generated.

Error detail: Error generating entities: Error generating entities: CompileException: null

photo
1

Dear Users,

We analysed the following message log:

16:47:14,048 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment C:\BizagiJEE\10.7.0.2145\jboss-eap-6.2\standalone\deployments\BizAgi-ear-JBoss.ear. Deployment changes will not be processed until all content is complete.

It means that after Bizagi generates project entities (predeploy) and for any unknown reason, Bizagi cannot copy the generated EAR to JBOSS deployment folder: (usually: C:\BizagiJEE\10.7.0.2145\jboss-eap-6.2\standalone\deployments\)

To solve this issue, you need to delete JBOSS temporary files and generated EARs. Please follow these steps:

  • Stop JBOSS service using Windows task Manager killing javaw.exe process

Delete temporary files of JBOSS and generated EAR of the project:

- Temporary file of JBOSS:

74ac9a166d6fbd0b30a9cdb723c404e2

- Generated EARs in JBOSS:

f7b5434925f14534a9f8df4e4c7805f8

- Project Generated EAR:

a801ea79b995a8a96ef83ccd30318784

  • Finally, From Bizagi Studio, click on publish. It should work without any problem
  • Regards

photo
1

Dear Juan,

thnaks for your response.

I'm sorry, but after doing steps you suggested, I get exactly the same error message when publishing and same behavior afterwards.

Here atteched 3 log files from today test after cleaning as you sugegsted

C:\BizagiJEE\10.7.0.2156\BizagiBPMJEE\log\bizagi-bpm.log

C:\BizagiJEE\10.7.0.2156\jboss-eap-6.2\standalone\log\server.log

C:\BizagiJEE\10.7.0.2156\BizagiConsoleManagerJEE\log\console.log

In advance, thanks for solving it.

Regards,

Walter

photo
1

Unfortunately, my issue is in the predeploy step itself.

[BizagiJEEConsole:PREDEPLOY] Bizagi version --> Generating entities...

[BizagiJEEConsole:PREDEPLOY] Begin: 22/04/2016 11:45:30

[BizagiJEEConsole:PREDEPLOY] ERROR: Bizagi version could not be generated.

Error detail: Error generating entities: Error generating entities: CompileException: null

photo
1

Error message from the console log.

This is from the log, /apps/BizagiBPMJEE/BizagiConsoleManagerJEE/log/console.log:

2016-04-22 11:45:30,122 [main] INFO BizAgi.entitygenerator.EntityGeneratorImpl - Generate Entities (Start): Fri Apr 22 11:45:30 EDT 2016

2016-04-22 11:45:32,327 [main] INFO BizAgi.entitygenerator.EntityProducerManager - Get all entities (Begin): Fri Apr 22 11:45:32 EDT 2016

2016-04-22 11:45:33,039 [main] INFO BizAgi.entitygenerator.EntityProducerManager - Get all entities (End): Fri Apr 22 11:45:33 EDT 2016

2016-04-22 11:45:33,043 [main] INFO BizAgi.entitygenerator.EntityProducerManager - Generating Source Code (Begin): Fri Apr 22 11:45:33 EDT 2016

2016-04-22 11:45:34,484 [main] INFO BizAgi.entitygenerator.EntityProducerManager - Generating Source Code (End): Fri Apr 22 11:45:34 EDT 2016

2016-04-22 11:45:34,487 [main] INFO BizAgi.entitygenerator.EntityProducerManager - Compiling (Begin): Fri Apr 22 11:45:34 EDT 2016

2016-04-22 11:45:34,491 [main] ERROR BizAgi.entitygenerator.EntityProducerManager - Error with compiled files Fri Apr 22 11:45:34 EDT 2016

2016-04-22 11:45:34,492 [main] ERROR com.bizagi.console.model.AbstractAppServerManagerDelegate - Error generating entities:

BizAgi.entitygenerator.EntityGeneratorException: Error generating entities: CompileException: null

at BizAgi.entitygenerator.EntityGeneratorImpl.generateAllEntities(EntityGeneratorImpl.java:45)

at com.bizagi.console.model.AbstractAppServerManagerDelegate.buildBizagiVersion(AbstractAppServerManagerDelegate.java:268)

at com.bizagi.console.model.AbstractAppServerManagerDelegate.preDeploy(AbstractAppServerManagerDelegate.java:105)

at com.bizagi.console.controller.AppServerManagerController.preDeploy(AppServerManagerController.java:109)

at com.bizagi.console.view.cmdline.CommandLineView.processRequest(CommandLineView.java:57)

at com.bizagi.console.main.ConsoleMain.main(ConsoleMain.java:20)

2016-04-22 11:45:34,496 [main] ERROR com.bizagi.console.controller.AppServerManagerController -

com.bizagi.console.appserver.AppServerManagerException: Error generating entities: Error generating entities: CompileException: null

at com.bizagi.console.model.AbstractAppServerManagerDelegate.buildBizagiVersion(AbstractAppServerManagerDelegate.java:273)

at com.bizagi.console.model.AbstractAppServerManagerDelegate.preDeploy(AbstractAppServerManagerDelegate.java:105)

at com.bizagi.console.controller.AppServerManagerController.preDeploy(AppServerManagerController.java:109)

at com.bizagi.console.view.cmdline.CommandLineView.processRequest(CommandLineView.java:57)

at com.bizagi.console.main.ConsoleMain.main(ConsoleMain.java:20)

photo
1

Dear Users,

We require to publish the project manually. To do this, please follow these steps:

1. Stop JBOSS services

2. Follow the same steps you did in the before post about to delete JBOSS temporary files and generated EARs.

3. In this case, you will not deploy the project using Bizagi Studio. You will deploy it and start JBOSS service manually.

4. Create the custom EAR (predeploy). Please go to Bizagi JEE console at C:\BizagiJEE\10.7.0.2174\BizagiConsoleManagerJEE\bin

[PROJECT_NAME] parameter is the name of the XML file without the extension. To deploy Distrital107 project, then you need to type: JEEConsoleManager.bat predeploy -p Distrital107

2016-04-26_1447

run the predeploy command with Bizagi JEE Console:

  • In a Unix-like OS such as Linux, use: sh <JEECONSOLE_HOME>/bin/JEEConsoleManager.sh predeploy -o

    <OUTPUT_PATH> -p [PROJECT_NAME] -f <FILE_PATH>

  • In a Windows OS, use: <JEECONSOLE_HOME>\bin\JEEConsoleManager.bat predeploy -o <OUTPUT_PATH>

    -p [PROJECT_NAME] -f <FILE_PATH>

Consider that:

  • <OUTPUT_PATH> is the optional path to specify where the EAR

    file will be generated. Do not use -o if this information is not to be included

    (by default, the output file will be generated as <JEECONSOLE_HOME>\projects\[PROJECT_NAME]\dist\BizAgi-ear-JBoss.ear)

    .

  • [PROJECT_NAME] is the project's name as specified in the XML at

    the <CONFIG_PATH>. Using -p for this parameter is mandatory.

  • <FILE_PATH> is the optional path where the basic .EAR

    distribution file is located (which needs to be referenced to generate the

    final .EAR).

  • This file is initially delivered within the configuration inputs

    as <CONFIGURATION_INPUTS>\BizagiBPMJEE\Bizagi-ear-JBoss.ear.

  • Do not use -f if this information is not to be included (when not

    specified, the location will be taken from the projectemplate.xml.)

  • If your JBoss configuration uses more than 1 node (cluster set

    up), you will need to use -c to specify that the predeploy should run with

    cluster considerations. Absence of this parameter will indicate that no cluster

    is involved (standalone set up).

5. Copy the final EAR of your project into Jboss deploy folder:

From: C:\Bizagi\Projects\[ProjectName]\JEE\dist

To: C:\BizagiJEE\10.7.0.2174\jboss-eap-6.2\standalone\deployments

6. Start Jboss application server,

Starting the Server

To start JBoss Application Server, locate the

<JBOSS_HOME>/bin folder and run the standalone executable file, usually

located in C:\BizagiJEE\10.7.0.2174\jboss-eap-6.2\standalone\bin

  • In Linux OS, run the standalone.sh file from a command prompt with

    the following parameters: standalone.sh -b 0.0.0.0

  • In Windows OS, run the standalone.bat file from a command prompt

    with the following parameters: standalone.bat -b 0.0.0.0

7. Log into Bizagi using your browser: http://localhost:8080/BizAgi-war/

For further information: http://help.bizagi.com/bpmsuite/en/index.html?jee_jboss_deploy.htm

Best Regards

photo
1

Dear Juan,

thanks for your return.

Is this a temporary workaround waiting for final solution in bizagi studio ?

Anyway, I"m not sur we all are in the same case.

More important, in my case (on Windows with bizagi 10.7.0.2174), I'd like to remind that after getting the error message when publishing, I can run the bizagi work portal at myPC:8080/BizAgi-war URL and it works (see my previous posts about it).

So, I can go directly to your step 7. with no need to perform all other 1. to 6. manual steps.

Do you see what I mean ?

Please tell me if you need other information or log files than those already sent.

Waiting for the solution in my case.

Regards,

Walter

.

photo
1

Dear Walter,

Concerning your last comment, we could analyse that the main problem is a timeout which JBOSS cannot send a message to Bizagi Studio informing it is already up and working.

In the following part of log text, we can confirm a timeout message after 5 minutes:

  • 2016-04-26 10:53:13,653 [main] INFO

    BizAgi.entitygenerator.EntityGeneratorImpl - Generate Entities

    (End): Tue Apr 26 10:53:13 CEST 2016

  • 2016-04-26 10:59:47,923 [main] INFO

    com.bizagi.console.model.AbstractAppServerManagerDelegate - The

    application was not deployed. The maximum Timeout was exceeded.

  • 2016-04-26 10:59:48,243 [main] INFO

    com.bizagi.console.view.cmdline.AppServerManagerViewImpl -

    renderCommonResponse: BJEECM_506||Bizagi version could not be published. Check

    server log for details.||null

Our product team has created it to be solved in a future release. At the moment, please discard it as an info message because you are able to work on the work portal.

Thank you for your understanding.

Regards

photo
1

Dear Juan,

thanks for your response.

I will do so and wait for next realease. By the way, what is the target date of next release ?

Regards,

Walter

photo
1

Dear Walter,

There is not a solution at the moment because it a performance problem. It takes longer time than a normal environment. Our product team has created it in the backlog to be developed in a future release, but I do not have a date when it will be included.

Regards

photo