[Bug 1210643] New: Release notes have not been through configure: showing @ tokens
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1210643
Bug ID: 1210643
Summary: Release notes have not been through configure: showing
@ tokens
Product: Fedora
Version: 20
Component: tomcat
Assignee: ivan.afonichev(a)gmail.com
Reporter: stephen.hindmarch(a)bt.com
QA Contact: extras-qa(a)fedoraproject.org
CC: alee(a)redhat.com, coolsvap(a)gmail.com,
ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com
Description of problem:
The RELEASE-NOTES file has not been through configure so all of the configure
tokens, such as @VERSION@ appear as tokens instead of being translated.
Version-Release number of selected component (if applicable):
tomcat-7.0.52-2.fc20.noarch
How reproducible:
Every time
Steps to Reproduce:
1. grep @VERSION@ /usr/share/doc/tomcat/RELEASE-NOTES
Actual results:
Apache Tomcat Version @VERSION@
Expected results:
Apache Tomcat Version 7.0.52
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=RWUwTAdV8g&a=cc_unsubscribe
8 years, 9 months
[Bug 1169102] New: [abrt] tomcat-7.0.52-2.fc20: Uncaught exception java.lang.RuntimeException in method java.util.concurrent.ThreadPoolExecutor.runWorker()
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1169102
Bug ID: 1169102
Summary: [abrt] tomcat-7.0.52-2.fc20: Uncaught exception
java.lang.RuntimeException in method
java.util.concurrent.ThreadPoolExecutor.runWorker()
Product: Fedora
Version: 20
Component: tomcat
Assignee: ivan.afonichev(a)gmail.com
Reporter: kkibwage(a)yahoo.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com
Version-Release number of selected component:
tomcat-7.0.52-2.fc20
Additional info:
reporter: libreport-2.2.3
cmdline: java -agentpath:/usr/lib64/libabrt-java-connector.so=abrt=on
-classpath
/usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar
-Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat
-Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat/temp
-Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
org.apache.catalina.startup.Bootstrap start
executable: /usr/share/tomcat/bin/bootstrap.jar
java_executable:
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre-abrt/bin/java
kernel: 3.17.3-200.fc20.x86_64
pid: 1494
runlevel: N 5
uid: 91
Truncated backtrace:
Exception in thread "http-bio-8080-exec-3" java.lang.RuntimeException: Stopping
thread http-bio-8080-exec-3 to avoid potential memory leaks after a context was
stopped.
at
org.apache.tomcat.util.threads.ThreadPoolExecutor.stopCurrentThreadIfNeeded(ThreadPoolExecutor.java:129)
[jar:file:/usr/share/java/tomcat/tomcat-coyote.jar!/org/apache/tomcat/util/threads/ThreadPoolExecutor.class]
at org.apache.tomcat.util.threads.TaskQueue.poll(TaskQueue.java:90)
[jar:file:/usr/share/java/tomcat/tomcat-coyote.jar!/org/apache/tomcat/util/threads/TaskQueue.class]
at org.apache.tomcat.util.threads.TaskQueue.poll(TaskQueue.java:32)
[jar:file:/usr/share/java/tomcat/tomcat-coyote.jar!/org/apache/tomcat/util/threads/TaskQueue.class]
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
[jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/rt.jar!/java/util/concurrent/ThreadPoolExecutor.class]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
[jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/rt.jar!/java/util/concurrent/ThreadPoolExecutor.class]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/rt.jar!/java/util/concurrent/ThreadPoolExecutor$Worker.class]
at java.lang.Thread.run(Thread.java:745)
[jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/rt.jar!/java/lang/Thread.class]
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=GtkS5uBD5s&a=cc_unsubscribe
8 years, 9 months
[Bug 1169095] New: [abrt] tomcat-7.0.52-2.fc20: Uncaught exception java.lang.RuntimeException in method java.util.concurrent.ThreadPoolExecutor.runWorker()
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1169095
Bug ID: 1169095
Summary: [abrt] tomcat-7.0.52-2.fc20: Uncaught exception
java.lang.RuntimeException in method
java.util.concurrent.ThreadPoolExecutor.runWorker()
Product: Fedora
Version: 20
Component: tomcat
Assignee: ivan.afonichev(a)gmail.com
Reporter: kkibwage(a)yahoo.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com
Description of problem:
i was undeploying an app
Version-Release number of selected component:
tomcat-7.0.52-2.fc20
Additional info:
reporter: libreport-2.2.3
cmdline: java -agentpath:/usr/lib64/libabrt-java-connector.so=abrt=on
-classpath
/usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar
-Dcatalina.base=/usr/share/tomcat -Dcatalina.home=/usr/share/tomcat
-Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat/temp
-Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
org.apache.catalina.startup.Bootstrap start
executable: /usr/share/tomcat/bin/bootstrap.jar
java_executable:
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre-abrt/bin/java
kernel: 3.17.3-200.fc20.x86_64
pid: 1494
runlevel: N 5
uid: 91
Truncated backtrace:
Exception in thread "http-bio-8080-exec-4" java.lang.RuntimeException: Stopping
thread http-bio-8080-exec-4 to avoid potential memory leaks after a context was
stopped.
at
org.apache.tomcat.util.threads.ThreadPoolExecutor.stopCurrentThreadIfNeeded(ThreadPoolExecutor.java:129)
[jar:file:/usr/share/java/tomcat/tomcat-coyote.jar!/org/apache/tomcat/util/threads/ThreadPoolExecutor.class]
at
org.apache.tomcat.util.threads.ThreadPoolExecutor.afterExecute(ThreadPoolExecutor.java:100)
[jar:file:/usr/share/java/tomcat/tomcat-coyote.jar!/org/apache/tomcat/util/threads/ThreadPoolExecutor.class]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
[jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/rt.jar!/java/util/concurrent/ThreadPoolExecutor.class]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/rt.jar!/java/util/concurrent/ThreadPoolExecutor$Worker.class]
at java.lang.Thread.run(Thread.java:745)
[jar:file:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/lib/rt.jar!/java/lang/Thread.class]
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=zbwT3JSe4B&a=cc_unsubscribe
8 years, 9 months
[Bug 1167033] New: All tomcat at name instances run under the same tomcat user
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1167033
Bug ID: 1167033
Summary: All tomcat at name instances run under the same tomcat
user
Product: Fedora
Version: 20
Component: tomcat
Assignee: ivan.afonichev(a)gmail.com
Reporter: bowabos(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com
Description of problem:
It should be possible to specify TOMCAT_USER variable in /etc/sysconfig/name to
change the user under which the name instance will run.
Version-Release number of selected component (if applicable):
How reproducible: easy
Steps to Reproduce:
1. create a second named instance
2. set TOMCAT_USER to a defined user (i.e. jira)
3. start the tomcat@name instance (i.e. tomcat@jira)
Actual results:
ps -ef | grep java shows the user is tomcat
Expected results:
ps -ef | grep java should return a process owned by the named tomcat instance
(i.e. jira)
Additional info:
modifying /usr/lib/systemd/system/tomcat@.service
and changing the User and Group line with
User=%I
Group=%I
may be an option explored.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=c32RhcyRMh&a=cc_unsubscribe
8 years, 9 months
[Bug 1144270] New: SBT doesn't start correctly in some 32-bit machines due to low memory
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1144270
Bug ID: 1144270
Summary: SBT doesn't start correctly in some 32-bit machines
due to low memory
Product: Fedora
Version: 20
Component: sbt
Assignee: willb(a)redhat.com
Reporter: dugucloud(a)qq.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org, s(a)shk.io,
willb(a)redhat.com
Description of problem:
When starting SBT, Java reports cannot start VM because it cannot reserve
enough heap.
Version-Release number of selected component (if applicable):
0.13.1
How reproducible:
Every time on my machine.
Steps to Reproduce:
Run command sbt in console and see the console output.
Actual results:
'''
$ sbt
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
'''
Expected results:
SBT works fine.
Additional info:
My machine is 32-bit. When I start SBT, my memory usage is 0.8 GiB / 2.5 GiB,
swap usage 0 GiB / 3.8GiB.
But after I modified the memory settings of Java in my SBT script
(/usr/bin/sbt), I can run it. These are the last few lines of my modified:
'''
export BASE_CLASSPATH=$(build-classpath scala ivy sbt ${JLINE} jansi
test-interface sbinary)
export JAVA_OPTS="-Xms256m -Xmx1024m -Xss1M -XX:+CMSClassUnloadingEnabled
-XX:MaxHeapSize=1000m -XX:MaxPermSize=256m"
java ${JAVA_OPTS} -Dfedora.sbt.boot.dir=${SBT_BOOT_DIR}
-Dfedora.sbt.ivy.dir=${SBT_IVY_DIR}
-Dsbt.boot.properties=${SBT_BOOT_PROPERTIES} -cp ${BASE_CLASSPATH}
xsbt.boot.Boot "$@"
'''
This is the StackOverflow question where I found my way:
https://stackoverflow.com/questions/4401396/could-not-reserve-enough-spac...
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=sZuZ0ALIyT&a=cc_unsubscribe
8 years, 9 months