Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Problem with Tomcat looping when using BridgeServlet with the console option on
Problem with Tomcat looping when using BridgeServlet with the console option on [message #95634] Wed, 22 August 2007 08:29 Go to next message
Francis Upton IV is currently offline Francis Upton IVFriend
Messages: 472
Registered: July 2009
Location: Oakland, CA
Senior Member
When I have the console option turned on:

<web-app id="WebApp">
<servlet id="bridge">
<servlet-name>equinoxbridgeservlet</servlet-name>
<display-name>Equinox Bridge Servlet</display-name>
<description>Equinox Bridge Servlet</description>
<servlet-class>org.eclipse.equinox.servletbridge.BridgeServlet </servlet-class>
<init-param>
<param-name>commandline</param-name>
<param-value>-console</param-value>
</init-param>

My Tomcat (6.0.14) goes into a loop taking all CPU, outputing this to
the log:

Aug 22, 2007 1:24:58 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The Apache Tomcat Native library which allows optimal performance
in production environments was not found on the java.library.path:
/usr/java/jdk1.6.0/jre/lib/i386/server:/usr/java/jdk1.6.0/jr e/lib/i386:/usr/java/jdk1.6.0/jre/../lib/i386:/usr/java/j2sd k1.4.2_13/bin/classic:/usr/java/j2sdk1.4.2_13/jre/bin::/usr/ java/packages/lib/i386:/lib:/usr/lib
Aug 22, 2007 1:24:58 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Aug 22, 2007 1:24:58 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 786 ms
Aug 22, 2007 1:24:58 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Aug 22, 2007 1:24:58 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
Aug 22, 2007 1:24:58 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive osdm.war

osgi>
osgi>
osgi>
(these go on forever, and in my emacs it shows as a ^M after each osgi>
prompt)

Any ideas?


Re: Problem with Tomcat looping when using BridgeServlet with the console option on [message #95650 is a reply to message #95634] Wed, 22 August 2007 14:17 Go to previous messageGo to next message
Simon Kaegi is currently offline Simon KaegiFriend
Messages: 381
Registered: July 2009
Senior Member
Hi Francis,
A similar problem was reported by Roberto Sanchez on June 1 "Critical
Problem with osgi console".
We're not currently able to reproduce the problem and are unsure as to what
is the cause.
Any info you can add would help --
https://bugs.eclipse.org/bugs/show_bug.cgi?id=192361

-Simon


"Francis Upton" <francisu@ieee.org> wrote in message
news:fags4s$64k$1@build.eclipse.org...
> When I have the console option turned on:
>
> <web-app id="WebApp">
> <servlet id="bridge">
> <servlet-name>equinoxbridgeservlet</servlet-name>
> <display-name>Equinox Bridge Servlet</display-name>
> <description>Equinox Bridge Servlet</description>
> <servlet-class>org.eclipse.equinox.servletbridge.BridgeServlet </servlet-class>
> <init-param>
> <param-name>commandline</param-name>
> <param-value>-console</param-value> </init-param>
> My Tomcat (6.0.14) goes into a loop taking all CPU, outputing this to the
> log:
>
> Aug 22, 2007 1:24:58 AM org.apache.catalina.core.AprLifecycleListener init
> INFO: The Apache Tomcat Native library which allows optimal performance in
> production environments was not found on the java.library.path:
> /usr/java/jdk1.6.0/jre/lib/i386/server:/usr/java/jdk1.6.0/jr e/lib/i386:/usr/java/jdk1.6.0/jre/../lib/i386:/usr/java/j2sd k1.4.2_13/bin/classic:/usr/java/j2sdk1.4.2_13/jre/bin::/usr/ java/packages/lib/i386:/lib:/usr/lib
> Aug 22, 2007 1:24:58 AM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on http-8080
> Aug 22, 2007 1:24:58 AM org.apache.catalina.startup.Catalina load
> INFO: Initialization processed in 786 ms
> Aug 22, 2007 1:24:58 AM org.apache.catalina.core.StandardService start
> INFO: Starting service Catalina
> Aug 22, 2007 1:24:58 AM org.apache.catalina.core.StandardEngine start
> INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
> Aug 22, 2007 1:24:58 AM org.apache.catalina.startup.HostConfig deployWAR
> INFO: Deploying web application archive osdm.war
>
> osgi>
> osgi>
> osgi>
> (these go on forever, and in my emacs it shows as a ^M after each osgi>
> prompt)
>
> Any ideas?
Re: Problem with Tomcat looping when using BridgeServlet with the console option on [message #95693 is a reply to message #95650] Wed, 22 August 2007 16:57 Go to previous message
Francis Upton IV is currently offline Francis Upton IVFriend
Messages: 472
Registered: July 2009
Location: Oakland, CA
Senior Member
Thanks Simon, I updated the bug report providing what you need to
reproduce it.

I'm not good at being able to debug an instance of Tomcat in the Eclipse
debugger and get at the code for the Eclipse code that is started by
the servlet bridge (I'm not even sure this is possible, and I have
tried). If this was possible and you could show me the way, I would
be happy to debug this myself.

Francis

Simon Kaegi wrote:
> Hi Francis,
> A similar problem was reported by Roberto Sanchez on June 1 "Critical
> Problem with osgi console".
> We're not currently able to reproduce the problem and are unsure as to what
> is the cause.
> Any info you can add would help --
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=192361
>
> -Simon
>
>
> "Francis Upton" <francisu@ieee.org> wrote in message
> news:fags4s$64k$1@build.eclipse.org...
>> When I have the console option turned on:
>>
>> <web-app id="WebApp">
>> <servlet id="bridge">
>> <servlet-name>equinoxbridgeservlet</servlet-name>
>> <display-name>Equinox Bridge Servlet</display-name>
>> <description>Equinox Bridge Servlet</description>
>> <servlet-class>org.eclipse.equinox.servletbridge.BridgeServlet </servlet-class>
>> <init-param>
>> <param-name>commandline</param-name>
>> <param-value>-console</param-value> </init-param>
>> My Tomcat (6.0.14) goes into a loop taking all CPU, outputing this to the
>> log:
>>
>> Aug 22, 2007 1:24:58 AM org.apache.catalina.core.AprLifecycleListener init
>> INFO: The Apache Tomcat Native library which allows optimal performance in
>> production environments was not found on the java.library.path:
>> /usr/java/jdk1.6.0/jre/lib/i386/server:/usr/java/jdk1.6.0/jr e/lib/i386:/usr/java/jdk1.6.0/jre/../lib/i386:/usr/java/j2sd k1.4.2_13/bin/classic:/usr/java/j2sdk1.4.2_13/jre/bin::/usr/ java/packages/lib/i386:/lib:/usr/lib
>> Aug 22, 2007 1:24:58 AM org.apache.coyote.http11.Http11Protocol init
>> INFO: Initializing Coyote HTTP/1.1 on http-8080
>> Aug 22, 2007 1:24:58 AM org.apache.catalina.startup.Catalina load
>> INFO: Initialization processed in 786 ms
>> Aug 22, 2007 1:24:58 AM org.apache.catalina.core.StandardService start
>> INFO: Starting service Catalina
>> Aug 22, 2007 1:24:58 AM org.apache.catalina.core.StandardEngine start
>> INFO: Starting Servlet Engine: Apache Tomcat/6.0.14
>> Aug 22, 2007 1:24:58 AM org.apache.catalina.startup.HostConfig deployWAR
>> INFO: Deploying web application archive osdm.war
>>
>> osgi>
>> osgi>
>> osgi>
>> (these go on forever, and in my emacs it shows as a ^M after each osgi>
>> prompt)
>>
>> Any ideas?
>
>


Previous Topic:Using Class.forName or Bundle.loadClass in bundles - whats the difference?
Next Topic:Deploy WAR unexploded into Equinox
Goto Forum:
  


Current Time: Thu Mar 28 09:19:38 GMT 2024

Powered by FUDForum. Page generated in 0.02375 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top