kannan vimal

Ranch Hand
+ Follow
since Jun 06, 2010
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by kannan vimal

Hi Naidu and  all,
I have seen this thread is  started 3  years before. can  you  please suggest after sandbox tutorial, what else  you  did  for learning advanced level.
5 years ago
i  have experience in java,hibernate,spring     technology.willing to learn bigdata,hadoop. kindly suggest the  path to learn  hadoop and  good free online courses  and  material.

5 years ago
Hi

Did you get the answer for this ,please share, how we can start from eclipse using standalone-full.xml

5 years ago
Hi
I  tried  this   MDB  sample in jboss7.1Final with eclipse.

MessageBean project code as below

TestListner
============



WebMessageSender
==============


package notes.ejb.message;

import javax.annotation.Resource;
import javax.ejb.LocalBean;
import javax.ejb.Stateless;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.JMSException;
import javax.jms.MessageProducer;
import javax.jms.Queue;
import javax.jms.Session;
import javax.jms.TextMessage;


/**
* Session Bean implementation class WebMessageSender
*/
@Stateless
@LocalBean
public class WebMessageSender {

   /**
    * Default constructor.
    */
   public WebMessageSender() {
       // TODO Auto-generated constructor stub
   }
   
   //@Resource (lookup = "jms/webmessage")
   
   @Resource (lookup = "java:/ConnectionFactory")
   ConnectionFactory conn;
   
   //@Resource (lookup = "jms/websendqueue")
   @Resource (lookup = "jms/queue/test")
   Queue queue;
   
   
   public void sendWebMessage(String message){
    try {
    Connection connection = conn.createConnection();
    Session session = connection.createSession(true, 0);
   
    MessageProducer producer = session.createProducer(queue);
    TextMessage msg = session.createTextMessage(message);
    producer.send(msg);
    System.out.println("WebMessageSender EJB Sending message: " + message);
    } catch (JMSException e) {
    // do nothing for the sake of the  example
    System.out.println( e.getMessage());
    }
   }

}



when deploying this bean getting  this  below error..

21:40:39,044 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
21:40:39,295 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
21:40:39,353 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
21:40:40,256 INFO  [org.xnio] XNIO Version 3.0.3.GA
21:40:40,256 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
21:40:40,269 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
21:40:40,278 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
21:40:40,308 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
21:40:40,313 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
21:40:40,355 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
21:40:40,368 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.7.Final
21:40:40,383 INFO  [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
21:40:40,403 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
21:40:40,404 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
21:40:40,415 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
21:40:40,442 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
21:40:40,519 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
21:40:40,620 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
21:40:40,628 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-5) JBAS015400: Bound mail session [java:jboss/mail/Default]
21:40:40,684 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-7) JBoss Web Services - Stack CXF Server 4.0.2.GA
21:40:41,215 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
21:40:41,391 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) JBAS015012: Started FileSystemDeploymentService for directory C:\param\learning\softwares\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
21:40:41,418 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost/127.0.0.1:8999
21:40:41,418 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on localhost/127.0.0.1:4447
21:40:41,422 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment sendmessage.ear
21:40:41,434 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found sendmessage.ear in deployment directory. To trigger deployment create a file called sendmessage.ear.dodeploy
21:40:41,523 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
21:40:41,543 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:8990
21:40:41,545 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 2798ms - Started 135 of 211 services (74 services are passive or on-demand)
21:40:41,560 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "sendmessage.ear"
21:40:41,607 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "MessageBean.jar"
21:40:41,607 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "messageweb.war"
21:40:41,795 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named WebMessageSender in deployment unit subdeployment "MessageBean.jar" of deployment "sendmessage.ear" are as follows:

java:global/sendmessage/MessageBean/WebMessageSender!notes.ejb.message.WebMessageSender
java:app/MessageBean/WebMessageSender!notes.ejb.message.WebMessageSender
java:module/WebMessageSender!notes.ejb.message.WebMessageSender
java:global/sendmessage/MessageBean/WebMessageSender
java:app/MessageBean/WebMessageSender
java:module/WebMessageSender

21:40:41,804 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named SingleMessageReceiver in deployment unit subdeployment "MessageBean.jar" of deployment "sendmessage.ear" are as follows:

java:global/sendmessage/MessageBean/SingleMessageReceiver!notes.ejb.message.SingleMessageReceiver
java:app/MessageBean/SingleMessageReceiver!notes.ejb.message.SingleMessageReceiver
java:module/SingleMessageReceiver!notes.ejb.message.SingleMessageReceiver
java:global/sendmessage/MessageBean/SingleMessageReceiver
java:app/MessageBean/SingleMessageReceiver
java:module/SingleMessageReceiver

21:40:42,176 INFO  [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /messageweb
21:40:42,382 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "sendmessage.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.\"notes.ejb.message.WebMessageSender\".queuejboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.jms.queue.testMissing[jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.\"notes.ejb.message.WebMessageSender\".queuejboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.jms.queue.test]","jboss.deployment.subunit.\"sendmessage.ear\".\"MessageBean.jar\".component.TestListener.CREATEjboss.ra.hornetq-raMissing[jboss.deployment.subunit.\"sendmessage.ear\".\"MessageBean.jar\".component.TestListener.CREATEjboss.ra.hornetq-ra]","jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.\"notes.ejb.message.WebMessageSender\".connjboss.naming.context.java.ConnectionFactoryMissing[jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.\"notes.ejb.message.WebMessageSender\".connjboss.naming.context.java.ConnectionFactory]"]}
21:40:42,432 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment MessageBean.jar in 48ms
21:40:42,434 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment messageweb.war in 50ms
21:40:42,437 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment sendmessage.ear in 55ms
21:40:42,440 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014775:   New missing/unsatisfied dependencies:
     service jboss.naming.context.java.ConnectionFactory (missing) dependents: [service jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env."notes.ejb.message.WebMessageSender".conn]
     service jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.jms.queue.test (missing) dependents: [service jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env."notes.ejb.message.WebMessageSender".queue]
     service jboss.ra.hornetq-ra (missing) dependents: [service jboss.deployment.subunit."sendmessage.ear"."MessageBean.jar".component.TestListener.CREATE]

21:40:42,450
ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.\"notes.ejb.message.WebMessageSender\".queuejboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.jms.queue.testMissing[jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.\"notes.ejb.message.WebMessageSender\".queuejboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.jms.queue.test]","jboss.deployment.subunit.\"sendmessage.ear\".\"MessageBean.jar\".component.TestListener.CREATEjboss.ra.hornetq-raMissing[jboss.deployment.subunit.\"sendmessage.ear\".\"MessageBean.jar\".component.TestListener.CREATEjboss.ra.hornetq-ra]","jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.\"notes.ejb.message.WebMessageSender\".connjboss.naming.context.java.ConnectionFactoryMissing[jboss.naming.context.java.comp.sendmessage.MessageBean.WebMessageSender.env.\"notes.ejb.message.WebMessageSender\".connjboss.naming.context.java.ConnectionFactory]"]}}}






In jboss  domain.xml found  below entries. kindly let me know in  what is wrong in TestListener and  WebMessageSender


<jms-connection-factories>
                       <connection-factory name="InVmConnectionFactory">
                           <connectors>
                               <connector-ref connector-name="in-vm"/>
                           </connectors>
                          <entries>
                               <entry name="java:/ConnectionFactory"/>
                           </entries>
                       </
connection-factory>
                       <connection-factory name="RemoteConnectionFactory">
                           <connectors>
                               <connector-ref connector-name="netty"/>
                           </connectors>
                           <entries>
                               <entry name="RemoteConnectionFactory"/>
                               <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
                           </entries>
                       </connection-factory>
                       <pooled-connection-factory name="hornetq-ra">
                           <transaction mode="xa"/>
                           <connectors>
                               <connector-ref connector-name="in-vm"/>
                           </connectors>
                           <entries>
                               <entry name="java:/JmsXA"/>
                           </entries>
                       </pooled-connection-factory>
                   </jms-connection-factories>
                  <jms-destinations>
                       <jms-queue name="testQueue">
                           <entry name="queue/test"/>
                           <entry name="java:jboss/exported/jms/queue/test"/>
                       </jms-queue>
               
      <jms-topic name="testTopic">
                           <entry name="topic/test"/>
                           <entry name="java:jboss/exported/jms/topic/test"/>
                       </jms-topic>
                   </jms-destinations>
             
This  below  is   my  client    invocation


Errorlog



19:44:10,169 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
19:44:10,636 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
19:44:10,686 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
19:44:13,824 INFO  [org.xnio] XNIO Version 3.0.3.GA
19:44:13,826 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
19:44:13,835 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
19:44:13,843 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
19:44:13,888 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
19:44:13,908 INFO  [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.7.Final
19:44:13,991 INFO  [org.jboss.as.connector] (MSC service thread 1-5) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
19:44:14,783 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
19:44:14,940 INFO  [org.jboss.as.naming] (MSC service thread 1-5) JBAS011802: Starting Naming Service
19:44:14,955 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
19:44:14,998 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-8) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
19:44:16,684 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
19:44:16,933 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.2.GA
19:44:17,613 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost/127.0.0.1:4447
19:44:17,613 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:8999
19:44:17,618 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory C:\param\learning\softwares\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
19:44:17,631 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found EjbExample.jar in deployment directory. To trigger deployment create a file called EjbExample.jar.dodeploy
19:44:17,988 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "EjbExample.jar"
19:44:18,032 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry javax.ejb-3.1.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
19:44:18,033 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jboss-client.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
19:44:18,266 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ExampleBean in deployment unit deployment "EjbExample.jar" are as follows:

java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:module/ExampleBean!com.ejbs.ExampleBeanRemote
java:jboss/exported/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:module/ExampleBean!com.ejbs.ExampleBeanLocal

19:44:18,558 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015951: Admin console listening on http://127.0.0.1:8990
19:44:18,559 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 9236ms - Started 173 of 250 services (76 services are passive or on-demand)
19:44:18,629 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "EjbExample.jar"
19:44:38,333 INFO  [org.jboss.as.naming] (Remoting "par-pc" task-4) JBAS011806: Channel end notification received, closing channel Channel ID 603862b4 (inbound) of Remoting connection 75629b42 to /127.0.0.1:49445

Kindly help  me to resolve
Hi how you  resolve this issue. i am facing same issue.
My client code





and i am getting  below problem

22:32:43,379 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
22:32:43,649 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
22:32:43,704 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
22:32:44,692 INFO  [org.xnio] XNIO Version 3.0.3.GA
22:32:44,692 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
22:32:44,704 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
22:32:44,713 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
22:32:44,744 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
22:32:44,749 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
22:32:44,757 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
22:32:44,782 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
22:32:44,788 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
22:32:44,806 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
22:32:44,854 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
22:32:44,865 INFO  [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
22:32:44,889 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
22:32:44,941 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
22:32:45,067 INFO  [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service
22:32:45,079 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]
22:32:45,170 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
22:32:45,674 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
22:32:45,887 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory C:\param\learning\softwares\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
22:32:45,897 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found EjbExample.jar in deployment directory. To trigger deployment create a file called EjbExample.jar.dodeploy
22:32:45,906 INFO  [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on localhost/127.0.0.1:4447
22:32:45,907 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost/127.0.0.1:8999
22:32:46,086 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
22:32:46,146 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "EjbExample.jar"
22:32:46,194 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry javax.ejb-3.1.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
22:32:46,197 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jboss-client.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
22:32:46,394 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ExampleBean in deployment unit deployment "EjbExample.jar" are as follows:

java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:module/ExampleBean!com.ejbs.ExampleBeanRemote
java:jboss/exported/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:module/ExampleBean!com.ejbs.ExampleBeanLocal

22:32:46,606 INFO  [org.jboss.as] (MSC service thread 1-5) JBAS015951: Admin console listening on http://127.0.0.1:8990
22:32:46,608 INFO  [org.jboss.as] (MSC service thread 1-5) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 3537ms - Started 173 of 250 services (76 services are passive or on-demand)
22:32:46,662 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "EjbExample.jar"
22:33:38,190 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:38:32,706 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:40:20,593 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:43:32,978 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:50:01,433 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host



kindly help me,where is the  issue
5 years ago
Based  on the below url

https://stackoverflow.com/posts/30036591/edit


https://developer.jboss.org/thread/201728#sthash.o0m10eDj.dpuf


I changed the standalone.xml.

Now my entire trace as below
22:32:43,379 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
22:32:43,649 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
22:32:43,704 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
22:32:44,692 INFO  [org.xnio] XNIO Version 3.0.3.GA
22:32:44,692 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
22:32:44,704 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
22:32:44,713 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
22:32:44,744 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
22:32:44,749 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
22:32:44,757 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
22:32:44,782 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
22:32:44,788 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
22:32:44,806 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
22:32:44,854 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
22:32:44,865 INFO  [org.jboss.as.connector] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
22:32:44,889 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
22:32:44,941 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
22:32:45,067 INFO  [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service
22:32:45,079 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]
22:32:45,170 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
22:32:45,674 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
22:32:45,887 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) JBAS015012: Started FileSystemDeploymentService for directory C:\param\learning\softwares\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
22:32:45,897 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found EjbExample.jar in deployment directory. To trigger deployment create a file called EjbExample.jar.dodeploy
22:32:45,906 INFO  [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on localhost/127.0.0.1:4447
22:32:45,907 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost/127.0.0.1:8999
22:32:46,086 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
22:32:46,146 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "EjbExample.jar"
22:32:46,194 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry javax.ejb-3.1.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
22:32:46,197 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jboss-client.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
22:32:46,394 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-6) JNDI bindings for session bean named ExampleBean in deployment unit deployment "EjbExample.jar" are as follows:

java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:module/ExampleBean!com.ejbs.ExampleBeanRemote
java:jboss/exported/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:module/ExampleBean!com.ejbs.ExampleBeanLocal

22:32:46,606 INFO  [org.jboss.as] (MSC service thread 1-5) JBAS015951: Admin console listening on http://127.0.0.1:8990
22:32:46,608 INFO  [org.jboss.as] (MSC service thread 1-5) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 3537ms - Started 173 of 250 services (76 services are passive or on-demand)
22:32:46,662 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "EjbExample.jar"
22:33:38,190 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:38:32,706 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:40:20,593 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:43:32,978 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
22:50:01,433 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host


5 years ago
JSF

serverside deployment

19:21:22,417 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
19:21:24,141 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
19:21:24,217 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
19:21:30,104 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
19:21:30,106 INFO  [org.xnio] XNIO Version 3.0.3.GA
19:21:30,167 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
19:21:30,237 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
19:21:30,308 INFO  [org.jboss.as.security] JBAS013101: Activating Security Subsystem
19:21:30,317 INFO  [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.
19:21:30,328 INFO  [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem
19:21:30,329 INFO  [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem
19:21:30,330 INFO  [org.jboss.as.osgi] JBAS011940: Activating OSGi Subsystem
19:21:30,313 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
19:21:30,344 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
19:21:30,543 INFO  [org.jboss.as.connector] (MSC service thread 1-5) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
19:21:31,934 INFO  [org.jboss.as.naming] (MSC service thread 1-8) JBAS011802: Starting Naming Service
19:21:32,123 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
19:21:32,335 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
19:21:32,561 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
19:21:34,081 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
19:21:34,434 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-6) JBoss Web Services - Stack CXF Server 4.0.2.GA
19:21:35,859 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\param\learning\softwares\jboss-as-7.1.1.Final\jboss-as-7.1.1.Final\standalone\deployments
19:21:35,867 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found EjbExample.jar in deployment directory. To trigger deployment create a file called EjbExample.jar.dodeploy
19:21:35,909 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on localhost/127.0.0.1:4447
19:21:35,909 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost/127.0.0.1:9999
19:21:36,353 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "EjbExample.jar"
19:21:36,412 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry javax.ejb-3.1.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
19:21:36,413 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-5) Class Path entry jboss-client.jar in "/C:/param/learning/softwares/jboss-as-7.1.1.Final/jboss-as-7.1.1.Final/standalone/deployments/EjbExample.jar"  does not point to a valid jar for a Class-Path reference.
19:21:36,764 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named ExampleBean in deployment unit deployment "EjbExample.jar" are as follows:

java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:module/ExampleBean!com.ejbs.ExampleBeanRemote
java:jboss/exported/EjbExample/ExampleBean!com.ejbs.ExampleBeanRemote
java:global/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:app/EjbExample/ExampleBean!com.ejbs.ExampleBeanLocal
java:module/ExampleBean!com.ejbs.ExampleBeanLocal

19:21:37,188 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015951: Admin console listening on http://127.0.0.1:9990
19:21:37,189 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 16009ms - Started 173 of 250 services (76 services are passive or on-demand)
19:21:37,274 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "EjbExample.jar"

After running  the client application
19:29:17,236 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host
5 years ago
JSF
I am trying stateless session bean  sample in jboss7.1 with eclipse.

Client application code  as  below.

public static void main(String[] args) {
try {
Properties props = new Properties();
props.setProperty("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
props.setProperty("java.naming.factory.url.pkgs",
"org.jboss.naming:org.jnp.interfaces");
props.setProperty("java.naming.provider.url", "localhost:9999");

InitialContext ctx = new InitialContext(props);
System.out.println("Initial context created");
ExampleBeanRemote exampleBean = (ExampleBeanRemote) ctx.lookup("ExampleBean/remote");
System.out.println("Message from Bean :" + exampleBean.getMessage());
} catch (NamingException e) {
e.printStackTrace();
}

}


I  am getting  the  below error, as well  as   the port  no :9999.is correct  or not.Kindly help me  to  solve this below issue


18:37:59,950 ERROR [org.jboss.remoting.remote.connection] (Remoting "par-pc:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host

5 years ago
JSF
Hi

Kindly tell  me the author  for this book.

a) EJB 3 In Action 2nd Edition (which cover EJB 3.2 and JPA , i just used the EJB part not the full book)



5 years ago
Hi
can you  please share the  author name

a) EJB 3 In Action 2nd Edition .

and  links for the references  study  notes  please
5 years ago

I don't expect to be with Java for my entire career. Languages change. Technology changes. We are software developers.



Yes.  because of this,  i  like to move to switchover to bigdata technology. How long it requires to  learn  the technology.
5 years ago
Hi,
I am  having around  10 years  of experience  in  java/j2ee technology.
8 years i worked in same company  with internal framework.  (in that  3 years   worked as Team  lead).

Then moved to another company with technical manager  role for L3. (but not  only management/involved to look on code for analysis)
Now i want to move  as manager role  in new company what  they will expect from me.

I was worked  in hibernate/Spring core/spring jdbc.(Spring mvc/Aspect oriented   programming worked  on  samples, not in  realtime).                

But  in technical  interview point  i have  to  remember  all the syntax  of  everything  or how  i have  to prepare. can  you help me  out.
5 years ago

Jeanne Boyarsky wrote:Java isn't a career any more than Big Data is. You will work on many things in your career. And yes, Big Data can be a next step.



Hi, can you  please elaborate what  you mean   "you will work  on  many  things in your  career"
5 years ago