I'd just like to add that I've used add-user to add an admin user and I can
now see the various admin screens for wf-26. They all show the JNDI and JMS
information as I would expect to see it. All the queues are there although
they are empty because I cannot connect. I wonder what port the server is
listening on for client connections.
I also tried changing the protocol from remote://hostname:portNumber to
remote+http://hostname:portNumber but it made no difference.
On Fri, 28 Jan 2022 at 14:05, Andrew Marlow <marlow.agents(a)gmail.com> wrote:
Hello everyone and thank you for your quick reply Eduardo.
cannot send the logs or the configuration; the work I am engaged in is
proprietary so I can share very little. But almost nothing has changed in
our code that has been using wildfly-23 for some time. We are running
wildfly standalone and I used standalone-full.xml as the template, just
adding stuff for our JDBC driver and our JMS queues.
When I trapped the exception I got a stack trace that revealed it was deep
in the wildfly code, starting at RemoteNamingProvider.java in the function
getPeerIdentityForNaming. Tracking back into the project code it is the
lookup function, which calls javx.naming.InitialContext.lookup.
I note from netstat that nothing seems to be listening on the port number
I am using. Shouldn't wildfly be listening to it? Of course if it isn't for
whatever reason then this might explain the client side error. But the
server.log from wildfly seems to be clean.
On Fri, 28 Jan 2022 at 13:43, Eduardo Martins <emartins(a)redhat.com> wrote:
> Hi Andrew, can you please share the logs?
> On 28 Jan 2022, at 11:56, Andrew Marlow <marlow.agents(a)gmail.com> wrote:
> Hello everyone,
> I am trying to move from 23 to 26 but am getting exception error
> WFNAM00018. My provider URL takes the form:
> remote://machineName:portNumber. Has this changed between 23 and 26? The
> port number is set via the property jboss.https.port. The line of code that
> blows up on is a call to context.lookup.
> Andrew Marlow
> wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
> To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org