[Gianluca84]

We faced a strange error this morning, we exported an EAR using the “Export…” feature and we installed on a server like we did already many times with the new environment (MyEclipse based).
The update failed in the end and checking the problem we found out that the EAR file itself was not complete, serveral .class files were missing and some of them were present but empty like some jasper files.
Can you explain why this could happen?
Have you ever encounter a similar problem?
There is a way to check the integrity of the generate EAR file?

Later on we exported the same EAR we checked and all was good, the update in this case was infact successfull.
In the end we are not able to determine what caused the faulty EAR the first time.

[support-joy]

Gianluca84,

Sorry to hear you came across this issue. I am afraid, I have never come across this issue nor can I reproduce it. We can investigate this issue if you could provide us steps to reproduce and also provide below details –
1. From MyEclipse IDE menu options click on MyEclipse > Installation Summary > Installation Details and copy and paste the same here
2. From menu options click on Help > About MyEclipse Enterprise Workbench and copy and paste build id and version id here
3. Attach your .log located at [your workspace dir]/.metadata/.log

Sorry for the inconvenience.

[Gianluca84]

1, 3 I’ve attached them to this message.

2.
Version: 9.1 Blue
Build id: 9.1-Blue-20110701

The problem happened just after an Update from the svn server. After the update was successfully complete and there was no task left in the progress view, nor anywere else, we selected a bunch of project and Hit F5. After all the refreshing completed successfully we did the Export… Ear and waited till the end.

There was no errors in the projects during this operations.

I must point out that during the refreshing some NPE Refreshin external folders appears, (our projects are fixed there is no external folder missing). Occasionally this happens but usually closing all projects and opening them up again works. Some other time like this one we just don’t bother.

After the EAR was exported the workspace started up againg rebuilding/refreshing itself like it didn’t finish before, but it did!

A second export after a while was, as I said, successfull.

Attachments:

You must be logged in to view attached files.

[Vittoriano Raffaelli]

Any news on this problem?

We’ve also notices that during the exportation process the windows showing the packaged being processed hangs up and doesn’t respond. Maybe this this is not correlated to the problem though.

[support-joy]

01Informatica,

I am afraid we could not reproduce this issue. Could you please answer below queries –
1. Please elaborate the steps in detail that result in this issue
2. Open MyEclipse IDE, from menu options click on MyEclipse > Installation Summary > Installation Details and copy and paste the same here
3. Clear your .log file located at [your workspace dir]/.metadata/.log, replicate the issue and attach .log
4. What are the third party plugins you have added to your profile? Please list them here, including update site details or weblink to download the plugin
5. Please attach a sample project which results in incomplete exported EAR
6. Please attach a screenshot to help me get a visual

We’ve also notices that during the exportation process the windows showing the packaged being processed hangs up and doesn’t respond. Maybe this this is not correlated to the problem though.

I am afraid, your issue is not clear. Could you elaborate.

[Vittoriano Raffaelli]

Sorry for the delayed response.

1. Our workspace contains many EAR projects, each project contains both jar and WAR modules with every WAR project been dependent on a JAR. We also use JasperReport and we have some ant buildfiles to compile the *.jrxml files into jasper files, this buildfiles have been attached in the builder properties of each project so that at refresh the jasper compilation would start.
We’re not sure what trigger the issue, but usually it happens after we’ve updated from svn all our project and then hit refresh on them to trigger the jasper compilation. We have discover that sometime righ after this procedure exporting a project that has already finisher build and refresh without any problems, we found out that the exported EAR was smaller that the usual. Looking at the differencies some *.class were not present and some were present but with size 0, some jasper files were not present at all.

The strange thing is that this problems happens randomly, sometimes the next export to EAR produces a correct file and some other time it need to be recalled many times before actually succeding.

Step that can cause the problem:
Svn Update of all the opened projects in the workspace
After Update and building completed hit F5 on the selected resources
After refresh completed select an ear project and do Export Ear, saving on the desktop
Usually this blocks the screem after this is completed sometimes the workspace start to build all over again.
Sometimes the EAR file does not cointains the jasper compiled and some .class are missing or with size 0

3. Subclipse 1.6 and Jrebel 4.5 for MyEclipse

5. I’m sorry company policies prevent me from send a project to you. Besides our project are quite heavy.

I’ve attached a zip with the logfiles, and the ant buildfile and launche that we use to build the jaspers. In the zip file there is also two screenshots taken during the exporting operation and immediadly after.

If you need something more don’t hesitate to ask!

Attachments:

You must be logged in to view attached files.

[support-joy]

01Informatica,

I have escalated your issue to dev team member. They would get back to you on this.

[Brian Fernandes]

O1,

I had a detailed look at our EAR exporting code and there isn’t anything in there that would actually re-compile your classes before export.

So the first thing to do is to examine the project/projects that you are exporting before you actually start the export process. I would examine these projects in Windows explorer; are all the classes and files that you wish to export actually present on the file system before the export starts?

Since you have a more complex build process, it is possible that some of these builders are not building when they should and the fault is not with the export per se, but other builders in your project that aren’t providing all the resources used during the export process. Can you check before exporting and let us know?

I would also keep an eye on the synchronization state of your projects. If they are out of synch with the file system (which can happen, especially if external scrip are used) then resource which are not visible to Eclipse will not be deployed / exported.

[Vittoriano Raffaelli]

Thanks Brian for you suggestions, we will keep an eye on the status of our projects they’re synchro with the file system before exportation.
I’ll give you more information on what happen and when.

[Author]

Posts