Online Deployment in Cluster
Hello,
we have currently set up a Netweaver application server cluster on SLES10. The cluster is setup like this:
Two physical servers.
1 WebDispatcher
1 SCS
1 JavaCentral Instance with SDM
3 Dialog Instances.
We wanted to know if the SDM provides an online deployment possibility, in which the WebDispatcher recognizes which dialog instance is not available due to current deployment.
Does there have to be something configured in the SDM or WebDispatcher?
We want to ensure if we deploy something during runtime that the server handles this appropriately without timeouts or errors.
Regards,
Kai
Hi Kai,
No the webdispatcher cannot be used by SDM to deploy software to other instances. The webdispatcher is used specifically to load balance HTTP, HTTPS and SMTP requests over different instances to one logical backend system.
This is not specific to SDM but the webdispatcher will poll the backend message server for specific information about the availability of all backend instances via the profile paraemeter wdisp/auto_refresh (default 120 seconds).
The information relayed from the message server includes the state of the instances. If the message server reports to the webdisp that a server is down it will be removed from the webdispatcher server pool.
Note: Dont set the wdisp/auto_refresh parameter too low as the webdispatcher uses this for receiving load balancing information as well as the state of the instances.
Hope this helps
Michael
Similar Messages
-
Hallo,
I have folloving problem with deploying SAPXITOOL SP14 L9.
When I started deploying there is a message that SAP WEB AS JAVA is currently stopped, but J2EE (dispatcher, server0 and SDM) is started. If SDM deploying part com.sap.aii.security.ws.proxy the SDM using online deploying.
Now there is a bad message:
Feb 24, 2006 8:23:49 AM Info: Software type of SDA: J2EE
Feb 24, 2006 8:23:49 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Feb 24, 2006 8:23:49 AM Info: Starting cluster instance processes.
Feb 24, 2006 8:23:49 AM Error: An error occured while starting a cluster instance.
Feb 24, 2006 8:23:49 AM Error: There is no control instance running in the cluster:
Name:JM_T1140765829632_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
Feb 24, 2006 8:23:49 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Feb 24, 2006 8:23:49 AM Error: Aborted: development component 'com.sap.aii.security.ws.proxy'/'sap.com'/'SAP AG'/'3.0.1420060214105340.0000':
SDM could not start the J2EE cluster on the host smbxi2db! The online deployment is terminated.
There is no control instance running in the cluster:
Name:JM_T1140765829632_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Feb 24, 2006 8:23:52 AM Error: An error occured while restoring the cluster instances states
Feb 24, 2006 8:23:52 AM Error: There is no control instance running in the cluster:
Name:JM_T1140765832130_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
Feb 24, 2006 8:23:52 AM Error: Received exception when restoring Engine state: There is no control instance running in the cluster:
Name:JM_T1140765832130_smbxi2db
Host:smbxi2db
State:5
Please check if there are running cluster instances.
Can you somebody help me to resolve this problem?
Thanks
Martin CapekPlease check if "smbxi2db" is the JAVA CI host . If not maintain correct host in secstore.
Configtool-> Secure Store -> admin/host/<SID> (JAVA CI host, Not DB host) -
WLS6sp2 Hot deployment in cluster does not work
I have two WLS6sp2 servers in cluster in two different machines. There is an EJB
deployed in the cluster that works fine. Now I go to the console and I undeploy
it: the servers show a message of "ejb undeployed". Now I activate the "deploy"
checkbox again: the following error appears:
weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested exception
is:
javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-aware
stub to a name that is currently bound to a replica-aware stub; remaining name
javax.naming.NameAlreadyBoundException: Can't rebind anything but a replica-aware
stub to a name that is currently bound to a replica-aware stub; remaining name
The object is obviously clusterable (it is a stateless EJB with "home-is-clusterable=true").
It has been deployed to the cluster target. When is working it is load balanced
between both servers. It deploys perfectly when starting up both servers, but
hot deployment does not work.
This works fine when only one server is up.
¿Is not possible to do hot deployment in cluster?
Hm, where are you seeing the javax.naming.NameAlreadyBoundException? In one of your managed
servers, in all of your managed server, or in your admin server?
If you see this in your admin server, then this means you got your admin joined in the cluster,
which is not good. Remove it from the cluster if this is so.
Gene
"David Agudo" <[email protected]> wrote in message news:[email protected]...
>
> Yes, target="mycluster".
>
> "Gene Chuang" <[email protected]> wrote:
> >Did you target the ejb to the cluster, or to each individual Node in
> >your cluster? There is a
> >difference...
> >
> >Gene
> >
> >"David Agudo" <[email protected]> wrote in message news:[email protected]...
> >>
> >> I have two WLS6sp2 servers in cluster in two different machines. There
> >is an EJB
> >> deployed in the cluster that works fine. Now I go to the console and
> >I undeploy
> >> it: the servers show a message of "ejb undeployed". Now I activate
> >the "deploy"
> >> checkbox again: the following error appears:
> >>
> >> weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB;
> >nested exception
> >> is:
> >> javax.naming.NameAlreadyBoundException: Can't rebind anything but a
> >replica-aware
> >> stub to a name that is currently bound to a replica-aware stub; remaining
> >name
> >> ''
> >> javax.naming.NameAlreadyBoundException: Can't rebind anything but a
> >replica-aware
> >> stub to a name that is currently bound to a replica-aware stub; remaining
> >name
> >> ''
> >>
> >> The object is obviously clusterable (it is a stateless EJB with "home-is-clusterable=true").
> >> It has been deployed to the cluster target. When is working it is load
> >balanced
> >> between both servers. It deploys perfectly when starting up both servers,
> >but
> >> hot deployment does not work.
> >>
> >> This works fine when only one server is up.
> >>
> >> ¿Is not possible to do hot deployment in cluster?
> >>
> >
> >
>
-
Hello,
DAG Exchange 2010 SP3 RU6 with MAPI network and Replication network. All works correctly.
But, when the DAG member restarts , the cluster goes offline and i can't bring it online.
The message error:
Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network 'Cluster Network 1' is not configured to allow client access.
Cluster Network 1 is the replication network and it is normal that allow client access is unchecked
I already tried to check, apply then uncheck apply. it does anything.
Could you please help me to figure out the issue ?
Best regardsHi,
Check below link.
http://forums.msexchange.org/Cluster_network_name_is_not_online/m_1800552315/tm.htm
I was able to resolve the issue without taking down any resources.
First, I noticed that the Failover Cluster Manager "Cluster Name" had the IP address of the replication network only..
After going back through the guide @
http://technet.microsoft.com/en-us/library/dd638104.aspx I changed the properties on the NICs for file sharing, etc..I then adjusted windows firewall rules to block traffic from my MAPI network destined for the replication network.
I then removed the IP from the replication network on the DAG leaving only the 1 MAPI network IP.
After an hour or so, I ran Get-DatabaseAvailabilityGroupNetwork and seen that the MAPIAccess property was finally set to true on my MAPI network. I went back to Failover Cluster Manager and my Cluster Core Resource Cluster Name dropped the IP address that was
associated (IP from the replication network) I added a new IP from my Mapi network range, updated the DAG IP in Exchange and the DNS record for the DAG and my cluster resource came online. -
How to deploy WebLogic Cluster on a Blade?
Hi, I am looking for recommendations on how ( if it makes sense ) to deploy WebLogic
Cluster on the (Intel) Blade HW. The question is, actually, caused by the fact
that the Blade is totally redundant and load-balanced HW where the requests are
managed by a Big-IP module ( and redirected to the IPs on the internal Blade Cassettes
One of possible solutions, we discuss now, is "either-or", i.e. let's discard
the App.Server cluster and use the HW cluster. This might work for the request
load balance but we loose all other, out-of-the-box, cluster features like session,
EJB, JNDI and so on failover and balance features.
Any notes with this regard will be greatly appreciated.
Thanks, - Michael
P.S. I repeated the same question om "cluster" Newsgroup but have not seen any
responds so far.It sounds like you're getting request routing and fail-over in front of
WLS with the Big-IP. Typically people would enable WLS clustering to
get replicated HTTP sessions in an environment like this.
-- Rob
Michael Poulin wrote:
Hi, I am looking for recommendations on how ( if it makes sense ) to deploy WebLogic
Cluster on the (Intel) Blade HW. The question is, actually, caused by the fact
that the Blade is totally redundant and load-balanced HW where the requests are
managed by a Big-IP module ( and redirected to the IPs on the internal Blade Cassettes
One of possible solutions, we discuss now, is "either-or", i.e. let's discard
the App.Server cluster and use the HW cluster. This might work for the request
load balance but we loose all other, out-of-the-box, cluster features like session,
EJB, JNDI and so on failover and balance features.
Any notes with this regard will be greatly appreciated.
Thanks, - Michael
P.S. I repeated the same question om "cluster" Newsgroup but have not seen any
responds so far. -
Error in Online Deployment patching J2EE Engine
Hi,
We are installing the J2EE engine in a BW server with Windows S.O. In step "Deploy Online" we obtain the following error:
Sep 13, 2006 8:23:22 AM Info: Start logging to console
Sep 13, 2006 8:23:22 AM Info:
Sep 13, 2006 8:23:22 AM Info: ============================================
Sep 13, 2006 8:23:22 AM Info: = Starting to execute command 'deploy' =
Sep 13, 2006 8:23:22 AM Info: ============================================
Sep 13, 2006 8:23:22 AM Info: Starting SDM - Software Deployment Manager...
Sep 13, 2006 8:23:23 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.4018.00.0000.20060706111659.0000
Sep 13, 2006 8:23:24 AM Info: SDM operation mode successfully set to: Standalone
Sep 13, 2006 8:23:25 AM Info: Initializing Network Manager (50017)
Sep 13, 2006 8:23:25 AM Info: Checking if another SDM is running on port 50018
Sep 13, 2006 8:23:25 AM Info: -
Starting deployment -
Sep 13, 2006 8:23:25 AM Info: Error handling strategy: OnErrorStop
Sep 13, 2006 8:23:25 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Sep 13, 2006 8:23:25 AM Info: Update strategy: UpdateLowerVersions
Sep 13, 2006 8:23:25 AM Info: Starting deployment prerequisites:
Sep 13, 2006 8:23:31 AM Info: Loading selected archives...
Sep 13, 2006 8:23:31 AM Info: Loading archive 'E:\18_0-20000118_directory\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA'
Sep 13, 2006 8:23:38 AM Info: Selected archives successfully loaded.
Sep 13, 2006 8:23:39 AM Info: Actions per selected component:
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111713.0000'/'1' updates currently deployed development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060426183247.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' will not update currently deployed development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/wslib'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172955.0000'/'1' updates currently deployed development component 'tc/workflowmodeler'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172955.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818153022.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818153022.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' will not update currently deployed development component 'com.sapportals.supportplatform.dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.customizing.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'tc/supportplatform/engine'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101310.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119145451.0000'/'1' updates currently deployed development component 'tc/SL/utility/wsear'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060119145451.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/api'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172625.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'1' will not update currently deployed development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101559.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101332.0000'/'1' updates currently deployed development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101332.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/xml_das_connector_init'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' will not update currently deployed development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' will not update currently deployed development component 'tc/TechSrv/XML_DAS_Connector_Schema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027104030.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050121164722.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606172625.0000'/'1' updates currently deployed development component 'tc/bcb/ici'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606172625.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'2' will not update currently deployed development component 'synclog'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112013.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'tc/monitoring/systeminfo'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027101045.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS_Connector'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027101045.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111519.0000'/'1' updates currently deployed development component 'com.sapportals.supportplatform'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101310.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' will be deployed.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' will not update currently deployed development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' will not update currently deployed development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4018.00.0000.20051027104030.0000'/'1' updates currently deployed development component 'com.sap.util.monitor.jarm.ccms'/'sap.com'/'SAP AG'/'6.4017.00.0000.20051027104030.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/vsi/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164207.0000'/'1' updates currently deployed development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606164207.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818152118.0000'/'1' updates currently deployed development component 'com.sap.pmi.adm'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818152118.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'1' will not update currently deployed development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112029.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/Util'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101532.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050331133205.0000'/'1' updates currently deployed development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050331133205.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413100235.0000'/'1' updates currently deployed development component 'tc/conn/connectorframework'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100235.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101532.0000'/'1' updates currently deployed development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101532.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050818150135.0000'/'1' updates currently deployed development component 'com.sap.ip.me.insttool'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050818150135.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111540.0000'/'1' updates currently deployed development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101350.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060726153907.0000'/'1' updates currently deployed development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060503180106.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050606164103.0000'/'1' updates currently deployed development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050606164103.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111002.0000'/'1' updates currently deployed development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413100412.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4018.00.0000.20050121164722.0000'/'1' updates currently deployed development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.4017.00.0000.20050121164722.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060119123705.0000'/'1' updates currently deployed development component 'tc/TechSrv/XML_DAS'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060119123705.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706112627.0000'/'1' updates currently deployed development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413102720.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: No action: Selected development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'1' will not update currently deployed development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413102101.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4018.00.0000.20041104140331.0000'/'1' updates currently deployed development component 'tc/eCATTPing'/'sap.com'/'SAP AG'/'6.4017.00.0000.20041104140331.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060413101559.0000'/'1' updates currently deployed development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101559.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
Sep 13, 2006 8:23:39 AM Info: Update: Selected development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060814115206.0000'/'1' updates currently deployed development component 'com.sap.engine.heartbeat'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060427163646.0000'/'0'.
Sep 13, 2006 8:23:40 AM Info: Ending deployment prerequisites. All items are correct.
Sep 13, 2006 8:23:41 AM Info: Saved current Engine state.
Sep 13, 2006 8:23:41 AM Info: Starting: Update: Selected development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' updates currently deployed development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4017.00.0000.20060413101546.0000'/'0'.
Sep 13, 2006 8:23:41 AM Info: SDA to be deployed: E:\usr\sap\SBD\DVEBMGS00\SDM\root\origin\sap.com\com.sap.lcr.saprfc\SAP AG\1\6.4018.00.0000.20060706111625.0000\lcrsaprfc.ear
Sep 13, 2006 8:23:41 AM Info: Software type of SDA: J2EE
Sep 13, 2006 8:23:41 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 13, 2006 8:24:03 AM Info: Begin of log messages of the target system:
06/09/13 08:23:57 - ***********************************************************
06/09/13 08:23:59 - References from application sap.com/com.sap.lcr.saprfc to its loaders done.
06/09/13 08:23:59 - Start updating EAR file...
06/09/13 08:23:59 - start-up mode is lazy
06/09/13 08:23:59 - EAR file updated successfully for 94ms.
06/09/13 08:23:59 - Start updating...
06/09/13 08:24:00 - EAR file uploaded to server for 719ms.
06/09/13 08:24:03 - ERROR: Not updated. Deploy Service returned ERROR:
java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.lcr.saprfc..
Reason: com/sap/mw/jco/JCO$Function; nested exception is:
java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:682)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
at java.lang.Class.privateGetPublicMethods(Class.java:1778)
at java.lang.Class.getMethods(Class.java:832)
at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getWithNotSpecifiedMethodInterface(MethodsExtractor.java:121)
at com.sap.engine.services.ejb.deploy.xml.MethodsExtractor.getAllMethodsInBean(MethodsExtractor.java:103)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.getMethodXml(EJBJarParser.java:1168)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processContainerTransaction(EJBJarParser.java:1023)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.processAssemblyDescriptor(EJBJarParser.java:924)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:156)
at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:297)
at com.sap.engine.services.ejb.EJBAdmin.buildAppDescriptorBeforeUpdate(EJBAdmin.java:408)
at com.sap.engine.services.ejb.EJBAdmin.needUpdate(EJBAdmin.java:341)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.getContainersWhichNeedUpdate(UpdateTransaction.java:537)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.getConcernedContainers(UpdateTransaction.java:493)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:263)
at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:670)
... 10 more
For detailed information see the log file of the Deploy Service.
06/09/13 08:24:03 - ***********************************************************
Sep 13, 2006 8:24:03 AM Info: End of log messages of the target system.
Sep 13, 2006 8:24:03 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 13, 2006 8:24:03 AM Error: Aborted: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1', grouped by :
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Exception in operation update with application sap.com/com.sap.lcr.saprfc..
Reason: com/sap/mw/jco/JCO$Function; nested exception is:
java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$Function
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Sep 13, 2006 8:24:03 AM Info: Starting to save the repository
Sep 13, 2006 8:24:04 AM Info: Finished saving the repository
Sep 13, 2006 8:24:04 AM Info: Starting: Initial deployment: Selected software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1' will be deployed.
Sep 13, 2006 8:24:04 AM Error: Aborted: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.40.18.0.20060816080857''/'1':
Failed deployment of SDAs:
development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.4018.00.0000.20060706111625.0000'/'1' : aborted
Please, look at error logs above for more information!
Sep 13, 2006 8:24:04 AM Info: Starting to save the repository
Sep 13, 2006 8:24:04 AM Info: Finished saving the repository
Sep 13, 2006 8:24:04 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Sep 13, 2006 8:24:04 AM Error: -
At least one of the Deployments failed -
Sep 13, 2006 8:24:05 AM Info: Summarizing the deployment results:
Sep 13, 2006 8:24:05 AM Error: Aborted: E:\18_0-20000118_directory\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS18_0.SCA
Sep 13, 2006 8:24:05 AM Error: Processing error. Return code: 4
Regards,Hi everybody,
Well, after of the last post where it commented that the possible solution would be to update Java to version 12, the issue continues.
Now, we have the following error after SAP recommended to deploy the file manually with SDM Tool, the file is lcrsaprfc.ear and show the following error:
Manifest attributes are missing or have badly formatted value:
attribute keylocation is missing
attribute keyname is missing
attribute keyvendor is missing
attribute keycounter is missing
Maybe can be a problem with the file?, format?, build?.
Thanks for your help and patience.
Regards,
Rafa R.R. -
JMS Server deployed to cluster of servers
Hey guys,
I was trying to deploy a JMS server to a cluster of servers and in the target section there wasn't an option for the cluster. They had an option for each individual server and another migratable version of the server. If I target one of the migratable servers in the cluster will it apply to all of the servers?
I read the following passage in the weblogic documents:
Obtain a Clustered JMS Licence
In order to implement JMS clustering, you must have a valid clustered JMS license, which allows a connection factory and a destination to be on different WebLogic Server instances. A clustered JMS license is also required to use the Foreign JMS Providers feature, as described in "Simple Access to Remote or Foreign JMS Providers" in the Administration Console Online Help. If you do not have a valid clustered JMS license, contact your BEA sales representative.
If i'm just building a model does this apply to me?
Thankscontinued reading to clarify. Problem solved, thanks for looking
-
Error during application deployment in cluster
Hi All,
I am seeing a weird error when I deploy my application in 2 node cluster. Few months back, the same cluster worked perfectly alright. The error relates to lookup at localhost:7001 which is no where in the configuration as admin server url is http://srai-xp:7001. I created a new domain and see the same problem.
Any pointers are greatly appreciated.
Thanks
--shashi
Here is the error log:
D:\apps\bea\user_projects\domains\nclusterdomain>startManagedWebLogic.cmd NodeSR http://srai-xp:7001
D:\apps\bea\user_projects\domains\nclusterdomain>echo off
CLASSPATH=CR190380_81sp3.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jax-qname.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\li
jsafe.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jsafejce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\asn1.jar;;C:\j2sd
.4.2_04\lib\tools.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic_sp.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic.jar;d:\apps\bea\WEBLOG~1\common\eval\
intbase\lib\pbserver44.jar;d:\apps\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\j2sdk1.4.2_04\jre\lib\rt.jar;d:\apps\bea\WEBLOG~1\server\lib\webservices.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_base.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_jce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb_jaas.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_license.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_provider.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\mysql-connector-java.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\nls_charset12.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\ojdbc14.jar;
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
<Mar 17, 2005 4:19:27 PM PST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Mar 17, 2005 4:21:22 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.2_04-b05 fr
Sun Microsystems Inc.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://srai-xp:7001 to ch
k if there exists a running admin server at this URL.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
<Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://srai-xp:7001 to retriev
the initial configuration.>
<Mar 17, 2005 4:21:25 PM PST> <Notice> <Log Management> <BEA-170019> <The server log file D:\apps\bea\user_projects\domains\nclusterdomain\NodeSR\No
SR.log is opened. All server side log events will be written to this file.>
<Mar 17, 2005 4:21:30 PM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 17, 2005 4:21:30 PM PST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "NodeSR" for domain "nclusterdomain">
<Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster XCluster on 237.0.0.101:8050.>
<Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of XCluster.>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 153.32.158.12
<Mar 17, 2005 4:22:08 PM PST> <Notice> <Cluster> <BEA-000102> <Joining cluster XCluster on 237.0.0.101:8050>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "NodeSR" for domain "nclusterdomain" running i
Production Mode>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_de': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_fr': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_ja': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:35 PM PST> <Warning> <J2EE> <BEA-160081> <The JMS connection factory resource EDCEventQCF declared in the EJB "EventManagerBean"
part of application "edc-server" does not support XA. It cannot be used inside a transaction context.>
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:618)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
... 28 more
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Unable to create InitialContext ] - with nested exception:
[javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is
java.net.ConnectException: Connection refused: connect; No available router to destination]]
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:770)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
<Mar 17, 2005 4:23:40 PM PST> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application edc-server.
java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2327)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>I checked all deployment descriptions and there are no references to t3://localhost:7001. Few months back, I had the complete clustering setup working on 2 machines and now when I deploy my application on same configuration, it fails with t3://localhost:7001 unreachable error. I created a new cluster configuration on one machine with 2 managed server and it deploys fine. Can not figure out what has changed ?
-
Web modules don't get deployed to cluster instance directory
Hi,
I have a domain with one cluster, which has one instance. Sometimes (!), the web aplications I deploy don't get unpacked in the directory {instanceRoot}/applications/j2ee-modules but only in {domainRoot}/applications/j2ee-modules. When that happens, they don't work and I cannot access them through their URL.
I deploy them using the web admin console, enable the to the cluster in question. Everything goes ok (or at least the UI says so) and in the domain.xml I have this:
<web-module availability-enabled="false" context-root="/myapp" directory-deployed="false" enabled="true" location="${com.sun.aas.instanceRoot}/applications/j2ee-modules/myapp" name="myapp" object-type="user"/>
<server...
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="myapp"/>
<cluster...
<application-ref disable-timeout-in-minutes="30" enabled="true" lb-enabled="false" ref="myapp"/>
In both the apps the were copied to the instance applications dir and in the ones that remained only in the domain applications dir (and do not work). In the latter, the location dir does not exist.
Anyone has gone through any similar situation? This deployment process is a bit confusing for me, wrt instances, clusters, domains etc.
Thanks!
Jo�o.Thanks for the answer.
But how is this mechanism controlled? Sometimes, the domain just doesn't seem to propagate the changes to the cluster instances (or stand-alone instances). For example, sometimes when I change a property of a data source through the admin gui of the domain, it does not get propagated to the desired instance config, even after restarting the whole system.
I think that it may have something to do with the manual changes that I have to do sometimes in the domain.xml file (this is neede when you have huge config changes to be replicated in many servers).
Is there any option to enforce the replication of the config from the domain to the instances? Or at least to make it verbose so that I can realize what is going on underneath.
Thanks. -
How to determine whether a resource is online in a cluster from a script
Hello All,
Environment:
Solaris 9
SC3.1/U4 and SC3.2
RG name:
dw-rg
Resources:
dw-vip - Logical hostname RS
dw-stor - HA storage RS
dw-ora - HA Oracle RS
dw-lis - HA Oracle listiner RS
Hostnames:
dwn1
dwn2
We have a situation where we are trying to backup an oracle DB's on our clusters. We are performing both hot and cold backups. During a cold backup, we take the database completely down and the other where we put the DB into hot backup mode.
In the coldbackup case, we simply take the oracle RS offline and in the hotbackup case, the oracle RS in still online. The scripts are ran from cron on each cluster node.
In the coldbackup case, As a consistency/error check I would like to first check the status of the oracle rs and see if it is online somewhere in the cluster.
in the hot backup case, I need to run the script from the cluster node that RG/RS is running on.
Since I am checking status and return codes, I don't want to use scstat and grep to get this information if I can avoid it, but, I would either write a C program or script to do this.
Any ideas or sugguestions would be greatly appreciated
Thanks in advance
GeorgeYou can use the Sun Cluster library functions, have a look at the manpage for scha_calls(3ha).
In your specific case you could have a cronjob running on each node. The first thing it would do is to check if the resource you are interested is online on the node, like
RS_STATUS=`/usr/cluster/bin/scha_resource_get -G dw-rg -R dw-ora -O RESOURCE_STATE`
if [ "$RS_STATUS" != ONLINE ] ; then
exit 0
else
<do what you need to do>
fiGreets
Thorsten -
OSB Proxy Service deployed in cluster environment FTP issue
Hi,
I have a OSB 11g proxy service based on a FTP JCA adapter. Here are the JCA settings:
<connection-factory location="JNDI_FILE_TOKEN" UIincludeWildcard="FILENAME_TOKEN"/>
<endpoint-activation portType="Get_ptt" operation="Get">
<activation-spec className="oracle.tip.adapter.ftp.inbound.FTPActivationSpec">
<property name="DeleteFile" value="true"/>
<property name="MinimumAge" value="0"/>
<property name="PhysicalDirectory" value="FOLDER_TOKEN"/>
<property name="Recursive" value="false"/>
<property name="PollingFrequency" value="30"/>
<property name="FileType" value="ascii"/>
<property name="IncludeFiles" value="FILENAME_TOKEN"/>
</activation-spec>
</endpoint-activation>
When I deploy this proxy in a cluster (having 2 osb nodes) and place the very first file on FTP server. Both nodes pick the file simultaneously. But after this when I place files on FTP server only one node is picking file. Could you kindly tell where is the issue ?
Thanks and RegardsHi Mani,
Do check the configuration of ProxyService-2 that it is enabled or not.
Do check the input payload of it, that ProxyService-1 is passing the correct payload to ProxyService-2.
Redeploy the ProxyService-2
There is some issue in your proxyService-2.
Regards,
Richa -
Resource Adapter deployment on cluster
Hi,
I have a weblogic cluster with 2 nodes and a load balancer. Recently I have deployed a database adapter to connect to a sql server database which is used by a service (OSB proxy service). The deployed was performed with both nodes running and I connected to the admin console using the LB IP. The deployed was done with successful and I have restarted both nodes. The cluster is configured with a stage mode in order to copy files from admin server.
When I call this service, it goes ok when node1 is used but not ok when node2 is used. It gives an JCA error accessing the sql server database. To solve this issue I had to copy the deployment plan file from node1 to node2 and reploy de dbadapter resource with node1 down in order to update the node2. I was expecting that these files were updated on both nodes whenever I deploy a resource adapter on admin console.
What am I doing wrong? Or what config should I check/update on admin console in order to avoid this manual task?
Thanks,
Regards,
António AmadoUse the shared location for deployment plans.
Please see the link : Managing the Topology for an Enterprise Deployment - 11g Release 1 (11.1.1) -
HI,
we have a clustered env for our production system. I am trying to deploy an SDA file from SDM of central instance. I am getting the following error.
Error: An error occured while starting a cluster instance.
Error: There is no control instance running in the cluster:
Name:JM_T1137182930718_hostname |Host:hostname |State:5|
Info:|Name:JC_hostname |Host:hostname |State:5|
Info:Please check if there are running cluster instances.
do i need to configure something in sdm of our central instance?
please help us.
Thank youAs per the previous message, it should work if the
cluster is installed correctly.
With a clustered installation the SCS (SAP Central
Services) would be installed using a virtual hostname.
Later when the Central instance is installed it must
refer to this logical hostname for the SCS.
My guess is that SDM is using the hostname of the CI
instead of the SCS logical hostname.
When you installed the Central Instance, did you use
the HA instructions for installing a Central Instance ?
regards
Tom -
HI,
we have a clustered env for our production system. i defined a track and set up the runtime systems. since our production box is a clustered environoment, i specified the SDM hostname as the host on which the central instance is running.
so when i try to transport, until QA everything is fine (as they are non - clustered), but while trying to import particluar assembly to production, the error shown in deploy log is
Error: An error occured while starting a cluster instance.
Error: There is no control instance running in the cluster:
Name:JM_T1137182930718_hostname |Host:hostname |State:5|
Info:|Name:JC_hostname |Host:hostname |State:5|
Info:Please check if there are running cluster instances.
do i need to configure something in SDM of our central instance?
please help us.
ThanksThis sounds like a bug to me. I'd suggest you contact [email protected]
-- Rob
Lars M wrote:
We are running WL 8.1 SP2
When the administration server is running, our ear is deployed to a cluster (2
managed instances on 2 different nodes) using stage mode, and everything is fine.
The problem:
Afterwards, if we try to start a managed server when the administraion server
is down, the managed server cannot activate the deployed application. It reports
that the application path is invalid.
The application path stored in the config.xml (and msi-config.xml) is the upload
path of the administration server (e.g. DOMAIN_HOME/adminserver/upload/OurApp.ear)
- and of course this path is only available on the node where the admin server
is running - and NOT on another hw node where the managed server is running.
Why is the managed server trying to open the original "source" application?
Especially when the application is staged?
Thanks
Lars -
Problem with weblogic.deploy and cluster
I'm having some problems with the weblogic.deploy class when trying to refresh
a jsp file. Using the following command to redeploy the entire application works
fine:
java weblogic.deploy -port 9876 -host apptest01 update
administrator portal c:\portal-site
However using the following command to refresh just one jsp
file:
java weblogic.deploy -url t3://apptest01:9876 -username system
-jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
refresh administrator portal
produces the following stack trace:
javax.naming.NameNotFoundException: Unable to resolve
weblogic.management.home.olbcluster.
Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
remaining name ''
at weblogic.rmi.internal.BasicOutboundRequest.
sendReceive(BasicOutboundRequest.java:85)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
invoke(ReplicaAwareRemoteRef.java:255)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
invoke(ReplicaAwareRemoteRef.java:222)
at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
at $Proxy0.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.
lookup(WLContextImpl.java:323)
at weblogic.management.tools.WebAppComponentRefreshTool.
getMBeanHomeForManagedServer
WebAppComponentRefreshTool.java:498)
at weblogic.management.tools.
WebAppComponentRefreshTool.
getComponentMBeanForServer
(WebAppComponentRefreshTool.java:225)
at weblogic.management.tools.
WebAppComponentRefreshTool.findInternalPaths
(WebAppComponentRefreshTool.java:187)
at weblogic.management.tools.WebAppComponentRefreshTool.
refresh(WebAppComponentRefreshTool.java:151)
at weblogic.deploy.refresh(deploy.java:704)
at weblogic.deploy.runBody(deploy.java:374)
at weblogic.utils.compiler.Tool.run(Tool.java:79)
at weblogic.deploy.main(deploy.java:1601)
Unable to resolve weblogic.management.home.olbcluster.
Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
Any ideas?
"John Murphy" <[email protected]> wrote:
>
>I'm having some problems with the weblogic.deploy class when trying to
>refresh
>a jsp file. Using the following command to redeploy the entire application
>works
>fine:
>
>java weblogic.deploy -port 9876 -host apptest01 update
>administrator portal c:\portal-site
>
>However using the following command to refresh just one jsp
>file:
>
>java weblogic.deploy -url t3://apptest01:9876 -username system
>-jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
>refresh administrator portal
>
>produces the following stack trace:
>
>javax.naming.NameNotFoundException: Unable to resolve
>weblogic.management.home.olbcluster.
>Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
>remaining name ''
> at weblogic.rmi.internal.BasicOutboundRequest.
> sendReceive(BasicOutboundRequest.java:85)
> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
> invoke(ReplicaAwareRemoteRef.java:255)
> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
> invoke(ReplicaAwareRemoteRef.java:222)
> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
> at $Proxy0.lookup(Unknown Source)
> at weblogic.jndi.internal.WLContextImpl.
> lookup(WLContextImpl.java:323)
> at weblogic.management.tools.WebAppComponentRefreshTool.
> getMBeanHomeForManagedServer
> WebAppComponentRefreshTool.java:498)
> at weblogic.management.tools.
> WebAppComponentRefreshTool.
> getComponentMBeanForServer
> (WebAppComponentRefreshTool.java:225)
> at weblogic.management.tools.
> WebAppComponentRefreshTool.findInternalPaths
> (WebAppComponentRefreshTool.java:187)
> at weblogic.management.tools.WebAppComponentRefreshTool.
> refresh(WebAppComponentRefreshTool.java:151)
> at weblogic.deploy.refresh(deploy.java:704)
> at weblogic.deploy.runBody(deploy.java:374)
> at weblogic.utils.compiler.Tool.run(Tool.java:79)
> at weblogic.deploy.main(deploy.java:1601)
>Unable to resolve weblogic.management.home.olbcluster.
>Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
>
>Any ideas?
>
Hi John,
How's tricks?
It looks to me as though the olbcluster JNDI reference isn't being resolved from
the tree. A similar error results when a Connection Pool cannot be resolved, the
JNDI context env.jdbc is resolved but the particlar pool isn't. In my experience
it often turns out to be an error in the correlation between the deployment descriptors,
settings applied via the console and references made in the code.
That's my tuppence worth,
James :-)
Maybe you are looking for
-
I forgot my passcode to my ipod, so it said ineeded to connect it to iTunes because it's disabled. So, i connected to itunes and it said "Ipod cannot be used because it's being locked with a passcode. Unlock passcode and try again". Well i dont know
-
I recently bought my first ipod. I have had an itunes account for some time. After I plugged in the ipod the first time, my computer stopped being able to access the itunes store. There is no error message, it just runs and runs trying to access the
-
Hi all, Don't have a technical question to ask but more of a philosophical, I think. Some time ago, I purchased a G4 tower and have been using my Mac for basic computing and internet access, but I have recently been wanting to learn more in detail th
-
How to get a list of users? Any FM?
Hi guys, is there a function module for getting the list of R/3 users? Thank you, AR
-
Hello :-) I have a MSI GT70 0NC laptop. It has the main C drive and a D drive. I reformatted the D drive but noticed it says 274 GB free of 275 GB. What is occupying 1 GB on this drive? Is it the factory restore image? Thank you,