Sun Cluster Application Development

Hi,
I am trying to create a sun cluster application using the GUI version of the Agent
builder, "rtwiz".
I successfully execute the create and configuration steps.
I install the package.
When I start the cluster application from the /opt/SUNWsample/util directory,
it fails in the step when it is trying to create a resource, the error message which
I get is "VALIDATE method failed".
Can somebody tell me what this problem is. Is the Validate method being run
from the /opt/SUNWsample/bin directory.
thanks.

The validation method checks the options be used to register the resource is correct. Are you using the correct option?

Similar Messages

What are typical failover times for application X on Sun Cluster

Our company does not yet have any hands-on experience with clustering anything on Solaris, although we do with Veritas and Miscrosoft. My experience with MS is that it is as close to seemless (instantaneous) as possible. The Veritas clustering takes a little bit longer to activate the standby's. A new application we are bringing in house soon runs on Sun cluster (it is some BEA Tuxedo/WebLogic/Oracle monster). They claim the time it takes to flip from the active node to the standby node is ~30minutes. This to us seems a bit insane since they are calling this "HA". Is this type of failover time typical in Sun land? Thanks for any numbers or reference.

This is a hard question to answer because it depends on the cluster agent/application.
On one hand you may have a simple Sun Cluster application that fails over in seconds because it has to do a limited amount of work (umount here, mount there, plumb network interface, etc) to actually failover.
On the other hand these operations may, depending on the application, take longer than another application due to the very nature of that application.
An Apache web server failover may take 10-15 seconds but an Oracle failover may take longer. There are many variables that control what happens from the time that a node failure is detected to the time that an application appears on another cluster node.
If the failover time is 30 minutes I would ask your vendor why that is exactly.
Not in a confrontational way but a 'I don't get how this is high availability' since the assumption is that up to 30 minutes could elapse from the time that your application goes down to it coming back on another node.
A better solution might be a different application vendor (I know, I know) or a scalable application that can run on more than one cluster node at a time.
The logic with the scalable approach is that if a failover takes 30 minutes or so to complete it (failover) becomes an expensive operation so I would rather that my application can use multiple nodes at once rather than eat a 30 minute failover if one node dies in a two node cluster:
serverA > 30 minute failover > serverB
seems to be less desirable than
serverA, serverB, serverC, etc concurrently providing access to the application so that failover only happens when we get down to a handful of nodes
Either one is probably more desirable than having an application outage(?)

Real Application Cluster on Sun Solaris 8 and Sun Cluster 3

Hello,
we want to install Oracle 9i Enterprise Edition in combination with Oracle Real Application Cluster-Option on 2 Nodes. Every node (12-CPU-SMP-Machine) should running Sun Solaris 8 and Sun Cluster 3 Service.
Does this configuration work with ORAC? I found nowhere informations about. Is there anything I have to pay special attention for during installation?
Thank you for helping and best regards from Berlin/Germany
Michael Wuttke

Forms and report services work fine on solaris 8.
My problem is on the client side.
I have to use solaris 8 with netscape like forms clients
and I wasn't able to make it work with java plugins.
Any solution?
Mauro

Where is "Sun ONE Application Server Developer's Guide to Clients"

Hi All,
"Sun ONE Application Server 7 Developer's Guide " refers
"Sun ONE Application Server Developer's Guide to Clients" many times. But I can not find it. Where is it?
Thanks.

I would also like to know where to find the "Developer's Guide to J2EE Features and Services" ?
Kind regards, Johann

Synchronize configuration changes among SUN One Application cluster

How to do the synchronization of configuration changes among the SUN One Application clustering.
I need to replicate the configuration changes from Appserver1 to appserver2, which is in the cluster farms.
Prakash

hi i'm a colleague of Mirza.
We have modified the web.xml and now server is asking for password. We dont want to specify a particular role name in authorization-constraint. We need all our authenticated users to access the application. When i remove the auth-constraint tag from the web.xml it does not not allow the user to acess the application and gives me the error "Access to the specified resource has been forbidden". To remedy this we have created a group called "authenticated" in our ldap directory server and put all the users in that group. Now even though i'm specifying in auth-constraint .. the role-name to be "authenticated" but its still not granting the user permission to the access the application.
here is the snippet of my web.xml
<security-constraint>
<web-resource-collection>
<web-resource-name>PAMS</web-resource-name>
<url-pattern>/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>authenticated</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name> ldap</realm-name>
</login-config>
<security-role>
<role-name>authenticated</role-name>
</security-role>
I need to know what ever I am doing is correct.

Sun Certified Mobile Application Developer

Respected Sir ,
i m souvik kundu from India i nead ur help
I already got SCJP certification now i want to give SCMAD(Sun Certified mobile application Developer) exam
Can u give me any guide line how i have to proceed to give this exam
I need some books plz tell me which book i have to follow or plz tell
me any site where i can download some e-Books . i am waiting 4ur
positive response.
thx
Souvik

when I took my SCMAD test, I recall there being a practice test as part of signing up for it, that was what I studied most. All the weird little rules to remember and such about what spec does this or that.

Running a Sun Cluster on one system using containers

Hello,
We would like to set up a test Sun Cluster Environment on one system using containers.
Has any one done this ? Is there documentation in the sun community on how to do this ?
Thank you
Bradley Duncan
Application Support
City University of New York

You can not install/configure a cluster just between non-global zones on the same physical node. The cluster software always needs to be installed in the global zone.
What you can do is install Solaris Cluster just on one physical node (a single-node cluster) and then you can configure native non-global zones and configure resource groups to failover between those non-global zones on the same node.
The resource group has a nodelist property, where you can configure node:zonea,node:zoneb - which will allow that RG to failover between zonea and zoneb on the same node.
A good start if your purpose is just to have a learning/development/experiment environment.
Regards
Thorsten

Problem with application developed with vtapi(Vt Systems) - events

Hello!
I'm developing aplication based on api prepared by VT Systems (http://www.cmsfx.com/en/trading-software/download-vt-trader/download-vt-trader-api/).
This api is used to perform forex transactions. I've written a Web
Service which connects with this api and
alows other modules of my application to perform transactions. I'm
using JAX-WS and Sun Java Application Server.
This is sample of Web Service :
@WebService()
public class ForexService{
protected static VT_API api;
Checker checker;
String userName = "***";
String userPassword = "***";
ConstRecord constants;
public static IVT_APIEventsAdapterExtended events;
public void initAPI(){
try{
System.loadLibrary("bridge2java");
OleEnvironment.Initialize();
api = new VT_API();
api.setForceDisableSSL(false);
events = new IVT_APIEventsAdapterExtended(api);
api.addIVT_APIEventsListener(events);
constants = new ConstRecord();
}catch(Exception e) {
e.printStackTrace();
public ForexService(){
initAPI();
logonResult = api.Login(userName, userPassword, 0) ;
System.out.println("Rezultat logowania: " + logonResult);
checker = new Checker(this);
new Thread(checker).start();
@WebMethod
public String getLogonResult() {
return new Integer(logonResult).toString();
@WebMethod
public String getServerList(){
return api.GetServerList();
I'm using event listener which was attached to Java Sample in
documentation.
public class IVT_APIEventsAdapterExtended extends
IVT_APIEventsAdapter{
private VT_API api;
public IVT_APIEventsAdapterExtended(VT_API apiInstance) {
api = apiInstance;
public void
OnInstrumentChange(IVT_APIEvents_OnInstrumentChangeEvent e)
super.OnInstrumentChange(e);
System.out.println("instrument change - " +
e.get_InstrumentID());
public void
OnNewServerMessage(IVT_APIEvents_OnNewServerMessageEvent e)
super.OnNewServerMessage(e);
System.out.println("Server message :" +
api.get_ServerMessages().get_Items(e.get_MsgID()).get_Text());
I've problem with listening events incoming from forex server. When I
run Wireshark(Network Protocol Analyzer) I can see that events income
to my computer (on different ports - for example: 2070, 2071, 2072),
but don't income to Sun Java Application Server. I suspect that server
don't listen on this ports, but how can I fix this? Maybe should I
choose a other server? I've tried also Tomcat -with similar result :(
Regards,
Peter
//Sorry for my english :)

Thank you very much for the reply :-)
We have been fiddling with the platform on many levels yesterday, and one thing we did do was bump that value up from 1024 to 8192... This made a HUGE improvement in ensuring the platform now holds the live streaming connections. (up to 8000 per edge)
I think for other future reference and to aid other people that might run into this problem in the future, its a good idea to increase this value. From what we have seen, read and heard, that default value is fairly conservative, its suppose to grow when the load demands it, however, if you have a large scale of connections coming in at once from multiple locations, it can happen that it grows too quickly which can result in the application to be reloaded (which disconnects all users, i.e. all edge servers connected to this origin).
Another option we were recommended to modify was the following :
In adaptor.xml you currently have this line:
<HostPort name="edge1" ctl_channel="localhost:19350" rtmfp="${ADAPTOR.HOSTPORT}">${ADAPTOR.HOSTPORT}</HostPort>
You can set this to
<HostPort name="edge1" ctl_channel="localhost:19350" rtmfp=":80">:80</HostPort>
<HostPort name="edge2" ctl_channel="localhost:19351" rtmfp=":1935">:1935</HostPort>
This will create two edge processes for both ports 80 and 1935. Currently both ports are served from the same fmsedge process.
Of course this is not a huge performance improvement, but should further distribute load over more processes which is a good thing. Especially when there are that many connections.
This setting can be made on all machines (origin + edge)
Hopefully this could help other people also running into the same problems we have seen ...

Creating Logical hostname in sun cluster

Can someone tell me, what exactly logical hostname in sun cluster mean?
For registering logical hostname resource in failoover group, what exactly i need to specify
for example, i have two nodes in sun cluster , How to create or configure a logical hostanme and it should point to which IP Address ( Whether it should point to IP addresses of nodes in sun cluster). Can i get clarification on this?

Thanks Thorsten for ur continue help...
The output of clrs status abc_lg
=== Cluster Resources ===
Resource Name Node Name State Status Message
abc_lg node1 Offline Offline
node2 Offline Offline
The status is offline...
the output of clresourcegroup status
=== Cluster Resource Groups ===
Group Name Node Name Suspended Status
abc_rg node1 No Unmanaged
node2 No Unmanaged
You say that the resource should de enabled after creating the resource.. I am using GDS and i am just following the steps he provided to acheive high availabilty (in developers guide...)
I have 1) Logical hostname resorce.
2) Application resource in my failover resource group
When i bring online the failover resource group , what should my failover resource group status and the status of resource in my resource group

Errors when trying to build HelloWorld application developped with SDS 4.1

Hi Community,
I getting some troubles when deploying a simple application developped by SDS on OCCAS 4.0,
When I deploy i get first a successful depoy message then get an internal error, please see the errors bellow:
Any idea ?
Thanks in advance,
Karim.
<Jun 21, 2009 1:10:27 PM EDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\occas\user_projects\domains\imt.vf.cable.rogers.com\servers\AdminServer\stage\_appsdir_HelloWorldServlet_war\HelloWorldServlet.war/WEB-INF/web.xml of module HelloWorldServlet.war. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
     at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1197)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:352)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=web-app@http://java.sun.com/xml/
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
     ... 33 more
.>
<Jun 21, 2009 1:10:27 PM EDT> <Error> <HTTP> <BEA-101064> <[WebAppModule(_appsdir_HelloWorldServlet_war:HelloWorldServlet.war)] Error parsing descriptor in Web appplication "C:\occas\user_projects\domains\imt.vf.cable.rogers.com\servers\AdminServer\stage\_appsdir_HelloWorldServlet_war\HelloWorldServlet.war"
weblogic.application.ModuleException: Unmarshaller failed
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1205)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:352)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     Truncated. see log file for complete stacktrace
com.bea.xml.XmlException: failed to load java type corresponding to e=web-app@http://java.sun.com/xml/
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
     Truncated. see log file for complete stacktrace
>
<Jun 21, 2009 1:10:27 PM EDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1245604227439' for task '0'. Error is: 'weblogic.application.ModuleException: [HTTP:101064][WebAppModule(_appsdir_HelloWorldServlet_war:HelloWorldServlet.war)] Error parsing descriptor in Web appplication "C:\occas\user_projects\domains\imt.vf.cable.rogers.com\servers\AdminServer\stage\_appsdir_HelloWorldServlet_war\HelloWorldServlet.war"
weblogic.application.ModuleException: Unmarshaller failed
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1205)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:352)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=web-app@http://java.sun.com/xml/
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
     at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1197)
     ... 26 more
weblogic.application.ModuleException: Unmarshaller failed'
weblogic.application.ModuleException: [HTTP:101064][WebAppModule(_appsdir_HelloWorldServlet_war:HelloWorldServlet.war)] Error parsing descriptor in Web appplication "C:\occas\user_projects\domains\imt.vf.cable.rogers.com\servers\AdminServer\stage\_appsdir_HelloWorldServlet_war\HelloWorldServlet.war"
weblogic.application.ModuleException: Unmarshaller failed
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1205)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:352)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=web-app@http://java.sun.com/xml/
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
     at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1197)
     ... 26 more
weblogic.application.ModuleException: Unmarshaller failed
     at weblogic.servlet.internal.WebAppModule.createModuleException(WebAppModule.java:1476)
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1228)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:352)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     Truncated. see log file for complete stacktrace
com.bea.xml.XmlException: failed to load java type corresponding to e=web-app@http://java.sun.com/xml/
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
     Truncated. see log file for complete stacktrace
>
<Jun 21, 2009 1:10:27 PM EDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application '_appsdir_HelloWorldServlet_war'.>
<Jun 21, 2009 1:10:27 PM EDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: [HTTP:101064][WebAppModule(_appsdir_HelloWorldServlet_war:HelloWorldServlet.war)] Error parsing descriptor in Web appplication "C:\occas\user_projects\domains\imt.vf.cable.rogers.com\servers\AdminServer\stage\_appsdir_HelloWorldServlet_war\HelloWorldServlet.war"
weblogic.application.ModuleException: Unmarshaller failed
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1205)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:352)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=web-app@http://java.sun.com/xml/
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
     at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1197)
     ... 26 more
weblogic.application.ModuleException: Unmarshaller failed
     at weblogic.servlet.internal.WebAppModule.createModuleException(WebAppModule.java:1476)
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1228)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:352)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     Truncated. see log file for complete stacktrace
com.bea.xml.XmlException: failed to load java type corresponding to e=web-app@http://java.sun.com/xml/
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
     Truncated. see log file for complete stacktrace
>
<Jun 22, 2009 7:50:36 AM EDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\occas\user_projects\domains\imt.vf.cable.rogers.com\servers\AdminServer\stage\_appsdir_HelloWorldServlet_war\HelloWorldServlet.war/WEB-INF/web.xml of module HelloWorldServlet.war. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
     at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1197)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:352)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=web-app@http://java.sun.com/xml/
     at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:361)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:316)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:326)
     at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:307)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:158)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
     ... 33 more
.>
<Jun 22, 2009 7:50:37 AM EDT> <Error> <HTTP> <BEA-101064> <[WebAppModule(_appsdir_HelloWorldServlet_war:HelloWorldServlet.war)] Error parsing descriptor in Web appplication "C:\occas\user_projects\domains\imt.vf.cable.rogers.com\servers\AdminServer\stage\_appsdir_HelloWorldServlet_war\HelloWorldServlet.war"
weblogic.application.ModuleException: Unmarshaller failed

You might want to look at my blog post at http://tinyurl.com/codesign .
Apart from that it might help if you could elaborate a bit more about the specific error you're experiencing. In my experience EVERY codesign problem is an issue of mis-configuration / restarting Xcode and can ultimately be resolved.

I am beginner to sun one studio and sun one application server

How can i access a cmp from a jsp page.
in sun one application server.
thanx in advance

where do you get the weblogic plugin from ?
i am intrested in doing the same thing
thanx
prem
"Ivan" <[email protected]> wrote in message
news:[email protected]..
>
Dear all,
My boss require me to use Sun One Studio 4 update 1 to do the development,but
I find it's a nightmare to deploy the EJB/ application to the WebLogic6.1.
>
I've already installed the weblogic plug-in in the Sun One Studio.
During deploying I could not find any setting that ask me for theweblogic-ejb-jar.xml.
So I think the deployment will fail.
Is there any others tutorial or e-book that can help me to familiar withthe deployment
process?
Many Thanks for all of you.
Ivan

Migrate Sun One application server from One Server to Another

Dear all,
We need to migrate the Sun ONE application from Sun Ultar server to Sun Fire 210. Please share with me if any one done the migration.
Thanks & Regards
Arun

I am sorry. My question was poorly worded after some hours of frustration. What I am really trying to do is develop a base virtual machine snapshot with Sun Web Server Loaded and a base set of applications.
When the need arises, I need to deploy another VM and start it up. There seems to be some issue with the host name of the VM and the administration server, or something. It is my impression that as longs as I have everything contained in one directory like /webserver, I should be able to copy everything to a new machine and start it up. I know I need the listeners listening on all ip addresses and the jdk being used would need to be in that directory as well. Is there anything I am missing here or that I need to watch out for?

Sun Cluster.. Why?

What are the advantages of installing RAC 10.2.0.3 on a Sun Cluster.? Are there any benefits?

Oracle 10g onward, there is no such burning requirement for Sun Cluster (or any third party cluster) as far as you are using all Oracle technologies for your Oracle RAC database. You should Oracle RAC with ASM for shared storage and that would not require any third party cluster. Bear inmind that
You may need to install Sun Cluster in the following scenarios:
1) If there is applicaiton running with in the cluster along with Oracle RAC database that you want to configure for HA and Sun Cluster provide the cluster resourced (easy to use) to manage and monitor the application. THIS can be achieved with Oracle Clusterware but you will have to write your own cluster resource for that.
2) If you want to install cluster file system such as QFS then you will need to install the Sun Cluster. If this cluster is only running the Oracle RAC database then you can rely on Oracle technologies such as ASM, raw devices without installing Sun Cluster.
3) Any certification conflicts.
Any correction is welcome..
-Harish Kumar Kalra

Issues in deploying files on sun one application server 8.2.

Hi,
We have developed a project using java, JSP & Struts Framework. The database used is oracle 9.i. We have created a single war file as it is a small application. Initially we had deployed this project on Tomcat Apachee server and now we have migrated Sun One application server 8.2.
During the deployment process we checked the "Verify" option. This option throws up certain errors for unknown reasons / resaons which we are not able to figure out. How ever if we do not check the "Verify" option the project gets deployed and runs sucessfully on the server.
Here is an extract of the Log file:
FAILED TESTS :
Test Name : tests.web.WebArchiveClassesLoadable
Test Assertion : All classes in this Web Archive are loadable. Please refer to J2EE 1.4 Specification Section #8.1.2 for further information.
Test Description : For [ careers.war ]
classes [ ] referenced by [ ] are not found
Please either bundle the above mentioned classes in the application or use optional packaging support for them.
Can some one throw some light onto this issue.
Thanks
Sanjay Subramanyam
Mobile: 98671-84285
email: [email protected]

can you run standalone verifier and let us know what results it produces? to run standalone verifier:
.../bin/verifier <path to your war file>
If it still produces those empty [] in the resukts, then please file a bug.
-- Sahoo

Beta Refresh Release Now Available! Sun Cluster 3.2 Beta Program

The Sun Cluster 3.2 Release team is pleased to announce a Beta Refresh release. This release is based on our latest and greatest build of Sun Cluster 3.2, build 70, which is close to the final Revenue Release build of the product.
To apply for the Sun Cluster 3.2 Beta program, please visit:
https://feedbackprograms.sun.com/callout/default.html?callid=%7B11B4E37C-D608-433B-AF69-07F6CD714AA1%7D
or contact Eric Redmond <[email protected]>.
New Features in Sun Cluster 3.2
Ease of use
* New Sun Cluster Object Oriented Command Set
* Oracle RAC 10g improved integration and administration
* Agent configuration wizards
* Resources monitoring suspend
* Flexible private interconnect IP address scheme
Availability
* Extended flexibility for fencing protocol
* Disk path failure handling
* Quorum Server
* Cluster support for SMF services
Flexibility
* Solaris Container expanded support
* HA ZFS
* HDS TrueCopy campus cluster
* Veritas Flashsnap Fast Mirror Resynchronization 4.1 and 5.0 option support
* Multi-terabyte disk and EFI label support
* Veritas Volume Replicator 5.0 support
* Veritas Volume Manager 4.1 support on x86 platform
* Veritas Storage Foundation 5.0 File System and Volume Manager
OAMP
* Live upgrade
* Dual partition software swap (aka quantum leap)
* Optional GUI installation
* SNMP event MIB
* Command logging
* Workload system resource monitoring
Note: Veritas 5.0 features are not supported with SC 3.2 Beta.
Sun Cluster 3.2 beta supports the following Data Services
* Apache (shipped with the Solaris OS)
* DNS
* NFS V3
* Java Enterprise System 2005Q4: Application Server, Web Server, Message Queue, HADB

Without speculating on the release date of Sun Cluster 3.x or even its feature list, I would like to understand what risk Sun would take when Sun Cluster would support ZFS as a failover filesystem? Once ZFS is part of Solaris 10, I am sure customers will want to use it in clustered environments.
BTW: this means that even Veritas will have to do something about ZFS!!!
If VCS is a much better option, it would be interesting to understand what features are missing from Sun Cluster to make it really competitive.
Thanks
Hartmut

Sun Cluster Application Development

Similar Messages

Maybe you are looking for