Eclipse Community Forums: ServerTools (WTP) » Odd behavior when publishing web project with deps

Home » Language IDEs » ServerTools (WTP) » Odd behavior when publishing web project with deps

Odd behavior when publishing web project with deps [message #117778]

Thu, 07 July 2005 21:22

Eclipse User

Originally posted by: ccostello.stubhub.com

Hello all,

I've created a dynamic web app foo and a util java project bar. Foo only
contains the default web application contents plus a simple, "Hello,
world!" index.jsp. Bar contains default contents (nothing) plus one
class, test.TestClass, that's comprised of a public constructor and
nothing else.

Before establishing any relationship between the projects, I can
successfully associate the web app with a server and
launching/stopping/publishing to Tomcat works fine.

However, as soon as I create a "Java Jar Dependency" within foo upon bar,
I can no longer run the Tomcat server. In the Servers view, status is
reported as "Stopped", and state is reported as "Republish". Trying to
start the server has no visible effect on anything, and nothing new shows
up in the console or .log file. Attempting to "Publish" foo (by
right-clicking on the server in the servers view) results in a
java.util.ConcurrentModificationException in the .log file. (See full
entry below).

If I remove the dependency, all returns to normal, expected behavior.

Deleting/recreating the server config has no effect. Restarting eclipse
(with and without -clean) has no effect. Restarting my machine has no
effect. The scenario is always reproducible.

I'm using Tomcat 5.5.9, jdk 5.0 update 3, windows xp pro sp2, eclipse 3.1
final and WTP M5. Is anyone else experiencing anything like this?

Thanks for reading,
-Cass

!ENTRY org.eclipse.ui 4 0 2005-07-07 18:15:35.355

!MESSAGE java.util.ConcurrentModificationException

!STACK 0

java.util.ConcurrentModificationException

at java.util.AbstractList$Itr.checkForComodification(Unknown
Source)
at java.util.AbstractList$Itr.next(Unknown Source)

at
org.eclipse.wst.server.core.internal.PublishServerJob.<init >(PublishServerJob.java:66)

at
org.eclipse.wst.server.ui.internal.view.servers.PublishActio n.perform(PublishAction.java:
52)

at
org.eclipse.wst.server.ui.internal.view.servers.AbstractServ erAction.run(AbstractServerAc
tion.java:53)

at org.eclipse.jface.action.Action.runWithEvent(Action.java:996 )

at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionI
tem.java:538)

at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)

at
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java
:400)

at
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)

at
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3080)

at
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2713)

at
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1699)

at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)

at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:367)

at
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)

at
org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:103)

at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:226)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)

at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )

at org.eclipse.core.launcher.Main.basicRun(Main.java:278)

at org.eclipse.core.launcher.Main.run(Main.java:973)

Re: Odd behavior when publishing web project with deps [message #117874 is a reply to message #117778]

Fri, 08 July 2005 04:10

Eclipse User

Originally posted by: nils.hartmann.teha-systems.de

Hi,

> I'm using Tomcat 5.5.9, jdk 5.0 update 3, windows xp pro sp2, eclipse 3.1
> final and WTP M5. Is anyone else experiencing anything like this?

same here running Eclipse/WTP on linux with Tomcat 5.5.4. I just tried
WTP's newest intergration build (wtp-I20050708) but it's the same :-(

Anyone has a solution/explanation for this problem?

Thanks,
Nils

Re: Odd behavior when publishing web project with deps [message #117926 is a reply to message #117874]

Fri, 08 July 2005 07:09

Eclipse User

Hi, I'm seeing exactly the same issue with a very similar configuration:
Tomcat 5.5.9, jdk 5.0 update 4, windows xp pro sp2, eclipse 3.1 final and
WTP M5

Another side effect for me is that once the error has occurred I don't see
any utility projects in the Java JAR Dependencies window anymore.

I've tried deleting the 3 projects: util, web and Servers and also remove
the Server in Window -> Preferences -> Server and start again. However the
2nd time, the Java JAR Dependencies window doesn't show the util project.

The only way I've found to recover to a clean state is to open eclipse in
a new workspace - however I've not been able to get to the state with a
web project and dependent util project working reliably together.

I posted earlier this week [Adding project natures for flexile project]
for more details.

I think that there might be something being stored in the
workspace/.metadata area that's causing some of the problems we are seeing
(certainly the missing projects in the Java JAR Dependencies window).

If I ever find a solution I'll post it for sure

Cheers
Jason

Re: Odd behavior when publishing web project with deps [message #118030 is a reply to message #117926]

Fri, 08 July 2005 09:29

Eclipse User

Originally posted by: nils.hartmann.teha-systems.de

Hi,

> Another side effect for me is that once the error has occurred I don't see
> any utility projects in the Java JAR Dependencies window anymore.

works for me... Anyway: libraries from those dependend projects are not
copied to my .deployables folder. Have to copy them manually to
"WEB-INF/lib" in "WebContent". Not really nice...

Another (better) observation: I discovered that I can start Tomcat
successfully from the "Run"-Menu instead from the "Servers" View (using
"Run -> Run last Launched" or by creating an own launch configuration from
the link "Open launch configuration..." in the "Server Overview" view).

Regards,
Nils

Re: Odd behavior when publishing .. works after fresh install. [message #118762 is a reply to message #117778]

Fri, 08 July 2005 18:33

Eclipse User

Originally posted by: ccostello.stubhub.com

After deleting 3.1 and reinstalling, everything now works as expected.
Before trying that, I tried (one last time) working from a new workspace
to no avail.

Now, foo starts/stops/publishes correctly even with the dependency. I had
started from a fresh install yesterday, too, so I remain confused. :)

On another note...
I've added a few more deps to foo, including log4j. A new servlet class
loads a log4j config file held inside WEB-INF appropriately. The config
file specifies a default loggin threshold of "debug," however, only
statements at level "info" and above are output to the eclipse console
when I launch Tomcat.

Debugging demonstrates that log.isDebugEnabled() returns false throughout
my codebase. Is there some special sauce required to get log4j, Tomcat,
Eclipse and WTP to play together nicely? I include the log4j config info
below...

Thanks again for everyone's time.

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">

<appender name="ConsoleAppender"
class="org.apache.log4j.ConsoleAppender">
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{ISO8601} [%t] %p - %m%n"/>
</layout>
</appender>

<root>
<level value="debug" />
<appender-ref ref="ConsoleAppender"/>
</root>

</log4j:configuration>

Cass Costello wrote:

> Hello all,

> I've created a dynamic web app foo and a util java project bar. Foo only
> contains the default web application contents plus a simple, "Hello,
> world!" index.jsp. Bar contains default contents (nothing) plus one
> class, test.TestClass, that's comprised of a public constructor and
> nothing else.

> Before establishing any relationship between the projects, I can
> successfully associate the web app with a server and
> launching/stopping/publishing to Tomcat works fine.

> However, as soon as I create a "Java Jar Dependency" within foo upon bar,
> I can no longer run the Tomcat server. In the Servers view, status is
> reported as "Stopped", and state is reported as "Republish". Trying to
> start the server has no visible effect on anything, and nothing new shows
> up in the console or .log file. Attempting to "Publish" foo (by
> right-clicking on the server in the servers view) results in a
> java.util.ConcurrentModificationException in the .log file. (See full
> entry below).

> If I remove the dependency, all returns to normal, expected behavior.

> Deleting/recreating the server config has no effect. Restarting eclipse
> (with and without -clean) has no effect. Restarting my machine has no
> effect. The scenario is always reproducible.

> I'm using Tomcat 5.5.9, jdk 5.0 update 3, windows xp pro sp2, eclipse 3.1
> final and WTP M5. Is anyone else experiencing anything like this?

> Thanks for reading,
> -Cass

> !ENTRY org.eclipse.ui 4 0 2005-07-07 18:15:35.355

> !MESSAGE java.util.ConcurrentModificationException

> !STACK 0

> java.util.ConcurrentModificationException

> at java.util.AbstractList$Itr.checkForComodification(Unknown
> Source)
> at java.util.AbstractList$Itr.next(Unknown Source)

> at
>
org.eclipse.wst.server.core.internal.PublishServerJob.<init >(PublishServerJob.java:66)

> at
>
org.eclipse.wst.server.ui.internal.view.servers.PublishActio n.perform(PublishAction.java:
> 52)

> at
>
org.eclipse.wst.server.ui.internal.view.servers.AbstractServ erAction.run(AbstractServerAc
> tion.java:53)

> at org.eclipse.jface.action.Action.runWithEvent(Action.java:996 )

> at
>
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionI
> tem.java:538)

> at
>
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)

> at
>
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java
> :400)

> at
> org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)

> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:843)

> at
> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3080)

> at
> org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2713)

> at
> org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1699)

> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)

> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:367)

> at
> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:143)

> at
> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:103)

> at
>
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:226)

> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:376)

> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:163)

> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

> at java.lang.reflect.Method.invoke(Unknown Source)

> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334 )

> at org.eclipse.core.launcher.Main.basicRun(Main.java:278)

> at org.eclipse.core.launcher.Main.run(Main.java:973)

Previous Topic:	xdoclet merge dir
Next Topic:	Bad performance of XML Schema Editor

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Apr 24 23:06:03 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter