[JBoss Tools] - Notes about Tycho on JBoss Tools
by Max Andersen
Max Andersen [http://community.jboss.org/people/max.andersen%40jboss.com] modified the document:
"Notes about Tycho on JBoss Tools"
To view the document, visit: http://community.jboss.org/docs/DOC-15095
--------------------------------------------------------------
h2. History
Devox 2009 - Max made first weird attempt at creating a scala script to generate pom, but bugs in Tycho and cyclic dependencies made it impossible to do "the easy way"
EclipseCon 2010 - Tycho 0.8 came out and we had a hack-a-thon to try break our monolith build.
h2. Status
https://svn.jboss.org/repos/jbosstools/branches/modular_build https://svn.jboss.org/repos/jbosstools/branches/modular_build contains the current work.
Has a parent-pom.xml for setting up Tycho and repositories.
Has scala script genpom.scala which currently automagically generates the proper pom.xml's based on our standard jboss tools plugin layot. Eventually these should be materialized and committed but for now it allows for rapid prototyping until we got it all working.
The build requires maven 3.
After doing scala genpom.xml you should (in theory) be able to run mvn install in any level. Right now only plugins/features works consistently :)
h2. Tidbits
Tycho uses surefire which picks up unittests which has "Test" somewhere in the name. Causing problems since we got Tests that aren't tests and AllTests which includes subtests.
What Maven group id should we be using ? Right now org.jboss.tools.* is the base.
How do we ensure the version in manifest.mf etc. are in sync with reality ? Some way for us to compare against latest JBDS/JBT 3 to ensure at least in sync ?
vpe.feature seem to be dead - had to remove xulrunner.vpe features. Seem all is in richfaces feature as opposed to be split up.
richfaces included hibernate xml editing features causing cyclic dependency between hibernate and vpe. For now hibernate drags in the xml editing; should probably be separated out in separate hibernate feature.
Right now we seem to run against the set of dependencies we explicitly have in our tests - which is great; but need to find a way to run all the tests against what will actually become the full IDE.
After fixing all dependency issues so Tycho would build (it seem to be more picky about ranges than PDE but we had stale version numbers in manifest headers and dependencies so it could just as well be our "fault") the memory usage goes through the roof for the uber-build. Doing mvn clean install for all failed even with 1024M. I believe that is caused by some bug in Tycho trying to keep fetching dependencies. Running with mvn -o (offline) seems to work fine after running it individually for sub modules to fetch their dependencies.
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15095]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years
[JBoss Tools] - Notes about Tycho on JBoss Tools
by Max Andersen
Max Andersen [http://community.jboss.org/people/max.andersen%40jboss.com] modified the document:
"Notes about Tycho on JBoss Tools"
To view the document, visit: http://community.jboss.org/docs/DOC-15095
--------------------------------------------------------------
h2. History
Devox 2009 - Max made first weird attempt at creating a scala script to generate pom, but bugs in Tycho and cyclic dependencies made it impossible to do "the easy way"
EclipseCon 2010 - Tycho 0.8 came out and we had a hack-a-thon to try break our monolith build.
h2. Status
https://svn.jboss.org/repos/jbosstools/branches/modular_build https://svn.jboss.org/repos/jbosstools/branches/modular_build contains the current work.
Has a parent-pom.xml for setting up Tycho and repositories.
Has scala script genpom.scala which currently automagically generates the proper pom.xml's based on our standard jboss tools plugin layot. Eventually these should be materialized and committed but for now it allows for rapid prototyping until we got it all working.
The build requires maven 3.
After doing scala genpom.xml you should (in theory) be able to run mvn install in any level. Right now only plugins/features works consistently :)
h2. Tidbits
Tycho uses surefire which picks up unittests which has "Test" somewhere in the name. Causing problems since we got Tests that aren't tests and AllTests which includes subtests.
What Maven group id should we be using ? Right now org.jboss.tools.* is the base.
How do we ensure the version in manifest.mf etc. are in sync with reality ? Some way for us to compare against latest JBDS/JBT 3 to ensure at least in sync ?
vpe.feature seem to be dead - had to remove xulrunner.vpe features. Seem all is in richfaces feature as opposed to be split up.
richfaces included hibernate xml editing features causing cyclic dependency between hibernate and vpe. For now hibernate drags in the xml editing; should probably be separated out in separate hibernate feature.
Right now we seem to run against the set of dependencies we explicitly have in our tests - which is great; but need to find a way to run all the tests against what will actually become the full IDE.
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15095]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years
Re: [jboss-user] [jBPM] - jBPM 4.3 starting a sub-process after a state node will fail
by Tun Mang
Tun Mang [http://community.jboss.org/people/tunmang] replied to the discussion
"jBPM 4.3 starting a sub-process after a state node will fail"
To view the discussion, visit: http://community.jboss.org/message/535294#535294
--------------------------------------------------------------
Hi Maciej:
Thanks a lot for your prompt assistance.
Attached is our standalone utility application's source code (we're not running from bpm console). Our test results are
(1) If run the utility with the following steps, it is OK (the sub-process started OK):
%> ....WfeUtility -deploy SubZzA.jpdl.xml
%> ....WfeUtility -all SimSubProc
(2) But if run it with the following steps, it throws exceptions:
%> ....WfeUtility -deploy SubZzA.jpdl.xml
%> ....WfeUtility -start SimSubProc
%> ....WfeUtility -signal SimSubProc.420001
14:59:10,564 SEV | [JDBCExceptionReporter] Cannot add or update a child row:
a foreign key constraint fails (`jbpm_4_3/jbpm4_execution`,
CONSTRAINT `FK_EXEC_SUBPI` FOREIGN KEY (`SUBPROCINST_`)
REFERENCES `jbpm4_execution` (`DBID_`))
### EXCEPTION ###########################################
14:59:10,564 SEV | [AbstractFlushingEventListener]
Could not synchronize database state with session
org.hibernate.exception.ConstraintViolationException:
could not update: [org.jbpm.pvm.internal.model.ExecutionImpl#420001]
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71)
......
Is it something related to our jBPM's configuration file(s) ? Or something else ? Please remove the package name (at the first line) in my source code when you try it.
Thanks a lot in advance.
Tun Mang
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535294#535294]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years
Re: [jboss-user] [Performance Tuning] - Slow JVM memory leak
by Jon Walton
Jon Walton [http://community.jboss.org/people/jw550] replied to the discussion
"Slow JVM memory leak"
To view the discussion, visit: http://community.jboss.org/message/535293#535293
--------------------------------------------------------------
I have finally found a workaround, using the standard OpenJDK that comes with Centos 5: java-1.6.0-openjdk-1.6.0.0-1.7.b09.el5. Using this JDK fixes the leak completely. VIRT size stabilizes at 1833M, which is exactly what I would expect. So I have no idea if this version of OpenJDK contains a fix, or the newer commercial JDKs from Sun contain a regression - as I still see the problem with JDK 6 update 19.
The crazy part is that no one else seems to have had such a problem. My application is rather busy - up to 50 transactions/second, but it still confounds that no one else seems to see this native leak. Anyway, thanks for your replies. I would still like to figure out what is going on, but for now, I will just be happy I have found a way to stabilize my cluster.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535293#535293]
Start a new discussion in Performance Tuning at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years
[JBoss Web Services] - Jboss Native - EJB based Webservice top down approach
by Sagar Sahasrabudhe
Sagar Sahasrabudhe [http://community.jboss.org/people/sagarps] created the discussion
"Jboss Native - EJB based Webservice top down approach"
To view the discussion, visit: http://community.jboss.org/message/535292#535292
--------------------------------------------------------------
Hello,
I was trying top down approach for generating EJB based webservice, using Jboss Native stack.
Generated the stubs using wsconsume command.
created EJB and web project in eclipse (copied the stubs and defined HelloServiceImpl) and structure as follows
EAR
- EJB
- src
HelloServiceImpl
HelloServicePort
- META-INF
wsdl
HelloService.wsdl
- WEB
- WebContent
META-INF
wsdl
HelloService.wsdl
WEB-INF
web.xml (defined servlet entry for HelloService)
HelloServiceImpl defined with annotations. Here i have to use the wsdl which i had defined so i am having the wsdlLocation.
@Stateless
@javax.jws.WebService(
name = "HelloServicePortImpl",
endpointInterface="com.mytest.test.businessservice.helloservice.facade.HelloServicePort",
targetNamespace = " http://facade.helloService.businessService.test.mytest.com/ http://facade.helloService.businessService.test.mytest.com/",
portName="HelloServicePort",
serviceName="HelloService",
wsdlLocation="META-INF/wsdl/HelloService.wsdl")
@TransactionManagement(TransactionManagementType.CONTAINER)
When i deploy this ear in jboss with native, it is not able to locate the wsdl in web project, but able to locate in EJB project.
(Note: But same EAR works fine on Jboss with Metro)
17:18:43,396 INFO [WSDLFilePublisher] WSDL published to: file:/C:/Architecture_POC/jboss-5.1.0.GA/server/default/data/wsdl/NewHelloEAR.ear/NewHelloEJB.jar/HelloService.wsdl
17:18:43,443 INFO [SessionSpecContainer] Stopping jboss.j2ee:ear=NewHelloEAR.ear,jar=NewHelloEJB.jar,name=HelloServicePortImpl,service=EJB3
17:18:43,443 INFO [EJBContainer] STOPPED EJB: com.starwood.test.businessservice.helloservice.facade.HelloServicePortImpl ejbName: HelloServicePortImpl
17:18:43,505 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/C:/Architecture_POC/jboss-5.1.0.GA/server/default/deploy/NewHelloEAR.ear/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/C:/Architecture_POC/jboss-5.1.0.GA/server/default/deploy/NewHelloEAR.ear/NewHelloWebRouter.war/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)
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.doInstallParentFirst(DeployersImpl.java:1210)
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.hotdeploy.HDScanner.scan(HDScanner.java:362)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:146)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:170)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.jboss.ws.WSException: Invalid wsdlFile 'vfszip:/C:/Architecture_POC/jboss-5.1.0.GA/server/default/deploy/NewHelloEAR.ear/NewHelloWebRouter.war/META-INF/wsdl/HelloService.wsdl', expected in: WEB-INF/wsdl/
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.getPublishLocation(WSDLFilePublisher.java:373)
at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:103)
at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.start(PublishContractDeploymentAspect.java:50)
at org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer.internalDeploy(WSDeploymentAspectDeployer.java:107)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
... 25 more
17:18:43,505 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS IN ERROR: Name -> Error
vfszip:/C:/Architecture_POC/jboss-5.1.0.GA/server/default/deploy/NewHelloEAR.ear/ -> org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/C:/Architecture_POC/jboss-5.1.0.GA/server/default/deploy/NewHelloEAR.ear/NewHelloWebRouter.war/
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/C:/Architecture_POC/jboss-5.1.0.GA/server/default/deploy/NewHelloEAR.ear/" is in error due to the following reason(s): org.jboss.ws.WSException: Invalid wsdlFile 'vfszip:/C:/Architecture_POC/jboss-5.1.0.GA/server/default/deploy/NewHelloEAR.ear/NewHelloWebRouter.war/META-INF/wsdl/HelloService.wsdl', expected in: WEB-INF/wsdl/
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:146)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:170)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
Did anyone faced the same problem?
I tried to place the wsdls in WEB-INF directory as mentioned in above exception stack trace, but no success.
How do we put a common wsdl across EJB and Web project (as defined in wsdlLocation)?
Thanks,
Sagar
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/535292#535292]
Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years
[JBoss Tools] - Notes about Tycho on JBoss Tools
by Max Andersen
Max Andersen [http://community.jboss.org/people/max.andersen%40jboss.com] modified the document:
"Notes about Tycho on JBoss Tools"
To view the document, visit: http://community.jboss.org/docs/DOC-15095
--------------------------------------------------------------
h2. History
Devox 2009 - Max made first weird attempt at creating a scala script to generate pom, but bugs in Tycho and cyclic dependencies made it impossible to do "the easy way"
EclipseCon 2010 - Tycho 0.8 came out and we had a hack-a-thon to try break our monolith build.
h2. Status
https://svn.jboss.org/repos/jbosstools/branches/modular_build https://svn.jboss.org/repos/jbosstools/branches/modular_build contains the current work.
Has a parent-pom.xml for setting up Tycho and repositories.
Has scala script genpom.scala which currently automagically generates the proper pom.xml's based on our standard jboss tools plugin layot. Eventually these should be materialized and committed but for now it allows for rapid prototyping until we got it all working.
The build requires maven 3.
After doing scala genpom.xml you should (in theory) be able to run mvn install in any level. Right now only plugins/features works consistently :)
h2. Tidbits
Tycho uses surefire which picks up unittests which has "Test" somewhere in the name. Causing problems since we got Tests that aren't tests and AllTests which includes subtests.
What Maven group id should we be using ? Right now org.jboss.tools.* is the base.
How do we ensure the version in manifest.mf etc. are in sync with reality ? Some way for us to compare against latest JBDS/JBT 3 to ensure at least in sync ?
vpe.feature seem to be dead - had to remove xulrunner.vpe features. Seem all is in richfaces feature as opposed to be split up.
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15095]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
14 years