Unable to deploy eis.jms.WLSConnectionFactoryJNDIXA on startup

I have a WLS 9.2 MP1 cluster with a messaging bridge which uses the jms XA resource adapter. (jmx-xa-adp).
          The messaging bridge and the jmx-xa-adp.rar targets the cluster. If I start the first applicationserver having the messaging bridge on "Started" it seems as if it tries to start before the jmx-xa-adp is deployed.
          I get this error:
          <Feb 19, 2007 2:32:02 PM CET> <Info> <MessagingBridge> <BEA-200021> <Bridge "EdosETC_Bridge" failed to get one of the adapters from JNDI
          (javax.naming.NameNotFoundException: Unable to resolve 'eis.jms.WLSConnectionFactoryJNDIXA'. Resolved 'eis.jms'; remaining name
          'WLSConnectionFactoryJNDIXA'). javax.naming.NameNotFoundException: Unable to resolve 'eis.jms.WLSConnectionFactoryJNDIXA'.
          Resolved 'eis.jms'; remaining name 'WLSConnectionFactoryJNDIXA'
          at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
          I even tried to lower the deploy order for the XA-adapter but I didn't help. If the bride hasn't "Started" checked, the cluster startup is fine. How do I solve this? Deploy order of the mesasging bridge can't be changed either...

Found yet another thing. If starting with bridge "off", the bridge won't start until I ALSO redeploy the "jms-xa-adp". Very strange as well...must be a WLS bug. Since the adapter works, even when clicking "test". But bridge won't start until redeploy of the adapter.

Similar Messages

  • Unable to create a JMS Message bridge between Weblogic 12c and Weblogic 8.1

    Hi,
    I am unable to successfully create a Message Bridge between Weblogic 12.1.1.0 and Weblogic 8.1. The error message being received is:
    eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException generated by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3://localhost:8001, user name = System) ">
    The error on the monitoring tab is WARN: failed to connect to target.
    Both domains are deployed on one box for testing purposes. The bridge itself is deployed on Weblogic 12c. The areas of config that may be of interest are:
    <server>
    <name>AdminServer</name>
    <listen-address></listen-address>
    </server>
    <messaging-bridge>
    <name>Bridge</name>
    <target>AdminServer</target>
    <source-destination>JMSBridgeSource12c</source-destination>
    <target-destination>JMSBridgeTarget81</target-destination>
    <selector>Test</selector>
    <quality-of-service>Exactly-once</quality-of-service>
    <qos-degradation-allowed>false</qos-degradation-allowed>
    <durability-enabled>true</durability-enabled>
    <idle-time-maximum>60</idle-time-maximum>
    <async-enabled>true</async-enabled>
    <started>true</started>
    <preserve-msg-property>false</preserve-msg-property>
    </messaging-bridge>
    <app-deployment>
    <name>jms-xa-adp</name>
    <target>AdminServer</target>
    <module-type>rar</module-type>
    <source-path>D:\ORACLE~3\WLSERV~1.1\server\lib\jms-xa-adp.rar</source-path>
    <security-dd-model>DDOnly</security-dd-model>
    </app-deployment>
    <jms-bridge-destination>
    <name>JMSBridgeSource12c</name>
    <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
    <user-name>System</user-name>
    <user-password-encrypted>{AES}nfFzhs+0J/O2Cenf0g4zDsDyvIKENMF7cZ5sAVUehX0=</user-password-encrypted>
    <classpath></classpath>
    <connection-factory-jndi-name>JMSConnectionFactory12c</connection-factory-jndi-name>
    <connection-url>t3://localhost:7001</connection-url>
    <destination-jndi-name>JMSQueue12c</destination-jndi-name>
    </jms-bridge-destination>
    <jms-bridge-destination>
    <name>JMSBridgeTarget81</name>
    <adapter-jndi-name>eis.jms.WLSConnectionFactoryJNDIXA</adapter-jndi-name>
    <user-name>System</user-name>
    <user-password-encrypted>{AES}eBkO46cHvtrzEraOMIOdXow6WvEAtA4NCUDTQ4mC+9w=</user-password-encrypted>
    <classpath></classpath>
    <connection-factory-jndi-name>JMSConnectionFactory81</connection-factory-jndi-name>
    <connection-url>t3://localhost:8001</connection-url>
    <destination-jndi-name>JMSQueue81</destination-jndi-name>
    </jms-bridge-destination>
    I have enforced global trust between the two domains. I have disabled the guest user on the 8.1 domain but can’t see where to do this on 12c.
    Any suggestions would be much appreciated.
    Regards
    John
    Edited by: 958336 on 13-Sep-2012 03:11

    Thanks for the recommendation. Unfortunately it did not help solve the problem.
    I have managed to get a JMS bridge working between 12c and 8.1 by including the 8.1 weblogic.jar on the classpath. This setup was using eis.jms.WLSConnectionFactoryJNDINoTX.
    After trying to use the adapter that supports transactions, WLSConnectionFactoryJNDIXA I received the following error:
    java.lang.IllegalStateException: can only be called from server
    Is this because the Weblogic 12c server now views the 8.1 server as being foreign?

  • Unable to deploy CMB with microsfoft access database

    Hi,
    I saw the news:[email protected] at
    http://forums.bea.com/bea/message.jspa?messageID=202177534.
    I am not able to deploy the Container managed bean .
    Am able to configure and deploy the connection pool
    and data source using the sun.jdbc driver but the bean deployment is not
    happening.
    Server always threw some error as below
    java.lang.NoClassDefFoundError: weblogic/jdbc/wrapper/JTSConnection
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
    3)
    at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic
    ClassLoader.java:476) .................
    Error in admin console is also attached.
    weblogic.management.ManagementRuntimeException: javax.management.InstanceNotFoundException: mydomain:Application=Emp,Name=Emp,Type=EJBComponent
         at weblogic.management.configuration.EJBComponentMBean_Stub.getTargets(EJBComponentMBean_Stub.java:1089)
         at .....
    and soemtimes,
    Exception:weblogic.management.ApplicationException: activate failed for acct Module: acct Error: Exception activating module: EJBModule(acct,status=PREPARED) Unable to deploy EJB: AccountEJB from acct.jar: Failed to Generate Wrapper Class. Nested Exception: java.lang.RuntimeException: Failed to Generate Wrapper Class at weblogic.utils.wrapper.WrapperFactory.createWrapper(WrapperFactory.java:141) at weblogic.jdbc.wrapper.JDBCWrapperFactory.getWrapper(JDBCWrapperFactory.java:73) at weblogic.jdbc.jts.Driver............
    Looks like it is similar issue as that in the new
    listed above.Am not able to find any wrapfact.jar in
    my server/lib.
    Am using evaluation copy of server811 on windows 2000
    with sp 4 installed on my machine.
    Please let me know of the pointers to this issue.
    If some patches are there ,please send me the jar
    files.
    Thanks and Regards,
    Poonkothai

    It looks like it's failing to deploy because the JMS resource hasn't been found.
    Do you have the OJMS resource provider setup on OC4J? And the data source configured to point at the database hosting the AQ service is configured correctly?
    Here's the steps I'm referring to from a version of README.txt I found:
    1. The users need to configure a resource provider named "mdbdemo" at the
    $J2EE_HOME/config/application.xml to access OJMS queues.
    <resource-provider class="oracle.jms.OjmsContext" name="mdbdemo">
    <description> OJMS/AQ </description>
    <property name="datasource" value="jdbc/OracleDS"></property>
    </resource-provider>
    NOTE: Do not use a different name since the resource provider name is hardcoded in the MDB's deployment descriptors. Use name of "mdbdemo" only.
    2. Configure the $J2EE_HOME/config/data-source.xml with the following entry as referenced above to connect to the database and schema used in "database setup".
    <data-source
    class="com.evermind.sql.DriverManagerDataSource"
    name="OracleDS"
    location="jdbc/OracleCoreDS"
    xa-location="jdbc/xa/OracleXADS"
    ejb-location="jdbc/OracleDS"
    connection-driver="oracle.jdbc.driver.OracleDriver"
    username="jmsuser"
    password="jmsuser"
    url="jdbc:oracle:thin:@%DB_HOST%:%DB_PORT%:%DB_SID%"
    inactivity-timeout="30"
    />
    cheers
    -steve-
    Message was edited by:
    sbutton

  • Unable to deploy EJB: ...Expected role in mapping - WL9.2 on XP

    Message Driven Bean deployment - getting error below - I thought the mapping was defined in weblogic-ejb-xml.jar?
    [i][i][i]Caused by: java.lang.AssertionError: Expected role in mapping        at weblogic.ejb.container.internal.RuntimeHelper.getRunAsPrincipalFromRoleMapping(RuntimeHelper.java:301)
            at weblogic.ejb.container.deployer.BeanInfoImpl.calculateRunAsPrincipal(BeanInfoImpl.java:866)
            at weblogic.ejb.container.deployer.BeanInfoImpl.prepare(BeanInfoImpl.java:816)
            at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:866)
            at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:946)
            ... 25 more
    Unable to deploy EJB: EjbFileRequest from EjbFileRequest.jar:
    Expected role in mapping
    <ejb-jar
    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"
    version="2.1">
    <enterprise-beans>
    <message-driven>
    <ejb-name>EjbFileRequest</ejb-name>
    <ejb-class>EjbFileRequest</ejb-class>
    <transaction-type>Container</transaction-type>
    <activation-config>
    <activation-config-property>
    <activation-config-property-name>destinationType</activation-config-property-name>
    <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
    </activation-config-property>
    </activation-config>
    <security-identity>
    <run-as>
    <role-name>EJBFileRequestRole</role-name>
    </run-as>
    </security-identity>
    </message-driven>
    </enterprise-beans>
    </ejb-jar>
    <weblogic-ejb-jar
      xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
      <weblogic-enterprise-bean>
        <ejb-name>EjbFileRequest</ejb-name>
        <message-driven-descriptor>
          <destination-jndi-name>jms/TrinityFRQ</destination-jndi-name>
        </message-driven-descriptor>
      </weblogic-enterprise-bean>
      <security-role-assignment>         
       <role-name>EJBFileRequestRole</role-name>
       <principal-name>trinityejbuser</principal-name>
    </security-role-assignment>
    </weblogic-ejb-jar>

    Did you ever figure out what was wrong here? I have the same setup and the same problem.

  • Unable to deploy EJB: unable to find EndPointFinder

    Hello.
    We are in a process of migrating applications from WL7 SP7 to WL 10.3
    JDK 1.4 to JDK 1.6
    EJB 2.1 remains same.
    When we try to connect to a third-party (SONIC) secured JMS infrastructure Topic. I have configured the credential mapper for that.
    When I deployed application in WL 10.3 I got following error
    Unable to deploy EJB: TLDBanMoveMDB from tbstotld.jar:
    unable to find EndPointFinder for ldap://emldev01.sbc.com:4299/t=jms,ou=2_0,ou=dst01,ou=telegence,ou=ld,o=billing'
    weblogic.application.ModuleException: Exception activating module: EJBModule(tbstotld.jar)
    Unable to deploy EJB: TLDBanMoveMDB from tbstotld.jar:
    unable to find EndPointFinder for ldap://emldev01.sbc.com:4299/t=jms,ou=2_0,ou=dst01,ou=telegence,ou=ld,o=billing
    at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:66)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
    Following is my deployment descriptor.
    <weblogic-enterprise-bean>
    <ejb-name>TLDBanMoveMDB</ejb-name>
    <message-driven-descriptor>
    <pool>
    <max-beans-in-free-pool>30</max-beans-in-free-pool>
    <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
    </pool>
    <destination-jndi-name>cn=tldNotify</destination-jndi-name>
    <initial-context-factory>com.sun.jndi.ldap.LdapCtxFactory</initial-context-factory>
    <provider-url>ldap://emldev01.sbc.com:4299/t=jms,ou=2_0,ou=dst01,ou=telegence,ou=ld,o=billing</provider-url>
    <connection-factory-jndi-name>cn=embdev01TCF</connection-factory-jndi-name>
    <jms-client-id>M20413</jms-client-id>
    </message-driven-descriptor>
    </weblogic-enterprise-bean>
    I did some research and learned that Weblogic seems to confuse as to which initial context factory to use. See the posts as linked in here. Is this a bug in Weblogic?
    http://forums.oracle.com/forums/thread.jspa?threadID=873769
    http://objectmix.com/weblogic/537901-unable-find-endpointfinder.html
    Some folks are recommending using weblogic.ejbcgen, but all I have is deployment descriptors and not sure how do I handle this.
    If I create a foreign jndi provider, how do I replace the details in my weblogic-ejb-jar.xml?
    Please help.
    Thanks
    Hari.
    Edited by: rihem09 on Nov 10, 2009 6:55 PM

    Check out this page.
    http://objectmix.com/weblogic/537901-unable-find-endpointfinder.html
    글 수정: user6407983

  • 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

  • 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 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 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

  • Unable to deploy a cmp 2.0 ejb to wls 8.1

    windows Xp professional
    IBM DB2
    JBuilder 9.0
    i build a ejb jar with jb9.0 wizard, then deploy it to wls.
    but ...
    D:\servers\bea\jdk141_03\bin\javaw -classpath
    D:\servers\bea\weblogic81\server\lib\weblogic_sp.jar;D:\servers\bea\weblogic81\server\lib\weblogic.jar;D:\servers\bea\weblogic81\server\lib\webservices.jar;
    weblogic.Deployer -user jerez -adminurl http://kame_house:7001
    -password kinchin4587 -activate -name water -upload -source
    D:/workspace/jbproject/water/water.jar -targets jerez
    Initiated Task: [4] [Deployer:149026]Deploy application water on jerez.
    Task 4 failed: [Deployer:149026]Deploy application water on jerez.
    Deployment failed on Server jerez
    weblogic.management.DeploymentException:
    Exception:weblogic.management.ApplicationException: activate failed for
    water
         Module: water     Error: Exception activating module:
    EJBModule(water,status=PREPARED)
    Unable to deploy EJB: Angle from water.jar:
    java.lang.AbstractMethodError:
    weblogic.jdbc.wrapper.DatabaseMetaData_COM_ibm_db2_jdbc_app_DB2DatabaseMetaData.supportsBatchUpdates()Z
         at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifyBatchUpdatesSupported(RDBMSPersistenceManager.java:2081)
         at
    weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:200)
         at
    weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
         at
    weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
         at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164)
         at
    weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1004)
         at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1322)
         at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
         at
    weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3012)
         at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2076)
         at
    weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2057)
         at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2624)
         at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2547)
         at
    weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2349)
         at
    weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2431)
         at
    weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2343)
         at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2511)
         at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
         at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
         at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
         at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

    Hi,
    How did you uninstall the graphics drvier? From Devices manager or Programs and Features?
    Please open Control Panel\All Control Panel Items\Programs and Features
    And then, search for "NVIDIA Graphics Driver" and then select the "Change/Remove" button to begin the uninstall process. 
    Next, once the uninstall has completed, reboot Windows so that the other NVIDIA components can be removed as well.
    If the issue still persists, since this driver that you recently installed caused problems with your PC, you can restore Windows back to an earlier point in time.
    http://windows.microsoft.com/en-us/windows-8/restore-refresh-reset-pc
    Regards,
    Kelvin Xu
    TechNet Community Support

  • Unable to Deploy a Webservice.

    Hello All,
    I created a java bean and put the implemented code in some of the methods etc. ( By the way the code is generated using a WSDL using the SAP Netweaver libraries )
    Now when I attempt to actually create the webservice out of the implemented Java Bean.
    ( By right click - > Webservice -> Create webservice.)
    It create the EJB Jar and also create EJB EAR file but I am unable to deploy this EAR archive.
    It throws following exception trace :
    Can any of you please throw some light on this . ?
    I am using NWDS Ce 7.1 SP05 .
    Can we get this problem if the NWDS and NWDI are not in Same version and same patch ?
    IWAB0014E Unexpected exception occurred.
      Client "com.sap.ide.jee.ws.jee5.core.provider.commands.AddWsdlToInfo" threw an exception.
          java.lang.IllegalArgumentException: Client "com.sap.ide.jee.ws.jee5.core.provider.commands.AddWsdlToInfo" threw an exception.
          at org.eclipse.wst.command.internal.env.core.data.DataFlowManager.invokeMethod(DataFlowManager.java:275)
          at org.eclipse.wst.command.internal.env.core.data.DataFlowManager.process(DataFlowManager.java:124)
          at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:411)
          at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:358)
          at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:253)
          at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$5.run(SimpleCommandEngineManager.java:252)
          at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369)
          at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313)
          at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934)
          at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:222)
          at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:96)
          at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.getNextPage(WizardPageManager.java:147)
          at org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizardPage.getNextPage(SimpleWizardPage.java:136)
          at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813)
          at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)
          at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616)
          at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227)
          at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
          at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
          at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
          at org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
          at org.eclipse.jface.window.Window.open(Window.java:796)
          at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
          at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:256)
          at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545)
          at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490)
          at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402)
          at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938)
          at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3682)
          at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3293)
          at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
          at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
          at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
          at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
          at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
          at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
          at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
          at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
          at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
          at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
          at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
          at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
          at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:585)
          at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504)
          at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443)
          at org.eclipse.equinox.launcher.Main.run(Main.java:1169)
          at org.eclipse.equinox.launcher.Main.main(Main.java:1144)

    Hi Ravi,
    can you please indicate the NWDS and NWDI versions and JDK being used?
    Regards,
    Désiré

  • Unable to deploy a jar on WEBLOGIC 8

    Hi everybody,
    I have a problem to deploy a jar file on my server IOException ....
    Informations :
    Solaris 8
    WEBLOGIC 8 SP1
    ORACLE 9.0.2
    Best regards,
    Alain.
    The time this task was completed.
    Exception: Exception:weblogic.management.ApplicationException: prepare failed
    for ReferenceDataEJB.jar Module: ReferenceDataEJB.jar Error: Exception preparing
    module: EJBModule(ReferenceDataEJB.jar,status=NEW) Unable to deploy EJB: ReferenceDataEJB.jar
    from ReferenceDataEJB.jar: Compiler failed executable.exec at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:401)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493) at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
    at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1275) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:473)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2842)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1529)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1183)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1026)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2568)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2520)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2450)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:829)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:538)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:496)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    java.io.IOException: Compiler failed executable.exec at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:505)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:364) at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:372) at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:401)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493) at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
    at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1275) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:473)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2842)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1529)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1183)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1026)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2568)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2520)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2450)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:829)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:538)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:496)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)

    Hello,
    Thanks a lot for your answer
    This step alone work very well. So i have supected and bad domaine configuration
    because I have deployed the same application onto another machine and everything
    was good (and the OS is the same).
    On the production machine (where there is a problem), i have check BEA_HOME, WL_HOME,
    JAVA_HOME and everything is good.
    Have you another tip for me ?
    Regards,
    Alain.
    "Deepak Vohra" <[email protected]> wrote:
    >
    Compile ReferenceDataEJB.jar with ejbc before deploying the jar file.
    "Compiler failed executable.exec at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)"
    is a ejbc error.
    thanks,
    Deepak
    "GREGOIRE Alain" <[email protected]> wrote:
    Hi everybody,
    I have a problem to deploy a jar file on my server IOException ....
    Informations :
    Solaris 8
    WEBLOGIC 8 SP1
    ORACLE 9.0.2
    Best regards,
    Alain.
    The time this task was completed.
    Exception: Exception:weblogic.management.ApplicationException: prepare
    failed
    for ReferenceDataEJB.jar Module: ReferenceDataEJB.jar Error: Exception
    preparing
    module: EJBModule(ReferenceDataEJB.jar,status=NEW) Unable to deployEJB:
    ReferenceDataEJB.jar
    from ReferenceDataEJB.jar: Compiler failed executable.exec at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468)at
    weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:401)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
    at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1275)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:473)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2842)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1529)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1183)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1026)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2568)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2520)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2450)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:829)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:538)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:496)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) atweblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
    java.io.IOException: Compiler failed executable.exec at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:505)
    at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:364)
    at
    weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:372)
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468)at
    weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:401)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
    at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:701)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1275)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:473)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2842)
    at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1529)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1183)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1026)
    at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2568)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2520)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2450)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:829)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:538)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:496)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) atweblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)

  • Unable to Deploy Applications:  "process is not defined in the descriptor"

    All
    I'm having a fairly serious issue here trying to take an LCA from one environment and get it in another environment.  Both the source and destination environments are LCES 2.5 (LCES 2 with SP2).  I have roughly 6 applications and there are some far dependencies (one application referencing an asset of another application) therein.  I've taken an LCA of all these applicaitons from the source environment and the LCA imports just fine in the destination environment but I am unable to deploy any of the applications that have far dependencies.  The error I consistently get when I attempt to deploy any application that has a far dependency is:
    [Some process name].process is not defined in the descriptor.
    I have tried all of the following:
    1) Taking 1 LCA of all applications together
    2) Taking multiple LCAs where each LCA contains only one application
    3) Taking multiple LCAs where each LCA includes an application as well as all far dependencies for that application
    Regardless of what I try, they won't deploy.  I can import the LCA and I can get the applications in Workbench and play around with them but they simply won't deploy.  I've also attempted to manually fix all depencies within the processes themselves but that doesn't work either.
    Any help would be appreciated.

    Just wanted to follow up on the solution to my issue.
    It appears the issue centers around circular far dependencies.  In general, it seems LiveCycle chokes when two applications each reference one another.  Note that I'm not talkinng about true circular referencing here wherein one process within application A references a process in application B while that same process refers back to the original process in application A.  In fact, although I haven't tested recently, I believe LiveCycle may actually catch this kind of issue.  The circular far dependencies I'm talking about is simply where a process in application A (call it a1) references a process in application B (call it b1) while a process in application B (call it b2) references a process in applicatoin A (call it a2).  Apparently this kind of circular referencing causes the deployment of said applications to choke.
    The fix was tedious as I had to manually delete all of the far dependencies from both application, deploy those two applications to get them into the runtime, and then implement those dependencies again.
    Going forward it seems like a best practice to only ever have 1 direction for dependencies for any application.

  • Unable to deploy EJB application

    Hi iam getting the following exception while deploying an EJB application in WebLogic 8.1
    Exception:weblogic.management.ApplicationException: prepare failed for Addition
    Module: Addition Error: Exception preparing module: EJBModule(Addition,status=NEW)
    Unable to deploy EJB: Addition.jar from Addition.jar:
    Compiler failed executable.exec
    at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:468)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:401)
    at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
    at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:763)
    what might be the reason for this exception ????

    This problem is caused by the way WebLogic calls javac to compile the generated classes for the EJBs deployment. This became a big problem for our project with 50 Entity EJBs 2.0 with CMP/CMR, about 15 EJB-QL statements, 3 MDB and 8 Session EJB. I think that these numbers are limits, so exceeding any of these numbers cause javac to exhaust the memory it allocates by default. Even the WebLogic 8.1.Server's administarion console allows you to supply additional parameters for RMI and EJB compilers, it does not allow to supply the -J-Xmx256M (or more) option needed to increase the memory javac allocates.
    Thus:
    1. In the active $JAVA_HOME/bin of the Server create the file:
    Windows:
    javac1.cmd Containing:
    javac -J-Xmx256M %*
    Linux:
    javac1.sh Containing:
    #!/bin/bash
    javac -J-Xmx256M $*
    make it "executable"
    NOTE: startWeblogic script sets it own JAVA_HOME, so check it first.
    2. In the administraitve console of WebLogic 8.1 Server select the server in the left frame under the
    <Domain> / Servers branch. In the right frame select the General tab.
    3. In the Java Compiler box change javac to javac1.cmd or javac1.sh respectively. No restart is needed.
    This solved our problem.
    I could not find any solution published, hopefully this will help other colleagues.
    Rusi Popov

Maybe you are looking for

  • Placing 2 Web items in the same place in a Dashboard

    Hi, I am creating a dashboard with 4 charts in a single page, 2 rows with 2 charts in each row.  One requirement of mine is like, take a chart for example, when i first execute the template, it should display a Bar chart and then the same chart shoul

  • Question about using the Combo Box feature!

    I have a form that I am trying to create for our company that will allow our field nurses to select what they need and print it more effieciently.  The problem is that some of the selections are too long and I can't get the Combo box feature to allow

  • New computer.  How do I get Itunes to sync the new podcasts without erasing the ones already on my iPod

    I just bought a new computer and have installed iTunes.  I want to be able to sync the new epsodes of the podcasts I regularly listen to without erasing any of the podcasts, music or books already on my ipod.

  • How to call function BAPI_GOODSMVT_CREATE ?

    Hi all, I want to create a material document by calling the function BAPI_GOODSMVT_CREATE I don't know what to pass although I know I have to export something (GOODSMVT_HEADER and GOODSMVT_CODE) in my ABAP. But what should I actually pass to the func

  • Document windows opening under the options bar

    Argh! anyone know how to get the windows from NOT opening under the options bar? I have to zoom the window each time so I can access the document bar and it is driving me MAD!!!!See how my top gray document bar is hidden?? If I hit the zoom out then