Diagnosing Worklight 6 SQL Adapter issue, JPA tracing - worklight-adapters

Worklight Studio 6, SQL adapter attempting connection to DB2 database.
Standard pattern for procedure
return WL.Server.invokeSQLStatement({
preparedStatement : listUnassignedWorkOrders,
parameters : []
});
When I invoke my procedure I see this error
[ERROR ] FWLSE0035E: Invocation of procedure 'SqlStatement' failed.
[project Infrabel01] Type 'Function' currently does not support
marshalling to JSON.
And the logs show
[err] 0 WorklightPU WARN [Scheduled Executor-thread-1]
openjpa.Runtime - An error occurred while registering a
ClassTransformer with PersistenceUnitInfo: name 'WorklightPU', root
URL
[file:/C:/djna-nobackup/Workspaces/WL6.0/01/WorklightServerConfig/shared/resources/worklight-jee-library-6.0.0.jar].
The error has been consumed. To see it, set your openjpa.Runtime log
level to TRACE. Load-time class transformation will not be available.
How to diagnose? How would I set the trace level in worklight?
JPA docs say:
property name="openjpa.Log" value="DefaultLevel=WARN, Runtime=INFO,
Tool=INFO, SQL=TRACE"
But where to put that in worklight?

The WorklightPU WARN in the log is not relevant and has been removed in newer releases of Worklight.
For your actual issue, see the following developerWorks threads with the same issue that was resolved.
Type 'Function' currently does not support marshalling to JSON.
developerWorks thread #1
developerWorks thread #2

Related

Visual Studio 2017 Error initializing VroomJs.JsEngine

My project uses Reactjs, and I use Visual Studio 2017. Recently I did an software update on VS 2017, but no code/config changes.
However, when I start my project locally in debug mode, I encountered below error:
No JavaScript engines were registered, falling back to a default config! It is recommended that you configure JavaScriptEngineSwitcher in your app. See https://github.com/Taritsyn/JavaScriptEngineSwitcher/wiki/Registration-of-JS-engines for more information.
Error initialising JavaScriptEngineSwitcher.V8.V8JsEngineFactory: JavaScriptEngineSwitcher.Core.JsEngineLoadException: During loading of V8JsEngine error has occurred.
See more details:
Cannot load V8 interface assembly. Load failure information for v8-ia32.dll:
C:\Users\user1\AppData\Local\Temp\Temporary ASP.NET Files\vs\77655ce5\ca0bb6d0\assembly\dl3\300b733a\003cadac_c3f4d201\v8-ia32.dll: The specified module could not be found
C:\Code\project1\branches\apps\src\DotNet\COMP.project1.Web\v8-ia32.dll: The specified module could not be found
C:\Code\project1\branches\apps\src\DotNet\COMP.project1.Web\bin\v8-ia32.dll: The specified module could not be found ---> System.TypeLoadException: Cannot load V8 interface assembly. Load failure information for v8-ia32.dll:
C:\Users\user1\AppData\Local\Temp\Temporary ASP.NET Files\vs\77655ce5\ca0bb6d0\assembly\dl3\300b733a\003cadac_c3f4d201\v8-ia32.dll: The specified module could not be found
C:\Code\project1\branches\apps\src\DotNet\COMP.project1.Web\v8-ia32.dll: The specified module could not be found
C:\Code\project1\branches\apps\src\DotNet\COMP.project1.Web\bin\v8-ia32.dll: The specified module could not be found
at Microsoft.ClearScript.V8.V8Proxy.LoadNativeLibrary()
at Microsoft.ClearScript.V8.V8Proxy.LoadAssembly()
at Microsoft.ClearScript.V8.V8Proxy.GetAssembly()
at Microsoft.ClearScript.V8.V8Proxy.GetImplType(Type type)
at Microsoft.ClearScript.V8.V8Proxy.CreateImpl[T](Object[] args)
at Microsoft.ClearScript.V8.V8IsolateProxy.Create(String name, V8RuntimeConstraints constraints, Boolean enableDebugging, Int32 debugPort)
at Microsoft.ClearScript.V8.V8Runtime..ctor(String name, V8RuntimeConstraints constraints, V8RuntimeFlags flags, Int32 debugPort)
at Microsoft.ClearScript.V8.V8ScriptEngine..ctor(V8Runtime runtime, String name, V8RuntimeConstraints constraints, V8ScriptEngineFlags flags, Int32 debugPort)
at JavaScriptEngineSwitcher.V8.V8JsEngine..ctor(V8Settings settings)
--- End of inner exception stack trace ---
at JavaScriptEngineSwitcher.V8.V8JsEngine..ctor(V8Settings settings)
at JavaScriptEngineSwitcher.V8.V8JsEngineFactory.CreateEngine()
at React.JavaScriptEngineFactory.GetFactory(JsEngineSwitcher jsEngineSwitcher, Boolean allowMsie)
Error initialising React.VroomJsEngine+Factory: JavaScriptEngineSwitcher.Core.JsEngineLoadException: During loading of VroomJs JavaScript engine error has occurred.
See more details:
The type initializer for 'VroomJs.JsEngine' threw an exception. ---> System.TypeInitializationException: The type initializer for 'VroomJs.JsEngine' threw an exception. ---> System.DllNotFoundException: Unable to load DLL 'VroomJsNative': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at VroomJs.JsEngine.js_set_object_marshal_type(JsObjectMarshalType objectMarshalType)
at VroomJs.JsEngine..cctor()
--- End of inner exception stack trace ---
at VroomJs.JsEngine..ctor(Int32 maxYoungSpace, Int32 maxOldSpace)
at React.VroomJsEngine.<>c.<.cctor>b__23_0()
at System.Lazy`1.CreateValue()
at System.Lazy`1.LazyInitValue()
at System.Lazy`1.get_Value()
at React.VroomJsEngine.get_Engine()
at React.VroomJsEngine..ctor()
--- End of inner exception stack trace ---
at React.VroomJsEngine..ctor()
at React.VroomJsEngine.Factory.CreateEngine()
at React.JavaScriptEngineFactory.GetFactory(JsEngineSwitcher jsEngineSwitcher, Boolean allowMsie)
This error does not block me from running and testing the code.
Like I said, all I did recently was to update the VS 2017 software...I tried to do a wild search in the project for 'v8-ia32' but nothing found.
To fix these errors I did the following:
Make sure you install the JavaScriptEngineSwitcher.V8, JavaScriptEngineSwitcher.V8.Native.win-x86 and JavaScriptEngineSwitcher.V8.Native.win-x64.
(I didn't install JavaScriptEngineSwitcher.V8.Native.win-x86)
According to https://reactjs.net/getting-started/aspnet.html
edit the ReactConfig.cs, basically, I just added this
JsEngineSwitcher.Current.DefaultEngineName = V8JsEngine.EngineName;
JsEngineSwitcher.Current.EngineFactories.AddV8();
Rebuild the project.

Internal server error in loadrunner script while replay

I've recorded a workflow using proxy recorder for a mobile application which is using API calls in VUGEN(loadrunner 12.55). I am getting internal server error 500 during update (POST) function. Following is the code snippet of script generated by Loadrunner
web_submit_data("signin",
"Action=http://beautymarksapp.com/api/user/signin",
"Method=POST",
"RecContentType=application/json",
"Referer=",
"Snapshot=t1.inf",
"Mode=HTML",
"EncodeAtSign=YES",
ITEMDATA,
"Name=email", "Value=user#domain.com", ENDITEM,
"Name=password", "Value=BMARKS", ENDITEM,
"Name=timezone", "Value=18000", ENDITEM,
LAST);
web_custom_request("update",
"URL=http://beautymarksapp.com/api/user/update",
"Method=PUT",
"Resource=0",
"RecContentType=application/json",
"Referer=",
"Snapshot=t2.inf",
"Mode=HTML",
"Body=device_token=c7ff93995d1dea60fea773819b582235b6367c0c7275238a65c2035c2d96fde6&device_type=ios",
LAST);
Any help in this regard will be highly appreciated.
The most common answer for 500 are:
Unhandled Dynamic Item
No checking for expected results
No exception handling/branching when unexpected results appear

Error in db2hpu procedure call

Is there a solution to this problem in db2hpu call:
SQL0443N Routine "DB2INST1.DB2HPU" (specific name "SQL160823160100917") has
returned an error SQLSTATE with diagnostic text "Cannot Connect: rc =
0x25a7dd". SQLSTATE=38107
Thanks a lot
The "Cannot Connect: rc = ..." error is coming from HPU stored procedure, not DB2 itself.
It may be raised if the db2hpudm deamon is not able to start.
Verify that the HPU was correctly installed and that you have no warnings or error in the installation trace files under :
[INSTALLDIR]/install/trace_error_install
[INSTALLDIR]/install/trace_warning_install

Connecting to QB 13 with QBSDK 12 gives qb_utils.js error popup

QB 13.0 Enterprise introduced an issue in our environment that did not exist in QB 12.0.
Using QBSDK 12.0, qbXML version 4.0, Windows Server 2008 R2 and a solution developed in python 2.7.3. QB File Doctor does not report any problems and all XMLs are successfully validated by the QB XML Validator.
I had to go thru this post to resolve the LGB file corruption issue after the upgrade:Automatic Login Failure
I have created a test .Net program to replicate the problem, which occurs at random points between BeginSession and EndSession calls:
using QBXMLRP2Lib;
RequestProcessor2 proc = new RequestProcessor2();
proc.OpenConnection2("Test QB", "Test QB", QBXMLRPConnectionType.localQBD);
string ticket = proc.BeginSession("the path to the QB file", QBFileMode.qbFileOpenMultiUser);
proc.EndSession(ticket);
proc.CloseConnection();
A "Script Error" dialog box pops up with:
Line: 46
Char: 8
Error: Unspecified error.
Code: 0
URL: https://qbinproduct.intuit.com/ipd/common/js/qb_utils.js
And the standard two options whether to continue to run the script or not.
Regardless of what is chosen, QB crashes with:
Problem signature:
Problem Event Name: APPCRASH
Application Name: qbw32.exe
Application Version: 23.0.4005.2305
Application Timestamp: 50d6cc51
Fault Module Name: StackHash_5b31
Fault Module Version: 6.1.7601.17725
Fault Module Timestamp: 4ec49b8f
Exception Code: c0000374
Exception Offset: 000ce6c3
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Additional Information 1: 5b31
Additional Information 2: 5b3188f7410a3a5d99b8b3c79d62fc31
Additional Information 3: 38e7
Additional Information 4: 38e72e11a56a600df179c0b7bdb3159c
I'll appreciate any solutions or suggestions.

saxon: problem reusing XsltTransformer object

Using Saxon-B, I'm trying to follow the javadoc and serially reuse an XsltTransformer object.
I'm thwarted by:
Error
XTDE1490: Cannot write more than one result document to the same URI, or write to a URI
that has been read: file:/Users/benson/x/btweb/web_2_0/sites/us/errors/404/404.xml.prepared
2011-03-22 11:06:23,830 [main] ERROR btweb.compiler.CompileSite - Site compilation terminated with error.
btweb.compiler.CompilerException: Error running transform Cannot write more than one result document to the same URI, or write to a URI that has been read: file:/Users/benson/x/btweb/web_2_0/sites/us/errors/404/404.xml.prepared
It's probably Saxon-B bug. You can find more information here. According to this site "Fixed in 8.9.0.4".

Resources