WLS Exception: <BEA-149132> <Split-dir application HRSystem can only be deployed to the Admin Server
2012-05-14 10:34
701 查看
Issue:
When you deploy a application to JDev Integrated WLS, you may got following exception.
Exception:
Solution:
Try to remove the Servers which is Not in Use from WLS console. Then try again. Issue may get resolved.
When you deploy a application to JDev Integrated WLS, you may got following exception.
Exception:
ServerInstance1 startup time: 25355 ms. ServerInstance1 started.[Running application HRSystem on Server Instance ServerInstance1...] [12:52:51 AM] ---- Deployment started. ---- [12:52:51 AM] Target platform is (Weblogic 10.3). [12:52:52 AM] Retrieving existing application information [12:52:53 AM] Running dependency analysis... [12:52:53 AM] Deploying 2 profiles... [12:52:55 AM] Wrote Web Application Module to C:\Users\Ami\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\HRSystem\ViewControllerWebApp.war [12:52:55 AM] Wrote Enterprise Application Module to C:\Users\Ami\AppData\Roaming\JDeveloper\system11.1.1.3.37.56.60\o.j2ee\drs\HRSystem [12:52:55 AM] Deploying Application... <Feb 10, 2011 12:52:55 AM IST> <Error> <Deployer> <BEA-149132> <Split-dir application HRSystem can only be deployed to the Admin Server> <Feb 10, 2011 12:52:55 AM IST> <Warning> <Deployer> <BEA-149124> <Failures were detected while initiating deploy task for application 'HRSystem'. Error is: '[Deployer:149132] Split-dir application HRSystem can only be deployed to the Admin Server' > [12:52:55 AM] #### Deployment incomplete. #### [12:52:55 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer) #### Cannot run application HRSystem due to error deploying to ServerInstance1.
Solution:
Try to remove the Servers which is Not in Use from WLS console. Then try again. Issue may get resolved.
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- WLS Exception: <BEA-149132> <Split-dir application HRSystem can only be deployed to the Admin Server
- Weblogic AdminServer启动失败，<Security> <BEA-090870> <The realm "myrealm" failed to be loaded
- <merge /> can be used only with a valid ViewGroup root and attachToRoot=true
- The project could not be deployed to the 'localhost' server because of the following connectivity problems.
- BEA-150021 - The admin server failed to authenticate the identity of the user username starting the managed server.
- Only one instance of a ScriptManager can be added to the page.
- <merge /> can be used only with a valid ViewGroup root and attachToRoot=true
- <<< Tomcat 部署项目There are no resources that can be added or removed from the server
- - Templates should only be responsible for mapping the state to the UI. Avoid placing tags with side-effects in your templates, such as <script>, as they will not be parsed.
- The only thing I can think of is to use something like "http://www.dyndns.org/cgi-bin/check_ip.cgi" others may have a be
- Cannot connect to WMI provider.You do not have permission or the server is unreachable.Note that you can only manager SQL Server 2005 and later version with SQL Server Configuration Manager.Invalid namespace [0x8004100e]
- vs2005下出现“Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive”的解决方法
- kubuntu之another application seems to be using the package system at this time问题即muon无法安装更新的问题
- Server Application Unavailable 【Failed to execute request because the App-Domain could not be created.】的解决办法
- ros-indigo卸载不全，出现The package <package name> needs to be reinstalled, but I can’t find an archive for
- Download and run CSQL on Linux -Only two commands will be used to start the server
- SQL Server 2005 RTM 安装错误 ：The SQL Server System Configuration Checker cannot be executed due to
- SQL Server 2005 RTM 安装错误 ：The SQL Server System Configuration Checker cannot be executed due to
- Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive
- Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server.