Lookup of local ejbHome in WSAD

I want to do lookup of ejbLocalHome through Web Module in WSAD (websphere studio application developer). Everytime I get NameNotFound Exception at run time. Is there anything particular regarding look up of EJBLocalHome in WSAD/Websphere environment ?
Thanks.

What is the string you are using to look it up? i.e. "java:comp/env/MyCoolNewEjbHome"

Similar Messages

Fail to lookup the local EJB by JNDI in Managed Server

Hi all,
I currently in a deep problem, and can't figure out the cause of it. It just annoying me for week.
In my app, I have binded to the local ejb to JNDI (let's say "ejb/CustomerLocal"), then the client lookup the Local EJB by the following code.
localIc = new InitialContext();
home = (EJBLocalHome)localIc.lookup("ejb/CustomerLocal");
It works well as I do development in the Domain Admin Server. However, when I do the System Integration Test and deploy my app to the managed server, the app fail. It just can't do the Local EJB lookup. Following is the exception.
javax.naming.NameNotFoundException: Unable to resolve 'ejb/CustomerLocal' Resolved ejb[Root exc
eption is javax.naming.NameNotFoundException: Unable to resolve 'ejb.CustomerLocal' Resolved ejb
]; remaining name CustomerLocal'
Does anybody know the cause of it and have solution?
Thanks a lot

Hi,
Just now I replicated the same problem what you are facing. I created one managed server. When I deployed my ejb to admin server I did not get any problem. But when I deploy the same into my managed server I got Naming Exception. Because I did n/t specify Context.PROVIDER_URL. A provider URL contains bootstrap server information that the initial context factory can use to obtain an initial context. So when you deploy EJB on another server, you have to get the Naming service from that server. Hence provider URL must pointing to that server. So I included following statements before lookup my ejb in managed server.
Properties p=new Properties ();
p.put (Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
p.put (Context.PROVIDER_URL,"t3://localhost: 7003");
Context ctx=new InitialContext (p);
FacadeHome home=(FacadeHome) ctx.lookup ("ejb/CustomerLocal");
In my case managed server port number is 7003. Now onwards managed server (Port number 7003) will provide ‘Naming Service’, not by admin server (port number 7001), which is default.
Note: Context.PROVIDER_URL— specifies the URL of the WebLogic Server that provides the name service. The default is t3://localhost: 7001. When you are not specified it will assume that POVIDER_URL is t3://localhost: 7001 this is nothing but your admin server in your case. However, a JNDI client may need to access a name space other than the one identified in its environment. In this case, it is necessary to explicitly set the java.naming.provider.url (provider URL) property used by the InitialContext constructor.
I hope it helps.
Regards,
Kuldeep Singh.

Howto: portable bind, lookup remote + local beans (EJB3) to JNDI with WL 10

I struggle writing portable ejb3 applications with weblogic.
I have a JEE5 (EJB3) application using the standard and it works fine on JBoss and WebSphere.
Porting it to Weblogic (10.0) there are quite a lot of problems, mainly
in the area of JNDI lookups of EJBs.
So the issue is how to configure the JNDI-Names of local and remote beans (EJB3!)
in a portable way with Weblogic without making the application unportable.
The biggest problem is caused by the fact, that WL 10 does not bind the EJBs
to the JNDI-tree by default. The bound name would not really be important (JBoss and WebSphere
come up with a value that can easily be used for a generic lookup). Just any binding
would be fine.
So there has to be some extra step in order to get WL 10 binding a remote or local
bean into the JNDI tree. Unfortunately none of them works/is acceptable in an portable JEE app.
Idea1: Using the "mappedName" attribute (of @Stateless, @Stateful)
Well, this one is not portable as the documentation states:
[http://edocs.bea.com/wls/docs100/ejb30/annotations.html#wp1417411|http://edocs.bea.com/wls/docs100/ejb30/annotations.html#wp1417411]
Idea2: Using @weblogic.ejbgen.JndiName
Using weblogic's annotation JndiName also doesn't bind the bean to the given names:
@Stateless
@weblogic.ejbgen.JndiName(local="myapp/XBean/local",remote="myapp/XBean/remote")
public class XBean implements XLocal {
Besides this, that code would not be portable (as nobody wants an weblogic.jar within another application server).
Idea3: Using weblogic-ejb-jar.xml
Mapping a bean using the weblogic-ejb-jar.xml below, also doesn't work.
The bean is not bound to the given name "myapp/XBean/remote":
Exception in thread "main" javax.naming.NameNotFoundException:
Unable to resolve 'myapp.XBean.remote'. Resolved 'myapp.XBean' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'myapp.XBean.remote'. Resolved 'myapp.XBean']; remaining name 'remote'
Looking at the JNDI tree, there is "something" bound to "myapp.XBean", but it is not the bean.
Doing a lookup with this name ("myapp/XBean" or "myapp.XBean"), gives this:
Exception in thread "main" java.lang.ClassCastException: weblogic.jndi.internal.WLContextImpl cannot be cast to test.server.XRemote
at test.client.Client.main(Client.java:14)
Question 1) What is the preferred way to bind and lookup a remote bean in Weblogic 10?
Again: the goal is to use pure EJB3.
Question 2) What is the preferred way to bind and lookup a local bean in WL 10?
This lookup has to be done on the server in some "unmanaged" classes
where injection doesn't work.
If there is an unportable way to bind a local bean to jndi, it might do for the time.
The important thing would be, that there is no weblogic specific code within the application.
So, solving it using weblogic-xml files would be best.
This declaration
<local-jndi-name>myapp/XBean/local</local-jndi-name>
will come up with the same problems, I guess.
Here's the code. We want the local interface extending the remote interface,
so that the local beans can do all what the remote beans can do too.
XRemote.java
package test.server;
import javax.ejb.Remote;
@Remote
public interface XRemote {
String JNDI_NAME = "myapp/XBean/remote";
void doXRemote();
XLocal.java
package test.server;
import javax.ejb.Local;
@Local
public interface XLocal extends XRemote {
String JNDI_NAME = "myapp/XBean/local";
void doXLocal();
XBean.java
package test.server;
import javax.ejb.Stateless;
@Stateless
public class XBean implements XLocal {
@Override
public void doXLocal() {
System.out.println("doXLocal() called");
@Override
public void doXRemote() {
System.out.println("doXRemote() called");
weblogic-ejb-jar.xml
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/10.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>XBean</ejb-name>
<jndi-name>myapp/XBean/remote</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Client.java
package test.client;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import test.server.XRemote;
public class Client {
public static void main(String[] args) throws NamingException {
InitialContext context = getInitialContext();
XRemote xRemote = (XRemote) context.lookup(XRemote.JNDI_NAME);
xRemote.doXRemote();
private static InitialContext getInitialContext() throws NamingException {
Properties properties = new Properties();
properties.put(Context.PROVIDER_URL, "t3://localhost:7001");
properties.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
properties.put(Context.SECURITY_PRINCIPAL, "weblogic");
properties.put(Context.SECURITY_CREDENTIALS, "weblogic");
return new InitialContext(properties);
}

Hi,
about how to specify jndi name of remote ejb, please refer to this link: http://forums.oracle.com/forums/thread.jspa?threadID=800314&tstart=1
please note @JNDIName isn't an EJBGen annotation. its package name is weblogic.javaee.
So far, based on the EJB spec, local ejb will not be bound to global JNDI. EJB3.1 specification is trying to specify the portable JNDI names including local EJBs, but it isn't published yet.
local EJB is used within one application and ejb reference is used to lookup the local EJB. please refer to EJB specification about how to declare an EJB local reference. once it is declared, it can be looked up from the java:comp\env JNDI namespace.
But, if the local client of the EJB isn't a JavaEE component, there won't be any declaration of ejb-local-ref. You may want to try remote access to the EJB from the non-JavaEE client.

Lookup for local interfaces.

Isn't lookup for local interfaces allowed from web client. I have defined a
ejb-reference for the bean in my web.xml. When I do a lookup as
TestBeanLocalHome home = (TestBeanLocalHome)
ic.lookup("java:comp/env/ejb/TestBeanLocal");
This statement result in an error
javax.naming.NameNotFoundException: Unable to resolve
comp/env/ejb/TestSLSBeanLocal/ Resolved: 'comp/env/ejb'
Unresolved:'TestBeanLocal' ; remaining name ''
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingN
ode.java:887)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:183)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:339)
at
weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWr
apper.java:36)
at
weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:124
at javax.naming.InitialContext.lookup(InitialContext.java:345)
at jsp_servlet.__client._jspService(__client.java:108)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2495)
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)
The same thing works when lookup is done for remote interface.
Regards,
Rupesh.

You need to use "ejb-local-ref" to refer to local interfaces. I meant
"ejb-local-ref" element was not available in web.xml in Servlet 2.2. They
were added in Servlet 2.3 specification. So unless your app server is
Servlet 2.3 compliant it does not need to support references to local
interfaces in web components (servlets or jsps). Weblogic 6.1 did not seem
to support them last time I tried.
-- Anand
"Rupesh" <[email protected]> wrote in message
news:[email protected]...
what do u mean by local interface in web component? its ejb's local
interfaces and lookups are any way being
done using ejb-ref and ref mapping are given in weblogic.xml.
Where does Servlet spec come into the picture?
Do you mean to say that you can not lookup for local home from a jsp in
WL6.1?
Regards,
Rupesh.
Anand Byrappagari <[email protected]> wrote in message
news:[email protected]...
Are you using Weblogic 6.1? Then local interfaces in web components arenot
supported. Local interfaces were added only in Servlet 2.3 I think.Weblogic
6.1 is not completely compliant with Servlet 2.3.
-- Anand
"Rupesh" <[email protected]> wrote in message
news:[email protected]...
Isn't lookup for local interfaces allowed from web client. I have
defined
a
ejb-reference for the bean in my web.xml. When I do a lookup as
TestBeanLocalHome home = (TestBeanLocalHome)
ic.lookup("java:comp/env/ejb/TestBeanLocal");
This statement result in an error
javax.naming.NameNotFoundException: Unable to resolve
comp/env/ejb/TestSLSBeanLocal/ Resolved: 'comp/env/ejb'
Unresolved:'TestBeanLocal' ; remaining name ''
at
weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingN
ode.java:887)
at
weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
atweblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:183)
atweblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
atweblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
atweblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
atweblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:339)
at
weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWr
apper.java:36)
at
weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:124
at javax.naming.InitialContext.lookup(InitialContext.java:345)
at jsp_servlet.__client._jspService(__client.java:108)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2495)
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)
The same thing works when lookup is done for remote interface.
Regards,
Rupesh.

Lookup for local home interface

Hi!
I am using the j2eesdk and there is a thing I cannot find anywhere:
When I use a local interface for a bean and define an EJB Ref on that bean in the 'deploytool', I cannot specify a JNDI name (only a bean name). Therefore I cannot map the coded name in my Context-lookup() call in the code to any JNDI name on the applications 'JNDI Names' tab.
My question is:
- how do I lookup local home interfaces?
- if this is done via JNDI, how do I do this in the deploytool?
Kind Regards
Ralf

Hi
The point u all should understand is you use a jndi name in your programs
say
public static void main(String[] args)
InitalContext ctx = new IntialContext();
ctx=(Context)ctx.lookup("java:comp/env");
DemoLocalHome home = ctx.lookup("ejb/DemoBean");
in the above program you use "ejb/DemoBean" as a reference name, but actually there won't be a Bean registered with that name. so, when u deploy the appclient u should map the reference name with the actual JNDI name ( if it's a remote interface) or with the class name (Local interface)
so, when u deploy the appclient in the "ejb ref " tab, u specify that it uses Local interfaces and in the end u don't map the refernce name to a JNDI name( because it's a local interface) and rather u speciy the class name.
that's how u map the references for Remote and Local home interfaces.....
thank's for listening to that......
for more suggestions mail me at [email protected]

Problems while performing lookup for Local EJBs

Can anybody tell me how can i perform local ejb lookup in Sun app Server 8.0/8.1 ?
I have following entries in ejb-jar.xml.
<?xml version="1.0" encoding="UTF-8"?>
<!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 >
<ejb-name>TeamLeaderBean</ejb-name>
<local-home>spring.ejb.example.TeamLeaderLocalHome
</local- home>
<local>spring.ejb.example.TeamLeaderLocal</local>
<ejb-class>spring.ejb.example.TeamLeaderBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor></assembly-descriptor>
</ejb-jar>
In sun-ejb-jar.xml I have
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>TeamLeaderBean</ejb-name>
<jndi-name>TeamLeaderBeanLocal</jndi-name>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
In the client EJBs code I have used following ways of performing lookup...
ctx.lookup("java:comp/env//TeamLeaderBeanLocal");
ctx.lookup("java:comp/env/ejb/local/TeamLeaderBeanLocal");
ctx.lookup("ejb/TeamLeaderBeanLocal");
Unfortunately none of these performs a successful lookup...???
Can anybody solve my problem?

In order to look up a local EJB from an EJB client you have to add an <ejb-local-ref> element for client EJB. So:
<session>
<ejb-name>MyClientEJB</ejb-name>
<ejb-local-ref>
<ejb-ref-name>ejb/TeamLeaderBeanLocal</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<ejb-link>TeamLeaderBeanLocal</ejb-link>
</ejb-local-ref>
</session>
fil
Can anybody tell me how can i perform local ejb
lookup in Sun app Server 8.0/8.1 ?
I have following entries in ejb-jar.xml.
<?xml version="1.0" encoding="UTF-8"?>
<!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 >
<ejb-name>TeamLeaderBean</ejb-name>
<local-home>spring.ejb.example.TeamLeaderLocalHome
</local- home>
<local>spring.ejb.example.TeamLeaderLocal</local>
<ejb-class>spring.ejb.example.TeamLeaderBean</ejb-clas
s>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor></assembly-descriptor>
</ejb-jar>
In sun-ejb-jar.xml I have
<sun-ejb-jar>
<enterprise-beans>
<ejb>
<ejb-name>TeamLeaderBean</ejb-name>
<jndi-name>TeamLeaderBeanLocal</jndi-name>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
In the client EJBs code I have used following ways of
performing lookup...
ctx.lookup("java:comp/env//TeamLeaderBeanLocal");
ctx.lookup("java:comp/env/ejb/local/TeamLeaderBeanLoca
l");
ctx.lookup("ejb/TeamLeaderBeanLocal");
Unfortunately none of these performs a successful
lookup...???
Can anybody solve my problem?

Unable to lookup ejb local home interface after moving to wls 7.0

I'm getting an exception trying to lookup an ejb's local home interface
which I believe was deployed correctly. On startup I get the message:
EJB Deployed EJB with JNDI name
com.logistics.basedata.ejb.shipperspecificfveb.ShipperSpecificFVDOLocalHome.
However, when I try to do a lookup using this jndi name, I get the
following exception:
javax.naming.LinkException: . Root exception is
javax.naming.NameNotFoundException: Unable to resolve
'app/ejb/ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificfveb/local-home'
Resolved: 'app/ejb'
Unresolved:'ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificfveb'
; remaining name
'ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificfveb/local-home'
The name it can't resolve is different than the name I was trying to
look up. I can see
com.logistics.basedata.ejb.shipperspecificfveb.ShipperSpecificFVDOLocalHome
in the jndi tree through the admin console, but the attributes Object
Class, Object Hash Code, and Object To String are blank.
This worked with weblogic 6.1 sp3. Is there something I missed in the
migration to 7.0?
Any help would be appreciated. Thanks in advance,
-Brad

That explains it - in 7.0 (unlike 6.1 - then the only factor was
classloaders arrangement) client has to be
in the same application (ear) - note JNDI links used to be able to lookup
local homes.
"Brad Geddes" <[email protected]> wrote in message
news:[email protected]...
I'm looking it up from a web application. I did notice a message on thistopic
from last thursday (subject: "Pls Help! Failed to access local Sessionbean in
7.0!"). In it, the individual said he had to add ejb-local-ref elementsin the
web.xml. I tried this but can't seem to get it to work.
javax.naming.NameNotFoundException: Unable to resolve ejb-link.
ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificfveb isnot in
the context. The context includes the following link bindings: {} Makesure the
link reference is relative to the URI of the referencing module.
Also, I don't have a war or ear in the environment I'm working in; theejb's are
all deployed separately in jar files, and the web app is in explodedformat.
>
-Brad
"Dimitri I. Rakitine" wrote:
Are you looking up the local home from outside of an application ?
"Brad Geddes" <[email protected]> wrote in message
news:[email protected]...
I'm getting an exception trying to lookup an ejb's local home
interface
which I believe was deployed correctly. On startup I get the message:
EJB Deployed EJB with JNDI name
com.logistics.basedata.ejb.shipperspecificfveb.ShipperSpecificFVDOLocalHome.
>>>
However, when I try to do a lookup using this jndi name, I get the
following exception:
javax.naming.LinkException: . Root exception is
javax.naming.NameNotFoundException: Unable to resolve
'app/ejb/ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificf
veb/local-home'
Resolved: 'app/ejb'
Unresolved:'ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecif
icfveb'
; remaining name
'ShipperSpecificFVDO.jar#com.logistics.basedata.ejb.shipperspecificfveb/loca
l-home'
The name it can't resolve is different than the name I was trying to
look up. I can see
com.logistics.basedata.ejb.shipperspecificfveb.ShipperSpecificFVDOLocalHome
in the jndi tree through the admin console, but the attributes Object
Class, Object Hash Code, and Object To String are blank.
This worked with weblogic 6.1 sp3. Is there something I missed in the
migration to 7.0?
Any help would be appreciated. Thanks in advance,
-Brad
Dimitri--
Dimitri

GWIA doing DNS lookup for local address

Hello,
I am running GW8.0.2 on Netware 6.5sp8. I have a server that our recreation department uses to send out confirmation emails when a customer signs up for a class. The recreation server and the GWIA are on the same subnet.
Here's the problem: When the Rec server sends out the first email confirmation, it gets sent out successfully. Subsequent emails after that fail. After about twenty minutes the next email will go out OK again but subsequent emails will fail.
The verbose logs on the GWIA don't tell me much but the diagnostic logs show what looks like a reverse DNS lookup happening at the GWIA for my local IP address of 10.0.0.3 (the Rec server). This reverse DNS lookup fails (probably a timeout) and subsequent emails from this local Rec server get dropped by the GWIA without the DNS lookup.
DNS is being done by DNS proxy on Bordermanager 9.2. I've bypassed the Bordermanager DNS and the same thing happens. I've made entries for the local Rec server into a route.cfg file but the GWIA seems to want to ignore these entries and keeps doing the DNS lookup.
The wierdest part of the puzzle is that if I restart the proxy on the Bordermanager the next email will go out with, of course, subsequent emails failing. I've looked at the proxy dns cache and can't even find an entry for my Rec server.
Attached are the entries from the Diagnostic logs of the GWIA. Novell tech support has assured me that the GWIA and the BM are working fine. I am also having this problem with a scanner that scans then emails but all other email and Bordermanager are functioning fine. This server and scanner were not having this problem before upgrading to GW8.0.2.
I don't understand why GWIA is doing DNS lookups for a local address and I don't know what I can do to stop it. Any help would be greatly appreciated.
This is a successful transfer right after restarting the proxy: 10.0.0.3 is the Rec server, 10.0.0.130 is the GWIA and 10.0.0.1 is the Bordermanager.
16:04:13 D15 NgwResQuery(3.0.0.10.in-addr.arpa, 1, 12)
16:04:13 D15 Querying server (# 1) address = 10.0.0.1
16:04:13 D15 HEADER:
16:04:13 D15 opcode = QUERY, id = 17615, rcode = SERVFAIL, flags: qr aa rd
16:04:13 D15 query = 1, answer = 0, authority = 0, additional = 0
16:04:13 D15
16:04:13 D15 QUESTIONS:
16:04:13 D15 3.0.0.10.in-addr.arpa, type = PTR, class = IN
16:04:13 D15
16:04:13 D15 rcode = 2, ancount=0
16:04:13 D15 NgwResQuery failed
16:04:13 D15 DMN: MSG 2000909 Accepted connection: [10.0.0.3] ()
16:04:13 D15 Successful login with client/server access: 10.0.0.130:1677
16:04:13 D15 DMN: MSG 2000909 Receiving file: ECMAIL/SYS:\PROGRAMS\GRPWISE\WPGATE\GWIA\3RD\receive\df30 fad4.221
16:04:13 D15 DMN: MSG 2000909 SMTP session ended: [10.0.0.3] ()
This is an unsuccessful transfer:
16:06:08 D04 timeout
16:06:08 D04 NgwResQuery: send error
16:06:08 D04 NgwResQuery failed
16:06:08 D04 DMN: MSG 2000933 Accepted connection: [10.0.0.3] ()
16:06:08 D04 DMN: MSG 2000933 SMTP session ended: [10.0.0.3] ()
Then the successful email comes back into the system:
16:06:26 AA8 MSG 2000909 Processing inbound message: ECMAIL/SYS:\PROGRAMS\GRPWISE\WPGATE\GWIA\receive\DF30FAD4 .221
16:06:26 AA8 MSG 2000909 Sender: [email protected]
16:06:26 AA8 MSG 2000909 Recipient: [email protected]
16:06:26 AA8 MSG 2000909 Queuing to MTA
16:06:26 AA8 MSG 2000909 File: ECMAIL/SYS:\PROGRAMS\GRPWISE\WPGATE\GWIA\wpcsin\4\4daf048 2.8m1 Message Id: (4DAF66F2.B67:244:35687) Size: 163.3 Kb

Thanks Massimo. I could have swore I already did that but when I did it again just to make sure it solved the problem. Appreciate the help. Have a good one.
Originally Posted by mrosen
On 02.05.2011 21:06, avanrav wrote:
>
> Hello,
>
> I am running GW8.0.2 on Netware 6.5sp8. I have a server that our
> recreation department uses to send out confirmation emails when a
> customer signs up for a class. The recreation server and the GWIA are on
> the same subnet.
>
> Here's the problem: When the Rec server sends out the first email
> confirmation, it gets sent out successfully. Subsequent emails after
> that fail. After about twenty minutes the next email will go out OK
> again but subsequent emails will fail.
>
> The verbose logs on the GWIA don't tell me much but the diagnostic logs
> show what looks like a reverse DNS lookup happening at the GWIA for my
> local IP address of 10.0.0.3 (the Rec server). This reverse DNS lookup
> fails (probably a timeout) and subsequent emails from this local Rec
> server get dropped by the GWIA without the DNS lookup.
>
> DNS is being done by DNS proxy on Bordermanager 9.2. I've bypassed the
> Bordermanager DNS and the same thing happens. I've made entries for the
> local Rec server into a route.cfg file but the GWIA seems to want to
> ignore these entries and keeps doing the DNS lookup.
>
> The wierdest part of the puzzle is that if I restart the proxy on the
> Bordermanager the next email will go out with, of course, subsequent
> emails failing. I've looked at the proxy dns cache and can't even find
> an entry for my Rec server.
The reverse DNS done by GWIA is normal, and can't be stopped or tricked.
That it fails in such odd ways must be a bug with the reverse DNS proxy
of Bordermanager though. Apparently on the second lookups, it doesn't
answer in a timely manner (the type of answer is irrelevant, just it
*has* to answer). Use a different, "real" DNS server for your GWIA.
CU,
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
Untitled Document

Local session bean lookup in another local session bean in EJB 3.0

Hi,
I am doing JNDI lookup of a local session bean in a session bean. ( I do not want to use EJB dependency injection).
Lookup of local interface from session bean is successful. But, when the calling session bean is a local session in another session bean, the lookup fails.
Here is an example:
@Stateless
@EJBs({@EJB(name="EJB2Local", beanInterface=EJB2Local.class),
@EJB(name="EJB3Local", beanInterface=EJB3Local.class)})
public class EJB1 implements EJB1Remote, EJB1Local{
public void findEJB3Local(){
//1. JNDI lookup for EJB3Local ----
//2. EJB3Local.someFunction()
@Stateless
@EJB(name="EJB1Local", beanInterface=EJB1Local.class)
public class EJB2 implements EJB2Remote, EJB2Local{
public void findEJB1Local(){
//1. JNDI lookup EJB1Local
// 2. Call EJB1Local.findEJB1Local method
//THIS METHOD CALL WILL FAIL.
public void findEJB1Remote(){
//1. JNDI lookup EJB1
/ 2. Call EJB1Local.findEJB1 method
@Stateless
public class EJB3 implements EJB3Remote, EJB3Local{
public void someFunction(){}
This setup was working in EJB 2.1, as we had clear ejb-local-ref definitions in our ejb-jar.xml file.
I am suspecting that EJB 3.0 has special annotation to use when lookup is made from another local session bean.
Any comments will be appreciated.
Thanks,
Mohan

From a private component environment perspective, declaring @EJB in a bean class is equivalent
to using ejb-ref or ejb-local-ref for that same bean in ejb-jar.xml. In each case, the EJB dependency
is declared for that bean. Each EJB component has its own private component environment, so
code running within invocations on different EJBs can not see the component environment of the
components that made the invocations.
What exact error are you getting? Please post the stack trace if possible.
--ken

Could not access Local Session Bean using JNDI lookup

Hi EJB Guru,
I am quite new to EJB 3.0 but have had a good deal of success including using JNDI to lookup Remote Stateless Session Bean in EJB 3.0. However, looking up local Stateless Session Bean prove more challenging with I had anticipated.
Here is my code
as follows:
public interface Calculator {
    public int add(int x, int y);
    public int subtract(int x, int y);
import javax.ejb.Remote;
@Remote
public interface CalculatorRemote extends Calculator {
import javax.ejb.Local;
@Local
public interface CalculatorLocal extends Calculator {
import javax.ejb.Local;
import javax.ejb.Remote;
import javax.ejb.Stateless;
import bean.CalculatorLocal;
import bean.CalculatorRemote;
@Stateless
public class CalculatorBean implements CalculatorRemote, CalculatorLocal {
    public int add(int x, int y) {
        return x + y;
    public int subtract(int x, int y) {
        return x - y;
import bean.*;
import bean.Calculator;
import bean.CalculatorLocal;
import javax.naming.InitialContext;
import javax.naming.NamingException;
public class ClientAccessLocalCalculator {
    public static void main(String[] args) throws NamingException {
        InitialContext ctx = new InitialContext();
        CalculatorLocal calculator = (CalculatorLocal) ctx.lookup("CalculatorBean/local");
        System.out.println("1 + 1 = " + calculator.add(1, 1));
        System.out.println("1 - 1 = " + calculator.subtract(1, 1));    }
import bean.Calculator;
import bean.CalculatorRemote;
import javax.naming.InitialContext;
import javax.naming.NamingException;
public class ClientAccessRemoteCalculator {
    public static void main(String[] args) throws NamingException {
        InitialContext ctx = new InitialContext();
        CalculatorRemote calculator = (CalculatorRemote) ctx.lookup("CalculatorBean/remote");
        System.out.println("1 + 1 = " + calculator.add(1, 1));
        System.out.println("1 - 1 = " + calculator.subtract(1, 1));    }
}Output when running ClientAccessRemoteCalculator gives
1 + 1 = 2
1 - 1 = 0
Output when running ClientAccessLocalCalculator on JBoss AS 4.0.5 gives:
Exception in thread "main" javax.ejb.EJBException: Invalid invocation of local interface (null container)
at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:75)
at $Proxy0.add(Unknown Source) at ClientAccessLocalCalculator.main(ClientAccessLocalCalculator.java:14)
JNDIView in JMX-Console in JBoss:
+- CalculatorBean (class: org.jnp.interfaces.NamingContext)
| +- local (proxy: $Proxy84 implements interface bean.CalculatorLocal,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBLocalObject)
| +- remote (proxy: $Proxy83 implements interface bean.CalculatorRemote,interface org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject)
Output when running ClientAccessLocalCalculator on SJSAS 9.0 gives:
Exception in thread "main" javax.naming.NameNotFoundException: bean.CalculatorLocal not found
C:\>asadmin
Use "exit" to exit and "help" for online help.
asadmin> list-jndi-entries
Jndi Entries for server within root context:
bean.CalculatorRemote: javax.naming.Reference
jbi: com.sun.enterprise.naming.TransientContext
jdbc: com.sun.enterprise.naming.TransientContext
UserTransaction: com.sun.enterprise.distributedtx.UserTransactionImpl
bean.CalculatorRemote__3_x_Internal_RemoteBusinessHome__: javax.naming.Reference
bean.CalculatorRemote#bean.CalculatorRemote: javax.naming.Reference
ejb: com.sun.enterprise.naming.TransientContext
Command list-jndi-entries executed successfully.
asadmin>I am using Application Client to lookup these Session Beans on Netbeans 5.5, JBoss AS 4.0.5 (EJB3 installer)/SJSAS
9.0, SDK 1.5.0_11 on Windows XP platform.
Any assistance would be much appreciated.
Many thanks,
Henry

Hi Henry,
Any direct global JNDI lookup is not portable. It works in some cases but not in others, which
is why we recommend using the portable Java EE approach of declaring an ejb dependency
and looking up that dependency via the bean's component environment (java:comp/env).
This is true whether you're dealing with Remote or Local ejb dependencies.
Local ejbs are not supported in the Application Client tier at all. In the server tier, there is no
guarantee that a Local EJB even is assigned a global JNDI name since there's no requirement
that it be available outside of the application in which the ejb is defined.
You can find more information on these ejb access topics in our EJB FAQ :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html

NamingException on EJB jndi lookup

I have two applications - deployed under the "default instance".
When I start up OC4J and deloy app1 and app2, then app1 can do a JNDI lookup on a session bean that resides in App2. It uses the RMIInitialContextFactory.
Provider is "ormi://localhost/app2"
My problem is that if I undeploy and redeploy app2, then app1 suddenly can't do a lookup to any sessionBean found in app2 anymore, even though the jndi name still shows up in the browser, and if I try to look it up from an external application running outside of oc4j (with exactly the same code as I'm using in app1), it also works.
So why is app1 not able to find app2 via jndi after a redeployment?
D

Avi - thank you for your response.
First of all, I run on Suse Linux 10.1. Dunno if that's any help, but hey, more info can't help :)
Let's answer your questions:
1.) OCJ4 Version: 10.1.3.0.0 (build 060119.1546.05277)
2.) JDK Version: 1.5.0_07-b03
As for your suggestions:
1.) app1 = parent of app2.
I'm rather new to Oracle, so maybe I made a mistake during my investigations. Still, I'd like to give a breakdown: I built a framework-type application, and thought about deploying "child modules" (plug-in applications) underneath it, as you proposed.
This worked fine, but there comes a problem whenever you try to use something like Hibernate in any application that's not deployed in the root (ie any app that's deployed as a child of another). The problem came in 2 flavours:
A) If you use a jar in the parent and try to do resource loading from the child, the context of the parent is used the whole time. Since the search-policy of the class-loader is loaded->parent->shared->local, and if Hibernate is already used in the parent, it never gets to the child and thus trying to load a resource in the child is futile since parent can't see child context.
B) Lets say you're not using Hibernate at all in the parent application. When doing resource loading (eg the hibernate.cfg.xml file), Hibernate tries to locate the resource via Thread.currentThread().getContextClassLoader(). OC4J returns the parent-app's thread as the currentThread, NOT that of the child-application that you're actually running the code from, thus it will never be able to pick up resources from within a jar part of the child application. The only way that I managed to get it to work, was to include the Hibernate3.jar as part of the EAR deployment (ie listed it as <library path...> in the orion-application.xml. Putting it in shared-libs or app-libs didn't work...ever. Also, if I happened to use Hibernate in the parent-application, it doesn't matter if I put hibernate3.jar in the EAR of the child - the parent-version gets picked up and used due to the search-policy... NOTE: This is in a JAR - I'm not using WAR's so cannot force local loading as is possible with web-apps...
I then opted to deploy applications seperately under the root, and using RMI to communicate from the framework-application to its "modules", and vice-versa. The master doesn't know the exact type of the remote interface of whatever child-module it needs to call, so it uses reflection to call the "create" on the EJBHome of whatever child-module it needs to invoke as well as the method on the actual remote-interface.
Please note, if I deploy both applications (master and child), and perform JNDI lookups from master to child, it works perfectly. As soon as I do a redeploy (or explicity undeploy, deploy), JNDI fails. External clients, though, works all the time. Also, if I redeploy the child before ever calling it from the parent-application, it also works after I did redeployment. It's as if, when you do a JNDI lookup the first time, it caches something and from there on it breaks if you do a redeploy and perform a consequent app-to-app JNDI lookup...
2.) dedicated.rmicontext=true
I tried this by setting it as a JNDI property before getting the InitialContext - makes no difference, unfortunately.
//========CODE============================
// This is in a SessionBean inside the Master Application. For the time being I've hard-coded the provider-url of the client-application.
// NOTE: This EXACT same code is used in the external java client - there it works perfect every time, whether I redeploy or not.
//========================================
Hashtable<String, String> env = new Hashtable<String, String>();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.PROVIDER_URL, "ormi://localhost/client-application");
env.put(Context.SECURITY_PRINCIPAL, "oc4jadmin");
env.put(Context.SECURITY_CREDENTIALS, "MyPassword");
env.put("dedicated.rmicontext","true");
InitialContext ctx = null;
try {
     ctx = new InitialContext(env);
     // WHEN I REDEPLOY, CODE CRASHES ON THE NEXT LINE
     Object home = ctx.lookup("ejb/TestWorkerAProxyBean");
     EJBHome obHome = (EJBHome) PortableRemoteObject.narrow(home, EJBHome.class);
     System.out.println("EJBHOME Is [" + obHome + "]");
     final Object invocationTarget = MethodUtils.invokeExactMethod(obHome,"create",new Object[0]);
     System.out.println("invocation target = [" + invocationTarget + "]");
     ClassLoader classLoader = Thread.currentThread().getContextClassLoader();
     IWorkerProxy proxy = (IWorkerProxy)Proxy.newProxyInstance(classLoader, new Class[]{IWorkerProxy.class}, new InvocationHandler() {
          public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
               try {
                    Method remoteEjbMethod = invocationTarget.getClass().getMethod(method.getName(),method.getParameterTypes());
                    return remoteEjbMethod.invoke(invocationTarget, args);
               } catch (Exception e) {
                    ExceptionHandler.handle(e);
               return null;
} catch (NamingException ne) {
     System.out.println("NamingException");
     ne.printStackTrace();
} catch (NoSuchMethodException e) {
     System.out.println("NoSuchMethodException");
     e.printStackTrace();
} catch (Exception e) {
     System.out.println("Other Exception");
     e.printStackTrace();
==========================
===========EXCEPTION (ONLY IF I REDEPLOY - IT WORKS PERFECT IF I RUN IT FIRST TIME)=================
==========================
06/09/25 17:15:51 NamingException
06/09/25 17:15:51 javax.naming.NameNotFoundException: ejb/TestWorkerAProxyBean not found
06/09/25 17:15:51 at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:51)
06/09/25 17:15:51 at javax.naming.InitialContext.lookup(InitialContext.java:351)
06/09/25 17:15:51 at com.myapp.master.RequestProcessorBean.processRequest(RequestProcessorBean.java:140)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/09/25 17:15:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/09/25 17:15:51 at java.lang.reflect.Method.invoke(Method.java:585)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.TxSupportsInterceptor.invoke(TxSupportsInterceptor.java:37)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:86)
06/09/25 17:15:51 at RequestProcessorLocal_StatelessSessionBeanWrapper4.processRequest(RequestProcessorLocal_StatelessSessionBeanWrapper4.java:37)
06/09/25 17:15:51 at com.myapp.master.gateway.FrameworkGatewayBean.processObjectRequest(FrameworkGatewayBean.java:172)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/09/25 17:15:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/09/25 17:15:51 at java.lang.reflect.Method.invoke(Method.java:585)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.TxSupportsInterceptor.invoke(TxSupportsInterceptor.java:37)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
06/09/25 17:15:51 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:69)
06/09/25 17:15:51 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:86)
06/09/25 17:15:51 at FrameworkGatewayRemote_StatelessSessionBeanWrapper10.processObjectRequest(FrameworkGatewayRemote_StatelessSessionBeanWrapper10.java:94)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/09/25 17:15:51 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/09/25 17:15:51 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/09/25 17:15:51 at java.lang.reflect.Method.invoke(Method.java:585)
06/09/25 17:15:51 at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
06/09/25 17:15:51 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
06/09/25 17:15:51 at java.lang.Thread.run(Thread.java:595)

Challenge: call local ejb from remote ejb on weblogic 9.2

Hi ALL,
How do I call to local ejb from remote ejb object. The jar file is deployed on weblogic server 9.2, if you want get it http://geocities.yahoo.com.br/lindembe/BEAProject.jar and the source code are http://geocities.yahoo.com.br/lindembe/BEAProject.zip. It is a sample app with two ejb that works so good on JBOSS, JOnAS, but BEA Weblogic.....
The complete problem you watch http://forum.java.sun.com/thread.jspa?threadID=768718&messageID=4387570#4387570
or
http://forums.bea.com/bea/message.jspa?messageID=600043148&tstart=0

Your code in SigemFacadeBean should just do:
InitialContext ctx = new InitialContext();
when you lookup the local EJB. (This will work on all app servers. There's no need to put an app-server specific intial context factory in your code.)
Also, you can remove the jndi-name setting for the local ejb from your weblogic-ejb-jar.xml. jndi-name is only applied to remote ejbs.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Calling Local Stateless session bean from Spring in weblogic 10.3

We are in the process of upgrading to Weblogic 10.3 from OC4J (OAS). We are using Spring and Stateless Session EJB 3 Local beans (Don't ask me why, it is decided before I came to the project).
Previously (OC4J):
-> There is no ejb-jar.xml. EJBs are configured with annotation @Stateless. No "name" or "mappedName" are defined.
Spring POJOs access EJBs by using "EJBMODULENAME_<<EJBBeanClass>>Local" as JNDI Name. I think this strange JNDI name is what OC4J assigns when there is no explicit JNDI name defined.
Sample Spring Bean configuration -
<bean name="securityEJB" class="org.springframework.ejb.access.LocalStatelessSessionProxyFactoryBean" lazy-init="true">
          <property name="jndiName">
               <value>myapp-ejb_SecurityEJBImplLocal</value>
          </property>
          <property name="resourceRef">
               <value>false</value>
          </property>
          <property name="businessInterface">
               <value>my.package.SecurityEJB</value>
          </property>
     </bean>
I understand that weblogic 10.x doesn't give any global JNDI name (JNDI tree is empty) and also looked at the blog, Link: [http://m-button.blogspot.com/2008/07/reminder-on-how-to-use-ejb3-with.html]
So far I have tried,
1. @EJB annotation works but, I don't want to add @EJB annotations in the entire application. Since we are using Spring and EJB3, I am trying to avoid mixing them -
2. java:comp/env is supposed to work (since it is a local session bean), but it doesn't for me.
I haven't added weblogic-ejb-jar.xml as I don't think it is going to help, as there is no global JNDI name defined. Am I missing some thing?
Thx

Hi,
if you don't want to use @EJB to inject the EJB, then you'll need declare the EJB reference in deployment descriptor.
Here is an example copied from EJB3 spec:
<ejb-local-ref>
<description>
This is a reference to the local business interface
of an EJB 3.0 session bean that provides a payroll
service.
</description>
<ejb-ref-name>ejb/Payroll</ejb-ref-name>
<local>com.aardvark.payroll.Payroll</local>
</ejb-local-ref>
then you can lookup the local ejb from "java:comp/env/ejb/Payroll".

Reader X crashes when user profile redirected to 2nd local disk

This issue is related to, and possibly a duplicate of, the Reader X Folder Redirection issue. This is with Reader version 10.1.0 on Windows 7. Reader version 9 works fine, and if we run Reader X in XP compatibility mode it also works fine, but then we lose protected mode operation.
In our Windows 7 deployments, there are two local disks (C: and U:). For most users the profile is relocated from C: to U: and replaced by a junction point, for example "C:\Users\fred" is really a junction point to "U:\Users\fred". This is part of our user data backup/restore mechanism and a key part of how we manage Windows images for users. This works well for most applications but we have found that it causes Reader X to crash with a MSVC++ runtime error similar to what others have reported in different circumstances. Here is what we have observed so far.
1. Reader X will crash immediately when a user attempts to start it from the desktop or start menu. Procmon suggests that this crash is related to errors encountered when the application attempts to access the user's temp folder (C:\Users\fred\AppData\Local\Temp) which is really on the U: drive.
2. Resetting the TEMP and TMP environment variables to "C:\temp" allows the application to launch, but...
3. Once Reader X is launched, some features will cause it to crash in the same way. For example displaying preferences causes it to crash immediately (Edit/Preferences in the menu or using the Ctrl-K shortcut). Procmon suggests this is related to the application trying to access the "C:\Users\fred\AppData\Roaming" folder which is really on the U: drive.
4. Reader X never crashes and works just fine if the user's profile has not been relocated from the C: drive to the U: drive. But this only applies to a small fraction of users that we manage.
Any advice would be greatly appreciated. I can provide Procmon traces if that might be helpful.

We were experiencing the same issue.
We solved this by creating a GPO:
First open your GP mangement console, edit the GPO to which this applies. (This is a user GPO, so make sure you are on the user Ou!)
Edit:
User Configuration\Preferences\Drive Maps
Add a new drive mapping, mapped to \\server\share\%username% (in our case we mapped to P:\)
On the Common tab, make sure the "Run in user context" is ticked.
Next create a shortcut (or multiple shortcuts)
Edit:
User Configuration\Preferences\Shortcuts
Add a shortcut to
C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe (this is for Adobe Reader XI on Win x64; lookup your local path on the destination machines)
Change the start in to P:\ (the driveletter used in the drive mapping)
On the common tab also make sure this policy runs in the Logged-on user's security context.
This solved all issues at our end and we have this running with Adobe Reader X and XI
If you need to apply this to both Win x32 and x64 machines, you can apply item level targeting and choose the Operating system of choice. (If you add 2 OS'es, like Win 7 and Win 8, make sure that the option is OR and not AND).
good luck

Local Referance tag in Sun one server

Hi All,
In my ejb-jar.xml file have one ejb in that i have local Ejb. How i can spacify in the sun-ejb-jar.xml.when i trying to lookup the local ejb i got name not found exception .where as jboss we have one tag i.e. <local-jndi-name>
like wise we have any tag for refer the local ejb in sun-ejb-jar.xml.
plz help me .
Thank u.

<ejb-local-ref>
                    <ejb-ref-name>ParametrosObjHomeLocal</ejb-ref-name>
                    <ejb-ref-type>Session</ejb-ref-type>
                    <local-home>
                         com.deceval.siidj.siidserver.ParametrosObjLocalHome
                    </local-home>
                    <local>
                         com.deceval.siidj.siidserver.ParametrosObjLocal
                    </local>
                    <ejb-link>ParametrosObjHome</ejb-link>
               </ejb-local-ref>
ejb-jar.xml
after that lookup of this local ejb is
public ParametrosObjLocal getParametroLocalSO() {
          ParametrosObjLocal local = null;
          try {
               Context ctx = new InitialContext();
               Object o = ctx.lookup("java:comp/env/ParametrosObjHomeLocal");
               //ParametrosObjLocalHome o = (ParametrosObjLocalHome)ctx.lookup("java:comp/env/ParametrosObjHomeLocal");
               ParametrosObjLocalHome helloHome = (ParametrosObjLocalHome) PortableRemoteObject
               .narrow(o, ParametrosObjLocalHome.class);
               local = (ParametrosObjLocal) helloHome.create();
          } catch (NamingException e) {
               //mLog.error("NamingException: " + e.getMessage());
               e.printStackTrace();
               mLog.info("Changeing the Lookup ");
               throw new GenericException(e);
          } catch (CreateException e) {
               e.printStackTrace();
               mLog.error("FinderException: " + e.getMessage());
               throw new GenericException(e);
          return local;
we should lookup the java:comp/env/ejbname

Lookup of local ejbHome in WSAD

Similar Messages

Maybe you are looking for