[jBPM Users] - Re: StaleObjectException in JBPM 4.0
by kukeltje
"mmusaji" wrote : I don't mind being a guinea pig. I hope this helps other people who have the same issue.
|
Not only others, also us (creating awareness)
"mmusaji" wrote :
| Most of what you guys are saying is going over my head, however I think if the teardown waited for the process to finish this would resolve this problem quite quickly.
|
Then you at least got my main point ;-)
"mmusaji" wrote :
| If I wanted to do this and override the tear down method in my Junit can you please post an example of how I would go about this? Would be a large amount of code involving checking the db or is there "isAlive()" method somewhere?
The source of the AbstractDBTestcase is the basis. But just before deleting it, retrieve the processinstance based on the id, if this succeeds,, sleep, then retrieve it again based on the processInstance id. If this returns null, it is ended and you can delete it
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251593#4251593
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251593
16 years, 8 months
[JBoss Portal Users] - Re: VFSZIP problem ?
by blopes
I did try with a different application, and still the same problem.
Does anyone knows how to solve it ?
16:33:42,275 INFO [TomcatDeployment] deploy, ctxPath=/jersey
16:34:23,128 INFO [PackagesResourceConfig] Scanning for root resource and provider classes in the packages:
com.bitkickers
16:34:23,141 WARNING [AnnotatedClassScanner] URL, vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/jersey.war/WEB-INF/lib/jersey.jar/com/bitk
ickers/, is ignored, it not a file or a jar file URL
16:34:23,983 SEVERE [WebApplicationImpl] The ResourceConfig instance does not contain any root resource classes.
16:34:23,984 ERROR [[/jersey]] StandardWrapper.Throwable
com.sun.jersey.api.container.ContainerException: The ResourceConfig instance does not contain any root resource classes.
at com.sun.jersey.server.impl.application.WebApplicationImpl.processRootResources(WebApplicationImpl.java:607)
at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:480)
at
...
Thanks,
Bruno
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251587#4251587
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251587
16 years, 8 months
[JBoss Messaging Users] - Connection error
by chipschoch
We are running JBossAS 4.2.2 with JBM 1.4.4. Recently we experience a problem and I am trying to track it down. It appeared to be a network issue in that we got the following in the log:
| 2009-08-25 10:45:22,902 ERROR | Thread-24 | org.jboss.remoting.callback.ServerInvokerCallbackHandler | Error handling callback
| org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [bisocket://10.33.32.22
| :1810191292/callback?callbackServerHost=10.33.32.22&callbackServerPort=1810191292&callbackServerProtocol=bisocket&clientMaxPoolSize=1&clientSocketClass=org.jb
| oss.jms.client.remoting.ClientSocketWrapper&datatype=jms&guid=axwm-58z961-fy0jth8v-1-fy0jumsb-4y&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.r
| emoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper]
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:548)
| at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:422)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:141)
| at org.jboss.remoting.Client.invoke(Client.java:1858)
| at org.jboss.remoting.Client.invoke(Client.java:718)
| at org.jboss.remoting.Client.invokeOneway(Client.java:769)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:829)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:700)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1467)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.handleDelivery(ServerSessionEndpoint.java:1379)
| at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:327)
| at org.jboss.messaging.core.impl.RoundRobinDistributor.handle(RoundRobinDistributor.java:119)
| at org.jboss.messaging.core.impl.MessagingQueue$DistributorWrapper.handle(MessagingQueue.java:583)
| at org.jboss.messaging.core.impl.ClusterRoundRobinDistributor.handle(ClusterRoundRobinDistributor.java:79)
| at org.jboss.messaging.core.impl.ChannelSupport.deliverInternal(ChannelSupport.java:670)
| at org.jboss.messaging.core.impl.MessagingQueue.deliverInternal(MessagingQueue.java:506)
| at org.jboss.messaging.core.impl.ChannelSupport.handle(ChannelSupport.java:251)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.routeInternal(MessagingPostOffice.java:2228)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.route(MessagingPostOffice.java:515)
| at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendMessage(ServerConnectionEndpoint.java:769)
| at org.jboss.jms.server.endpoint.ServerSessionEndpoint.send(ServerSessionEndpoint.java:399)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$send$aop(SessionAdvised.java:87)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
| at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspect.java:157)
| at sun.reflect.GeneratedMethodAccessor114.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_7280680627620114891.invokeNext(SessionAdvised$send_7280680627620114891.java)
| at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvised.java)
| at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendRequest.java:95)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:862)
| at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
| at org.jboss.remoting.Client.invoke(Client.java:1858)
| at org.jboss.remoting.Client.invoke(Client.java:718)
| at org.jboss.remoting.Client.invoke(Client.java:706)
| at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
| at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$send$aop(ClientSessionDelegate.java:499)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
| at org.jboss.jms.client.container.SessionAspect.handleSend(SessionAspect.java:661)
| at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect28.invoke(SessionAspect28.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
| at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$send_6145266547759487588.invokeNext(ClientSessionDelegate$send_6145266547759487588.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.send(ClientSessionDelegate.java)
| at org.jboss.jms.client.container.ProducerAspect.handleSend(ProducerAspect.java:276)
| at org.jboss.aop.advice.org.jboss.jms.client.container.ProducerAspect39.invoke(ProducerAspect39.java)
| at org.jboss.jms.client.delegate.ClientProducerDelegate$send_3961598017717988886.invokeNext(ClientProducerDelegate$send_3961598017717988886.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
|
I am particularly curious about the line
callbackServerPort=1810191292
Does this port number look to be correct? If not, could this be the cause of the failure to get a connection?
Thanks alot.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251575#4251575
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251575
16 years, 8 months
[JBoss Tools Users] - Re: Generating DDL from annotated POJOs
by JPAV
No, I'm not working with DTP at all. I've added the sqljdbc.jar to the Hibernate Console configuration classpath, the same type of configuration referenced in the video you pointed me to. I'm guessing there's probably something fundamentally wrong with my project due to the way I built it. My goal here was to start from a WSDL, then use the JAXWS tools built into JDK 1.6 to generate the respective POJOs from it, annotate those POJOs with JPA annotations (right along side the generated JAXB annotations), then generate DDL from these entities that I can use to build a representative view model in Teiid Designer. So, the only evidence in the project of things related to Hibernate/JPA is the @Entity tag on each of 2 classes and @GeneratedValue / @Id / @Column(name = "ID") for the id property I manually added to each. I don't have any entity resolvers, naming strategies, HibernateUtil classes, etc.
I also *sometimes* get compilation errors in this project (I haven't figured out the pattern yet for when these appear/disappear) related to those annotations in the form of "Column XXX cannot be resolved" for every property, where XXX is the property's name.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251558#4251558
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251558
16 years, 8 months