[JBoss Microcontainer Users] - Re: Confused about POJO service
by karypid
Would that be packaged in a JAR for JBoss to pick it up?
My current test (which does not get activated) is a JAR with one class and one interface (the interface defines the start/stop methods) as follows:
public class MyServiceImpl implements MyService {
| private Logger logger;
|
| public void start() {
| logger = LoggerFactory.getLogger(MyServiceImpl.class);
| logger.info("has been started");
| }
|
| public void stop() {
| logger.info("has been shut down");
| logger = null;
| }
| }
It contains a META-INF/my-service-beans.xml as follows:
<?xml version="1.0" encoding="UTF-8"?>
| <deployment xmlns="urn:jboss:bean-deployer:2.0">
| <bean name="MyService" class="test.MyServiceImpl" />
| </deployment>
I drop it into the deploy folder (archived, not exploded) but nothing happens.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259343#4259343
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259343
15 years, 3 months
[JBoss Messaging Users] - Performance issues after switching from mq to jboss messagin
by luuzz
For few days now, i'm working on switching from mq to jboss messaging on jboss 4.2.0. I successfully started the server with jboss messaging without any errors and messages are processed by the mdbs.
So yesterday we did the same in the production environment but unfortunately customers are complaining that the web application is too slow although it was early in the morning with not much activity.
When we switched back to mq everything worked fine. Seems like the problem is messaging. we cheched that all the connections are closed normally. I noticed that we get many logs like that
| 2009-10-08 09:06:02,722 DEBUG [org.jboss.remoting.Client] starting callback Connector: InvokerLocator [bisocket://84.246.229.70:1724524841/callback?serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper&isCallbackServer=true&callbackServerProtocol=bisocket&datatype=jms&guid=2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6we&callbackServerHost=84.246.229.70&callbackServerPort=1724524841&clientMaxPoolSize=1&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper]
| 2009-10-08 09:06:02,722 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SocketServerInvoker[UNINITIALIZED] setting pingFrequency to 214748364
| 2009-10-08 09:06:02,722 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SocketServerInvoker[UNINITIALIZED] setting pingWindowFactor to 10
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] did not find server socket factory configuration as mbean service or classname. Creating default server socket factory.
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] created server socket factory javax.net.DefaultServerSocketFactory@10efd7c
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.transport.Connector] org.jboss.remoting.transport.Connector@ce79ab started
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.ServerInvoker] ServerInvoker (SocketServerInvoker[UNINITIALIZED]) added client callback handler CallbackManager[1ced81d] with session id of 2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf and callback handle object of null.
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@196046f from registry
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] Session id for callback handler is 2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] ServerInvokerCallbackHandler[2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf] using callbackTimeout value 10000
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] DefaultCallbackErrorHandler[UNITIALIZED] setting server invoker to SocketServerInvoker[127.0.0.1:4457]
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] DefaultCallbackErrorHandler[SocketServerInvoker[127.0.0.1:4457]] setting callback handler to ServerInvokerCallbackHandler[2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf]
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] adding callback handler ServerInvokerCallbackHandler[2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf]
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] found calllback handler for remoting session ...-g0jaad7m-6wc UID=2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc
| 2009-10-08 09:06:02,724 DEBUG [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] registered connection ConnectionEndpoint[iw6-o7daaj0g-1-byjvoi0g-cdp89-y1d6u6c2] as ...-g0jaad7m-6wc
| 2009-10-08 09:06:02,725 DEBUG [org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was available for Q_PENDING_MESSAGE_OUT, using default security config
| 2009-10-08 09:06:02,726 DEBUG [org.jboss.remoting.ServerInvoker] Thread pool class supplied is not an object name.
| 2009-10-08 09:06:02,731 DEBUG [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] unregistered connection ConnectionEndpoint[iw6-o7daaj0g-1-byjvoi0g-cdp89-y1d6u6c2] with remoting session ID ...-g0jaad7m-6wc
| 2009-10-08 09:06:02,731 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] removing callback handler ServerInvokerCallbackHandler[2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf]
| 2009-10-08 09:06:02,731 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@78c932 from registry
| 2009-10-08 09:06:02,731 DEBUG [org.jboss.remoting.ServerInvoker] ServerInvoker (SocketServerInvoker[UNINITIALIZED]) removing client callback handler with session id of 2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7m-6wc+2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf.
| 2009-10-08 09:06:02,731 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] unrecognized listener ID: 2c6u6d1y-98pdc-g0iovjyb-1-g0jaad7o-6wf
| 2009-10-08 09:06:02,731 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.local.LocalClientInvoker@1e0f1db from registry
| 2009-10-08 09:06:02,731 DEBUG [org.jboss.remoting.ServerInvoker] SocketServerInvoker[UNINITIALIZED] stopped
|
I wonder if it doesn't have anything to do with this line : bisocket://84.246.229.70:1724524841
may be it should be 127.0.0.1 instead.
Any Thought ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259342#4259342
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259342
15 years, 3 months
[EJB 3.0 Users] - Re: Stateful session beans don't keep state !!!
by daziplqa
Thank, I get it.
So, You mean to be able to use the statefullness of statefull session beans, I should keep a single instance of the bean.
But, If i use a state**less** bean, and i kept a single instance from it while setting the bean data, It should save the same date.
In other words, If I have changed the constructor above to a static initialize block, then change the stateFul bean to a stateLess bean, I will get code will still works, I just tried it.
So, What is the story behind that?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259340#4259340
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259340
15 years, 3 months
[jBPM Users] - jPDL decision or fork?
by cash1981
Hi.
I am quite new to jBPM and wondering what I should in the following example.
This is the snippet of the jpdl file:
| <task-node name="review">
| <event type="node-enter">
| <action expression="#{attachmentHandler.setupAttachments}"></action>
| <action expression="#{templateAttachmentHandler.setupTemplateAttachments}"></action>
| </event>
|
| <task name="10-reviewInput" swimlane="handlingOfficer"></task>
| <task name="20-reviewAttachment" swimlane="handlingOfficer"></task>
| <task name="30-rulingAssessment" swimlane="handlingOfficer"></task>
|
| <transition name="next" to="permit"></transition>
| </task-node>
|
| <task-node name="permit">
| <task name="40-ruling" swimlane="handlingOfficer"></task>
| <task name="50-sendPermit" swimlane="handlingOfficer"></task>
| <transition name="denied" to="denied"></transition>
| <transition name="next" to="end"></transition>
| </task-node>
|
In the task <task name="30-rulingAssessment" swimlane="handlingOfficer"></task>
The user handlingOfficer has the option to do something. If he does A, I would like to design in JBPM "skip 40-ruling and go straight to 50-sendPermit", and if he choose option B in 30-rulingAssessment, I want to have the same behaviour as modeled.
So my question is, how can I do this? Should I create a fork somehow from rulingAssessment or maybe just a decision node?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259328#4259328
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259328
15 years, 3 months