Topic
4 replies Latest Post - ‏2003-01-30T16:04:10Z by SystemAdmin
SystemAdmin
SystemAdmin
11979 Posts
ACCEPTED ANSWER

Pinned topic Deployment error on WSAD 5

‏2003-01-30T11:01:17Z |
Hi,

can somebody help me with this problem please

I have a project containing a Web application and 2 EJB.
When I deploy the EAR or the EJBs on the testserver
I get an error that it could not be published. It has the following
detail message (I translated it from german):

____________________________________________
Directory .repository is created.
The J2EE projects defined in the server configuration are not
consistent with the projects of the workbench: the module project
"null" defined in the server configuration is not existent in the EAR
Project "Hadv". This error can be fixed by opening an editor for the
server "TestServer" or the serverconfiguration, and replying "yes" to
the warning that appears.
____________________________________________

I did this "workaround" several times and it does not work!
Here is a log file extract of the server for the time of deployment:

com.ibm.etools.server.ui FINER 30/01/03 11:20.22.626 Getting
command manager for L/Servers/TestServer.wsi
com.ibm.etools.server.ui FINER 30/01/03 11:20.22.626 Creating new
command manager for L/Servers/TestServer.wsi
com.ibm.etools.server.ui FINER 30/01/03 11:20.22.636 Getting
command manager for F/Servers/TestServer.wsc
com.ibm.etools.server.ui FINER 30/01/03 11:20.22.636 Creating new
command manager for F/Servers/TestServer.wsc
com.ibm.etools.server.ui FINER 30/01/03 11:20.58.948 Releasing
command manager for L/Servers/TestServer.wsi
com.ibm.etools.server.ui FINER 30/01/03 11:20.58.958 Releasing
command manager for F/Servers/TestServer.wsc
com.ibm.etools.server.ui FINER 30/01/03 11:21.00.210 Getting
command manager for L/Servers/TestServer.wsi
com.ibm.etools.server.ui FINER 30/01/03 11:21.00.340 Creating new
command manager for L/Servers/TestServer.wsi
com.ibm.etools.server.ui FINER 30/01/03 11:21.00.360 Getting
command manager for F/Servers/TestServer.wsc
com.ibm.etools.server.ui FINER 30/01/03 11:21.00.360 Creating new
command manager for F/Servers/TestServer.wsc
com.ibm.etools.server.core SEVERE 30/01/03 11:22.26.263 Could not
publish to server
java.lang.ArrayIndexOutOfBoundsException: 1
at
com.ibm.etools.server.core.internal.ServerControl.publishPublishable(ServerControl.java:654)
at
com.ibm.etools.server.core.internal.ServerControl.publishPublishables(ServerControl.java:719)
at
com.ibm.etools.server.core.internal.ServerControl.publish(ServerControl.java:565)
at
com.ibm.etools.server.ui.internal.publish.PublishDialog$7.run(PublishDialog.java:749)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:98)

My environment is WSAD Version 5.0.0 build id 20021125_2118 on Win2000.
Any help is really appreciated!

Regards

Britt
Updated on 2003-01-30T16:04:10Z at 2003-01-30T16:04:10Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    11979 Posts
    ACCEPTED ANSWER

    Re: Deployment error on WSAD 5

    ‏2003-01-30T11:09:40Z  in response to SystemAdmin
    I usually by pass this error going to Server Perspective, select Server
    View, choose your Server Instance and remove and add again the project.

    Hope this helps,

    Chemi.

    Britt Worofsky wrote:

    > Hi,
    >
    > can somebody help me with this problem please
    >
    > I have a project containing a Web application and 2 EJB.
    > When I deploy the EAR or the EJBs on the testserver
    > I get an error that it could not be published. It has the following
    > detail message (I translated it from german):
    >
    > ____________________________________________
    > Directory .repository is created.
    > The J2EE projects defined in the server configuration are not
    > consistent with the projects of the workbench: the module project
    > "null" defined in the server configuration is not existent in the EAR
    > Project "Hadv". This error can be fixed by opening an editor for the
    > server "TestServer" or the serverconfiguration, and replying "yes" to
    > the warning that appears.
    > ____________________________________________
    >
    > I did this "workaround" several times and it does not work!
    > Here is a log file extract of the server for the time of deployment:
    >
    > com.ibm.etools.server.ui FINER 30/01/03 11:20.22.626 Getting
    > command manager for L/Servers/TestServer.wsi
    > com.ibm.etools.server.ui FINER 30/01/03 11:20.22.626 Creating
    > new command manager for L/Servers/TestServer.wsi
    > com.ibm.etools.server.ui FINER 30/01/03 11:20.22.636 Getting
    > command manager for F/Servers/TestServer.wsc
    > com.ibm.etools.server.ui FINER 30/01/03 11:20.22.636 Creating
    > new command manager for F/Servers/TestServer.wsc
    > com.ibm.etools.server.ui FINER 30/01/03 11:20.58.948 Releasing
    > command manager for L/Servers/TestServer.wsi
    > com.ibm.etools.server.ui FINER 30/01/03 11:20.58.958 Releasing
    > command manager for F/Servers/TestServer.wsc
    > com.ibm.etools.server.ui FINER 30/01/03 11:21.00.210 Getting
    > command manager for L/Servers/TestServer.wsi
    > com.ibm.etools.server.ui FINER 30/01/03 11:21.00.340 Creating
    > new command manager for L/Servers/TestServer.wsi
    > com.ibm.etools.server.ui FINER 30/01/03 11:21.00.360 Getting
    > command manager for F/Servers/TestServer.wsc
    > com.ibm.etools.server.ui FINER 30/01/03 11:21.00.360 Creating
    > new command manager for F/Servers/TestServer.wsc
    > com.ibm.etools.server.core SEVERE 30/01/03 11:22.26.263 Could not
    > publish to server
    > java.lang.ArrayIndexOutOfBoundsException: 1
    > at
    > com.ibm.etools.server.core.internal.ServerControl.publishPublishable(ServerControl.java:654)
    >
    > at
    > com.ibm.etools.server.core.internal.ServerControl.publishPublishables(ServerControl.java:719)
    >
    > at
    > com.ibm.etools.server.core.internal.ServerControl.publish(ServerControl.java:565)
    >
    > at
    > com.ibm.etools.server.ui.internal.publish.PublishDialog$7.run(PublishDialog.java:749)
    >
    > at
    > org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:98)
    >
    >
    >
    >
    > My environment is WSAD Version 5.0.0 build id 20021125_2118 on Win2000.
    > Any help is really appreciated!
    >
    > Regards
    >
    > Britt
    • SystemAdmin
      SystemAdmin
      11979 Posts
      ACCEPTED ANSWER

      Re: Deployment error on WSAD 5

      ‏2003-01-30T12:34:05Z  in response to SystemAdmin
      Hi Chemi,

      I did the remove/add several times, I also deleted the server instance
      and created a new one, but it does not help :-(

      When I create a new enterprise project an import my bean there, then it
      works. That's what I am going to do with the all the project modules now
      and hopefully it works then.

      Regards

      Britt

      Chemi wrote:
      > I usually by pass this error going to Server Perspective, select Server
      > View, choose your Server Instance and remove and add again the project.
      >
      > Hope this helps,
      >
      > Chemi.
      >
      > Britt Worofsky wrote:
      >
      >> Hi,
      >>
      >> can somebody help me with this problem please
      >>
      >> I have a project containing a Web application and 2 EJB.
      >> When I deploy the EAR or the EJBs on the testserver
      >> I get an error that it could not be published. It has the following
      >> detail message (I translated it from german):
      >>
      >> ____________________________________________
      >> Directory .repository is created.
      >> The J2EE projects defined in the server configuration are not
      >> consistent with the projects of the workbench: the module project
      >> "null" defined in the server configuration is not existent in the EAR
      >> Project "Hadv". This error can be fixed by opening an editor for the
      >> server "TestServer" or the serverconfiguration, and replying "yes" to
      >> the warning that appears.
      >> ____________________________________________
      >>
      >> I did this "workaround" several times and it does not work!
      >> Here is a log file extract of the server for the time of deployment:
      >>
      >> com.ibm.etools.server.ui FINER 30/01/03 11:20.22.626 Getting
      >> command manager for L/Servers/TestServer.wsi
      >> com.ibm.etools.server.ui FINER 30/01/03 11:20.22.626 Creating
      >> new command manager for L/Servers/TestServer.wsi
      >> com.ibm.etools.server.ui FINER 30/01/03 11:20.22.636 Getting
      >> command manager for F/Servers/TestServer.wsc
      >> com.ibm.etools.server.ui FINER 30/01/03 11:20.22.636 Creating
      >> new command manager for F/Servers/TestServer.wsc
      >> com.ibm.etools.server.ui FINER 30/01/03 11:20.58.948 Releasing
      >> command manager for L/Servers/TestServer.wsi
      >> com.ibm.etools.server.ui FINER 30/01/03 11:20.58.958 Releasing
      >> command manager for F/Servers/TestServer.wsc
      >> com.ibm.etools.server.ui FINER 30/01/03 11:21.00.210 Getting
      >> command manager for L/Servers/TestServer.wsi
      >> com.ibm.etools.server.ui FINER 30/01/03 11:21.00.340 Creating
      >> new command manager for L/Servers/TestServer.wsi
      >> com.ibm.etools.server.ui FINER 30/01/03 11:21.00.360 Getting
      >> command manager for F/Servers/TestServer.wsc
      >> com.ibm.etools.server.ui FINER 30/01/03 11:21.00.360 Creating
      >> new command manager for F/Servers/TestServer.wsc
      >> com.ibm.etools.server.core SEVERE 30/01/03 11:22.26.263 Could not
      >> publish to server
      >> java.lang.ArrayIndexOutOfBoundsException: 1
      >> at
      >> com.ibm.etools.server.core.internal.ServerControl.publishPublishable(ServerControl.java:654)
      >>
      >> at
      >> com.ibm.etools.server.core.internal.ServerControl.publishPublishables(ServerControl.java:719)
      >>
      >> at
      >> com.ibm.etools.server.core.internal.ServerControl.publish(ServerControl.java:565)
      >>
      >> at
      >> com.ibm.etools.server.ui.internal.publish.PublishDialog$7.run(PublishDialog.java:749)
      >>
      >> at
      >> org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:98)
      >>
      >>
      >>
      >>
      >> My environment is WSAD Version 5.0.0 build id 20021125_2118 on Win2000.
      >> Any help is really appreciated!
      >>
      >> Regards
      >>
      >> Britt
      >
      >
      • SystemAdmin
        SystemAdmin
        11979 Posts
        ACCEPTED ANSWER

        Re: Deployment error on WSAD 5

        ‏2003-01-30T15:37:09Z  in response to SystemAdmin
        Have you tried with a new server instance and configuration?

        Felix

        Britt Worofsky wrote:
        > Hi Chemi,
        >
        > I did the remove/add several times, I also deleted the server instance
        > and created a new one, but it does not help :-(
        >
        > When I create a new enterprise project an import my bean there, then it
        > works. That's what I am going to do with the all the project modules now
        > and hopefully it works then.
        >
        > Regards
        >
        > Britt
        • SystemAdmin
          SystemAdmin
          11979 Posts
          ACCEPTED ANSWER

          Re: Deployment error on WSAD 5

          ‏2003-01-30T16:04:10Z  in response to SystemAdmin
          We solved the problem by exporting all modules to .jars, .wars etc.,
          then deleting the whole enterprise project and creating a new one.
          Then we imported all the code from the .jars etc.

          Britt

          Felix Wong wrote:
          > Have you tried with a new server instance and configuration?
          >
          > Felix
          >
          > Britt Worofsky wrote:
          >
          >> Hi Chemi,
          >>
          >> I did the remove/add several times, I also deleted the server instance
          >> and created a new one, but it does not help :-(
          >>
          >> When I create a new enterprise project an import my bean there, then
          >> it works. That's what I am going to do with the all the project
          >> modules now and hopefully it works then.
          >>
          >> Regards
          >>
          >> Britt
          >
          >