I'm working on a apache pulsar cluster and it was working fine, but for some reason I started getting the following message when I try to send a message:
ERROR [id: 0xc5de4911, L:/127.0.0.1:55672 - R:localhost/127.0.0.1:6650] Close connection becaues received internal-server error java.lang.IllegalArgumentException: bound must be positive
Also i'm getting the following error:
persistent://global/mycluster-cluster1/ns1/topic-partition-0] [null] Error connecting to broker: org.apache.pulsar.client.api.PulsarClientException$LookupException: org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /loadbalance/brokers/ip-11-55-123-80.ec2.internal:8080
I know the topic is created because i doble checked it using the pulsar-admin cli. I'm lost on where to start looking anyone could point me out.
from the error message, it seems to be a race condition when Pulsar splits a namespace bundle. What version of Pulsar are you using?
Related
Short description of the issue:
I'm using ActiveMQ 5.10.2 (AMQ) in a project where I have Application A sending data over to Application B via amq and saw this exception :
javax.jms.JMSException: Could not post command: KeepAliveInfo
Here's the full stack trace:
ERROR JMSConsumer:148 - Consumer Exception
javax.jms.JMSException: Could not post command: KeepAliveInfo {} due to: java.net.SocketTimeoutException: Read timed out
at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
...
Caused by: java.io.IOException: Could not post command: KeepAliveInfo {} due to: java.net.SocketTimeoutException: Read timed out
at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)
at org.apache.activemq.transport.http.HttpClientTransport.oneway(HttpClientTransport.java:138)
...
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
That exception was seen in App B and due to this exception it could not connect to the AMQ. Restarting the app allowed it to talk to the AMQ again.
Does anyone know how I can reproduce that exception so I can do proper error handling/recovery?
More details about the issue:
As mentioned above, I'm trying to recreate the exception to do proper error handling/recovery. But so far I'm unable to reproduce it.
I've looked online and don't see too much on this specific exception nor on the keepaliveinfo message other than from activemq's own site.
Per its link https://activemq.apache.org/activemq-inactivitymonitor if the useInactivityMonitor parameter is set to true, which is the default value, then the apps connecting to that AMQ on the same topic/queue will have that keepaliveinfo message sent if it doesn't detect any normal traffic. In my environment that parameter is set to true
My thought is, with this value set to true, something happened in my environment (perhaps the AMQ got in a funky state or was low in memory) that it failed to handle a keepaliveinfo message sent from my apps and then that jms exception occurred.
In trying to reproduce that exception I have done the following tests to no avail:
Test 1:
Start App A, App B and the AMQ. After everything is up and running and data is flowing I would then stop the AMQ broker.
I got this exception :
javax.jms.JMSException: Failed to perform GET on: <my amq ip>:443 Reason: Connection refused: connect
Which isn't the exception I noticed before.
Test 2:
I would start App A, App B, and the AMQ, and then after everything is up and running I would then stop App A (which sends data to App B via AMQ).
I did not witness any keepaliveinfo messages getting sent and more importantly I don't see the specific jms exception above.
Test 3:
I started App B and the AMQ. I modified App A to connect to the AMQ but commented out the code that sends data to App B on the queue/topic.
Again I did not witness this message JMSException: could not post command: keepaliveinfo
Test 4
I modified the AMQ broker activemq.xml file to have its <memoryUsage> <storeUsage> and <tempUsage> values to be really low. In a way to simulate that the ActiveMQ is super busy and can't handle more data being sent. More info on those parameters are mentioned here https://activemq.apache.org/producer-flow-control.html
After restarting AMQ and App A and App B, I still didn't witness that exception message.
End of tests
So again, does anyone know what is the setup/conditions on reproducing this issue?
Extra note:
It seems like I can avoid this exception altogether if I set the useInactivityMonitor parameter to false. With that set then no keepaliveinfo messages are sent if no normal traffic occurs over a connection. But I don't want to change it to false.
And here is my pom file defining the amq artifact id's:
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-all</artifactId>
<version>5.10.2</version>
</dependency>
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-http</artifactId>
<version>5.10.2</version>
</dependency>
I am following the link for Enabling Basic Authentication in solr 4.3.
https://lucidworks.com/blog/2015/08/17/securing-solr-basic-auth-permission-rules/
and when o am uploading security.json to ZooKeeper by
scripts/cloud-scripts/zkcli.sh -zkhost localhost:8983 -cmd putfile /security.json security.json
but getting the following Error:
WARN - 2016-06-16 23:19:28.798; org.apache.zookeeper.ClientCnxn$SendThread; Session 0x0 for server localhost/127.0.0.1:8983, unexpected error, closing socket connection and attempting reconnect
java.io.IOException: Packet len1213486160 is out of range!
at org.apache.zookeeper.ClientCnxnSocket.readLength(ClientCnxnSocket.java:112)
at org.apache.zookeeper.ClientCnxnSocketNIO.doIO(ClientCnxnSocketNIO.java:79)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:366)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
Can anyone please help to resolve this issue.
I think issue is port number you are using port 8983 which is your host port. Solr run Zookeeper on hostPort+1000, so in your case port number would be localhost:9983
After general server configuration i'm able to log in to carbon, store or publisher without any issue with default admin login.
Unfortunately when i sign in EMM: https://myserver:port/emm -> sso/login
i end up in /emm/acs - "500: Something has gone wrong" page.
Debug: 2 errors in live terminal:
*[2015-06-12 20:35:21,254] ERROR {org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject} - Connection refused java.net.ConnectException: Connection refused*
*[2015-06-12 20:35:21,261] ERROR {org.jaggeryjs.jaggery.core.manager.WebAppManager} - org.mozilla.javascript.WrappedException: Wrapped org.jaggeryjs.scriptengine.exceptions.ScriptException: java.net.ConnectException: Connection refused (http#220)
org.jaggeryjs.scriptengine.exceptions.ScriptException: org.mozilla.javascript.WrappedException: Wrapped org.jaggeryjs.scriptengine.exceptions.ScriptException: java.net.ConnectException: Connection refused (http#220)*
And i got another 2 errors after wso2server startup:
*[2015-06-12 21:44:34,231] ERROR {org.wso2.carbon.apimgt.keymgt.internal.APIKeyMgtServiceComponent} - Error in initializing thrift transport
org.apache.thrift.transport.TTransportException: Could not bind to port 10397*
*[2015-06-12 21:44:34,247] ERROR {org.wso2.carbon.apimgt.keymgt.internal.APIKeyMgtServiceComponent} - Failed to initialize key management service.
java.lang.Exception: Error in initializing thrift transport*
Any hints?
Regards,
Lukas
I encountered with the /emm/acs redirection issue, actually I don't know why it has been happening, but when it happens, I do a refresh on the page, everything works fine.
The second issue you have mentioned, is nothing to do with the first one, it says that Apache Thrift Transport layer could not bind the port. Since EMM does not require Thrift, you can simply disable by editing the following XML configuration files.
Change true to false for the following config files, under the target folder.
./repository/conf/api-manager.xml:280: <EnableThriftServer>true</EnableThriftServer>
./repository/conf/identity.xml:218: <EnableThriftService>true</EnableThriftService>
Getting below error with MQ(Message Queue), how to resolve this?
Message : com.ibm.msg.client.jms.DetailedJMSException: JMSWMQ1107: A problem with
this connection has occurred. An error has occurred with the WebSphere MQ JMS
connection. Use the linked exception to determine the cause of this error.
Caused by [1] -->
Message : com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with
compcode '2' ('MQCC_FAILED') reason '2009' ('MQRC_CONNECTION_BROKEN').
Caused by [3] -->
Message : com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009;AMQ9208: Error on receive
from host '/xx.xx.xx.xx:xxxx
(emb701t7.dci.bt.com)'. [1=-1,2=ffffffff,3=/xx.xx.xx.xx:xxxx
(emb701t7.dci.bt.com),4=TCP]
Please take me forward.
I faced the same error and its resolved now!
As Magic Wand mentioned in the comment, below error comes up if you have a lower version of MQ jar i.e if your MQ jar version is 7.0.1.5 or below
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2009;AMQ9208: Error on receive from host
This bug has been fixed in IBM MQ version 7.0.1.6 or higher as mentioned here: http://www-01.ibm.com/support/docview.wss?uid=swg1IV00348
Add the newer version of below ibm.mq jars and make sure you have the additional jars too mentioned below:
com.ibm.mq.commonservices.jar
com.ibm.mq.jar
com.ibm.mq.jmqi.jar
com.ibm.mqbind.jar
com.ibm.mqjms.jar
fscontext.jar
jms-1.1-20020430.jar
providerutil.jar
The TCP connection between the MQ client running in weblogic and the MQ Queue Manager channel process is being broken unexpectedly (that is what the return code 2009 means). This could be down to a number of issues such as the queue manager being killed, the channel process exiting for some reason, a firewall killing the connection etc. Have a look on the MQ queue manager error logs for issues with the channel process at the same time. Take a note of how often the error message occurs i.e. is the first error 2 hours after the weblogic server starts.
You could take a network trace to see how the TCP connection is being closed and by who.
I'm trying to deploy my java based appengine app through the eclipse plugin. I get an error at the very end of the process whichI pasted below. Any ideas what this could mean?
com.google.appengine.tools.admin.AdminException: Unable to update app: Error posting to URL: http://appengine.google.com/api/queue/update?app_id=ipoobeta&version=v1-6&
500 Internal Server Error
Server Error (500)
A server error has occurred.
at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:62)
at com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java:271)
at com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java:148)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.io.IOException: Error posting to URL: http://appengine.google.com/api/queue/update?app_id=ipoobeta&version=v1-6&
500 Internal Server Error
Server Error (500)
A server error has occurred.
at com.google.appengine.tools.admin.ServerConnection.send(ServerConnection.java:143)
at com.google.appengine.tools.admin.ServerConnection.post(ServerConnection.java:81)
at com.google.appengine.tools.admin.AppVersionUpload.send(AppVersionUpload.java:522)
at com.google.appengine.tools.admin.AppVersionUpload.updateQueue(AppVersionUpload.java:255)
at com.google.appengine.tools.admin.AppVersionUpload.doUpload(AppVersionUpload.java:134)
at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:56)
... 4 more
Since this question was written there have been many enhancements to the serving infrastructure of Google App Engine. Be sure you are using the High Replication Datastore (HRD). It is extremely unlikely that you will encounter this type of error and if you do it will be transient.