When trying the LDAP sample project provided by Worklight, I get the following error:
[ERROR ] FWLSE0020E: Ajax request exception: Adapter 'DummyAdapter'
does not exist [project module_23_2_LDAPLoginModule] [ERROR ]
FWLSE0117E: Error code: 1, error description: INTERNAL_ERROR, error
message: FWLSE0069E: An internal error occurred during gadget request
[project module_23_2_LDAPLoginModule]Adapter 'DummyAdapter' does not
exist, User Identity {SubscribeServlet=null, LDAPRealm=null,
wl_authenticityRealm=null, wl_remoteDisableRealm=null,
wl_antiXSRFRealm=(name:rtm5uf72muh56gak3ms4gvvt42,
loginModule:WLAntiXSRFLoginModule),
wl_deviceAutoProvisioningRealm=null,
wl_deviceNoProvisioningRealm=null,
myserver=(name:776c1909-3ae4-45b5-a029-f0372b507a7d,
loginModule:WeakDummy),
wl_anonymousUserRealm=(name:776c1909-3ae4-45b5-a029-f0372b507a7d,
loginModule:WeakDummy)}. [project module_23_2_LDAPLoginModule]
com.worklight.common.log.filters.ErrorFilter
In order to make it work, what values do I need to change. I want to use my IBM LDAP server.
Thanks..Johnson
At least by reading the error message, it is pretty clear.
Did you make sure to also deploy the adapter and not just the application?
In your Worklight project, find the adapters folder. Open it. Then, right-click on the adapter folder within and select Run As > Deploy Worklight adapter.
Try the application again and see if it works, or if there are other errors displayed.
I suggest that instead of jumping right into what you want to do in your app, first learn the basics. Review the IBM Worklight Getting Started training modules, from the top.
Related
We are using adapter-based authenticators. WL.Server.setActiveUser was called on the adapter.
I user WL.Logger.info to print out the parameters which I send to setActiveUser. They are correct.
In WL console, DeviceId got updated ,but we can not saw the userid in the device table.
enter image description here
we are using MFP 7.1 version.
We got below error in the log file. not sure it is related to the issue.
[9/5/16 23:09:48:567 EDT] 000000f4 GadgetAPIServ E com.worklight.gadgets.serving.GadgetAPIServlet createAjaxRequestExceptionJSON FWLSE0020E: Ajax request exception: Optimistic locking errors were detected when flushing to the data store. The following objects may have been concurrently modified in another transaction: [com.ibm.pushworks.server.entities.PushSubscription-com.ibm.pushworks.server.entities.PushSubscription-2] [project ]
[9/5/16 23:09:48:579 EDT] 000000f4 GadgetAPIServ E createAjaxRequestExceptionJSON FWLSE0117E: Error code: 1, error description: INTERNAL_ERROR, error message: FWLSE0069E: An internal error occurred during gadget request [project ]Optimistic locking errors were detected when flushing to the data store. The following objects may have been concurrently modified in another transaction: [com.ibm.pushworks.server.entities.PushSubscription-com.ibm.pushworks.server.entities.PushSubscription-2], User Identity {wl_directUpdateRealm=(name:null, loginModule:WLDirectUpdateNullLoginModule), SubscribeServlet=null, wl_authenticityRealm=null, ServicesRealm=(name:xxx#cn.ibm.com, loginModule:StrongDummy), wl_remoteDisableRealm=(name:null, loginModule:WLRemoteDisableNullLoginModule), SampleAppRealm=(name:xxx#cn.ibm.com, loginModule:StrongDummy), wl_antiXSRFRealm=(name:qmd8e821mcil59j4tedagchnvi, loginModule:WLAntiXSRFLoginModule), wl_deviceAutoProvisioningRealm=null, wl_deviceNoProvisioningRealm=(name:D07571B0-2685-4F6F-9C42-37B616F52190, loginModule:WLDeviceNoProvisioningLoginModule), myserver=(name:ea57e780-ce09-4bbd-aee5-5a1701388b72, loginModule:WeakDummy), wl_anonymousUserRealm=(name:ea57e780-ce09-4bbd-aee5-5a1701388b72, loginModule:WeakDummy)}. [project ]
It seems the security test defined in Authentication config file is not mentioned in Application Descriptor file . Please cross check security test in AuthenticatonConfig.xml and applicationDescription.xml
please follow below link.
https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/6.3/authentication-security/adapter-based-authentication/
I'm receiving the following message on server log in IBM Mobile First 6.3 every time an Adapter is getting called:
Stacktrace
[ERROR ] Error sending bulk request: java.lang.RuntimeException:
failure in bulk execution: [2]: index [worklight], type [devices], id
[b2deefe7-0d15-4ed4-b199-7e42440fc372], message
[VersionConflictEngineException[[worklight][1]
[devices][b2deefe7-0d15-4ed4-b199-7e42440fc372]: version conflict,
current [58], provided [57]]] at
com.ibm.elasticsearch.servlet.DataReceiver.processData(DataReceiver.java:132)
at
com.ibm.elasticsearch.servlet.DataReceiver.processDataLegacy(DataReceiver.java:85)
at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source) ...
The adapter is executed correctly and the response is returned to the app.
Any idea why this error is happening?
Help will be appreciated.
Thanks.
This is an internal error in analytics. The error itself is actually harmless, however the analytics platform should be catching it... A defect will be logged for the message. In the meantime, if you're not using analytics, you can disable it by removing the WAR files from the Liberty server.
If you are using analytics, then I would recommend clearing out the analytics data folder and restarting the IMF platform (this would remove any data you have stored in analytics). This is assuming that you are running in development mode. The analytics data folder can be in the same directory as the server.xml file for your Liberty server.
We have uploaded the .war file , wlapp and adapter. How can we resolve this issue?
The error is the url of .war file.
Error 500: javax.servlet.ServletException: Worklight Console
initialization failed.Logged Exception:
com.worklight.server.database.api.WorklightDataSourceException:
FWLSE0194E: MobileFirst Server cannot be started because of failure
while getting a connection from data-source bound to resource
reference: jdbc/WorklightDS. Make sure the database is up, the
credentials are correct and the driver is available for the server
I have stopped the middleware server and start it again where my .war project is located. The issue was resolve.
I have created an application using IBM worklight and i am using customAuthenticator for login process
I am getting following validation error while deploying application
Security test DummyAdapter-securityTest must include user and device
realms for AuthDemo:iphone:1.0:api. [project
module_23_1_CustomLoginModule]
You need to re-read the entire Getting Started section about Authentication and Security. There is more reading material here and here.
From the error I am thinking you have added a securityTest="DummyAdapter-securityTest" attribute to your iphone element in application-descriptor.xml.
As noted by the name of the securityTest, it is not meant for the application but for the adapter. This securityTest is already defined for the adapter procedure in the adapter XML file. Remove the securityTest you've added and it will work.
The sample you are trying to run (module_23_1_CustomLoginModule) is ready-made; no need for editing. You need only to build & deploy and run it.
I have migrated an application from WL 8 to WL 10 and set up my managed servers. They indicate that they are running, but when I try to access the site it throws a 404. This is my first time deploying anything on 10 so I could be missing something. Any ideas? Please let me know what additional information could be helpful. edit: I had this working, added a db connection and now it fails.
Here is my error:
weblogic.management.DeploymentException: Exception occured while downloading files
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:670)
at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:713)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from admin server for deployment request "0". Underlying error is: "[DeploymentService:290065]Deployment service servlet encountered an Exception while handling the deployment datatransfer message for request id "0" from server "TEST01". Exception is: "weblogic.management.configuration.JDBCSystemResourceMBeanImpl"."
at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:86)
at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:670)
at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:713)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:100)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
You got a weblogic.management.DeploymentException and this means that something went wrong in some server even if everything seems OK from the console.
Underlying error is from weblogic.management.configuration.JDBCSystemResourceMBeanImpl so I would review datasource config is appropiate for every target in your environment. Also check that datasource targets are the same as web application targets and JDBC drivers are available at managed servers classpath as well.
Try to log to the WebLogic Admin console and see what is the status of your application.
You can use the 'Testing' tab of your deployment to see the URL that the application has been deployed to. This will assist you in the troubleshooting process.
If you don't see anything here to test there are a few possible reasons, including the following:
The application failed to deploy and/or is not 'Active'
You are using a cluster and no managed servers are running
You have managed servers running but they are not in a 'RUNNING' state