I am trying to set "maxThreadsActive" to 1 , to make sure there is only one thread pulling messages form queue , but for some reason i am getting sax parse exception in compile time .
Following is the Configuration :
<anypoint-mq:config name="Anypoint_MQ_Configuration"
provider-ref="anypointMQ_Provider_Settings" doc:name="Anypoint MQ Configuration" >
<http:worker-threading-profile maxThreadsActive="1"/>
</anypoint-mq:config>
error :
ERROR 2017-10-04 12:35:00,849 [main] org.mule.module.launcher.application.DefaultMuleApplication: null
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'http:worker-threading-profile'. One of '{"http://www.mulesoft.org/schema/mule/core":annotations, "http://www.mulesoft.org/schema/mule/tls":context, "http://www.mulesoft.org/schema/mule/http":proxy, "http://www.mulesoft.org/schema/mule/anypoint-mq":provider, "http://www.mulesoft.org/schema/mule/anypoint-mq":prefetch, "http://www.mulesoft.org/schema/mule/anypoint-mq":worker-threading-profile}' is expected.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) ~[?:?]
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) ~[?:?]
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) ~[?:?]
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) ~[?:?]
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) ~[?:?]
The issue is with the Anypoint Studio.
The anypoint-mq connector configuration from Studio creates a internal tag with http:worker-threading-profile, which is not a valid child element for the anypoint-mq:config element.
To fix the error, you need to manually update the XML file by removing the http:worker-threading-profile, and add the following child element 'anypoint-mq:worker-threading-profile'. If you add this element, then it would not be shown in the Studio, but it will set the Thread profiling to Anypoint MQ connector.
This is an error with Studio.
Please refer the following link and go to section 'Threading Profile Settings'
https://docs.mulesoft.com/mule-user-guide/v/3.9/anypoint-mq-connector-reference
It seems you may be missing some configurations, do check the following SO answer : https://stackoverflow.com/a/37904111/7141847
And if you are setting maxThreadsActive to 1 i believe you need to set poolExhaustedAction="WAIT" in anypoint-mq-configurations
I have faced the similar issue.To ressolve this we need to use updated anypoint mq connector for the AnypointStudio-version(6.6.0).
Studio & Mq version
Related
It throws below error and restarts thereafter without printing much logs.
TcpDiscoverySpi [tcp-disco-sock-reader-[]-#13-#76] Failed to initialize connection (this can happen due to short time network problems and can be ignored if does not affect node discovery) [sock=Socket[addr=/10.178.19.121,port=45450,localport=18036]]
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method) ~[?:?]
at java.net.SocketInputStream.socketRead(SocketInputStream.java:115) ~[?:?]
at java.net.SocketInputStream.read(SocketInputStream.java:168) ~[?:?]
at java.net.SocketInputStream.read(SocketInputStream.java:140) ~[?:?]
at java.io.BufferedInputStream.fill(BufferedInputStream.java:252) ~[?:?]
at java.io.BufferedInputStream.read1(BufferedInputStream.java:292) ~[?:?]
at java.io.BufferedInputStream.read(BufferedInputStream.java:351) ~[?:?]
at org.apache.ignite.spi.discovery.tcp.ServerImpl$SocketReader.body(ServerImpl.java:6784) ~[ignite-core-2.10.0.jar!/:2.10.0]
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:58) ~[ignite-core-2.10.0.jar!/:2.10.0]
What could be the potential reason for this error and how to prevent Ignite from throwing this error?
I am a beginner to jmeter. I am trying to perform a simple load test using jmeter 4.0. I created a HTTP sampler and added a view results tree listener.
HTTP Sampler
But getting the below error under Response data in results tree.
"java.net.UnknownHostException: This is usually a temporary error during hostname resolution and means that the local server did not
receive a response from an authoritative server at
java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at
java.net.InetAddress$2.lookupAllHostAddr(Unknown Source) at
java.net.InetAddress.getAddressesFromNameService(Unknown Source) at
java.net.InetAddress.getAllByName0(Unknown Source) at
java.net.InetAddress.getAllByName(Unknown Source) at
java.net.InetAddress.getAllByName(Unknown Source) at
org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:263)
at
org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:162)
at
org.apache.jmeter.protocol.http.sampler.hc.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:318)
at
org.apache.jmeter.protocol.http.sampler.MeasuringConnectionManager$MeasuredConnection.open(MeasuringConnectionManager.java:114)
at
org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445)
at
org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835)
at
org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
at
org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.executeRequest(HTTPHC4Impl.java:697)
at
org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl.sample(HTTPHC4Impl.java:455)
at
org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:74)
at
org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1189)
at
org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1178)
at
org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:490)
at
org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:416)
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:250)
at java.lang.Thread.run(Unknown Source)"
All requests are getting failed. There is no problem in internet connectivity. Please resolve my issue.
I just faced same issue. Found solution using below steps:
1.
Protocol:http/https
server name/IP:google.com
port & path:blank(as no params)
add proxy details if required
I am trying to connect with mule Dynamics CRM online connector v-2.9.1 and mule esb version 3.8.5. After configuration when I am testing the connection I am getting below exception.
org.mule.api.ConnectionException: Error trying to create the security policy
org.mule.api.ConnectionException: Error trying to create the security policy
at org.mule.module.dynamicscrm.connection.OnlineConnectionStrategy.createServiceForOnline(OnlineConnectionStrategy.java:97)
at org.mule.module.dynamicscrm.connection.OnlineConnectionStrategy.createOrganizationServiceClient(OnlineConnectionStrategy.java:70)
at org.mule.module.dynamicscrm.connection.BaseCrmConnectionStrategy.connect(BaseCrmConnectionStrategy.java:183)
at org.mule.module.dynamicscrm.connection.BaseCrmConnectionStrategy.testConnectivity(BaseCrmConnectionStrategy.java:195)
at org.mule.module.dynamicscrm.generated.connectivity.OnlineConnectionStrategyDynamicsCRMConnectorAdapter.test(OnlineConnectionStrategyDynamicsCRMConnectorAdapter.java:27)
at org.mule.module.dynamicscrm.generated.connectivity.DynamicsCRMConnectorOnlineConnectionConfigConnectionManagementConnectionManager.test(DynamicsCRMConnectorOnlineConnectionConfigConnectionManagementConnectionManager.java:447)
at org.mule.tooling.metadata.api.utils.ConnectionTester.internalTestConnection(ConnectionTester.java:88)
at org.mule.tooling.metadata.api.utils.ConnectionTester.testConnectionFor(ConnectionTester.java:113)
at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction$1$1$1$1.call(TestConnectorConnectionFromMuleConfigAction.java:68)
at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction$1$1$1$1.call(TestConnectorConnectionFromMuleConfigAction.java:1)
at org.mule.tooling.utils.SilentRunner.run(SilentRunner.java:25)
at org.mule.tooling.core.StudioDesignContextRunner.runSilentWithMuleProject(StudioDesignContextRunner.java:17)
at org.mule.tooling.core.StudioDesignContextRunner.runSilentWithMuleProject(StudioDesignContextRunner.java:37)
at org.mule.tooling.messageflow.action.TestConnectorConnectionFromMuleConfigAction$1$1$1.run(TestConnectorConnectionFromMuleConfigAction.java:65)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.xml.sax.SAXParseException; lineNumber: 45; columnNumber: 3; The element type "meta" must be terminated by the matching end-tag "</meta>".
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
at org.mule.module.dynamicscrm.connection.utils.DynamicsCrmConnectionUtils.downloadUrlIntoDocument(DynamicsCrmConnectionUtils.java:228)
at org.mule.module.dynamicscrm.security.online.MicrosoftOnlineAuthenticationPolicy.initialize(MicrosoftOnlineAuthenticationPolicy.java:73)
at org.mule.module.dynamicscrm.security.online.MicrosoftOnlineAuthenticationPolicy.<init>(MicrosoftOnlineAuthenticationPolicy.java:65)
at org.mule.module.dynamicscrm.connection.OnlineConnectionStrategy.createServiceForOnline(OnlineConnectionStrategy.java:95)
... 14 more
java.lang.Throwable: org.mule.api.ConnectionException: Error trying to create the security policy
at
It seems the configuration xml is not getting parsed successfully due to validation errors.Below line in exception trace clearly suggest that.
The element type "meta" must be terminated by the matching end-tag
""
We are trying to run https request in Jmeter 3.1.
But while executing getting following error.
javax.net.ssl.SSLException: Received fatal alert: protocol_version
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)
at sun.security.ssl.AppOutputStream.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
at java.io.BufferedOutputStream.flush(Unknown Source)
at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:828)
at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2116)
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at org.apache.jmeter.protocol.http.sampler.HTTPHC3Impl.sample(HTTPHC3Impl.java:269)
at org.apache.jmeter.protocol.http.sampler.HTTPSamplerProxy.sample(HTTPSamplerProxy.java:74)
at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1166)
at org.apache.jmeter.protocol.http.sampler.HTTPSamplerBase.sample(HTTPSamplerBase.java:1155)
at org.apache.jmeter.threads.JMeterThread.executeSamplePackage(JMeterThread.java:475)
at org.apache.jmeter.threads.JMeterThread.processSampler(JMeterThread.java:418)
at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:249)
at java.lang.Thread.run(Unknown Source)
We tried following solutions but did't solved the issue:
added "https.default.protocol=TLSv1" in "jmeter.properties" file
Tried solution provided in
http://rajanmanoj.blogspot.in/2011/02/how-to-test-ssl-using-jmeter.html
this link
We are Using Jmeter 3.1, Java Jdk 1.7, Windows 7
Https default protocol may vary depending on the version of JVM.
You can change it. Go to jmeter home directory. Open jmeter.properties file. Uncomment line:
https.default.protocol=SSLv3
May be you need to restart jmeter after change. Not sure about that.
This is highly due to protocol version mismatch. There is mismatch between SSL protocol version used by the client and the server.
Make sure that you have latest version of Java and JMeter installed in your system. Also check for the security certificate in JMETER_HOME\bin folder.
You can check this question for more details.
Is there anyone having experience with DominoTomcatSSO project? (see here http://www.openntf.org/internal/home.nsf/project.xsp?action=openDocument&name=DominoTomcatSSO )
I'm running Tomcat 6.0.37 and Domino 9 server. I have configured everything and can't see any error on Domino console. When I try to login in my Tomcat application and mistype the password, Domino and Tomcat correctly report, that username/password is incorrect so things are working fine. But when I type the correct password, I'm getting an error in my Tomcat application as below. When I look into my browser cookies, the LtpaToken is there but somehow cannot be used when creating a Notes Session as in error message. Any hint what can be wrong here?
NotesException - 4616 Cookie is invalid
NotesException: Cookie is invalid
at lotus.domino.NotesExceptionHelper.read(Unknown Source)
at lotus.domino.NotesExceptionHolder._read(Unknown Source)
at lotus.priv.CORBA.iiop.RepImpl.invoke(Unknown Source)
at lotus.priv.CORBA.portable.ObjectImpl._invoke(Unknown Source)
at lotus.domino.corba._IObjectServerStub.createSessionWithCookie(Unknown Source)
at lotus.domino.cso.Session.initSession(Unknown Source)
at lotus.domino.cso.Session.<init>(Unknown Source)
at lotus.domino.cso.Session.createSession(Unknown Source)
at lotus.domino.NotesFactory.createSessionC(Unknown Source)
at lotus.domino.NotesFactory.createSession(Unknown Source)
at com.automatedlogic.domino.sso.DominoBridge.openDominoSession(DominoBridge.java:84)
at com.automatedlogic.domino.sso.DominoBridge.openDominoSession(DominoBridge.java:68)
at com.automatedlogic.domino.sso.DominoUserProfile.refresh(DominoUserProfile.java:180)
at com.automatedlogic.domino.sso.DominoLoginFilter.doFilter(DominoLoginFilter.java:141)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:879)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:617)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1760)
at java.lang.Thread.run(Thread.java:722)
Just found a problem, see URL below. I have updated the InternetSite configuration (descriptive name) based on point 1 from the answer in URL below.
http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21202709