[jBPM Development] - How to stop NioProcessor-2 logging. [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
by uvijayreddy657
uvijayreddy657 [https://community.jboss.org/people/uvijayreddy657] created the discussion
"How to stop NioProcessor-2 logging. [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE"
To view the discussion, visit: https://community.jboss.org/message/715135#715135
--------------------------------------------------------------
In JBoss server always for every second the below is scrolling continuously. Because of this *server.log size is increasing till 400MB to 500MB*. Getting disk out of space error and also getting *java.net.SocketException : Too many open files.*
*How to stop this LoggingFilter.* Please suggest and advice.
2012-02-08 11:59:13,309 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:13,309 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:14,262 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:14,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:15,277 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,262 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:21,280 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,280 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,280 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:21,281 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:22,263 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:22,264 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,310 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:22,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:23,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:23,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
2012-02-08 11:59:25,266 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-3) IDLE
2012-02-08 11:59:25,283 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-1) IDLE
2012-02-08 11:59:25,311 INFO [org.apache.mina.filter.logging.LoggingFilter] (NioProcessor-2) IDLE
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/715135#715135]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 2 months
[JMX Development] - Deploying a .ear in domain mode (vs standalone) using remoting-jmx
by Guillaume Archambault
Guillaume Archambault [https://community.jboss.org/people/guillo] created the discussion
"Deploying a .ear in domain mode (vs standalone) using remoting-jmx"
To view the discussion, visit: https://community.jboss.org/message/811456#811456
--------------------------------------------------------------
Hi,
In JBoss AS7,
>From a client java program,
i'm using this: service:jmx:remoting-jmx://my_host_name:port to connect to either a standalone mode server or a domain mode server.
In standalone mode:
I can retreive the MBean jboss.as:deployment=myEar.ear, and then able to deploy, redeploy, undeploy or remove myEar.ear
This works great !
However,
In domain mode:
I have 3-4 ears deployed on this server, belonging to different server groups.
There is only a few MBeans (not interesting for deploying) availables, and mainly, no jboss.as:deployment=myEar.ear available, or any MBeans related to server-groups or cluster etc...
I'm thinking that there must be a xml configuration file (domain.xml,host.xml,....) somewhere to offer the wanted MBeans ?
Why standalone mode has the jboss.as:deployment MBean and not the domain mode ?
JBoss AS7 is installed on Linux 2.6.32-279.5.2.el6.x86_64
Any idea ?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/811456#811456]
Start a new discussion in JMX Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 2 months
[jBPM Development] - How to auto delegate using jbpm
by Krishna Ananthoj
Krishna Ananthoj [https://community.jboss.org/people/krishna.ananthoj] created the discussion
"How to auto delegate using jbpm"
To view the discussion, visit: https://community.jboss.org/message/818562#818562
--------------------------------------------------------------
I have a requirement where I need to auto delegate a task to a delegatee. The business requirement is to verify in the DB and find out who are the valid delegatees for the current delegator(actorId) for the current duration.
On node trigger event we need to check for the valid delegatee and auto assign/delegate this user to the task. We know that Jbpm allows us to do the delegation explicitly using delegate() method.
We have the valid delegatee information from DB at the time of node triggered but inorder to delegate the task we need to have the taskId information which is not available in this node trigger event. This is because, task object might not have been created yet.
public void delegate(*taskId*, userId, targetUserId)
We can't even use taskClaimed event method because it is not getting triggerd in case where there is single actorId specified for the node(in bpmn). It is because Jbpm directly moves the node from task 'Created' to 'Reserved' status in this case.
public void taskClaimed(TaskClaimedEvent event)
So, I dont have any idea, how to implement our requirement. Please help us.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/818562#818562]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 2 months
[JBoss AS 7 Development] - JBOSS 7.0 Deployment failure
by Razmik Z
Razmik Z [https://community.jboss.org/people/razmikz] created the discussion
"JBOSS 7.0 Deployment failure"
To view the discussion, visit: https://community.jboss.org/message/823079#823079
--------------------------------------------------------------
Hi
I'm new to Jboss. We have a Windows 2008 R2 server that I used to install Jboss 7.0. I have added the following to the servers Environment Variable +C:\Program Files\Java\jdk1.7.0\bin+
Our developer has created a .war file that we have copied to the /standalone/deployments folder.
When we start the instance (standalone.bat -b 0.0.0.0), within 2 seconds the deployment fails and in the /deployments folder we have a file +filename.war.failed+.
As soon as we delete this file the deployment succeeds. Everytime we have a new .WAR file, or everytime we stop the site and start it we see the same thing.
I don't know much about the deployment process but is it possible that Jboss attempts to deploy before some conditions are met? And a few seconds later when we delete the +filename.war.failed+ file the conditions are correct and deployment succeeds?
Here is a typical log of the failed deployment. I would appreciate any help.
D:\Test_Jboss\bin>standalone.bat -b 10.238.57.133
Calling "D:\Test_Jboss\bin\standalone.conf.bat"
'#' is not recognized as an internal or external command,
operable program or batch file.
JAVA_HOME is not set. Unexpected results may occur.
Set JAVA_HOME to the directory of your local JDK to avoid this message.
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: D:\Test_Jboss
JAVA: java
JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx51
2M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.se
rver.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.war
ning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djboss.server.default.c
onfig=standalone.xml -Djboss.bind.address.management=10.238.57.133 -Djboss.bind.
address=10.238.57.133
===============================================================================
16:14:19,875 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
16:14:20,875 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
16:14:20,937 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" sta
rting
16:14:24,359 INFO [org.xnio] XNIO Version 3.0.3.GA
16:14:24,375 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
16:14:24,406 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
16:14:24,359 INFO [org.jboss.as.server] JBAS015888: Creating http management se
rvice using socket-binding (management-http)
16:14:24,641 INFO [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin
Subsystem
16:14:24,672 INFO [org.jboss.as.clustering.infinispan] JBAS010280: Activating I
nfinispan subsystem.
16:14:24,656 INFO [org.jboss.as.osgi] JBAS011940: Activating OSGi Subsystem
16:14:24,703 INFO [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem
16:14:24,688 INFO [org.jboss.as.webservices] JBAS015537: Activating WebServices
Extension
16:14:24,688 INFO [org.jboss.as.security] JBAS013101: Activating Security Subsy
stem
16:14:24,781 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log han
dlers
16:14:24,844 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: St
arting Naming Service
16:14:24,875 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013100:
Current PicketBox version=4.0.7.Final
16:14:25,000 INFO [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408:
Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
16:14:25,219 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS01
5400: Bound mail session [java:jboss/mail/Default]
16:14:25,297 INFO [org.jboss.as.connector.subsystems.datasources] (ServerServic
e Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Dr
iver (version 1.3)
16:14:25,891 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread
1-4) Starting Coyote HTTP/1.1 on http--10.238.57.133-8180
16:14:26,047 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service
thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
16:14:26,953 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC se
rvice thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
16:14:27,407 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread
1-1) JBAS015012: Started FileSystemDeploymentService for directory D:\Test_Jboss
\standalone\deployments
16:14:27,469 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t
hreads - 1) JBAS015014: Re-attempting failed deployment OrangeCountyDemo (2).war
16:14:27,485 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t
hreads - 1) JBAS015014: Re-attempting failed deployment OrangeCountyDemo.war
16:14:27,485 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100:
Listening on /10.238.57.133:10000
16:14:27,485 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t
hreads - 1) JBAS015014: Re-attempting failed deployment TestOrangeCountyDemo.war
16:14:27,485 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100:
Listening on /10.238.57.133:4448
16:14:27,532 ERROR [org.jboss.as.controller.management-operation] (DeploymentSca
nner-threads - 2) Operation ("composite") failed - address: (undefined) - failur
e description: "JBAS014719: Invalid value specification OrangeCountyDemo (2).war
"
16:14:27,532 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t
hreads - 1) JBAS014719: Invalid value specification OrangeCountyDemo (2).war
16:14:27,547 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t
hreads - 1) undefined
16:14:27,547 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t
hreads - 1) JBAS015004: Caught exception writing deployment marker file D:\Test_
Jboss\standalone\deployments\Archive\OrangeCountyDemo.war.failed: java.io.FileNo
tFoundException: D:\Test_Jboss\standalone\deployments\Archive\OrangeCountyDemo.w
ar.failed (Access is denied)
at java.io.FileOutputStream.open(Native Method) [rt.jar:1.7.0_17]
at java.io.FileOutputStream.<init>(Unknown Source) [rt.jar:1.7.0_17]
at java.io.FileOutputStream.<init>(Unknown Source) [rt.jar:1.7.0_17]
at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.wr
iteFailedMarker(FileSystemDeploymentService.java:916) [jboss-as-deployment-scann
er-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.ac
cess$3100(FileSystemDeploymentService.java:88) [jboss-as-deployment-scanner-7.1.
1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$De
ployTask.handleFailureResult(FileSystemDeploymentService.java:1056) [jboss-as-de
ployment-scanner-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.sc
an(FileSystemDeploymentService.java:447) [jboss-as-deployment-scanner-7.1.1.Fina
l.jar:7.1.1.Final]
at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$De
ploymentScanRunnable.run(FileSystemDeploymentService.java:149) [jboss-as-deploym
ent-scanner-7.1.1.Final.jar:7.1.1.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [
rt.jar:1.7.0_17]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
[rt.jar:1.7.0_17]
at java.util.concurrent.FutureTask.runAndReset(Unknown Source) [rt.jar:1
.7.0_17]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source) [rt.jar:1.7.0_17]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source) [rt.jar:1.7.0_17]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt
.jar:1.7.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [r
t.jar:1.7.0_17]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-thread
s-2.0.0.GA.jar:2.0.0.GA]
16:14:27,563 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t
hreads - 1) undefined
16:14:27,563 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t
hreads - 1) JBAS015004: Caught exception writing deployment marker file D:\Test_
Jboss\standalone\deployments\Archive\TestOrangeCountyDemo.war.failed: java.io.Fi
leNotFoundException: D:\Test_Jboss\standalone\deployments\Archive\TestOrangeCoun
tyDemo.war.failed (Access is denied)
at java.io.FileOutputStream.open(Native Method) [rt.jar:1.7.0_17]
at java.io.FileOutputStream.<init>(Unknown Source) [rt.jar:1.7.0_17]
at java.io.FileOutputStream.<init>(Unknown Source) [rt.jar:1.7.0_17]
at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.wr
iteFailedMarker(FileSystemDeploymentService.java:916) [jboss-as-deployment-scann
er-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.ac
cess$3100(FileSystemDeploymentService.java:88) [jboss-as-deployment-scanner-7.1.
1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$De
ployTask.handleFailureResult(FileSystemDeploymentService.java:1056) [jboss-as-de
ployment-scanner-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.sc
an(FileSystemDeploymentService.java:447) [jboss-as-deployment-scanner-7.1.1.Fina
l.jar:7.1.1.Final]
at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$De
ploymentScanRunnable.run(FileSystemDeploymentService.java:149) [jboss-as-deploym
ent-scanner-7.1.1.Final.jar:7.1.1.Final]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [
rt.jar:1.7.0_17]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
[rt.jar:1.7.0_17]
at java.util.concurrent.FutureTask.runAndReset(Unknown Source) [rt.jar:1
.7.0_17]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$301(Unknown Source) [rt.jar:1.7.0_17]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
run(Unknown Source) [rt.jar:1.7.0_17]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt
.jar:1.7.0_17]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [r
t.jar:1.7.0_17]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-thread
s-2.0.0.GA.jar:2.0.0.GA]
16:14:27,563 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t
hreads - 1) undefined
16:14:27,907 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774
: Service status report
JBAS014777: Services which failed to start: service jboss.logging.handler
.FILE: org.jboss.msc.service.StartException in service jboss.logging.handler.FIL
E: java.io.FileNotFoundException: D:\Test_Jboss\standalone\log\server.log (Acces
s is denied)
16:14:27,922 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Ca
ught exception during boot: java.lang.IllegalStateException: JBAS014643: Could n
ot delete D:\Test_Jboss\standalone\configuration\standalone_xml_history\20130503
-110307226\standalone.v1.xml
at org.jboss.as.controller.persistence.ConfigurationFile.deleteRecursive
(ConfigurationFile.java:441) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.persistence.ConfigurationFile.deleteRecursive
(ConfigurationFile.java:437) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.persistence.ConfigurationFile.createHistoryDi
rectory(ConfigurationFile.java:422) [jboss-as-controller-7.1.1.Final.jar:7.1.1.F
inal]
at org.jboss.as.controller.persistence.ConfigurationFile.successfulBoot(
ConfigurationFile.java:273) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.persistence.BackupXmlConfigurationPersister.s
uccessfulBoot(BackupXmlConfigurationPersister.java:65) [jboss-as-controller-7.1.
1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractControllerService.finishBoot(Abstract
ControllerService.java:195) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.ServerService.boot(ServerService.java:268) [jboss
-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractContr
ollerService.java:155) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_17]
16:14:27,938 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Se
rver boot has failed in an unrecoverable manner; exiting. See previous messages
for details.
16:14:27,969 INFO [org.jboss.as.osgi] JBAS011942: Stopping OSGi Framework
16:14:27,969 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log han
dlers
16:14:28,079 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying Transactio
nManagerService
16:14:28,079 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction
recovery manager
16:14:28,094 INFO [org.apache.catalina.core.StandardContext] Container org.apac
he.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been start
ed
16:14:28,110 INFO [org.jboss.as] JBAS015950: JBoss AS 7.1.1.Final "Brontes" sto
pped in 145ms
Press any key to continue . . .
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/823079#823079]
Start a new discussion in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 2 months