com.bea.wli.sb.transports.TransportException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • JMS queue issue - behaving like a topic
    via by 974733,
    • com.bea.wli.sb.transports.TransportException: No service information is registered for: ProxyService default/Socket/SocketProxy at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:330) at com.bea.alsb.transports.sock.SocketTransportReceiver$WorkerThread$4.run(SocketTransportReceiver.java:452) at com.bea.alsb.transports.sock.SocketTransportReceiver$WorkerThread$4.run(SocketTransportReceiver.java:449) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.security.Security.runAs(Security.java:61) at com.bea.alsb.transports.sock.SocketTransportReceiver$WorkerThread.run(SocketTransportReceiver.java:449) at weblogic.work.WorkAreaContextWrap.run(WorkAreaContextWrap.java:55) at weblogic.work.ContextWrap.run(ContextWrap.java:40) at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:194) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:548) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311) at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
    No Bugmate found.