回覆︰ Tomcat 8 webapp failed to start on Windows reboot
Hi Chris, Christopher Schultz ch...@christopherschultz.net 於 2015年06月19日 (週五) 3:16 AM 寫道﹕ -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 James, On 6/18/15 4:56 AM, James Cheung wrote: Environment --- Tomcat 8.0.21 x64 bit, JDK 8u31, Windows 2008 R2 x64 bit Problem --- After upgrading from tomcat 7.0.42 to 8.0.21, my webapp(gih-ws) failed to startup every time the machine is rebooted. In the tomcat catalina log, it did not show any error, but in my webapp(gih-ws) access log, it showed below error. ERROR 08 6月 2015 03:20:39,329 (AxisEngine.java:219) -[]- The service cannot be found for the endpoint reference (EPR) /gih-ws/services/GIH3Service/keywordSearchWithIndex?maxNoOfResult=11k eyword=North%20Point%20Government%20OfficesstartIndex=0response=applic ation%2Fjsonlang=enextent=839266.674348%2C816651.312098%2C839765.32565 2%2C817436.687902 org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) /gih-ws/services/GIH3Service/keywordSearchWithIndex?maxNoOfResult=11k eyword=North%20Point%20Government%20OfficesstartIndex=0response=applic ation%2Fjsonlang=enextent=839266.674348%2C816651.312098%2C839765.32565 2%2C817436.687902 at org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhas e.java:78) This looks like you are trying to call a web service that does not exist. Is the gih-ws service failing to start because it can't access a remote web service, or is the local Axis service logging that the gih-ws service hasn't been deployed? We didn't make change to the web servcie. They worked fine before our upgrade. at org.apache.axis2.engine.Phase.invoke(Phase.java:329) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:168) at org.apache.axis2.transport.http.util.RESTUtil.invokeAxisEngine(RESTUti l.java:144) at org.apache.axis2.transport.http.util.RESTUtil.processURLRequest(RESTUt il.java:139) at org.apache.axis2.transport.http.AxisServlet$RestRequestProcessor.proce ssURLRequest(AxisServlet.java:837) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:273 ) at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli cationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi lterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli cationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi lterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVa lve.java:219) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextVa lve.java:106) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authenticat orBase.java:502) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.ja va:142) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja va:79) at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAcces sLogValve.java:610) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv e.java:88) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java :518) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp1 1Processor.java:1091) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(A bstractProtocol.java:668) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.pro cess(Http11AprProtocol.java:283) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoi nt.java:2463) at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint .java:2452) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j ava:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor. java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThr ead.java:61) at java.lang.Thread.run(Thread.java:745) Our finding --- We stopped the tomcat 8 service and then started it again and the webapp(gih-ws) can startup and there was no error in the gih-ws access log. It is so weird. Is there any tomcat 8 service startup issue every time the machine is rebooted? Should we start the Tomcat 8 service in Startup(Delayed) mode? I also include below tomcat catalina log for your reference. Thanks. Tomcat catalina log --- 10-Jun-2015 10:04:20.250 INFO [Thread-25] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler
RE: SSL configuration using PFX as keystore
Thanks, I've done much searching - hence why I'm finally posting here.
Windows WebDAV is actually quite reasonable - a lot of what one reads on the
internet is because people don't know how to configure it. It won't pass basic
authentication across a connection by default, you have to turn it on and there
are two different settings for allowing it over SSL only or a non-encrypted
connection.
When connecting from a Windows client (any Windows client) I get a 'network
path not found' error 0x80070035. I know the path is valid as I can reach it
via other means, and other WebDAV clients.
The main reason I think this is a Tomcat issue is that it was working just fine
with v7.0 and no other Windows client changes (updates, software etc.) have
been made. There wasn't anything specific in the Tomcat7 config that I needed
to get the MS client to work, only on the client itself those registry changes
as previously mentioned.
I'll run a Wireshark trace and see what comes up, nothing in the Tomcat logs
that I can see...
Thanks
Michael Salisbury
Senior Systems Architect | P 07 960 7011 | E mich...@skypoint.co.nz
| W skypoint.co.nz
Waikato Innovation Park, Ruakura Rd, PO Box 9466, Hamilton 3240, NZ
Please send any support enquiries to E supp...@skypoint.co.nz
-Original Message-
From: André Warnier [mailto:a...@ice-sa.com]
Sent: Saturday, 20 June 2015 1:15 a.m.
To: Tomcat Users List
Subject: Re: SSL configuration using PFX as keystore
Daniel Mikusa wrote:
On Fri, Jun 19, 2015 at 12:42 AM, Michael Salisbury
mich...@skypoint.co.nz
wrote:
Hi there,
I’m trying to get the above working using Tomcat 8.0, previously
working with 7.0. This is part of a WebDAV connector in Confluence.
It seems I can connect from anything other than a Windows Mini
Redirector client (Windows 7 or 8.1, x86 or x64). Using a web
browser or 3rd party client (CyberDuck for instance) connects OK.
You should do a search in Google for Windows and DAV.
The various implementations over the years of DAV in MS Windows are a real
horror story.
As far as I know (but it varies according to Windows versions and patches, and
even according to whatever other software is installed on the workstation) :
- recent version of Windows will only accept to connect to DAV folders via HTTPS
- recent and less recent versions of Windows will only accept to connect to a
DAV folder, if that DAV folder is at the document root of the webserver
In other words, for all practical purposes, you /have to/ use a third-party
client.
(WebDrive is another one which I know works)
And if you don't, be prepared for a lot of support calls..
What happens when you try to connect with the Windows Mini Redirector?
Do you get a client error? If so, what? Do you get any errors or
messages in the Tomcat logs? If not, you might try running wireshark
to investigate further. Capture packets from a working client and
packets from the MS client then look to see what's different.
That said, the fact that it's working for a large selection of clients
except one, seems to point to a problem with the client and not your
Tomcat setup. What makes you think this is a Tomcat issue? Was there
something specific you had to do in Tomcat 7 to make the MS client work?
Dan
There are some registry keys in Windows one needs to enable to get
this working first:
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Internet]
BasicAuthLevel=dword:0001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Param
eters]
BasicAuthLevel=dword:0001
UseBasicAuth=dword:0001
Server.xml
Connector port=9443 maxHttpHeaderSize=8192
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
protocol=org.apache.coyote.http11.Http11NioProtocol
enableLookups=false disableUploadTimeout=true
acceptCount=100 scheme=https secure=true
clientAuth=false sslProtocols=TLS SSLEnabled=true
URIEncoding=UTF-8
keystoreType=PKCS12
keystoreFile=${catalina.base}/conf/certname.pfx
keystorePass=keypassword/
I’m fairly new to this, but have done a fair bit of reading to get it
working previously in Tomcat7…so any help would be greatly appreciated.
Kind regards
*Michael Salisbury*
*Senior Systems Architect* | *P* 07 960 7011 | *E*
mich...@skypoint.co.nz | *W* skypoint.co.nz
Waikato Innovation Park, Ruakura Rd, PO Box 9466, Hamilton 3240, NZ
[image: cid:image001.png@01CF0265.772EC520]
Please send any support enquiries to *E* supp...@skypoint.co.nz
[image: MCSA_2013(rgb)_14802] [image: HP Accredited Technical
Professional]
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
-
To unsubscribe, e-mail:
Re: I'm using jdk1.6 + tomcat 7.0.23
Can you put my E-mail account deleted from the mailing list, thank you！ 2015-06-11 12:42 GMT+08:00 chedana jayasinghe chedanajayasin...@gmail.com: HI, In my web application, in a jsp there is a javascript which sends request to a servlet every twenty seconds, so it kills my applications user idle time tracking by resetting the lastAccessed time. the funny thing is lastAccessed time doesn't get updated in tomcat 6 and my applications idle time tracking works fine in it, but in 7 it gets updated and kills that functionality of the application . so I'm little bit confused about the changes in the session tracking of tomcat 6 and tomcat 7
Re: I'm using jdk1.6 + tomcat 7.0.23
On Saturday, June 20, 2015 11:17 PM, hao huang huanghao...@gmail.com wrote: Can you put my E-mail account deleted from the mailing list, thank you Hao, as indicated here: Apache Tomcat - Mailing Lists you should send a blank email to users-unsubscr...@tomcat.apache.org to unsubscribe from the Tomcat users list. - Bob
