So i have deployed jenkins.war into the tomcat docker container but apparently when i try to open this jenkins.war file i end up getting HTTP Status 404 – Not Found error,
What i expect is a jenkins page to be opened, I went through the docker logs and i found these errors
17-Sep-2020 10:21:25.176 WARNING [localhost-startStop-1] org.apache.tomcat.util.scan.StandardJarScanner.scan Failed to scan JAR [war:file:/usr/local/tomcat/webapps/jenkins.war*/WEB-INF/lib/spring-webmvc-2.5.6.SEC03.jar] from /WEB-INF/lib
java.nio.file.AccessDeniedException: /usr/local/tomcat/temp/jar_cache7070370173706501058.tmp
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
17-Sep-2020 10:21:26.629 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
17-Sep-2020 10:21:26.954 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
17-Sep-2020 10:21:26.960 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/jenkins] startup failed due to previous errors
What is it that i'm missing, Please help me out with your suggestions.
Related
I was able to setup Jenkins 2.361.1 in Tomcat 9.0.67. It is running perfectly fine in http://localhost:8080/jenkins but if I try to restart tomcat by using shutdown.bat and then startup.bat, I get the following errors:
...
SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more Filters failed to start. Full details will be found in the appropriate container log file
SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/jenkins] startup failed due to previous errors
INFO [main] hudson.lifecycle.Lifecycle.onStatusUpdate Stopping Jenkins
INFO [main] jenkins.model.Jenkins$16.onAttained Started termination
SEVERE [main] jenkins.model.Jenkins$16.onTaskFailed Failed NioChannelSelector.cleanUp
java.lang.IllegalArgumentException: Unable to inject class jenkins.slaves.NioChannelSelector
at hudson.init.TaskMethodFinder.lookUp(TaskMethodFinder.java:130)
...
http://localhost:8080 will still work fine but http://localhost:8080/jenkins displays a 404 page
Why am I getting that error even if I didn't change a thing after Tomcat shutdown? I used the zip file download to install Tomcat not the service installer.
The only workaround that works so far for me is to delete the jenkins folder inside the webapps folder and let tomcat redeploy it again. After doing that, no error occurred and jenkins worked just like before.
I am facing below issue while switch VS2019 to VS2022. I am not able to run my API project its throwing below error. I Search on google and look many articals but not got success. Please suggest to resolve this problem. I checked and found that .netCore upper version not support to old version code.
HTTP Error 500.37 - ANCM Failed to Start Within Startup Time Limit
Common solutions to this issue:
ANCM failed to start after -1 milliseconds
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
I am trying to run the Grails -clean command on Ubuntu machine running in Docker container but I am getting the below error:
$ grails clean
| Loading Grails 2.4.0
| Configuring classpath
| Error Resolve error obtaining dependencies: Failed to read artifact descriptor for xalan:serializer:jar:2.7.1 (Use --stacktrace to see the full trace)
| Error Required Grails build dependencies were not found. This is normally due to internet connectivity issues (such as a misconfigured proxy) or missing repositories in grails-app/conf/BuildConfig.groovy. Please verify your configuration to continue.
Because of this issue, I am not able to proceed further with the war file deployment using grails. I have checked the "BuildConfig.groovy" and added some repositories as well as mentioned in various portals, but no luck. Getting the same error again and again.
Any help will be highly appreciated.
Thanks,
Akshat
Try using https instead of just http.
mavenRepo "https://repo.grails.org/grails/core"
mavenRepo "https://repo.grails.org/grails/plugins"
Also try running with Java 8 over Java 7 due to Java 8 default to TLS 1.2.
I am migrating my java enterprise application from WAS8.5 full profile
to liberty server. My application code has soap client and required
stubs generated from WSDL. I am able to receive response when using
WAS8.5 but getting below exceptions while running liberty server.
I have already added jaxws-2.2 .
Recreated the stubs again pointing to liberty server, IBM-WS from eclipse. I
couldn't find relevant answers online.
Console logs
[WARNING ] Could not unwrap Operation {http://services.abc.com/gb/getsomepoint/v1}getSomeInfoByParam to match method "public abstract void com.abc.services.gb.getsomepoint.v1.GBGetSomePointV1.getSomeInfoByParam(javax.xml.ws.Holder,java.lang.String,java.lang.String,javax.xml.ws.Holder,javax.xml.ws.Holder)"
javax.xml.ws.soap.SOAPFaultException: BIP3113E: Exception detected in message flow GB_GetSomePoint_V1.SOAP Input (integration node NMD4BRK)
[err] at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:156)
[err] at [internal classes]
[err] ... 51 more
[err] Caused by:
[err] org.apache.cxf.binding.soap.SoapFault: BIP3113E: Exception detected in message flow GB_GetSomePoint_V1.SOAP Input (integration node NMD9BRK)
[err] at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:84)
[err] at [internal classes]
[err] ... 53 more
There isn't much information to go on from the console but one thing to check is if the request/response messages to and from the client look the same on Liberty as they do on WAS 8.5. That'd be a simple way to verify if the expected behavior is the same. Another thing to consider is if your WSDL contract matches the request generated by the client (i.e. all the bindings are there).
The Web Services configuration (WS-Policy/WS-Security) can be substantially different on Liberty vs WAS 8.5 and this Knowledge Center document has some good info on how to properly configure your app if you need it.
Deploying JAX-WS applications to Liberty:
https://www.ibm.com/support/knowledgecenter/SSD28V_9.0.0/com.ibm.websphere.wlp.core.doc/ae/twlp_dep_jaxws.html
The last thing I’d suggest is turning on Liberty’s Web Services trace. There isn’t a lot of info about root cause from the console messages, but by turning on the trace the specific problem might make itself known. You can turn trace on by following these directions.
Enabling trace on WebSphere Liberty:
https://www.ibm.com/support/knowledgecenter/SSD28V_9.0.0/com.ibm.websphere.wlp.core.doc/ae/rwlp_logging.html
The specific trace specification you’ll want to enable for Web Services is as follows:
traceSpecification="*=audit:com.ibm.ws.jaxws.*=finest:org.apache.cxf.*=finest”
If it works after commenting out jaxws-2.2 feature, you must be using a different jax-ws implementation packaged with your application. You can try adding back the jaxws-2.2 feature and set this JVM property for liberty server: -Dcom.ibm.xml.xlxp.jaxb.opti.level=0
I have placed the solace jar files in the below location :
C:\oracle10.3.6\Middleware\user_projects\domains\solace_domain\lib (solace jar files)
If I have the log4j.properties in application level, how this will effect the logging ?
As I start the weblogic server it starts printing the INFO login in the server console ?
Here is my log4j.properites file :
The log4j.properties file should be contained somewhere in the Weblogic server's CLASSPATH. You can enable the Java system property "-Dlog4j.debug" to see debug level log4j logs. This will tell you where the properties file is being read from.
If the following is contained in the correct log4j.properties file, you should only be seeing ERROR and FATAL level Solace JMS and Solace JCSMP logs. You should not be seeing INFO level Solace JMS or Solace JCSMP logs on startup.
log4j.category.com.solacesystems.jms=ERROR
log4j.category.com.solacesystems.jcsmp=ERROR