0

将应用程序上传到 Worklight Application Center 时，message.log 中出现以下错误：

"com.ibm.puremeap.resources.desktop.UploadService W JSON error when trying to upload file IBMApplicationCenter.apk"

此外，在 trace.log 中，整个堆栈跟踪如下：

[4/10/13 20:23:23:350 CST] 00000148 id=         com.ibm.puremeap.resources.desktop.UploadService             W JSON error when trying to upload file IBMApplicationCenter.apk
[4/10/13 20:23:23:351 CST] 00000148 id=         UploadService                                                2 response THROW
org.apache.wink.json4j.JSONException: The value for key: [pkg] was null.  Object required.
    at org.apache.wink.json4j.JSONObject.getString(JSONObject.java:1098)
    at com.ibm.puremeap.resources.desktop.UploadService.fileUploaded(UploadService.java:198)
    at com.ibm.puremeap.resources.desktop.UploadService.__fileUploadedJSON__(UploadService.java:102)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:616)
    at org.apache.wink.server.internal.handlers.InvokeMethodHandler.handleRequest(InvokeMethodHandler.java:63)
    at org.apache.wink.server.handlers.AbstractHandler.handleRequest(AbstractHandler.java:33)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:67)
    at org.apache.wink.server.internal.handlers.CreateInvocationParametersHandler.handleRequest(CreateInvocationParametersHandler.java:54)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:67)
    at org.apache.wink.server.handlers.AbstractHandler.handleRequest(AbstractHandler.java:34)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:67)
    at org.apache.wink.server.internal.handlers.FindResourceMethodHandler.handleSubResourceMethod(FindResourceMethodHandler.java:183)
    at org.apache.wink.server.internal.handlers.FindResourceMethodHandler.handleRequest(FindResourceMethodHandler.java:110)
    at org.apache.wink.server.internal.handlers.FindResourceMethodHandler.handleSubResourceLocator(FindResourceMethodHandler.java:230)
    at org.apache.wink.server.internal.handlers.FindResourceMethodHandler.handleRequest(FindResourceMethodHandler.java:115)
    at org.apache.wink.server.internal.handlers.FindResourceMethodHandler.handleSubResourceLocator(FindResourceMethodHandler.java:230)
    at org.apache.wink.server.internal.handlers.FindResourceMethodHandler.handleRequest(FindResourceMethodHandler.java:115)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:67)
    at org.apache.wink.server.internal.handlers.FindRootResourceHandler.handleRequest(FindRootResourceHandler.java:95)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:67)
    at org.apache.wink.server.internal.handlers.HeadMethodHandler.handleRequest(HeadMethodHandler.java:53)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:67)
    at org.apache.wink.server.internal.handlers.OptionsMethodHandler.handleRequest(OptionsMethodHandler.java:46)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:67)
    at org.apache.wink.server.internal.handlers.SearchResultHandler.handleRequest(SearchResultHandler.java:33)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:67)
    at org.apache.wink.server.internal.log.ResourceInvocation.handleRequest(ResourceInvocation.java:92)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:67)
    at org.apache.wink.server.internal.log.Requests.handleRequest(Requests.java:76)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:26)
    at org.apache.wink.server.handlers.RequestHandlersChain.handle(RequestHandlersChain.java:22)
    at org.apache.wink.server.handlers.AbstractHandlersChain.doChain(AbstractHandlersChain.java:67)
    at org.apache.wink.server.handlers.AbstractHandlersChain.run(AbstractHandlersChain.java:52)
    at org.apache.wink.server.internal.RequestProcessor.handleRequestWithoutFaultBarrier(RequestProcessor.java:207)
    at org.apache.wink.server.internal.RequestProcessor.handleRequest(RequestProcessor.java:154)
    at org.apache.wink.server.internal.servlet.RestServlet.service(RestServlet.java:133)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1234)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:757)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:440)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1041)
    at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:81)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:930)
    at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVirtualHost.java:274)
    at com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$TaskWrapper.run(HttpDispatcherLink.java:529)
    at com.ibm.ws.threading.internal.Worker.executeWork(Worker.java:398)
    at com.ibm.ws.threading.internal.Worker.run(Worker.java:380)
    at java.lang.Thread.run(Thread.java:636)

[4/10/13 20:23:23:352 CST] 00000148 id=         UploadService                                                2 response Result: {0} 
                                                                                                               [{"message":"The value for key: [pkg] was null.  Object required.","status":200,"exception":"org.apache.wink.json4j.JSONException","acl_upload_denied":"IBMApplicationCenter.apk"}]

谁能告诉我如何解决这个问题？顺便说一句，我成功尝试在 worklight 控制台中部署 wlapp 和适配器。

我的环境是：

- RHEL v6.x 64 bit
- Worklight v5.0.6
- DB2 10.x

我做了进一步的调查：

  1. 在 Win7 64 位上使用 Worklight Server 并连接到同一个数据库实例。每件事都很好。此外，我浏览了在 Linux 环境上运行的应用程序中心。在Win7上appcenter上传的应用程序显示没有问题。

  2. 从两个环境（RHEL 6 和 Win7）检查 trace.log 中的 pkg 值。结果是不同的。

在 Win7 的 trace.log 上：

[2013/4/11   10:48:18:944 TST] 00000040 id=         ApplicationService                                           > __create__ ENTRY {0} {1} {2} 
                                                                                                               uri=http://[hostname_win7]:9080/applicationcenter/service/desktop/application/
                                                                                                               securityContext=org.apache.wink.server.internal.contexts.SecurityContextImpl_1700851040
                                                                                                               {"os":"Android","pkg":"com.ibm.appcenter","version":"1","versionName":"1.0","label":"IBM App Center","author":"appcenteradmin","author_display":"appcenteradmin","mandatory":"N","description":"","remote_url":"","is_installer":"Y","is_active":"Y","is_ready_prod":"Y","files":[{"type":"apk","cid":"1","size":1599708,"filename":"IBMApplicationCenter.apk"}]}

在 RHEL 6 的 trace.log 上：

[4/11/13 11:44:48:694 CST] 00000308 id=         ApplicationService                                           > __create__ ENTRY {0} {1} {2} 
                                                                                                               uri=http://[hostname_RHEL]:10080/applicationcenter/service/desktop/application
                                                                                                               securityContext=org.apache.wink.server.internal.contexts.SecurityContextImpl_1489398078
                                                                                                               {"files":[{"filename":"IBMApplicationCenter.apk","type":"apk","cid":null,"size":null}],"os":"Android","description":"This is application null.","mandatory":"N","pkg":null,"label":null,"version":null}
4

1 回答 1

1

当您尝试将 APK 上传到 Worklight Application Center 时发生错误。在此步骤中，会分析 APK。RHEL 跟踪日志表明不仅缺少 pkg (null)，而且 APK 大小为 null。这可能表明 APK 非常错误。

第一步是验证APK是否正确。为此，只需解压缩它（APK 是一个 zip 文件），并验证它是否包含 AndroidManifest.xml。该文件是二进制文件，pkg 值将来自那里。如果丢失，这是致命的。

接下来，验证 APK 是否可以被 aapt 分析（位于您的 Android SDK 的平台工具中）：

aapt dump badging somefile.apk

您似乎尝试上传 IBMApplicationCenter.apk，因此在您的特定情况下，它是：

aapt dump badging IBMApplicationCenter.apk

这会输出几行，通常以一行开头，例如

package: name='com.ibm.appcenter' versionCode='1' versionName='1.0'

这就是 pkg 值的来源。如果这不起作用，则 Worklight Application Center 无法找到 pkg，或者 Android Manifest 无效。

在 APK 上传机制期间，会发生以下情况：

  • 如果在服务器配置文件（Liberty 的 bootstrap.properties、Tomcat 的 catalina.properties 或 WAS 的 Java VM 属性）中设置了属性 android.aapt 或 android.aapt.dir，则在该位置搜索 aapt，并且如前所述执行“aapt dump badging”，并由 Worklight Application Center 分析输出。这可以解释为什么您会在 Win7 和 RHEL 上看到不同的行为，因为那里有不同的 aapt 可执行文件。
  • 如果未设置任何属性 android.aapt 或 android.aapt.dir，则 Worklight Application Center 不使用 aapt，而是尝试解码 APK 本身。因此，您可以尝试取消设置服务器中的 android.aapt 属性并重新启动服务器，以检查这是否解决了问题。
于 2013-04-11T12:37:31.420 回答