[jBPM] New message: "Re: Exception handling in JBPM4 ?"
by Maciej Swiderski
User development,
A new message was posted in the thread "Exception handling in JBPM4 ?":
http://community.jboss.org/message/527675#527675
Author : Maciej Swiderski
Profile : http://community.jboss.org/people/swiderski.maciej
Message:
--------------------------------------------------------------
What about following scenario:
- there are 4 nodes (regardless of type) that executed as part one transaction.
- some of the nodes modify some external systems via different protocols
- no exceptions are thrown from nodes
- runtime exception is thrown due to some persistence issues
Transaction will be rolled back but changes made to external system are not rolled back since they were not part of the transcation (for example web service call).
Have you put any thoughts into that? I was wondering if some sort of compensation mechanism could be introduces to the execution where nodes that take part in transaction can inform runtime engine what to invoke in case of roll backs. This could give kind of undo operation for already finished nodes and should not cause any problems when process will go thru them again.
What's your opinion about it? Does it sound reasonable?
Cheers,
Maciej
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/527675#527675
16 years, 2 months
[Beginner's Corner] New message: "Re: Port already in use: 1098 - URGENT"
by Sashi Kanth
User development,
A new message was posted in the thread "Port already in use: 1098 - URGENT":
http://community.jboss.org/message/527671#527671
Author : Sashi Kanth
Profile : http://community.jboss.org/people/rockey007
Message:
--------------------------------------------------------------
Ya I tried checking whether JBoss is still running. I made sure no server instance is still running. I tried with checking TCPView but nothing helped out. There was no process is binding this port. After completely stopping JBoss from my IDE I ran another instance from JBoss dump which is from originally downloaded long back. Even that standalone running complained saying 1098 port is already taken by some other process. Finally I had to delete my server, delete the backup dump, clean registry, disable my jBoss service, clean everything what ever that had info on jBoss, search and delete registry, totally get rid of jBoss from my system, download a fresh copy again and ran the server. Now its working normally like before.
I think this is not a feasible solution but this how I got rid of that port bind message. Since I'm using jBoss as standalone server in my local dev box deleting is not going to be a big problem but definitely not a correct solution. I had to spend time again on creating my dev environment. There was no definite answer in the web. Not my co-developers had the same solutions. When I sent mail across team most of them replied saying they had this problem, surprisingly everybody had their way of solving and any one of their solution helped me. Well, this is how this problem solved but there must be something else is happening for jBoss preferred ports binding.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/527671#527671
16 years, 2 months
[JBoss Microcontainer Development] New message: "Re: CallbackItem.changeCallback() very expensive due to context tracking"
by Ales Justin
User development,
A new message was posted in the thread "CallbackItem.changeCallback() very expensive due to context tracking":
http://community.jboss.org/message/527663#527663
Author : Ales Justin
Profile : http://community.jboss.org/people/alesj
Message:
--------------------------------------------------------------
> For B I don't really understand exactly why this is being done? It looks like we check for ContextTracker in each metadata level at INSTANCE level and above, up to JVM. Wouldn't that be handled by the call to metaData.getMetaData() in C anyway?
Yeah, I think it you're right.
Since, if the context/scopeInfo's scope key doesn't include certain scope level,
looking with B doesn't really help -- same result as with C.
e.g. B's MetaData is just a collection of Cs
> For A, maybe scopeInfo could keep a reference to the MetaData to avoid having to access the repository every time we call scopeInfo.getMetaData()?
>
>
>
How many times do we invoke this?
For ContextTracker retrieval, this should only be called once, as we should get the CT on the first call.
(CT is setup in AS -- see kernel.xml, but not by default for MC tests)
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/527663#527663
16 years, 2 months
[JBoss Web Services] New message: "Issues with JBoss 5.1.0 GA and JBossWS CXF 3.2.2 GA"
by Michael Maretzke
User development,
A new message was posted in the thread "Issues with JBoss 5.1.0 GA and JBossWS CXF 3.2.2 GA":
http://community.jboss.org/message/527657#527657
Author : Michael Maretzke
Profile : http://community.jboss.org/people/maretzke
Message:
--------------------------------------------------------------
Hi guys,
we're using JBoss 5.1.0 GA and JBossWS CXF 3.2.2 GA on Ubuntu Linux 9.10 (x86 32 Bit). We've installed JBoss 5.1.0 in /opt/jboss-5.1.0 and followed the description on how to install JBossWS - which went all fine and without any (!) issues.
When running JBoss in the "default" configuration (e.g. "./run.sh -c default" or "./run.sh") JBoss starts up without any issues - indicating JBossWS installation went smooth and fine. I tested the system with a EAR file containing some WS invocations - everything went really nicely.
Starting the same installation with the "all" configuration (e.g. "./run.sh -c all") doesn't start as smoothly ... Right in the beginning of the server.log file it starts with:
2010-02-22 17:29:02,592 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Real: name=vfsfile:/opt/jboss-5.1.0/server/all/deployers/jbossws.deployer/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying: vfsfile:/opt/jboss-5.1.0/server/all/deployers/jbossws.deployer/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:136)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.internalDeploy(AbstractRealDeployerWithInput.java:102)
at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:78)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalArgumentException: Exception loading class for ScopeKey addition.
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:67)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
... 34 more
Caused by: java.lang.ClassNotFoundException: org.jboss.wsf.spi.util.KernelLocator from BaseClassLoader@477b4e{VFSClassLoaderPolicy@f0691c{name=vfsfile:/opt/jboss-5.1.0/server/all/deployers/jbossws.deployer/ domain=ClassLoaderDomain@ed32c4{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.bootstrap.NoAnnotationURLClassLoader@118f375}
Because of this error listed above, JBoss can't deploy the mentioned EAR file (which worked nicely in "default").
The root cause "java.lang.ClassNotFoundException: org.jboss.wsf.spi.util.KernelLocator" catched my attention and it turned out that no JAR file on my system did contain the searched-for class. Interestingly, JBossWS 3.2.0 contains the missing class in "jbossws-spi.jar". Putting this one single class from jbossws-spi.jar (version 3.2.0) to jbossws-spi.jar (version 3.2.2) lead to another missing class: org.jboss.wsf.spi.metadata.j2ee.EJBArchiveMetaData$PublishLocationAdapter.
There I stopped and searched the internet with no usable result.
Do you guys have the same issue? Any suggestion on a resolution?
Any feedback appreciated!!
With best regards,
Michael.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/527657#527657
16 years, 2 months