jndi

问题 I have configured JNDI read & connect timeout properties through VM options as shown below: -Dcom.sun.jndi.ldap.connect.timeout=5000 -Dcom.sun.jndi.ldap.read.timeout=5000 But it is not working. JNDI read time out fails with below exception: javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms. But if I configured these properties in JNDI environment properties as shown below: env.put("com.sun.jndi.ldap.read.timeout", "5000"); env.put("com.sun.jndi.ldap.connect.timeout

问题 I have an activemq broker deployed within my jboss server. activemq is deployed as a rar file placed in jboss standalone/deployment repository. An other project is also deployed within my jboss as an ear file. This last is exposing some ejb objects in my jboss. I tried to get an ejb from a jar file that I put into my activemq rar file. A class placed within the jar is called when I connect a client to the broker. This is how I tried to get ejb within jar file: Context ctx; Properties

问题 I have searched a lot to get the answer for my question. But I can't . What I have got in search : public class RetrieveUserAttributes { public static void main(String[] args) { RetrieveUserAttributes retrieveUserAttributes = new RetrieveUserAttributes(); retrieveUserAttributes.getUserBasicAttributes("anand", retrieveUserAttributes.getLdapContext()); } public LdapContext getLdapContext(){ LdapContext ctx = null; try{ Hashtable<String, String> env = new Hashtable<String, String>(); env.put

问题 I have searched a lot to get the answer for my question. But I can't . What I have got in search : public class RetrieveUserAttributes { public static void main(String[] args) { RetrieveUserAttributes retrieveUserAttributes = new RetrieveUserAttributes(); retrieveUserAttributes.getUserBasicAttributes("anand", retrieveUserAttributes.getLdapContext()); } public LdapContext getLdapContext(){ LdapContext ctx = null; try{ Hashtable<String, String> env = new Hashtable<String, String>(); env.put

问题 I am trying to access an ejb that is exposed in jbossAS7.1 from code running in an embedded jetty server: final Properties jndiProperties = new Properties(); jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); jndiProperties.put(Context.PROVIDER_URL, "remote://127.0.0.1:4447"); jndiProperties.put("jboss.naming.client.ejb.context", true); jndiProperties.put("jboss.naming.client.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT",

问题 I have an EJB stateless running under a JBoss server and a client under another JBoss server. In the client side, I am using the following code: final Properties initialContextProperties = new Properties(); initialContextProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); initialContextProperties.put(Context.PROVIDER_URL, "remote://127.0.0.1:8083"); initialContextProperties.setProperty(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp

问题 I'm writing a REST API backend servlet with Jersey, and I have some problems using jndi to configure mail sending. Here's my WEB-INF/jetty-env.xml: <?xml version="1.0"?> <!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN" "http://www.eclipse.org/jetty/configure_9_0.dtd"> <Configure id='wac' class="org.eclipse.jetty.webapp.WebAppContext"> <New id="mail" class="org.eclipse.jetty.plus.jndi.Resource"> <Arg><Ref refid="wac"/></Arg> <Arg>mail/Session</Arg> <Arg> <New class="org

问题 JNDI is a mean to retrieve/store data or objects from string names. This feature is provided by the container running the application. ApplicationContext allows the creation and retrieval of beans from their string name. Both serve similar needs. Yet, Spring offers means to retrieve objects from JNDI. One can also access JNDI via the JndiTemplate . Is there a real need to use JNDI in Spring? Which problem does it solve that ApplicationContext does not? 回答1: The Application Context would not

问题 I have a problem identical to this question: JNDI lookup failing when looking up JMS queue in WebLogic 10.3.5 However, I can't figure out how to actually implement the solution. It seems simple enough to match the subdeployment and target to the same for both, but it isn't for me: If I change the connectionfactory's subs and target, I get the same error as i used to get on the queue, on the connectionfactory also Default targetting is not an option for queues, only connectionfactories. So how

问题 Warning: New to Java I have a simple Netbeans project - I wanted to just learn about interacting with DB's coming from php I thought I would have a go with a local one running on my computer. Lots of the examples out there say to use the InitialContext() object to refer to the database resource. After following the examples I get the following exception - Lots of Google stuff points to some .xml file - which I have no idea about or even where it exists in the Netbeans project? I'm not using a