[EJB3] - Failed to acquire the pool semaphore in empty pool
by Garry Dias
Garry Dias [http://community.jboss.org/people/garrydias] created the discussion
"Failed to acquire the pool semaphore in empty pool"
To view the discussion, visit: http://community.jboss.org/message/625367#625367
--------------------------------------------------------------
Hello .. I have a similar issue but in jboss 5.1 using ejb 3.0
My clustered app process thousands requests but I have problems in only one node.
My bean is annotated with StrictMaxPool=100 without strictTimeout. Sometimes the max pool size is reached and the incoming requests (new bean instances creation in the pool) are blocked with *Failed to acquire the pool semaphore, strictTimeout=-1*. Until now it´s an application regular behavior.
When beans creation requests decreases my ejb blocks new instances creation =/ and *Failed to acquire the pool semaphore, strictTimeout=-1* occurs all the time. It´s like the pool is still full but in JMX-CONSOLE (domain j2ee, service=EJB3) and accessing MyWorkerBean link, the AvailableCount attribute is always 0 (until in other clustered node this attribute increases and decreases normally) and worse: no bean is instantiated anymore. My pool is empty but the container can´t instatiate MyWorkerBeans anymore. Why???
I´ll appreciate any help
thanks
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/625367#625367]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months
[jBPM] - Switch from localhost to hostname
by Tobias Wittur
Tobias Wittur [http://community.jboss.org/people/tob1as] created the discussion
"Switch from localhost to hostname"
To view the discussion, visit: http://community.jboss.org/message/625165#625165
--------------------------------------------------------------
Hi,
I am trying to get jBPM to listen on my hostname rather than the localhost.
I found this:
> *+JBoss listens on localhost only by default. To make it listen on the hostname also, start it with the -b flag:at+*
> *+run.bat -b 0.0.0.0
> +*
>
> *+this will make it listen on every available address on that machine. To limit to a single address, replace 0.0.0.0 with your IP address.+*
>
> *+http://stackoverflow.com/questions/1136254/access-jboss-tomcat-web-application-from-remote-computer http://stackoverflow.com/questions/1136254/access-jboss-tomcat-web-applic...
The build file contains:
> <target name="start.jboss">
> <property name="jboss.full.path.win" location="*${jboss.home}/bin/run.bat*"/>
> <exec spawn="yes" osfamily="windows" executable="*${jboss.full.path.win}*">
> * <arg value="-b"/>
> <arg value="${jboss.bind.address}"/>*
> ...
> </exec>
The variable jboss.bind.address looks as follows:
> <property name="jboss.bind.address" value="*localhost*"/>
So I replaced localhost with my IP, but still no success.
Am I missing something?
I also started the IIS in order to test it and I could get through, so I guess it shouldnt be a firewall issue.
Best regards,
tobias
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/625165#625165]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months
[jBPM] - Incorrect Gateway diverge and converge operations in jBPM 5
by shashi mhatre
shashi mhatre [http://community.jboss.org/people/khalipili] created the discussion
"Incorrect Gateway diverge and converge operations in jBPM 5"
To view the discussion, visit: http://community.jboss.org/message/581930#581930
--------------------------------------------------------------
I am using below sample flow in my test. it contains three human task. once the process process is started it execute successfully till human task creation. As the first gateway diverge is of type "AND" it creates two task as shown below. I can view these task in jbpm-console. now once i login as user "Shashi" and complete the first task, As the next gateway converge is of type "XOR", the flow proceeds further and create the next task for user "Shashi".
As process have proceed further till gateway converge, jbpm should have remove the task for user "kris". but jbpm still shows the task for user "kris".
this seems to be a error in jbpm process execution.
next once user "shashi" completes the human task, process execution completes but throws below error. it seems that human task handler tries to abort the "kris" task which should have be aborted prior (at gateway converge).
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
java.lang.IllegalArgumentException: attempt to create merge event with null entity
at org.hibernate.event.MergeEvent.<init>(MergeEvent.java:60)
at org.hibernate.event.MergeEvent.<init>(MergeEvent.java:43)
at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:688)
at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:692)
at org.hibernate.ejb.AbstractEntityManagerImpl.merge(AbstractEntityManagerImpl.java:235)
at org.drools.persistence.processinstance.JPAWorkItemManager.abortWorkItem(JPAWorkItemManager.java:124)
at org.drools.command.runtime.process.AbortWorkItemCommand.execute(AbortWorkItemCommand.java:56)
at org.drools.command.runtime.process.AbortWorkItemCommand.execute(AbortWorkItemCommand.java:29)
at org.drools.persistence.session.SingleSessionCommandService.execute(SingleSessionCommandService.java:274)
at org.drools.command.impl.CommandBasedStatefulKnowledgeSession$1.abortWorkItem(CommandBasedStatefulKnowledgeSession.java:149)
at com.sample.util.CommandBasedWSHumanTaskHandler$GetCompletedTaskResponseHandler.execute(CommandBasedWSHumanTaskHandler.java:257)
at org.jbpm.task.service.TaskClientHandler.messageReceived(TaskClientHandler.java:81)
at org.jbpm.task.service.mina.MinaTaskClientHandler.messageReceived(MinaTaskClientHandler.java:47)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$TailFilter.messageReceived(DefaultIoFilterChain.java:713)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:793)
at org.apache.mina.filter.codec.ProtocolCodecFilter$ProtocolDecoderOutputImpl.flush(ProtocolCodecFilter.java:375)
at org.apache.mina.filter.codec.ProtocolCodecFilter.messageReceived(ProtocolCodecFilter.java:229)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$1200(DefaultIoFilterChain.java:46)
at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.messageReceived(DefaultIoFilterChain.java:793)
at org.apache.mina.core.filterchain.IoFilterAdapter.messageReceived(IoFilterAdapter.java:119)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextMessageReceived(DefaultIoFilterChain.java:434)
at org.apache.mina.core.filterchain.DefaultIoFilterChain.fireMessageReceived(DefaultIoFilterChain.java:426)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:638)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:598)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:587)
at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$400(AbstractPollingIoProcessor.java:61)
at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:969)
at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[2011:01:19 17:01:78:exception] Uncaught exception on client
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
. http://community.jboss.org/servlet/JiveServlet/showImage/2-581930-11171/S... http://community.jboss.org/servlet/JiveServlet/downloadImage/2-581930-111...
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/581930#581930]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months
[EJB3] - @Service Annotation in JBoss6 not solved
by Carmen Teich
Carmen Teich [http://community.jboss.org/people/catares] created the discussion
"@Service Annotation in JBoss6 not solved"
To view the discussion, visit: http://community.jboss.org/message/625288#625288
--------------------------------------------------------------
Hello,
I have a Bean wich have the Annotations: (using JBoss6.1Final)
import org.jboss.ejb3.annotation.Depends;
import org.jboss.ejb3.annotation.Service;
@Service(objectName="eDesk:service=IndexingService")
@Depends("jboss.jca:service=ConnectionFactoryDeployer")
public class SearchEngineImpl extends ServiceMBeanSupport implements SearchEngine {
...
}
My problem is, that JBoss the two services
(1) eDesk:service=IndexingService and
(2) jboss.jca:service=ConnectionFactoryDeployer
are not installed (not seen at JMX-Console)
The service jboss.jca:service=ConnectionFactoryDeployer is defined in the file: jbossjca-service.xml
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- JBoss JCA Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- $Id: jbossjca-service.xml 37786 2005-11-02 20:35:46Z adrian $ -->
<!--
| This contains configuration for the RARDeployer
and some xsl based deployers.
-->
<server>
<!-- ==================================================================== -->
<!-- JBossCX setup, for J2EE connector architecture support -->
<!-- The RARDeployer is needed only until xslt based deployment is written.-->
<!-- ==================================================================== -->
<mbean code="org.jboss.util.threadpool.BasicThreadPool"
name="jboss.jca:service=WorkManagerThreadPool">
<!-- The name that appears in thread names -->
<attribute name="Name">WorkManager</attribute>
<!-- The maximum amount of work in the queue -->
<attribute name="MaximumQueueSize">1024</attribute>
<!-- The maximum number of active threads -->
<attribute name="MaximumPoolSize">100</attribute>
<!-- How long to keep threads alive after their last work (default one minute) -->
<attribute name="KeepAliveTime">60000</attribute>
</mbean>
<mbean code="org.jboss.resource.work.JBossWorkManager"
name="jboss.jca:service=WorkManager">
<depends optional-attribute-name="ThreadPoolName">jboss.jca:service=WorkManagerThreadPool</depends>
<depends optional-attribute-name="XATerminatorName">jboss:service=TransactionManager</depends>
</mbean>
<mbean code="org.jboss.resource.deployment.RARDeployer"
name="jboss.jca:service=RARDeployer">
<depends optional-attribute-name="WorkManagerName">jboss.jca:service=WorkManager</depends>
<depends optional-attribute-name="XATerminatorName">jboss:service=TransactionManager</depends>
</mbean>
<mbean code="org.jboss.deployment.XSLSubDeployer" name="jboss.jca:service=ConnectionFactoryDeployer">
<attribute name="DdSuffix">-ds.xml</attribute>
<attribute name="EnhancedSuffixes">300:-ds.xml</attribute>
<attribute name="XslUrl">stylesheets/ConnectionFactoryTemplate.xsl</attribute>
<attribute name="ValidateDTDs">false</attribute>
</mbean>
<!--
| The CachedConnectionManager is used partly to relay started UserTransactions to
| open connections so they may be enrolled in the new tx.
-->
<mbean code="org.jboss.resource.connectionmanager.CachedConnectionManager"
name="jboss.jca:service=CachedConnectionManager">
<depends optional-attribute-name="TransactionManagerServiceName">jboss:service=TransactionManager</depends>
<!-- Enable connection close debug monitoring -->
<attribute name="Debug">true</attribute>
</mbean>
</server>
The Server install only two services from this xml-file, all other services wehre not installed.
Please help me..I need this services!!!!!!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/625288#625288]
Start a new discussion in EJB3 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months
[jBPM] - passing data to nodes
by Darryl Youngblood
Darryl Youngblood [http://community.jboss.org/people/d.y.] created the discussion
"passing data to nodes"
To view the discussion, visit: http://community.jboss.org/message/624808#624808
--------------------------------------------------------------
Hey guys,
I'm not sure if I got it right. So far i believe there are two ways to pass information to other nodes.
1. In the executeWorkItem method of a custom workItemHandler class I can put information in a map and use WorkItemManager.completeWorkItem(workItemId, Map<String, Object>); to pass the information to the next node.
2. I could use globals to store information inside
Is this right or am I wrong?
The problems I encounter are:
1. I don't know how to retrieve that map from that workItemManager especially when the next node is a gateway
2. When I use globals it is always stored as Object which is kinda unhandy
ty in advance
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/624808#624808]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months
