[CS Tan]

We recently made some change to infrastructure
– changed WAS_ROOT folder and services of WAS
– we have also migrated to git from CVS (no error in the new build)

Now we have a problem using this new config in Myeclipse. After add WAS 8.5.5 server, it does not start.
A prompt message shows “Server WebSphere Application Server 8.5 at localhost failed to start.” Has encountered a problem.

Please help us resolve urgently.

CS

[support-swapna]

CS,

Sorry that you are seeing this issue.

1. Can you please clarify if the WAS server starts fine from outside MyEclipse?
2. If the server starts fine from outside, does MyEclipse pick up the running server status in the Servers view?
3. Does the runConfigActions.disableAtServerStartup (empty file) under the [profile_root]/properties/service/ directory still exist as per this suggestion in your previous report?
4. Please share the exact WAS version, MyEclipse version, the location of WAS_ROOT folder, changes you made to the WAS service and the .log file located at workspace dir to help us investigate further.

Apologies for inconvenience caused.

–Swapna
Genuitec Support

[CS Tan]

Hi Swapna, thanks for your prompt reply.
And yes we forgot to redirect the echo that creates runConfigActions.disableAtServerStartup (empty file) in the new root. The server is starting now.
We also got this prompt quite often.
Searching for workspace which requires migration has encountered a problem. java.lang.ExceptionInitialize Error. Is there a way to stop this. Or is there something we need to handle.

[support-swapna]

CS,

Glad that the server starts fine.
For the migration error, can you please share the .log file located at workspace dir/.metadata/.log to help us get the full stacktrace of the error?
Rename the extension to .txt and attach it here.

–Swapna
Genuitec Support

[CS Tan]

Attached log file…

Attachments:

You must be logged in to view attached files.

[CS Tan]

Hi Swapna, any clue from the file?

[Brian Fernandes]

CS,

This exception trace is related to re-associating the project with a server with which it was deployed prior to the migration. You can simply ignore this error and turn off the migration scanning. Go to Preferences > MyEclipse > Project Migration and check Disable automatic scanning for migration. That should stop the error from repeatedly showing up.

[Author]

Posts