[JBoss JIRA] Created: (JBMESSAGING-1701) Server closes connections from alive clients
by Bijith Kumar (JIRA)
Server closes connections from alive clients
--------------------------------------------
Key: JBMESSAGING-1701
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1701
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 2.0.0.beta4
Environment: Windows Vista-32 bit
Reporter: Bijith Kumar
Assignee: Tim Fox
Priority: Critical
Attachments: Sender.java
As per the JBM documentation, if a client is idle (i.e. not sending/receiving any message), it will automatically send "ping" packets periodically to prevent the server from closing it down. So my understanding is that, the server should not close the connection as long as client program is running (e.g. just looping in an empty while loop). It seems this pinging is not happening always. Because, in my case, client program sends some messages and sits idle for 5 min and server closes the connection after 2-3 minutes saying "no ping received". Please see the complete server message below.
[main] 17:49:54,850 WARNING [org.jboss.messaging.jms.server.impl.JMSServerManagerImpl] Binding for
java:/XAConnectionFactory already exists
[main] 17:49:54,949 INFO [org.jboss.messaging.core.server.impl.MessagingServerImpl] JBoss Messaging
Server version 2.0.0.BETA4 (maggot, 104) started
[Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:04,158 WARNING [org.jboss.messaging.core.rem
oting.impl.RemotingConnectionImpl] Connection failure has been detected Did not receive p
lient. It is likely a client has exited or crashed without closing its connection, or the network be
tween the server and client has failed. The connection will now be closed.:3
[Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:04,163 WARNING [org.jboss.messaging.core.ser
ver.impl.ServerSessionImpl] Client connection failed, clearing up resources for session 4
ba-11de-93a5-001aa035dde5
[Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:04,163 WARNING [org.jboss.messaging.core.ser
ver.impl.ServerSessionImpl] Cleared up resources for session 4dd07287-81ba-11de-93a5-001a
[Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:06,414 WARNING [org.jboss.messaging.core.rem
oting.impl.RemotingConnectionImpl] Connection failure has been detected Did not receive p
lient. It is likely a client has exited or crashed without closing its connection, or the network be
tween the server and client has failed. The connection will now be closed.:3
[Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:06,414 WARNING [org.jboss.messaging.core.ser
ver.impl.ServerSessionImpl] Client connection failed, clearing up resources for session 4
ba-11de-93a5-001aa035dde5
[Thread-4 (group:JBM-scheduled-threads-25935701)] 18:00:06,415 WARNING [org.jboss.messaging.core.ser
ver.impl.ServerSessionImpl] Cleared up resources for session 4dae6b96-81ba-11de-93a5-001a
Attached is the simple JMS client class to reproduce the issue. It sends 5000 messages to the Queue and idles for 5 minutes (just loops in an empty while loop) before exiting. Please find test instructions below.
1) Update JMX_URL, HOST and PORT in the attached Sender.java file according to your env
2) Compile and execute Sender.java a couple of times
3) Observe that the Server closes connection after 2-3 minutes printing WARNING messages shown above. If you are not able to reproduce it this way, try sending more messages so that paging starts in server, that would definitely reproduce it. I was able to reproduce the issue both ways (i.e. paged or not paged).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (JBAS-6870) Error deploying JavaEE application which uses Ehcache
by Rainer Flicker (JIRA)
Error deploying JavaEE application which uses Ehcache
-----------------------------------------------------
Key: JBAS-6870
URL: https://jira.jboss.org/jira/browse/JBAS-6870
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-5.0.1.GA
Environment: JDK 1.5.0_11
JBoss AS 5.0.1.GA
Reporter: Rainer Flicker
Deploying a JavaEE application (EAR), which uses hibernate 3.3.1, JBoss Seam 2.1.1 and Ehcache 1.5.0 results in following error
(works with JBoss AS 4.2.3.GA):
2009-05-06 14:59:14,095 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=persistence.unit:unitName=asms.ear/asms.jar#asms state=Create
java.lang.IllegalArgumentException: Cache name cannot contain '/' characters.
at net.sf.ehcache.config.CacheConfiguration.setName(CacheConfiguration.java:163)
at net.sf.ehcache.Cache.setName(Cache.java:1721)
at net.sf.ehcache.CacheManager.addCache(CacheManager.java:632)
at net.sf.ehcache.hibernate.EhCacheProvider.buildCache(EhCacheProvider.java:90)
at org.hibernate.cache.impl.bridge.RegionFactoryCacheProviderBridge.buildEntityRegion(RegionFactoryCacheProviderBridge.java:96)
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:255)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1327)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:132)
at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:301)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
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.doInstallParentFirst(DeployersImpl.java:1178)
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:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
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:698)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (BPEL-308) Support variable initialization per OASIS BPEL 2.0 spec
by Aleksander Adamowski (JIRA)
Support variable initialization per OASIS BPEL 2.0 spec
-------------------------------------------------------
Key: BPEL-308
URL: https://jira.jboss.org/jira/browse/BPEL-308
Project: JBoss jBPM BPEL
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 GA
Reporter: Aleksander Adamowski
Assignee: Alejandro Guizar
OASIS Web Services Business Process Execution Language Version 2.0 specification, section 8.1, states that variables can be initialized upon definition:
"The syntax of the <variables> declaration is:
<variables>
<variable name="BPELVariableName"
messageType="QName"?
type="QName"?
element="QName"?>+
from-spec?
</variable>
</variables>
....
A variable can optionally be initialized by using an in-line from-spec. From-spec is defined in
section 8.4. Conceptually the in-line variable initializations are modeled as a virtual <sequence>
activity that contains a series of virtual <assign> activities, one for each variable being
initialized, in the order they are listed in the variable declarations. The virtual <assign>
activities each contain a single virtual <copy> whose from-spec is as given in the variable
initialization and the to-spec points to the variable being created.
[SA00026] Variable initialization logic contained in scopes that contain or whose children
contain a start activity MUST only use idempotent functions in the from-spec. The use of
idempotent functions allows for all the values for such variables to be pre-computed and re-used
on each process instance. "
The Eclipse BPEL Business Process Editor supports this - one can select a variable, and in its properties panel choose "Initialization" tab, then e.g. specify From = "Expression", Expression language = "Same as Process (XPath 1.0 in BPEL 2.0)" and input an expression.
Here's an example of such generated variable specification:
<bpws:variable name="myVariable">
<bpws:from>
<![CDATA[number(123)]]>
</bpws:from>
</bpws:variable>
Unfortunately, jBPM BPEL ignores initialization from spec:
DEBUG [org.jbpm.context.exe.VariableContainer] create variable 'myVariable' in 'TokenVariableMap10d7fa4' with value '[myVariable: null]'
This feature of BPEL spec should be supported.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
[JBoss JIRA] Created: (BPEL-244) Support for BPEL process instance monitoring in jBPM admin console
by Meghana Joglekar (JIRA)
Support for BPEL process instance monitoring in jBPM admin console
------------------------------------------------------------------
Key: BPEL-244
URL: http://jira.jboss.com/jira/browse/BPEL-244
Project: JBoss jBPM BPEL
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Engine
Reporter: Meghana Joglekar
Assigned To: Alejandro Guizar
One can currently run BPEL processes on jBPM engine and check the log files to see the runtime report. But this process is not efficient in monitoring how the process is doing, what processes are running, what went wrong when a fault occurred etc. It will be nice to have administration console to see this information. The administration console can then list the process instances that are running, show visual graph of the instance and for each node in the graph more information about it. ActiveBPEL and OracleBPEL both provide such consoles and they are great tools for administrators. It will be nice if it also provides 'delete' functionality for stalled processes or old processes. The list could go on but in its basic form, processes listing, process instance listing and then more information about them [instances] will be useful.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 11 months
test
by Bounced mail
The message was undeliverable due to the following reason(s):
Your message could not be delivered because the destination server was
unreachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.
Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.
Your message could not be delivered within 5 days:
Server 213.129.30.230 is not responding.
The following recipients did not receive this message:
<jboss-jira(a)lists.jboss.org>
Please reply to postmaster(a)lists.jboss.org
if you feel this message to be in error.
16 years, 11 months
