Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Dalavai Ravindranath Bharath (BHARATHD)
Hcl

Hcl
AU
BHARATHD Member since 2011 2 posts
Hcl
Posted: Feb 21, 2017
Last activity: Feb 23, 2017
Posted: 21 Feb 2017 21:16 EST
Last activity: 23 Feb 2017 17:56 EST
Closed

JBOSS - JMS connection failed

Hi I am using LINUX REDHAT EAP6 JBOSS app serer and Deployed .ear file.

Now while creating JNDI server in Pega, getting the below error. Can you please let me know if any one faced the same issue

javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.NoSuchMethodError: org.jboss.remoting3.Remoting.createEndpoint(Ljava/lang/String;Lorg/xnio/OptionMap;)Lorg/jboss/remoting3/Endpoint;]

Do we need to deploy any external Jar files for JMS connection?

***Updated by moderator: Lochan to update Categories***

To see attachments, please log in.
Data Integration

Posted: 7 years ago
Posted: 22 Feb 2017 1:23 EST
Penchalanarasimhulu Vendipalli (Narasimha522)
PEGA
Senior Technical Solutions Engineer
Pegasystems Inc.
IN

Hi,

I think you haven't added JBoss Client jar tou your project. Go to JBOSS_FOLDER/bin/client and add the jar jboss-client.jar to your classpath. Check if it works! If not, please share complete stack trace.

 

To see attachments, please log in.
Posted: 7 years ago
Posted: 23 Feb 2017 17:56 EST
Dalavai Ravindranath Bharath (BHARATHD)
Hcl

Hcl
AU

Hi Vendp,

I tried adding the jboss-client.jar file in the APP-INF/LIB in .ear file and added the Manifest.MF file for the same. But still I am getting the same error.

Do you have any document that details the configuration steps to create the Service-JMS in Jboss.

Thanks In Advance

 

 

 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice