Deployment descriptor Using weblogic Builder

Hi
I am new to Ejb,
So kindly help me. can we create Deployment Descriptor from CMP bean,using Weblogic Builder.
Thanks
Satya
Edited by: satya22 on Dec 11, 2007 10:37 AM

satya22 wrote:
Hi
I am new to Ejb,Please let me know can we create an Deployment Descriptor
Using Weblogic Builder for an CMP Bean
ThanksHow many things are wrong here, hmmm.
1. Your subject line is useless
2. You posted in the wrong forum
3. You posted about an unrelated technology
4. You didn't make any attempt to do the task yourself
5. You probably haven't searched for an answer on Google
....did I miss anything?

Similar Messages

NullPointerException when validating module *.jar using WebLogic Builder

Hi,
When using WebLogic Builder to validate module ceiba.jar, it shows the following errors. How to fix it? Thanks a lot. Attachment is the deployment descriptors.
Validating module ceiba.jar
Compiling input jar D:\gzdswebproject\gzdsweb\ceiba.jar
Processing input descriptor
ERROR: Error processing input descriptor
ERROR: Error from ejbc: null
java.lang.NullPointerException at weblogic.ejb20.deployer.SessionBeanInfoImpl.assignDefaultTXAttributesIfNecessary(SessionBeanInfoImpl.java:291) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeTransactionAttribute(MBeanDeploymentInfoImpl.java:807) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:240) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:397) at weblogic.ejbc20.runBody(ejbc20.java:517) at weblogic.utils.compiler.Tool.run(Tool.java:146) at weblogic.utils.compiler.Tool.run(Tool.java:103) at weblogic.marathon.tasks.EJBCTask.runBackground(EJBCTask.java:140) at weblogic.tools.jellybeans.core.task.TaskThread.execute(TaskThread.java:127) at weblogic.tools.jellybeans.core.task.TaskThread.run(TaskThread.java:64)

following is the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<display-name>Bblm</display-name>
<ejb-name>Bblm</ejb-name>
<home>com.foresee.ceiba.bbxz.BblmHome</home>
<remote>com.foresee.ceiba.bbxz.Bblm</remote>
<ejb-class>com.foresee.ceiba.bbxz.BblmBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>Bbnr</display-name>
<ejb-name>Bbnr</ejb-name>
<home>com.foresee.ceiba.bbxz.BbnrHome</home>
<remote>com.foresee.ceiba.bbxz.Bbnr</remote>
<ejb-class>com.foresee.ceiba.bbxz.BbnrBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>Fjxx</display-name>
<ejb-name>Fjxx</ejb-name>
<home>com.foresee.ceiba.comm.FjxxHome</home>
<remote>com.foresee.ceiba.comm.Fjxx</remote>
<ejb-class>com.foresee.ceiba.comm.FjxxBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>Yhzxx</display-name>
<ejb-name>Yhzxx</ejb-name>
<home>com.foresee.ceiba.comm.YhzxxHome</home>
<remote>com.foresee.ceiba.comm.Yhzxx</remote>
<ejb-class>com.foresee.ceiba.comm.YhzxxBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>GsbsProcess</display-name>
<ejb-name>GsbsProcess</ejb-name>
<home>com.foresee.ceiba.gsbs.ejb.GsbsProcessHome</home>
<remote>com.foresee.ceiba.gsbs.ejb.GsbsProcess</remote>
<ejb-class>com.foresee.ceiba.gsbs.ejb.ejb.GsbsProcessBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>BGDJ</display-name>
<ejb-name>BGDJ</ejb-name>
<home>com.foresee.ceiba.swdj.bg.BGDJHome</home>
<remote>com.foresee.ceiba.swdj.bg.BGDJ</remote>
<ejb-class>com.foresee.ceiba.swdj.bg.BGDJBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>PersonalRegister</display-name>
<ejb-name>PersonalRegister</ejb-name>
<home>com.foresee.ceiba.swdj.gr.PersonalRegisterHome</home>
<remote>com.foresee.ceiba.swdj.gr.PersonalRegister</remote>
<ejb-class>com.foresee.ceiba.swdj.gr.PersonalRegisterBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>ProjectRegister</display-name>
<ejb-name>ProjectRegister</ejb-name>
<home>com.foresee.ceiba.swdj.xm.ProjectRegisterHome</home>
<remote>com.foresee.ceiba.swdj.xm.ProjectRegister</remote>
<ejb-class>com.foresee.ceiba.swdj.xm.ProjectRegisterBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>SqjlCjwtLm</display-name>
<ejb-name>SqjlCjwtLm</ejb-name>
<home>com.foresee.ceiba.sqjl.SqjlCjwtLmHome</home>
<remote>com.foresee.ceiba.sqjl.SqjlCjwtLm</remote>
<ejb-class>com.foresee.ceiba.sqjl.SqjlCjwtLmBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>SqjlCjwtNr</display-name>
<ejb-name>SqjlCjwtNr</ejb-name>
<home>com.foresee.ceiba.sqjl.SqjlCjwtNrHome</home>
<remote>com.foresee.ceiba.sqjl.SqjlCjwtNr</remote>
<ejb-class>com.foresee.ceiba.sqjl.SqjlCjwtNrBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>Xxlm</display-name>
<ejb-name>Xxlm</ejb-name>
<home>com.foresee.ceiba.xxfb.XxlmHome</home>
<remote>com.foresee.ceiba.xxfb.Xxlm</remote>
<ejb-class>com.foresee.ceiba.xxfb.XxlmBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>Xxnr</display-name>
<ejb-name>Xxnr</ejb-name>
<home>com.foresee.ceiba.xxfb.XxnrHome</home>
<remote>com.foresee.ceiba.xxfb.Xxnr</remote>
<ejb-class>com.foresee.ceiba.xxfb.XxnrBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>ZCDJ</display-name>
<ejb-name>ZCDJ</ejb-name>
<home>com.foresee.ceiba.swdj.zc.ZCDJHome</home>
<remote>com.foresee.ceiba.swdj.zc.ZCDJ</remote>
<ejb-class>com.foresee.ceiba.swdj.zc.ZCDJBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>Bblm</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>Bbnr</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>Fjxx</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>Yhzxx</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>GsbsProcess</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>BGDJ</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>PersonalRegister</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>ProjectRegister</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>SqjlCjwtLm</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>SqjlCjwtNr</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>Xxlm</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>Xxnr</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>ZCDJ</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>

How to edit deployment descriptor in weblogic 9.0?

Hi ,
I need to edit the values of certain environment variables mentioned in the deployment descriptor of a ejb module.
In weblogic 7,its a straight forward method in which we have the option to edit the deployment descriptor in weblogic console.
But I'm not sure how the same can be done in weblogic 9.0.
Please guide me..!!! its urgent...
Thanks,
Smita

If you want to edit the actual deployment descriptor (ie as a developer) than using any text editor or using an IDE like WebLogic Workshop/Eclipse etc would be the way to go.
If you're trying to change values in an already deployed application, then configuration and tunables can be changed in the admin console. These write the changes to a separate file called a deployment plan. It allows you to change performance and environment settings without disturbing the original EAR file.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

EJB references in deployment descriptors and weblogic heuristic on resolving links

There are two different ways to lookup home interfaces using JNDI.
1. Query JNDI tree at runtime using some initial context.
2. Use <ejb-ref> in deployment descriptor for all the refrenced EJBs and then
use initCtxt.lookup(java:comp/env/BeanHomeName).
The second approach is recommended as most of the EJB vendors resolve these referenced
EJBs at deployment time and it becomes much faster as compare to lookup in JNDI
as EJB refrences or links can bypass querying the JNDI.
Does anyone know if Weblogic (5.1 sp9 or higher) resolves these links at deployment
time or not?

Hi Sami,
Run your question by the folks in the EJB newsgroup and see if they can
offer some assistance:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=xover&group=weblogic.developer.interest.ejb
Thanks,
Bruce
sami titi wrote:
>
Bruce,
Thanks for your prompt reply. We have resorted to using a startup servlet much
like we do in CA. However, we're still faced with the second issue which is related
to not being able to lookup the EJB after it has been included in an EAR file
now. Is there any setting we're missing?
Thanks
Sami
Bruce Stephens <[email protected]> wrote:
Hello,
Please correct me if I'm not understanding your question, but you are
looking for an easy way to pass initialization parameters to your
webservice? This is not currently supported, however it is on the wish
list for the next major release.
The workaround is to use a handler or read your init params from a
file. If you backend is java class, then you can put file loading:
1. in the constructor
2. in init() method if you java class implement
javax.xml.rpc.server.ServiceLifecycle
Regards,
Bruce

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 AM

Atlassian 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).

Error 500 while deploying Servlets using Weblogic 5.1

          hi,
          i have followed all the intructions on how to run servlets in weblogic 5.1 server.
          till yesterday i have done nearly 10 servlets which worked perfectly. but today
          when i coded a new servlet and started running using internet explorer it gave
          "Error 500--Internal Server Error
          From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
          10.5.1 500 Internal Server Error
          The server encountered an unexpected condition which prevented it from fulfilling
          the request. "
          can u please give me the solution .
          regards,
          anitha


how this newly coded servlet is different from the other servlets?
          Http 500 errror means some "internal error" happened while processing your request.
          Do you see any error messages or stack trace on the server console?
          Kumar
          Anitha wrote:
          > hi,
          >
          > i have followed all the intructions on how to run servlets in weblogic 5.1 server.
          > till yesterday i have done nearly 10 servlets which worked perfectly. but today
          > when i coded a new servlet and started running using internet explorer it gave
          >
          > "Error 500--Internal Server Error
          >
          > From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
          >
          > 10.5.1 500 Internal Server Error
          >
          > The server encountered an unexpected condition which prevented it from fulfilling
          > the request. "
          >
          > can u please give me the solution .
          >
          > regards,
          > anitha
          >
          >
          >

Deployment Failed using Weblogic

Hello,
The following error message appears when deploy to Weblogic. I have tried undeploy
then re-deploy the application without luck. The EJB is not in any package. Could
anyone show me what I've done wrong? Thanks a million. John.
Unexpected Error
Connected to localhost:7001 Active Domain: mydomain Jan 23, 2003 11:05:41 AM EST
Exception
weblogic.management.ManagementException: New source location,
C:\bea\user_projects\mydomain\beaBmpTax.ear, cannot be deployed to configured
application, beaBmpTax.
Application source is at C:\bea\user_projects\mydomain.
at weblogic.management.deploy.DeployerRuntime.validatePath(DeployerRuntime.java:786)
at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:319)
at weblogic.management.deploy.DeployerRuntime.access$0(DeployerRuntime.java:282)
at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:947)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:941)
at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:279)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:717)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:699)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:921)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
at $Proxy50.activate(Unknown Source)
at weblogic.management.console.actions.mbean.ConfigureAppWizardAction.commit(ConfigureAppWizardAction.java:248)
at weblogic.management.console.actions.mbean.ConfigureAppWizardAction.perform(ConfigureAppWizardAction.java:100)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.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$ServletInvocationAction.run(ServletStubImpl.java:945)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:332)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5360)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3043)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2468)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)

The server is complaining because you have an application named
beaBmpTax with some path. Then you've asked it to redeploy that
application, but with a different path.
If that doesn't clear it up, can you show me the application entries
from your config.xml?
-- Rob
John Smith wrote:
Hello,
The following error message appears when deploy to Weblogic. I have tried undeploy
then re-deploy the application without luck. The EJB is not in any package. Could
anyone show me what I've done wrong? Thanks a million. John.
Unexpected Error
Connected to localhost:7001 Active Domain: mydomain Jan 23, 2003 11:05:41 AM EST
Exception
weblogic.management.ManagementException: New source location,
C:\bea\user_projects\mydomain\beaBmpTax.ear, cannot be deployed to configured
application, beaBmpTax.
Application source is at C:\bea\user_projects\mydomain.
at weblogic.management.deploy.DeployerRuntime.validatePath(DeployerRuntime.java:786)
at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:319)
at weblogic.management.deploy.DeployerRuntime.access$0(DeployerRuntime.java:282)
at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:947)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:941)
at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:279)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:717)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:699)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:921)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
at $Proxy50.activate(Unknown Source)
at weblogic.management.console.actions.mbean.ConfigureAppWizardAction.commit(ConfigureAppWizardAction.java:248)
at weblogic.management.console.actions.mbean.ConfigureAppWizardAction.perform(ConfigureAppWizardAction.java:100)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.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$ServletInvocationAction.run(ServletStubImpl.java:945)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:332)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5360)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:721)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3043)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2468)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)

Deploying Jira using Weblogic 10.3 - Can't access new jira server

I was able to install WL 10.3, create a new domain named, 'atlassian', and add a new server to that domain named 'jira'. I add a datasource to 'jira' then deployed jira via a .war to the new server. By default the new domains AdminServer comes up and is accessable via port 7001/console, but the managed server, jira requied that I start nodemanger before it would allow me to start 'jira' sever. Now, jira sever, datasource and app are all running, but I can not access via URL.
The Jira Server is running on port 7011, but I get a 404 when attempting to connect to http:\\<myserver>:7011 or http:\\<myserver>:7011\jira. Any ideas here are appreciated since Jira is not certified on 10.3, they aren't much help.
Edited by: user9952700 on Mar 25, 2009 3:54 PM

Atlassian 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).

How to use weblogic.DDconverter Tool to upgrade Deployment Descriptors.

Hi,
I want to know how to use weblogic.DDconverter Tool to upgrade Deployment Descriptors using EAR of previous verisons(JDK and weblogic).
Regards,
Neeraj

Looks like the protocol is not correct (Unable to connect to 'http://localhost:7001': Destination unreachable)
Could you try the t3 protocol, for example,
java weblogic.Deployer -adminurl t3://localhost:7001 -username weblogic -password welcome1 -listapps

Practical to modify app parameters for deployed app (using Builder, perhaps)?

I see that it's very convenient to deploy a WAR file to WebLogic using WebLogic
Builder. It's also easy to edit the init parameters of a WAR file and redeploy
it.
I'm wondering, however, how practical it will be to dynamically edit application
parameters and redeploy in a production environment.
For instance, if I'm in my development environment, I will definitely have a WAR
(exploded or not) in my build environment that I can edit and deploy.
In production, however, we don't necessarily have the original WAR that was referenced
in the deployment, we have what was installed into WebLogic. Is it practical to
run WebLogic Builder on an already installed WAR file, edit it, and then redeploy
it? Would we instead have to store the WAR file to be deployed into a "staging"
environment before it is actually deployed? Any changes made to the WAR by the
administrator would be made to the staged WAR file and then redeployed. I guess
the "staging" filesystem would have to be reachable by the host where the administrator
runs WebLogic Builder.

"David M. Karr" <[email protected]> wrote in message
news:[email protected]...
>
"Sanjeev Chopra" <[email protected]> wrote:
"David M. Karr" <[email protected]> wrote in message
news:[email protected]...
I see that it's very convenient to deploy a WAR file to WebLogic usingWebLogic
Builder. It's also easy to edit the init parameters of a WAR file andredeploy
it.do you mean servlet init-param ?Both that and context init parameters.
I'm wondering, however, how practical it will be to dynamically editapplication
parameters and redeploy in a production environment.
For instance, if I'm in my development environment, I will definitelyhave
a WAR
(exploded or not) in my build environment that I can edit and deploy.
In production, however, we don't necessarily have the original WARthat
was referenced
in the deployment, we have what was installed into WebLogic. Is itpractical to
run WebLogic Builder on an already installed WAR file, edit it, andthen
redeploy
it?
Would we instead have to store the WAR file to be deployed into a
"staging"
environment before it is actually deployed?If the .war is deployed with staging mode as "stage", you should have
no
problem modifying the master copy and then doing a redeploy. The redeploy
operation will take care of copying the modified .war to the staging
areas
of all targets.Ok, but what I'm wondering is if this "master copy" that you refer to isin a
location that we set up outside of WebLogic, or whether that is where thedeployed
WAR gets stored. I'm trying to determine whether WARs that get deployedwill first
have to be stored outside of WebLogic in a directory that we control,which will
be on a filesystem that will be accessible by the administrator runningWebLogic
Builder (using Samba, perhaps).The 'master copy' is the path specified to the deployment tool (deployer,
admin console) when you deployed the app to WLS. So yes, if thats not
available to the user running builder, they have to keep a copy, modify it
and make it available to the admin.

Weblogic Builder in 10.3

I just upgraded from WLS 8.1 to 10.3. I don't see the Weblogic Builder feature in it. Can someone tell me how to modify/add properties to a war file (like adding context root etc.) in 10.3 that was done using Weblogic Builder in 8.1?
Thanks
Jacob

Hi Jacob,
WLBuilder (WebLogic Builder tool) is not available anymore. After WLS9.x onwards.
But if you want to generate the Deployment descriptors for your Applications then you can use the following then:
For WEB Applications:
java weblogic.marathon.ddinit.WebInit <module>
For Enterprise Applications:
java weblogic.marathon.ddinit.EarInit <module>
As described in : http://download.oracle.com/docs/cd/E11035_01/wls100/admin_ref/utils.html#wp1201812
<h3><font color=maroon>PREWORK before running the above utility</font></h3>
Make Sure to set the Environment in your Shell/Commnd prompt before running the above commands:
Step1). Open a Shell Prompt.
Step2). echo $CLASSPATH … Just to see what is the current CLASSPATH value.
Step3). run the “setWLSEnv.sh” by adding two DOTs separated by a single space …..before the actual script like following : (use ‘cd’ command to move inside the <BEA_HOME>/wlserver_10.3/server/bin) then run the following command….
. ./setWLSEnv.sh
<b><font color=red>Note:</font></b> The first DOT represents that set the Environment in the current Shell, AND the second ./ represents execute the script from the current directory. For WINDOWS just run "setWLSEnv.cmd"
Step4). Verify that the Classpath is Set properly or not:
echo $CLASSPATH
Step5). Now u can run your command
Thanks
Jay SenSharma
http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)

WebLogic Builder remote-client-timeout

Just wondering if anyone has encountered this before.
After using WebLogic Builder to make and save changes to an EAR file the weblogic-ejb-jar.xml file is updated to include the remote-client-timeout tag. This tag causes warning messages in the weblogic console.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>HelloWorldEJB</ejb-name>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>test.HelloWorldHome</jndi-name>
<remote-client-timeout>0</remote-client-timeout>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Warning Messages
<Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout specifies a rmi level timeout in seconds for remote clients that call the home and remote methods of the ejb. The method call(s) timeout on the client side after the specified number of seconds. The server will continue to process the request(s) and may change the state. The rmi level timeout shall be set by the container only for non-transactional methods (i.e, method with tx-attributes of Never or Not-Supported). Please ensure that the parameter is used only for methods that are idempotent in nature.>

I think the tool sets the default value for this flag. The default value
should not have any effect. However, I would expect the tool (weblogic
builder) not to insert this element in the descriptor.
More details on this setting can be found here -
http://e-docs.bea.com/wls/docs81/rmi/rmi_api.html#rmi_timeout
--Sathish
<Colin Yeung> wrote in message news:[email protected]..
Just wondering if anyone has encountered this before.
After using WebLogic Builder to make and save changes to an EAR file the
weblogic-ejb-jar.xml file is updated to include the remote-client-timeout
tag. This tag causes warning messages in the weblogic console.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>HelloWorldEJB</ejb-name>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>test.HelloWorldHome</jndi-name>
<remote-client-timeout>0</remote-client-timeout>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Warning Messages
<Nov 2, 2005 4:46:22 PM PST> <Warning> <EJB> <BEA-014009> <Warning: EJB
HelloWorldEJB, has the remote-client-timeout set to 0 secs. This timeout
specifies a rmi level timeout in seconds for remote clients that call the
home and remote methods of the ejb. The method call(s) timeout on the
client side after the specified number of seconds. The server will
continue to process the request(s) and may change the state. The rmi level
timeout shall be set by the container only for non-transactional methods
(i.e,
method with tx-attributes of Never or Not-Supported). Please ensure that
the parameter is used only for methods that are idempotent in nature.>

How to execute a batch file on different remote server using TFS Build

I have a build server and have 2 web servers. I am deploying using TFS Builds. Now, I have a requirement to execute a batch file which is kept on these 2 web servers. i.e. C:\MyBatch\CreateMe.bat
After my build is successful, I need to execute this batch from the build server.
Note, I cannot make any shared folder.

Hi Sameer,
Thanks for your post.
What’s the version of your TFS?
How do you deploy solution using TFS Build, run MSBuild deploy command or using Release Management?
That C:\MyBatch\CreateMe.bat file stay on your two web server machines separately?
If you want execute this bat file on your two web server machines separately using build process template, you need configure your web server machine as build agent, then add the InvokeProcess activity in build process template to run the bat file on build
agent machine after build, please refer to Hari’s answer reply in this post:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/b8bcb19f-1296-441c-8356-e701b949445a/tfs-2010-how-to-execute-a-batch-file-after-build?forum=tfsbuild.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error in Sun XML schema for servlet2.4 deployment descriptor?

Hi,
I'm including the new XML schema for version 2.4 of the servlet standard in my web.xml deployment descriptor, using http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
When I try to save the XML file, XMLSpy reports an error in the schema file itself: "Undefined schema component 'base' encountered - simpleContext can not have a base that is a complexType with complexContent"
This error is on line 744, and is caused by the snippet:
<xsd:simpleContent>
<xsd:extension base="j2ee:nonEmptyStringType"/>
</xsd:simpleContent>
Can anyone explain why I'm getting a validation failure on this schema? Surely someone else must have experienced the same thing, but I can't track down any reference to it anywhere. Help!

XMLSpy is known to be flawed. From my own experience of implementing
validators and data-binding tools, and from my experience of working in the
W3C Schema working group, I can tell you that there are countless cases
where XMLSpy violates the schema specification.
I checked the corresponding part of the schema, but it looks correct to me.
So I suspect that this is another bug in XMLSpy.
Try Xerces. That's probably the best in terms of conformance to the spec.

EJB deployment descriptors in clustered environment

          I was wondering how EJB deployment descriptor settings work in a clustered environment. Are the deployment descriptors per WebLogic instance they are deployed in or the entire clustered environment? For example, if my descriptor for a stateless session ejb has max-beans-in-free-pool set to 5 and I deploy this stateless ejb in 4 WebLogic instances of one cluster, does this mean that there will be a max of 5 instance of this bean in the free pool for the entire cluster or will there be a max of 20 (5 per WebLogic instance and 4 WebLogic instances in the cluster) instances of this bean for the entire cluster?
          Thanks,
          Bryan


Those settings are per server instance.
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com
          +1.617.623.5782
          WebLogic Consulting Available
          "Bryan Dixon" <[email protected]> wrote in message
          news:3a6b51a0$[email protected]..
          >
          > I was wondering how EJB deployment descriptor settings work in a clustered
          environment. Are the deployment descriptors per WebLogic instance they are
          deployed in or the entire clustered environment? For example, if my
          descriptor for a stateless session ejb has max-beans-in-free-pool set to 5
          and I deploy this stateless ejb in 4 WebLogic instances of one cluster, does
          this mean that there will be a max of 5 instance of this bean in the free
          pool for the entire cluster or will there be a max of 20 (5 per WebLogic
          instance and 4 WebLogic instances in the cluster) instances of this bean for
          the entire cluster?
          >
          > Thanks,
          > Bryan
          >

Deployment descriptor Using weblogic Builder

Similar Messages

Maybe you are looking for