2015-02-11 109 views
0

我安装了IBM工作灯服务器6.2 20150129在WAS 8.5.5.2 ND在Windows 2008数据中心虚拟机4GB内存部署到IBM工作灯6.2服务器

最小堆:512MB,最大堆:1536MB

我正在部署一个大约140mb的* -all.wlapp,并发生错误。
部署应用程序< 20mb很好。

server1_exception.log

com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS

server1_(很长的无意义的文字).TXT

[2/11/15 7:10:54:960 PST]  FFDC Exception:javax.naming.ConfigurationException SourceId:com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS ProbeId:537 Reporter:[email protected] 
javax.naming.ConfigurationException: A JNDI operation on a "java:" name cannot be completed because the server runtime is not able to associate the operation's thread with any J2EE application component. This condition can occur when the JNDI client using the "java:" name is not executed on the thread of a server application request. Make sure that a J2EE application does not execute JNDI operations on "java:" names within static code blocks or in threads created by that J2EE application. Such code does not necessarily run on the thread of a server application request and therefore is not supported by JNDI operations on "java:" names. [Root exception is javax.naming.NameNotFoundException: Name "comp/env/ibm.worklight.admin.lockTimeoutInMillis" not found in context "java:".] 
    at com.ibm.ws.naming.java.javaURLContextImpl.throwExceptionIfDefaultJavaNS(javaURLContextImpl.java:522) 
    at com.ibm.ws.naming.java.javaURLContextImpl.throwConfigurationExceptionWithDefaultJavaNS(javaURLContextImpl.java:552) 
    at com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLContextImpl.java:481) 
    at com.ibm.ws.naming.java.javaURLContextRoot.lookupExt(javaURLContextRoot.java:485) 
    at com.ibm.ws.naming.java.javaURLContextRoot.lookup(javaURLContextRoot.java:370) 
    at org.apache.aries.jndi.DelegateContext.lookup(DelegateContext.java:161) 
    at javax.naming.InitialContext.lookup(InitialContext.java:436) 
    at com.ibm.worklight.admin.common.util.ContextPropertyUtil.getContextProperty(ContextPropertyUtil.java:184) 
    at com.ibm.worklight.admin.common.util.ContextPropertyUtil.getContextProperty(ContextPropertyUtil.java:164) 
    at com.ibm.worklight.admin.common.util.ContextPropertyUtil.getContextProperty(ContextPropertyUtil.java:65) 
    at com.ibm.worklight.admin.common.util.ContextPropertyUtil.getContextPropertyAsLong(ContextPropertyUtil.java:300) 
    at com.ibm.worklight.admin.actions.BaseCommitable.getLockTimeOutInMillis(BaseCommitable.java:415) 
    at com.ibm.worklight.admin.actions.CleanUnfinishedTransaction.cleanUnfinishedTransaction(CleanUnfinishedTransaction.java:94) 
    at com.ibm.worklight.admin.actions.BaseTransaction.internalRun(BaseTransaction.java:284) 
    at com.ibm.worklight.admin.actions.BaseTransaction$1.run(BaseTransaction.java:210) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906) 
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929) 
    at java.lang.Thread.run(Thread.java:796) 
Caused by: javax.naming.NameNotFoundException: Name "comp/env/ibm.worklight.admin.lockTimeoutInMillis" not found in context "java:". 
    at com.ibm.ws.naming.ipbase.NameSpace.lookupInternal(NameSpace.java:1228) 
    at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:1141) 
    at com.ibm.ws.naming.urlbase.UrlContextImpl.lookupExt(UrlContextImpl.java:1436) 
    at com.ibm.ws.naming.java.javaURLContextImpl.lookupExt(javaURLContextImpl.java:477) 
    ... 15 more 
+0

这是完整的日志吗?你在WAS之前有IIS吗?你如何部署.wlapp文件? – 2015-02-11 17:37:24

+0

如果您尝试不使用您正在使用的虚拟机,它是否工作?我怀疑有一个神秘的东西在玩一些大小限制,而不是WAS。 – 2015-02-11 17:45:35

+0

是的,还有一些其他日志我不确定它们是否相关,所以我没有发布它。安装WAS时我安装了IIS。我去灯光控制台工作,选择.wlapp并点击按钮。 – Leslie 2015-02-11 17:54:07

回答

0

卸载IBM Installation Manager中的WAS 8.5.5.2修补程序以回滚到WAS 8.5.5.0并重新启动所有内容,然后我可以部署适配器。

0

在微软IIS有一个属性来控制这个文件大小限制。该属性被称为maxAllowedContentLength,它可以在IIS配置文件的<requestLimits>元素中找到。其默认值是30 000 000字节。

你应该增加它到一个文件大小将包含wlapp的文件大小。

+0

oops..i在“C:\ Windows \ System32 \ inetsrv”下找不到配置文件 – Leslie 2015-02-11 18:38:02

+0

日志中的错误消息与MobileFIrst Platform Foundation V6.3中修复的缺陷有关:https:// www -304.ibm.com/support/entdocview.wss?uid=swg1PI34203。我不确定它如何连接到文件大小(希望增加此属性将处理该问题),但除非实际尝试设置该属性,否则关于JNDI属性本身的消息可以忽略。 – patbarron 2015-02-11 18:52:47

+0

为了澄清,我在WAS安装向导期间选择了IIS,我从未启动该Web服务器的服务。我没有设置这些属性中的任何一个,但这是部署.wlapp时引发的异常。 – Leslie 2015-02-12 05:28:40

相关问题