Deployment of Web Application when the managed Server is down .....

Part of our installation, we want to deploy our web application on to a managed server.
So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
Can anyone help to deploy web application on to a managed server when the managed server is down ?
Thanks,
Selva-
[att1.html]

This is currently being fixed in 7.0 line, contact [email protected] and reference
CR110687
Cheers
mbg
"Selvamohan Neethiraj" <[email protected]> wrote in message news:[email protected]..
Part of our installation, we want to deploy our web application on to a managed server.
So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
Can anyone help to deploy web application on to a managed server when the managed server is down ?
Thanks,
Selva-
[att1.html]

Similar Messages

Problem: Deploy a web app from a managed server - Can someone answer: Is this a bug?!

We're running 6.0sp2 on both AIX and RedHat. Deploying or redeploying
a web app to the managed server fails, works fine on the Admin server.
War's work fine in the 'applications' dir. The browser fails with a
404 on the managed server, with the following error in the log:
####<Aug 9, 2001 4:58:45 PM GMT> <Error> <J2EE> <szuinet5> <ect2>
<ExecuteThread: '11'
for queue: 'default'> <system> <> <160001> <Error deploying application
DefaultWebApp
ect2: Cannot deploy WebAppServletContext(4320491,DefaultWebAppect2) on
ect2 because
WebAppServletContext(2930053,DefaultWebApp_ect2) is already registered
for path >
Are we missing the point here? Or, is this a known bug? Also, we are
not in a position to jump onto v6.1 at this time.
Thanks in advance.

Hi,
Yes..it's a bug. I had the same problem and it has been reported to support
but no indication if it's fixed.
Rgds,
E-Wan
ppower wrote:
We're running 6.0sp2 on both AIX and RedHat. Deploying or redeploying
a web app to the managed server fails, works fine on the Admin server.
War's work fine in the 'applications' dir. The browser fails with a
404 on the managed server, with the following error in the log:
####<Aug 9, 2001 4:58:45 PM GMT> <Error> <J2EE> <szuinet5> <ect2>
<ExecuteThread: '11'
for queue: 'default'> <system> <> <160001> <Error deploying application
DefaultWebApp
ect2: Cannot deploy WebAppServletContext(4320491,DefaultWebAppect2) on
ect2 because
WebAppServletContext(2930053,DefaultWebApp_ect2) is already registered
for path >
Are we missing the point here? Or, is this a known bug? Also, we are
not in a position to jump onto v6.1 at this time.
Thanks in advance.

OSB dashboard Service Health tab broken when a managed server is down

I have shut down one of the managed servers in my three-member OSB 10.3.1 cluster to load test the reduced configuration, and that has broken the "service health" tab on the OSB console dashboard.
The problem is that with the mgd1 server shut down (the one the Singleton marker ear is deployed to, if that matters), in the OSB console's Dashboard everything in the "Service Health" tab is broken. I get the warning message "Unable to obtain metrics data from the server" at the top of the page whenever I go to the dashboard. I can't even look at the displays for the individual (mgd2, mgd3) servers that are running. I get the following error in the log when trying to access the service health for the services in the cluster, or even if I try to get the health of services in either of the two remaining cluster members individually:
+####<Apr 8, 2010 11:00:02 PM EDT> <Error> <AlertLog> <nj09mhm0033.edmz.mcgraw-hill.com> <SS_ESB_Admin> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1270782002573> <BEA-000000> <WLDFAccessRuntimeMBean is not available for server SS_ESB_mgd1>+
Also, as part of the load test procedure, I need to collect performance stats from the proxy service pipeline and the business service. To do this, I've written JMX code called out of soapUI scripts to reset the stats on these services before the run, then collect the stats after the run ends; the code connects to the admin server. This too is broken when the mgd1 server is shut down.
I get the error below when trying to collect the cluster stats from the Admin server from the JMX code. This error is fatal, and no statistics come back from the rest of the cluster either. (you can ignore all the groovy stuff in the stack trace, it's the nested Exceptions that are more interesting).
Does anyone have an idea about what's going on, and how I fix this? I would have thought the DomainService Runtime MBean would be able to catch and handle an Exception like this if one of the managed servers were down, and collect the stats from the available part of the cluster, but it looks like that's not the case.
TIA for any help.
/Steve Elkind
java.lang.reflect.UndeclaredThrowableException
at $Proxy6.getBusinessServiceStatistics(Unknown Source)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getAndResetStatsForMonitoredBizService(ServiceStatsRetriever.java:193)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getStatsForMonitoredBizService(ServiceStatsRetriever.java:142)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$GetAndResetStatisticsTask.run(ServiceStatsRetriever.java:652)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$GetAndResetStatisticsTask.getStats(ServiceStatsRetriever.java:619)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getStats(ServiceStatsRetriever.java:779)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$getStats.call(Unknown Source)
at Script1.sleepGetStats(Script1.groovy:75)
at Script1$sleepGetStats.callCurrent(Unknown Source)
at Script1.runBenchMarkTest(Script1.groovy:104)
at Script1$runBenchMarkTest.callCurrent(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:44)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:143)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:163)
at Script1.run(Script1.groovy:152)
at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:93)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTest.runSetupScript(WsdlLoadTest.java:915)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTestRunner.start(WsdlLoadTestRunner.java:102)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTest.run(WsdlLoadTest.java:418)
at com.eviware.soapui.impl.wsdl.panels.loadtest.WsdlLoadTestDesktopPanel$RunLoadTestAction.actionPerformed(WsdlLoadTestDesktopPanel.java:424)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:272)
at java.awt.Component.processMouseEvent(Component.java:6263)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6028)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4630)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.lang.reflect.InvocationTargetException
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:597)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$ServiceDomainMBeanInvocationHandler.invoke(ServiceStatsRetriever.java:567)
... 46 more
Caused by: com.bea.wli.monitoring.MonitoringException: [Monitoring Runtime:473057]Failed to get statistics for services due to java.rmi.UnknownHostException: Could not discover administration URL for server 'SS_ESB_mgd1'
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsForServices(ServiceDomainMBeanImpl.java:967)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getServiceStatistics(ServiceDomainMBeanImpl.java:802)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getBusinessServiceStatistics(ServiceDomainMBeanImpl.java:366)
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:597)
at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:437)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:255)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:445)
at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:445)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:443)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10$1.run(AuthenticatedSubjectInterceptor.java:582)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10.run(AuthenticatedSubjectInterceptor.java:580)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.invoke(AuthenticatedSubjectInterceptor.java:573)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:307)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.rmi.UnknownHostException: Could not discover administration URL for server 'SS_ESB_mgd1'
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:175)
at com.bea.wli.sb.util.server.AggregatorUtils.getAggregatorServerAdminURL(AggregatorUtils.java:105)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsRetrieverMBean(ServiceDomainMBeanImpl.java:2036)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsForServices(ServiceDomainMBeanImpl.java:933)
... 35 more
java.lang.reflect.UndeclaredThrowableException
at $Proxy6.getBusinessServiceStatistics(Unknown Source)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getAndResetStatsForMonitoredBizService(ServiceStatsRetriever.java:193)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getStatsForMonitoredBizService(ServiceStatsRetriever.java:142)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$GetAndResetStatisticsTask.run(ServiceStatsRetriever.java:652)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$GetAndResetStatisticsTask.getStats(ServiceStatsRetriever.java:619)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever.getStats(ServiceStatsRetriever.java:779)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$getStats.call(Unknown Source)
at Script1.sleepGetStats(Script1.groovy:75)
at Script1$sleepGetStats.callCurrent(Unknown Source)
at Script1.runBenchMarkTest(Script1.groovy:104)
at Script1$runBenchMarkTest.callCurrent(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:44)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:143)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:163)
at Script1.run(Script1.groovy:152)
at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:93)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTest.runSetupScript(WsdlLoadTest.java:915)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTestRunner.start(WsdlLoadTestRunner.java:102)
at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTest.run(WsdlLoadTest.java:418)
at com.eviware.soapui.impl.wsdl.panels.loadtest.WsdlLoadTestDesktopPanel$RunLoadTestAction.actionPerformed(WsdlLoadTestDesktopPanel.java:424)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:272)
at java.awt.Component.processMouseEvent(Component.java:6263)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
at java.awt.Component.processEvent(Component.java:6028)
at java.awt.Container.processEvent(Container.java:2041)
at java.awt.Component.dispatchEventImpl(Component.java:4630)
at java.awt.Container.dispatchEventImpl(Container.java:2099)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
at java.awt.Container.dispatchEventImpl(Container.java:2085)
at java.awt.Window.dispatchEventImpl(Window.java:2478)
at java.awt.Component.dispatchEvent(Component.java:4460)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.lang.reflect.InvocationTargetException
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:597)
at com.mgh.im.esb.jmxutils.ServiceStatsRetriever$ServiceDomainMBeanInvocationHandler.invoke(ServiceStatsRetriever.java:567)
... 46 more
Caused by: com.bea.wli.monitoring.MonitoringException: [Monitoring Runtime:473057]Failed to get statistics for services due to java.rmi.UnknownHostException: Could not discover administration URL for server 'SS_ESB_mgd1'
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsForServices(ServiceDomainMBeanImpl.java:967)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getServiceStatistics(ServiceDomainMBeanImpl.java:802)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getBusinessServiceStatistics(ServiceDomainMBeanImpl.java:366)
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:597)
at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:437)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:255)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:445)
at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:65)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:447)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:445)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:443)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10$1.run(AuthenticatedSubjectInterceptor.java:582)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10.run(AuthenticatedSubjectInterceptor.java:580)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.invoke(AuthenticatedSubjectInterceptor.java:573)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:307)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426)
at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1366)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.rmi.UnknownHostException: Could not discover administration URL for server 'SS_ESB_mgd1'
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:175)
at com.bea.wli.sb.util.server.AggregatorUtils.getAggregatorServerAdminURL(AggregatorUtils.java:105)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsRetrieverMBean(ServiceDomainMBeanImpl.java:2036)
at com.bea.wli.sb.management.monitoring.ServiceDomainMBeanImpl.getStatisticsForServices(ServiceDomainMBeanImpl.java:933)
... 35 more

As a follow-up, does anyone know if I can simply retarget the two OSB Singleton Marker Apps (shown below from config.xml) to another server instance to fix this and any other Singleton issues (e.g., flie transport, ftp, and email pollers), or is it more involved than that?
<app-deployment>
<name>ALSB Cluster Singleton Marker Application</name>
<target>SS_ESB_mgd1</target>
<module-type>ear</module-type>
<source-path>/opt/bea/osb1031/osb_10.3/lib/common/clustersingletonmarker.ear</source-path>
<deployment-order>80</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<app-deployment>
<name>ALSB Domain Singleton Marker Application</name>
<target>SS_ESB_mgd1</target>
<module-type>ear</module-type>
<source-path>/opt/bea/osb1031/osb_10.3/lib/common/domainsingletonmarker.ear</source-path>
<deployment-order>85</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>

Deploying a web application on Sun One app server 7

Hi,
I am not able to deploy a web application on sun one server using Sun java studio.
I have created Jsp, Servlet, Session bean and entity bean.
When I am creating a web_module in the directory where JSP are kept, it is giving me error "directory is already mounted.
I have already created EJB modules for both the Session and entity bean.
Can some one tell me the cause / solution of this problem.

Hi Amol,
Thank you very much for replying my question. The contents in my application.xml are:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>testwsapp</display-name>
<description>J2EE Application testwsapp</description>
<module>
<web>
<web-uri>testws_War.war</web-uri>
<context-root>testws</context-root>
</web>
<alt-dd>testws_War.xml</alt-dd>
</module>
</application>
The contents in jaxrpc-ri-runtime.xml are:
<?xml version="1.0" encoding="UTF-8"?>
<endpoints xmlns='http://java.sun.com/xml/ns/jax-rpc/ri/runtime' version='1.0'>
<endpoint
name='testws'
interface='contactws.testwsGenServer.testwsRPC'
implementation='contactws.testwsGenServer.testwsRPCBean'
tie='contactws.testwsGenServer.testwsRPC_Tie'
model='null'
wsdl='/WEB-INF/testws.wsdl'
service='{urn:testws/wsdl}Testws'
port='{urn:testws/wsdl}testwsRPCPort'
urlpattern='/testws'
</endpoint></endpoints>
I tried to access and check the web service using:
http://servername:port/testws/testws
The first testws is contextroot named and the second testws is url pattern, which was exactly like what you mentioned but I got "404 Not Found" error.
By the way, using the same ear to deploy to Windows Sun ONE App. Server 7 env. and then using the same url, I can access the web service. I am wondering if there is any special for deploying Web Service on Unix Sun ONE app. Server 7 env. or I missed something?
I hope I can hear from you soon.
Thank you again,
Jackie

How to Deploy a web Application

Can Any one tell me the right procedure to Deploy A web Application on the server.
I have made the application using Html,Servlets,JSP,Java beans,web.xml
now I have lots of html,java class file
At this moment I have put all the classes file in \WEB-INF\CLASSES DIRECTORY, and the HTML file And the JSP in \WEB-INF directory
But it make the whole classes and WEB-INF directory populated with files.
Now Should I make a jar or war file and put on the
Can Anyone tell me the Correct method of deployment

http://ant.apache.org/manual/CoreTasks/war.html

Deploy JRC web application on Sun Solaris

Hi everyone,How can i deploy my web application including the JRC on a Sun solaris OS?.Can anyone help me? Thanks

This is pretty easy.1. Get a Java Application Server running on Sun Solaris2. Create a WAR file containing the JRC. (WAR files for Solaris are no different than windows)<a href="http://technicalsupport.businessobjects.com/KanisaSupportSite/search.do?cmd=displayKC&docType=kc&externalId=c2014756&sliceId=&dialogID=14310478&stateId=1%200%2014312298">CLICK HERE for instructions to make a war file</a> 3. Deploy that WAR file to the App server on the Sun Solaris Box. Rob Horne <a href="/blog/10">Rob's blog - http://diamond.businessobjects.com/blog/10</a>

Health Service Heartbeat Failure Alert for Generated when one Management Server Down,

Hi,
I have Two Management Server, every one manage about 100 server, when one Management Server goes down unexpected, I receive 100 Alert for 100 Server Health Service Heartbeat Failure.
My Question, why when the Management Server down, it send that all Managed agent Health Service Heartbeat Failure?
Is there a way to change this?

SCOM 2012 agent will autofailover when primary server is down. You can check the failover management server by using the following powershell cmdlet:
#Verify Failover for Agents reporting to MS1
$Agents = Get-SCOMAgent | where {$_.PrimaryManagementServerName -eq 'MS1.DOMAIN.COM'}
$Agents | sort | foreach {
Write-Host "";
"Agent :: " + $_.Name;
"--Primary MS :: " + ($_.GetPrimaryManagementServer()).ComputerName;
$failoverServers = $_.getFailoverManagementServers();
foreach ($managementServer in $failoverServers) {
"--Failover MS :: " + ($managementServer.ComputerName);
Write-Host "";
http://www.systemcentercentral.com/how-does-the-failover-process-work-in-opsmgr-2012-scom-sysctr/

How can a JMS Listener Notified get when a Topic Server Goes Down?

I'm in the process of looking into pub/sub model for a centeralized data source where vertical applications subscribe to a topic to get updates on person demographic information.
          I was playing with the JMS topic examples and noticed that when I have a Durable Subscriber listener (java main) and the topic Server goes down. It never gets notified. When I restart the Topic server and send msgs to the topic, the Durable Listener doesn't get them.
          Once I restart the Durable Listener (java main), it receives all the messages that were pending.
          I implemented the ExceptionListener and it never gets a shutdown msg either. I shutdown the Topic server via Ctrl-C, Graceful Shutdown and Forced Shutdown.
          Is there a way for the client listener to determine when the Topic Server went down, came backup, and restore the connection to it automatically? Or do we have to implement some type of ping mechanism on the client listener and re-create the connection ourselves?
          Thanks. Later...
          - Wayne
          Edited by wlau1000 at 03/07/2007 8:34 AM

Hi Wayne,
          I think the exception listener should have fired. Some comments/questions:
          - Does your app call "connection.setExceptionListener" in addition to implementing ExceptionListener?
          - Which version and maintenance/service pack are you using?
          - Is the client using the wl* "thin" client jars or the "thick" client jar?
          - Version 9.2 provides an automatic reconnection capability for consumers. This behavior isn't enabled by default due to natural side effects that some apps might not be prepared to handle (needles to say, I recommend reading the doc thoroughly).
          http://edocs.bea.com/wls/docs92/jms/recover.html#wp1320125
          Tom

Problem when we created the managed server to configure different ports.

I am trying to configure different ports for admin console and my communication service as we can’t share admin port to the outside world.
So that only admin can access admin console using admin port.
And out side clients can access my webapplication using different port.
For this i have created the managed server in weblogic.and I deployed the application on managed server.
Now admin server is running on 8001 port and my Communication Service application is running on 7001 port.
But when I tried to configure MBeans related to myCommunicationServiceApplication those were disapper on admin console. And the other wlng services are appearing on admin console.
1. Since my application deployed on managed server MBeans registration happened from myapplication hence it’s disappear on admin console.
Now If I want to configure Mbeans (related to my communication service) how can I configure it?
2. My communication service using configurationStore module and other wlng services.
When I tried to start my application on managed server I got the below error:
<Apr 28, 2009 12:22:44 PM IST> <Error> <Deployer> <BEA-149231> <dscp11166.TechMahindra.com> <Unable to set the activation state to true for the application 'wlng_nt_qualcomm_active_mediation [Version=1.0]'.
com.bea.wlcp.wlng.api.storage.configuration.ConfigurationException: Configuration store module is not available.
3. I tried to target all wlngResources to manged server by editing config.xml file.
Then all wlng services disappears on admin console. If this is the case how can I configure container/account services on wlng?
I have created the Basicweblogic domain.
Below is the config.xml for reference.
"QualcommServer" is managed server name.
Can any one please suggest me how to configure this kind of scenarios?
<server>
<name>AdminServer</name>
<machine>new_Machine_1</machine>
<listen-port>8001</listen-port>
<default-iiop-user>weblogic</default-iiop-user>
<default-iiop-password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</default-iiop-password-encrypted>
<listen-address>localhost</listen-address>
</server>
<server>
<name>QualcommServer</name>
<machine>new_Machine_1</machine>
<listen-address>localhost</listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<java-home>C:\Program Files\Java\jdk1.6.0</java-home>
<class-path>C:\bea\wlng400\server\lib\weblogic.jar;C:\bea\wlng_pds400\lib\wlng\wlng.jar</class-path>
<bea-home>C:\bea</bea-home>
<username>weblogic</username>
<password-encrypted>{3DES}W8nBdoJPRZ8TkwcXwAZoxA==</password-encrypted>
</server-start>
</server>
<embedded-ldap>
<name>managedserver</name>
<credential-encrypted>{3DES}9q80YuFJueVVJxoWduJA1OGhbqk14EpgQWWyTrzlmxo=</credential-encrypted>
</embedded-ldap>
<configuration-version>10.0.1.0</configuration-version>
<app-deployment>
<name>wlng_nt_session#4.0</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>C:\bea\wlng400/applications/wlng_nt_session.ear</source-path>
<security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
<name>interceptors</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>C:\bea\wlng400/applications/interceptors.ear</source-path>
<security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
<name>wlng_prm</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>C:\bea\wlng400/applications/wlng_prm.ear</source-path>
<security-dd-model>CustomRolesAndPolicies</security-dd-model>
</app-deployment>
<app-deployment>
<name>wlng_nt_qualcomm_active_mediation#1.0</name>
<target>QualcommServer</target>
<module-type>ear</module-type>
<source-path>servers\AdminServer\upload\wlng_nt_qualcomm_active_mediation.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
</app-deployment>
<machine>
<name>new_Machine_1</name>
<node-manager>
<name>new_Machine_1</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
<jms-server>
<name>JMSServer-AdminServer</name>
<target>AdminServer</target>
</jms-server>
<jms-system-resource>
<name>WLNGJMSResource</name>
<target>QualcommServer</target>
<descriptor-file-name>jms/wlng-jms.xml</descriptor-file-name>
</jms-system-resource>
<custom-resource>
<name>networktier</name>
<target>AdminServer</target>
<descriptor-file-name>custom/nt.xml</descriptor-file-name>
<resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngTierResource</resource-class>
<descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngTierBean</descriptor-bean-class>
</custom-resource>
<custom-resource>
<name>wlng-edr</name>
<target>AdminServer</target>
<descriptor-file-name>custom/wlng-edr.xml</descriptor-file-name>
<resource-class>com.bea.wlcp.wlng.management.descriptor.resource.WlngEdrResource</resource-class>
<descriptor-bean-class>com.bea.wlcp.wlng.management.descriptor.bean.WlngEdrBean</descriptor-bean-class>
</custom-resource>
<admin-server-name>AdminServer</admin-server-name>
<jdbc-system-resource>
<name>wlng.datasource</name>
<target>QualcommServer</target>
<descriptor-file-name>jdbc/wlng-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
<jdbc-system-resource>
<name>wlng.localTX.datasource</name>
<target>QualcommServer</target>
<descriptor-file-name>jdbc/wlng-localTX-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
Thanks,
Srinu Babu P

Dear Nariharan,
Today I faced a simlar issue, and this SAP Note helped me fix it: 1966807 - Duplication of AET table records in change processing
In my case, cardinality of AET table was 1:1, and I was getting duplicate PARENT_ID every time when trying to create a subsequent service request for my activity.
Regards,
Andrew

Application unable to identify the managed server after restart

Hi
          I have a application deployed in a cluster in production environment which has two managed servers configured to it in separate machines. this application generates a wsdl file.
          now we are facing a strange problem as below.
          when one managed server crashes and goes down in some situation, the cluster is able to manage it.
          we have a class which does remote binding of objects.
          Even when we restart the second server it is not able to identify it.
          Edited by [email protected] at 04/18/2008 9:45 PM

Hi,
I tried starting the server from the console as well as from command prompt. Here I am giving the command below.
nohup ./startManagedWebLogic.sh bi_server1 t3://machineIP:portNo > bis1_startup.log &
But each time I got the same exception.
Korandla

Issue of deploying a fusion Web Application with integrated Weblogic server

Hi,
i'm using Jdev 11.1.1.3.0 to develop a fusion web application, with a model and ViewController Projects.
When i try to deploy this application with the integrated server, i have any issues.
The origin seems to be that it builds an application with 3 profiles. The model application is recognized and deployed as a webapp and not an ADF library as it should be..
[11:00:45 PM] Retrieving existing application information
[11:00:45 PM] Running dependency analysis...
[11:00:45 PM] Deploying 3 profiles...
[11:00:46 PM] Wrote Web Application Module to /home/david/.jdeveloper/system11.1.1.3.37.56.60/o.j2ee/drs/easygestionV2.0/ViewControllerWebApp.war
*[11:00:48 PM] Wrote Web Application Module to /home/david/.jdeveloper/system11.1.1.3.37.56.60/o.j2ee/drs/easygestionV2.0/ModelWebApp.war*
[11:00:48 PM] Wrote Enterprise Application Module to /home/david/.jdeveloper/system11.1.1.3.37.56.60/o.j2ee/drs/easygestionV2.0
[11:00:48 PM] Deploying Application...
<27 déc. 2010 23 h 00 CET> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application easygestionV2.0 is not versioned.>
<JpsDstCredential><setCredential> Impossible de migrer le dossier/la clé d'informations d'identification et de connexion ADF/anonymous#easygesprod. Raison : oracle.security.jps.service.credstore.CredentialAlreadyExistsException: JPS-01007: Les informations d'identification et de connexion avec la correspondance ADF et la clé anonymous#easygesprod existent déjà..
<TrinidadFilter><init>
java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory
 at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:725)
 at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:239)
 at oracle.adfinternal.view.faces.util.rich.ConverterValidatorRegistrationUtils.register(ConverterValidatorRegistrationUtils.java:36)
 at oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator.init(RegistrationConfigurator.java:79)
 at org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.init(GlobalConfiguratorImpl.java:400)
 at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.init(RegistrationFilter.java:53)
 at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.init(TrinidadFilterImpl.java:103)
 at org.apache.myfaces.trinidad.webapp.TrinidadFilter.init(TrinidadFilter.java:54)
 at weblogic.servlet.internal.FilterManager$FilterInitAction.run(FilterManager.java:332)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.FilterManager.loadFilter(FilterManager.java:98)
 at weblogic.servlet.internal.FilterManager.preloadFilters(FilterManager.java:59)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1867)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 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:41)
 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:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 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:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
How can i fix the model project to be deployed as an ADf library and not a webapp with the integrated weblogic server ? Because with me it doesn't do it by itself.
Thanks a lot for help

duplicate to Issue of deploying a fusion Web Application with integrated Weblogic server

Can I use the search engine and run a web application under the same iPlanet 6.0 virtual server?

I've got an iPlanet 6.0 SP2 virtual server with the search engine enabled, which was tested and working. I then deployed a web application to it (mapped to "/"), and the web application works fine but now the search functionality is completely broken. Browsing to /search results in a directory index being displayed. Is there some trick to getting the two working together? I tried shuffling NameTrans directives around, but can only get either the search or the web app working, not both.

Ok, I'm going to answer my own question now...
The issue has been resolved after some additional experimentation on my part. There were two causes for my problem:
1. The NameTrans directives in obj.conf are in the wrong order when Java and Search are enabled from the administration interface.
Here's the admin server generated obj.conf I started with initially, when the web application was working, but requests to the URI "/search" returning a 404 error:
<Object name="default">
NameTrans fn="NSServletNameTrans" name="servlet"
NameTrans fn="pfx2dir" from="/search-ui" dir="/usr/local/iWS-6.0/plugins/search/ui" name="es-internal"
NameTrans fn="pfx2dir" from="/mc-icons" dir="/usr/local/iWS-6.0/ns-icons" name="es-internal"
NameTrans fn="pfx2dir" from="/manual" dir="/usr/local/iWS-6.0/manual/https" name="es-internal"
NameTrans fn="es-search-nametrans" from="/search"
NameTrans fn="NSServletNameTrans" name="servlet"
NameTrans fn="document-root" root="$docroot"
</Object>
Here's my obj.conf now, which works perfectly:
<Object name="default">
NameTrans fn="pfx2dir" from="/search-ui" dir="/usr/local/iWS-6.0/plugins/search/ui" name="es-internal"
NameTrans fn="pfx2dir" from="/mc-icons" dir="/usr/local/iWS-6.0/ns-icons" name="es-internal"
NameTrans fn="pfx2dir" from="/manual" dir="/usr/local/iWS-6.0/manual/https" name="es-internal"
NameTrans fn="es-search-nametrans" from="/search"
NameTrans fn="NSServletNameTrans" name="servlet"
NameTrans fn="document-root" root="$docroot"
</Object>
The "servlet" NameTrans directive needs to go below all others which map a URI to a function or directory (but before "document-root"), or they break. This is consistent with the iPlanet documentation on NameTrans, but the admin server doesn't get it right!
2. The developer who wrote the web application uploaded a directory named "search" in the root of his application, which caused the server to display a directory index of "/search", instead of executing the search function. I believe this issue is covered in an iPlanet knowledge base article.

Problem with JMS migration when using Ctrl+C to stop the managed server in cluster

          Hi,
          I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
          uses JMS as a asynchrous communication. We have MDB which listens to these JMS
          messages.
          If something is being processed on Managed Server 1 and while the request is in
          process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
          After this, i go to admin console and migrate teh JTA and JMS. After this, i am
          expecting other running Managed Server should restart the incomplete transaction.
          But this is not happening. The Managed Serve2 doesn't process the requst.
          But when i restart teh MAnaged SErver 1 again, it takes up the same request and
          processes it.
          Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
          Please note that the same thing is working fine when i stop the server using Admin
          console(Normal shutdown OR forced shutdown).
          Any comments in this regards are apprecciated.
          Thanks,
          Naresh


          Hi,
          I am having a clustered weblogic application running on Weblogic 7.0 SP5. My application
          uses JMS as a asynchrous communication. We have MDB which listens to these JMS
          messages.
          If something is being processed on Managed Server 1 and while the request is in
          process, i am stopping the the MAnaged SErver 1 using Ctrl+C.
          After this, i go to admin console and migrate teh JTA and JMS. After this, i am
          expecting other running Managed Server should restart the incomplete transaction.
          But this is not happening. The Managed Serve2 doesn't process the requst.
          But when i restart teh MAnaged SErver 1 again, it takes up the same request and
          processes it.
          Is this a known problem with Weblogic that it doesn't support Ctlr+C case?
          Please note that the same thing is working fine when i stop the server using Admin
          console(Normal shutdown OR forced shutdown).
          Any comments in this regards are apprecciated.
          Thanks,
          Naresh

Deploying applications on the Admin Server

Hi there
I have recently moved to a new project team who have been deploying their applications to the admin server. They have been doing this for years with no issues.
I was always led to believe that the best practice was to keep the admin server completely separate. And I always deployed to a managed server (or a cluster of servers).
Does anyone know of any specific reasons why applications should not be deployed to an admin server.
Thanks in advance.

Typically, you want your managed servers to focus on applications, and the admin server to focus on management of the servers. If you have your heavy load applications deployed to the admin server, then that impacts both your applications and the management of those applications.
If your applications are deployed to the managed server, and not the admin server, you can recycle applications remotely just through the admin server console. If you need to restart the application, and it's running on the admin server, then you'll have to take additional steps to get the server running again.

Please help, how to guide the user to deploy a web application easily.

hello,
i have created an application which creates a new web application every time it is run. now i am writing the documentation of it and dont know which web server the client may have so i have to write / show to the user general steps that he should follow to deploy the web application after it has been created.
i have written that the user should deploy the web app by making the following entry into the server.xml file (for tomcat)
<Context path="/webappname" docBase="webapppath"></Context>
it is not compulsary that the user should place the web application in the webapps directory of the server hence the above webapppath is used.
now i want to indicate to him where and before / after which tag and under which host name etc the above line should be added in a manner that he is able to do it properly.
please anyone can help me how to do it.

i would like to know if there is any way without Java web start.
it has to be set manually.
i.e every user should make this entry in the server.xml so that the context is set.

Deployment of Web Application when the managed Server is down .....

Similar Messages

Maybe you are looking for