2015-02-11 57 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

相關問題