Open kyawswar87 opened 2 years ago
I used mysql version 5.7.29
Now I found the root cause of the error. Because I got the JMS error as following
[2022-06-14 13:00:40,846] ERROR - AMQConnection Throwable Received but no listener set. org.wso2.andes.AMQDisconnectedException: Server closed connection and reconnection not permitted. at org.wso2.andes.client.protocol.AMQProtocolHandler.closed(AMQProtocolHandler.java:274) ~[andes_3.3.23.jar:?] at org.wso2.andes.transport.network.mina.MinaNetworkHandler.sessionClosed(MinaNetworkHandler.java:150) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.sessionClosed(AbstractIoFilterChain.java:548) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain.callNextSessionClosed(AbstractIoFilterChain.java:267) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain.access$800(AbstractIoFilterChain.java:51) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.sessionClosed(AbstractIoFilterChain.java:631) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.IoFilterAdapter.sessionClosed(IoFilterAdapter.java:65) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain.callNextSessionClosed(AbstractIoFilterChain.java:267) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain.access$800(AbstractIoFilterChain.java:51) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.sessionClosed(AbstractIoFilterChain.java:631) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:230) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:264) ~[andes_3.3.23.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_322] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_322] at org.wso2.org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51) ~[andes_3.3.23.jar:?] at java.lang.Thread.run(Thread.java:750) [?:1.8.0_322] [2022-06-14 13:00:40,846] ERROR - JMSListener JMS Provider is not yet started. Please start the JMS provider now. [2022-06-14 13:00:40,846] ERROR - JMSListener Connection attempt : 3 for JMS Provider failed. Next retry in 80 seconds [2022-06-14 13:00:40,847] ERROR - JMSListener JMS Provider is not yet started. Please start the JMS provider now. [2022-06-14 13:00:40,847] ERROR - JMSListener Connection attempt : 3 for JMS Provider failed. Next retry in 80 seconds [2022-06-14 13:00:40,861] ERROR - AMQConnection Throwable Received but no listener set. org.wso2.andes.AMQDisconnectedException: Server closed connection and reconnection not permitted. at org.wso2.andes.client.protocol.AMQProtocolHandler.closed(AMQProtocolHandler.java:274) ~[andes_3.3.23.jar:?] at org.wso2.andes.transport.network.mina.MinaNetworkHandler.sessionClosed(MinaNetworkHandler.java:150) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain$TailFilter.sessionClosed(AbstractIoFilterChain.java:548) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain.callNextSessionClosed(AbstractIoFilterChain.java:267) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain.access$800(AbstractIoFilterChain.java:51) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.sessionClosed(AbstractIoFilterChain.java:631) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.IoFilterAdapter.sessionClosed(IoFilterAdapter.java:65) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain.callNextSessionClosed(AbstractIoFilterChain.java:267) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain.access$800(AbstractIoFilterChain.java:51) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.common.support.AbstractIoFilterChain$EntryImpl$1.sessionClosed(AbstractIoFilterChain.java:631) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.filter.executor.ExecutorFilter.processEvent(ExecutorFilter.java:230) ~[andes_3.3.23.jar:?] at org.wso2.org.apache.mina.filter.executor.ExecutorFilter$ProcessEventsRunnable.run(ExecutorFilter.java:264) ~[andes_3.3.23.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_322] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_322] at org.wso2.org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:51) ~[andes_3.3.23.jar:?] at java.lang.Thread.run(Thread.java:750) [?:1.8.0_322] [2022-06-14 13:00:40,861] ERROR - JMSListener JMS Provider is not yet started. Please start the JMS provider now. [2022-06-14 13:00:40,861] ERROR - JMSListener Connection attempt : 3 for JMS Provider failed. Next retry in 80 seconds [2022-06-14 13:00:40,874] ERROR - JMSListener JMS Provider is not yet started. Please start the JMS provider now. [2022-06-14 13:00:40,874] ERROR - JMSListener Connection attempt : 3 for JMS Provider failed. Next retry in 80 seconds
I ignored this error and tried to create new endpoints. And the APIM response 404 for this new endpoint.
Solution: I tried to solve for JMS ERROR as following. https://stackoverflow.com/questions/70638927/wso2-apim-4-jms-provider-is-not-yet-started
I changed my admin password without including '@' character. And this JMSListener ERROR is gone.
And 404 Not found error is solved now. I don't need to restart APIM server after create new endpoint.
Thanks.
This issue is NOT closed with a proper Resolution/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.
- Resolution/Cannot Reproduce - Issue cannot be reproduced.
- Resolution/Duplicate - Issue is already reported before.
- Resolution/Fixed - Issue has already been fixed.
- Resolution/Answered - Issue has already been answered.
- Resolution/Invalid - Issue is invalid.
- Resolution/Not a bug - Issue is not a bug.
- Resolution/Postponed - Issue is postponed.
- Resolution/Won’t Fix - Issue won't be fixed.
Resolution/Not a bug
This issue is NOT closed with a proper Resolution/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.
- Resolution/Cannot Reproduce - Issue cannot be reproduced.
- Resolution/Duplicate - Issue is already reported before.
- Resolution/Fixed - Issue has already been fixed.
- Resolution/Answered - Issue has already been answered.
- Resolution/Invalid - Issue is invalid.
- Resolution/Not a bug - Issue is not a bug.
- Resolution/Postponed - Issue is postponed.
- Resolution/Won’t Fix - Issue won't be fixed.
Resolution/Not a bug
This issue is NOT closed with a proper Resolution/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.
- Resolution/Cannot Reproduce - Issue cannot be reproduced.
- Resolution/Duplicate - Issue is already reported before.
- Resolution/Fixed - Issue has already been fixed.
- Resolution/Answered - Issue has already been answered.
- Resolution/Invalid - Issue is invalid.
- Resolution/Not a bug - Issue is not a bug.
- Resolution/Postponed - Issue is postponed.
- Resolution/Won’t Fix - Issue won't be fixed.
Resolution/Not a bug - Issue is not a bug.
This issue is NOT closed with a proper Resolution/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.
- Resolution/Cannot Reproduce - Issue cannot be reproduced.
- Resolution/Duplicate - Issue is already reported before.
- Resolution/Fixed - Issue has already been fixed.
- Resolution/Answered - Issue has already been answered.
- Resolution/Invalid - Issue is invalid.
- Resolution/Not a bug - Issue is not a bug.
- Resolution/Postponed - Issue is postponed.
- Resolution/Won’t Fix - Issue won't be fixed.
Description
I got 404 Not found issue after creation new endpoint. There is no such issue on H2 db. But when I used Mysql, I got such error.
I need to restart the APIM on every time I create new endpoints to load the new endpoints.
Steps to Reproduce
I just added the Mysql in
deployment.toml
as below.add into mysql connector jar into
./wso2am-4.1.0/repository/components/lib/mysql-connector-java-5.1.49.jar
Affected Component
APIM
Version
4.1.0
Environment Details (with versions)
OS: CentOS Linux release 7.9.2009 (Core)
uname -r 3.10.0-1160.62.1.el7.x86_64
Relevant Log Output
Related Issues
No response
Suggested Labels
Affected/APIM-4.1.0