Similar logical host resource configured on 2 different resource groups

hi,
I had an issue with logical host setup as follows.
Background
We had a failover resource group RGA which is running a critical Oracle instance and listener process.
It has a logical host resource ora-lh-rs configured with logical host pointing to VirtualHostA.
I need to create another failover resource group called RGB with another Oracle instance.
Now at present this Oracle instance (Not under cluster control yet) is listening to the same logical host - VirtualHostA as RGA.
When I create this new resource group RGB, I need to configure it to share the same logical host as RGA.
The problem is if I need to add the logical host resource ora-lh-rs with VirtualHostA to this RGB, I foresee that there will be an IP address conflict if I failover RGB to the other cluster node (If my guess is wrong, but logically there should be an IP address conflict if SUN Cluster does not block me from adding the same logical host resource to RGB).
Question
Is there any other way to overcome this issue other than to configure the second Oracle instance to listen on a different logical IP?
To add, RGB is a less priority Oracle instance and will always need to be with RGA on the same node.
Any suggestions are welcome. My apology if this question sounds stupid as I do not have an UAT environment to test.
Thanks
ldd76

HI Tim,
Thanks very much for your kind advice. I must say that I have very little experience with SUN Cluster so I beg your pardon if my concept is too superficial.
The reason why I cannot put both Oracle instance in the same RG is because that' s my boss initial proposal. I will speak to her again on the log_only option.
But can I confirm that the command looks like this after I add the resources to RGA.
scrgadm -cj rgb-ora-rs -y Failover_mode=LOG_ONLY (Oracle server)
scrgadm -cj rgb-lsn-rs -y Failover_mode=LOG_ONLY (Oracle Listener)
scrgadm -cj rgb-hasp-rs -y Failover_mode=LOG_ONLY (HA Storage Plus)
As for the logical host questions, it has been legacy that both the Oracle instance listens on the same logical IP(Just that the new and less critical Oracle instance is not under cluster control yet)
But my gut feel for the reason behind this is that the less important Oracle instance is always running on the same node where RGA is running (since that Oracle instance is used for data warehousing with data replicated from the more critical Oracle instance only) else it is meaningless. Thats my guess why ony one logical IP is used.
If the direction is still to use RG_affinities, then if I tweak the following steps a bit will it work?
1) Create RGB.
2) Activate RGB - scswitch -Z -g RGB
3) Offline RGB - scswitch -F -g RGB
4) Failover RGA to the other node
5) Failover RGB to the other node
6) Offline RGB on the other node
7) Failover RGA back to the original node
8) Failover RGB back to the original node
Thanks.

Similar Messages

Using different configured views for different user group in crm2007

Hello SAP Expert,
Want to clarify if the BADI (Configuration Access Determination BADI ; BSP_DLC_ACCESS_ENHANCEMENT) is used as design time or Run time. By looking the help of this BADI it says "This Business Add-In (BAdI) is used in the UI Configuration Tool (CRM-FRW-CON) component." Looks like this is at configuration time not at run time.
The actual requirement is that for a set of users which work on a particular department, we want to have some extra information on 2 views and rest of the views they would be using same as entire organization. We are inclined towards using config role rather than zviews. If we were to use zviews then it would not be a difficult one.
We were thinking of a mechanism to show the configured view based on user's Business Role at runtime. e.g. we have 2 roles A and B. Role A user have only 2 views specific to them and all other views they use same as Role B. We do not want to use ZView rather use Role Config Key to distinguish the views. What I was thinking that we should be able to create these 2 views with Config Role A and all views (including these 2) with Config Role B. On Business Role A and Business Role B both, We will assign Config Role "B". but at runtime system should determine if the Business Role is A and Component is CMP1 then use the view V1 with Config Role A not the default view with config role B. (we can maintain that information in a Z table). This is not based on runtime profile but to use configured view at runtime.
Any thoughts/ help really appreciated.
Best regards,

Hi Amithab,
you can use badi CRM_BP_UIU_VIEW_CONFIG of enhancement spot CRM_UIU_BP_ENHANCEMENT for your requirements. Please read the badi documentation because you need also a implementation of badi CRM_BP_UIU_CONFIG_CALLBACK (same spot). SAP considers badi CRM_BP_UIU_VIEW_CONFIG only for use at dynamically loading different configuartions of view details for business partners or contact persons at runtime. But you can use your badi implementation also for other views. You have to redefine method DO_CONFIG_DETERMINATION in your views. And call your badi from there. For this copy&paste the logic of DO_CONFIG_DETERMINATION of bp details to the views you have to load dynamically at runtime.
We have used this approach for access controll and granting special access to views dependent on different employee functions.
Best regards
Michael

Zone Cluster: Creating a logical host resource fails

Hi All,
I am trybing to create a logical host resource with two logical addresses to be part of the resource, however, the command is failing. Here is what I run to create the resource:
clrslh create -Z pgsql-production -g pgsql-rg -h pgprddb-prod,pgprddb-voip pgsql-halh-rs
And I am presented with this failure:
clrslh: specified hostname(s) cannot be hosted by any adapter on bfieprddb01
clrslh: Hostname(s): pgprddb-prod pgprddb-voip
I have pgprddb-prod and pgprddb-voip defined in the /etc/hosts files on the 2 global cluster nodes and also within the two zones in the zone cluster.
I have also modified the zone cluster configuration as described in the following thread:
http://forums.sun.com/thread.jspa?threadID=5420128
This is what I have done to the zone cluster:
clzc configure pgsql-production
clzc:pgsql-production> add net
clzc:pgsql-production:net> set address=pgprddb-prod
clzc:pgsql-production:net> end
clzc:pgsql-production> add net
clzc:pgsql-production:net> set address=pgprddb-voip
clzc:pgsql-production:net> end
clzc:pgsql-production> verify
clzc:pgsql-production> commit
clzc:pgsql-production> quit
Am I missing something here, help please :)
I did read a blog post mentioning that the logical host resource is not supported with exclusive-ip zones at the moment, but I have checked my configuration and I am running with ip-type=shared.
Any suggestions would be greatly appreciated.
Thanks

I managed to fix the issue, I got the hint from the following thread:
http://72.5.124.102/thread.jspa?threadID=5432115&tstart=15
Turns out that you can only define more than one logical host if they all reside on the same subnet. I therefor had to create 2 logical host resources for each subnet by doing the following in the global zone:
clrslh create -g pgsql-rg -Z pgsql-production -h pgprddb-prod pgsql-halh-prod-rs
clrslh create -g pgsql-rg -Z pgsql-production -h pgprddb-voip pgsql-halh-voip-rs
Thanks for reading :)

Logical host resource in SC3.2 missing IPMP

I was under the impression that when creating a logical host resource in Solaris Cluster 3.2, that it will read the hosts and hostname.* files to get the IPMP info and do this automatically for you. I am not seeing this behavior and am hoping someone can shed some light on this for me. Here is the relevant data, any help is greatly appreciated. If it matters, this is Solaris Cluster 3.2 on Solaris 10, running in a 25k domain.
# grep cluster1vip hosts
10.230.108.28 cluster1vip cluster1vip.example.com
10.230.108.29 cluster1vip-ce1 #ipmp_test_cluster1vip1
10.230.108.30 cluster1vip-ce5 #ipmp_test_cluster1vip2
# cat hostname.ce1
cluster1vip netmask + broadcast + group ipmp_sc1 up \
addif cluster1vip-ce1 deprecated -failover netmask + up
# cat hostname.ce5
cluster1vip-ce5 deprecated -failover netmask + broadcast + group ipmp_sc1 up
When I bring the resource online, these are the settings that get applied:
ce6:1: flags=1040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRECATED,IPv4> mtu 1500 index 3
inet 10.230.108.28 netmask ffffff80 broadcast 10.230.108.127
Again, any help or guidance is greatly appreciated.

For probe based IPMP the following has always worked for me:
- IPMP interfaces of same media type
- SPARC needs local-mac-address set to true in OBP
- Supported interface (if using probe method - [http://docs.sun.com/app/docs/doc/816-4554/mpoverview?a=view|http://docs.sun.com/app/docs/doc/816-4554/mpoverview?a=view] )
/etc/hosts
192.168.1.1 hawkeye
192.168.1.2 ipmp-test1
192.168.1.3 ipmp-test2
For the cluster node 'hawkeye'
/etc/hostname.ce0 before the IPMP change:
hawkeye group sc_ipmp0 -failover
/etc/hostname.ce0 after the IPMP change:
hawkeye group sc_ipmp- failover up addif ipmp-test1 -failover deprecated up
/etc/hostname.ce.1
group sc_ipmp0 failover up addif ipmp-test2 -failover deprecated up
Reboot cluster node and you should be good to go.

Unable to Start JCAPS 5.1.0 Logical host in Windows XP

Hi,
I am unable to start Start JCAPS 5.1.0 Logical Host on my Windows XP OS. I have installed it recently following the JCAPS installation instructions. I have created a domain with the default name 'domain1'.
Please see the error message that i get in my logs folder C:\JavaCAPS51\logicalhost\is\domains\domain1\logs
Starting Integration Server 5.1 (build 20060319-0947) ...
[#|2006-10-05T11:11:00.341+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_06] from [Sun Microsystems Inc.]|#]
[#|2006-10-05T11:11:02.705+0100|INFO|IS5.1|javax.enterprise.system.tools.admin|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2006-10-05T11:11:02.965+0100|INFO|IS5.1|javax.enterprise.system.tools.admin|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-10-05T11:11:02.965+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|JMS5038: jms-service element in domain.xml is configured to have type=REMOTE. JMS service will be started locally only if type is LOCAL.|#]
[#|2006-10-05T11:11:02.975+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|STCMS configuration: dir=[../../domains/domain1/stcms/instance1]; bin=[C:\JavaCAPS51\logicalhost\is\domains\domain1/../../stcms/bin]; config dir=[C:\JavaCAPS51\logicalhost\is\domains\domain1/config]; config=[C:\JavaCAPS51\logicalhost\is\domains\domain1/config/stcms.default.Properties]|#]
[#|2006-10-05T11:11:03.576+0100|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Minimum nonce freshness limitation time period is set to: 300000|#]
[#|2006-10-05T11:11:03.576+0100|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Maximum nonce clock skew limitation time period is set to: 0|#]
[#|2006-10-05T11:11:03.576+0100|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Nonce cache sweep interval is set to: 180000|#]
[#|2006-10-05T11:11:03.636+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Registered STCMS configuration MBean com.sun.appserv:jmsservertype=stcms,name=SeeBeyond_JMS_IQ_Manager,type=messaging-server-config-mbean|#]
[#|2006-10-05T11:11:03.867+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|stcms journal service server disabled|#]
[#|2006-10-05T11:11:03.867+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Registered STCMS admin management MBean com.sun.appserv:jmsservertype=stcms,name=SeeBeyond_JMS_IQ_Manager,type=messaging-server-admin-mbean|#]
[#|2006-10-05T11:11:03.877+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Registered STCMS alert MBean com.sun.appserv:jmsservertype=stcms,name=SeeBeyond_JMS_IQ_Manager,type=messaging-server-alert-mbean|#]
[#|2006-10-05T11:11:03.877+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|stcms server alert disabled|#]
[#|2006-10-05T11:11:03.877+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Set user.timezone=Europe/London|#]
[#|2006-10-05T11:11:03.887+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=11; ThreadName=STCMS process monitoring;|Starting STCMS server on Windows XP|#]
[#|2006-10-05T11:11:04.618+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=11; ThreadName=STCMS process monitoring;|Monitoring STCMS process ...|#]
[#|2006-10-05T11:11:06.370+0100|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Creating virtual server server|#]
[#|2006-10-05T11:11:06.441+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|IS AVK Instrumentation disabled|#]
[#|2006-10-05T11:11:06.461+0100|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-10-05T11:11:06.901+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC JTS Extension] The last agent commit optimization is enabled.|#]
[#|2006-10-05T11:11:07.782+0100|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]EE/SE Corba Util delegate loaded|#]
[#|2006-10-05T11:11:09.395+0100|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]Enabling SE Corba support|#]
[#|2006-10-05T11:11:09.605+0100|WARNING|IS5.1|javax.enterprise.resource.jms|_ThreadID=11; ThreadName=STCMS process monitoring;|STCMS process ended unexpectedly with exit code 1; initiating application server restart|#]
[#|2006-10-05T11:11:09.635+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=11; ThreadName=STCMS process monitoring;|sending restart notification to server...server|#]
[#|2006-10-05T11:11:09.685+0100|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=12; ThreadName=RMI TCP Connection(2)-127.0.0.1;|WEB0303: Stopping Tomcat.|#]
[#|2006-10-05T11:11:09.685+0100|WARNING|IS5.1|javax.enterprise.system.core|_ThreadID=12; ThreadName=RMI TCP Connection(2)-127.0.0.1;stacktrace-id=0;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:536)
     at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:65)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.Shutdown.startShutdown(Shutdown.java:41)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeShutdownEventListener(AdminEventMulticaster.java:769)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.handleShutdownEvent(AdminEventMulticaster.java:758)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:318)
     at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:107)
     at com.sun.enterprise.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:89)
     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:585)
     at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
     at sun.rmi.transport.Transport$1.run(Transport.java:153)
     at java.security.AccessController.doPrivileged(Native Method)
     at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
     at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
     at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
     at java.lang.Thread.run(Thread.java:595)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
     at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:529)
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:528)
     ... 19 more
|#]
[#|2006-10-05T11:11:09.685+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=12; ThreadName=RMI TCP Connection(2)-127.0.0.1;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2006-10-05T11:11:09.685+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=12; ThreadName=RMI TCP Connection(2)-127.0.0.1;|core.standalone_connector_modules_shutdown_complete|#]
[#|2006-10-05T11:11:09.685+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=12; ThreadName=RMI TCP Connection(2)-127.0.0.1;|CORE5052: Application shutdown complete.|#]
[#|2006-10-05T11:11:09.715+0100|WARNING|IS5.1|javax.enterprise.system.tools.admin|_ThreadID=12; ThreadName=RMI TCP Connection(2)-127.0.0.1;|core.tmp_folder_deletion_failed|#]
[#|2006-10-05T11:11:09.715+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=12; ThreadName=RMI TCP Connection(2)-127.0.0.1;|stcms.alert_shutting_down|#]
[#|2006-10-05T11:11:09.715+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=12; ThreadName=RMI TCP Connection(2)-127.0.0.1;|stcms.broker_shutting_down|#]
[#|2006-10-05T11:11:10.176+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5082: Exception running j2ee services: [java.lang.RuntimeException: java.lang.ExceptionInInitializerError]|#]
[#|2006-10-05T11:11:10.226+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=1;|CORE5091: Error executing J2EE server ...
java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     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:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:374)
     at com.sun.enterprise.iiop.ORBMonitoring.<init>(ORBMonitoring.java:48)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:236)
     ... 9 more
Caused by: java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:368)
     ... 11 more
Caused by: java.lang.NullPointerException: No MBeanServer was returned by the MBeanServerFactory
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.getMBeanServer(MonitoringRegistrationHelper.java:83)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<init>(MonitoringRegistrationHelper.java:60)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<clinit>(MonitoringRegistrationHelper.java:55)
     ... 14 more
|#]
[#|2006-10-05T11:11:10.226+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5092: J2EE server reported following error: [java.lang.ExceptionInInitializerError] |#]
[#|2006-10-05T11:11:10.226+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5093: Error executing J2EE server |#]
[#|2006-10-05T11:11:10.226+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=2;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: com.sun.appserv.server.ServerLifecycleException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:235)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     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:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.appserv.server.ServerLifecycleException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:763)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     ... 7 more
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     ... 8 more
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:374)
     at com.sun.enterprise.iiop.ORBMonitoring.<init>(ORBMonitoring.java:48)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:236)
     ... 9 more
Caused by: java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:368)
     ... 11 more
Caused by: java.lang.NullPointerException: No MBeanServer was returned by the MBeanServerFactory
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.getMBeanServer(MonitoringRegistrationHelper.java:83)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<init>(MonitoringRegistrationHelper.java:60)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<clinit>(MonitoringRegistrationHelper.java:55)
     ... 14 more
|#]
[#|2006-10-05T11:11:10.226+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server Startup failed. Exiting...|#]
[#|2006-10-05T11:11:10.226+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server shutdown in progress...|#]
[#|2006-10-05T11:11:10.236+0100|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|WEB0303: Stopping Tomcat.|#]
[#|2006-10-05T11:11:10.236+0100|WARNING|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=3;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:536)
     at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:65)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:255)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     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:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
     at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:529)
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:528)
     ... 9 more
|#]
[#|2006-10-05T11:11:10.236+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2006-10-05T11:11:10.236+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|core.standalone_connector_modules_shutdown_complete|#]
[#|2006-10-05T11:11:10.236+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5052: Application shutdown complete.|#]
[#|2006-10-05T11:11:10.236+0100|WARNING|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=4;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: java.rmi.NoSuchObjectException: object not exported
     at com.sun.enterprise.admin.server.core.channel.AdminChannel.destroyRMIChannel(AdminChannel.java:96)
     at com.sun.enterprise.admin.server.core.AdminService.stop(AdminService.java:294)
     at com.sun.enterprise.admin.server.core.AdminServiceLifeCycle.onShutdown(AdminServiceLifeCycle.java:124)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:255)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     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:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.rmi.NoSuchObjectException: object not exported
     at sun.rmi.transport.ObjectTable.unexportObject(ObjectTable.java:136)
     at java.rmi.server.UnicastRemoteObject.unexportObject(UnicastRemoteObject.java:280)
     at com.sun.enterprise.admin.server.core.channel.AdminChannel.destroyRMIChannel(AdminChannel.java:94)
     ... 10 more
|#]
[#|2006-10-05T11:11:10.236+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|stcms.alert_shutting_down|#]
[#|2006-10-05T11:11:10.236+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|stcms.broker_shutting_down|#]
Starting Integration Server 5.1 (build 20060319-0947) ...
[#|2006-10-05T11:11:20.131+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_06] from [Sun Microsystems Inc.]|#]
[#|2006-10-05T11:11:21.062+0100|INFO|IS5.1|javax.enterprise.system.tools.admin|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2006-10-05T11:11:21.182+0100|INFO|IS5.1|javax.enterprise.system.tools.admin|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|ADM0001:MBeanServer initialized successfully|#]
[#|2006-10-05T11:11:21.202+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|JMS5038: jms-service element in domain.xml is configured to have type=REMOTE. JMS service will be started locally only if type is LOCAL.|#]
[#|2006-10-05T11:11:21.202+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|STCMS configuration: dir=[../../domains/domain1/stcms/instance1]; bin=[C:\JavaCAPS51\logicalhost\is\domains\domain1/../../stcms/bin]; config dir=[C:\JavaCAPS51\logicalhost\is\domains\domain1/config]; config=[C:\JavaCAPS51\logicalhost\is\domains\domain1/config/stcms.default.Properties]|#]
[#|2006-10-05T11:11:21.573+0100|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Minimum nonce freshness limitation time period is set to: 300000|#]
[#|2006-10-05T11:11:21.573+0100|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Maximum nonce clock skew limitation time period is set to: 0|#]
[#|2006-10-05T11:11:21.573+0100|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Nonce cache sweep interval is set to: 180000|#]
[#|2006-10-05T11:11:21.583+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Registered STCMS configuration MBean com.sun.appserv:jmsservertype=stcms,name=SeeBeyond_JMS_IQ_Manager,type=messaging-server-config-mbean|#]
[#|2006-10-05T11:11:21.703+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|stcms journal service server disabled|#]
[#|2006-10-05T11:11:21.703+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Registered STCMS admin management MBean com.sun.appserv:jmsservertype=stcms,name=SeeBeyond_JMS_IQ_Manager,type=messaging-server-admin-mbean|#]
[#|2006-10-05T11:11:21.713+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Registered STCMS alert MBean com.sun.appserv:jmsservertype=stcms,name=SeeBeyond_JMS_IQ_Manager,type=messaging-server-alert-mbean|#]
[#|2006-10-05T11:11:21.713+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|stcms server alert disabled|#]
[#|2006-10-05T11:11:21.713+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Set user.timezone=Europe/London|#]
[#|2006-10-05T11:11:21.733+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=11; ThreadName=STCMS process monitoring;|Starting STCMS server on Windows XP|#]
[#|2006-10-05T11:11:21.753+0100|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=11; ThreadName=STCMS process monitoring;|Monitoring STCMS process ...|#]
[#|2006-10-05T11:11:23.205+0100|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Creating virtual server server|#]
[#|2006-10-05T11:11:23.225+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|IS AVK Instrumentation disabled|#]
[#|2006-10-05T11:11:23.235+0100|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-10-05T11:11:23.386+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC JTS Extension] The last agent commit optimization is enabled.|#]
[#|2006-10-05T11:11:23.876+0100|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]EE/SE Corba Util delegate loaded|#]
[#|2006-10-05T11:11:24.087+0100|WARNING|IS5.1|javax.enterprise.resource.corba.S1AS-ORB.rpc.transport|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=0;|"IOP00710209: (INTERNAL) Unable to create listener thread on the specific port"
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
     at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:3142)
     at com.sun.corba.ee.impl.logging.ORBUtilSystemException.createListenerFailed(ORBUtilSystemException.java:3160)
     at com.sun.corba.ee.impl.legacy.connection.SocketFactoryAcceptorImpl.initialize(SocketFactoryAcceptorImpl.java:60)
     at com.sun.corba.ee.impl.transport.CorbaTransportManagerImpl.getAcceptors(CorbaTransportManagerImpl.java:190)
     at com.sun.corba.ee.impl.transport.CorbaTransportManagerImpl.addToIORTemplate(CorbaTransportManagerImpl.java:207)
     at com.sun.corba.ee.spi.oa.ObjectAdapterBase.initializeTemplate(ObjectAdapterBase.java:104)
     at com.sun.corba.ee.impl.oa.poa.POAImpl.initialize(POAImpl.java:385)
     at com.sun.corba.ee.impl.oa.poa.POAImpl.makeRootPOA(POAImpl.java:253)
     at com.sun.corba.ee.impl.oa.poa.POAFactory$1.evaluate(POAFactory.java:163)
     at com.sun.corba.ee.impl.orbutil.closure.Future.evaluate(Future.java:28)
     at com.sun.corba.ee.impl.resolver.LocalResolverImpl.resolve(LocalResolverImpl.java:22)
     at com.sun.corba.ee.impl.resolver.CompositeResolverImpl.resolve(CompositeResolverImpl.java:20)
     at com.sun.corba.ee.impl.orb.ORBImpl.resolve_initial_references(ORBImpl.java:1112)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:209)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     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:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.RuntimeException: Failed to create server socket when calling ORBSocketFactory.createServerSocket(IIOP_CLEAR_TEXT, 18002)
     at com.sun.corba.ee.impl.legacy.connection.SocketFactoryAcceptorImpl.initialize(SocketFactoryAcceptorImpl.java:57)
     ... 20 more
Caused by: java.net.BindException: Address already in use: bind
     at sun.nio.ch.Net.bind(Native Method)
     at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
     at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
     at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:52)
     at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createServerSocket(IIOPSSLSocketFactory.java:274)
     at com.sun.corba.ee.impl.legacy.connection.SocketFactoryAcceptorImpl.initialize(SocketFactoryAcceptorImpl.java:53)
     ... 20 more
|#]
[#|2006-10-05T11:11:24.217+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5081: Exception while creating ORB: [org.omg.CORBA.INTERNAL:   vmcid: SUN minor code: 209 completed: No]|#]
[#|2006-10-05T11:11:24.217+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5082: Exception running j2ee services: [java.lang.RuntimeException: Unable to create ORB]|#]
[#|2006-10-05T11:11:24.217+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=1;|CORE5091: Error executing J2EE server ...
java.lang.RuntimeException: Unable to create ORB
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     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:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.RuntimeException: Unable to create ORB
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:224)
     ... 9 more
|#]
[#|2006-10-05T11:11:24.217+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5092: J2EE server reported following error: [Unable to create ORB] |#]
[#|2006-10-05T11:11:24.217+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5093: Error executing J2EE server |#]
[#|2006-10-05T11:11:24.217+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=2;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: com.sun.appserv.server.ServerLifecycleException: Unable to create ORB
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:235)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     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:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.appserv.server.ServerLifecycleException: Unable to create ORB
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:763)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     ... 7 more
Caused by: java.lang.RuntimeException: Unable to create ORB
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     ... 8 more
Caused by: java.lang.RuntimeException: Unable to create ORB
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:224)
     ... 9 more
|#]
[#|2006-10-05T11:11:24.217+0100|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server Startup failed. Exiting...|#]
[#|2006-10-05T11:11:24.217+0100|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server shutdown in progress...|#]
[#|2006-10-05T11:11:24.217+0100|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|WEB0303: Stopping T

According to your log...
"Unable to create ORB"
at com.sun.corba.ee.impl.legacy.connection.SocketFactoryAcceptorImpl.initialize
And related message...
(INTERNAL) Unable to create listener thread on the specific port"
Failed to create server socket when calling ORBSocketFactory.createServerSocket(IIOP_CLEAR_TEXT, 18002)
Address already in use: bind
Would indicate that the address 18002 is already used by another process.
So you can do:
1.restart your machine:
2. a netstat -an to validate that the port is free
You may have the localhost already started as a service on your machine...
TE

Creating logical host on zone cluster causing SEG fault

As noted in previous questions, I've got a two node cluster. I am now creating zone clusters on these nodes. I've got two problems that seem to be showing up.
I have one working zone cluster with the application up and running with the required resources including a logical host and a shared address.
I am now trying to configure the resource groups and resources on additional zone clusters.
In some cases when I install the zone cluster the clzc command core dumps at the end. The resulting zones appear to be bootable and running.
I log onto the zone and I create a failover resource group, no problem. I then try to create a logical host and I get:
"Method hafoip_validate on resource xxx stopped or terminated due to receipt of signal 11"
This error appears to be happening on the other node, ie: not the one that I'm building from.
Anyone seen anything like, this have any thoughts on where I should go with it?
Thanks.

Hi,
In some cases when I install the zone cluster the clzc command core dumps at the end. The resulting zones appear to be bootable and running.Look at the stack from your core dump and see whether this is matching with the bug:
6763940 clzc dumped core after zones were installed
As far as I know, the above bug is harmless and no functionality should be impacted. This bug is already fixed in the later release.
"Method hafoip_validate on resource xxx stopped or terminated due to receipt of signal 11" The above message is not enough to figure out what's wrong. Please look at the below:
1) Check the /var/adm/messages on the nodes and observe the messages that got printed around the same time that the above
message got printed and see whether that gives more clues.
2) Also see whether there is a core dump associated with the above message and that might also provide more information.
If you need more help, please provide the output for the above.
Thanks,
Prasanna Kunisetty

2 Logical Host, 2 Web Servers, Big Problem?

I am setting up a sun HA cluster using 2 E4500 servers. I have created 2 logical hosts, each one needs to host a Netscape iPlanet 4.0 web server sitting at port 80. Each logical host is serving up web applications for different clients.
If I need to fail over one of the logical hosts so that they are both running on the same system, the newly imported instance of the web server will fail because port 80 is already in use by the logical host that is on that physical host.
At first this seemed totally wrong. Each logical host should be able to run applications on any port they need to. Then someone who has a lot more time on Solaris told me that this was not the case, and each logical host had to steer clear of using the same ports as other logical hosts in the same cluster.
Can someone clue me into what is reality?
Any good documentation that tells how to set this stuff up?
Thanks!
Bruce

Hi,
The best way to resolve this would be to try implementing the same.
Instead of going through an entire cluster install/configuration
process, you may want to try setting up two different web servers
on a single node. You may want to set up a virtual interface (like
le0:1, hme0:1 etc) for this. You coud then try connecting to
individual web servers on port 80. If this works, then the two
webserver/two node cluster implementation should also work.
Hope this helps.
Thanks,
Gopinath.

Logical host name Question

Hi
Iam in process of creating 2 node cluster on 2 domains.This is for FailOver Clustering
I would appreciate if someone can throw some light and explain if Iam doing right and answer some of the Questions that I had
We have created 2 RG and we are in the process of creating logical host name. Here are the steps that I think Iam going to execute
1> The name of the logicalhost name resources are LH-01 , LH-02
The name of the logical host name are virtualhost-01 , virtualhost-02
The name of the domains are domainapp-01 , domainapp-02
2> Create entry in /etc/hosts for the new logical host name and IP address
Question : Is there any command which can be used to add entries to this files , instead of manually addding them. Iam not a Sys Admin and I do not know how many more places I have to add.
3>Create logicalhostname resources by following commands
a>clreslogicalhostname create -g RG-01 -h virtualhost-01 LH-01
b>clreslogicalhostname create -g RG-02 -h virtualhost-02 LH-02
4>Edit the /etc/nsswitch.conf
Question : I could not understand why we have to do this and what needs to be modified. Do I have to comment out the lines which says
host: cluster files
rpc : files
5>Question : Do I need to also create Shared Address Resource? I really did not understand the concept of Shared Address Resource
I would really appreciate if someone can throw some light on this. I have gone through the documents , but It really did not clear up for me
Thanks
Edited by: Cluster_newbie on Jun 25, 2008 4:06 PM

actually scinstall put this host: cluster files , i dont remember was the the logic
here is some explaination about shared address which used scalable applications like apache
The SUNW.SharedAddress Resource Type
Resources of type SUNW.SharedAddress represent a special type of IP
address that is required by scalable services. This IP address is configured
on the public net of only one node with failover capability, but provides a
load-balanced IP address that supports scalable applications that run on
multiple nodes simultaneously. This subject is described in greater detail
I hope this helps
Regards

Problem starting logical host on eGate 5.1.0

I'm having problem starting logical host for eGate 5.1.0 on Linux platform, and I cant see where is the problem lies. Is there anybody here that can give me some hint or guide?
Below is the error message from the log.
[#|2006-08-22T17:57:28.506+0800|WARNING|IS5.1|javax.enterprise.resource.jms|_ThreadID=11; ThreadName=STCMS process monitoring;|STCMS process ended unexpectedly with exit code 1; initiating application server restart|#]
[#|2006-08-22T17:57:28.567+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=11; ThreadName=STCMS process monitoring;|sending restart notification to server...server|#]
[#|2006-08-22T17:57:28.721+0800|WARNING|IS5.1|javax.enterprise.system.tools.admin|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|core.tmp_folder_deletion_failed|#]
[#|2006-08-22T17:57:28.722+0800|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|stcms.alert_shutting_down|#]
[#|2006-08-22T17:57:28.722+0800|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|stcms.broker_shutting_down|#]
[#|2006-08-22T17:57:31.020+0800|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Creating virtual server server|#]
[#|2006-08-22T17:57:31.039+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|IS AVK Instrumentation disabled|#]
[#|2006-08-22T17:57:31.045+0800|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2006-08-22T17:57:31.117+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC JTS Extension] The last agent commit optimization is enabled.|#]
[#|2006-08-22T17:57:32.315+0800|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]EE/SE Corba Util delegate loaded|#]
[#|2006-08-22T17:57:33.730+0800|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]Enabling SE Corba support|#]
[#|2006-08-22T17:57:34.007+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5082: Exception running j2ee services: [java.lang.RuntimeException: java.lang.ExceptionInInitializerError]|#]
[#|2006-08-22T17:57:34.008+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=0;|CORE5091: Error executing J2EE server ...
java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     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:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:374)
     at com.sun.enterprise.iiop.ORBMonitoring.<init>(ORBMonitoring.java:48)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:236)
     ... 9 more
Caused by: java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:368)
     ... 11 more
Caused by: java.lang.NullPointerException: No MBeanServer was returned by the MBeanServerFactory
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.getMBeanServer(MonitoringRegistrationHelper.java:83)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<init>(MonitoringRegistrationHelper.java:60)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<clinit>(MonitoringRegistrationHelper.java:55)
     ... 14 more
|#]
[#|2006-08-22T17:57:34.012+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5092: J2EE server reported following error: [java.lang.ExceptionInInitializerError] |#]
[#|2006-08-22T17:57:34.012+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5093: Error executing J2EE server |#]
[#|2006-08-22T17:57:34.013+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=1;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: com.sun.appserv.server.ServerLifecycleException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:235)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     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:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: com.sun.appserv.server.ServerLifecycleException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:763)
     at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
     ... 7 more
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
     at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
     ... 8 more
Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:374)
     at com.sun.enterprise.iiop.ORBMonitoring.<init>(ORBMonitoring.java:48)
     at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:236)
     ... 9 more
Caused by: java.lang.ExceptionInInitializerError
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:164)
     at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:368)
     ... 11 more
Caused by: java.lang.NullPointerException: No MBeanServer was returned by the MBeanServerFactory
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.getMBeanServer(MonitoringRegistrationHelper.java:83)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<init>(MonitoringRegistrationHelper.java:60)
     at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<clinit>(MonitoringRegistrationHelper.java:55)
     ... 14 more
|#]
[#|2006-08-22T17:57:34.023+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server Startup failed. Exiting...|#]
[#|2006-08-22T17:57:34.023+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server shutdown in progress...|#]
[#|2006-08-22T17:57:34.024+0800|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|WEB0303: Stopping Tomcat.|#]
[#|2006-08-22T17:57:34.025+0800|WARNING|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=2;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:536)
     at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:65)
     at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
     at com.sun.enterprise.server.PEMain.run(PEMain.java:255)
     at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
     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:585)
     at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
     at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:529)
     at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:528)
     ... 9 more
|#]
Hopefully somebody can help me as I'm stuck with it for few days already. Thank you.

This is what I got when I try to start the server from the directory logicalhost/is/domains/domain1/bin/
./startservAug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger <init>
INFO: Setting URL to http://localhost:18000
Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
INFO: Opening connection to http://localhost:18000
Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
INFO: Connection to http://localhost:18000 opened successfully.
Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
SEVERE: Connection refused
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:507)
at java.net.Socket.connect(Socket.java:457)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:214)
at sun.net.www.http.HttpClient.New(HttpClient.java:287)
at sun.net.www.http.HttpClient.New(HttpClient.java:299)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:792)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:744)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:669)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:913)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
at com.stc.is.util.pinger.HttpOKPinger.isAlive(Unknown Source)
at com.stc.is.util.Ping.main(Unknown Source)
Aug 23, 2006 7:23:55 PM com.stc.is.util.Ping main
INFO: IS is not alive.
Startup failed.
any clue what is it about?

Problem in mail resource configuration ??

Hi
Version: Oracle 9iAS Release 2(9.0.2, 9.0.3)
We used to specify the Mail-resource configuration in orion-application.xml, with required properties like smtp-host, user etc..
My application requires a mail session, I did specify the mail-resouce refence in ejb-jar.xml and map with JNDI-NAME in the orion-ejb-jar.xml.
If I deploy the application through EMWebsite, the maping of mail-resource(JNDI-NAME) with mail-resource reference in orion-ejb-jar.xml is getting lost.
It requires manual edit of orion-ejb-jar.xml and restart the OC4J component after deployment.
If I deploy through the emctl, the problem is not happening.
Is there any better way to do this.
Thanks in Advance
Madhu

Can anybody provide answer/suggestion for the above problem
Thanks
Madhu

Technical Monitoring for Logical host name

Dear experts,
We are in mid of technical monitoring finalisation.
one of the interesting thing which i found with respect to the logical host name, we installed SMD agent on Virtual host name and our system is not with HA environment and no clustering. It is just a system with single instance.
During the managed system configuration all the physical and logical host name reported by SMD autodiscovery, all went fine. But in Technical monitoring shows only virtual host name with the updated alerts , and logical host name only shows grey alert.
virtual host shows alert here
logical host name shows grey
how can i get alert displayed for logical host name too? do i need to do some settings at the OS level , could you guide us?
Thanks
Jansi

Hi Giri Raju Ayyagari,
I am sorry, seems you are still not able to get my issue, moreover you get diverting my issue
Here the problem is not at all related to agents on fly. thats the separate topic.
We are having issue on Logical Host names where there is no HA environment, means only One logical host name created.
I raised to SAP, l will update once the update from SAP given.
Best regards
Jansi

How to Configure Adapter for different environments?

Hi
I wanted to know solution to a pratical problem. If a communication channel is created by configuring a adapter, how is the configuration managed for different phases of the life cycle i,e when it goes from development to QA to Production. A adapter may need to be configured differently depending upon the environment it is in. I hope one doesn't have to change it every time it is taken from one environment to another. Is there any concept like properties file in XI?
Vijay

HI,
In general the Same evironment should be in both Dev and QA and also in Prod .
Whatever we developed in Dev environment , if you transport it to QA , the same should work, similarly in Prod also.
We have certain fecilities like cutomising the Communication channel with the Communication Channel Template.With this we can configure as per our needs.
Eventhough it is not sufficient to meet your BS requirement , then we need to have
Dynamic configuration see the below link for more details
Dynamic configuration in adapter modules - /people/daniel.graversen/blog/2006/10/05/dynamic-configuration-in-adapter-modules
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping -
/people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping
Regards
Chilla

Solaris Cluster - two machines - logical host

Good morning!
I am a complete dummie Solaris Cluster, buuuuuuuuuuuuuuuuuuuut... I need to create a cluster and install an application:
I have two V440, with Solaris 10;
I need to put the two machines in the cluster;
I have CE0 of each of the machines plugged into the network;
I have CE1 and CE2 of each machine connected together via a crossover cable;
According to the documentation "Oracle Solaris Cluster HA for Alliance Access" there are prerequisites (http://docs.oracle.com/cd/E19680-01/html/821-1547/ciajejfa.html) as creating HAstoragePlus , and logical host resource group;
Could anyone give me some tips on how to create this cluster and the prerequisites?
tanks!
Edited by: user13045950 on 05/12/2012 05:04
Edited by: user13045950 on 05/12/2012 05:06

Hi,
a good source of information for the beginner is: http://www.oracle.com/technetwork/articles/servers-storage-admin/how-to-install-two-node-cluster-166763.pdf
To create a highly available logical IP address just do
clrg create <name-for-resource-group>
clrslh create -g <name-for-resource-group> <name-of-ip-address> # This IP address should be available in /etc/hosts on both cluster nodes.
clrg online -M <name-for-resource-group>
Regards
Hartmut

Issue when naming resources the same on different zone clusters

Dear all
I found a very strange issue related to naming of resources and zone clusters, and would like to know weather what I am doing is supported.
I have a 4 node cluster and on the first two nodes I have zone cluster A. On the second two nodes I have zone cluster B. Each zone cluster has configured in it a unique shared address. On each zone cluster various scalable GDS services having same names are configured. When creating the GDS resource the following warning cropped up “Warning: Scalable service group for resource test has already been created” . When I put the resource on zone A up everything works fine but when I startup the resource on cluster B , then for some reason it registers the shared address of zone A on the nodes of zone B ie.. it gets confused.. and thus the service on zone A becomes unavailable from the shared address ip
Is the use of same names for resources on two different zone clusters supported? From my perspective this issue breaks the “Containment” concept of zone clusters, since zone cluster B can “confuse” zone cluster A
Regards
Daniel

Daniel,
Is the use of same names for resources on two different zone clusters supported? From my perspective this issue breaks the Containment concept of >zone clusters, since zone cluster B can confuse zone cluster AYes, the use of same resource name on two different zone clusters is supported.
I have a 4 node cluster and on the first two nodes I have zone cluster A. On the second two nodes I have zone cluster B. Each zone cluster has >configured in it a unique shared address. On each zone cluster various scalable GDS services having same names are configured. When creating >the GDS resource the following warning cropped up Warning: Scalable service group for resource test has already been createdAs mentioned above, using the same resource name is allowed and the above warning message should not be printed. I will open a bug against
the product for this.
When I put the resource on zone A up everything works fine but when I startup the resource on cluster B , then for some reason it registers the shared >address of zone A on the nodes of zone B ie.. it gets confused.. and thus the service on zone A becomes unavailable from the shared address ipThis is the issue we could not see in our lab and need reproducing steps. We were successfully able to create(except for seeing the above warning message) the shared address resources and scalable resources with the same names in two different zones and able to bring them up correctly. This is not GDS service, but a regular apache scalable service and the choice of the data service should not matter here. If you can provide the following, we would be happy to investigate further and send you information:
1) Reproducing steps (The exact order of the commands that were run to create and bring up the resources)
2) Is your shared address resource name was also same (Ofcourse the IP address has to be different) in addition to the GDS service name?
3) Any error messages that got printed.
4) syslog messages related to this failure (or the syslog messages that you have seen during this time frame)
Thanks,
Prasanna

Resource configuration for updating multiple tables

Hi all,
My aim is to update multiple tables in Sun Identity Manager
I would like to know what is the resource to be configured for this
Could any one help me in solving this issue
Thanks in advance,
Shalini

I have used the Scripted JBDC resource as follows;
go to Resources > Configure Types and select Scripted JDBC > Save
at Resources, select resource Type Actions > New Resource
select Scripted JDBC from the drop down, this should start the wizard
the wizard will guide you with lots of questions.
The one problem we had is in the Action Scripts (second wizard page). we found the example scripts
at the webserver root /idm/sample/ScriptedJdbc/SimpleTable/beanshell
the above scripts had to be modified to the SQL required for the application, but it worked well with the example databases and codes that it is easily understood.
there are several examples of different table types here... there are lots of options, see the README iles for each type
hope this helps;
TG

Similar logical host resource configured on 2 different resource groups

Similar Messages

Maybe you are looking for