× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WDSCI-L
  3. June 2006

HATS development using WDSCi - WAS server problem

I installed the HATS studio components into WDSC and, outside of some learning curve issues, I am making some progress. However, when I try to run a HATS app under the local WAS 6.0 test server (selecting the "Run on Server"option on the project) I get a dialog with the following message:
The server named WebSphere v6.0 Server @ localhost did not start correctly. Check the Console for error messages. * 

The console, of course, shows absolutely nothing....

The logfile is equally helpful:

ENTRY com.ibm.sse.model 4 4 Jun 23, 2006 13:51:47.950
!MESSAGE null_argument: IFile parameter can not be null

!ENTRY com.ibm.wtp.server.ui 4 0 Jun 23, 2006 13:56:47.852
!MESSAGE The server named WebSphere v6.0 Server @ localhost did not start correctly. Check the Console for error messages. *
I tried turning off Windows Firewall. I changed the sever to use SOAP as the connection type rather than RMI and got this: 

!ENTRY com.ibm.sse.model 4 4 Jun 23, 2006 14:11:57.784
!MESSAGE null_argument: IFile parameter can not be null

!ENTRY org.eclipse.core.runtime 4 2 Jun 23, 2006 14:12:02.741
!MESSAGE An internal error occurred during: "Server Selection".
!STACK 0
java.lang.NullPointerException
at org.eclipse.jface.dialogs.IconAndMessageDialog.getSWTImage(Unknown Source) at org.eclipse.jface.dialogs.IconAndMessageDialog.getErrorImage(Unknown Source) 
   at org.eclipse.jface.dialogs.MessageDialog.<init>(Unknown Source)
   at org.eclipse.jface.dialogs.MessageDialog.openError(Unknown Source)
at com.ibm.etools.websphere.tools.internal.util.MessageHandler.showDlg(Unknown Source) at com.ibm.etools.websphere.tools.internal.util.MessageHandler.showErrorDlg(Unknown Source) at com.ibm.ws.ast.st.v6.internal.util.ServerProcessLauncher.launch(Unknown Source) at com.ibm.ws.ast.st.v6.internal.AbstractWASTestServer.ensureJmxConnection(Unknown Source) at com.ibm.ws.ast.st.v6.internal.AbstractWASTestServer.start(Unknown Source) at com.ibm.ws.ast.st.v6.internal.WASLaunchConfigurationDelegate.launch(Unknown Source) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(Unknown Source) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(Unknown Source) 
   at com.ibm.wtp.server.core.internal.Server.start(Unknown Source)
at com.ibm.wtp.server.core.internal.Server.synchronousStart(Unknown Source) at com.ibm.wtp.server.ui.internal.task.ModifyModulesTask.execute(Unknown Source) 
   at com.ibm.wtp.server.ui.wizard.TaskWizard.executeTask(Unknown Source)
at com.ibm.wtp.server.ui.wizard.TaskWizard$1$FinishWizardJob.run(Unknown Source) 
   at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)

So it seems that WAS test server is hosed up.
Any words of wisdom on how to get the server to run? Perhaps a place to look to look for more helpful logs? 

Thanks.

Pete Helgren

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.