I'm using nifi in version 1.14.0 and facing a very weird situation.
I have a loadbalanced connection and after disconnection in the cluster (due to out of memory errors)
I'm getting the following error:
Error load balance server -
standartLoadBalanceProtocol attempted to receive flowfile from peer for connection with id xxx but no connection exists with that ID
Did anyone experience anything familiar? Thanks for the help!
I think it relates to this ticket https://issues.apache.org/jira/plugins/servlet/mobile#issue/NIFI-9695. Please upgrade to NiFi version 1.16 and see if this error happens again.
Related
Am trying to connect vertica from DBeaver, but am getting below connection error. Initially it was working fine, but suddenly its throwing connection error.
Error Message:
[Vertica][VJDBC](100071) GSS authentication failed due to problems establishing a TGT with JAAS using configuration verticajdbc; reason: Message stream modified (41).
Message stream modified (41)
Message stream modified (41)
I am not able to establish the connection now. Can anyone please help me on it.
The main issue I see with vertica users struggling to connect relate to the drivers used or where the host has changed. Have you updated vertica recently or has there been a change to the host name are just a couple of things you should check.
Sorry I cant be more specific its hard to troubleshoot when I dont have all the information.
Thanks
I am using tDBConnection(JDBC) component to connect with a snowflake.
After all the setup I am getting the below error
net.snowflake.client.jdbc.RestRequest execute
SEVERE: Stop retrying since elapsed time due to network issues has reached
timeout. Elapsed: 71,253(ms), timeout: 60,000(ms)
Exception in component tDBConnection_1 (sf_test)
java.lang.RuntimeException: JDBC driver encountered communication error. Message: Exception encountered for HTTP request: Certificate for <xxxxxxxxxx.ap-southeast-1.snowflakecomputing.com> doesn't match any of the subject alternative names: [*.ap-southeast-1.snowflakecomputing.com, *.global.snowflakecomputing.com, *.sg.ap-southeast-1.aws.snowflakecomputing.com].
at snowflake_poc.sf_test_0_1.sf_test.tDBConnection_1Process(sf_test.java:397)
at snowflake_poc.sf_test_0_1.sf_test.runJobInTOS(sf_test.java:700)
at snowflake_poc.sf_test_0_1.sf_test.main(sf_test.java:550)
I am using latest snowflake JDBC driver 3.12.2
Any leads would be really helpful
Thanks
I had the similar issue, in the Talend account box just give your account name alond which is "<xxxxxxxxxx.ap-southeast-1" don't postfix snowflakecomputing.com to your account name
I have running nifi instance 1.2.0.
I just tried to use "Wait\Notify" Processor with following reference
http://ijokarumawak.github.io/nifi/2017/02/02/nifi-notify-batch/#why-mergecontent-dont-suffice
Drag the template in canvas and i try to running it.
It shows following error in "Wait/Notify" processor.
Unable to communicate with cache when processing StandardFlowFileRecord[uuid=faab337f-034c-4137-a2f3-abb46f22b474,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1494485406343-1, container=default, section=1], offset=0, length=7005603],offset=5280310,name=input.csv,size=1054261] due to java.net.ConnectException: Connection refused: connect:
I don't know what this error says?
I am not apply any patches in 1.2.0 i just download binary file and tried it
Please stop me if anything if anything i'm missed?
And guide me to solve this.
You will need to create and start a DistributedMapCacheServer and DistributedMapCacheClient. The client needs to be configured with the port and host that the server is listening on.
Then the Wait and Notify processors use the DistributedMapCacheClient.
Since you were able to start the processors, you likely already have the client setup, but you don't have the server running.
When our application tries to connect Oracle database, this exception is thrown:
java.sql.SQLRecoverableException: Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Tue Oct 20 23:55:14 CEST 2015
But, from Weblogic console the connection test returns OK.
Weblogic version: 12.1.3.0.0
Any explanation is welcome. Thanks
The reason the test works is because that is creating a connection and running a test query. That is not what your code is doing when it is using the data source in an ejb. The code is going through the connection pool and that is what has been marked as bad. There is no solution provided by Oracle that I have found except to: restart the server and that will re-enable the connection pool.
I suspect you have "Test connections on reserve" set because that is when this usually arises. What Weblogic does is: before it returns a connection from the pool it will run a test query, if the test query fails it waits and runs it one more time. If the query fails again it marks the connection as unhealthy. If all the connections in the pool become unhealthy it will mark the pool as disabled and gives you the error message you see: 'Connection has been administratively disabled by console/admin command. Try later.'
In regards to the 'Try Later' part of the error message, as far as I can tell Oracle is wrong about trying again later. I have never seen it recover later.
I'd like to share this article that help me out to understand better my problem:
https://www.techpaste.com/2012/09/connection-administratively-destroyed-reconnect-oracle-weblogic-server/
The “java.sql.SQLException: Connection has been administratively destroyed.” is expected:
the DB was shutdown; even if it was restarted later, the JDBC connection are pointing to DB processes
that have been destroyed.
You need to restart your WebLogic Server to recreate new JDBC connections.
All the current transactions are lost, as the database was shutdown.
High availability of your RDBMS is required to minimize this issue.
Is there any other error before that one ?
Maybe in the log you can find that connection is been closed.
You can avoid this by selecting "Test on Connection Reserve" in the datasource.
We are migrate a old vb application from windows server 2000 to 2012, after the installation, the application give following errors when running:
<40006> Wrong protocol or connection state for the requested
transaction or request (Winsock-->[WSUtils]frmClient.gfSendData
LN1-->[WSUtils]Client.SendData LN1-->[IIMMC]Client.msSendData
LN0-->[IIMMC]Client.LockSchedule LN0-->[IIMMC]frmMain.cmdLock_Click
LN0)
We dont have any source code for this application. How could I explore to find the reason caused the error? Thanks.