July 2007 - jboss-user - Jboss List Archives

[EJB 3.0] - Re: Automatic table creation

by waynebaylor

yeah, I've only seen those errors when using create-drop and it can't drop the tables because they don't exist. But that's not a fatal error and things still work... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061377#4061377 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061377

18 years, 9 months

1
0
0 / 0

[JBoss jBPM] - Re: Concurrent Processing using Fork in synchronous manner

by drashmi30

I have already seen this JIRA but this JobExecutorThread comes into picture when you mark the node execution to be in asynchronous mode. But my case is not like that. Consider the below processdefinition: | <?xml version="1.0" encoding="UTF-8"?> | | <process-definition | xmlns="" name="mainprocsimple1_JBPM"> | <join name="join1"> | <transition name="" to="end1"></transition> | </join> | <start-state name="start"> | <transition name="" to="fork1"></transition> | </start-state> | <fork name="fork1"> | <transition name="tr1" to="state1"></transition> | <transition name="2" to="state2"></transition> | </fork> | <node name="mainnode_sleep120"> | <action class="org.jbpm.tutorial.action.Sleep_120_ActionHandler"> | </action> | | <transition name="" to="join1"></transition> | </node> | <node name="mainnode_sleep80"> | <action class="org.jbpm.tutorial.action.Sleep_80_ActionHandler"> | </action> | | <transition name="" to="join1"></transition> | </node> | <state name="state1"> | <transition name="tim" to="mainnode_sleep80"></transition> | </state> | <end-state name="end1"></end-state> | <state name="state2"> | <transition name="" to="mainnode_sleep120"></transition> | </state> | </process-definition> | In the above example, when i signal state1 and state2 simultaneously, then the execution flows to mainnode_sleep80 and mainnode_sleep120. But since in mainnode_sleep80, I call an ActionHandler which simply makes a sleep for 80 secs and in the other node mainnode_sleep120, the ActionHandler makes a sleep of 120 secs. The path of execution for mainnode_sleep80 completes successfully but when mainnode_sleep120 completes after making a sleep for 120 secs, we get an error as StaleObjectStateException saying that the row was already updated or deleted in another transaction. The above scenario is only an example of our process and not the real case. We are just trying to find out why we are getting this error and whether there is any solution to avoid such an error. I make myself very clear that I am not looking for async operation. I want the normal sync operation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061372#4061372 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061372

18 years, 9 months

1
0
0 / 0

[JBoss jBPM] - Re: StaleObjectStateException after a fork

by estaub

See http://jira.jboss.com/jira/browse/JBPM-983 , and vote for it if relevant - it probably is. Are you using the JobExecutor? It may help your particular case to mark a node on each fork with "asynchronous=exclusive". This helps in some simple cases. But it really just changes the odds in a race-condition situation - it's not a sure fix. -Ed Staub View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061369#4061369 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061369

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: fail to send parameter to a function in xhtml

by JakeC

If your el is in an action, you can use it directly in the el, like this: | <h:column> | <s:button action="#{pooledTask.assign(actorId)}" taskInstance="#{task}" value="Assign"/> | </h:column> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061368#4061368 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061368

18 years, 9 months

1
0
0 / 0

[Tomcat, HTTPD, Servlets & JSP] - Re: jboss 3.2.8 (SP1) with tomcat 5.5

by abhinav76

Hi mk, I am assuming that you are trying to replace the tomcat 55.sar because you want to run the JSPs having J2SE 1,5 syntax. For doing that, you can just replace the jasper compiler instead of replacing the whole sar. All you have to do is - copy jasper-compiler.jar, jasper-compiler-jdt.jar and jasper-runtime.jar from jbossweb-tomcat55.sar into jbossweb-tomcat50.sar. Warm regards, Abhinav http://abhinavmaheshwari.blogspot.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061367#4061367 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061367

18 years, 9 months

1
0
0 / 0

[JBoss jBPM] - Re: Concurrent Processing using Fork in synchronous manner

by estaub

See http://jira.jboss.com/jira/browse/JBPM-983, and vote for it if relevant - it probably is. Are you using the JobExecutor? More specifics on your workflow would be helpful, if it's at all more complicated than you've stated. It may help your particular case to mark a node on each fork with "asynchronous=exclusive". This helps in some simple cases. -Ed Staub View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061366#4061366 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061366

18 years, 9 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Exception is thrown when shutting down the server

by DjHitItUp

When shutting downt he server with: shutdown.sh --shutdown The exception that is being thrown is: Exception: Could not obtain connection to any of these urls: localhost:1099 [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused (errno:239)]]] at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1414) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:594) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.Shutdown.main(Shutdown.java:214) Caused by: javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused (errno:239)]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1385) ... 4 more Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused (errno:239)] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243) ... 5 more Caused by: java.net.ConnectException: Connection refused (errno:239) at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:517) at java.net.Socket.connect(Socket.java:467) at java.net.Socket.(Socket.java:364) at java.net.Socket.(Socket.java:265) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239) ... 5 more Why is this? I take it this is not a good shutdown of JBoss so what can I do to resolve the issue? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061364#4061364 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061364

18 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: Automatic table creation

by georgesberscheid

Right, that's the theory. The database was empty at first. The tables were created the first time I deployed the beans. If I change the entity beans, the tables are not modified at redeployment. SQL Exceptions are thrown instead when the data is accessed because the schema doesn't match. But that doesn't matter because I don't change my beans. I'm just wondering why it says that the tables do not exist if it has just created them in the previous deployment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061363#4061363 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061363

18 years, 9 months

1
0
0 / 0

[JBoss jBPM] - Re: Partnership between JBoss and ActiveEndpoints

by bill.burke＠jboss.com

Don't quote me, but I think the partnership is meant to address tooling and doesn't affect us implementing a bpel engine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061362#4061362 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061362

18 years, 9 months

1
0
0 / 0

[JBoss Tools (users)] - Re: New Seam project configuration

by fabricio.lemos

Issue created: http://jira.jboss.com/jira/browse/JBIDE-561 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4061359#4061359 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4061359

18 years, 9 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 July 2007