[JBoss Tools] - JBoss Knowledge Base Builder hangs up
by hd0815
hd0815 [https://community.jboss.org/people/hd0815] created the discussion
"JBoss Knowledge Base Builder hangs up"
To view the discussion, visit: https://community.jboss.org/message/831542#831542
--------------------------------------------------------------
Hi there.
It seems like JBoss Knowledge Base Builder hangs up repeatedly or is at least so slow that I think it hangs up. I haven't had this problem some time before and I'm not quite sure what causes this problem.Trying to cancel the invocation of the builder doesn't seem to have any effect. I have waited for about five minutes for the builder to come to an end. I have to kill the Java process via task manager in Windows.
I use Eclipse Juno Juno Service Release 2 Build 20130225-0426 and JBoss Tools 1.4.0.Final-v20130326-2027-B145. I have a huge workspace which might cause the builder to cause an overflow.
This problem occurs quite unsteady. I'll add the logs and my .ini file from Eclipse. Please let me know if I can provide more information.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/831542#831542]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months
[JBoss Messaging] - Can I configure JMS XA Recovery for use with Amazon EC2 auto-scaling in EAP 5.1.2?
by Stanley Tso
Stanley Tso [https://community.jboss.org/people/stso0001] created the discussion
"Can I configure JMS XA Recovery for use with Amazon EC2 auto-scaling in EAP 5.1.2?"
To view the discussion, visit: https://community.jboss.org/message/826014#826014
--------------------------------------------------------------
I am attempting to configure a cluster of JBoss EAP 5.1.2 nodes at Amazon EC2. My goal is to set up a template image so that I can use the nearly the same configuration when I add new nodes with Amazon auto-scaling. I am following the documentation at *https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/5/html-single/Messaging_User_Guide/index.html#recovery https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Appli... and I need clarification on what it is saying.
Let say that I add a new JBoss node using Amazon auto-scaling and I wish for this node to join the existing JBoss cluster, in particular JMS. Is it even possible for a new JMS node to dynamically appear in the cluster and participate in the JMS XA recovery process? My understanding of what the documentation says is that it is possible for a new JMS provider to be defined and added dynamically in "*server/all/deploy/messaging/hajndi-jms-ds.xml*" because this file is located in a directory watched by the hot deployment scanner. I would have to add the new provider (JMS node) to all of the existing JMS nodes in this particular configuration file. However, for new JMS nodes to participate in JMS XA recovery, would I have to also modify "*server/all/conf/jbossts-properties.xml*" to tell the recovery manager that there are new JMS nodes from which we must recover? Isn't this file statically loaded by each JBoss node and if so, does that mean I have to restart the existing JBoss JMS nodes to pick up this new configuration? That would defeat the purpose of auto-scaling in the first place, wouldn't it?
Am I on the right track here? Thank you in advance for your help!
Stan Tso
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/826014#826014]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months
[jBPM] - How to change console version for jbpm recompile
by Marco Burrafato
Marco Burrafato [https://community.jboss.org/people/ocramot] created the discussion
"How to change console version for jbpm recompile"
To view the discussion, visit: https://community.jboss.org/message/833506#833506
--------------------------------------------------------------
I wanted to make some specific changes in the jbpm console, relative to a project I'm working on, so I followed the guide here:
https://community.jboss.org/docs/DOC-18178 https://community.jboss.org/wiki/HowToBuildmodifyJbpm-consoleAndDeployItO...
Anyway I downloaded the jbpm 5.4 version (last stable nowadays). This version uses the console version 2.3.8.Final by default, so I downloaded the 2.3.9-SNAPSHOT version, to avoid conflicts.
Following the wiki, I compile the bpm-console code and then the jbpm code, taking care to follow the point 10 (search for "<version>2.3.8.Final</version>" and replace with "<version>2.3.9-SNAPSHOT</version>") in all the pom.xml files that I can find within the jbpm source directory. I find also some dependencies without the version specified; I suppose there is some "default version" defined somewhere, but I am unable to find it, so I add explicitly the version tag in those files.
Still, when I try to compile, I get the following:
[...]
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources' with basic configurator -->
[DEBUG] (f) buildFilters = []
[DEBUG] (f) encoding = UTF-8
[DEBUG] (f) escapeWindowsPaths = true
[DEBUG] (s) includeEmptyDirs = false
[DEBUG] (s) outputDirectory = C:\Users\ocramot\repository\edit_console\jbpm\jbpm-flow\target\classes
[DEBUG] (s) overwrite = false
[DEBUG] (f) project = MavenProject: org.jbpm:jbpm-flow:5.4.1-SNAPSHOT @ C:\Users\ocramot\repository\edit_console\jbpm\jbpm-flow\pom.xml
[DEBUG] (s) resources = [Resource {targetPath: null, filtering: false, FileSet {directory: C:\Users\ocramot\repository\edit_console\jbpm\jbpm-flow\src\main\resources, PatternSet [includes: {}, excludes: {}]}}]
[DEBUG] (f) session = org.apache.maven.execution.MavenSession@10ebe2f8
[DEBUG] (f) useBuildFilters = true
[DEBUG] (s) useDefaultDelimiters = true
[DEBUG] -- end configuration --
[DEBUG] properties used { [ ... ], bpm.console.version=2.3.8.Final, [ ... ]}
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[DEBUG] resource with targetPath null
[ ... ]
and so on for every sub-project (jbpm-flow-builder, jbpm-persistence-jpa, etc.)
and in fact, maven takes care to dowload and install in my local repository the 2.3.8.Final version, ignoring the 2.3.9.SNAPSHOT version already present there.
How can I resolve this? What pom files do I have to modify? What could I have missed? Is there a default version defined somewhere?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/833506#833506]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months
[JBoss Remoting] - Possible bug in "org.jboss.ejb.client.EjbClientContext"
by Sunil Dixit
Sunil Dixit [https://community.jboss.org/people/sunil_dixit] created the discussion
"Possible bug in "org.jboss.ejb.client.EjbClientContext""
To view the discussion, visit: https://community.jboss.org/message/833533#833533
--------------------------------------------------------------
jboss-ejb-client (*Version 1.0.18.Final and above*) has one bug (garbage collection related) in "*public void unregisterEJBReceiver(final EJBReceiver receiver)*" API.
This API uses "ExecutorService" to send close notification to registered listeners (if any) asynchronously.
Now if your InitialContext is eligible for garbage collection then it JVM calls RemoteContext.finalize() method which internally result into calling "*org.jboss.ejb.client.EJBReceiverContext.close()*" which triggers
"*org.jboss.ejb.client.EJBClientContext.unregisterEJBReceiver()*" .
Before "*org.jboss.ejb.client.EJBClientContext.unregisterEJBReceiver() "* gets executed "*org.jboss.ejb.client.EJBClientContext.ejbClientContextTasksExecutorService*" state is changed from RUNNING to TERMINATED i.e. ( runState is being set to 3) which result into "java.util.concurrent.RejectedExecutionException".
T*hreadPoolExecutor.addIfUnderMaximumPoolSize() API will always return false as " if (poolSize < maximumPoolSize && runState == RUNNING)" prevents to create new thread*.
Finally caller APIs gets following exception
java.util.concurrent.RejectedExecutionException
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.reject(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.execute(Unknown Source)
at java.util.concurrent.AbstractExecutorService.submit(Unknown Source)
at org.jboss.ejb.client.EJBClientContext.unregisterEJBReceiver(EJBClientContext.java:432)
at org.jboss.ejb.client.EJBReceiverContext.close(EJBReceiverContext.java:59)
at org.jboss.ejb.client.remoting.ChannelAssociation.notifyBrokenChannel(ChannelAssociation.java:404)
at org.jboss.ejb.client.remoting.ChannelAssociation.access$100(ChannelAssociation.java:59)
at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:118)
at org.jboss.ejb.client.remoting.ChannelAssociation$1.handleClose(ChannelAssociation.java:110)
at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:54)
at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:501)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:406)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:277)
at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:515)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:390)
at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:231)
at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:376)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:52)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
at org.jboss.naming.remote.client.HaRemoteNamingStore.closeAsync(HaRemoteNamingStore.java:385)
at org.jboss.naming.remote.client.NamingStoreCache.release(NamingStoreCache.java:113)
at org.jboss.naming.remote.client.NamingStoreCache$1.close(NamingStoreCache.java:98)
at org.jboss.naming.remote.client.RemoteContext.finalize(RemoteContext.java:199)
at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
at java.lang.ref.Finalizer.runFinalizer(Unknown Source)
at java.lang.ref.Finalizer.access$100(Unknown Source)
at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)
Below code in "org.jboss.ejb.client.EJBClientContext" is added into new versions and causing this problem
// we *don't* want to send these notification to listeners synchronously since the listeners can be any arbitrary
// application code and can potential block for a long time. So invoke the listeners asynchronously via our ExecutorService
final Collection<EJBClientContextListener> listeners = new ArrayList<EJBClientContextListener>(this.ejbClientContextListeners);
for (final EJBClientContextListener listener : listeners) {
this.ejbClientContextTasksExecutorService.submit(new Runnable() {
@Override
public void run() {
try {
listener.receiverUnRegistered(receiverContext);
} catch (Throwable t) {
// log and ignore
logger.debug("Exception trying to invoke EJBClientContextListener " + listener + " for EJB client context " + EJBClientContext.this + " on un-registertation of EJBReceiver " + receiver, t);
}
}
});
}
}
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/833533#833533]
Start a new discussion in JBoss Remoting at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months
[JBoss Web Services] - JBossWS wsconsume Maven plugin FAIL
by stephen b
stephen b [https://community.jboss.org/people/slbanal] created the discussion
"JBossWS wsconsume Maven plugin FAIL"
To view the discussion, visit: https://community.jboss.org/message/833531#833531
--------------------------------------------------------------
Hi,
I followed instructions here https://docs.jboss.org/author/display/JBWS/wsconsume https://docs.jboss.org/author/display/JBWS/wsconsume
But it seems there are dependency issues whenever i use the version of the plugin specified in the tutorial.
Which version of plugin should i use?
POM:
<project xmlns=" http://maven.apache.org/POM/4.0.0 http://maven.apache.org/POM/4.0.0" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation=" http://maven.apache.org/POM/4.0.0 http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>au.com.example.webservice</groupId>
<artifactId>test-ws</artifactId>
<version>0.0.1-SNAPSHOT</version>
<pluginRepositories>
<pluginRepository>
<id>JBOSS</id>
<name>JBoss Repository</name>
<url> https://repository.jboss.org/nexus/content/groups/public/ https://repository.jboss.org/nexus/content/groups/public/</url>
</pluginRepository>
</pluginRepositories>
<build>
<plugins>
<plugin>
<groupId>org.jboss.ws.plugins</groupId>
<artifactId>maven-jaxws-tools-plugin</artifactId>
<version>1.1.0.GA</version>
<configuration>
<wsdls>
<wsdl>src/main/java/resources/Example.wsdl</wsdl>
</wsdls>
<targetPackage>au.com.example.webservice</targetPackage>
<extension>true</extension>
<verbose>true</verbose>
<goalPrefix>wsconsume</goalPrefix>
</configuration>
<executions>
<execution>
<goals>
<goal>wsconsume</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.jboss.ws.cxf</groupId>
<artifactId>jbossws-cxf-client</artifactId>
<version>4.0.0.GA</version>
</dependency>
</dependencies>
</project>
Exact Maven logs:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.427s
[INFO] Finished at: Thu Aug 22 21:51:47 EST 2013
[INFO] Final Memory: 4M/15M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project test-ws: Could not resolve dependencies for project au.com.example.webservice:test-ws:jar:0.0.1-SNAPSHOT: Failure to find org.jboss.ws.cxf:jbossws-cxf-client:jar:4.0.0.GA in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project test-ws: Could not resolve dependencies for project au.com.example.webservice:test-ws:jar:0.0.1-SNAPSHOT: Failure to find org.jboss.ws.cxf:jbossws-cxf-client:jar:4.0.0.GA in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
at org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not resolve dependencies for project au.com.example.webservice:test-ws:jar:0.0.1-SNAPSHOT: Failure to find org.jboss.ws.cxf:jbossws-cxf-client:jar:4.0.0.GA in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:189)
at org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:185)
... 22 more
Caused by: org.sonatype.aether.resolution.DependencyResolutionException: Failure to find org.jboss.ws.cxf:jbossws-cxf-client:jar:4.0.0.GA in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:375)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:183)
... 23 more
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Failure to find org.jboss.ws.cxf:jbossws-cxf-client:jar:4.0.0.GA in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:358)
... 24 more
Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Failure to find org.jboss.ws.cxf:jbossws-cxf-client:jar:4.0.0.GA in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:230)
at org.sonatype.aether.impl.internal.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:204)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:427)
... 26 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExce...
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/833531#833531]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months
[jBPM] - JTA in jBPM5.4 on jBoss7.1.1 is inconsistent - Urgent help please
by Arif Mohammed
Arif Mohammed [https://community.jboss.org/people/arif.mohammed] created the discussion
"JTA in jBPM5.4 on jBoss7.1.1 is inconsistent - Urgent help please"
To view the discussion, visit: https://community.jboss.org/message/800174#800174
--------------------------------------------------------------
Hi All,
Iam doing a prototype to evaluate jBPM5 for using it in a web application. I have defined a simple process StartUseCase -> CheckDuplicateOperator -> PersistOperator -> EndUseCase.
In StartUseCase and EndUseCase activities Iam calling LocalTaskService to start and complete the user task respectively. I can't use HumanTask here due to some other reason. Following are the technology stack Iam using.
JBoss7.1.1 Application server
Spring MVC 3.0.5
Hibernate4
jBPM5.4.0.Final
*Problem:* When I create a persistable session I get the exception "*java.lang.IllegalStateException: BaseTransaction.rolback - ARJUNA01604: no transaction!*" When I inspect the stack trace further I see "*java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (JBPM.SYS_C0010966) violated*"
The above integrity constraint violation which is related to primary key in SESSIONINFO table is strange to me, as Iam not having any control over there and it is jBPM's responsibility to insert and update the session information. I also noticed the first line of exception some times during the end of my process, while it is updating the information in DB about the process and this behaviour is sporadic.
It is even strange to me that if I restart the jBoss Application server it works fine with out any exception huff... Am I doing any thing wrong here ? I have attached all of my handlers along with persistence.xml and spring configuration, your quick help is appreciated.
To look at the code you can start at OperatorController.saveOperator which is the trigger point for the process.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/800174#800174]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months