Getting the below error while stopping the Apache ActiveMQ 5.15.6. Setting the createConnector="false" becuase do not want default JMX connection.
Note:- Start the ActiveMQ(activemq-admin.bat start)
Stop the ActiveMQ(activemq-admin.bat stop)
<managementContext createConnector="false"/>
Error:
Connecting to JMX URL:
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi INFO: Broker not
available at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
Related
I followed steps as mentioned in Azure ServiceBus JMS Sample with below properties
spring.jms.servicebus.connection-string=Endpoint=sb://test-dt.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=key
spring.jms.servicebus.topic-client-id=12345
spring.jms.servicebus.idle-timeout=18000
spring.jms.servicebus.pricing-tier=Standard
however I get below error
ERROR 43904 --- [ntContainer#0-1] org.apache.qpid.jms.JmsConnection : Failed to connect to remote at: amqps://test-dt.servicebus.windows.net:-1
ERROR 43904 --- [ntContainer#0-1] o.s.j.l.DefaultMessageListenerContainer : Could not refresh JMS Connection for destination 'test-topic' - retrying using FixedBackOff{interval=5000, currentAttempts=6, maxAttempts=unlimited}. Cause: handshake timed out after 10000ms
On the other hand, I followed steps as mentioned in ServiceBus without JMS and added transportType as AmqpTransportType.AMQP_WEB_SOCKETS then I am able to connect.
We want to implement using spring boot starter and listener method, instead of calling from (public static void main) method.
Please guide on what am I missing when following first link
ERROR 43904 --- [ntContainer#0-1] org.apache.qpid.jms.JmsConnection : Failed to connect to remote at: amqps://test-dt.servicebus.windows.net:-1
To resolve above error, try as suggested by Anand Sowmithiran:
Check if port 5671 is blocked:
telnet <yournamespacename>.servicebus.windows.net 5671
Note: Clients that use AMQP connections over TCP require ports 5671 and 5672 to be opened in the firewall. Along with these ports, it might be necessary to open additional ports if the EnableLinkRedirect feature is enabled.
You can refer to Troubleshooting guide for Azure Service Bus, AMQP outbound port requirements and Port 5671 Blocked :(. What are other options?
I made Java Enterprise app using Java 15.0.2 and GlassFish 4.1.1.
This is what I got in glassfish output:
`C:\Users\s\Documents\Java\glassfish4\glassfish\bin\asadmin.bat start-domain domain1
Attempting to start domain1.... Please look at the server log for more details.....
C:\Users\s\.jdks\openjdk-15.0.2\bin\java.exe -Dfile.encoding=windows-1252 -classpath C:\Users\s\AppData\Local\Temp\classpath1367306742.jar com.intellij.javaee.oss.process.JavaeeProcess 64094 com.intellij.javaee.oss.glassfish.agent.Glassfish31Agent
[2021-03-19 09:07:21,872] Artifact demo:war exploded: Waiting for server connection to start artifact deployment...
Detected server admin port: 4848
Detected server http port: 8080
`
Unable to ping server at localhost 4848
Use the ping-connection-pool subcommand in remote mode to test if a connection pool is usable. For example, if you create a new JDBC connection pool for an application that is expected to be deployed later, you can test the JDBC pool with this subcommand before the application is deployed. Running a ping will force the creation of the pool if it hasn't already been created.
Before You Begin
According to Oracle Glassfish admin guide
Before you can contact a connection pool, the connection pool must be created with authentication, and the server or database must be running.
Ensure that the server is running.
Remote subcommands require a running server.
Ping a connection pool by using the ping-connection-pool(1) subcommand.
While adding a document using solr cloud server I'm getting following exception
60 [main] INFO org.apache.solr.common.cloud.ConnectionManager - Waiting for client to connect to ZooKeeper
65 [main-SendThread(jmajeed.ibsorb.com:8982)] INFO org.apache.zookeeper.ClientCnxn - Opening socket connection to server jmajeed.ibsorb.com/192.168.70.91:8982. Will not attempt to authenticate using SASL (unknown error)
69 [main-SendThread(jmajeed.ibsorb.com:8982)] INFO org.apache.zookeeper.ClientCnxn - Socket connection established to jmajeed.ibsorb.com/192.168.70.91:8982, initiating session
Exception in thread "main" java.lang.RuntimeException: java.util.concurrent.TimeoutException: Could not connect to ZooKeeper 192.168.70.91:8982/#/hotelcontent within 10000 ms
Does anybody has any idea why this is happening??
Thanks.
Have the disturbed the default configuration of solr nodes because by default if you do not specify the port the first node in the cluster will start in 8983 port so check this first. If this is not the problem then check whether the cluster is up or not by accessing admin UI of solr cloud. Then see whether all the shards in the cluster are alive by clicking on the cloud tab.
If everything is fine and still you are facing the above problem then are you trying to access a remote solr cloud server and it is firewall issue.
I have a Jboss 7 server running & accepting secure connections on port 443.
All along i was testing locally which was working fine . However now when i make connection attempts i get a
"javax.naming.NamingException: Failed to create proxy [Root exception is java.lang.IllegalStateException: ..." .
I tried to follow what is written # EJB invocations from a remote client using JNDI
I guess my jndi.properties & jboss-ejb-client.properties file need changes . I think i got it right but still no success .
1 ) jndi.properties
java.naming.factory.url.pkgs=org.jboss.ejb.client.naming
2 ) jboss-ejb-client.properties
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
remote.connections=default
remote.connection.default.host=10.160.148.61
remote.connection.default.port = 4447
remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
Any suggestions anyone . Making the port 443 also doesnt help .
My ejb call from the client
InitialContext aJNDI = new InitialContext();
Ppi handle = (Ppi) aJNDI
.lookup("ejb:PPIEAR/PService/PConnect!com.gem.p.PConnection?stateful");
Posting Full stracktrace :
log4j: Finished configuring.
- JBoss EJB Client version 1.0.5.Final
- XNIO Version 3.0.3.GA
- XNIO NIO Implementation Version 3.0.3.GA
- JBoss Remoting version 3.2.3.GA
- Could not register a EJB receiver for connection to remote://10.160.148.61:4447
java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:93)
at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:121)
at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.<init>(ConfigBasedEJBClientContextSelector.java:78)
at org.jboss.ejb.client.EJBClientContext.<clinit>(EJBClientContext.java:77)
at org.jboss.ejb.client.EJBClient.createSession(EJBClient.java:160)
at org.jboss.ejb.client.naming.ejb.EjbNamingContext.doCreateProxy(EjbNamingContext.java:135)
at org.jboss.ejb.client.naming.ejb.EjbNamingContext.createEjbProxy(EjbNamingContext.java:113)
at org.jboss.ejb.client.naming.ejb.EjbNamingContext.lookup(EjbNamingContext.java:96)
at javax.naming.InitialContext.lookup(Unknown Source)
..
Quoting this page:
WARN: Could not register a EJB receiver for connection to
remote://10.160.148.61:4447 java.lang.RuntimeException: Operation failed
with status WAITING
This is commonly caused by a wrong combination of IP or port in the file jboss-ejb-client.properties.
You might be unable to reach that host address
Maybe you are using a port-offset on that server, so instead of port 4447 you should use 4447 + offset
You could start by testing if you can connect to your target using telnet:
telnet 10.160.148.61 4447
Red5 takes more time while starting in centOS. I checked the stdout.log. There is JMX timeout error.
[ERROR] [main] org.red5.server.jmx.JMXAgent - {}
java.io.IOException: Cannot bind to URL [rmi://:9999/red5]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 69.164.154.24; nested exception is:
java.net.ConnectException: Connection timed out]
How to disable JMX in red5..?
Red5 used JMX for monitoring deployed application from remote. By default port 9999 used for JMX. It will wait for upto 100/200 seconds if program can not able to make connection with port 9999. To disable JMX monitoring you have to set false for "enableRmiAdapter" in red5-common.xml in conf folder of red5 server.
<bean id="jmxAgent" class="org.red5.server.jmx.JMXAgent" init-method="init">
<!-- The RMI adapter allows remote connections to the MBeanServer -->
<property name="enableRmiAdapter" value="false"/>
....
FYI I am using red5-0.9.1 and JMX port and host configuration in red5.properties file.
For 1.0 and more follow this https://code.google.com/p/red5/wiki/SlowStartup