[JBoss JIRA] Created: (JBAS-3667) HotSpot Crashes
by srk (JIRA)
HotSpot Crashes
---------------
Key: JBAS-3667
URL: http://jira.jboss.com/jira/browse/JBAS-3667
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build System
Affects Versions: JBossAS-4.0.4.GA
Environment: OS:Red Hat Enterprise Linux ES release 3 (Taroon) , Java HotSpot(TM) Server VM (1.5.0_03-b07) for linux-x86
Reporter: srk
Assigned To: Ruel Loehr
Priority: Blocker
Attachments: hs_err_pid7517.log
When I start JBoss it crashes with the following hs-errpid*.log file generated..
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb6ed014a, pid=7517, tid=2638216112
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_03-b07 mixed mode)
# Problematic frame:
# V [libjvm.so+0x3b514a]
#
--------------- T H R E A D ---------------
Current thread (0x9d418f38): VMThread [id=7520]
siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x00000400
Registers:
EAX=0xb1000f08, EBX=0xb7078b2c, ECX=0x9d806d48, EDX=0x9d806d74
ESP=0x9d3ff230, EBP=0x9d3ff238, ESI=0x00000400, EDI=0xb1004a74
EIP=0xb6ed014a, CR2=0x00000400, EFLAGS=0x00010206
Top of Stack: (sp=0x9d3ff230)
0x9d3ff230: b7078b2c b1000f08 9d3ff268 b6ef8e6e
0x9d3ff240: b1000f08 b708706c 9d3ff268 b6ef8e21
0x9d3ff250: 9ea5a0ac b0f336d0 9ea5b804 b7078b2c
0x9d3ff260: b706a140 b708706c 9d3ff288 b6ed0332
0x9d3ff270: 9d80a810 b0ffae28 b7077120 b6ed02fa
0x9d3ff280: b7078b2c b708706c 9d3ff318 b6f3defe
0x9d3ff290: b708706c 00000000 00000001 9d3ff2b8
0x9d3ff2a0: b7503dfd b75c8660 0000baa8 9d3ff2c0
Instructions: (pc=0xb6ed014a)
0xb6ed013a: 00 00 00 5b 81 c3 ef 89 1a 00 8b 30 85 f6 74 45
0xb6ed014a: 8b 06 83 e0 03 83 f8 03 74 3b 8b 16 c7 06 03 00
Stack: [0x9d37f000,0x9d400000), sp=0x9d3ff230, free space=512k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x3b514a]
V [libjvm.so+0x3dde6e]
V [libjvm.so+0x3b5332]
V [libjvm.so+0x422efe]
V [libjvm.so+0x42220e]
V [libjvm.so+0x421e97]
V [libjvm.so+0x4bb2af]
V [libjvm.so+0x4baca6]
V [libjvm.so+0x4ba317]
V [libjvm.so+0x4ba525]
V [libjvm.so+0x4ba130]
V [libjvm.so+0x3eca78]
C [libpthread.so.0+0x4dac]
VM_Operation (0x9cc52e8c): parallel gc system gc, mode: safepoint, requested by thread 0x9d44bba0
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x9a528258 JavaThread "HSQLDB Timer @39859" daemon [_thread_blocked, id=7547]
0x9c2b30c0 JavaThread "WorkManager(3)-1" daemon [_thread_blocked, id=7546]
0x99407a98 JavaThread "Thread-3" daemon [_thread_blocked, id=7545]
0x9a9cc3d0 JavaThread "JBossMQ Cache Reference Softner" daemon [_thread_blocked, id=7544]
0x9a3dfcd0 JavaThread "SubscriptionWatchDog" [_thread_blocked, id=7543]
0x082481a8 JavaThread "ContainerBackgroundProcessor[StandardEngine[jboss.web]]" daemon [_thread_blocked, id=7542]
0x9b17f900 JavaThread "PooledInvokerAcceptor#0-4445" [_thread_in_native, id=7541]
0x9be2a548 JavaThread "RMI TCP Accept-4444" daemon [_thread_in_native, id=7540]
0x9b133e78 JavaThread "TimeoutFactory-0" daemon [_thread_blocked, id=7539]
0x9afea8c0 JavaThread "JBoss System Threads(1)-2" daemon [_thread_in_native, id=7538]
0x9be5e778 JavaThread "GC Daemon" daemon [_thread_blocked, id=7537]
0x9be5ddc0 JavaThread "RMI Reaper" [_thread_blocked, id=7536]
0x9adf2570 JavaThread "Timer-1" daemon [_thread_blocked, id=7535]
0x9bef60a0 JavaThread "RMI TCP Accept-1098" daemon [_thread_in_native, id=7534]
0x087179c8 JavaThread "JBoss System Threads(1)-1" daemon [_thread_in_native, id=7533]
0x08154638 JavaThread "ScannerThread" daemon [_thread_blocked, id=7532]
0x08650da0 JavaThread "Timer-0" daemon [_thread_blocked, id=7531]
0x9d44c6c8 JavaThread "DestroyJavaVM" [_thread_blocked, id=7517]
0x9d44bba0 JavaThread "main" [_thread_blocked, id=7529]
0x9d4298c8 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=7527]
0x9d428528 JavaThread "CompilerThread1" daemon [_thread_blocked, id=7526]
0x9d4275e8 JavaThread "CompilerThread0" daemon [_thread_blocked, id=7525]
0x9d426678 JavaThread "AdapterThread" daemon [_thread_blocked, id=7524]
0x9d4257f0 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=7523]
0x9d41c318 JavaThread "Finalizer" daemon [_thread_blocked, id=7522]
0x9d41b6d8 JavaThread "Reference Handler" daemon [_thread_blocked, id=7521]
Other Threads:
=>0x9d418f38 VMThread [id=7520]
0x9d42add8 WatcherThread [id=7528]
VM state:at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x0805a510/0x0805a538] Threads_lock - owner thread: 0x9d418f38
[0x0805a960/0x0805a978] Heap_lock - owner thread: 0x9d44bba0
Heap
PSYoungGen total 19456K, used 4556K [0xafb30000, 0xb17a0000, 0xb17a0000)
eden space 9792K, 0% used [0xafb30000,0xafb30000,0xb04c0000)
from space 9664K, 47% used [0xb0e30000,0xb12a3138,0xb17a0000)
to space 9664K, 0% used [0xb04c0000,0xb04c0000,0xb0e30000)
PSOldGen total 233024K, used 19194K [0xa17a0000, 0xafb30000, 0xafb30000)
object space 233024K, 8% used [0xa17a0000,0xa2a5e998,0xafb30000)
PSPermGen total 20096K, used 19991K [0x9d7a0000, 0x9eb40000, 0xa17a0000)
object space 20096K, 99% used [0x9d7a0000,0x9eb25c50,0x9eb40000)
Dynamic libraries:
08048000-08056000 r-xp 00000000 08:11 15925290 /usr/java/jdk1.5.0_03/bin/java
VM Arguments:
jvm_args: -Xms256m -Xmx256m -Dprogram.name=run.sh -Djava.endorsed.dirs=/home/jboss/jboss-4.0.4/lib/endorsed
java_command: org.jboss.Main
Environment Variables:
JAVA_HOME=/usr/java/jdk1.5.0_03/
PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/jboss/bin:/usr/java/jdk1.5.0_03//bin
LD_LIBRARY_PATH=/usr/java/jdk1.5.0_03/jre/lib/i386/server:/usr/java/jdk1.5.0_03/jre/lib/i386:/usr/java/jdk1.5.0_03/jre/../lib/i386:/usr/local/lib/
SHELL=/bin/bash
--------------- S Y S T E M ---------------
OS:Red Hat Enterprise Linux ES release 3 (Taroon)
uname:Linux 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 i686
libc:glibc 2.3.2 NPTL 0.60
rlimit: STACK 10240k, CORE 0k, NPROC 7168, NOFILE 1024, AS infinity
load average:1.08 0.25 0.08
CPU:total 2 family 15, cmov, cx8, fxsr, mmx, sse, sse2, ht
Memory: 4k page, physical 2053540k(1281952k free), swap 2040244k(2040244k free)
vm_info: Java HotSpot(TM) Server VM (1.5.0_03-b07) for linux-x86, built on Apr 13 2005 02:09:32 by java_re with gcc 3.2.1-7a (J2SE release)
--
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
19 years, 10 months
[JBoss JIRA] Commented: (JBPM-429) Support for external security systems
by Tomaz Cerar (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-429?page=comments#action_12343570 ]
Tomaz Cerar commented on JBPM-429:
----------------------------------
is it possible to get this fix ready for 3.1.3 or at least 3.2?
> Support for external security systems
> -------------------------------------
>
> Key: JBPM-429
> URL: http://jira.jboss.com/jira/browse/JBPM-429
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 3.0
> Environment: NA
> Reporter: Ashwini Kumar
> Assigned To: Tom Baeyens
> Original Estimate: 2 minutes
> Remaining Estimate: 2 minutes
>
> Please change the readAssignmentDelegation method in org.jbpm.jpdl.xml.JpdlXmlReader to be the following.
> The original method would ignore the class attribute assigned to swimlane assignments and default it to org.jbpm.identity.assignment.ExpressionAssignmentHandler
> Thanks,
> private Delegation readAssignmentDelegation(Element assignmentElement) {
> Delegation assignmentDelegation = new Delegation();
> String expression = assignmentElement.attributeValue("expression");
> if (expression!=null) {
> assignmentDelegation.setProcessDefinition(processDefinition);
> String assignmentHandler = assignmentElement.attributeValue("class");
> if (assignmentHandler != null){
> assignmentDelegation.setClassName(assignmentHandler);
> }
> else{
> assignmentDelegation.setClassName("org.jbpm.identity.assignment.ExpressionAssignmentHandler");
> }
> assignmentDelegation.setConfiguration("<expression>"+expression+"</expression>");
>
> } else {
> assignmentDelegation.read(assignmentElement, this);
> }
> return assignmentDelegation;
> }
--
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
19 years, 10 months
[JBoss JIRA] Updated: (JBESB-68) Tidy-up JDBC classes
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBESB-68?page=all ]
Mark Little updated JBESB-68:
-----------------------------
Fix Version/s: 4.0 Beta 1 Maintenance Pack 1
(was: 4.0 Beta 1)
Affects Version/s: 4.0 Beta 1
(was: 4.0 Alpha 1)
> Tidy-up JDBC classes
> --------------------
>
> Key: JBESB-68
> URL: http://jira.jboss.com/jira/browse/JBESB-68
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: ESB Core, Documentation
> Affects Versions: 4.0 Beta 1
> Reporter: Mark Little
> Assigned To: Mohit Keswani
> Priority: Minor
> Fix For: 4.0 Beta 1 Maintenance Pack 1
>
>
> - common\src\org\jboss\soa\esb\helpers\persist\JdbcCleanConn.java
> 1) Refactor
> - rename to conventions
> - categorize exceptions instead of using Exception
> - group into a db specific package instead of persist
> - common\src\org\jboss\soa\esb\helpers\persist\SqlDbTable.java
> 1) Refactor
> - rename to conventions e.g getFldName - > getFieldName
--
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
19 years, 10 months
[JBoss JIRA] Closed: (JBESB-68) Tidy-up JDBC classes
by Mark Little (JIRA)
[ http://jira.jboss.com/jira/browse/JBESB-68?page=all ]
Mark Little closed JBESB-68.
----------------------------
Resolution: Done
> Tidy-up JDBC classes
> --------------------
>
> Key: JBESB-68
> URL: http://jira.jboss.com/jira/browse/JBESB-68
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: ESB Core, Documentation
> Affects Versions: 4.0 Beta 1
> Reporter: Mark Little
> Assigned To: Mohit Keswani
> Priority: Minor
> Fix For: 4.0 Beta 1 Maintenance Pack 1
>
>
> - common\src\org\jboss\soa\esb\helpers\persist\JdbcCleanConn.java
> 1) Refactor
> - rename to conventions
> - categorize exceptions instead of using Exception
> - group into a db specific package instead of persist
> - common\src\org\jboss\soa\esb\helpers\persist\SqlDbTable.java
> 1) Refactor
> - rename to conventions e.g getFldName - > getFieldName
--
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
19 years, 10 months
[JBoss JIRA] Created: (JBESB-129) Wrong jar referred to in Getting Started
by Mark Little (JIRA)
Wrong jar referred to in Getting Started
----------------------------------------
Key: JBESB-129
URL: http://jira.jboss.com/jira/browse/JBESB-129
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.0 Beta 1
Reporter: Mark Little
Assigned To: Jason Lenhart
Priority: Minor
Fix For: 4.0
Issue 1
In the GettingStarted.doc
The recommended PostgreSQL is JDBC 2 EE 8.1 Build 407. This version is available from the PostgreSQL JDBC website.
This refers to a .jar file that is NOT the one that ships with the Beta1. Therefore it can lead to confusion when the reader is trying to tweak out their deployment.properties file as described on page 10.
At least the line above could say that while build 407 is recommended, we have provided pg74.216.jdbc2ee.jar in the conf/lib folder and you can use that one for testing purposes.
Or something along those lines.
--
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
19 years, 10 months
[JBoss JIRA] Commented: (JBAS-2631) AttributePersistenceService should be started early
by gunter zeilinger (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2631?page=comments#action_12343557 ]
gunter zeilinger commented on JBAS-2631:
----------------------------------------
conf/jboss-service.xml provided by jems-installer-1.2.0.BETA2.jar does not include the AttributePersistenceService - and it is also not started by any other deploy/xxx-service.xml.
> AttributePersistenceService should be started early
> ---------------------------------------------------
>
> Key: JBAS-2631
> URL: http://jira.jboss.com/jira/browse/JBAS-2631
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Installer
> Affects Versions: JBossAS-4.0.3 SP1
> Reporter: Dimitris Andreadis
> Assigned To: Scott M Stark
> Priority: Minor
> Fix For: JBossAS-4.0.4.CR2
>
>
> When using the installer to create a full configuration the AttributePersistenceService is started through
> ./deploy/attrpm-service.xml.
> Now since this service needs to be present before any XMBean using it, it needs to be started earlier, probably throught conf/jboss-service.xml, as we do in the .zip distribution of jboss.
--
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
19 years, 10 months