Ejb-link error

I am fairly new to weblogic and have the following problem on deployment. It complains
about an ejb-link property that cannot be resolved, but I have done a bunch of
research and cannot figure out why I'm getting this problem. The ejb in the ejb-link
is in the same jar as the ejb-jar.xml. The entries look correct. Strange thing
is, the ejb it complains about not being able to deploy isn't even referencing
the other ejb in question. I've attached the ejb-jar.xml we're using. The app
server we were using was fairly liberal with this sort of thing and we got away
with it. There probably is a problem, but it's not clear what. Any help would
be appreciated. I've included the output from weblogic.
[Deployer:149033]preparing application Armanta on Armanta-Custom
[Deployer:149033]prepared application Armanta on Armanta-Custom
[Deployer:149033]activating application Armanta on Armanta-Custom
[Deployer:149033]failed application Armanta on Armanta-Custom
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application
Armanta on Armanta-Custom.:
Exception:weblogic.management.ApplicationException: activate failed for ArmantaCustomEJB.jar
Module: ArmantaCustomEJB.jar Error: Exception activating module: EJBModule(ArmantaCustomEJB.jar,status=PREPARED)
Unable to deploy EJB: ejb/CouponType from ArmantaCustomEJB.jar:
weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'ejb/SysProperty'
declared in the ejb-ref or ejb-local-ref 'ejb/SysProperty' in the application
module 'ArmantaCustomEJB.jar' could not be resolved. The target EJB for the ejb-ref
could not be found. Please ensure the link is correct.
at weblogic.ejb20.deployer.EnvironmentBuilder.addEJBLinkRef(EnvironmentBuilder.java:738)
at weblogic.ejb20.deployer.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:537)
at weblogic.ejb20.deployer.EJBDeployer.bindEJBReferences(EJBDeployer.java:1609)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1375)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2399)
at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2311)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2479)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
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)
[ejb-jar.xml]

Thanks Deepak. It's strange that the O'reilly 3rd edition enterprise javabeans
book doesn't mention this.
"Deepak Vohra" <[email protected]> wrote:
>
Refer to http://e-docs.bea.com/wls/docs81/webserv/wsp.html#ejb-link
"Eric Kaplan" <[email protected]> wrote:
I am fairly new to weblogic and have the following problem on deployment.
It complains
about an ejb-link property that cannot be resolved, but I have donea
bunch of
research and cannot figure out why I'm getting this problem. The ejb
in the ejb-link
is in the same jar as the ejb-jar.xml. The entries look correct. Strange
thing
is, the ejb it complains about not being able to deploy isn't even referencing
the other ejb in question. I've attached the ejb-jar.xml we're using.
The app
server we were using was fairly liberal with this sort of thing andwe
got away
with it. There probably is a problem, but it's not clear what. Any help
would
be appreciated. I've included the output from weblogic.
[Deployer:149033]preparing application Armanta on Armanta-Custom
[Deployer:149033]prepared application Armanta on Armanta-Custom
[Deployer:149033]activating application Armanta on Armanta-Custom
[Deployer:149033]failed application Armanta on Armanta-Custom
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
application
Armanta on Armanta-Custom.:
Exception:weblogic.management.ApplicationException: activate failedfor
ArmantaCustomEJB.jar
Module: ArmantaCustomEJB.jar Error: Exception activating module: EJBModule(ArmantaCustomEJB.jar,status=PREPARED)
Unable to deploy EJB: ejb/CouponType from ArmantaCustomEJB.jar:
weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link
'ejb/SysProperty'
declared in the ejb-ref or ejb-local-ref 'ejb/SysProperty' in the application
module 'ArmantaCustomEJB.jar' could not be resolved. The target EJBfor
the ejb-ref
could not be found. Please ensure the link is correct.
at weblogic.ejb20.deployer.EnvironmentBuilder.addEJBLinkRef(EnvironmentBuilder.java:738)
at weblogic.ejb20.deployer.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:537)
at weblogic.ejb20.deployer.EJBDeployer.bindEJBReferences(EJBDeployer.java:1609)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1375)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2399)
at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2311)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2479)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
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)

Similar Messages

Error: Unresolved ejb-link :

I want to call a session bean from a servlet.while deploying i am getting the error
Error: Unresolved <ejb-link>:
I am using Netbeans 6.0 IDE. here i am posting my code.
Calling code in servlet :
Context ctx = new InitialContext();
Object objref = ctx.lookup("java:comp/env/ejb/Etrack");
testBean=(MyHome)PortableRemoteObject.narrow(objref,MyHome.class);
web.xml :
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
<servlet>
<servlet-name>MyClientServlet</servlet-name>
<servlet-class>MyClientServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>MyClientServlet</servlet-name>
<url-pattern>/MyClientServlet</url-pattern>
</servlet-mapping>
<ejb-local-ref>
<ejb-ref-name>ejb/Etrack</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>MyHome</local-home>
<local>MyRemote</local>
<ejb-link>Etrack</ejb-link>
</ejb-local-ref>
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
</web-app>
My ejb-jar.xml :
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<session>
<display-name>Etrack Bean</display-name>
<ejb-name>Etrack</ejb-name>
<local-home>MyHome</local-home>
<local>MyRemote</local>
<ejb-class>MyEjbClass</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
<ejb-local-ref>
<ejb-ref-name>ejb/Etrack</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>MyHome</local-home>
<local>MyRemote</local>
<ejb-link>Etrack</ejb-link>
</ejb-local-ref>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>Etrack</ejb-name>
<method-intf>Local</method-intf>
<method-name>*</method-name>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
My sun-ejb-jar.xml :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 EJB 2.1//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_2_1-1.dtd">
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>Etrack</ejb-name>
<stateless-session-descriptor>
<bean-pool>
<steady-pool-size>10</steady-pool-size>
<resize-quantity>10</resize-quantity>
<max-pool-size>100</max-pool-size>
<pool-idle-timeout-in-seconds>600</pool-idle-timeout-in-seconds>
</bean-pool>
</stateless-session-descriptor>
<jndi-name>ejb/Etrack</jndi-name>
<pass-by-reference>true</pass-by-reference>
<ejb-ref>
<ejb-name>Etrack</ejb-name>
<ejb-ref-name>ejb/Etrack</ejb-ref-name>
<jndi-name>ejb/Etrack</jndi-name>
</ejb-ref>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
Can anyone help me in resolving this issue.It will be a great help for me.Thanks in advance

You could always try removing the ejb-link, and see if the container can inject a reference in the runtime environment (accessible using jndi java:comp/env/ejb/Etrack).
If it doesn't, check these:
1) http://www.redhat.com/docs/manuals/rhaps/jonas-guide/ch-beans-ejbref.html
2) the ejb 2.0 spec, which the original poster was using (although this is the same in 2.1 and 3.0), states the folowing:
+20.3.2 Application Assembler’s responsibilities+
The Application Assembler can use the ejb-link element in the deployment descriptor to link an*
EJB reference to a target enterprise bean.*
The Application Assembler specifies the link between two enterprise beans as follows:*
+• The Application Assembler uses the optional ejb-link element of the ejb-ref or+
ejb-local-ref element of the referencing enterprise bean. The value of the ejb-link*
element is the name of the target enterprise bean. (It is the name defined in the ejb-name element*
of the target enterprise bean.) The target enterprise bean can be in any ejb-jar file in the*
same J2EE application as the referencing application component.*
+• Alternatively, to avoid the need to rename enterprise beans to have unique names within an+
entire J2EE application, the Application Assembler may use the following syntax in the*
ejb-link element of the referencing application component. The Application Assembler*
specifies the path name of the ejb-jar file containing the referenced enterprise bean and*
appends the ejb-name of the target bean separated from the path name by # . The path name*
is relative to the referencing application component jar file. In this manner, multiple beans with*
the same ejb-name may be uniquely identified when the Application Assembler cannot*
change ejb-names.*
+• The Application Assembler must ensure that the target enterprise bean is type-compatible with+
the declared EJB reference. This means that the target enterprise bean must be of the type indicated*
in the ejb-ref-type element, and that the home and component interfaces of the target*
enterprise bean must be Java type-compatible with the interfaces declared in the EJB*
reference.*
The following illustrates an ejb-link in the deployment descriptor.*
+...+
*+<enterprise-beans>+*
*+<session>+*
+...+
*+<ejb-name>EmployeeService</ejb-name>+*
*+<ejb-class>com.wombat.empl.EmployeeServiceBean</ejb-class>+*
+...+
*+<ejb-ref>+*
*+<ejb-ref-name>ejb/EmplRecord</ejb-ref-name>+*
*+<ejb-ref-type>Entity</ejb-ref-type>+*
*+<home>com.wombat.empl.EmployeeRecordHome</home>+*
*+<remote>com.wombat.empl.EmployeeRecord</remote>+*
*+<ejb-link>EmployeeRecord</ejb-link>+*
*+</ejb-ref>+*
+...+
*+</session>+*
+...+
*+<entity>+*
*+<ejb-name>EmployeeRecord</ejb-name>+*
*+<home>com.wombat.empl.EmployeeRecordHome</home>+*
*+<remote>com.wombat.empl.EmployeeRecord</remote>+*
+...+
*+</entity>+*
+...+
*+</enterprise-beans>+*
+...+
The Application Assembler uses the ejb-link element to indicate that the EJB reference “Empl-*
Record” declared in the EmployeeService enterprise bean has been linked to the EmployeeRecord*
enterprise bean.</stro
The following example illustrates using the ejb-link element to indicate an enterprise bean reference*
to the ProductEJB enterprise bean that is in the same J2EE application unit but in a different ejb-jar*
file.*
*+<entity>+*
+...+
*+<ejb-name>OrderEJB</ejb-name>+*
*+<ejb-class>com.wombat.orders.OrderBean</ejb-class>+*
+...+
*+<ejb-ref>+*
*+<ejb-ref-name>ejb/Product</ejb-ref-name>+*
*+<ejb-ref-type>Entity</ejb-ref-type>+*
*+<home>com.acme.orders.ProductHome</home>+*
*+<remote>com.acme.orders.Product</remote>+*
*+<ejb-link>../products/product.jar#ProductEJB</ejb-link>+*
*+</ejb-ref>+*
+...+
*+</entity>+*

Error Deploying Application - ejb-link or jndi-name

I get the following error when depoying my J2EE application. Can anyone help ?
Deployment failed on Server MServer1
weblogic.management.DeploymentException:
Exception:weblogic.management.ApplicationException: activate failed for Supplier
     Module: Supplier     Error: weblogic.management.DeploymentException: Could not setup environment - with nested exception:
[weblogic.deployment.EnvironmentException: ejb-ref ejb/ReceiverSes requires an ejb-link or jndi-name]
weblogic.deployment.EnvironmentException: ejb-ref ejb/ReceiverSes requires an ejb-link or jndi-name
     at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:473)
     at weblogic.servlet.internal.CompEnv.init(CompEnv.java:123)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:5616)
     at weblogic.servlet.internal.WebAppServletContext.setActive(WebAppServletContext.java:5588)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:841)
     at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
     at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2399)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2311)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2479)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
     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)
--------------- nested within: ------------------
weblogic.management.DeploymentException: Could not setup environment - with nested exception:
[weblogic.deployment.EnvironmentException: ejb-ref ejb/ReceiverSes requires an ejb-link or jndi-name]
     at weblogic.servlet.internal.CompEnv.init(CompEnv.java:133)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:5616)
     at weblogic.servlet.internal.WebAppServletContext.setActive(WebAppServletContext.java:5588)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:841)
     at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
     at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2399)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2311)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2479)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
     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)

I found the issue. The below entries were missing from weblogic.xml
<ejb-reference-description>
<ejb-ref-name>ejb/PipelineExecutor</ejb-ref-name>
<jndi-name>${APPNAME}.BEA_personalization.PipelineExecutor</jndi-name>
</ejb-reference-description>
"rohit" <[email protected]> wrote:
>
Does anyone knows why we would get the below error. I verified the web.xml
and
it seems to be right. Any help appreciated. Rohit
<Jul 1, 2003 5:08:12 PM PDT> <Error> <Deployer> <149231> <The slave deployer
was
unable to set the activation state to true for the application portalApp
weblogic.management.ApplicationException: activate failed forceoportal
Module Name: ceoportal, Error: weblogic.j2ee.DeploymentException: Could
not setu
p environment - with nested exception:
[weblogic.deployment.EnvironmentException: ejb-ref ejb/PipelineExecutor
requires
an ejb-link or jndi-name]
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:1093)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContai
ner.java:1022)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForA
llApplications(SlaveDeployer.java:617)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:376)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:235)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
65)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
at weblogic.Server.main(Server.java:32)

Ejb-ref error when deploying a previously working ear on weblogic 8.1

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

ORABPEL-08033: EJB Transaction Error

Hi
I have a usecase in which procA(sync Service) calling procB (Async Service) and on completion of execution, ProcB gives a non blocking invoke back to procA. Condition: The either of one should be in running state always.
However there are fault situation in ProcB hence to not to break the sequence we have put a catchAll block which handles/logs and then gives the non blocking invoke back to procA.
But when ProcB fails somewhere because of some other partner links, it is safely going into catchAll and handling it well and when it tries to do a non blocking invoke it is resulting in following:
ORABPEL-08033
EJB Transaction Error.
EJB exception happened while invoking the partner. Please verify partner service.
Can somebody give me some leads in this?
TIA
regards
Joy

I have setup catch statements, both an catch all in the outermost scope and a catch for remote fault at the scope surrounding the call to the AQ. But that's not the issue. The problem is that BPEL don't get the error. The error stay's at the adapter and the BPEL don't come to a failed state.

Ejb-link not working when i access ejb in different ear

Hi All
I am here trying to access ejb's which is in different ear, I am providing ejb-link inside web.xml of war file deployed inside deffirent ear file.
I am using wls8.1sp5. I tried different combination with elb-link name , but its not working . <ejb-ref>
<ejb-ref-name>ejb/AuditService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.onstar.audit.ejb.AuditServiceHome</home>
<remote>com.onstar.audit.ejb.AuditService</remote>
<ejb-link>ccarenewal.jar#AuditService</ejb-link>
</ejb-ref>
<ejb-ref>
     <ejb-ref-name>ejb/AccountService</ejb-ref-name>
     <ejb-ref-type>Session</ejb-ref-type>
     <home>com.onstar.account.ejb.AccountServiceHome</home>
     <remote>com.onstar.account.ejb.AccountService</remote>
     <ejb-link>ccarenewal.jar#AccountService</ejb-link>
     </ejb-ref>
Exception:weblogic.management.ApplicationException: activate failed for sbwo Module: sbwo Error: weblogic.management.DeploymentException: Could not setup environment - with nested exception: [weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'ccarenewal.jar#AuditService' declared in the ejb-ref or ejb-local-ref 'ejb/AuditService' in the application module 'accountadj.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct.] weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'ccarenewal.jar#AuditService' declared in the ejb-ref or ejb-local-ref 'ejb/AuditService' in the application module 'accountadj.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct. at weblogic.deployment.EnvironmentBuilder.addEJBLinkRef(EnvironmentBuilder.java:658) at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:467) at weblogic.servlet.internal.CompEnv.init(CompEnv.java:123) at weblogic.servlet.internal.WebAppServletContext.activate
I will appreciate any help.
Rajiv

Rob,
Thanks for your reply.
Below is all deployment descriptor entries i have(ejb-jar.xml, weblogic-ejb-jar.xml, web.xml, weblogic.xml)
please correct me if i have wrong entries any where.
ejb-jar.xml
ejb-ref>
<description />
<ejb-ref-name>ejb/AccountService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.onstar.account.ejb.AccountServiceHome</home>
<remote>com.onstar.account.ejb.AccountService</remote>
<ejb-link>AccountService</ejb-link>
</ejb-ref>
weblogic-ejb-jar.xml
<ejb-reference-description>
<ejb-ref-name>ejb/AccountService</ejb-ref-name>
<jndi-name>cca/AccountService</jndi-name>
</ejb-reference-description>
web.xml
<ejb-ref>
<ejb-ref-name>ejb/AccountService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.onstar.account.ejb.AccountServiceHome</home>
<remote>com.onstar.account.ejb.AccountService</remote>
<ejb-link>ccarenewal.jar#AccountService</ejb-link>
</ejb-ref>
weblogic.xml
<ejb-reference-description>
<ejb-ref-name>ejb/AccountService</ejb-ref-name>
<jndi-name>cca/AccountService</jndi-name>
</ejb-reference-description>
I appreciate your help.
Thanks
Rajiv

Ejb-ref errore when deploying a previously working ear on weblogic 8.1

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
Thanks in advance!
Greets,
Luca
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

The issue is that WLS 6.1 didn't really support ejb-links properly. An
ejb-link should allow you to link a webapp or an ejb to another EJB
without requiring additional information or a global JNDI name on the
target EJB.
WLS 8.1 is following your ejb-link and telling you there's not enough
information.
You have 2 options:
1) Remove the <ejb-link>...</ejb-link> from your web.xml. You'll be
using just an ejb-reference at that point, but you've already included
the necessary information in the weblogic.xml that we can locate the EJB
via its global jndi-name
or
2) Change the ejb-link to be
<ejb-link>CustomMessaginBrick.jar#CustomMessagingBrick</ejb-link>
If you wanted to, you could then remove the reference info from the
weblogic.xml
-- Rob
luca wrote:
when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
Thanks in advance!
Greets,
Luca
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

Avk w/ ejb-links in different jars

Hello all,
I'm trying to use the 1.4.1 AVK and keep running into an issue.
I have an entity EJB jar and two session EJB jars, each with their own ejb-jar.xml.
In the entity jar's ejb-jar.xml I have:
=====
<ejb-name>Mydataobject</ejb-name>
=====
For each of the session jars, their ejb-jar.xml has a local reference:
=====
<ejb-local-ref id="EJBLocalRef_1">
<ejb-ref-name>com/mydomain/interfaces/MydataobjectLocalHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>com.mydomain.interfaces.MydataobjectLocalHome</local-home>
<local>com.mydomain.interfaces.MydataobjectLocal</local>
<ejb-link>Mydataobject</ejb-link>
</ejb-local-ref>
=======
Now, everything I've read regarding the EJB2.1 spec (specifically section 20.3.2) says this is how you can do this as long as all the jars are within the same application. So how come the AVK keeps coming failing with:
========
Error: No enterprise bean matching [ Mydataobject ] found within [ com.mydomain.session.ejb.<SessionOne or SessionTwo> ] JAR file.
Assertion:
EJB Link element test. Please refer to EJB 2.1 Specification Section #20.3.2 for further information.
Test Name:
tests.ejb.elements.EjbLinkElement
========
thanks, very confused.
-D

Try to consolidate the Session and Entity Beans into a single jar containing the consolidated ejb-jar.xml file having implementations for both Session and Entity.

External ejb reference error

Again WLS 8.1 SP1
i write by hand the weblogic.xml descriptor with the reference information for
an external ejb and im sure it's correct, but when i try to compile it with appc
it fails with this exception
Element "<ejb-jar>" with ejb-ref-name "xyz" must either specify a valid ejb-link
element or have corresponding ejb-reference-descriptor element in weblogic.xml
with a valid jndi-name.
This is my reference in weblogic.xml file
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>CnCargaFacade</ejb-ref-name>
<jndi-name>ejb.CnCargaFacade</jndi-name>
</ejb-reference-description>
</reference-descriptor>
of this web.xml
<ejb-ref>
<ejb-ref-name>CnCargaFacade</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>load.ejb.CnCargaFacadeHome</home>
<remote>load.ejb.CnCargaFacade</remote>
</ejb-ref>
This is not only if a try to use appc (which is not really necesary) but the error
is also when i try to deploy the application on my server.
Is this a Bug?? i thik it is, or where i'm wrong
Thanks

I believe it will solve both. In this case, appc and the server are
sharing some common code with a bug.
-- Rob
eric velazquez wrote:
Thanks for your time
Just one more question, this patch will solve too the deployment issue? or just
the appc compiler issue.
Thanks again
Rob Woollen <[email protected]> wrote:
Unfortunately I believe this is an appc bug. You should be able to get
a temporary patch from [email protected] Reference CR112803.
-- Rob
eric velazquez wrote:
Again WLS 8.1 SP1
i write by hand the weblogic.xml descriptor with the reference informationfor
an external ejb and im sure it's correct, but when i try to compileit with appc
it fails with this exception
Element "<ejb-jar>" with ejb-ref-name "xyz" must either specify a validejb-link
element or have corresponding ejb-reference-descriptor element in weblogic.xml
with a valid jndi-name.
This is my reference in weblogic.xml file
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>CnCargaFacade</ejb-ref-name>
<jndi-name>ejb.CnCargaFacade</jndi-name>
</ejb-reference-description>
</reference-descriptor>
of this web.xml
<ejb-ref>
<ejb-ref-name>CnCargaFacade</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>load.ejb.CnCargaFacadeHome</home>
<remote>load.ejb.CnCargaFacade</remote>
</ejb-ref>
This is not only if a try to use appc (which is not really necesary)but the error
is also when i try to deploy the application on my server.
Is this a Bug?? i thik it is, or where i'm wrong
Thanks

Ejb-link jndi issue

Hi,
I am trying to hook up a web service that talks to one of my EJBs. I feel that
I have followed the instructions to the letter, but no matter what I do I keep
getting a ServletException when I try to deploy it.
The EJB I am trying to invoke is deployed in an ejb module called SunstartEJBModule
which is deployed within an application called SunstartApplication.
This is the build file I am using:
<project name="buildWebservice" default="generate-typeinfo">
<target name="generate-typeinfo">
<source2wsdd
     javaSource="sunstart/ejbs/webservices/StudentWS.java"
     ejbLink="SunstartEJBModule.jar#ejb/StudentWS"
     ddFile="ddfiles/web-services.xml"
     serviceURI="/StudentService"
/>
</target>
<target name="generate-webservice">
<wspackage
output="ears/SunstartApplication.ear"
contextURI="web_services"
webAppClasses="com.sun.ad.sunstart.ejbs.webservices.StudentWS"
ddFile="ddfiles/web-services.xml"
overwrite="false"
/>
</target>
</project>
The SunstartWS ejb is definitely deployed as I can access it using my ServiceLocator
using java:comp/env/ejb/StudentWS. I notice in the server error log it is trying
to use a slightly different JNDI name to this - java:/app/ejb/SunstartEJBModule.jar#ejb/StudentWS/home
but I can't see how I can control this in the ant script because whenever I remove
the "SunstartEJBModule.jar#ejb/StudentWS" part and change it to "ejb/StudentWS"
it won't even deploy.
The full exception trace I am seeing is:
javax.servlet.ServletException: ERROR: The EJB component named: StudentWS specified
an ejb-link to SunstartEJBModule.jar#ejb/StudentWS, but this ejb-link could not
be found in JNDI. Please ensure that this ejb-link refers to a valid EJB, and
this EJB has already deployed. The exception was: javax.naming.NamingException:
Could not lookup EJB home, tried java:/app/ejb/SunstartEJBModule.jar#ejb/StudentWS/home
and java:/app/ejb/SunstartEJBModule.jar#ejb/StudentWS/localhome
     at weblogic.webservice.server.servlet.WebServiceServlet.initLocal(WebServiceServlet.java:132)
     at weblogic.webservice.server.servlet.WebServiceServlet.init(WebServiceServlet.java:86)
     at javax.servlet.GenericServlet.init(GenericServlet.java:258)
     at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:993)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:869)
     at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:848)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:787)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3252)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3197)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3174)
     at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5647)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:869)
     at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2022)
     at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2063)
     at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDeployer.java:2399)
     at weblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.java:2311)
     at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2479)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
     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)
>
If anyone know what I Am doing wrong I would be grateful if they would let me
know as this has been driving me nuts over the past few days!
Cheers,
Lucas.

Here is am working example of how to use source2wsdd
with an EJB.
http://manojc.com/?sample10
Please check if this works ok for you.
Regards,
-manoj
http://manojc.com
"Lucas King" <[email protected]> wrote in message
news:40d9b346$1@mktnews1...
>
Hi,
I am trying to hook up a web service that talks to one of my EJBs. I feelthat
I have followed the instructions to the letter, but no matter what I do Ikeep
getting a ServletException when I try to deploy it.
The EJB I am trying to invoke is deployed in an ejb module calledSunstartEJBModule
which is deployed within an application called SunstartApplication.
This is the build file I am using:
<project name="buildWebservice" default="generate-typeinfo">
<target name="generate-typeinfo">
<source2wsdd
javaSource="sunstart/ejbs/webservices/StudentWS.java"
ejbLink="SunstartEJBModule.jar#ejb/StudentWS"
ddFile="ddfiles/web-services.xml"
serviceURI="/StudentService"
/>
</target>
<target name="generate-webservice">
<wspackage
output="ears/SunstartApplication.ear"
contextURI="web_services"
webAppClasses="com.sun.ad.sunstart.ejbs.webservices.StudentWS"
ddFile="ddfiles/web-services.xml"
overwrite="false"
/>
</target>
</project>
The SunstartWS ejb is definitely deployed as I can access it using myServiceLocator
using java:comp/env/ejb/StudentWS. I notice in the server error log it istrying
to use a slightly different JNDI name to this -java:/app/ejb/SunstartEJBModule.jar#ejb/StudentWS/home
but I can't see how I can control this in the ant script because wheneverI remove
the "SunstartEJBModule.jar#ejb/StudentWS" part and change it to"ejb/StudentWS"
it won't even deploy.
The full exception trace I am seeing is:
javax.servlet.ServletException: ERROR: The EJB component named: StudentWSspecified
an ejb-link to SunstartEJBModule.jar#ejb/StudentWS, but this ejb-linkcould not
be found in JNDI. Please ensure that this ejb-link refers to a valid EJB,and
this EJB has already deployed. The exception was:javax.naming.NamingException:
Could not lookup EJB home, triedjava:/app/ejb/SunstartEJBModule.jar#ejb/StudentWS/home
and java:/app/ejb/SunstartEJBModule.jar#ejb/StudentWS/localhome
atweblogic.webservice.server.servlet.WebServiceServlet.initLocal(WebServiceSer
vlet.java:132)
atweblogic.webservice.server.servlet.WebServiceServlet.init(WebServiceServlet.
java:86)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
atweblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubI
mpl.java:993)
atweblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
t.java:317)
atweblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
atweblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java
:869)
atweblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.ja
va:848)
atweblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.jav
a:787)
atweblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletC
ontext.java:3252)
atweblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServlet
Context.java:3197)
atweblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServle
tContext.java:3174)
atweblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletConte
xt.java:5647)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:869)
atweblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2
022)
atweblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
a:2063)
atweblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activat
eContainer(SlaveDeployer.java:2592)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
atweblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.jav
a:2317)
atweblogic.management.deploy.slave.SlaveDeployer$Task.checkAutoCommit(SlaveDep
loyer.java:2399)
atweblogic.management.deploy.slave.SlaveDeployer$Task.prepare(SlaveDeployer.ja
va:2311)
atweblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
loyer.java:2479)
atweblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
yer.java:798)
atweblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
va:507)
atweblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
ava:465)
atweblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
va:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
If anyone know what I Am doing wrong I would be grateful if they would letme
know as this has been driving me nuts over the past few days!
Cheers,
Lucas.

Javax.naming.NameNotFoundException: Unable to resolve ejb-link.

Env: JDK 1.3.1_08
Weblogic: 7.0
We are attempting to use EJB's (session) and have it all localized in a jar.
The Business and Custom Logic is all compiled to WEB-INF/classes. All the jars including the EJB jar is under WEB-INF/lib.
On Startup Weblogic throws the error message
weblogic.management.ApplicationException: activate failed for application
Module Name: application, Error: weblogic.j2ee.DeploymentException: Could not setup environment - with nested exception:
[javax.naming.NameNotFoundException: Unable to resolve ejb-link. Appejb.jar#AppServerBean is not in the context. The context includes the following link bindings: {} Make sure the link reference is relative to the URI of the referencing module.]
I have tried using the ../ notation before the Appejb.jar in the web.xml and what not, but that does not work either.
I have sucesfully deployed the EJB jar through the weblogic console.
Any Clues or suggestions will be most appreciated..
thanks
-a

Create a ear application from the ejb jar and web application war.
Copy ear application to the applications directory.
In the ejb-link element in web.xml specify the relative path to the ejb jar.
<ejb-link>../Appejb.jar</ejb-link>
thanks,
Deepak
Akshay <[email protected]> wrote:
Env: JDK 1.3.1_08
Weblogic: 7.0
We are attempting to use EJB's (session) and have it all localized in
a jar.
The Business and Custom Logic is all compiled to WEB-INF/classes. All
the jars including the EJB jar is under WEB-INF/lib.
On Startup Weblogic throws the error message
weblogic.management.ApplicationException: activate failed for application
Module Name: application, Error: weblogic.j2ee.DeploymentException: Could
not setup environment - with nested exception:
[javax.naming.NameNotFoundException: Unable to resolve ejb-link. Appejb.jar#AppServerBean
is not in the context. The context includes the following link bindings:
{} Make sure the link reference is relative to the URI of the referencing
module.]
I have tried using the ../ notation before the Appejb.jar in the web.xml
and what not, but that does not work either.
I have sucesfully deployed the EJB jar through the weblogic console.
Any Clues or suggestions will be most appreciated..
thanks
-a

Linker Error during compiling ODBC WinCE C++_Sample Project

I am devloping a ODBC application for PocketPC2003 using OLite 10g Release 10.3.0.2. before that i am understanding the sample application provided with Olite.
I followed all the instructions provided in ReadMe.txt file available before using VC++ sample. After making all the settings and compiling i am getting following linker errors as mentioned below.
Any solution for this problem at the earliest will be appreciated, i have tried link all the libraries provided with WinCE armv4.
Linker Error Messages:
Error     1     error LNK2019: unresolved external symbol SQLExecDirect referenced in function "public: virtual __cdecl CSQLResult::~CSQLResult(void)" (??1CSQLResult@@UAA@XZ)     dbaccess.obj
Error     2     error LNK2019: unresolved external symbol SQLFreeStmt referenced in function "public: virtual __cdecl CSQLResult::~CSQLResult(void)" (??1CSQLResult@@UAA@XZ)     dbaccess.obj
Error     3     error LNK2019: unresolved external symbol SQLGetData referenced in function "public: class CRowObj const * __cdecl CSQLResult::Fetch(int)" (?Fetch@CSQLResult@@QAAPBVCRowObj@@H@Z)     dbaccess.obj
Error     4     error LNK2019: unresolved external symbol SQLFetch referenced in function "public: class CRowObj const * __cdecl CSQLResult::Fetch(int)" (?Fetch@CSQLResult@@QAAPBVCRowObj@@H@Z)     dbaccess.obj
Error     5     error LNK2019: unresolved external symbol SQLFreeEnv referenced in function "public: void __cdecl COLiteDB::Disconnect(void)" (?Disconnect@COLiteDB@@QAAXXZ)     dbaccess.obj
Error     6     error LNK2019: unresolved external symbol SQLFreeConnect referenced in function "public: void __cdecl COLiteDB::Disconnect(void)" (?Disconnect@COLiteDB@@QAAXXZ)     dbaccess.obj
Error     7     error LNK2019: unresolved external symbol SQLDisconnect referenced in function "public: void __cdecl COLiteDB::Disconnect(void)" (?Disconnect@COLiteDB@@QAAXXZ)     dbaccess.obj
Error     8     error LNK2019: unresolved external symbol SQLConnect referenced in function "public: int __cdecl COLiteDB::Connect(void)" (?Connect@COLiteDB@@QAAHXZ)     dbaccess.obj
Error     9     error LNK2019: unresolved external symbol SQLAllocConnect referenced in function "public: int __cdecl COLiteDB::Connect(void)" (?Connect@COLiteDB@@QAAHXZ)     dbaccess.obj
Error     10     error LNK2019: unresolved external symbol SQLAllocEnv referenced in function "public: int __cdecl COLiteDB::Connect(void)" (?Connect@COLiteDB@@QAAHXZ)     dbaccess.obj
Error     11     error LNK2019: unresolved external symbol SQLError referenced in function "public: class CSQLResult * __cdecl COLiteDB::Execute(wchar_t const *)" (?Execute@COLiteDB@@QAAPAVCSQLResult@@PB_W@Z)     dbaccess.obj
Error     12     error LNK2019: unresolved external symbol SQLDescribeCol referenced in function "public: class CSQLResult * __cdecl COLiteDB::Execute(wchar_t const *)" (?Execute@COLiteDB@@QAAPAVCSQLResult@@PB_W@Z)     dbaccess.obj
Error     13     error LNK2019: unresolved external symbol SQLNumResultCols referenced in function "public: class CSQLResult * __cdecl COLiteDB::Execute(wchar_t const *)" (?Execute@COLiteDB@@QAAPAVCSQLResult@@PB_W@Z)     dbaccess.obj
Error     14     error LNK2019: unresolved external symbol SQLAllocStmt referenced in function "public: class CSQLResult * __cdecl COLiteDB::Execute(wchar_t const *)" (?Execute@COLiteDB@@QAAPAVCSQLResult@@PB_W@Z)     dbaccess.obj

Hi,
The OLITE forum (Database Mobile Server (inc. legacy Database Lite) would be a better place to post your issue. This forum deals with the ODBC driver that connects to a "normal" Oracle database.
Hope it helps,
Greg
Edited by: gdarling on Nov 12, 2008 8:31 AM

The broken link error

Hi,
Please help me with this broken link error in Office Excel 2010. Thank you.
The problem is: a broken link cannot be removed from the file. The link was used in data validation, which refers to a list of values. After the path was corrected, it still shows there’s a broken link. Here are the details:
I have 4 files named “000TVA_Test – 3”, “000TVA_Test – 4”, “000TVA_Test – 5”, and “000TVA_Test – 6”. The posterior files were developed based on the previous files.
In Test-3, sheet “Template “, cell “L4”, “O4”, “R4”… were built as dropdown list using data validation. The list source is in the “Library” worksheet. There’s no problem so far.
Test-4 was firstly copied from Test-3. In this file I renamed the worksheet from “Library” to “Setting” and the link was broken from here. I can also fix the broken link in this file. (While I didn’t realize there was a broken link.)
In Test-5 I fixed the path, but every time when opening the file, the broken link still shows.
In Test-6 I’ve removed the data validations. The broken link is still there.
I tried to find solutions online. I tried common methods, cannot find anything in the files is still using links. I also tried the “findlink.xla” add-in, but it only worked for Test-4, and couldn’t find the link in other files.
Please help. Thank you!
I uploaded files here: https://onedrive.live.com/redir?resid=1A97736E0ABBAA41!113&authkey=!AF5wAd9rwUPnYyE&ithint=folder%2cxlsm
Thanks again!

Hi,
Based on my tested the files downloaded, I found that Test-5 & Test-6 included the "A defined name that refers to an external workbook", Test-4 had not. (Please click Formula Tab>Name Manage, you'll see them.)
However, the Break Links command cannot break the following types of links:
A defined name that refers to an external workbook
A ListBox control with an input range that refers to an external workbook.
A DropDown control with an input range that refers to an external workbook.
http://support2.microsoft.com/kb/291984/en-us (It also applies to Excel 2010)
Thus, we'd better try the workaround： re-build the Test-5 & Test 6.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Error while running ejbc. Fatal error from EJB Compiler ---- Error while pr

Hi!
I was deploying a test application for a session bean with sun 1 studio 5 and I started getting this message while deploying.
I had tested the bean previously and I had no problems.
I found this in the sun app server 7 release notes, but I don't understand what I'm supposed to do...
"Deployment of CMP beans fails.
The following error is thrown because there are no <query-params> entries in the container-managed persistence (CMP) bean in sun-ejb-jar.xml file:
Error while running ejbc. Fatal error from EJB Compiler ---- Error while processing CMP beans.
Solution
Even if it isn't necessary for the CMP beans, add the query-params tag for finders in the sun-ejb-jar.xml file with the empty parameters."
Here is my sun-ejb-jar.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 EJB 2.0//EN" "http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_0-0.dtd">
<sun-ejb-jar>
<enterprise-beans>
<name>GestorDoBanco_EJBModule</name>
<ejb>
<ejb-name>Cliente</ejb-name>
<jndi-name>ejb/Cliente</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/Cliente.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>ClienteAssociadoAConta</ejb-name>
<jndi-name>ejb/ClienteAssociadoAConta</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/ClienteAssociadoAConta.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>Conta</ejb-name>
<jndi-name>ejb/Conta</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/Conta.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>GestorDoBanco</ejb-name>
<jndi-name>ejb/GestorDoBanco</jndi-name>
<pass-by-reference>false</pass-by-reference>
</ejb>
<ejb>
<ejb-name>MensagemM003</ejb-name>
<jndi-name>ejb/MensagemM003</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM003.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>MensagemM003Rejeitada</ejb-name>
<jndi-name>ejb/MensagemM003Rejeitada</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM003Rejeitada.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>MensagemM012</ejb-name>
<jndi-name>ejb/MensagemM012</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM012.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>MensagemM012Rejeitada</ejb-name>
<jndi-name>ejb/MensagemM012Rejeitada</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM012Rejeitada.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>MensagemM103</ejb-name>
<jndi-name>ejb/MensagemM103</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM103.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>MensagemM112</ejb-name>
<jndi-name>ejb/MensagemM112</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/MensagemM112.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>Registo</ejb-name>
<jndi-name>ejb/Registo</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/Registo.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>TransaccaoConfirmada</ejb-name>
<jndi-name>ejb/TransaccaoConfirmada</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/TransaccaoConfirmada.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>TransaccaoFinalizada</ejb-name>
<jndi-name>ejb/TransaccaoFinalizada</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/TransaccaoFinalizada.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<ejb>
<ejb-name>TransaccaoIniciada</ejb-name>
<jndi-name>ejb/TransaccaoIniciada</jndi-name>
<pass-by-reference>false</pass-by-reference>
<cmp>
<mapping-properties>pcImpl0/moduleComp1/Data/TransaccaoIniciada.mapping</mapping-properties>
</cmp>
<refresh-period-in-seconds>600</refresh-period-in-seconds>
</ejb>
<pm-descriptors>
<pm-descriptor>
<pm-identifier>SunONE</pm-identifier>
<pm-version>1.0</pm-version>
<pm-class-generator>com.iplanet.ias.persistence.internal.ejb.ejbc.JDOCodeGenerator</pm-class-generator>
<pm-mapping-factory>com.iplanet.ias.cmp.NullFactory</pm-mapping-factory>
</pm-descriptor>
<pm-inuse>
<pm-identifier>SunONE</pm-identifier>
<pm-version>1.0</pm-version>
</pm-inuse>
</pm-descriptors>
<cmp-resource>
<jndi-name>mysqlpmanager</jndi-name>
<default-resource-principal>
<name>bes</name>
<password>besbes</password>
</default-resource-principal>
</cmp-resource>
</enterprise-beans>
</sun-ejb-jar>
Thanks in advance for any help.
Nuno

http://docs.sun.com/source/817-2175-10/decmp.html
Please go to the above docs and look thru the examples given in it.
Example 2
This query returns all products in a specified price range. It defines two query parameters which are the lower and upper bound for the price: double low, double high. The filter compares the query parameters with the price field:
"low < price && price < high"
The finder element of the sun-ejb-jar.xml file would look like this:
<finder>
<method-name>findInRange</method-name>
<query-params>double low, double high</query-params>
<query-filter>low < price && price &lt
high</query-filter
</finder>
I hope this hepls. In your case u just have to make it null.

I am getting an linker error LNK2001 : unresolved symbol _main while compiling Microsoft c code

I am writng a simple application in C language for communicating with GPIB. when I compile the c file I am getting a linker error
LIBC.lib(ctr0.obj): LNK2001 error: unresolved sysmbol _main
I compile the application in the dos window using the command
cl gpibApplication.c gpib-32.obj.
Could anyone tell me how to remove this error

Hello-
It sounds like the main function is missing from the gpibApplication.c file. Be sure that the following function is somewhere in the code:
int main (int argc, char *argv[])
Also, note that this function is case sensitive, so be sure main is not capitalized.
Randy Solomonson
Application Engineer
National Instruments

Ejb-link error

Similar Messages

Maybe you are looking for