[JBoss AOP] - Failed to install aop-ver2 to jboss server ver-4.2.2
by avihaimar
Hey,
I download fresh copy of jboss-server version - 4.2.2, aop-ver-2CR13
I run the build script under - jboss-40-install\jboss-aop-jdk50.deployer\
and the script run successfully, but now when i execute jboss run script(i didnt deploy or change anything in jboss-server) i get an exception:
22:45:12,153 WARN [ServiceController] Problem starting service jboss:service=We
| bService
| java.lang.Exception: Port 8083 already in use.
| at org.jboss.web.WebServer.start(WebServer.java:233)
| at org.jboss.web.WebService.startService(WebService.java:322)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
| upport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
| eanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
| er.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168572#4168572
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168572
17 years, 8 months
[JBoss Messaging] - Re: All messages are not persisted in Database.
by sajankn
I'm not able to attach the files, hence putting the code as such.
Publisher Code:
| import javax.jms.Connection;
| import javax.jms.ConnectionFactory;
| import javax.jms.DeliveryMode;
| import javax.jms.JMSException;
| import javax.jms.MessageProducer;
| import javax.jms.Session;
| import javax.jms.TextMessage;
| import javax.jms.Topic;
| import javax.jms.TopicConnection;
| import javax.jms.TopicConnectionFactory;
| import javax.jms.TopicPublisher;
| import javax.jms.TopicSession;
|
| import javax.naming.InitialContext;
| import javax.naming.NamingException;
|
| public class MyPublisher
| {
| public static void main(String[] args)
| {
| try
| {
| String destinationName = "/topic/testTopic";
| InitialContext ic = new InitialContext();
| TopicConnectionFactory cf = (TopicConnectionFactory)ic.lookup("/ClusteredConnectionFactory");
| Topic topic = (Topic)ic.lookup(destinationName);
| TopicConnection connection = cf.createTopicConnection();
| TopicSession session = connection.createTopicSession(false, TopicSession.AUTO_ACKNOWLEDGE);
| TopicPublisher publisher = session.createPublisher(topic);
| connection.start();
| String msgStr = "Hello World";
| for (int i = 0; i< 1000; i++)
| {
| TextMessage tm = session.createTextMessage(msgStr + i);
| publisher.publish(tm);
| }
| }
| catch(JMSException jmse)
| {
| jmse.printStackTrace();
| }
| catch(NamingException ne)
| {
| ne.printStackTrace();
| }
| catch(Exception e)
| {
| e.printStackTrace();
| }
| }
| }
|
Run.sh for Publisher:
| java -Dcom.sun.management.jmxremote.port=12346 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.naming.factory.initial=org.jboss.naming.NamingContextFactory -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces -Djava.naming.provider.url=jnp://MY_SERVER:PORT_NO -DespStress-Xms256m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=360000 -Dsun.rmi.dgc.server.gcInterval=360000 -Xloggc:gc.log -classpath ${CLIENT_CLASSPATH} MyPublisher
|
Subscriber Code:
| import javax.jms.JMSException;
| import javax.jms.TextMessage;
| import javax.jms.Topic;
| import javax.jms.TopicConnection;
| import javax.jms.TopicConnectionFactory;
| import javax.jms.TopicSession;
| import javax.jms.TopicSubscriber;
| import javax.naming.InitialContext;
| import javax.naming.NamingException;
|
| public class MySubscriber
| {
| public static void main(String[] args)
| {
| try
| {
| String destinationName = "/topic/testTopic";
| InitialContext ic = new InitialContext();
| TopicConnectionFactory cf = (TopicConnectionFactory)ic.lookup("/ClusteredConnectionFactory");
| Topic topic = (Topic)ic.lookup(destinationName);
| TopicConnection connection = cf.createTopicConnection("admin", "admin");
| connection.setClientID("MyClientID");
| TopicSession session = connection.createTopicSession(false, TopicSession.AUTO_ACKNOWLEDGE);
| TopicSubscriber subscriber = session.createDurableSubscriber(topic, "MyName");
| connection.start();
| while (true)
| {
| TextMessage message = (TextMessage)subscriber.receive(5000);
| if (message != null)
| {
| String msgStr = message.getText();
| System.out.println(msgStr);
| }
| message = null;
| }
| }
| catch(JMSException jmse)
| {
| jmse.printStackTrace();
| }
| catch(NamingException ne)
| {
| ne.printStackTrace();
| }
| catch(Exception e)
| {
| e.printStackTrace();
| }
| }
| }
|
Run.sh for Subscriber:
| java -Dcom.sun.management.jmxremote.port=12346 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djava.naming.factory.initial=org.jboss.naming.NamingContextFactory -Djava.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces -Djava.naming.provider.url=jnp://MY_SERVER:PORT_NO -DespStress-Xms256m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=360000 -Dsun.rmi.dgc.server.gcInterval=360000 -Xloggc:gc.log -classpath ${CLIENT_CLASSPATH} MySubscriber
|
Currently I'm doing a work-around for the messages not persisted in DB. For every new topic, I publish a few test messages and subscribe them. After the first time, the messages are always persisted, hence I dont lose any message.
Also the Subscriber sometime do not consume messages even though they are present in the database and require restart (some time more than once) of the subscriber.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168567#4168567
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168567
17 years, 8 months
[JBoss jBPM] - Re: Unable to locate current JTA transaction
by crued
"shilpa.kumar(a)indussoft.com" wrote : I am also getting the same error. I am working on jbpm3.2.2\jbpm-jpdl-3.2.2 & websphere 6. I am able to connect and give token.signal but at state-end i am getting this error.
|
| | org.jbpm.db.JobSession deleteJobsForProcessInstance org.hibernate.TransactionException: Could not register synchronization
| |
| Can you please help me. I already running behind time. and saw all sites from almost 2 weeks. but still not getting any solution.....
|
|
I don't have a solution, but I'm experiencing the same problem, I think. In my case, I'm manually clicking "End" while viewing a process instance in the jbpm-console web app.
I've followed the stack traces and found that the reason that the synchronization couldn't be registered is because of a NullPointerException that occurs inside CMTTransaction on line 156:
| 154: public void registerSynchronization(Synchronization sync) throws HibernateException {
| 155: try {
| 156: getTransaction().registerSynchronization(sync);
| 157: }
| 158: catch (Exception e) {
| 159: throw new TransactionException("Could not register synchronization", e);
| 160: }
| 161: }
|
So for some reason, getTransaction() is returning null...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168559#4168559
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168559
17 years, 8 months
[Beginners Corner] - Re: Application Error - Resource not Found
by shawn.geraghty
Here is the application.xml file:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN' 'http://java.sun.com/dtd/application_1_3.dtd'>
|
| <application>
| <display-name>TrufinaCSA</display-name>
| <module>
| <web>
| <web-uri>csa.war</web-uri>
| <context-root>turtle</context-root>
| </web>
| </module>
| </application>
|
Here is the jboss-app.xml file:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Document : jboss-app.xml
| Created on : April 11, 2005, 1:27 PM
| Author : Administrator
| Description:
| Purpose of the document follows.
| -->
|
| <jboss-app>
| <loader-repository>www.trufina.com:loader=csa-turtle</loader-repository>
| </jboss-app>
|
And here is the jboss-web.xml file:
| <jboss-web>
| <security-domain>java:/jaas/mytrufina_TrufinaDev</security-domain>
| </jboss-web>
And here is the ls of the deploy directory:
| rw-r--r--@ 1 slegg slegg 2048 Oct 14 2004 cache-invalidation-service.xml
| -rw-r--r--@ 1 slegg slegg 1481 Oct 14 2004 client-deployer-service.xml
| -rw-r--r-- 1 slegg slegg 9475965 Aug 1 18:11 csa-turtle.ear
| -rw-r--r--@ 1 slegg slegg 384 Oct 14 2004 hibernate-deployer-service.xml
| -rw-r--r--@ 1 slegg slegg 4486 Oct 14 2004 hsqldb-ds.xml
| drwxr-xr-x@ 4 slegg slegg 136 Oct 14 2004 http-invoker.sar
| -rw-r--r--@ 1 slegg slegg 123001 Oct 14 2004 jboss-jca.sar
| -rw-r--r--@ 1 slegg slegg 6735 Oct 14 2004 jboss-local-jdbc.rar
| -rw-r--r--@ 1 slegg slegg 12307 Oct 14 2004 jboss-xa-jdbc.rar
| drwxr-xr-x@ 33 slegg slegg 1122 Jun 16 19:50 jbossweb-tomcat50.sar
| drwxr-xr-x@ 11 slegg slegg 374 Jun 16 19:50 jms
| drwxr-xr-x@ 11 slegg slegg 374 Aug 1 18:10 jmx-console.war
| drwxr-xr-x@ 3 slegg slegg 102 Oct 14 2004 jmx-invoker-adaptor-server.sar
| -rw-r--r--@ 1 slegg slegg 1580 Oct 14 2004 mail-service.xml
| drwxr-xr-x@ 4 slegg slegg 136 Oct 14 2004 management
| -rw-r--r--@ 1 slegg slegg 4025 Oct 14 2004 monitoring-service.xml
| -rw-r--r--@ 1 slegg slegg 1830 Oct 14 2004 properties-service.xml
| -rw-r--r--@ 1 slegg slegg 3906 Oct 14 2004 schedule-manager-service.xml
| -rw-r--r--@ 1 slegg slegg 1784 Oct 14 2004 scheduler-service.xml
| -rw-r--r--@ 1 slegg slegg 198 Oct 14 2004 sqlexception-service.xml
| -rw-r--r--@ 1 slegg slegg 1348 Oct 14 2004 transaction-service.xml
| -rw-r--r-- 1 slegg slegg 704 Jul 29 14:39 trufina_TrufinaDev-ds.xml
| -rw-r--r-- 1 slegg slegg 10827882 Jul 29 14:39 turtle-turtle.ear
| -rw-r--r--@ 1 slegg slegg 1103 Oct 14 2004 user-service.xml
| -rw-r--r--@ 1 slegg slegg 5405 Oct 14 2004 uuid-key-generator.sar
|
And yes, the csa.war file is contained within the csa-turtle.ear file.
So, from the application.xml file, I see the context-root is "turtle". Now in our QA, staging, and production environments, context-root is set to "latest", "stage", and "prod". I would assume that I have this incorrectly set here .... it should be something other than "turtle". Is this why my turtle app is getting hosed?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168549#4168549
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168549
17 years, 8 months