Deploying JAR - OK -- Deploying EAR - Not OK
All,
I am just working on a little sample application and have encountered a problem. I am using JBoss 4.2.2 GA (just recently downloaded) for this sample and can provide other system information if necessary (but I doubt it impacts anything).
When I build my stateless beans and package them in a Jar file everything works fine. I compile, Jar and then drop them to <jboss>/server/default/deploy. Running the following code results in success:@Test
public void doTest() throws NamingException {
// load the bean
Object obj = initialContext.lookup("DeploymentBase/remote");
Assert.assertNotNull(obj);
Assert.assertTrue(obj instanceof DeploymentBaseCore);
// execute
((DeploymentBaseCore) obj).sayHi();
}When I package things up in an EAR, however, I cannot run this test.
I package everything up under the following structure:*EAR File*
- lib (+empty at this time+)
- META-INF
- application.xml
- myTest-main.jar
- +stateless bean package/classes+
- META-INF
- myTest-web.war
- +servlet package/classes+
- META-INF
- WEB-INF
- web.xml
- index.jspWhen I drop the packaged EAR into the <jboss>/server/default/deploy folder, it deploys just fine. The JSP pages at http://localhost:8080/myTest/index.jsp look just fine. However, when I attempt to run the test listed above, I receive the following error:javax.naming.NameNotFoundException: remote not bound
org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
org.jnp.server.NamingServer.getObject(NamingServer.java:543)
org.jnp.server.NamingServer.lookup(NamingServer.java:296)
org.jnp.server.NamingServer.lookup(NamingServer.java:270)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:597)
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
sun.rmi.transport.Transport$1.run(Transport.java:159)
java.security.AccessController.doPrivileged(Native Method)
sun.rmi.transport.Transport.serviceCall(Transport.java:155)
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
java.lang.Thread.run(Thread.java:619)
sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
javax.naming.InitialContext.lookup(InitialContext.java:392)
com.myserver.DeploymentBaseServlet.doGet(DeploymentBaseServlet.java:87)
javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)When I look at the JMX Console in JBoss (http://localhost:8080/jmx-console), I see that the jboss.j2ee section contains the proper information (and it looks the same as when I deploy the Jar file directly). That is as follows:
jboss.j2ee
* ear=myTest.ear,jar=myTest-main.jar,name=DeploymentBase,service=EJB3
* module=myTest-main.jar,service=EJB3
* service=ClientDeployer
* service=EARDeployer
* service=EARDeployment,url='myTest.ear'I'm not sure what I'm doing wrong here. My web.xml and application.xml files are listed below. Any help that can be provided would be greatly appreciated.
web.xml
<web-app>
<display-name>Web Test</display-name>
<servlet>
<servlet-class>com.myserver.DeploymentBaseServlet</servlet-class>
<servlet-name>DeploymentBaseServlet</servlet-name>
<display-name>Deployment Base Servlet</display-name>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>DeploymentBaseServlet</servlet-name>
<url-pattern>/servlets/DeploymentBase</url-pattern>
</servlet-mapping>
<session-config>
<session-timeout>0</session-timeout>
</session-config>
</web-app>-----
application.xml
<application xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd"
version="1.4">
<display-name>EJB 3 / JBoss Sample</display-name>
<module>
<ejb>myTest-main.jar</ejb>
</module>
<module>
<web>
<web-uri>myTest-web.war</web-uri>
<context-root>/myTest</context-root>
</web>
</module>
</application>
Hi,
Could you get it going? I am also facing same problem and couldn't find any pointers on the internet that actually describe the problem here.
I am trying to deploy EJB3.0 on jboss-4.2.1.GA. Putting all the pieces(war/jar etc) into an ear and deploying it results in NameNotFoundException. Here is the error trace:
07:22:02,993 ERROR [STDERR] javax.naming.NameNotFoundException: AuthenticationBSEJBBean not bound
07:22:02,993 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
07:22:02,993 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
07:22:02,993 ERROR [STDERR] at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
07:22:02,993 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
07:22:02,993 ERROR [STDERR] at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)
07:22:02,993 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
07:22:02,993 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597)
07:22:02,993 ERROR [STDERR] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
07:22:02,993 ERROR [STDERR] at sun.rmi.transport.Transport$1.run(Transport.java:159)
07:22:02,993 ERROR [STDERR] at java.security.AccessController.doPrivileged(Native Method)
07:22:02,993 ERROR [STDERR] at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
07:22:02,993 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
07:22:02,993 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
07:22:02,993 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
07:22:02,993 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
07:22:02,993 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
07:22:02,993 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619)
07:22:02,993 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
07:22:02,993 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
07:22:02,993 ERROR [STDERR] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
07:22:02,993 ERROR [STDERR] at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
07:22:02,993 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
07:22:02,993 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
07:22:02,993 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialContext.java:392)
07:22:02,993 ERROR [STDERR] at com.account.helper.AuthenticationUIHelper.bind(AuthenticationUIHelper.java:117)
07:22:02,993 ERROR [STDERR] at com.account.helper.AuthenticationUIHelper.<init>(AuthenticationUIHelper.java:132)
07:22:02,993 ERROR [STDERR] at com.account.helper.AuthenticationUIHelper.getInstance(AuthenticationUIHelper.java:94)
07:22:02,993 ERROR [STDERR] at com.account.action.LoginActionForm.execute(LoginActionForm.java:82)
07:22:02,993 ERROR [STDERR] at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
07:22:02,993 ERROR [STDERR] at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
07:22:02,993 ERROR [STDERR] at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
07:22:02,993 ERROR [STDERR] at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
07:22:02,993 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
07:22:02,993 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
07:22:03,009 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
07:22:03,009 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
07:22:03,009 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
07:22:03,009 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
07:22:03,009 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
07:22:03,009 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
07:22:03,009 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
07:22:03,009 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
07:22:03,009 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
07:22:03,009 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
07:22:03,009 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
07:22:03,009 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
07:22:03,009 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
07:22:03,009 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
07:22:03,009 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
07:22:03,009 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
07:22:03,009 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)My deployment descriptor & ear file structure are exactly like yours.
Any help is highly appreciated.
Similar Messages
-
How to Create a jar war or ear--Probelms in deploying
I have the following dir structure. I am using Struts 1.1 and weblogic 7.0
APP
+jsp
+WEB-INF
+ ---lib
+--- classes
+----com
--ap
--action
--beans
--handler
--service
--client
--ejb
--valueobject
1> Do I need to create a ear file since i want both the ejb (under service folder) and war as reusable components. Whenever we have a EJB component do we always need to have an EAR file??
2> Whats the best way to create the jar, war or ear file. I am facing great difficulty in deploying the war.Do we need to set any classpath before we create the war and jar files except for the deployment descriptors.I have created the ejb descriptors correctly through ejbc.
3>I have kept struts.jar,log4j.jar under lib folder. However when i create the ear and try to deploy it under weblogic it deploys the war file but gives error in deploying the jar which has the ejb. I have aslo validated the jar using ejbc.
It gives error indicating that it requires struts.jar in classpath. If we give the classpath of struts.jar at system leve the Application deploys with ease..Can anyone tell whats the error.The jar does not use any strust component .
4>Also the valueobject which has some beans which are used to populate the jsp through Actionformbean. Is it ok if we give refrences in both ejb jar and war?
ie while creating jar and war folder have the valueobject in both the files or will it lead to any errors..
Thanks in Advance
....Yes, I have tried that. But, as the server is running and the jars are in use, it throws and EditFailedException
-
How to deploy ear file with jar file and war file with different names
Hi,
As part of weblogic migration from WL 6.1 sp3 to WL 10, Iam facing some problem.
Problem:
I have one ear file(abc.ear) to deploy which contains one jar file(xyz.jar) and one war file(pqr.war).
In config.xml file of WL 6.1, it was mentioned as :
<Application Deployed="true" Name="abc" Path="./config/mydomain/applications/abc.ear">
<EJBComponent Name="xyz" Targets="myserver" URI="xyz.jar"/>
<WebAppComponent Name="pqr" Targets="myserver" URI="pqr.war"/>
</Application>.
The above is working fine.
But in config.xml file WL10,I cannot mention the same.
I need to have different application anmes for ear,jar and war.If I deploy as a ear file,the jar and war files are deployed with the same ear file name.
I tried the following options:
1) Deploying as a ear file by adding <sub-deployments>
2) Deploying both war and jar seperately which is not recommended in my application.
Please provide the content I should place in the config.xml so that everything works fine correctly.
Any help is appreciated.Hi,
As part of weblogic migration from WL 6.1 sp3 to WL 10, Iam facing some problem.
Problem:
I have one ear file(abc.ear) to deploy which contains one jar file(xyz.jar) and one war file(pqr.war).
In config.xml file of WL 6.1, it was mentioned as :
<Application Deployed="true" Name="abc" Path="./config/mydomain/applications/abc.ear">
<EJBComponent Name="xyz" Targets="myserver" URI="xyz.jar"/>
<WebAppComponent Name="pqr" Targets="myserver" URI="pqr.war"/>
</Application>.
The above is working fine.
But in config.xml file WL10,I cannot mention the same.
I need to have different application anmes for ear,jar and war.If I deploy as a ear file,the jar and war files are deployed with the same ear file name.
I tried the following options:
1) Deploying as a ear file by adding <sub-deployments>
2) Deploying both war and jar seperately which is not recommended in my application.
Please provide the content I should place in the config.xml so that everything works fine correctly.
Any help is appreciated. -
Deploying EJB JAR and Application EAR, META-INF directory name
To all:
I had a problem the last couple of days with deploying an EJB and application.
I'm new to WebLogic, maybe this is common knowledge, but I researched it and
didn't find any reference to what I discovered.
I'm using WebLogic Server 7 Service Pack 2 (7.02), on Windows 2000.
My problem was that the application that I was trying to deploy would not deploy
successfully, because a dependent class was not found for the EJB. I tried everything,
but the only thing I could get to work was placing the dependent jar files in
the classpath of the WebLogic server, within the start script. I correctly had
the Class-Path manifest line correct, but the dependent classes were not being
found.
Through trial and error I discovered that the META-INF directory within the JAR
and EAR archives HAS TO BE ALL UPPERCASE for the app server to successfully find
the manifest.mf file and the application.xml file.
As soon as I changed the directory name in both the EJB JAR file and the application
EAR file, the EJB deployed successfully, all dependent classes were then found.
I'm posting this here to help anybody that might have the same problem. There
is not any documentation that I could find that had this directory name requirement
explicitly stated.
Regards,
JDWhat does the manual for the OC4J application server have to say about it all?
-
I was trying to deploy EAR at Sun 8.1 Q2. But I got the following error:
Fatal Error from EJB Compiler -- Caught javax.ejb.EJBException while processing CMP beans for application [testApp]; module [testEJB.jar]: nested exception is: java.lang.ClassNotFoundException: com.abc.ejb.actionItemBean. See log for details.
testEJB.jar is my EJB module, and actionItemBean is an entity bean included in my jar file. I am able to deploy testEJB.jar as EJB module at Sun app server.
Any idea to resolve the problem is appreciated!hi JatWork
testApp is not able to find com.abc.ejb.actionItemBean
You may want to extract the EAR, check testApp's META-INF, application descriptor e.g. application-client.xml, and make sure it refers to correct package name used in actionItemBean.java. Then bundle the EAR and redeploy it -
Deploying EAR using weblogic 10.3.6 under XP
Hi Guys,
tha last step of deployment EAR is to Star--->Servicing all requests, i am getting the following error?
Messages
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment. weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'BODQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation. at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:691) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:267) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1131) at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:1025) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1288) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208) at weblogic.deploy.internal.targetserver.operations.StartOperation.createAndPrepareContainer(StartOperation.java:94) at weblogic.deploy.internal.targetserver.operations.StartOperation.doPrepare(StartOperation.java:107) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) NestedException Message is :[EJB:010176]The resource-env-ref 'BODQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-env-ref must be mapped to a JNDI name using the resource-env-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.
Errors were encountered while performing this operation.
what does it mean? is there any idea?
Have a nice day.
Edited by: ashash on Aug 22, 2012 3:36 AMAtlassian has pretty good user forums, you might be able to get additional help there:
http://forums.atlassian.com/forum.jspa?forumID=46
Does the deployment screen show it has "Running". What does the deployment screen for the app show its context root as?
Also, why not just JIRA standalone? (it comes out of the box running in embedded tomcat). -
Problem while deploying ear application in OAS
Hello,
I am trying to undeploy application or redeploy, its is giving exception below exception
ADMN-300071
No ApplicationInfo is associated with application named: example1
oracle.ias.sysmgmt.deployment.j2ee.exception.J2eeDeploymentException: No ApplicationInfo is associated with application named: example1 ,
Again i have tried to deploy application freshly, it is telling already application is exists, i am not getting what we can do, even i have checked list of applications , the above application is present in list ,
i am also getting admn-300075
i am not able to deploy, redeploy or undeploy , i am not able to do anything.
Thanks,
ChaitanyaI removed the jar files from /lib/ext and putted el-api.jar by myself in /lib directory. Now I can deploy my application as EAR file without problems but when I try to deploy it directly through JDeveloper the problem is the same:
[#|2013-08-22T09:43:22.507+0200|SEVERE|glassfish3.1.2|org.apache.catalina.core.ContainerBase|_ThreadID=98;_ThreadName=Thread-2;|ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: java.lang.IllegalArgumentException: java.lang.ClassNotFoundException:oracle.adf.share.glassfish.listener.ADFGlassFishAppLifeCycleListener
I do understand that I should have this JAR but I do not know where to find it and where to put then.
Can you help in this point? Thanks -
Error during deploying *.ear to sap using ant
I want to deploy ear to sap with ant script,but it can not work.The error information as follows,can anybody give me some advice if you had the similar error,thanks.
C:\usr\sap\LJ1\J00\j2ee\deployment\ant>ant -f example_build.xml deploy -v
Apache Ant version 1.7.0 compiled on December 13 2006
Buildfile: example_build.xml
Detected Java version: 1.6 in: D:\Java\jdk1.6.0_18\jre
Detected OS: Windows 2003
parsing buildfile C:\usr\sap\LJ1\J00\j2ee\deployment\ant\example_build.xml with
URI = file:/C:/usr/sap/LJ1/J00/j2ee/deployment/ant/example_build.xml
Project base dir set to: C:\usr\sap\LJ1\J00\j2ee\deployment\ant
parsing buildfile jar:file:/D:/Perforce/tools/ant1.7.0/lib/ant.jar!/org/apache/t
ools/ant/antlib.xml with URI = jar:file:/D:/Perforce/tools/ant1.7.0/lib/ant.jar!
/org/apache/tools/ant/antlib.xml
[property] Loading C:\usr\sap\LJ1\J00\j2ee\deployment\ant\cfg\ant.properties
Build sequence for target(s) `deploy' is [deploy]
Complete build sequence is [deploy, import_ear, undeploy, params, ]
deploy:
[sapdeploy] Starting deployment with the following properties:
[sapdeploy] Version Handling Rule: all
[sapdeploy] Error Handling Strategies: [error action: 'prerequisites', error str
ategy: 'stop', error action: 'deploy', error strategy: 'stop']
[sapdeploy] The targeted SAP J2EE Engines are: [server host: 'localhost', server
port '50004', user name 'Administrator'.]
[sapdeploy] Deploy timeout: null
[sapdeploy] Starting to validate the data...
[sapdeploy] Validation ended
[sapdeploy] root dir c:\temp
[sapdeploy] Selected archives for deployment:
[sapdeploy] 1: 'c:\temp\dataservices-samples.war'
[sapdeploy] 2: 'c:\temp\test.ear'
[sapdeploy] Starting validation for the engine 'server host: 'localhost', server
port '50004', user name 'Administrator'.'
[sapdeploy] Engine data validated successfully
[sapdeploy] Starting deployment for the engine 'server host: 'localhost', server
port '50004', user name 'Administrator'.'
[sapdeploy] An error occured during the deployment.
[sapdeploy] The result of the deployment is: Error
[sapdeploy] Deployment ended
BUILD SUCCESSFUL
Total time: 0 secondsThe problem has been resolved,I make a stupid mistake.The reason caused the error is that the user of server was locked.I hope these will be helpful for people troubled by the same mistake.
-
How to deploy EAR file in Tomcat?
Is we can deploy ear file in tomcat?
Normally we can deploy WAR file in tomcat webapps folder. When we run the tomat it will automatically extract the war file.
But samethink I have tried EAR file. But it is not working.
Is we can deploy EAR file or not?
If not plz give reason.Hi
Normally we can deploy the war file thats routene stuff ofcourse ..........but when u deploy ear file it will give problmes as ear structure and war structure are differeant
The Tomcat Servlet/JSP Container
The Apache Tomcat 5.5 Servlet/JSP Container
Apache Logo
Links
* Docs Home
Contents
* Contents
* Introduction
* Installation
* Deployment
* Source Code
* Processes
* Example App
Application Developer's Guide
Deployment
Printer Friendly Version
print-friendly
version
Background
Before describing how to organize your source code directories, it is useful to examine the runtime organization of a web application. Prior to the Servlet API Specification, version 2.2, there was little consistency between server platforms. However, servers that conform to the 2.2 (or later) specification are required to accept a Web Application Archive in a standard format, which is discussed further below.
A web application is defined as a hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately, or in a "packed" form known as a Web ARchive, or WAR file. The former format is more useful during development, while the latter is used when you distribute your application to be installed.
The top-level directory of your web application hierarchy is also the document root of your application. Here, you will place the HTML files and JSP pages that comprise your application's user interface. When the system administrator deploys your application into a particular server, he or she assigns a context path to your application (a later section of this manual describes deployment on Tomcat). Thus, if the system administrator assigns your application to the context path /catalog, then a request URI referring to /catalog/index.html will retrieve the index.html file from your document root.
Standard Directory Layout
To facilitate creation of a Web Application Archive file in the required format, it is convenient to arrange the "executable" files of your web application (that is, the files that Tomcat actually uses when executing your app) in the same organization as required by the WAR format itself. To do this, you will end up with the following contents in your application's "document root" directory:
* *.html, *.jsp, etc. - The HTML and JSP pages, along with other files that must be visible to the client browser (such as JavaScript, stylesheet files, and images) for your application. In larger applications you may choose to divide these files into a subdirectory hierarchy, but for smaller apps, it is generally much simpler to maintain only a single directory for these files.
* /WEB-INF/web.xml - The Web Application Deployment Descriptor for your application. This is an XML file describing the servlets and other components that make up your application, along with any initialization parameters and container-managed security constraints that you want the server to enforce for you. This file is discussed in more detail in the following subsection.
* /WEB-INF/classes/ - This directory contains any Java class files (and associated resources) required for your application, including both servlet and non-servlet classes, that are not combined into JAR files. If your classes are organized into Java packages, you must reflect this in the directory hierarchy under /WEB-INF/classes/. For example, a Java class named com.mycompany.mypackage.MyServlet would need to be stored in a file named /WEB-INF/classes/com/mycompany/mypackage/MyServlet.class.
* /WEB-INF/lib/ - This directory contains JAR files that contain Java class files (and associated resources) required for your application, such as third party class libraries or JDBC drivers.
When you install an application into Tomcat (or any other 2.2/2.3-compatible server), the classes in the WEB-INF/classes/ directory, as well as all classes in JAR files found in the WEB-INF/lib/ directory, are made visible to other classes within your particular web application. Thus, if you include all of the required library classes in one of these places (be sure to check licenses for redistribution rights for any third party libraries you utilize), you will simplify the installation of your web application -- no adjustment to the system class path (or installation of global library files in your server) will be necessary.
Much of this information was extracted from Chapter 9 of the Servlet API Specification, version 2.3, which you should consult for more details.
Shared Library Files
Like most servlet containers, Tomcat 5 also supports mechanisms to install library JAR files (or unpacked classes) once, and make them visible to all installed web applications (without having to be included inside the web application itself. The details of how Tomcat locates and shares such classes are described in the Class Loader HOW-TO documentation. For the purposes of our discussion, there are two locations that are commonly used within a Tomcat 5 installation for shared code:
* $CATALINA_HOME/common/lib - JAR files placed here are visible both to web applications and internal Tomcat code. This is a good place to put JDBC drivers that are required for both your application and internal Tomcat use (such as for a JDBCRealm).
* $CATALINA_BASE/shared/lib - JAR files placed here are visible to all web applications, but not to internal Tomcat code. This is the right place for shared libraries that are specific to your application.
Out of the box, a standard Tomcat 5 installation includes a variety of pre-installed shared library files, including:
* The Servlet 2.4 and JSP 2.0 APIs that are fundamental to writing servlets and JavaServer Pages.
* An XML Parser compliant with the JAXP (version 1.2) APIs, so your application can perform DOM-based or SAX-based processing of XML documents.
Web Application Deployment Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
As mentioned above, the /WEB-INF/web.xml file contains the Web Application Deployment Descriptor for your application. As the filename extension implies, this file is an XML document, and defines everything about your application that a server needs to know (except the context path, which is assigned by the system administrator when the application is deployed).
The complete syntax and semantics for the deployment descriptor is defined in Chapter 13 of the Servlet API Specification, version 2.3. Over time, it is expected that development tools will be provided that create and edit the deployment descriptor for you. In the meantime, to provide a starting point, a basic web.xml file is provided. This file includes comments that describe the purpose of each included element.
NOTE - The Servlet Specification includes a Document Type Descriptor (DTD) for the web application deployment descriptor, and Tomcat 5 enforces the rules defined here when processing your application's /WEB-INF/web.xml file. In particular, you must enter your descriptor elements (such as <filter>, <servlet>, and <servlet-mapping> in the order defined by the DTD (see Section 13.3).
Tomcat Context Descriptor
The description below uses the variable name $CATALINA_HOME to refer to the directory into which you have installed Tomcat 5, and is the base directory against which most relative paths are resolved. However, if you have configured Tomcat 5 for multiple instances by setting a CATALINA_BASE directory, you should use $CATALINA_BASE instead of $CATALINA_HOME for each of these references.
A /META-INF/context.xml file can be used to define Tomcat specific configuration options, such as loggers, data sources, session manager configuration and more. This XML file must contain one Context element, which will be considered as if it was the child of the Host element corresponding to the Host to which the The Tomcat configuration documentation contains information on the Context element.
Deployment With Tomcat 5
In order to be executed, a web application must be deployed on a servlet container. This is true even during development. We will describe using Tomcat 5 to provide the execution environment. A web application can be deployed in Tomcat by one of the following approaches:
* Copy unpacked directory hierarchy into a subdirectory in directory $CATALINA_HOME/webapps/. Tomcat will assign a context path to your application based on the subdirectory name you choose. We will use this technique in the build.xml file that we construct, because it is the quickest and easiest approach during development. Be sure to restart Tomcat after installing or updating your application.
* Copy the web application archive file into directory $CATALINA_HOME/webapps/. When Tomcat is started, it will automatically expand the web application archive file into its unpacked form, and execute the application that way. This approach would typically be used to install an additional application, provided by a third party vendor or by your internal development staff, into an existing Tomcat installation. NOTE - If you use this approach, and wish to update your application later, you must both replace the web application archive file AND delete the expanded directory that Tomcat created, and then restart Tomcat, in order to reflect your changes.
* Use the Tomcat 5 "Manager" web application to deploy and undeploy web applications. Tomcat 5 includes a web application, deployed by default on context path /manager, that allows you to deploy and undeploy applications on a running Tomcat server without restarting it. See the administrator documentation (TODO: hyperlink) for more information on using the Manager web application.
* Use "Manager" Ant Tasks In Your Build Script. Tomcat 5 includes a set of custom task definitions for the Ant build tool that allow you to automate the execution of commands to the "Manager" web application. These tasks are used in the Tomcat deployer.
* Use the Tomcat Deployer. Tomcat 5 includes a packaged tool bundling the Ant tasks, and can be used to automatically precompile JSPs which are part of the web application before deployment to the server.
Deploying your app on other servlet containers will be specific to each container, but all containers compatible with the Servlet API Specification (version 2.2 or later) are required to accept a web application archive file. Note that other containers are NOT required to accept an unpacked directory structure (as Tomcat does), or to provide mechanisms for shared library files, but these features are commonly available.
Copyright © 1999-2006, Apache Software Foundation -
Error when deploying ear with war module.
Can somebody help me with a problem? This problem is realy strange.
I have three projects: ordinary project (jar project), war project and ear project.
The war project uses classes form jar project and it is a part of ear project.
There is an abstract class in jar:
public abstract class MyDataTable {
public abstract String method1();
public abstract String method2();
//And some others abstract methods
Class MyResultSetTable extends MyDataTable class:
public class MyResultSetTable extends MyDataTable {
private ResultSet rs;
public MyResultSetTable(ResultSet resSet) {
rs = resSet;
//Implementation of abstract methods
In jar there is another class MyDataPacket, which performs transformation between MyDataTable and XML document (Delphi data packet):
public class MyDataPacket {
public static String tableToXML(MyDataTable table) {/Implementation}
public static MyDataTable xmlToTable(String xmlSource) {/Implementation}
In war there is a simple Web service which interact with clients by means of the data packets:
@WebService
public class MyWebService {
@WebMethod
public String myMethod(){
//Creating connection and opening ResultSet rs
MyDataTable t = new MyResultSetTable(rs);
return MyDataPacket.tableToXML(t);
This war application belongs to Enterprise Application (ear project). I use Sun Java System
Application Server Platform Edition 9.0_01 (build b02-p01). When I deploy ear into server an
error occurs:
Exception occured in J2EEC Phase
java.lang.NoClassDefFoundError: jarSource/MyDataTable
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)
at java.lang.Class.privateGetPublicMethods(Class.java:2519)
at java.lang.Class.getMethods(Class.java:1406)
When I change abstract class MyDataTable on MyResultSetTable in static method
tableToXML, the error disappears. I think that the problem is that I use abstract
class in this method. Please, can somebody explanes me this situation.
PS: Sorry for my bad English. I jast start to study this language.
PSS: You can copy-past these classes for simple testing this misunderstanding:
jar:
public abstract class MyDataTable {
public abstract String method1() throws Exception;
public abstract String method2() throws Exception;
public class MyResultSetTable extends MyDataTable{
public String method1() throws Exception {return "method1";}
public String method2() throws Exception {return "method2";}
public class MyDataPacket {
public static String tableToXML(MyDataTable t) {return "tableToXML";}
war:
import jarSource.MyDataPacket;
import jarSource.MyDataTable;
import jarSource.MyResultSetTable;
import javax.jws.WebMethod;
import javax.jws.WebService;
@WebService()
public class MyView {
@WebMethod
public String myMethod1(){
MyDataTable t = new MyResultSetTable();
return MyDataPacket.tableToXML(t);
ear: Adding war to ear.I beleive this is a classpath problem, namely the classespath does not exist for the .jar file when the .war is trying to access the files. I would think if the .jar file is in WEB-INF/classes in your .war your error would go away. If you are placing the .jar in the root of the .ear then you must set the classpath.
-
Error when deploying ear to MAS managed AS 11g.
I posted this on General, but, I guess this is the right forum for this.
I used "asctl deployApp ..." to deploy ear to MAS mode AS11g and encountered a following error.
Connected to:
Oracle Fusion Middleware Administration Server Release 11.1.1.0.0
MAS Transaction started.
MAS Transaction rolledback.
MAS-0416: Management Exception.
Cause:
Java heap space
Is there any documents showing reason/solution for the error ?
If you can give an answer, that'll be great.
Thanks,
IncheolYes, my EAR has been deployed on WLS8.1.6 and works fine...
Yes, i found com.bea.wlw.runtime.core.servlet.WebappContextListener on my web.xml
Ok my first run was giving me this:
<Mar 20, 2010 3:00:05 PM ICT> <Error> <HTTP> <BEA-101163> <Could not load user defined listener: com.bea.wlw.runtime.core.servlet.WebappCont
extListenerjava.lang.ClassNotFoundException: com.bea.wlw.runtime.core.servlet.WebappContextListener
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:296)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
Truncated. see log file for complete stacktrace
And then I added my knex.jar and log4j.jar (on newly created domain on WLS10.3.2)...Thus giving me error on the first post....something like
<Mar 20, 2010 3:09:25 PM ICT> <Warning> <HTTP> <BEA-101162> <User defined listener com.bea.wlw.runtime.core.servlet.WebappContextListener fa
iled: java.lang.NoSuchMethodError: weblogic.servlet.internal.WebAppServletContext.registerServlet(Ljava/lang/String;Ljava/lang/String;Ljava/util/Map;)V.java.lang.NoSuchMethodError: weblogic.servlet.internal.WebAppServletContext.registerServlet(Ljava/lang/String;Ljava/lang/String;Ljava/util/Map;)V
at com.bea.wlw.runtime.core.servlet.WebappContextListener.contextInitialized(WebappContextListener.java:62)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
Truncated. see log file for complete stacktrace
So what is the solution?
Regards -
Read the version of deployed EAR modules via JMX (WLS 10.0)
Hello
We are deploying some EAR components into a WLS 10.0. Now we want to monitor the version number of the deployed EARs via a JMX client. The version number is provided in the manifest of the EAR (Implementation-Version).
I read through some JMX related documents by BEA and searched the web, but I could not find any information on how to read the version.
Does anybody know how to do that or where to look in order to get the version numbers of the deployed components via JMX? Do I have to write my own MBean offering this version attribute?
Every hint is welcomed!
Thanks
Toni
Edited by: user10451156 on Oct 21, 2008 10:53 AMHi, Toni.
The input must be a externally provided version number, if you have no access to write manifest entries, or to the deployment process.
If this version number is already set in the ear file, you can use this process inside your custom mbean (an elaboration of Benoit's suggestion)
1 look up the application component from JMX
* http://edocs.bea.com/wls/docs100/wlsmbeanref/mbeans/AppDeploymentMBean.html
2 obtain the path of the ear file
3 open a JarURLConnection to this ear
* http://java.sun.com/javase/6/docs/api/java/net/JarURLConnection.html
4 read the implementation version, which was already provided.
* http://java.sun.com/javase/6/docs/api/java/util/jar/Attributes.Name.html#IMPLEMENTATION_VERSION
Sadly, this won't pop-up on the WLS console, you'd have to write or use a custom extension to do that.
* https://wls-console-extensions.projects.dev2dev.bea.com/
I hope this helps.
-Adrian -
Deploy EAR failure,Who can help me to deploy?
Dear all:
I'm running two cluster set-ups in the WLS6.1 , follow introduction my
test condition:
Two members on NT server and an Admin server, they reside all different
Machine.
I test it before package EAR , jsp and servlet call SessionBean to work
very well,but
I package a test EAR file , it includes a Stateful Session Bean and war
file(only one Servlet and three JSPs)
When I deployed EAR file, Server show a error message to below:
> > <Error> <Management> <Error initializing module Login.war of
application ClusterAdmin:Name=gfortuneNet,
> > Type=Application from path
.\config\ClusterAdmin\applications\gfortuneNet.ear: Login.war does not
exist.>
> > <Notice> <Management> <Application Poller not started for production
server.>
I check out the Administrator Console , I find "Login.war" to deploy
unsuccessful , Following is my test code and configuration:
***Servlet***
public class loginServlet extends HttpServlet implements
java.io.Serializable {
private static final String CONTENT_TYPE = "text/html; charset=BIG5";
public void doPost(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
response.setContentType(CONTENT_TYPE);
PrintWriter out = response.getWriter();
doGet(request,response);
public void doGet(HttpServletRequest request, HttpServletResponse
response) throws ServletException, IOException {
response.setContentType(CONTENT_TYPE);
PrintWriter out = response.getWriter();
HttpSession session = request.getSession(false);
try{
Context ctx = getInitialContext();
LoginQueryHome home = (LoginQueryHome) ctx.lookup("LoginQuery");
LoginQuery the_ejb = home.create();
} catch (NamingException e)
{ e.printStackTrace(); }
catch (RemoteException e)
{ e.printStackTrace(); }
catch (CreateException e)
{ e.printStackTrace();}
public static Context getInitialContext()throws NamingException
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
p.put(Context.PROVIDER_URL, "t3://10.168.168.32:9001"); //
cluster1 server
return new InitialContext(p);
**web.xml :**
<?xml version="1.0" ?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
Application 1.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd>
<web-app>
<servlet>
<servlet-name>loginServlet</servlet-name>
<servlet-class>com.servlet.loginServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>loginServlet</servlet-name>
<url-pattern>/loginServlet</url-pattern>
</servlet-mapping>
</web-app>
**weblogic.xml :**
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web
Application 6.0//EN"
"http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd>
<weblogic-web-app>
<description>WebLogic Descriptor</description>
<session-descriptor>
<session-param>
<param-name>
PersistentStoreType
</param-name>
<param-value>
replicated
</param-value>
</session-param>
</session-descriptor>
</weblogic-web-app>
**application.xml:**
<?xml version="1.0" encoding="ISO8859_1"?>
<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE
Application 1.2//EN'
'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
<application>
<display-name>login</display-name>
<description>Application description</description>
<module>
<ejb>Test_BookBean.jar</ejb> // This is
Stateful Session Bean
</module>
<module>
<web>
<web-uri>Login.war</web-uri>
<context-root>clicklit</context-root>
</web>
</module>
</application>
***weblogic-ejb-jar.xml***
<!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD
WebLogic 6.0.0 EJB//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>LoginQueryBean</ejb-name>
<stateful-session-descriptor>
<stateful-session-clustering>
<home-load-algorithm>RoundRobin</home-load-algorithm>
<replication-type>InMemory</replication-type>
</stateful-session-clustering>
</stateful-session-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/CORDataSource</res-ref-name>
<jndi-name>GalaxyDataSource</jndi-name>
</resource-description>
</reference-descriptor>
<jndi-name>LoginQuery</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Please every bea consultants tell me what's lost to build up ?
Best Regards,
James Huang
I'm not really a servlet expert, but it appears that you've enabled
in-memory replication for the Login servlet, but your WLS is not
clustered.
-- Rob
james wrote:
>
> Hi! Rob Woollen:
> First thanks for your responsion , I forget Configure the
> HttpClusterServlet .
> but I configure the HttpClusterServlet to web.xml lately, and only deploy
> Login.war to WLS6.1 , finding the other error message,Can you tell me,
> what's wrong for me?
>
> > > **web.xml
> file************************************************************************
> **
> <?xml version="1.0" ?>
> <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
> 1.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
> <web-app>
> <servlet>
> <servlet-name>loginServlet</servlet-name>
> <servlet-class>com.servlet.loginServlet</servlet-class>
> </servlet>
> <servlet>
> <servlet-name>HttpClusterServlet</servlet-name>
>
> <servlet-class>weblogic.servlet.internal.HttpClusterServlet</servlet-class>
> <init-param>
> <param-name>defaultServers</param-name>
>
> <param-value>10.168.168.32:9001:9002|10.168.168.200:9001:9002|10.168.168.154
> :9001:9002</param-value>
> </init-param>
> <init-param>
> <param-name>DebugConfigInfo</param-name>
> <param-value>OFF</param-value>
> </init-param>
> </servlet>
> <servlet-mapping>
> <servlet-name>loginServlet</servlet-name>
> <url-pattern>/loginServlet</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>HttpClusterServlet</servlet-name>
> <url-pattern>/</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>HttpClusterServlet</servlet-name>
> <url-pattern>*.jsp</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>HttpClusterServlet</servlet-name>
> <url-pattern>*.htm</url-pattern>
> </servlet-mapping>
> <servlet-mapping>
> <servlet-name>HttpClusterServlet</servlet-name>
> <url-pattern>*.html</url-pattern>
> </servlet-mapping>
> </web-app>
>
> > > **Error
> message*********************************************************************
> *****
> <2001/9/10 ??11?35?52?> <Error> <HTTP Session> <FATAL: replicated HTTP sess
> ions specified but clustering not enabled for webapp: /Login>
> javax.management.MBeanException
> at
> weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
> .java:960)
> at
> weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl
> .java:913)
> at
> weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:898)
> at
> weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
> .java:618)
> at
> weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
> 90)
> at
> weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> nImpl.java:350)
> at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
> at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
> at
> weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
> at
> weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
> at $Proxy69.addTarget(Unknown Source)
> at
> weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationM
> anager.java:833)
> at
> weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
> ionManager.java:930)
> at
> weblogic.management.mbeans.custom.ApplicationManager.addApplication(Applicat
> ionManager.java:852)
> at
> weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
> .java:768)
> at
> weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager
> .java:701)
> at
> weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManag
> er.java:198)
> at java.lang.reflect.Method.invoke(Native Method)
> at
> weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
> .java:606)
> at
> weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:5
> 90)
> at
> weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
> nImpl.java:350)
> at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
> at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
> at
> weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
> at
> weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
> at $Proxy5.update(Unknown Source)
> at
> weblogic.management.console.webapp._domain.__upload_app._jspService(__upload
> _app.java:150)
> at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
> at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :263)
> at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :200)
> at
> weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImp
> l.java:190)
> at
> weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
> at
> weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java
> :35)
> at
> weblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
> rvlet.java:172)
> at
> weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
> let.java:85)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :263)
> at
> weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
> :200)
> at
> weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
> ntext.java:2390)
> at
> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
> :1959)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> <2001/9/10 ??11?35?52?> <Error> <Management> <Error deploying application
> .\config\ClusterAdmin\applications\Login.war :
> java.lang.reflect.UndeclaredThrowableException>
>
> > > Best Regards,
> > >
> > > James Huang 09/10/2001
>
> "Rob Woollen" <[email protected]> ?????
> news:[email protected]...
> > It looks like the server is complaining about the Login.war file not
> > existing (or in the specified place) in the ear file.
> >
> > -- Rob
> >
> > james wrote:
> > >
> > > Dear all:
> > > I'm running two cluster set-ups in the WLS6.1 , follow
> introduction my
> > > test condition:
> > > Two members on NT server and an Admin server, they reside all different
> > > Machine.
> > > I test it before package EAR , jsp and servlet call SessionBean to work
> > > very well,but
> > > I package a test EAR file , it includes a Stateful Session Bean and war
> > > file(only one Servlet and three JSPs)
> > > When I deployed EAR file, Server show a error message to below:
> > >
> ****************************************************************************
> > > *******************
> > > > > <Error> <Management> <Error initializing module Login.war of
> > > application ClusterAdmin:Name=gfortuneNet,
> > > > > Type=Application from path
> > > .\config\ClusterAdmin\applications\gfortuneNet.ear: Login.war does not
> > > exist.>
> > > > > <Notice> <Management> <Application Poller not started for
> production
> > > server.>
> > >
> ****************************************************************************
> > > *******************
> > > I check out the Administrator Console , I find "Login.war" to deploy
> > > unsuccessful , Following is my test code and configuration:
> > >
> > > ***Servlet***
> > > public class loginServlet extends HttpServlet implements
> > > java.io.Serializable {
> > > private static final String CONTENT_TYPE = "text/html;
> charset=BIG5";
> > > public void doPost(HttpServletRequest request, HttpServletResponse
> > > response) throws ServletException, IOException {
> > > response.setContentType(CONTENT_TYPE);
> > > PrintWriter out = response.getWriter();
> > > doGet(request,response);
> > > }
> > > public void doGet(HttpServletRequest request, HttpServletResponse
> > > response) throws ServletException, IOException {
> > > response.setContentType(CONTENT_TYPE);
> > > PrintWriter out = response.getWriter();
> > > HttpSession session = request.getSession(false);
> > > . . . . . . . . . . . . . .
> > > . . . . . . . . . . . . . .
> > > try{
> > > Context ctx = getInitialContext();
> > > LoginQueryHome home = (LoginQueryHome) ctx.lookup("LoginQuery");
> > > LoginQuery the_ejb = home.create();
> > > . . . . . . . . . . . . . .
> > > . . . . . . . . . . . . . .
> > > } catch (NamingException e)
> > > { e.printStackTrace(); }
> > > catch (RemoteException e)
> > > { e.printStackTrace(); }
> > > catch (CreateException e)
> > > { e.printStackTrace();}
> > > }
> > > public static Context getInitialContext()throws NamingException
> > > {
> > > Properties p = new Properties();
> > > p.put(Context.INITIAL_CONTEXT_FACTORY,
> > > "weblogic.jndi.WLInitialContextFactory");
> > > p.put(Context.PROVIDER_URL, "t3://10.168.168.32:9001");
> //
> > > cluster1 server
> > > return new InitialContext(p);
> > > }
> > > }
> > >
> ****************************************************************************
> > > ********
> > > **web.xml :**
> > > <?xml version="1.0" ?>
> > > <!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web
> > > Application 1.2//EN"
> > > "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd>
> > > <web-app>
> > > <servlet>
> > > <servlet-name>loginServlet</servlet-name>
> > >
> <servlet-class>com.servlet.loginServlet</servlet-class>
> > > </servlet>
> > > <servlet-mapping>
> > > <servlet-name>loginServlet</servlet-name>
> > > <url-pattern>/loginServlet</url-pattern>
> > > </servlet-mapping>
> > > </web-app>
> > >
> > > **weblogic.xml :**
> > > <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web
> > > Application 6.0//EN"
> > > "http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd>
> > > <weblogic-web-app>
> > > <description>WebLogic Descriptor</description>
> > > <session-descriptor>
> > > <session-param>
> > > <param-name>
> > > PersistentStoreType
> > > </param-name>
> > > <param-value>
> > > replicated
> > > </param-value>
> > > </session-param>
> > > </session-descriptor>
> > > </weblogic-web-app>
> > >
> ****************************************************************************
> > > ********
> > > **application.xml:**
> > > <?xml version="1.0" encoding="ISO8859_1"?>
> > > <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD
> J2EE
> > > Application 1.2//EN'
> > > 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
> > > <application>
> > > <display-name>login</display-name>
> > > <description>Application description</description>
> > > <module>
> > > <ejb>Test_BookBean.jar</ejb> // This is
> > > Stateful Session Bean
> > > </module>
> > > <module>
> > > <web>
> > > <web-uri>Login.war</web-uri>
> > > <context-root>clicklit</context-root>
> > > </web>
> > > </module>
> > > </application>
> > >
> ****************************************************************************
> > > ********
> > > ***weblogic-ejb-jar.xml***
> > > <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD
> > > WebLogic 6.0.0 EJB//EN'
> > >
> 'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
> > > <weblogic-ejb-jar>
> > > <weblogic-enterprise-bean>
> > > <ejb-name>LoginQueryBean</ejb-name>
> > > <stateful-session-descriptor>
> > > <stateful-session-clustering>
> > >
> <home-load-algorithm>RoundRobin</home-load-algorithm>
> > > <replication-type>InMemory</replication-type>
> > > </stateful-session-clustering>
> > > </stateful-session-descriptor>
> > > <reference-descriptor>
> > > <resource-description>
> > > <res-ref-name>jdbc/CORDataSource</res-ref-name>
> > > <jndi-name>GalaxyDataSource</jndi-name>
> > > </resource-description>
> > > </reference-descriptor>
> > > <jndi-name>LoginQuery</jndi-name>
> > > </weblogic-enterprise-bean>
> > > </weblogic-ejb-jar>
> > >
> > > Please every bea consultants tell me what's lost to build up ?
> > >
> > > Best Regards,
> > >
> > > James Huang
> >
> > --
> >
> > ----------------------------------------------------------------------
> >
> > AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
> >
> > by Michael Girdley, Rob Woollen, and Sandra Emerson
> >
> > http://learnWebLogic.com
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnWebLogic.com
-
About deploy ear including war
hi, i create a ear project referencing a war project, an exception occurs:
2008-10-21 15:24:14 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[003]Deployment aborted
Result
=> deployment aborted : file:/C:/DOCUME1/shihl/LOCALS1/Temp/temp61405cnafmpcear.ear
Aborted: development component 'cnafmpcear'/'sap.com'/'localhost'/'2008.10.21.15.09.45'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file cnafmpc.war com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason: java.io.IOException: Stream closed
at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.writeUpdatedJar(SimpleEARUpdater.java:338)
at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.writeUpdatedJar(SimpleEARUpdater.java:231)
at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.updateEar(SimpleEARUpdater.java:192)
at com.sap.engine.deploy.manager.DeployManagerImpl.makeTempEar(DeployManagerImpl.java:3737)
at com.sap.engine.deploy.manager.DeployManagerImpl.makeNewEar1(DeployManagerImpl.java:3715)
at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:529)
at com.sap.engine.deploy.manager.DeployManagerImpl.deploy(DeployManagerImpl.java:513)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:188)
at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:128)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68)
at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)
at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)
at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: Stream closed
at java.io.BufferedInputStream.ensureOpen(BufferedInputStream.java:120)
at java.io.BufferedInputStream.available(BufferedInputStream.java:336)
at com.sap.engine.services.deploy.ear.jar.SimpleEARUpdater.writeUpdatedJar(SimpleEARUpdater.java:331)
... 35 more
. Reason:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Deployment exception : The deployment of at least one item abortedI am not sure but I think that the file system could not change the file, is there any application running that you can stop to try again after stop it ?
-
Oracle.mds.core.MetadataNotFoundException when deploying EAR into local WLS
Hi all,
I tried to search the forum and read this: How to get rid of MDS I checked the domain path: C:\JDev11g_Home\system11.1.1.4.37.59.23\DefaultDomain, no space in the path. I searched this file it complains "adf-config.xml", couldn't find such file in my application at all. (My app is migrated from 10g to 11g using Trinidad.) I am using JDEV 11.1.14.0 and WLS 10.
Also, I tried these 2 scenarios when creating the EAR file: include / exclude these 2 jars: mdsrt.jar & oramds.jar, (Though I don't think this is the cause since it doesn't complain ClassNotFoundException.) same deployment error.
Below is the console output when deploying the EAR:
<MDSBackingStore> <obtainMetadataObject> Exception while getting mutable object
oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/META-INF/adf-config.xml"
at oracle.mds.core.MetadataObject.getBaseMO(MetadataObject.java:1163)
at oracle.mds.core.MDSSession.getBaseMO(MDSSession.java:2837)
at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1204)
at oracle.adf.share.jndi.MDSBackingStore.getMetadataObject(MDSBackingStore.java:389)
at oracle.adf.share.jndi.MDSBackingStore.obtainMetadataObject(MDSBackingStore.java:510)
at oracle.adf.share.jndi.MDSBackingStore.getMOBean(MDSBackingStore.java:566)
at oracle.adf.mbean.share.config.RuntimeMXBeanImpl.init(RuntimeMXBeanImpl.java:169)
at oracle.adf.mbean.share.config.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:159)
at oracle.adf.mbean.share.config.RuntimeMXBeanImpl.<init>(RuntimeMXBeanImpl.java:151)
at oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack.contextInitialized(ADFConfigLifeCycleCallBack.java:127)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
<ADFConfigLifeCycleCallBack> <contextInitialized> Failed to create config mbean.
Please help!
Thanks.
ShawnYes, I found this file in that folder. But, I checked the EAR file which is created from ant script such that there's no such adf-config.xml file at all anywhere in the EAR file inlcuding within the WAR file of the EAR. I also check another EAR file (of another application) and didn't see such adf-config.xml file either, but that EAR file is able to be deployed successfully in the local WLS. Both applications are migrated from 10g to 11g. I checked the other application for the build script and these 2 MDS jars are not used at all. I tried to remove these 2 MDS jars from the EAR file, but still same MDS-00013 error. Why will this occur in one app, but not in another app? Is there something I am missing?
Thanks
Maybe you are looking for
-
How do I use the raw file editor in PSE9 on a jpeg file?
How do I use the raw editor in PSE9 on a jpeg file?
-
new firefox autoupdated instead o asking me as usual. ( soubds similar to other ppls prob., but w a twist or two. now no toolbar, so ur answer to click bookmarks or whatever doesn't help me n there is no sidebar. also, i no longer can see which other
-
BlackBerry PlayBook battery power charge, discharge characteristics, and guidance on extending battery life KB27705 Overview The BlackBerry PlayBook may come to a power state where it is unable to power on; a Yellow LED may flash in a sequence of 5 f
-
Hi all, I m using internal frame. i m showing a menu which show cascde, tile horizontal and vertical. when i click on tile horizontal it should display all open internal frame in tile horizontal same as for cascade and tile vertical. how do i proceed
-
Error while executing Automatic Workflow Customizing
Hi!!!!!! In ECC6.0, i need to activate all the workflows in SWU3 (Automatic Workflow Customizing), but i was able to activate only some of the steps, remaining is still in red mark. While executing "Schedule Background Job for Missed Deadlines", it i