[Installation, Configuration & Deployment] - "could not make connection to the server"
by Mellman99
When I start jboss I get the following error:
16:24:56,436 ERROR [IpcConnection] Could not make connection to the server. <Host>isd-portal</Host><Port>5400</Port><Timeout>20000</Timeout>
| 16:24:56,445 ERROR [PoolManager] com.appiancorp.asl3.runtimefw.rta.ipc.TcpException: java.net.ConnectException: Connection refused
| com.appiancorp.asl3.runtimefw.rta.ipc.TcpException: java.net.ConnectException: Connection refused
| at com.appiancorp.asl3.runtimefw.rta.ipc.IpcConnection.o(IpcConnection.java:39)
| at com.appiancorp.asl3.runtimefw.rta.ipc.IpcConnection.<init>(IpcConnection.java:45)
| at com.appiancorp.asl3.runtimefw.rta.connect.pool.ServerUtils.isPrimary(ServerUtils.java:31)
| at com.appiancorp.asl3.runtimefw.rta.connect.pool.PoolManager.addServer(PoolManager.java:503)
| at com.appiancorp.asl3.runtimefw.rta.connect.pool.PoolManager$CheckInvalidConnections.run(PoolManager.java:74)
| at java.util.TimerThread.mainLoop(Timer.java:432)
| at java.util.TimerThread.run(Timer.java:382)
| Caused by: java.net.ConnectException: Connection refused
| at java.net.PlainSocketImpl.socketConnect(Native Method)
| at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
| at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
| at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
| at java.net.Socket.connect(Socket.java:452)
| at java.net.Socket.connect(Socket.java:402)
| at java.net.Socket.<init>(Socket.java:309)
| at java.net.Socket.<init>(Socket.java:124)
| at com.appiancorp.asl3.runtimefw.rta.ipc.IpcConnection.o(IpcConnection.java:33)
| ... 6 more
|
I am running JBoss version 3.2.5 and I am completely new to JBoss, just got handed the assignment to figure out what these errors are that started occuring ~4 months ago
It looks like it cannot connect to itself?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977683#3977683
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977683
19 years, 7 months
[Security & JAAS/JBoss] - Re: Bug in SecurityAssociation(?) - EJB3 MDB Calls a SLSB wh
by sappenin
Ok, so I found various threads (like this one: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=37807 and http://www.jboss.org/index.html?module=bb&op=viewtopic&t=35269).
>From what I can tell, the @RunAs annotation is merely specifying the "role" to use, whereas an MDB that calls a secured SLSB will not have a principal. The suggestions seem to be, "Just perform a JAAS login before accessing your SLSB, and you'll be ok".
However, something about this isn't sitting right with me.
1.) If the MDB RunAs annotation is merely providing a role, but no principal, shouldn't the "unauthenticated" identity get used, just with the @RunAs role? This isn't happening, since my unauthenticated identity is "guest" (in login-config.xml), the SecurityAssociation Stack (detailed above) is showing "anonymous" as the principal, and JBAS doesn't care about either....it is simply throwing an IllegalStateException whenever I try to access the principal inside of my SLSB (called from an MDB). (Error: java.lang.IllegalStateException: No valid security context for the caller identity).
2.) If I perform a programmatic JAAS login inside of my MDB, but just before calling my SLSB, everything works fine. However, shouldn't I be able to use the unauthenticated identiy coupled with the RunAs role in this scenario???
Any thoughts?
David
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977677#3977677
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977677
19 years, 7 months