I am connecting 2 different application using web-logic jms bridge.
But when I check for bridge its showing in warning state and error is fail to connect target. and after some time server is go in warning state.
Can anyone help me in this?
Exception [JMSException045028] the message threshold for jms server
***** has been exceeded more than one hour.
using weblogic 12c
Related
I want to check whether my JBoss EAP 7 is started via jboss-cli.
With JBoss EAP 6 I could use the following command
jboss-cli.bat -c --commands="read-attribute server-state"
While the server is starting, the response is starting. When the server booted successfully, the response is running.
After migrating to JBoss EAP 7.0, the same command returns the following message, while the server is starting. Failed to connect to the controller: Timeout waiting for the system to boot. When the server started successfully, the usual message running is returned.
My question is: Why can't the jboss-cli connect to the server until it started?
In EAP 7.x and EAP 6.3.0 or later, you can configure jboss.as.management.blocking.timeout system property to tune timeout (seconds) waiting for service container stability.
Try setting this parameter once connected via CLI.
Since EAP 6.3.0.ER8 there is a new class in jboss.as.controller: BlockingTimeout. This class loads the value of system property jboss.as.management.blocking.timeout or defaults to 300 (seconds).
Note: This property is not a timeout per deployment but a timeout on container stability and if jboss.as.management.blocking.timeout is reached during startup then all applications will be undeployed and the container shutdown. The reasoning behind this is that having a half-working server is potentially dangerous as you may not notice major failures.
Thus if your application is unable to load within the given timeout value,CLI will throw the errorFailed to connect to the controller: Timeout waiting for the system to boot
jboss-cli.sh --connect --controller=IP:PORT --timeout=40000 configure timeouts value to be more then the amount of time your server takes to start.
Actual command line is
./jboss-cli.sh --connect command=":read-attribute(name=server-state)"
"Your request timed out" message on management console of WildFly domain mode while starting the server instance.
Its' not clear that whether an operation like server start-up or deployment has been succeeded or not.
It requires two or three restart commands from the management GUI before the domain controller correctly displays the running status of WildFly instances.
I found that "request timed out" message appears after cca 20-21 seconds when I do restart server instance.
I use WildFly version 10.1.0.Final in Domain mode.
JBoss doesn't start
and it shows the following error message after trying to connect:
Server JBoss 7.1 Runtime Server was unable to start within 450 second. if the server requires more time, try increasing the timeout in the server editor
When I increase the timeout, it shows the same error message. I tried to change the server and the host name to '172.0.0.1'
Can anyone help me get past this problem or even guide me to a keyword so I can search?
I have WAS MQ 7.1 Server installed in windows. My application running on unix is trying to connect to this server during which it gives the error "MQ Connect failed 2195" in the application logs. On debugging the code , i found it is while connecting to the q manager that it is throwing this error.
I tried to run a netstat on the MQ Server port no. and do a telnet to check if there is any connection being established . But I could not see any connection being established to the q manager .
The possible issues could be
1. Que Manager has not been started
2. Listener not started
3. Initiation queue not started or created or attached(usually optional depending on set up)
4. Listening to the wrong Port or IP
5. Firewall stopping traffic to Port or IP
6. Queue Manager not created on destination
7. Not authorized to Queue manager and/or channel and/or queue
8. Trial MQ copy expired.
9. Wrong Queue manager name
10. Wrong channel name or password or queue or queue type
Have done the following to check if it is working fine .
1. Tried to put a message from windows to the MQ Server which was successful.
2. Gave auth(setmqaut) permission to Request queue that was created.
3. There is no firewall between application and MQ Server.
4. Channel name , q manager , IP and port no.s are correct.
In my windows MQ Setup i have created the Server connection channel and Client connection Channel.
export the mqm lib to SHLIB_PATH.
Added the application user to mqm group and also the windows user through which I had created the MQ Server setup
Had copied the AMQCLCHL.TAB to the unix machine containing the client program.
exported MQCHLTAB to the table filename
exported MQCHLLIB to the path containing the table name
exported the MQSERVER=QMgrName/CHANNEL1/hostname from the client machine.
Please let me know if I am missing anything w.r.t connection of the application(in Unix) to the MQ Server(in Windows).
2195 is MQRC_UNEXPECTED_ERROR. It implies something that should not have happened, even if you set it up wrong. It may well be accompanied with an FDC file in the errors directory. You should raise a PMR with IBM Service.
When my JBoss server is down, my JMS client application repeatedly tries to reconnect to the JMS server. However, after a couple of failed attempts, it connects to any other available servers in the LAN. How can I avoid this ?
It can be resolved by setting the following property when creating the initial context
props.setProperty("jnp.disableDiscovery", "true");