I'm attempting to run an application "ehour" on Tomcat. When I enter in my browser http://localhost:8080/ehour I get the error HTTP Status 404-/ehour. I've downloaded the mysql connector file and extracted and copied the mysql-connector-java-5.0.8-bin.jar file into tomcat's bin directory and restarted tomcat but still get the same error. This is the error that shows in the tomcat log
"Caused by: java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getDriver(Unknown Source)
at com.zaxxer.hikari.util.DriverDataSource.<init>(DriverDataSource.java:47)
... 69 more".
Related
I'm using the "On New or Update" source of the Mule 4 SFTP Connector, to process files from an SFTP server directory. The process works fine, however while reading the last file the SFTP connector throws an error as shown below and the file remains in directory waiting next schedule time to be picked up and the same thing will happen for the last file of other new set of files.
Any thoughts on how to fix this issue?
ERROR:
11:20:45.315 05/04/2022 Worker-0 [MuleRuntime].uber.27: [sftp-demo-app].prcsACKFiles-Error-SuccessFlow.CPU_INTENSIVE #1648077b ERROR
event:c458bc90-cbbd-11ec-85e2-06a565d43154
********************************************************************************
Message : "org.mule.weave.v2.module.reader.ReaderParsingException: org.mule.runtime.api.exception.MuleRuntimeException - Exception was found trying to retrieve the contents of file /home/messages/file_8ddb7674.json
org.mule.runtime.api.exception.MuleRuntimeException: Exception was found trying to retrieve the contents of file /home/messages/file_8ddb7674.json
at org.mule.extension.sftp.internal.connection.SftpClient.exception(SftpClient.java:427)
at org.mule.extension.sftp.internal.connection.SftpClient.exception(SftpClient.java:423)
at org.mule.extension.sftp.internal.connection.SftpClient.getFileContent(SftpClient.java:349)
at org.mule.extension.sftp.internal.connection.SftpFileSystem.retrieveFileContent(SftpFileSystem.java:117)
at org.mule.extension.sftp.internal.SftpInputStream$SftpFileInputStreamSupplier.getContentInputStream(SftpInputStream.java:111)
at org.mule.extension.sftp.internal.SftpInputStream$SftpFileInputStreamSupplier.getContentInputStream(SftpInputStream.java:93)
at org.mule.extension.file.common.api.AbstractConnectedFileInputStreamSupplier.getContentInputStream(AbstractConnectedFileInputStreamSupplier.java:81)
at org.mule.extension.file.common.api.AbstractFileInputStreamSupplier.get(AbstractFileInputStreamSupplier.java:65)
at org.mule.extension.file.common.api.AbstractFileInputStreamSupplier.get(AbstractFileInputStreamSupplier.java:33)
at org.mule.extension.file.common.api.stream.LazyStreamSupplier.lambda$new$1(LazyStreamSupplier.java:29)
at org.mule.extension.file.common.api.stream.LazyStreamSupplier.get(LazyStreamSupplier.java:42)
at org.mule.extension.file.common.api.stream.AbstractNonFinalizableFileInputStream.lambda$createLazyStream$0(AbstractNonFinalizableFileInputStream.java:48)
at $java.io.InputStream$$EnhancerByCGLIB$$55e4687e.read(<generated>)
at org.apache.commons.io.input.ProxyInputStream.read(ProxyInputStream.java:102)
at org.mule.runtime.core.internal.streaming.bytes.AbstractInputStreamBuffer.consumeStream(AbstractInputStreamBuffer.java:111)
at com.mulesoft.mule.runtime.core.internal.streaming.bytes.FileStoreInputStreamBuffer.consumeForwardData(FileStoreInputStreamBuffer.java:239)
at com.mulesoft.mule.runtime.core.internal.streaming.bytes.FileStoreInputStreamBuffer.consumeForwardData(FileStoreInputStreamBuffer.java:202)
at com.mulesoft.mule.runtime.core.internal.streaming.bytes.FileStoreInputStreamBuffer.doGet(FileStoreInputStreamBuffer.java:125)
at org.mule.runtime.core.internal.streaming.bytes.AbstractInputStreamBuffer.get(AbstractInputStreamBuffer.java:93)
at org.mule.runtime.core.internal.streaming.bytes.BufferedCursorStream.assureDataInLocalBuffer(BufferedCursorStream.java:126)
at org.mule.runtime.core.internal.streaming.bytes.BufferedCursorStream.doRead(BufferedCursorStream.java:101)
at org.mule.runtime.core.internal.streaming.bytes.AbstractCursorStream.read(AbstractCursorStream.java:124)
at org.mule.runtime.core.internal.streaming.bytes.BufferedCursorStream.read(BufferedCursorStream.java:26)
at java.io.InputStream.read(InputStream.java:101)
at org.mule.runtime.core.internal.streaming.bytes.ManagedCursorStreamDecorator.read(ManagedCursorStreamDecorator.java:96)
at org.mule.weave.v2.el.SeekableCursorStream.read(MuleTypedValue.scala:306)
at org.mule.weave.v2.module.reader.UTF8StreamSourceReader.handleBOM(SeekableStreamSourceReader.scala:179)
at org.mule.weave.v2.module.reader.UTF8StreamSourceReader.readAscii(SeekableStreamSourceReader.scala:163)
at org.mule.weave.v2.module.json.reader.JsonTokenizer.$init$(JsonTokenizer.scala:21)
at org.mule.weave.v2.module.json.reader.indexed.IndexedJsonTokenizer.<init>(IndexedJsonTokenizer.scala:15)
at org.mule.weave.v2.module.json.reader.indexed.IndexedJsonParser.parser(IndexedJsonParser.scala:17)
at org.mule.weave.v2.module.json.reader.JsonReader.readValue(JsonReader.scala:40)
at org.mule.weave.v2.module.json.reader.JsonReader.doRead(JsonReader.scala:30)
at org.mule.weave.v2.module.reader.Reader.read(Reader.scala:35)
at org.mule.weave.v2.module.reader.Reader.read$(Reader.scala:33)
at org.mule.weave.v2.module.json.reader.JsonReader.read(JsonReader.scala:20)
at org.mule.weave.v2.el.MuleTypedValue.value(MuleTypedValue.scala:147)
at org.mule.weave.v2.model.values.wrappers.DelegateValue.valueType(DelegateValue.scala:17)
at org.mule.weave.v2.model.values.wrappers.DelegateValue.valueType$(DelegateValue.scala:16)
at org.mule.weave.v2.el.MuleTypedValue.valueType(MuleTypedValue.scala:177)
at org.mule.weave.v2.model.types.ObjectType$.accepts(Type.scala:1068)
Caused by: org.mule.extension.sftp.api.SftpConnectionException: Error occurred while trying to connect to host
... 112 more
Caused by: org.mule.runtime.api.connection.ConnectionException:
at org.mule.extension.sftp.api.SftpConnectionException.<init>(SftpConnectionException.java:38)
... 112 more
Caused by: org.mule.runtime.api.connection.ConnectionException:
... 112 more
Caused by: 4:
at com.jcraft.jsch.ChannelSftp.get(ChannelSftp.java:1540)
at com.jcraft.jsch.ChannelSftp.get(ChannelSftp.java:1290)
at org.mule.extension.sftp.internal.connection.SftpClient.getFileContent(SftpClient.java:347)
... 110 more
Caused by: java.io.IOException: Pipe closed
Error Pipe closed in SFTP indicates a communication error that the SFTP connector can not resolve, so the operation fails. I don't believe that there is anything that you can do about that. You might try to test a newer version of the connector if you are using an older one, just in case.
I tried to run the cordapp-example from the command prompt. But when I input the "gradlew.bat deployNodes" command, I got the error as below.
Execution failed for task ':kotlin-source:compileKotlin'.
Could not resolve all dependencies for configuration ':kotlin-source:compileClasspath'.
Could not determine artifacts for org.jolokia:jolokia-war:1.3.7
Could not get resource 'https://jcenter.bintray.com/org/jolokia/jolokia-war/1.3.7/jolokia-war-1.3.7.war'.
Could not HEAD 'https://jcenter.bintray.com/org/jolokia/jolokia-war/1.3.7/jolokia-war-1.3.7.war'.
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
I had done the "keytool -importcert" command to import the certificate of jolokia-war into java cacerts, but the error was still there.
Does anyone know how to solve the problem?
The error message indicates that the compilation failed because your machine was unable to download the resource at this location: https://jcenter.bintray.com/org/jolokia/jolokia-war/1.3.7/jolokia-war-1.3.7.war.
This URL works for me and I was able to download the resource. You are most likely behind a firewall or otherwise unable to download this resource. You need to make your machine able to access this resource to compile and deploy the node.
I'm unable to reliably use ASP.NET web deployment to push updates to my server running on an EC2 instance.
The server is running Windows Server 2012 R2 (fully updated and patched), and it's running the latest version of the Web Deployment Service (3.5, actual version 9.0.176.0). I'm trying under both Visual Studio 2013 and Visual Studio 2015, and try connecting directly to the EC2 instance or via the ELB. In all cases, if the deploy takes more than x seconds, it just hangs and then errors out (many) minutes later.
If the deploy consists of many small files, each subsequent attempt to deploy will upload another handful of files before hanging, like this:
2>Start Web Deploy Publish the Application/package to http://52.8.131.99/MSDEPLOYAGENTSERVICE ...
2>Adding ACL's for path (NeoSmart)
2>Adding ACL's for path (NeoSmart)
2>Updating file (NeoSmart\bin\RestSharp.dll).
2>Updating file (NeoSmart\bin\secure\secrets.release.bin).
2>Updating file (NeoSmart\bin\secure\secrets.sandbox.bin).
2>Updating file (NeoSmart\bin\System.Net.Http.Formatting.dll).
2>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4270,5): Warning : Retrying the sync because a socket error (10054) occurred.
2>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 1 of 10.
2>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4270,5): Warning : Retrying the sync because a socket error (10054) occurred.
2>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 2 of 10.
After abort, restart of VS, and retry, it continues where it left off only to hang again:
2>Start Web Deploy Publish the Application/package to http://52.8.131.99/MSDEPLOYAGENTSERVICE ...
2>Adding ACL's for path (NeoSmart)
2>Adding ACL's for path (NeoSmart)
2>Updating file (NeoSmart\bin\System.Net.Http.Formatting.dll).
2>Updating file (NeoSmart\bin\System.Web.Helpers.dll).
2>Updating file (NeoSmart\bin\System.Web.Http.Common.dll).
2>Updating file (NeoSmart\bin\System.Web.Http.dll).
2>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4270,5): Warning : Retrying the sync because a socket error (10054) occurred.
2>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 1 of 10.
If the file it hangs on is too big to go through (for example, the latest version of the AWS SDK, weighing in at 6.3MiB), subsequent restarts won't help any - it hangs on the same file repeatedly:
2>Start Web Deploy Publish the Application/package to http://52.8.131.99/MSDEPLOYAGENTSERVICE ...
2>Adding ACL's for path (NeoSmart)
2>Adding ACL's for path (NeoSmart)
2>Updating file (NeoSmart\bin\System.Web.Http.dll).
2>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4270,5): Warning : Retrying the sync because a socket error (10054) occurred.
2>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 1 of 10.
Deploying to a new EC2 instance takes care of the problem; only a day later I have the same issue and I need to deploy a new Server 2012 instance and deploy all over again. No way, no how.
To me, it looks like the connection is being dropped without acknowledgement somewhere along the line. I'm not sure how/why since I've tried deploying directly to the EC2 instance's public IP and to the ELB. I've tried with w3svc stopped and started, in case it was contention over the target files that was causing the issue, but to no avail. It's probably not on my end because creating a new EC2 instance and deploying from the same machine I'm on works without a problem.
Any idea how I can find out what's causing this? Nothing shows up in the event viewer. Is there a better alternative to the Web Deployment Service for pushing updates to ASP.NET websites on IIS?
Any insight would be most appreciated.
I have built a Camel project in Eclipse with Maven dependencies.
It ran successfully and also Built the Jar file and ran it from the command prompt
which is running as required. But when I moved the JAR file onto to our Linux machine
which is like a Job Manager server and when I try to run the JAR file as below
I am getting the below error message.
When I try to run with the below command
$ java –jar mycamelproject
I am getting the below error, but I do have the below mentioned dependency in the Dependency-Jars folder.
Exception in thread "main" java.lang.NoClassDefFoundError: org/springframework/c
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2531)
at java.lang.Class.getMethod0(Class.java:2774)
at java.lang.Class.getMethod(Class.java:1663)
at sun.launcher.LauncherHelper.getMainMethod(LauncherHelper.java:494)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:486)
Caused by: java.lang.ClassNotFoundException: org.springframework.context.support
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 6 more
Then I tried running with the below command.
$ mvn -X exec:java -Dexec.mainClass=mycamelpackage.mycamelmainclass
I am getting a series of the below errors such as below
[DEBUG] Could not find metadata org.codehaus.mojo/maven-metadata.xml in local (/home/ec2-user/.m2/repository)
[DEBUG] Skipped remote update check for org.codehaus.mojo/maven-metadata.xml, already updated during this session.
[WARNING] Failure to transfer org.codehaus.mojo/maven-metadata.xml from
http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer metadata org.codehaus.mojo/maven-metadata.xml from/to central (http://repo.maven.apache.org/maven2): proxy.host.net
[ERROR] No plugin found for prefix 'exec' in the current project
and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo]
available from the repositories
How should java –jar mycamelproject work if no classpath is set? And mycamelproject should be a JAR file anyway (and if it is, you should add the *.jar extension).
Beside that, I guess your local Maven repository may be corrupt. That's usually the reason why you see the resolution will not be reattempted error message. The easiest way to fix this is to remove the corrupt directories and start Maven again.
i'm setting a Plone server. and set add-on Document Viewer on it.
but when i convert .doc on broswer i get error.
Exception in thread "main" org.artofsolving.jodconverter.office.OfficeException: failed to start and connect
at org.artofsolving.jodconverter.office.ManagedOfficeProcess.startAndWait(ManagedOfficeProcess.java:64)
at org.artofsolving.jodconverter.office.PooledOfficeManager.start(PooledOfficeManager.java:101)
at org.artofsolving.jodconverter.office.ProcessPoolOfficeManager.start(ProcessPoolOfficeManager.java:62)
at org.artofsolving.jodconverter.cli.Convert.main(Convert.java:112)
Caused by: java.util.concurrent.ExecutionException: org.artofsolving.jodconverter.office.OfficeException: could not establish connection
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
at java.util.concurrent.FutureTask.get(FutureTask.java:111)
at org.artofsolving.jodconverter.office.ManagedOfficeProcess.startAndWait(ManagedOfficeProcess.java:62)
... 3 more
from debug information i know the error come from a command:
java -Djava.awt.headless=true
-Djava.util.logging.config.file=/usr/lib/ruby/gems/1.8/gems/docsplit-0.7.2/vendor/logging.properties
-cp /usr/lib/ruby/gems/1.8/gems/docsplit-0.7.2/build:/usr/lib/ruby/gems/1.8/gems/docsplit-0.7.2/vendor/'*'
-jar /usr/lib/ruby/gems/1.8/gems/docsplit-0.7.2/vendor/jodconverter/jodconverter-core-3.0-beta-4.jar
-r /usr/lib/ruby/gems/1.8/gems/docsplit-0.7.2/vendor/conf/document-formats.js /tmp/tmpPYP2u5/dump.doc /tmp/tmpPYP2u5/dump.pdf 2>&1
but if i run it in bash with root privileges. i get no error.
I change libreoffice to openoffice3.org then the problem disapeared