August 2009 - jboss-user - Jboss List Archives

[jBPM Users] - Re: BUILD FAILED and deployment failed: Internal server Er

by sutiantian

I got exactly the same error and struggle for two days already. did you get your solution? if you have one, could you please post here? that would be very helpful. Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251954#4251954 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251954

16 years, 8 months

1
0
0 / 0

[JNDI and Naming] - Re: JNDI lookup from JBoss embedded MQ Provider

by vickyk

"moonbird79" wrote : | +- activemq (class: org.jnp.interfaces.NamingContext) | | +- topic (class: org.jnp.interfaces.NamingContext) | | | +- inbound (class: org.apache.activemq.command.ActiveMQTopic) | | +- QueueConnectionFactory (class: org.apache.activemq.ra.ActiveMQConnectionFactory) | +- stationInfoQueue (class: org.apache.activemq.command.ActiveMQQueue) | +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory) The following call should work ConnectionFactory factory = (ConnectionFactory) ctx.lookup("activemq/QueueConnectionFactory"); What error do you get when this is called? Does this configuration work in JBoss4.x series? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251949#4251949 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251949

16 years, 8 months

1
0
0 / 0

[JNDI and Naming] - Re: Fail to get tables by a remote Datasource deployed in JB

by poweryoung

Sorry, the "red line" should be: ResultSet rs = dbmd.getTables(null, "%", "%", new String[] { "TABLE", "VIEW" }); View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251947#4251947 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251947

16 years, 8 months

1
0
0 / 0

[JNDI and Naming] - Fail to get tables by a remote Datasource deployed in JBOSS

by poweryoung

Hi, all: I try to use DatabaseMetaData to get all tables and views from a Oracle database. But exception is thrown at the red line. You can see that I look up a remote DataSource and get connection from the data source. But if I use DriverManager.getConnection(url, user, pwd) way to get connection. This issue does not exist. I can get all the tables and views successfully... Any help from you will be much appreciated! public class Test { | | public static void main(String[] args) throws Exception { | | Properties props = new Properties(); | | props.put(Context.PROVIDER_URL, "jnp://10.111.3.161:1099"); | | props.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); | | Context ctx = new InitialContext(props); | | DataSource ds = (DataSource)ctx.lookup("OracleDS"); | | Connection conn = ds.getConnection(); | | DatabaseMetaData dbmd = conn.getMetaData(); | | ResultSet rs = dbmd.getTables(null, "%", "%", new String[] { "TABLE", "VIEW" }); | | } | | } Exception: Exception in thread "main" java.lang.ClassCastException: $Proxy3 at $Proxy2.getTables(Unknown Source) at Test.main(Test.java:62) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251946#4251946 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251946

16 years, 8 months

1
0
0 / 0

[jBPM Users] - Re: How to control process transition in JBPM 4.0?

by jbpmjboss11

My puzzle still not resolved. I got another problem while working on use case i have explained earlier in the same thread. I have a process with two java task one after another... Both takes input values and return some object. Now, per my use case one UI page calls one Java task of the process. First web page calls to first java task but, when I do startprocessInstanceByKey("name",variables); it throws exception shouting for input arguments for second java task, and can not proceed further. But, when I am at first page I do not have input ready for the class mentioned in second java task. The input for second task comes from the second web page. Can you experts throw some light ... Appreciate your help. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251944#4251944 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251944

16 years, 8 months

1
0
0 / 0

[JBoss Messaging Users] - Re: enableOrderingGroup() not available inside ejb3 Bean an

by gaohoward

Yes you can use the XAConnectionFactory and use JTA stuff to enlist the resources into the transaction. Howard View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251939#4251939 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251939

16 years, 8 months

1
0
0 / 0

[JBoss Messaging Users] - Re: Messages get stuck on node

by gaohoward

Hi, How is the JMX console looks like? such as message count, delivering count etc. Thanks Howard View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251938#4251938 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251938

16 years, 8 months

1
0
0 / 0

[jBPM Users] - Re: JobScheduler going crazy - ignoring wait

by rachel.primrose

OK so I found the issue. After an unsafe shutdown, if a job is in the "Aquired" state in the DB, then the job executor will look for the next job to process and assume that a thread is currently dealing with that Aquired job. So, basically, I had to delete that job (or I guess I could have set it back to waiting), and the problem went away. Good thing this is a development environment. I'm going to update my shutdown code to correctly shutdown the job scheduler, and add a checker for this on startup. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251937#4251937 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251937

16 years, 8 months

1
0
0 / 0

[jBPM Users] - JobScheduler going crazy - ignoring wait

by rachel.primrose

Hi guys, I've got the same code (EXACTLY the same code) running on my windows machine, and on Ubuntu. On windows, my java version is 1.6.0_13 on ubuntu it's 1.6.0_06. My problem is that even using identical code, the scheduler on the ubuntu box goes crazy. Here's my debug logs from the windows machine: | 2009-08-27 14:35:37,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:35:37,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-28 09:31:00.0 | 2009-08-27 14:35:37,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.DispatcherThread - DispatcherThread will wait for max 5000ms on org.jbpm.pvm.internal.jobexecutor.JobExecutor@127e2ee | 2009-08-27 14:35:42,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.DispatcherThread - DispatcherThread woke up | 2009-08-27 14:35:42,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:35:42,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:35:42,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:35:42,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-28 09:31:00.0 | 2009-08-27 14:35:42,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.DispatcherThread - DispatcherThread will wait for max 5000ms on org.jbpm.pvm.internal.jobexecutor.JobExecutor@127e2ee | 2009-08-27 14:35:47,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.DispatcherThread - DispatcherThread woke up | 2009-08-27 14:35:47,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:35:47,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:35:47,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:35:47,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-28 09:31:00.0 | 2009-08-27 14:35:47,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.DispatcherThread - DispatcherThread will wait for max 5000ms on org.jbpm.pvm.internal.jobexecutor.JobExecutor@127e2ee | 2009-08-27 14:35:52,947 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.DispatcherThread - DispatcherThread woke up | As you can see, it is running the default three threads, with each one waiting politely for around 5 seconds. Here's the log from the ubuntu box: | 2009-08-27 14:25:26,438 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,439 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,439 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,439 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,439 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,439 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,439 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,440 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,440 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,440 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,440 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,440 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,440 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,440 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,440 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,441 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,441 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,441 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,441 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,442 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,442 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,442 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,442 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,443 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,443 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,443 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,443 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,443 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,443 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,444 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,444 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,444 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,444 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,444 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,444 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,444 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,444 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,445 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,445 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,445 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,445 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,445 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,445 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,446 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,446 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | 2009-08-27 14:25:26,446 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - next due date is 2009-08-17 10:48:36.0 | 2009-08-27 14:25:26,446 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - start querying first acquirable job... | 2009-08-27 14:25:26,446 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.AcquireJobsCmd - locking jobs [] | 2009-08-27 14:25:26,446 [DispatcherThread] DEBUG org.jbpm.pvm.internal.jobexecutor.GetNextDueDateCmd - getting next due date... | It's not waiting! The only difference between the two is that on windows I'm running this in Eclipse, and on the Ubuntu box it's nicely jar'd up etc. However, all the required files are still on the classpath, and every other aspect of the workflow engine runs like clockwork. If you have any ideas, I'd be very grateful. Thanks. - Rachel (Kit) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251936#4251936 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251936

16 years, 8 months

1
0
0 / 0

[Security] - Re: run -c default -b node1.jboss.com

by norazanita_adnan

hi Wolfgang Knauf thanks for highlighting it.. it been Last Modified: Aug 25, 2009 2:38 PM by ANIL SALDHANA.... alright .. i'll start from here.. thanks once again..... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251935#4251935 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251935

16 years, 8 months

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-user August 2009