I am working through the Digital Asset quickstart guide. I am receiving some warning messages when starting Sandbox:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/home/vantage/.da/packages/sandbox/6.0.0/lib/protobuf-java-3.5.1.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
So too when I start Navigator:
Version 1.1.1
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/home/vantage/.da/packages/navigator/1.1.1/navigator-1.1.1.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Should I be concerned that something is wrong somewhere?
this warning is because gRPC uses some operations, which are deprecated above Java 8. I assume you are using a fairly recent JRE, that's why you see this error.
They fixed the problem about a month ago and it takes time until the change propagates up the stack into higher level libraries, so it can be included in the Sandbox and Navigator.
See: https://github.com/protocolbuffers/protobuf/issues/3781
TL;DR: Ignore the warning for now, it's harmless and will be fixed. :)
Related
We have a package that will be triggered through MVC application by invoking store procedure which creates a execution request for the Package. MVC app is hosted on different server and DB is on different server. This error started occurring after 3 months of Windows Server 2019 migration.
Package executes successfully most of the time, but fails once or twice per day with the following errors. After re-executing the package immediately it succeeds. Error occurs in the below order.
Illegal operation attempted on a registry key that has been marked for deletion
Failed to acquire connection. Connection may not be configured correctly or you may not have the right permissions on this connection.
Upon capturing the "ISServexec.exe" process dump and analyzed through DebugDiag, we came to know the below details.
System.Runtime.InteropServices.COMException: Retrieving the COM class factory for component with CLSID {2206CDB2-19C1-11D1-89E0-00C04FD7A829} failed due to the following error: 800703fa Illegal operation attempted on a registry key that has been marked for deletion. (Exception from HRESULT: 0x800703FA).
System.InvalidOperationException: The .Net Framework Data Providers require Microsoft Data Access Components(MDAC). Please install Microsoft Data Access Components(MDAC) version 2.6 or later.
System.Runtime.InteropServices.COMException: Illegal operation attempted on a registry key that has been marked for deletion.
Microsoft.SqlServer.Dts.Runtime.DtsGenericException: Illegal operation attempted on a registry key that has been marked for deletion.
Note:
Package doesn't have any excel reading operations. Just source table to target table load (both same database).
We have validated the MDAC version in the DB server as 6.3.
App Server: Windows 2019 with .Net framework 4.8 installed.
DB Server: Windows 2019, SQL Server 2019, SSIS v15, .Net framework 4.8.
Package executed using domain service account.
We have triggered the Package through SQL job and Package did not fail at all. Almost 200 executions tested. This failure is random and only fails when store procedure invoked through MVC application.
We have used ProcMon to collect the "ISServexec.exe" logs and only thing we noticed is hive unloaded and no errors.
SQL Profiler didnt even capture the error.
Package is not failing at the same step when this error occurs.
Package logging is configured to write errors in event log, but in event log only "package is failed" information is captured.
Package configured to use Oledb connection type. SQL Native client and MSOLEDB providers are used and error occurs in both the providers.
Package has been upgraded to SQL 2019. Hence we created a new Package in Visual Studio 2019 from scratch and this also fails with same error.
No errors captured in SQL Server extended events.
My Questions:
What are possible ways to validate the service account holds necessary permissions when the above error happens. Is this required ?
Is there any tools that I can use to debug and find the cause of the error or additional information ?
Is this oledb driver issue ?
How to capture any logs at windows server level when package execution happens.
Sorry for the detailed explanation. Any suggestions would be greatly appreciated.
I have this error
[ERROR]: Exception on / [POST]
as the last entry in the Log tab of the Cloud Function after testing the function failed with:
Error: function terminated. Recommended action: inspect logs for termination reason. Additional troubleshooting documentation can be found at https://cloud.google.com/functions/docs/troubleshooting#logging Details:
500 Internal Server Error: The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
What to do?
Just sharing this since it surprised me. The log just needs some dozen seconds to really finish the entries. In my case, I went to the Log directly after the failed test, and then jumped to Edit of the CF right after seeing that log entry error at the bottom, thinking it would be all to gain from the log.
Then I changed my mind, went back to the Log tab and saw the real error entry only coming after that [ERROR]: Exception on / [POST].
Not important since you will have another error anyway: I had used create_engine() function without the needed module prefix sqlalchemy.create_engine(). (Side-note: Querying your own db does not seem to work anyway in a CF unless you use a VPC connector, do not think from this example that it might be possible).
I am facing an issue where I am getting the following error:
CONTAINER:atg.repositoryException; SOURCE:java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource'ATGProductionDS_atg11':XAResource.XAER_RMFAIL: Resource manager is unavailable.
How do I solve this?
Do ATG connection threads get closed implicitly or do we have to close it explicitly?
Do ATG connection threads get closed after updateItem() and addItem() methods implicitly?
How can we close an ATG session thread explicitly?
There are potentially a number of causes for this issue. There is a support document in Oracle support portal which helps understand where the issue is (You will have to register for Oracle Support access)
Slow running query which is never timing out due to a misconfiguration
The timeouts for your datasource(s) are not setup correctly between WebLogic and the ATG application
I need to install keyring plugin in mysql running over google cloud and I can not because the user doesn't have SUPER privileges. Have anyone had the same situation?
mysql < sql_dupm.sql
and the error is :
Error : ERROR 3185 (HY000) at line 98: Can't find master key from keyring, please check keyring plugin is loaded.
When I tried to install plugin
mysql> INSTALL PLUGIN keyring_file SONAME 'keyring_file.so';
ERROR 1227 (42000): Access denied; you need (at least one of) the SUPER privilege(s) for this operation
It looks like you are trying to use a feature that is not supported.
That may sound like I'm stating the obvious, since it isn't working, but SUPER is definitely not available so anything relying on it typically would not be, either. This is not surprising for a managed service.
Additonally, because the keyring_file plugin uses a local file on the server, and you don't have access to the actual server's filesystem, it stands to reason that it is not supported.
I don't find a mention of it in the documentation.
I agree with Michael, Cloud SQL doesn't support SUPER privilege such as the "Unsupported features" section says in the link that he shared. Here is another link that I found that confirms this behavior.
Additionally, I found out that MySQL keyring is a "service that enables internal server components and plugins to securely store sensitive information for later retrieval.". With this in mind, I figured out in Cloud SQL FAQ some answers that can address your concern, basically your data is encrypted. For a detailed information, look for the questions:
Is my data encrypted?
How is encryption managed for data at rest?
How is encryption managed for data in transit?
Hope the information above help you.
I am running Visual Studio 2010, and attempting to update my Entity Framework project using the Update Wizard. When I attempt to add a single table from the MySql database, the add tab will show the table that I am attempting to add, however when I click finish, I get the following error message.
Unable to generate the model because of the following exception: 'An error occurred while executing the command definition. See the inner exception for details.
Fatal error encountered during command execution.
Fatal error encountered attempting to read the resultset.
Reading from the stream has failed.
Attempted to read past the end of the stream.
I get the same error message if attempt to create the Entity Framework from scratch. In addition, Server Explorer shows that the connection is successful when I test it.
I have also contacted Host Gator who is hosting the database and they where not able to see any issues on their side.
The problem ended up being that our shared server, was not able to handle the Update Request from the Entity Connector Framework and was timing out. Once we moved our database over to a different server we no longer had an issue.