March 2007 - jboss-dev-forums - Jboss List Archives

[Design of Kosmos] - Re: What do I do next?

by aron.gombas

> These Forums don't seem to be too active, is Kosmos > still a 'current' project? Unfortunately, because of successful commercial project I couldn't spend any time working on this recently, but the project is definitely not "dead". There is some interesting activity (by a pretty big name) in the background. You'll notice when they really "pick up" the project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025724#4025724 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025724

19 years, 1 month

1
0
0 / 0

[Design of Kosmos] - Re: Install kosmos-0.2.0RC2 for Liferay 4.2.0

by aron.gombas

AFAIK, Liferay has seriously changed their portlet deployment mechanism with the recent releases. Kosmos itself doesn't have any special requirements, so please read the Liferay manual. I'd appreciate it, if you could contribute the changed build.xml back to the project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025722#4025722 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025722

19 years, 1 month

1
0
0 / 0

[Design of JBossXB] - Re: Cleaning up the jbossxb projects

by alex.loubyansky＠jboss.com

Fine by me. Is there a reason not to merge Adrian's annotations work into trunk? The lesser branches we have the better. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025720#4025720 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025720

19 years, 1 month

1
0
0 / 0

[Design of Kosmos] - Re: JIRA monitoring problem: Nothing found to display.

by aron.gombas

Well, this log snippet shows the app and Slide were properly deployed, but it's not related to your particular problem. Instead, I'd need that log part that is generated when reloading the JIRA information. BTW do you have the same problem both with JIRA web scraping implementation and the remote API-based implementation? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025719#4025719 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025719

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Need source for the jboss/jms-integration-tests jars

by scott.stark＠jboss.org

We need to include source artifacts for the jboss/jms-integration-tests jars to facilitate debugging. Currently these all fail with no exceptions and I want to look at what they do. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025713#4025713 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025713

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - org.objectweb.jtests configuration logic is poor

by scott.stark＠jboss.org

I'm looking at why the jbm tests are not running in trunk The way the org.objectweb.jtests.* tests look for a provider.properties resource does not work in trunk due to there being multiple sources of this resource. One is in the joram-tests.jar (this is what is found and its useless), one is in testsuite/source/resources/jbossmessaging. There are also multiple places that try to load this file, one is org.jboss.test.jbossmessaging.JMSTestCase, another is org.objectweb.jtests.jms.admin.AdminFactory from the joram-tests.jar. In order for these tests to run as currently coded, the testsuite/source/resources/jbossmessaging would need to be on the test classpath. Instead of using a static provider.properties resource name, it would be better to accept a dynamic resource name like "jbossmessaging/provider.properties". This would allow the test specific classes to override the location without needing additional classpath hacking, and it would allow one to run the tests from within eclipse using the current testsuite/resources classpath element. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025694#4025694 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025694

19 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Re: JPDL based web services example

by kukeltje

in an actionhandler and just like you would normally from java View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025690#4025690 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025690

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Need help for ESB related Exception

by mishra.piku

Hi Guys, I have written a simple web application for which I get some text information from a JSP page. The text message is "Hello How are you". I am passing this message using ESB and I want a response from the server ie server will generate some message(Text), this message will be displayed in the JSP page. Everything relating to ESB configuration is ok for me. I have deployed this application as a .war file in deploy folder of Jboss. I have written an Initialization servlet to initiate ESB related stuffs. But when I passing the message and trying to get a response , I am getting the following Exception. I am unable to solve this. Can anybody help me to figure it out. I am giving the exception. ***************** Exception Below *************************** 12:52:45,037 INFO [STDOUT] ConsoleNotifier 2007/03/07 12:52:45.037<Response From Server.....> 12:52:50,068 INFO [STDOUT] java.lang.reflect.InvocationTargetException 12:52:50,068 INFO [STDOUT] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 12:52:50,068 INFO [STDOUT] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) 12:52:50,068 INFO [STDOUT] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.ja 12:52:50,068 INFO [STDOUT] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) 12:52:50,068 INFO [STDOUT] at org.jboss.soa.esb.notification.NotificationTarget.fromParams(NotificationTarget.java:100) 12:52:50,084 INFO [STDOUT] at org.jboss.soa.esb.notification.NotificationList.notifyAll(NotificationList.java:150) 12:52:50,084 INFO [STDOUT] at org.jboss.soa.esb.actions.Notifier.notifyOK(Notifier.java:66) 12:52:50,084 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 12:52:50,084 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 12:52:50,084 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 12:52:50,084 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:585) 12:52:50,084 INFO [STDOUT] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.actionClassFinishedOk(ActionProce 12:52:50,084 INFO [STDOUT] at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.run(ActionProcessingPipeline.java 12:52:50,084 INFO [STDOUT] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) 12:52:50,084 INFO [STDOUT] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) 12:52:50,084 INFO [STDOUT] at java.lang.Thread.run(Thread.java:595) 12:52:50,084 INFO [STDOUT] Caused by: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketT 12:52:50,084 INFO [STDOUT] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1317) 12:52:50,084 INFO [STDOUT] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1446) 12:52:50,084 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594) 12:52:50,084 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) 12:52:50,084 INFO [STDOUT] at javax.naming.InitialContext.lookup(InitialContext.java:351) 12:52:50,099 INFO [STDOUT] at org.jboss.soa.esb.notification.NotifyQueues.lookupQueueConnectionFactory(NotifyQueues.java:97) 12:52:50,099 INFO [STDOUT] at org.jboss.soa.esb.notification.NotifyQueues.setQueues(NotifyQueues.java:69) 12:52:50,099 INFO [STDOUT] at org.jboss.soa.esb.notification.NotifyQueues.(NotifyQueues.java:65) 12:52:50,099 INFO [STDOUT] ... 16 more 12:52:50,099 INFO [STDOUT] Caused by: java.net.SocketTimeoutException: Receive timed out 12:52:50,099 INFO [STDOUT] at java.net.PlainDatagramSocketImpl.receive0(Native Method) 12:52:50,099 INFO [STDOUT] at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136) 12:52:50,099 INFO [STDOUT] at java.net.DatagramSocket.receive(DatagramSocket.java:712) 12:52:50,115 INFO [STDOUT] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1287) 12:52:50,115 INFO [STDOUT] ... 23 more 12:52:50,115 INFO [STDOUT] 12:52:50,115 ERROR [NotificationList] Can't instantiate target <messageProp name="ESB_First_Test_Project_V1" value="SomeActionForListene java.lang.Exception: NotifyQueues does not extend NotificationTarget at org.jboss.soa.esb.notification.NotificationTarget.fromParams(NotificationTarget.java:103) at org.jboss.soa.esb.notification.NotificationList.notifyAll(NotificationList.java:150) at org.jboss.soa.esb.actions.Notifier.notifyOK(Notifier.java:66) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.actionClassFinishedOk(ActionProcessingPipeline.java:181) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.run(ActionProcessingPipeline.java:112) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025685#4025685 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025685

19 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Re: Major transaction problem

by david.lloyd＠jboss.com

Okay, this just isn't making any sense. There are so many exceptions around rollback, things like "transaction already marked for rollback" and "could not register synchronization with JTA TransactionManager", that it's nearly impossible to figure out the underlying cause. What I *can* tell is that both hibernate and jBPM seem to be forcing a rollback on the transaction under some circumstances, and it seems like a new transaction may not be started afterwards. Still trying to unwind the txn spaghetti. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025610#4025610 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025610

19 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Re: Major transaction problem

by david.lloyd＠jboss.com

Yes, JTA transactions in the EAR are majorly broken. The underlying exception *appears* to be: java.lang.NullPointerException at org.jbpm.persistence.db.DbPersistenceService.rollback(DbPersistenceService.java:304) at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:238) at org.jbpm.svc.Services.close(Services.java:222) Investigating further. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025601#4025601 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025601

19 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2007