[jboss-jira] [JBoss JIRA] (AS7-1338) Remote JNDI support for AS7

[Ed Keen (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665097#comment-12665097 ] 

Ed Keen commented on AS7-1338:
------------------------------

Jaikiran,

I get the error message after every time I send a basic TextMessage to the queue and my MDB picks up the message and processes it.  I am seeing this on Windows XP Professional, which is our local development environment.  It does not appear that the log messages are affecting functionality, because the message is picked up and processed.  However, if this happens in our live environment, we might have a problem with so many ERROR level log entries.

Here is my sample code:

{code}
Session session = null;
Connection conn = null;
MessageProducer producer = null;
		
try
{
  Properties props = new Properties();
  props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
  props.put(Context.PROVIDER_URL, "remote://localhost:4447");
  Context context = new InitialContext(props);	
			
  ConnectionFactory connFactory = (ConnectionFactory) context.lookup("jms/RemoteConnectionFactory");
  conn = connFactory.createConnection();
  session = conn.createSession(false, Session.AUTO_ACKNOWLEDGE);
			
  Queue queue = (Queue)context.lookup(queueName);
  producer = session.createProducer(queue);
  Message messageToSend = session.createTextMessage("hello world");
  producer.send(messageToSend);
			
}
catch (Exception e)
{
  e.printStackTrace();
}

{code}
                
> Remote JNDI support for AS7
> ---------------------------
>
>                 Key: AS7-1338
>                 URL: https://issues.jboss.org/browse/AS7-1338
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Naming
>            Reporter: Richard Opalka
>            Assignee: John Bailey
>            Priority: Critical
>              Labels: eap6_prd_req
>             Fix For: 7.1.0.Final
>
>
> Add support for remote JNDI after all.  It was agreed that:
> * Remote JNDI would run over Remoting
> * Remote JNDI for EJB is strictly a legacy access protocol, deprecated in favor of "ejb:"
> * The Remote JNDI service would proxy to a specific Context of the server JNDI tree - maybe "java:jboss/shared", maybe something else
> * Server-side services would opt-in to Remote JNDI; initially we'd only support:
> ** Remote EJB interfaces
> ** HornetQ connection factories
> * In the future we may support:
> ** User bindings, so long as they're serializable
> * In the future we will never support:
> ** Proxied DataSources
> ** Proxied JMS invocations
> Initial project tree is at https://github.com/dmlloyd/jboss-remote-jndi for now.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira