[JBoss Tools] - Start JBoss after running with exceptions
by lancerx
lancerx [https://community.jboss.org/people/lancerx] created the discussion
"Start JBoss after running with exceptions"
To view the discussion, visit: https://community.jboss.org/message/727507#727507
--------------------------------------------------------------
I use Eclipse 3.7, JBoss AS 7 and JBoss Tools plugin.
I can not run second time JBoss after terminating first running of JBoss where one of my EAR (JSF project) has mistakes.
This is console when everything is ok
WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
18:34:10,763 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
18:34:12,605 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
18:34:12,730 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final "Thunder" starting
18:34:17,832 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
18:34:17,879 INFO [org.xnio] XNIO Version 3.0.3.GA
18:34:17,911 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
18:34:17,957 INFO [org.jboss.remoting] JBoss Remoting version 3.2.2.GA
18:34:18,035 INFO [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem
18:34:18,035 INFO [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.
18:34:18,051 INFO [org.jboss.as.osgi] JBAS011940: Activating OSGi Subsystem
18:34:18,051 INFO [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem
18:34:18,067 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
18:34:18,363 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
18:34:18,394 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.6.final
18:34:18,519 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)
18:34:18,597 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
18:34:19,112 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
18:34:19,456 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0)
18:34:20,002 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
18:34:21,172 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/Tour]
18:34:21,172 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
18:34:21,781 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.1.GA
18:34:22,359 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss\standalone\deployments
18:34:22,406 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TourEAR.ear in deployment directory. To trigger deployment create a file called TourEAR.ear.dodeploy
18:34:22,422 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TourWebSpring.war in deployment directory. To trigger deployment create a file called TourWebSpring.war.dodeploy
18:34:22,453 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999
18:34:22,453 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447
18:34:22,968 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "TourEAR.ear"
18:34:22,968 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "TourWebSpring.war"
18:34:24,591 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /TourWebSpring
18:34:25,060 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "TourJSF.war"
18:34:25,060 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "TourEJB.jar"
18:34:25,513 INFO [org.jboss.as.jpa] (MSC service thread 1-4) JBAS011401: Read persistence.xml for jee_project
18:34:25,544 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'
18:34:25,544 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'
18:34:26,468 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named HotelBoImpl in deployment unit subdeployment "TourEJB.jar" of deployment "TourEAR.ear" are as follows:
java:global/TourEAR/TourEJB/HotelBoImpl!tour.jee.bc.bo.HotelBo
java:app/TourEJB/HotelBoImpl!tour.jee.bc.bo.HotelBo
java:module/HotelBoImpl!tour.jee.bc.bo.HotelBo
java:global/TourEAR/TourEJB/HotelBoImpl
java:app/TourEJB/HotelBoImpl
java:module/HotelBoImpl
18:34:26,484 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named ClientBoImpl in deployment unit subdeployment "TourEJB.jar" of deployment "TourEAR.ear" are as follows:
java:global/TourEAR/TourEJB/ClientBoImpl!tour.jee.bc.bo.ClientBo
java:app/TourEJB/ClientBoImpl!tour.jee.bc.bo.ClientBo
java:module/ClientBoImpl!tour.jee.bc.bo.ClientBo
java:global/TourEAR/TourEJB/ClientBoImpl
java:app/TourEJB/ClientBoImpl
java:module/ClientBoImpl
..................
18:34:26,702 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0)
18:34:27,249 INFO [org.jboss.as.jpa] (MSC service thread 1-4) JBAS011402: Starting Persistence Unit Service 'TourEAR.ear/TourEJB.jar#jee_project'
18:34:27,608 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-4) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
18:34:27,608 INFO [org.hibernate.Version] (MSC service thread 1-4) HHH000412: Hibernate Core {4.0.1.Final}
18:34:27,608 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-4) HHH000206: hibernate.properties not found
18:34:27,639 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-4) HHH000021: Bytecode provider name : javassist
18:34:27,655 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
18:34:27,655 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-3) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
18:34:27,702 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-3) Initializing Mojarra 2.1.5 (SNAPSHOT 20111202) for context '/TourJSF'
18:34:27,702 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-4) HHH000204: Processing PersistenceUnitInfo [
name: jee_project
...]
18:34:28,232 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-4) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
18:34:29,606 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-3) Hibernate Validator 4.2.0.Final
18:34:29,732 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-4) HHH000400: Using dialect: org.hibernate.dialect.PostgreSQLDialect
18:34:29,747 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-4) HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException
18:34:29,763 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-4) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
18:34:29,778 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-4) HHH000397: Using ASTQueryTranslatorFactory
18:34:30,371 INFO [org.jboss.web] (MSC service thread 1-3) JBAS018210: Registering web context: /TourJSF
18:34:30,621 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-4) HHH000228: Running hbm2ddl schema update
18:34:30,621 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-4) HHH000102: Fetching database metadata
18:34:30,653 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-4) HHH000396: Updating schema
18:34:31,027 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] (MSC service thread 1-4) HHH000261: Table found: public.client
18:34:31,027 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] (MSC service thread 1-4) HHH000037: Columns: [id, name, surname, userrole, login, password]
18:34:31,183 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] (MSC service thread 1-4) HHH000108: Foreign keys: [fk63eebaccf024201, fk63eebac59f73361]
18:34:31,183 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] (MSC service thread 1-4) HHH000126: Indexes: [reservation_pkey]
18:34:31,215 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] (MSC service thread 1-4) HHH000261: Table found: public.tour
18:34:31,215 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] (MSC service thread 1-4) HHH000037: Columns: [id, base_price, date_from, hotel_id, description, date_to, placequantity]
.......................
18:34:31,230 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] (MSC service thread 1-4) HHH000108: Foreign keys: [fk27de782fa87ed3]
18:34:31,230 INFO [org.hibernate.tool.hbm2ddl.TableMetadata] (MSC service thread 1-4) HHH000126: Indexes: [tour_pkey]
18:34:31,230 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-4) HHH000232: Schema update complete
18:34:31,371 INFO [org.jboss.as] (MSC service thread 1-3) JBAS015874: JBoss AS 7.1.0.Final "Thunder" started in 21950ms - Started 830 of 910 services (78 services are passive or on-demand)
18:34:31,464 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "TourWebSpring.war"
18:34:31,464 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "TourEAR.ear"
When in my application are some errors:
18:40:18,081 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.web.deployment.default-host./TourJSF: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./TourJSF: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21]
18:40:18,081 ERROR [org.jboss.as] (MSC service thread 1-2) JBAS015875: JBoss AS 7.1.0.Final "Thunder" started (with errors) in 18046ms - Started 828 of 910 services (2 services failed or missing dependencies, 78 services are passive or on-demand)
18:40:18,299 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "TourWebSpring.war" was rolled back with no failure message
18:40:18,315 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "TourEAR.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./TourJSF" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./TourJSF: JBAS018040: Failed to start context"}}
18:40:18,346 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011403: Stopping Persistence Unit Service 'TourEAR.ear/TourEJB.jar#jee_project'
18:40:18,424 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment TourWebSpring.war in 126ms
18:40:18,440 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment TourEJB.jar in 128ms
18:40:18,455 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment TourJSF.war in 132ms
18:40:18,518 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment TourEAR.ear in 201ms
18:40:18,518 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.web.deployment.default-host./TourJSF: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./TourJSF: JBAS018040: Failed to start context
18:40:18,549 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./TourJSF" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./TourJSF: JBAS018040: Failed to start context"}}}}
18:40:18,549 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
I choose terminate icon, improve my application and again choose "Run on server". JBoss seems to start...:
WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
18:44:14,797 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
18:44:14,999 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
18:44:15,052 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final "Thunder" starting
18:44:16,039 INFO [org.xnio] XNIO Version 3.0.3.GA
18:44:16,039 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
18:44:16,049 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
18:44:16,057 INFO [org.jboss.remoting] JBoss Remoting version 3.2.2.GA
18:44:16,075 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
18:44:16,080 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
18:44:16,160 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
18:44:16,165 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
18:44:16,237 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
18:44:16,262 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
18:44:16,322 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
18:44:16,332 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
18:44:16,335 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.6.final
18:44:16,387 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
18:44:16,395 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.0)
18:44:16,532 INFO [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)
18:44:16,552 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]
18:44:16,845 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.1.GA
18:44:17,052 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory C:\jboss\standalone\deployments
18:44:17,065 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TourEAR.ear in deployment directory. To trigger deployment create a file called TourEAR.ear.dodeploy
18:44:17,067 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found TourWebSpring.war in deployment directory. To trigger deployment create a file called TourWebSpring.war.dodeploy
18:44:17,201 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447
18:44:17,266 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
18:44:17,268 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999
18:44:17,431 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
18:44:17,433 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/Tour]
18:44:17,528 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.0.Final "Thunder" started in 3016ms - Started 138 of 210 services (70 services are passive or on-demand)
but no application can run.
Only Windows restart can help.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/727507#727507]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years
[JBoss Messaging] - JMS Client program is not able to receive messages from the queue
by chithu21
chithu21 [https://community.jboss.org/people/chithu21] created the discussion
"JMS Client program is not able to receive messages from the queue"
To view the discussion, visit: https://community.jboss.org/message/727422#727422
--------------------------------------------------------------
I have a jms client program and an MDB. The client program is not able to receive message from the queue. But I am able to see the messages in the MDB's system.out log.
Can anyone help me please? Thanks in advance.
Client Program:
----------------------
public class MessageReceiver {
static final int N = 1;
static CountDown done = new CountDown(N);
ReadValues readValues = new ReadValues();
Config config = readValues.readPropertiesFile();
public static class ExListener implements MessageListener {
public void onMessage(Message msg) {
System.out.println("Inside OnMessage");
done.release();
TextMessage tm = (TextMessage) msg;
try {
String receivedMsg = tm.getText();
System.out.println("onMessage, recv text=" + receivedMsg);
// System.out.println("Added Some text with " + receivedMsg);
} catch (Throwable t) {
t.printStackTrace();
}
}
}
public void receiveMessage() throws JMSException, NamingException,
InterruptedException, ClassNotFoundException, SQLException {
System.out.println("Begin receiveMessage method");
JMSConnector jmsConnector = new JMSConnector();
QueueObject queueObj = jmsConnector.setupPTP(config.getProviderUrl(),
"XibToCatQueue");
QueueSession session = queueObj.getQueueSession();
Queue xibToCatQueue = queueObj.getQueue();
System.out.println("Queue Name : " + xibToCatQueue.getQueueName());
// Set the async listener for xibToCatQueue
QueueReceiver recv = session.createReceiver(xibToCatQueue);
// System.out.println("........." + recv.getQueue());
recv.setMessageListener(new ExListener());
Queue catToXibQueue = queueObj.getCatToXibQueue();
QueueSender send = session.createSender(catToXibQueue);
String text = "Test Message...";
TextMessage tm = session.createTextMessage(text);
tm.setJMSReplyTo(xibToCatQueue);
send.send(tm);
System.out.println("Sent text=" + tm.getText());
send.close();
MessageReceiver.done.acquire();
jmsConnector.closePTP();
System.out.println("End receiveMessage method");
System.exit(0);
}
public static void main(String[] args) throws JMSException,
NamingException, InterruptedException, ClassNotFoundException,
SQLException {
MessageReceiver msgReceiver = new MessageReceiver();
msgReceiver.receiveMessage();
}
}
Connector Program:
---------------------------------
public QueueObject setupPTP(String contextUrl,String queueName) throws JMSException, NamingException {
ReadValues readValues = new ReadValues();
Config config = readValues.readPropertiesFile();
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,config.getContextFactory());
env.put(Context.PROVIDER_URL, contextUrl);
env.put(Context.URL_PKG_PREFIXES,config.getPkgPrefixes());
InitialContext iniCtx = new InitialContext(env);
Object tmp = iniCtx.lookup("ConnectionFactory");
QueueConnectionFactory qcf = (QueueConnectionFactory) tmp;
connection = qcf.createQueueConnection();
String lookUpObj = "queue/" + queueName;
Queue xibToCatQueue = (Queue) iniCtx.lookup(lookUpObj);
Queue catToXIbQueue = (Queue) iniCtx.lookup("queue/CatToXibQueue");
session = connection.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
connection.start();
return new QueueObject(session,xibToCatQueue,catToXIbQueue);
}
public void closePTP() throws JMSException {
System.out.println("Inside closePTP.....");
connection.stop();
if(session != null) {
session.close();
}
if(connection != null) {
connection.close();
}
}
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/727422#727422]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years
[JBoss Web Services] - JBOSS WS | OutOfMemory GC overhead limit exceeded
by Keshav Savant
Keshav Savant [https://community.jboss.org/people/kcsavant] created the discussion
"JBOSS WS | OutOfMemory GC overhead limit exceeded"
To view the discussion, visit: https://community.jboss.org/message/726901#726901
--------------------------------------------------------------
Hi All,
We have a web service deployed on JBoss 5.1.0 GA with JBoss Native 3.2.2.GA . (Got to know that Native WS is EOL now, will work on migration later). We used bottom-up approach and we are sending a complex java object that contains Strings, Long, Boolean and byte[] to web service.
We are calling web service for almost 60 to 90 times per minute. We are getting OOM GC overhead limit exceeded often (every 2 to 3 weeks), we got the heapdump (we have a heap of 1.5G) for that, on analysing the heapdump we see a lot of objects of ConcurrentHashMap for almost 1G. Most of these ConcurrentHashMaps<String, Object> are containing key as pointing to some XSD that is in-turn pointing to the web service class we have, for example the key is *+java.lang.String "JBossWS_webservice.my_package.my_company.com_8892700084997890448.xsd",+* here our web service implementation class is in +*com.my_company.my_package.webservice*+ package. All the ConcurrentHashMap shows same kind of stuff.
Can anybody please advise why there are so much of ConsurrentHashMap object in heap ?
Thanks,
Keshav
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/726901#726901]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years
[jBPM] - Re: Only the default "Evaluation" process is shown in the process list after restarting jBPM 5.2
by Yanhui Xie
Yanhui Xie [https://community.jboss.org/people/yanhuixie] created the discussion
"Re: Only the default "Evaluation" process is shown in the process list after restarting jBPM 5.2"
To view the discussion, visit: https://community.jboss.org/message/726242#726242
--------------------------------------------------------------
Should the text(excerpt from UserGuide 5.2, Chapter 15) below helps?
-----------------------------
The current integration of jBPM-console with Guvnor uses the following conventions to find the artefacts it needs:
* jBPM-console looks up artefacts from all available Guvnor packages (it does not look for assets in the Global Area). You can alternatively modify the guvnor.packages property in jBPM.console.properties to limit the lookup to only the packages you need, for example: guvnor.packages=defaultPackage, myPackageA, myPackageB
* A process should define the correct package name attribute, which needs to match the Guvnor package name it belongs to (otherwise you won't be able to build your package in Guvnor)
* Don't forget to build all of your packages in Guvnor before trying to view available processes in the console. Otherwise jBPM-console will not be able to retrieve the pkg from Guvnor.
* Currently, the console will load the process definitions the first time the list of processes is requested in the console. At this point, automatic updating from Guvnor when the package is rebuilt is turned off by default, so you will have to either configure this or restart the application server to get the latest versions.
* Task forms that should be associated with a specific process definition should have the name "{processDefinitionId}.ftl" or "{processDefinitionId}-taskform.ftl"
* Task forms for a specific human task should have the name "{taskName}.ftl" or "{taskName}-taskform.ftl"
* The process diagram for a specific process should have the name "{processDefinitionId}-image.png"
* By default jBPM-console looks up your Guvnor instance under http://localhost:8080/drools-guvnor http://localhost:8080/drools-guvnor. To change this, locate jbpm.console.properties and modify the guvnor.protocol, guvnor.host, and guvnor.subdomain property values as needed
* jBPM-console communicates with Guvnor via its REST api. The default connect and read timeouts for this communication are set to 10 seconds via the guvnor.connect.timeout, and guvnor.read.timeout properties in jbpm.console.properties. You can edit values of these properties to set your specific timeout values (in milliseconds)
* If you are using Guvnor with JAAS authentication enabled, jBPM-console uses by default admin/admin credentials. To change this information again locate jbpm.console.properties and change the guvnor.usr, and guvnor.pwd property values.
If you follow these rules, your processes, forms and images should show up without any issues in the jBPM-console.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/726242#726242]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years