• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Deployment failures - Netbeans 6.1 / Websphere 6.1

 
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am testing some development options using Netbeans 6.1. I have WebSphere 6.1.0.19 installed on this machine and have configured a new server within NB 6.1 that "points" to the Websphere instance. It is based on choosing the "IBM Websphere Application Server V6.1" connector (server). I am able to start and stop the server without any issues - and open a browser outside of NB 6.1 to access the Admin console. At first I was doing a Web Service project and thought the issue was with it specifically - so I created a brand new project - simple Hello World web application w/ just an index.jsp. I set the Run property to use the newly configured IBM Webspher App Server 6.1 instance. I started up the server. I can right click on the Project and choose Clean and Build ... build is successful. However as soon I choose Run or Undeploy and Deploy...all I get is a Deployment failure. (so it was not specific to my previous web service project either). The errors in the console output in NB 6.1:




I did find the following in the IDE log (Netbeans):

SEVERE [com.ibm.ws.management.application.j2ee.deploy.spi.factories.DeploymentFactoryImpl]: ADMJ1002E
INFO [org.netbeans.modules.j2ee.deployment.impl.ServerInstance]
java.lang.IllegalStateException: This operation is not possible on a disconnected deployment manager
at org.netbeans.modules.j2ee.websphere6.WSDeploymentManager.getTargets(WSDeploymentManager.java:938)
[catch] at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.getTargetMap(ServerInstance.java:517)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.getTargets(ServerInstance.java:490)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.initCoTarget(ServerInstance.java:1499)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance.access$200(ServerInstance.java:101)
at org.netbeans.modules.j2ee.deployment.impl.ServerInstance$1.run(ServerInstance.java:383)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:561)
at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:986)

This implies that the server is not running - but it is...

I have spent hours on Google, finding nothing...

Any ideas would be appreciated...Thanks
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi

i m also having the same problem.
please please please if someone solve this problem then provide the solution.
 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
IDE timeout: refresh the server node to see if it's running now.
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
 
palla jayakrishna
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Possible reason include:
IDE timeout: refresh the server node to see if it's running now.
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
 
M Streit
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I will check that out...but I don't think those are factors. So... is it safe to say that YOU have seen this actually work yourself. I can deploy to every other server except WAS 6.1 w/o errors.

Thanks
[ October 01, 2008: Message edited by: M Streit ]
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

try changing the server port.
I fix the problem by changing the port 8080 and 8025 by another
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic