[Greg Duerbusch]

I am getting the followin error when I attempt to Deploy one of my Web Applications to my local WebSphere 6.1 server
Add Deployment has encountered a problem
An internal error occured during ‘Add Deployment’

The following showed up when I clicked details
An internal error occurred during: “Add Deployment”.
java.lang.NullPointerException

I checked the deployment log and there is nothing there

The depolyment does begin tho copy classes and jsp tp the AppServer directory.
I can’t tell where it’s failing exactly.

[support-swapna]

gduerb ,

Sorry that you are seeing this issue with MyEclipse.

Can you give some more information?

1. Can you copy paste your installation details from MyEclipse > Installation Summary > Installation Details?

2. Can you go to your log file located at workspace dir > .metadata > .log, clear the contents and save your log file and then try to deploy your application again. What are the errors logged in the log file? Paste them here.

3. Can you check if your application can be deployed without issues to any other server which is configured in MyEclipse?

[Greg Duerbusch]

I’ve attached the Installation Summary Detail and metadata log files as text file.I attempted to deploy the application undet Tomcat and I’m getting the same error.

Attachments:

You must be logged in to view attached files.

[support-swapna]

gduerb ,

Thank you for the summary details. The .log file contents are missing from the .txt file you uploaded.
Can you please resend the contents of the .log file for us to investigate further ?

[Greg Duerbusch]

Sorry

I must have for got to clcik the Add Attachment.
Here it is.
Thanks

By the way, I want to mention that I have a very similiar application in a different workspace under the same MyEclipse configuration that deploys without any issues.

[support-swapna]

gduerb ,

The attachment is still missing. If you are facing difficulty in attaching it to the forum post, then please send an email with the attachment to support@genuitec.com, with subject ATTN:SWAPNA and also mention the link to this post in the subject.

[Greg Duerbusch]

I’m attaching the Project metadata file to this reply and sent it via e-mail as you requested.

Attachments:

You must be logged in to view attached files.

[support-swapna]

gduerb ,

Thank you for the log details.

1) Can you please take a look at this thread which discusses similar issue and apply the suggestion ?

https://www.genuitec.com/forums/topic/deployment-problem-with-web-project-in-myeclipse-10/#post-321668

Here is the link to the milestone release.Please update to the milestone release (10.0.1) and check if you still see the issue :

https://www.genuitec.com/forums/topic/myeclipse-10-0-1-milestone-is-now-available/

2) If you are still seeing the issue, please attach your file(s) to an email to support@genuitec.com, with a subject of ATTN: SWAPNA and a link in the email to this thread, please.

Let us know how it works for you.

[Greg Duerbusch]

Question
Since we are MyEclipse blue shouldn’t i sue the MyEclipse blye 1.0.0.2 ?

[support-swapna]

gduerb ,

You should install MyEclipse Blue 10.0.1. The 10.0.1 is a mile stone release and 10.0.2 is an update. You can get MyEclipse Blue from the links mentioned in this FAQ :
https://www.genuitec.com/forums/topic/myeclipse-10-0-1-milestone-is-now-available/

Let us know if you see any issues.

[Greg Duerbusch]

Swapna

I’m not getting the Deployment error message any longer but the Application is still not deploying.

We are still gettin an error the depoyment log and metadata log that indicates the deployment failed.

Attached you’ll find the depoyment log and Project metadata log

Attachments:

You must be logged in to view attached files.

[support-tony]

gduerb,

Thanks for the files. They are confusing. From most of the information, it looks like your latest deployment was as a packaged war file but the deployment log starts off indicating an exploded deployment. Could you confirm how you tried deployment when you got the last error?

If you deployed in packaged mode (as a war file), then could you try in exploded mode? There is a fix in the milestone stream (which you have) for a problem with non-Java dependent projects. I’m thinking that the problem might still be there for packaged deployments.

If all of your deployments have been exploded, could you explain the structure of your project and its dependent projects? What type of dependent projects do you have? Have you changed any workspace or project settings related to deployment of dependent projects (right click on the main project and go to Properties, then MyEclipse->Web->Deployment tab)?

[Greg Duerbusch]

Tony
One, just to give you some background. I have a sister application (another Warranty application but a different client) that has similiar code and similiar project structure that resides in a different workspace but uses the same MyEclipse configuration.

To answer your first question, I’m deploying this as exployed.
Most of the projects that this project depends on are Java projects. There is one project that is also a web project (We just use the java classes) and the deployment type is exacly the same as the current project.
To explain the hierarchy as defined in the order and export
1 framework project, (java only)
2. A extra common utilitily project (java only)
3. A Security Project (java only)
4 the Warranty project (WarrantyIQ) java and web
5 The Console reporting project. (This is a java/Web project we only use the java classes)

The MyEclipse->Web->Deployment Tab has the use Use Smart deployment radial button selected.

I hope I’ve answered all your questions. If not let me know. I need to get this resolved

[support-tony]

gduerb,

I was unable to replicate your exact problem. However, your dependence on another web project will produce problems as the web project dependent will not be packaged as a library (exploded or as a jar). Indeed, this use of web dependencies may be against the J2EE spec, which would mean it is not fixable. We would recommend that the java classes that your warranty project depends on be packaged as another Java project. If your warranty project is dependent on projects which also have dependencies, please make sure that those secondary dependent projects are exported in the build path configuration (this is done from the Order and Export page).

Your exact problem may also be caused by residuals of past dependencies on other projects. Could you check the project properties of each project (right click on the project and select Properties) to make sure that there are no Project References to non-Java or deleted projects? If the project properties show no such projects, it may be wise to double-check by editing the .project file of each project to make sure there are no <project> elements that reference such files.

I hope this helps.

[Greg Duerbusch]

Tony
I thought you were on to something with the depenance on another Web Project.Unfortunatily splitting the projct to a java and web and only refernecing the java project did not resolve the issue.

[Author]

Posts