facebook

Deployment problems [Closed]

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #201711 Reply

    mdichi
    Member

    I’m using MyEclipse 2.7RC2 with JBoss 3.2.1 on Windows 2000. Two people have observed this problem. I observed the following behaviour after initially installing 2.7, but it mysteriously stopped. Now someone else is having the same problem. The project involves struts, so there are java files and jsps.

    When the project is deployed, it simply doesn’t copy the files. If I stop JBoss and delete the directory (.war) from JBoss deploy directory manually and then start Jboss again, things work. But I have to kill JBoss each time.

    I had a couple of ideas as to what may be going. It seems like some of the libraries (.jars), become locked (in the file system). I didn’t determine which one(s), but MyEclipse didn’t seem to be able to delete the lib directory with the JARs while Jboss was running.

    I switched to a packaged deployment and the problem seemed to stop.

    Mike

    #201719 Reply

    mdichi
    Member

    Another thing that I’ve noticed is that since switching to package deployment, sometimes a redeploy fails. On the JBoss console an error appears that says something about a “ZLIB” error.

    Mike

    #201738 Reply

    Scott Anderson
    Participant

    Mike,

    I think what you’re asking for is a Reload function. More information on it, and a workaround is available in this thread:
    https://www.genuitec.com/forums/topic/jboss-redeployment-of-exploded-ear-file-fails/&highlight=jboss+reload

    #201759 Reply

    mdichi
    Member

    Scott,

    In my case, I have a web project – not an enterprise application project. I don’t think that web projects have an application.xml.

    Mike

    #201773 Reply

    We are also running a web project and have seen this behavior. However, we think that we tracked it down to having an explorer window open on the deployment directory – thus making windows (sigh) unable to delete the directory. When we restarted Eclipse and got rid of the explorers, we were able to deploy again 😀 .

    The problem is exacerbated by the project deployer following this partial deployment as it shows a caution flag (but without any explaination) and both the deploy and remove buttons appear to work – but without any real behavior. It was very frustrating to not be able to remove the deployment – then again this was on windows and your milage may vary.

    Hope that this information is helpful,

    James

    #201776 Reply

    Riyad Kalla
    Member

    James thank you for the additional info, its these little tidbits of information that can save someone hair late at night 🙂

    Mike did this solution help you at all?

    #201899 Reply

    mdichi
    Member

    I’m assuming you mean Windows Explorer. I closed all the Windows Explorer instances, but the problem still seems to be occurring.

    Mike- System Setup ——————————-
    Operating System and version: Windows 2000 Pro with SP4
    Eclipse version: 2.1.2
    Eclipse build id: 200311030802
    MyEclipse version: 2.7RC2
    Eclipse JDK version: 1.4.1 (03)
    Application Server JDK version: 1.4.1 (03)

    – Message Body ——————————-
    undefined

    #201948 Reply

    Scott Anderson
    Participant

    Mike,

    In my case, I have a web project – not an enterprise application project. I don’t think that web projects have an application.xml.

    Sorry, I didn’t notice it was just a web project. Then what you need to do is ‘touch’ web.xml to force JBoss to reload instead of application.xml as the thread suggests.

    What version of the JDK are you using to launch Eclipse? You stated 1.4.1 for the server and what I’m wondering is there might be an issue with an old JDK launching Eclipse that has a buggy implemenation of the zip code, thus creating an erroneous packaged deployment, and a new correctly functioning version of the zip libs in JDK 1.4.1 that can’t read it. Can you ensure that you also launch Eclipse with 1.4.1 to test this out?

    #202246 Reply

    mdichi
    Member

    Changing the web.xml file works nicely. The deployment problems no longer occur and don’t have to continually shut down and restart JBoss.

    I believe I v1.4.1_03 of java is being used. The 1.3 library is set for J2EE in the MyEclipse settings.

    The exact error that I get when deploying is, “unexpected end of ZLIB input stream”. I usually just redeploy again and it works – so this is not a critical issue.

    Mike

    #202248 Reply

    Riyad Kalla
    Member

    Mike thanks for following up with us

Viewing 10 posts - 1 through 10 (of 10 total)
Reply To: Deployment problems [Closed]

You must be logged in to post in the forum log in