Unable to deploy VIO OpenStack due to anti-affinity rule

Hello,
I am trying to deploy OpenStack through vSphere web client. The deployment fails due to an error "Deploy OpenStack instance failed. Insufficient number of ESXi hosts to meet the anit-affinity rule."
I saw a previous post related to the same issue where it is mentioned that you need atleast 800GB of datastore space on the hosts combined in a cluster.
I have 2 Hosts in Management cluster adding up to 1000GB and 2 Hosts in Computer Cluster about 800GB datastore space combined. I have one host in Edge Cluster with datastore space of 250GB.
How much datastore space should each cluster comprise off to deploy OpenStack instances without failing? Are there any other credentials like CPU/Memory/Disk space that must be considered for the deployment?
I would really appreciate any help.
Thanks,
Radhika

Hi,
I have followed the OpenStack Quick Start Guide and deployed hosts and enabled DRS, host monitoring etc along with enabling vMotion and FT. I did deploy another ESXi host under Management cluster. Now, management cluster comprises of 3 Hosts with total 1080GB datastore space, Compute cluster with 2 hosts and about ~800GB datastore space and Edge cluster with 1 Host - 250GB datastore space.
Now, while deploying the OpenStack, it fails due to "Cannot find datastore with enough space and meets datastore anti-affinity rule for [VIO-Controller 0]"
Attached is the error message. Datastore has enough space, but I don't understand why I am getting this. How do I fix this?
Thanks,
Radhika

Similar Messages

Deploy OpenStack GA release failed due to anti-affinity rule

When I deploy the OpenStack GA release, following error popped up at the last step on the deployment wizard page.
"Deploy OpenStack instance failed. Insufficient number of ESXi hosts to meet the anti-affinity rule"
I have 3 ESXi hosts in management cluster and 1 host in compute cluster, which I used to deploy the beta version without any problem.
Is there any workaround for this without adding more hosts?

I have the same/similar error:
"PlacementException: Cannot find datastore with enough space and meets the datastore anti-affinity rule for [VIO-Controller-0]. Nodes with the same role cannot be placed onto the same datastore."
According to the oms.log [VIO-DB-0], [VIO-DB-1] and [VIO-DB-2] can be properly placed but the problem is always with [VIO-Controller-0]. Whatever I have done (more disc space, more ESXi servers, more datastores) - the problem did not disappear.
Unfortunately I was not able to find any document which explains the requirements for datastore (anti) affinity - there is only 1 page in the documents which describe the storage requirements e.g. db server requires 80 GB (although actually [VIO-DB-0] could only be placed if the disc has 100GB).
But no word on affinity rules or number of required datastores or datastore size.
I am using a test environment with 3 to 5 nested ESXi v6.0 (!!) for the management cluster with a total of around 1.2 TB free disc space for the management cluster.
To me it appears that there exists "somewhere" an undocumented affinity/anti-affinity rule for the placement of the management VMs, especially for [VIO-Controller-x].
I would appreciate if someone could describe the disc/datastore configuration for a successful implementation of OpenStack GA release!
I do attach an older oms.log with above error message (not sure which configuration I tested at that time, probably 3 ESXi with 3 or 4 datastores with 100GB disc space each per ESXi).

The server was unable to process the request due to an internal error.

Properties set in my project are below
namespace EmployeeService
public class Employee
private int _Id;
private string _Name;
private string _Gender;
private DateTime _DateofBirth;
public int Id
get { return _Id; }
set { _Id = value; }
public string Name
set { _Name = value; }
get { return _Name; }
public string Gender
set { _Gender = value; }
get { return _Gender; }
public DateTime DateofBirth
set { _DateofBirth = value; }
get { return _DateofBirth; }
This is the service i have developed in my project
namespace EmployeeService
// NOTE: You can use the "Rename" command on the "Refactor" menu to change the class name "Service1" in both code and config file together.
public class EmployeeService : IEmployeeService
public Employee GetEmployee(int Id)
Employee objemp = new Employee();
string cs = ConfigurationManager.ConnectionStrings["DBCS"].ConnectionString;
using (SqlConnection con = new SqlConnection(cs))
SqlCommand cmd = new SqlCommand("spGettblEmployeewcf", con);
cmd.CommandType = CommandType.StoredProcedure;
SqlParameter Idparameter = new SqlParameter();
Idparameter.ParameterName = "@Id";
Idparameter.Value = Id;
cmd.Parameters.Add(Idparameter);
con.Open();
SqlDataReader dr = cmd.ExecuteReader();
while (dr.Read())
objemp.Id = Convert.ToInt32(dr["Id"]);
objemp.Name = dr["Name"].ToString();
objemp.Gender = dr["Gender"].ToString();
objemp.DateofBirth = Convert.ToDateTime(dr["DateofBirth"]);
return objemp;
public void SaveEmployee(Employee objemp)
string cs = ConfigurationManager.ConnectionStrings["DBCS"].ConnectionString;
using (SqlConnection con = new SqlConnection(cs))
SqlCommand cmd = new SqlCommand("spInsertEmployeewcf", con);
cmd.CommandType = CommandType.StoredProcedure;
SqlParameter ParameterId = new SqlParameter()
Value = objemp.Id,
ParameterName = "@Id"
cmd.Parameters.Add(ParameterId);
SqlParameter ParameterName = new SqlParameter()
Value = objemp.Name,
ParameterName = "@Name"
cmd.Parameters.Add(ParameterName);
SqlParameter ParameterGender = new SqlParameter()
Value = objemp.Gender,
ParameterName = "@Gender"
cmd.Parameters.Add(ParameterGender);
SqlParameter ParameterDateofBirth = new SqlParameter()
Value = objemp.DateofBirth,
ParameterName = "@DateofBirth"
cmd.Parameters.Add(ParameterDateofBirth);
con.Open();
cmd.ExecuteNonQuery();
The Service Contract code is
namespace EmployeeService
// NOTE: You can use the "Rename" command on the "Refactor" menu to change the interface name "IService1" in both code and config file together.
[ServiceContract]
public interface IEmployeeService
[OperationContract]
Employee GetEmployee(int Id);
[OperationContract]
void SaveEmployee(Employee objemp);
// TODO: Add your service operations here
// Use a data contract as illustrated in the sample below to add composite types to service operations
and i deployed the EmployeeService in iis and consuming the service in my web application the code is below
protected void btnsave_Click(object sender, EventArgs e)
EmployeeService.EmployeeServiceClient client = new EmployeeService.EmployeeServiceClient("basicHttpBinding");
EmployeeService.Employee employee = new EmployeeService.Employee();
employee.Id = Convert.ToInt32(txtid.Text);
employee.Name = txtname.Text;
employee.Gender = txtgender.Text;
employee.DateofBirth = Convert.ToDateTime(txtdob.Text);
client.SaveEmployee(employee);
protected void btnget_Click(object sender, EventArgs e)
EmployeeService.EmployeeServiceClient client = new EmployeeService.EmployeeServiceClient("basicHttpBinding");
EmployeeService.Employee employee = client.GetEmployee(Convert.ToInt32(txtid.Text));
txtname.Text = employee.Name;
txtgender.Text = employee.Gender;
txtdob.Text = employee.DateofBirth.ToShortDateString();
and when i am entering the details of employee Id,Name,Gender,DateofBirth and clicking save button iam getting the following error
The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior)
on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.
Code in web.config file in Webapplication(Client) is the following
<?xml version="1.0"?>

<configuration>
<system.diagnostics>
<sources>
<source name="System.ServiceModel.MessageLogging" switchValue="Warning, ActivityTracing">
<listeners>
<add type="System.Diagnostics.DefaultTraceListener" name="Default">
<filter type="" />
</add>
<add name="ServiceModelMessageLoggingListener">
<filter type="" />
</add>
</listeners>
</source>
<source name="System.ServiceModel" switchValue="Warning, ActivityTracing"
propagateActivity="true">
<listeners>
<add type="System.Diagnostics.DefaultTraceListener" name="Default">
<filter type="" />
</add>
<add name="ServiceModelTraceListener">
<filter type="" />
</add>
</listeners>
</source>
</sources>
<sharedListeners>
<add initializeData="C:\Users\HEMANTH\Desktop\Client\Client\Web_messages.svclog"
type="System.Diagnostics.XmlWriterTraceListener, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
name="ServiceModelMessageLoggingListener" traceOutputOptions="Timestamp">
<filter type="" />
</add>
<add initializeData="C:\Users\HEMANTH\Desktop\Client\Client\Web_tracelog.svclog"
type="System.Diagnostics.XmlWriterTraceListener, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
name="ServiceModelTraceListener" traceOutputOptions="Timestamp">
<filter type="" />
</add>
</sharedListeners>
<trace autoflush="true" />
</system.diagnostics>
<system.web>
<compilation debug="true" targetFramework="4.0" />
</system.web>
<system.serviceModel>
<diagnostics>
<messageLogging logEntireMessage="true" logMalformedMessages="true"
logMessagesAtTransportLevel="true" />
</diagnostics>
<bindings>
<basicHttpBinding>
<binding name="basicHttpBinding" />
</basicHttpBinding>
<wsHttpBinding>
<binding name="mexHttpBinding">
<security mode="None" />
</binding>
</wsHttpBinding>
</bindings>
<client>
<endpoint address="http://localhost/EmployeeWebServices/EmployeeService.svc/basic"
binding="basicHttpBinding" bindingConfiguration="basicHttpBinding"
contract="EmployeeService.IEmployeeService" name="basicHttpBinding" />
<endpoint address="http://localhost/EmployeeWebServices/EmployeeService.svc/mex"
binding="wsHttpBinding" bindingConfiguration="mexHttpBinding"
contract="EmployeeService.IEmployeeService" name="mexHttpBinding" />
</client>
</system.serviceModel>
</configuration>
Things i have tried till now are
1)changed the name of the name of the endpoint address basicHttpBinding to basicHttpBinding_IEmployeeService but still get the save error.
2)Opened the Message Log Trace. Got the error as follows
<MessageLogTraceRecord>
<HttpResponse xmlns="http://schemas.microsoft.com/2004/06/ServiceModel/Management/MessageTrace">
<StatusCode>InternalServerError</StatusCode>
<StatusDescription>Internal Server Error</StatusDescription>
<WebHeaders>
<Content-Length>730</Content-Length>
<Cache-Control>private</Cache-Control>
<Content-Type>text/xml; charset=utf-8</Content-Type>
<Date>Sat, 03 Jan 2015 12:12:24 GMT</Date>
<Server>Microsoft-IIS/7.5</Server>
<X-AspNet-Version>4.0.30319</X-AspNet-Version>
<X-Powered-By>ASP.NET</X-Powered-By>
</WebHeaders>
</HttpResponse>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header></s:Header>
<s:Body>
<s:Fault>
<faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher" xmlns="">a:InternalServiceFault</faultcode>
<faultstring xml:lang="en-US" xmlns="">The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute
or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.</faultstring>
</s:Fault>
</s:Body>
</s:Envelope>
</MessageLogTraceRecord>
Try to understand but could not understand because i'am new to wcf services. Please help me to find the error details.
Thanks in advance
Regards
rax227

Hi Mohan,
I didn't use Fiddler before, I just download and use it but how to see the request message from this software?
I have logged the request to event log before send to web service and copy this request from event log to testing with soapUI, so I don't think have between the actual messages being sent to your client via orchestration and soapui. In the log Response shape
I see the fault response in event log.
You can see
this link to know how to use fiddler. As I suggested above the error you need to check is at the server side who is hosting the service( your party ) because you are getting fault response properly from them. The webservice you are calling seems to look
like WCF service too. Your life would have been so easier if you could ask them to have firewall open from your dev box to their dev server so that you can use use "Add Service Reference" wizard, that even they have .NET wcf service too.
Did you by any chance manage to talk to them what they are getting or if they can increase the exception details in the fault message for you?
If this answers your question please mark it as Answer and if this post is helpful, please vote as helpful. Thanks !

Unable to deploy a form on the Web!!

Hi,
I am unable to deploy my form onto the web.
The following is the error message :
Oracle Forms Web CGI: Error detected
Your request cannot be serviced at this time due to the following error:
ERROR: Cannot open baseHTML file %FORMS60%\server\tester.htm.
Pls help me out in solving the problem.
Thanks in advance
Vishant

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Vishant Shenoy ([email protected]):
Hi,
I am unable to deploy my form onto the web.
The following is the error message :
Oracle Forms Web CGI: Error detected
Your request cannot be serviced at this time due to the following error:
ERROR: Cannot open baseHTML file %FORMS60%\server\tester.htm.
Pls help me out in solving the problem.
Thanks in advance
Vishant<HR></BLOCKQUOTE>
The most likely thing is that the file tester.htm is not in the directory %FORMS60%\server\
null

Not able to deploy VIO 1.0.1 with NSX integration

Hello,
Whenever I try to deploy VIO with NSX integration I stuck on "Configure Neutron networking" step.
Edge Cluster drop-down menu does not contain any options and so I cannot proceed with the deployment. (DVS works fine)
As this a POC deployment, I use the same cluster for Management nodes, NSX Edge nodes and users VMs.
According to the documentation that configuration is supported, even it is not recommended.
Thanks,
Max

Please check if you have the prerequisites met for NSX integration for VIO.
Create a Virtual Distributed Switch(s) and add all hosts from both the management and compute clusters.
On separate VLANs, create three port groups: Management, External, and Public API Network. The fourth port group, VXLAN Transport, is created inline with the NSX installation:
The Management network carries traffic among the management components. This network requires 13 or more static IP addresses.
The Public API network exposes the OpenStack dashboard and provides access for tenants to the OpenStack APIs and services. This network requires 3 or more static IP addresses.
The External network provides external access for the instances. This network requires 8 or more static IP addresses.
The Transport network is used to carry traffic among the instances. This network requires 1 address for each host in the Edge and Compute clusters
Note: Some designs you may collapse both the Public API Network and External network into a single network segment.
-nathan

Unable to deploy ear on weblogic 8.1 sp3

hi .
i have an application in struts 1.1 which was working fine in weblogic 8.1 sp3. now i have upgraded to struts 1.2.8 and when i am trying to deploy the applicaiton following error is thrown.
Unable to initialize Struts ActionServlet due to an unexpected exception or error thrown, so marking the servlet as unavailable. Most likely, this is due to an incorrect or missing library dependency.
java.lang.NoSuchMethodError: <init>
at org.apache.commons.digester.Digester.<init>()V(Digester.java:150)
at org.apache.struts.action.ActionServlet.initServlet()V(ActionServlet.java:1111)
at org.apache.struts.action.ActionServlet.init()V(ActionServlet.java:328)
at javax.servlet.GenericServlet.init(Ljavax.servlet.ServletConfig;)V(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run()Ljava.lang.Object;(ServletStubImpl.java:1018)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.jav
at weblogic.servlet.internal.ServletStubImpl.createServlet()Ljavax.servlet.Servlet;(ServletStubImpl.java:894)
at weblogic.servlet.internal.ServletStubImpl.createInstances()V(ServletStubImpl.java:873)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(Lweblogic.servlet.internal.RequestCallback;)V(ServletStubImpl.java:812)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(Ljava.lang.String;)V(WebAppServletContext.java:3281)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(Ljava.util.Vector;)V(WebAppServletContext.java:3238)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets()V(WebAppServletContext.java:3224)
at weblogic.servlet.internal.WebAppServletContext.preloadResources()V(WebAppServletContext.java:3207)
at weblogic.servlet.internal.HttpServer.preloadResources()V(HttpServer.java:694)
at weblogic.servlet.internal.WebService.preloadResources()V(WebService.java:483)
at weblogic.servlet.internal.ServletInitService.resume()V(ServletInitService.java:30)
at weblogic.t3.srvr.SubsystemManager.resume()V(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume()V(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:361)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
I have checked the digester and the clas spath. i am using the digester-1.6 which is shipped with struts 1.2.8
Edited by surya_shikha at 04/02/2008 4:08 AM

hi,
Maybe your commons-digester is not the same version as provided with struts-1.2.8

Unable to deploy EJB: AdobeIDP2UI_HealthMonitorComponent from HealthMonitorComponent.jar

Hi we have a weblogic clostered installation of LC ES2 on Linux and we're recieving a weblogic error when trying to start it up
####<Sep 9, 2013 8:42:12 PM EDT> <Warning> <Deployer> <vmelxap367.rogers.com> <adobe-admin> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1378773732809> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(HealthMonitorComponent.jar)
Unable to deploy EJB: AdobeIDP2UI_HealthMonitorComponent from HealthMonitorComponent.jar:
[EJB:011055]Error deploying the EJB 'AdobeIDP2UI_HealthMonitorComponent(Application: adobe-livecycle-weblogic, EJBComponent: HealthMonitorComponent.jar)', the JNDI name 'ejb/AdobeIDP2UI_HealthMonitorComponent' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
And in the LC logs there is
####<Sep 10, 2013 7:35:36 AM EDT> <Error> <Deployer> <vmelxap369.rogers.com> <adobe-ms3> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1378812936887> <BEA-149205> <Failed to initialize the application 'adobe-livecycle-weblogic' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(CoreSystemConfigComponent.jar)
Unable to deploy EJB: AdobeIDP2UI_CoreSystemConfigComponent from CoreSystemConfigComponent.jar:
registerEjbRolesAndUsers: Exception while attempting to deploy Security Role: weblogic.security.service.RoleCreationException: weblogic.security.spi.RoleCreationException: [Security:090320]Failed to create role
weblogic.application.ModuleException: Exception preparing module: EJBModule(CoreSystemConfigComponent.jar)
Unable to deploy EJB: AdobeIDP2UI_CoreSystemConfigComponent from CoreSystemConfigComponent.jar:
registerEjbRolesAndUsers: Exception while attempting to deploy Security Role: weblogic.security.service.RoleCreationException: weblogic.security.spi.RoleCreationException: [Security:090320]Failed to create role
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.ja va:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.j ava: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.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java: 155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.jav a:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java: 39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeploy ments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.j ava:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.ja va:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerServic e.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService .java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.jav a:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
weblogic.ejb.container.interfaces.NoSuchRoleException: registerEjbRolesAndUsers: Exception while attempting to deploy Security Role: weblogic.security.service.RoleCreationException: weblogic.security.spi.RoleCreationException: [Security:090320]Failed to create role
at weblogic.ejb.container.internal.SecurityHelperWLS.deployRoles(SecurityHelperWLS.java:181)
at weblogic.ejb.container.internal.SecurityHelper.deployRoles(SecurityHelper.java:194)
at weblogic.ejb.container.internal.SecurityHelper.deployRoles(SecurityHelper.java:169)
at weblogic.ejb.container.internal.RuntimeHelper.deployRoles(RuntimeHelper.java:191)
at weblogic.ejb.container.deployer.EJBDeployer.deployRoles(EJBDeployer.java:780)
at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:940)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1188)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:425)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.ja va:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.j ava: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.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java: 155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.jav a:60)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:141)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java: 39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeploy ments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.j ava:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.ja va:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerServic e.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService .java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.jav a:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any help that could be provided would be greatly appreciated. Thanks!

It normally indicates something wrong with your auth provider settings. I believe there are similar messages on this forum , search them(the last time was someone had a different schema for his user tables than the normal portal schema). See if there are any other errors (before) or the complete stack trace.
Check whether your security realm is configured correctly and all the expected users and roles are present there.

TestStand 3.5 unable to deploy overridden LabVIEW methods

Just found a slight in-compatibility between TestStand and LabVIEW.
I've created and deployed many LabVIEW classes using TestStand 3.5 without any problems including using inheritance.
But I've just discovered that if you inherit a class and then override one of its methods then TestStand is unable to deploy this.
As TestStand 3.5 was around before LabVIEW 8.2 I'm not overly suprised it doesn't work in this case, although it does seem to work with most of the other class functionality, but thought I'd just flag it up in case anyone else is thinking of using LabVIEW inheritance and overriding with TestStand 3.5.
Maybe it works in 4.0?
David Clark
CLA | CTA
CLA Design Ltd
Hampshire, England

Hi Jon,
That's a fairly sneeky way round it, but unfortunately due to the way we deploy our test software it just wouldn't be workable, and would in fact completely destroy the whole point of our system architecture so it's a no-go unfortunately.
Many thanks for looking into it anyway, hopefully R&D will come up with a fix for a future TestStand release - as I've said it is a real shame as i'm using the LabVIEW classes by default now, and have just been starting to realise the full potential of using the classes in a number of software modules I've been working on, but if the override functionality is not compatible with TestStand then I'm going to have to regress slightly from where I was.
Damn shame,
David Clark
CLA | CTA
CLA Design Ltd
Hampshire, England

Unable to deploy changes to SLD

Hi,
This seems to be strange problem for me, but I think some one here would have come across this issue.
I am unable to deploy changes to SLD even thoug the requet was success. I had this problem earlier and found out that this is due to faileure automatic deployemnt.
But this time, it doesnot seem to be similar. My coleague, who is working on the same track, but on a different SC is able to deploy, and automatic depployment settings are same for both SC as they are in same track.
I wonder what is causing this problem.
Also, my NWDS hangs frequently when I try to activiate an open activity forcing me to close and activate again from activation view. Also, it hangs when I try to open Activation Requests perspective...
This is causing lot of problem and my developments are taking more than twice the actual time.
I hope some one can help me with this..
Thanks in advance,
Chinnu

Hello,
Fixed it myself, issue is caused by a library dc properties that is used in my DC. I have checkd all the options, runtime design time buildtime deploytime. I have changed it to buildtime, and unchecked other three properties. It got fixed
Best regards,
Chinnu

Unable to deploy from Eclipse - Runner class cannot be initialized

Hello
two days ago, I installed the newest versions of Glassfish Tools together with the newest Eclipse Luna SR1
when trying to deploy, I am getting the following error message:
org.glassfish.tools.ide.admin.CommandException: Cannot initialize Runner class
at org.glassfish.tools.ide.admin.AdminFactory.newRunner(AdminFactory.java:180)
at org.glassfish.tools.ide.admin.AdminFactoryHttp.getRunner(AdminFactoryHttp.java:110)
at org.glassfish.tools.ide.admin.ServerAdmin.exec(ServerAdmin.java:75)
at oracle.eclipse.tools.glassfish.GlassfishServerBehaviourDelegate.publishDeployedDirectory(GlassfishServerBehaviourDelegate.java:608)
at oracle.eclipse.tools.glassfish.GlassfishV4ServerBehavior.publishModuleForGlassFishV3(GlassfishV4ServerBehavior.java:96)
at oracle.eclipse.tools.glassfish.GlassfishV4ServerBehavior.publishModule(GlassfishV4ServerBehavior.java:56)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
the same application works if deployed directly to the glassfish server
I did all the suggestions as mentioned in Unable to deploy app form Eclipse Luna on Glassfish 4.0 or 4.1 with JDK8 but without success.
Does anybody has an idea what the problem could be and how to track it down?
Thanks a lot!

Hello Kostas
Thanks a lot for your help and hints! I am running Windows 7 64 Bit
I had Java 8, once with Release 20 and once with Release 25, installed - and thought that I pointed all to the newest version.
What helped in the end was to
- deinstall all Javas
- reboot
- installed newest JDK, without the "Public JRE"
- reboot
- set JAVA_HOME and appended the Java-bin-dir to the path-Variable
- reboot
- installed a fresh version of Glassfish
- configured a new Glassfish-Server on Eclipse
-> and now it runs perfectly!
Thanks again for your work and hints!

Unable to deploy Web App in Exploded format

Using WLS 6.1 sp2, I am unable to deploy a web application successfully using the
web app "ora" from http://www.thejspbook.com/examples.jspbook.zip. I've moved
the /ora directory under the /WEB-INF/applications directory.
The error I am getting is:
java.lang.reflect.InvocationTargetException: weblogic.management.DistributedManagementException:
Distributed Management [1 exceptions]
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:543)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.addDeployment(Unknown Source)
     at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
     at $Proxy18.setTargets(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Distributed update exception
- remote object: efs-developer3:Location=efsserver,Name=efsserver,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@5420eb
- actionName: addDeployment
- params: [Ljava.lang.Object;@10c03e
- signature: [Ljava.lang.String;@3d4a20
Distributed update exception
- remote object: efs-developer3:Location=efsserver,Name=efsserver,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@5420eb
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
     at java.lang.String.substring(String.java:1525)
     at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:476)
     at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:232)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3415)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3384)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
     at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:815)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
     at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy34.addWebDeployment(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.addDeployment(Unknown Source)
     at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
     at $Proxy18.setTargets(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.j2ee.DeploymentException: Could not load ora - with nested exception:
[java.lang.StringIndexOutOfBoundsException: String index out of range: -1]
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:431)
     at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy34.addWebDeployment(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.--------------- nested within: ------------------
weblogic.management.console.utils.SetException: An error occurred while updating
Targets-Server on Proxy for efs-developer3:Application=ora,Name=ora,Type=WebAppComponent
- with nested exception:
[java.lang.reflect.InvocationTargetException - with target exception:
[weblogic.management.DistributedManagementException: Distributed Management [1
exceptions]]]
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:151)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help is appreciated.
Thanks,
Dennis

you are probably using a older version of 6.1. please use the latest service pack. Service Packs are mostly bug fix releases and they are safe to be upgraded even on production systems. Please note - we always recommend using the latest service pack
http://www.sun.com/download/products.xml?id=47d5d3eb

I have just switched over to iCloud and I am now getting an error message in iCal which is the following: The server is currently unable to handle the connection due to a temporary overloading or maintenance of the server. If this continues you should con

I have recently switched from MobileMe to iCloud and I now getting an error message in iCal :
"The server is currently unable to handle the connection due to a temporary overloading or maintenance of the server. If this continues you should contact the server administrator.
You may try to connect to the server again or take the account offline."
Since I am working from home and I am not on a server other than iCloud I don't understand why I am getting this message. (for 3 days). How do I fix it?

TomCT60,
Is your MacBook using Mac OS X 10.6.8 as indicated in your post? If so you will not be able to fully integrate with iCloud.
iCloud and Snow Leopard, by Roger Wilmut describes what iCloud options are available for Snow Leopard.
If you are using Lion, go to iCal>Preferences...>Accounts, and delete/re-add your iCloud CalDAV server.

Unable to confirm transfer order due to error message "enter a storage unit

Hi guys:
I am unable to confirm transfer order due to error message popping up and saying "enter a storage unit", and I tried to search it in whole thread in the forum,it was suggestion to pick up destination storage unit via ls24, but I did went to ls24 and trying to click that line(transfer order) but unable to find the storage unit, so is there another way to fix it?

Hi Allen...
Pls check if your Storage Type is SU Active. If yes, then system will create a storage unit according to the setting done for the storage unit management, perhaps in your case you are confirmin TO for the putaway.
Pls confirm and revert
Regards
Shiva

Error while deploying WC application: Unable to deploy EJB

Hi All,
we are getting the below error quite frequently, whenever we deploy the application to server:
[03:35:14 AM] Weblogic Server Exception: weblogic.application.ModuleException: Exception preparing module: EJBModule(CAWrapperEJB.jar)
Unable to deploy EJB: CAService from CAWrapperEJB.jar:
[EJB:011055]Error deploying the EJB 'CAService(Application: CAPortal, EJBComponent: CAWrapperEJB.jar)', the JNDI name 'CAPortal-CAPModel-CAService2#com.lexisnexis.service.CAService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
[03:35:14 AM] Caused by: java.lang.Throwable: Substituted for missing class [EJB - 11055]Error deploying the EJB 'CAService(Application: CAPortal, EJBComponent: CAWrapperEJB.jar)', the JNDI name 'CAPortal-CAPModel-CAService2#com.lexisnexis.service.CAnService' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
[03:35:14 AM] See server logs or server console for more details.
-to solve this issue we just delete the cache and restart the Managed server.
Please tell me what is the cause of this error and how can we fix it permanently, as restarting the server everytime is not very convenient.
TIA,
Bob

The content of "weblogic-ejb-jar.xml" present in code is:
<?xml version = '1.0' encoding = 'windows-1252'?>
<weblogic-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd"
xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar">
</weblogic-ejb-jar>

Unable to deploy EJB 3.0 on JBoss 4.0.4GA - no home interface

I am stuck in that my EJB3.0 project (one entity bean, one session bean and one client test bean) builds OK but somehow Eclipse Europa is unable to deploy it to JBoss (4.0.4 GA and 5 Beta) -- something to do with JNDI error as it involves javax.naming exceptions.
My Eclipse directory structure is :-
Titan (project name)
|
ejb - com.titan (package name)
| |
| domain -> Cabin.java (my entity bean)
| |
| travelagent -> TravelAgentBean.java
| -> TravelAgentRemote.java
|
META_INF -> ejb-jar.xml
-> MANIFEST.MF
-> persistence.xml
My ejb-jar.xml is :
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>Titan</display-name>
<enterprise-beans>

<session >
<display-name>TravelAgentBean</display-name>
<ejb-name>com/titan/travelagent/ejb/TravelAgentBean</ejb-name>
<remote>com.titan.travelagent.ejb.TravelAgentRemote</remote>
<ejb-class>com.titan.travelagent.ejb.TravelAgentBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
And my persistence.xml is :
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="Titan">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<class>com.titan.domain.Cabin</class>
<properties>
<property name="hibernate.connection.driver_class" value="oracle.jdbc.OracleDriver" />
<property name="hibernate.connection.url"
value="jdbc:oracle:thin:@localhost:1521:XE" />
<property name="hibernate.connection.username" value="SYSTEM" />
<property name="hibernate.connection.password" value="Swordfish1" />
</properties>
</persistence-unit>
</persistence>
I right-click on the Titan project name and choose Build Project. I get the following error message :-
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.2
Warning: A Session bean must implement, directly or indirectly, the javax.ejb.SessionBean interface.
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.3
Warning: A Session bean must define at least one ejbCreate method.
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.1
Warning: The session bean must implement either a remote home and remote, or a local home and a local interface or a service endpoint interface.
13:01:06,062 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.0.4.GA/server/default/deploy/Titan.jar
I don't understand, because as of EJB 3.0, you don't really need a home or local-home interface anymore...

Using @SecurityDomain("exemplo1") in my EJB and NOT providing jboss.xml, it works.
@SecurityDomain("exemplo1")
@RolesAllowed("yyy")
@Stateless(name="UserManagement")
public class UserManagementBean implements UserManagement {
public void add(User user) {
}Damn! This is some serious shit... I don�t want to configure this in every single EJB.
EJB 3.0 is nice, but some small trivial details like this and others, that was forgotten by Sun, piss me off!

Unable to deploy VIO OpenStack due to anti-affinity rule

Similar Messages

Maybe you are looking for