This discussion is archived
3 Replies Latest reply: Feb 21, 2013 4:46 AM by 675997 RSS

Cannot use outbound protocol "t3", it does not have administrator privilege

991800 Newbie
Currently Being Moderated
Hi,

I'm having problems with the servers are two different with "Nós", verify the connection to the port are correct and serves more the error persisted.
After restarting the error does not happen anymore.

The operation [connect({java.naming.provider.url=t3://url:port, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory, java.naming.security.principal=xxxxx, java.naming.security.credentials=xxxxx})] failed. Additional context information = [Invalid port. Check connection string].
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.security.Security.runAs(Security.java:41)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
... 23 more
Caused by: java.net.ConnectException: Cannot use outbound protocol "t3", it does not have administrator privileges
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:223)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:344)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.security.Security.runAs(Security.java:41)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:590)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:232)
... 3 more
Caused by: java.net.ConnectException: Cannot use outbound protocol "t3", it does not have administrator privileges
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:223)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:344)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:198)


Any sugestions ???
  • 1. Re: Cannot use outbound protocol "t3", it does not have administrator privilege
    991800 Newbie
    Currently Being Moderated
    Hi,

    Just some more information about the problem:

    We have two servers and each one has several nodes.

    When the error "Cannot use outbound protocol "t3", it does not have administrator privileges" starts to occur in one of server, all nodes starts give the same error.

    The online one solution is the workaround to restart all nodes (it is necessary also to restart the admin server).

    When the problem occurs we try to check the connection between the server with the destination server/port and the connection are ok.

    The problem occurs in an EJB that tries to connect with another server.

    Anyone could help me what could be the reason for the problem?

    We're using weblogic 10.3
  • 2. Re: Cannot use outbound protocol "t3", it does not have administrator privilege
    Kishore Rout Journeyer
    Currently Being Moderated
    Hi,
    The error which you are facing is coming while forwarding a message for distributed destination member now this issue can happen when something went wrong while forwarding a message for a distributed destination, however the system will retry message forwarding after a delay.

    There might be many cause of this issue like temporary network glitch or one of the members of the cluster may be unavailable etc, however its just a warring message so you can overlook it if its not happen frequently.

    mark if this helps.
    Thanks,
    Kishore
  • 3. Re: Cannot use outbound protocol "t3", it does not have administrator privilege
    675997 Newbie
    Currently Being Moderated
    KishoreRout, this answer I had already found in other forum for the same problem, but in that thread the problem was not solved.

    I cannot overlook it, since the only way to stop the problem is to restart the admin and node servers.

    I need more information about how could I identify the root cause of the problem and how can I handle that. Which information/config from weblogic which the application is deployed and the destination weblogic should I check when the problem occurs?

    Thanks

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points