[JBoss JIRA] (AS7-1338) Remote JNDI support for AS7
by David Lloyd (Updated) (JIRA)
[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ]
David Lloyd updated AS7-1338:
-----------------------------
Fix Version/s: No Release
(was: 7.1.0.CR1)
Description:
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.
was:
<opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :(
<opalka> wolfc, dmlloyd in the config I see the following ports defined
<opalka> ---
<opalka> <socket-binding name="jndi" port="1099"/>
<opalka> <socket-binding name="jmx-connector-registry" port="1090"/>
<opalka> <socket-binding name="jmx-connector-server" port="1091"/>
<opalka> ---
<dmlloyd> we don't do JNDI over RMI anymore
<dmlloyd> that listing is an error
<opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to?
<opalka> dmlloyd, or we'll be doing JNDI over different binary protocol?
<dmlloyd> no, we will be able to, it'll just work somewhat differently
<opalka> dmlloyd, ok, I'm excluding the tests then ...
<opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment?
<dmlloyd> not that I'm aware of, it's just an outstanding task
<dmlloyd> remote invocation is not planned to be covered in next months' beta release
<opalka> dmlloyd, ok, thx for info ;)
Forum Reference: http://community.jboss.org/message/619784#619784 (was: http://community.jboss.org/message/619784#619784)
Was previously rejected:
<opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :(
<opalka> wolfc, dmlloyd in the config I see the following ports defined
<opalka> ---
<opalka> <socket-binding name="jndi" port="1099"/>
<opalka> <socket-binding name="jmx-connector-registry" port="1090"/>
<opalka> <socket-binding name="jmx-connector-server" port="1091"/>
<opalka> ---
<dmlloyd> we don't do JNDI over RMI anymore
<dmlloyd> that listing is an error
<opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to?
<opalka> dmlloyd, or we'll be doing JNDI over different binary protocol?
<dmlloyd> no, we will be able to, it'll just work somewhat differently
<opalka> dmlloyd, ok, I'm excluding the tests then ...
<opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment?
<dmlloyd> not that I'm aware of, it's just an outstanding task
<dmlloyd> remote invocation is not planned to be covered in next months' beta release
<opalka> dmlloyd, ok, thx for info ;)
But now it's back :)
> 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: Blocker
> Fix For: No Release
>
>
> 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
13 years
[JBoss JIRA] (AS7-1338) Remote JNDI support for AS7
by Jason Greene (Commented) (JIRA)
[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ]
Jason Greene commented on AS7-1338:
-----------------------------------
We have decided to implement a pure jndi forwarding remote jndi solution for everyone that is used to the old behavior.
> 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: Blocker
> Fix For: 7.1.0.CR1
>
>
> <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :(
> <opalka> wolfc, dmlloyd in the config I see the following ports defined
> <opalka> ---
> <opalka> <socket-binding name="jndi" port="1099"/>
> <opalka> <socket-binding name="jmx-connector-registry" port="1090"/>
> <opalka> <socket-binding name="jmx-connector-server" port="1091"/>
> <opalka> ---
> <dmlloyd> we don't do JNDI over RMI anymore
> <dmlloyd> that listing is an error
> <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to?
> <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol?
> <dmlloyd> no, we will be able to, it'll just work somewhat differently
> <opalka> dmlloyd, ok, I'm excluding the tests then ...
> <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment?
> <dmlloyd> not that I'm aware of, it's just an outstanding task
> <dmlloyd> remote invocation is not planned to be covered in next months' beta release
> <opalka> dmlloyd, ok, thx for info ;)
--
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
13 years
[JBoss JIRA] (AS7-1338) Remote JNDI support for AS7
by Jason Greene (Updated) (JIRA)
[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ]
Jason Greene updated AS7-1338:
------------------------------
Fix Version/s: 7.1.0.CR1
(was: No Release)
Forum Reference: http://community.jboss.org/message/619784#619784 (was: http://community.jboss.org/message/619784#619784)
> 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: Blocker
> Fix For: 7.1.0.CR1
>
>
> <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :(
> <opalka> wolfc, dmlloyd in the config I see the following ports defined
> <opalka> ---
> <opalka> <socket-binding name="jndi" port="1099"/>
> <opalka> <socket-binding name="jmx-connector-registry" port="1090"/>
> <opalka> <socket-binding name="jmx-connector-server" port="1091"/>
> <opalka> ---
> <dmlloyd> we don't do JNDI over RMI anymore
> <dmlloyd> that listing is an error
> <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to?
> <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol?
> <dmlloyd> no, we will be able to, it'll just work somewhat differently
> <opalka> dmlloyd, ok, I'm excluding the tests then ...
> <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment?
> <dmlloyd> not that I'm aware of, it's just an outstanding task
> <dmlloyd> remote invocation is not planned to be covered in next months' beta release
> <opalka> dmlloyd, ok, thx for info ;)
--
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
13 years
[JBoss JIRA] (AS7-1338) Remote JNDI support for AS7
by Jason Greene (Assigned) (JIRA)
[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ]
Jason Greene reassigned AS7-1338:
---------------------------------
Assignee: John Bailey (was: David Lloyd)
> 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: Blocker
> Fix For: 7.1.0.CR1
>
>
> <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :(
> <opalka> wolfc, dmlloyd in the config I see the following ports defined
> <opalka> ---
> <opalka> <socket-binding name="jndi" port="1099"/>
> <opalka> <socket-binding name="jmx-connector-registry" port="1090"/>
> <opalka> <socket-binding name="jmx-connector-server" port="1091"/>
> <opalka> ---
> <dmlloyd> we don't do JNDI over RMI anymore
> <dmlloyd> that listing is an error
> <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to?
> <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol?
> <dmlloyd> no, we will be able to, it'll just work somewhat differently
> <opalka> dmlloyd, ok, I'm excluding the tests then ...
> <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment?
> <dmlloyd> not that I'm aware of, it's just an outstanding task
> <dmlloyd> remote invocation is not planned to be covered in next months' beta release
> <opalka> dmlloyd, ok, thx for info ;)
--
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
13 years
[JBoss JIRA] (AS7-1338) Remote JNDI support for AS7
by Jason Greene (Reopened) (JIRA)
[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ]
Jason Greene reopened AS7-1338:
-------------------------------
It's back!
> 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: David Lloyd
> Priority: Blocker
> Fix For: No Release
>
>
> <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :(
> <opalka> wolfc, dmlloyd in the config I see the following ports defined
> <opalka> ---
> <opalka> <socket-binding name="jndi" port="1099"/>
> <opalka> <socket-binding name="jmx-connector-registry" port="1090"/>
> <opalka> <socket-binding name="jmx-connector-server" port="1091"/>
> <opalka> ---
> <dmlloyd> we don't do JNDI over RMI anymore
> <dmlloyd> that listing is an error
> <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to?
> <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol?
> <dmlloyd> no, we will be able to, it'll just work somewhat differently
> <opalka> dmlloyd, ok, I'm excluding the tests then ...
> <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment?
> <dmlloyd> not that I'm aware of, it's just an outstanding task
> <dmlloyd> remote invocation is not planned to be covered in next months' beta release
> <opalka> dmlloyd, ok, thx for info ;)
--
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
13 years
[JBoss JIRA] (AS7-2882) CLONE - New Management Jars do not work on previous app-server versions
by Paul Gier (Created) (JIRA)
CLONE - New Management Jars do not work on previous app-server versions
-----------------------------------------------------------------------
Key: AS7-2882
URL: https://issues.jboss.org/browse/AS7-2882
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Affects Versions: 7.1.0.Beta1
Reporter: Paul Gier
Assignee: Jason Greene
Fix For: 7.1.0.Beta1
I'm not sure if this is in the correct component, however, using the new management jars in JBoss 7.1 beta1, and trying to access the management functions of as7.0.x, the result is not successful. These jars need to be tested for regressions with previous versions.
My first test against what seems to be 7.0.0.final (built 5 days before the release, so I suspect it was a near-final build) involved the following error in the CLIENT:
Caused by: javax.security.sasl.SaslException: No more authentication mechanisms to try
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:301)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:200)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:179)
at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:100)
at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:98)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
at org.xnio.nio.NioHandle.run(NioHandle.java:90)
at org.xnio.nio.WorkerThread.run(WorkerThread.java:184)
at ...asynchronous invocation...(Unknown Source)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:263)
at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:246)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:353)
at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337)
at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:133)
... 5 more
A try against 7.0.2 has different results: when the server started up, the test client simply freezes, with the following stack trace:
Object.wait(long) line: not available [native method]
ManagementRequest$ManagementFuture<T>(Object).wait() line: 485
ManagementRequest$ManagementFuture<T>(AsyncFutureTask<T>).await() line: 192
ManagementRequest$ManagementFuture<T>(AsyncFutureTask<T>).get() line: 266
AbstractModelControllerClient$ExecuteRequest(ManagementRequest<T>).executeForResult(ExecutorService, ManagementClientChannelStrategy) line: 131
RemotingModelControllerClient(AbstractModelControllerClient).executeSynch(ModelNode, OperationAttachments, OperationMessageHandler) line: 128
RemotingModelControllerClient(AbstractModelControllerClient).execute(ModelNode, OperationMessageHandler) line: 93
RemotingModelControllerClient(AbstractModelControllerClient).execute(ModelNode) line: 83
TestClient.performOneCheck(ModelControllerClient) line: 201
No result is ever found.
The exception on the server when performing this test client is as follows:
17:55:57,187 ERROR [org.xnio.listener] (XNIO NIO Read 1) A channel event listener threw an exception: java.lang.IllegalStateException: Unsupported Callback 'ANONYMOUSanonymous'
at org.jboss.as.remoting.RealmAuthenticationProvider.getCallbackHandler(RealmAuthenticationProvider.java:132)
at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:235)
at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:107)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:71)
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:173)
at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:94)
at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:92)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:71)
at org.xnio.nio.NioHandle.invoke(NioHandle.java:77)
at org.xnio.nio.AbstractNioChannelThread$1.run(AbstractNioChannelThread.java:142)
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
The test client's logic will be attached momentarily
--
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
13 years