Develop Reference

What could be the reason for consumer of JMS queue being unable to read and returns error: Not authorised?

Error message:
Setup of JMS message listener invoker failed for destination 'topic://XXX.XXX' - trying to recover. Cause: User <XXXX> is not authorized to read from: topic://xxxx.xxxx
The URL is correct. The user/password is correct. The certificate file is present. What else can I check to understand the issue?

The error message indicates the user is "not authorized." In other words, the user doesn't have permission to read from the specified topic. This can happen even if the credentials (i.e. user, password, certificate) allow successful authentication since authentication and authorization are separate (but related) concerns.
You'll need to check the authorization configuration for whatever JMS broker you're using.

Found the issue.
Indeed it was something to do with JMS configuration.
The topic was published as XXX., while we were trying to connect to YYY.
The error was misleading.
Thanks

SOAP web service returns data on and off

My source system provides SOAP url (hosted in IIS server) which we use it to get data, but lately we cannot pull data where it fails with nothing more than this msg in my side
"org.apache.axiom.om.OMException: SOAP message MUST NOT contain a Document Type Declaration(DTD)"
When the issue was debugged on the other side we got the following error
DEBUG httpclient.333.content [main] << " [0x9]IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred."
The team that developed this service too cannot provide us anything useful info like where their app fails or any other useful info. A bizzare scenario occurs every now and then, wherein a data pull is successful in a test server but fails in prod server even when both of them point to the same SOAP url.
Everything worked fine as long as they hosted it in Apache tomcat, things worsened after they moved to IIS.
I want to know what settings to be looked at to resolve the issue.

MSMQ error while trying to access remote private queue.Cannot open queue. (hr=unknown hr (-2147023071))

MSMQ error while trying to access remote private queue.
Exception: Cannot open queue. (hr=unknown hr (-2147023071))
I already added these two:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters\Security\AllowNonauthenticatedRPC and set the value to 1.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters\Security\NewRemoteReadServerAllowNoneSecurityClient and set it to 1

-2147023071 is 0x80070721 which isn't an MSMQ-specific error code (as they start 0xC00Exxxx). I believe this is a security-related error code.
As you are receiving messages from a remote queue, you are using the RPC protocol so this article will help:
Understanding how MSMQ security blocks RPC traffic
Sending a message uses the MSMQ protocol and so does not have the same problems.

Pubnub Socket Timeout exception

This is the error I get in PubNub, when I publish. I am publishing from a normal Java file on eclipse.
[Error: 103-2] : HTTP Error. Please check network connectivity. Please contact support with error details if issue persists. : java.net.SocketTimeoutException: connect timed out
My network is connected and is working. Ping requests to google & other servers are successful. Yet, the error keeps occurring randomly.

Proxy Error 502 : The proxy server received an invalid response from an upstream server

We are building a mass mailing sending application in Java. Mail is being send by third party SMTP. After sending 400-500 mails tomcat6 service get stopped. Below is the error.
Proxy Error
The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET
/lin/Campaignn.jsp.
Reason: Error reading from remote server
Additionally, a 502 Bad Gateway error was encountered while trying to use an ErrorDocument to handle the request.
Apache Server at msizzler.com Port 80
But when we are sending from localhost I did not received any error. It send all the mails.
Please help me to sort it out this problem.

The HTTP 502 "Bad Gateway" response is generated when Apache web server does not receive a valid HTTP response from the upstream server, which in this case is your Tomcat web application.
Some reasons why this might happen:
Tomcat may have crashed
The web application did not respond in time and the request from Apache timed out
The Tomcat threads are timing out
A network device is blocking the request, perhaps as some sort of connection timeout or DoS attack prevention system
If the problem is related to timeout settings, you may be able to resolve it by investigating the following:
ProxyTimeout directive of Apache's mod_proxy
Connector config of Apache Tomcat
Your network device's manual

Add this into your httpd.conf file
Timeout 2400
ProxyTimeout 2400
ProxyBadHeader Ignore

The java application takes too long to respond(maybe due start-up/jvm being cold) thus you get the proxy error.
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /lin/Campaignn.jsp.
As Albert Maclang said amending the http timeout configuration may fix the issue.
I suspect the java application throws a 500+ error thus the apache gateway error too. You should look in the logs.

I had this issue once. It turned out to be database query issue. After re-create tables and index it has been fixed.
Although it says proxy error, when you look at server log, it shows execute query timeout. This is what I had before and how I solved it.

I had this problem too.
I was using apache as a reverse proxy for tomcat, my problem was associated with the return time of the response for "apache" proxy
I solved it like this:
open the "etc/apache/apache2.conf" and the ssl mod conf file "etc/apache/sites-available/000-default-le-ssl.conf" and add the following lines:
Timeout 28800
KeepAlive On
maybe this will help you