Question
Areteans
IN
Last activity: 12 Jul 2024 10:43 EDT
Unable to import application backup in Infinity 24
Not able to import the application backup (Size: 2.5GB) in Infinity 24. It's is loading for 5 minutes and getting error status. We tried couple of methods to import the file but it failed: 1. Import via Import wizard (Both file and file from server) Error on logs: ERROR - Exception: com.datastax.oss.driver.api.core.AllNodesFailedException: Could not reach any contact point, make sure you've provided valid addresses (showing first 1 nodes, use getAllErrors() for more): Node(endPoint=/ Proprietary information hidden:9042, hostId=null, hashCode=808cf3b): [com.datastax.oss.driver.api.core.connection.ConnectionInitException: [s5|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (java.nio.channels.NotYetConnectedException)] at com.datastax.oss.driver.api.core.AllNodesFailedException.copy(AllNodesFailedException.java:141) ~[java-driver-core-shaded-4.17.0.jar:?]
2. Using prpcServiceUtils from my system to the server
Error on logs:
Not able to import the application backup (Size: 2.5GB) in Infinity 24. It's is loading for 5 minutes and getting error status. We tried couple of methods to import the file but it failed: 1. Import via Import wizard (Both file and file from server) Error on logs: ERROR - Exception: com.datastax.oss.driver.api.core.AllNodesFailedException: Could not reach any contact point, make sure you've provided valid addresses (showing first 1 nodes, use getAllErrors() for more): Node(endPoint=/ Proprietary information hidden:9042, hostId=null, hashCode=808cf3b): [com.datastax.oss.driver.api.core.connection.ConnectionInitException: [s5|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (java.nio.channels.NotYetConnectedException)] at com.datastax.oss.driver.api.core.AllNodesFailedException.copy(AllNodesFailedException.java:141) ~[java-driver-core-shaded-4.17.0.jar:?]
2. Using prpcServiceUtils from my system to the server
Error on logs:
ERROR [viceclient.requestmanager.RequestManager] - Request on system DefaultSystem failed java.util.concurrent.ExecutionException: com.pega.pegarules.serviceclient.exception.PRPCServiceException: java.net.SocketException: An established connection was aborted by the software in your host machine 3. Using prpcUtils from remote desktop Error on logs: ERROR - Exception: com.datastax.oss.driver.api.core.AllNodesFailedException: Could not reach any contact point, make sure you've provided valid addresses (showing first 1 nodes, use getAllErrors() for more): Node(endPoint=/ Proprietary information hidden:9042, hostId=null, hashCode=808cf3b): [com.datastax.oss.driver.api.core.connection.ConnectionInitException: [s5|control|connecting...] Protocol initialization request, step 1 (OPTIONS): failed to send request (java.nio.channels.NotYetConnectedException)] at com.datastax.oss.driver.api.core.AllNodesFailedException.copy(AllNodesFailedException.java:141) ~[java-driver-core-shaded-4.17.0.jar:?] Quick resolution for this would be appreciated.
Accepted Solution
Updated: 12 Jul 2024 10:43 EDT
Pegasystems Inc.
GB
@Vishali Ravichandran you will need to troubleshoot based on available resources online.
It seems like the issue might be related to network connectivity or timeout settings, given the errors you're encountering. For large imports, it's recommended to increase the timeout settings. If you're using a load balancer, ensure it's not timing out. Also, check your network connectivity to the server. If the issue persists, consider breaking down the backup into smaller chunks if possible and try importing them separately.
The Connection refused message in the exception indicates that there is no process on the host listening for connections. During the startup process, the last step for Cassandra is to start listening for clients on the CQL port when it is ready. Until the initialisation process has completed, Cassandra will not be ready to accept requests so your app needs to wait.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Command line import utility takes a very long time to load
Known Issues with Embedded Hazelcast Deployments
Third party externalized service FAQ
@Vishali Ravichandran you will need to troubleshoot based on available resources online.
It seems like the issue might be related to network connectivity or timeout settings, given the errors you're encountering. For large imports, it's recommended to increase the timeout settings. If you're using a load balancer, ensure it's not timing out. Also, check your network connectivity to the server. If the issue persists, consider breaking down the backup into smaller chunks if possible and try importing them separately.
The Connection refused message in the exception indicates that there is no process on the host listening for connections. During the startup process, the last step for Cassandra is to start listening for clients on the CQL port when it is ready. Until the initialisation process has completed, Cassandra will not be ready to accept requests so your app needs to wait.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Command line import utility takes a very long time to load
Known Issues with Embedded Hazelcast Deployments
Third party externalized service FAQ
Application performance issues related to nodes in clustered environments
Unable to import jar file - getting bad request
Unable to import larger product with Jenkins
Pegasystems Inc.
IN
@Vishali Ravichandran The exception com.datastax.oss.driver.api.core.AllNodesFailedException seems to be Cassandra (DDS) related. Can you check if all your DDS nodes are in Normal status? I am not sure if this exception is the reason causing import failures but maybe you can try fixing this and see if the issue goes away.
Areteans
IN
Hi @RaghuShankhawaram, DDS node status is 'Normal' and still we are facing this issue.
Pegasystems Inc.
IN
@Vishali Ravichandran is this for a client? I would recommend raise a support ticket so that the right team gets engaged to look in to this issue.
Areteans
IN
Hi @RaghuShankhawaram, It is not for client, it's for Areteans internal CDH practice work.
Accepted Solution
Updated: 12 Jul 2024 10:43 EDT
Pegasystems Inc.
GB
@Vishali Ravichandran you will need to troubleshoot based on available resources online.
It seems like the issue might be related to network connectivity or timeout settings, given the errors you're encountering. For large imports, it's recommended to increase the timeout settings. If you're using a load balancer, ensure it's not timing out. Also, check your network connectivity to the server. If the issue persists, consider breaking down the backup into smaller chunks if possible and try importing them separately.
The Connection refused message in the exception indicates that there is no process on the host listening for connections. During the startup process, the last step for Cassandra is to start listening for clients on the CQL port when it is ready. Until the initialisation process has completed, Cassandra will not be ready to accept requests so your app needs to wait.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Command line import utility takes a very long time to load
Known Issues with Embedded Hazelcast Deployments
Third party externalized service FAQ
@Vishali Ravichandran you will need to troubleshoot based on available resources online.
It seems like the issue might be related to network connectivity or timeout settings, given the errors you're encountering. For large imports, it's recommended to increase the timeout settings. If you're using a load balancer, ensure it's not timing out. Also, check your network connectivity to the server. If the issue persists, consider breaking down the backup into smaller chunks if possible and try importing them separately.
The Connection refused message in the exception indicates that there is no process on the host listening for connections. During the startup process, the last step for Cassandra is to start listening for clients on the CQL port when it is ready. Until the initialisation process has completed, Cassandra will not be ready to accept requests so your app needs to wait.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Command line import utility takes a very long time to load
Known Issues with Embedded Hazelcast Deployments
Third party externalized service FAQ
Application performance issues related to nodes in clustered environments
Unable to import jar file - getting bad request
Unable to import larger product with Jenkins