My Oracle Support Banner

When Testing the Connections for Eventing from P6 the Error "Can Not Connect to Server" Occurs (Doc ID 2329851.1)

Last updated on AUGUST 09, 2018

Applies to:

Primavera Web Services - Version 17.7 and later
Information in this document applies to any platform.

Symptoms

When attempting to run the Test Connection for Event Notification in P6, the following errors occur.

ERROR
-----------------------
P6 Web:
Can not connect to server.

P6WebAccess.html:
ERROR com.primavera.infr.events.publishers.SpringJMSEventPublisher ?:? ?Directory Services is incorrectly configured. Retrying in a minute...
javax.naming.NameNotFoundException: Unable to resolve 'jms.JMSQueue'. Resolved 'jms'; remaining name 'JMSQueue'
  at weblogic.utils.StackTraceDisabled.unknownMethod()

ERROR com.primavera.infr.events.publishers.SpringJMSEventPublisher ?:? ?Directory Services is incorrectly configured. Retrying in a minute...
javax.naming.CommunicationException: Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
  no protocol: localhost:7001 [Root exception is java.net.MalformedURLException: no protocol: localhost:7001]
  at weblogic.jndi.WLInitialContextFactoryDelegate.throwRetryException(WLInitialContextFactoryDelegate.java:467)
  at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:403)
  at weblogic.jndi.Environment.getContext(Environment.java:353)
  at weblogic.jndi.Environment.getContext(Environment.java:322)
  at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:131)
  at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
  at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
  at javax.naming.InitialContext.init(InitialContext.java:244)
  at javax.naming.InitialContext.(InitialContext.java:216)
  at org.springframework.jndi.JndiTemplate.createInitialContext(JndiTemplate.java:136)
  at org.springframework.jndi.JndiTemplate.getContext(JndiTemplate.java:103)
  at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:85)
  at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:152)
  at com.primavera.infr.events.publishers.SpringJMSEventPublisher.b(Unknown Source)
  at com.primavera.infr.events.publishers.SpringJMSEventPublisher.a(Unknown Source)
  at com.primavera.infr.events.publishers.SpringJMSEventPublisher$ConnectionChecker$1.run(Unknown Source)
  at java.util.TimerThread.mainLoop(Timer.java:555)
  at java.util.TimerThread.run(Timer.java:505)
  Caused by: java.net.MalformedURLException: no protocol: localhost:7001
  at weblogic.protocol.ServerURL.parseURL(ServerURL.java:416)
  at weblogic.protocol.ServerURL.(ServerURL.java:149)
  at weblogic.rjvm.ClientServerURL.(ClientServerURL.java:49)
  at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:347)
  ... 16 more

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create the JMS Connection Factory and JMS Queue in Weblogic
2. In P6 Web under the Administration tab configure the Event Notification settings.
3. Enter the JNDI name for the Connection Factory and the Queue
4. Run the Test Connection for either the Directory Services or for Eventing.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.