Does Apache Fuse 5.5 supports stomp 1.1 completely?
I am trying to send "NACK" from python client. The connection is made on version 1.1
##############Connected##########
{'body': '', 'headers': {'session': 'ID:ap-pun-ws6099-60937-1327039578399-2:5',
'version': '1.1', 'server': 'ActiveMQ/5.5.1-fuse-01-13', 'heart-beat': '1000,100
0'}, 'cmd': 'CONNECTED'}
but when i send "NACK" it throws exception saying 2012-01-20 13:46:03,815 receiver ERROR Received server error - messageNACK received but connection is in v1.0 mode.
Please help me regarding this.
A bug was found for this and resolved today: https://issues.apache.org/jira/browse/AMQ-3670
Related
I'm using node 14.17.0 and adonisjs 5.8.5.
This is my rabbitmq .env :
RABBITMQ_HOSTNAME=localhost
RABBITMQ_USER=
RABBITMQ_PASSWORD=
RABBITMQ_PORT=15672
RABBITMQ_PROTOCOL= 'amqp://'
I try sendToQueue. But I get that's error. Anyone can help?
When you get the problem. Just change RABBITMQ_PORT=15672 become RABBITMQ_PORT=5672 It will passed.
I wanted to configure XA datasource for Mariadb in REDHAT JBoss EAP 7.0. I
I have created a non-XA datasource with below details and connection is working fine.
Driver: mysql-connector-java-5.1.46.jar_com.mysql.jdbc.Driver_5_1
Connection URL: jdbc:mysql://localhost:3306/test
But when I tried to create new XA datasource for distributed transactions then it fails with error detail.
Unexpected HTTP response: 500
Request
{
"address" => [
("subsystem" => "datasources"),
("xa-data-source" => "MysqlXADS1")
],
"operation" => "test-connection-in-pool"
}
Response<br>
Internal Server Error<br>
{`enter code here`
"outcome" => "failed",
"failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0042: failed to match
pool. Check JndiName: java:/MysqlXADS1",
"rolled-back" => true
}
Configuration Details :
Driver: mysql-connector-java-5.1.46.jar_com.mysql.jdbc.jdbc2.optional.MysqlXADataSource_5_1
Url: jdbc:mariadb://localhost:3306/test
Valid Connection Checker: org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker
Exception Sorter: org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter
JBoss EAP support for MariaDB started on version 7.0 so your version is not a problem.
From the error WFLYJCA0040: failed to invoke operation: WFLYJCA0042: failed to match pool. Check JndiName, and assuming the jdbc name is correctly assigned, I believe your issue will be solved on step 1.3 and 2, as below:
When setting up a data source on JBoss EAP 7.0:
deploy the driver
create the datasource
Verify the pool size, removing the line <max-pool-size>0</max-pool-size> as explained here.
reload
For your version, JBoss EAP 7.0 : Remember to enable the DB:
#/subsystem=datasources/data-source=MyExampleDS:enable()
#/subsystem=datasources/data- source=MyExampleDS:test-connection-in-pool()
I am trying to configure Sonarqube to notify the developers automatically by an email if their is a new issue assigned to their account.
On the settings-page I sent a test-email successfully and I recieved in my inbox (gmail).
But inside the Sonar-Process the notification fails!
Does anyone have experience with that?
org.apache.commons.mail.EmailException: Sending the email to the following server failed : smtp.gmail.com:465
at org.apache.commons.mail.Email.sendMimeMessage(Email.java:1410) ~[commons-email-1.3.2.jar:1.3.2]
at org.apache.commons.mail.Email.send(Email.java:1437) ~[commons-email-1.3.2.jar:1.3.2]
at org.sonar.plugins.emailnotifications.EmailNotificationChannel.send(EmailNotificationChannel.java:182) [sonar-email-notifications-plugin-4.3.2.jar:na]
at org.sonar.plugins.emailnotifications.EmailNotificationChannel.deliver(EmailNotificationChannel.java:130) [sonar-email-notifications-plugin-4.3.2.jar:na]
at org.sonar.plugins.emailnotifications.EmailNotificationChannel.deliver(EmailNotificationChannel.java:106) [sonar-email-notifications-plugin-4.3.2.jar:na]
at org.sonar.server.notifications.NotificationService.dispatch(NotificationService.java:197) [NotificationService.class:na]
Caused by: javax.mail.MessagingException: Unknown SMTP host: smtp.gmail.com
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1970) ~[mail-1.4.5.jar:1.4.5]
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:642) ~[mail-1.4.5.jar:1.4.5]
Caused by: java.net.UnknownHostException: smtp.gmail.com
just restart the server... this is not part of the documentation
I upgraded to ruby 1.9.3 this morning, kept the same version of Rails 3.0.8 and installed / updated passenger-3.0.9. Everything seems to run OK when I launch the application, until I try and login (make a database connection), I get a 502 Bad Gateway and the following error message in the console:
[NOTE] You may have encountered a bug in the Ruby interpreter or
extension libraries. Bug reports are welcome. For details:
http://www.ruby-lang.org/bugreport.html
2011/10/31 08:37:22 [error] 6201#0: *6 upstream prematurely closed
connection while reading response header from upstream, client:
127.0.0.1, server: _, request: "GET /status HTTP/1.1", upstream: "passenger:unix:/passenger_helper_server:", host: "0.0.0.0:3000"
Any ideas? Thank you
This has been discussed in the last week on the Passenger mailing list.
Looks like it's still an open bug:
http://code.google.com/p/phusion-passenger/issues/detail?id=714
Only solution I know of is to downgrade to 1.9.2-p290 until it's fixed.
I want to create a http2 server using node-http2 module without TLS. My code is as follows:
http2 = require('http2');
const bunyan = require('bunyan');
var log = bunyan.createLogger({name: "HTTP2 server without TLS!"});
var options = {
log: log
}
var server = http2.raw.createServer(options, function(request, response) {
console.log("Receiving HTTP2 request!");
// response.writeHead(200);
response.end('Hello world from HTTP2!');
});
server.listen(8000);
However, it does not work. When connecting to this server from chrome, it shows downloading something. When I closed the server, the downloading is finished with blank file (26 bytes).
Does anyone know what is wrong here? Do I need to configure the browser? Thanks in advance!
Chrome and all other browsers only support HTTP/2 over TLS (h2) and not plain HTTP/2 (h2c). So your browser does not understand what is returned from the server and apparently node-http2 does not send a proper error response when it receives a non-http2 request.
The problem seems not just from the browser. Using [curl] curllink that supports http2 over an http:// URL does not working either. Following is the output from the curl:
$ curl -I --http2 http://54.208.83.136:8000/ -v -k
* Trying 54.208.83.136...
* Connected to 54.208.83.136 (54.208.83.136) port 8000 (#0)
> HEAD / HTTP/1.1
> Host: 54.208.83.136:8000
> User-Agent: curl/7.47.1
> Accept: */*
> Connection: Upgrade, HTTP2-Settings
> Upgrade: h2c
> HTTP2-Settings: AAMAAABkAAQAAP__
>
As we see from the curl output. It sends http/1.1 Upgrade request with proper headers set as it supposed to do according to the [http2 rfc] rfclink.
On the server side, the logs were very long, so I present here only the content of msg in the relevant three logs.
New incoming HTTP/2 connection
Client connection header prelude does not match
PROTOCOL ERROR, Fatal error, closing connection
So basically the server closed the connection because the client connection header prelude does not match. By checking the code, I figured out the error was originated from the readPrelude function of [endpoint.js] endpointlink. It is a function to read the client header, but I don't know what is wrong in the client header :(.
Thus maybe I can say the node-http2 module does not support http2 over plaintext.
Update: it turns out that I was wrong. The node-http2 module do support http2 over plaintext with direct connecting, it does not support HTTP/2 server with Upgrade from HTTP/1.1. The problem resulted from the client side using Upgrade mechanism to connect to the server not supporting Upgrade. Using nghttp client to connect sever with prior knowledge works as follows.
$ nghttp http://127.0.0.1:8000/
Hello world from HTTP2!
nghttpd server also supports HTTP2 without TLS, even though it does not support HTTP Upgrade.
$ nghttpd -d /Documents/Proxy 8080 --no-tls -v
So I highly suggest to use nghttp when you want to test HTTP2 without TLS.