Devserver 1.9.4 launches two separate instances of the same module. [35897703]

Assigned

Bug

Status Update

No update yet.

Description

hu...@gmail.com

created issue #1

May 19, 2014 08:30PM

When I try to run module with basic scaling in devserver 1.9.4, it tries to run two instances locally one on port 8080 and one in another port. The one on 8080 gives this exception:

expected one element but was: <ManualServerInstanceHolder: containerservice=com.google.appengine.tools.development.JettyContainerService@1cedb15a instance=-1, ManualServerInstanceHolder: containerservice=com.google.appengine.tools.development.JettyContainerService@39169a8c instance=0>
Caused by:

java.lang.IllegalArgumentException: expected one element but was: <ManualServerInstanceHolder: containerservice=com.google.appengine.tools.development.JettyContainerService@1cedb15a instance=-1, ManualServerInstanceHolder: containerservice=com.google.appengine.tools.development.JettyContainerService@39169a8c instance=0>
at com.google.appengine.repackaged.com.google.common.collect.Iterators.getOnlyElement(Iterators.java:318)
at com.google.appengine.repackaged.com.google.common.collect.Iterables.getOnlyElement(Iterables.java:292)
at com.google.appengine.tools.development.BasicModule.getAndReserveAvailableInstanceHolder(BasicModule.java:90)
at com.google.appengine.tools.development.BasicModule.getAndReserveAvailableInstanceHolder(BasicModule.java:23)
at com.google.appengine.tools.development.Modules.getAndReserveFreeInstance(Modules.java:326)
at com.google.appengine.tools.development.DelegatingModulesFilterHelper.getAndReserveFreeInstance(DelegatingModulesFilterHelper.java:39)
at com.google.appengine.tools.development.DevAppServerModulesFilter.doRedirect(DevAppServerModulesFilter.java:304)
at com.google.appengine.tools.development.DevAppServerModulesFilter.doFilter(DevAppServerModulesFilter.java:119)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at com.google.appengine.tools.development.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:98)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(JettyContainerService.java:491)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

Comments

st...@google.com <st...@google.com> #2May 20, 2014 12:14AM

Hello,

Thank you for reaching out to us!

This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs and request features on Google Cloud products. Please go through link to learn more about issue trackers.

I recommend you to ask the technical questions on Stack Exchange sites which are best suited for this type of questions.

For now, I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.

Thank you!

is...@google.com <is...@google.com> Jun 3, 2016 10:07PM

Assigned to is...@google.com.

ro...@arcus-solutions.nl <ro...@arcus-solutions.nl> #3Jul 11, 2016 10:15AM

Yes, this works but why isn't one instance not possible?

is...@google.com <is...@google.com> Dec 12, 2017 06:48PM

Reassigned to da...@google.com.

da...@google.com <da...@google.com> Jan 26, 2018 03:40PM

Reassigned to lu...@google.com.

su...@google.com <su...@google.com> #4Jan 16, 2020 06:41AM

Why is this bug being demoted to P3?
Since this bug has been older than 270 days and idle for >90 days, we are demoting this to P3. Also, as per Bugscope, this bug rolls up under the Cloud/TI hierarchy: go/cloud-ti-bugscope-demotion-candidate. If you have a question about why a bug is being considered as a candidate, please check go/bugscope-coa for more information w.r.t bug owner attribution
.
What is the motivation for the demotion?
As part of the effort to address the growing P2 backlog within Cloud/TI, all abandoned P2s (Customer Issues, Bugs & Vulnerabilities) i.e. older than 270 days and out of response SLO for > 90 days, will be demoted one-time to P3s. We hope this gives teams fewer P2s to triage manually.
See these announcements in go/cloud-bug-slos-update-jan-2020.

How often do bugs get demoted?
This is a one-time demotion and is being done over the week of Jan 13th 2020.

Questions?
For any questions, please reach out to cloud-bug-slo-updates-help@google.com. Thank you!

Issue 35897703