April 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1157) JGroups threads get stuck and stop communicating

by vivek v (JIRA)

JGroups threads get stuck and stop communicating ------------------------------------------------ Key: JGRP-1157 URL: https://jira.jboss.org/jira/browse/JGRP-1157 Project: JGroups Issue Type: Bug Affects Versions: 2.9, 2.8 Environment: Linux Reporter: vivek v Assignee: Bela Ban We are having problem where a node gets isolated after some intermittent network outage and is never able to join back. Bela suspected some issue /w RouterStub and fixed a bug - JGRP-1151. But, we are were able to reproduce this problem /w even JGroups 2.9 GA. Looks like the problem is that the node that gets isolated becomes unresponsive as all its JGroups threads hang. Here is how we reproduced the error /w 3 nodes (Node A - coordinator also running Gossip Router, Node B, Node C), 1) We added WANem between A and B - so there are random disconnects,high packet loss and 200 msec of delay 2) Due to our WANem setting B loses connectivity /w GR - in and out 3) We restart A and it becomes isolated. A becomes singleton and never joins back the group. We see NAKACK on the node C - as A is still able to get to C, but not B. C keeps dropping messages from A as A is not in its transmission table. 4) We turned on tracing on A, but after a while (couple of hours) we see no JGroups trace on A - we suspected that some of the JGroups threads might have got stuck. So we took the thread dump of the java process on A (attached). As you can see there are quite a few JGroups threads in the waiting state and all are for TCP.send We are not clear on how or why will the JGroups threads hang. Could outgoing messages be queued up and not moving for some reason? The only solution to fix this was to restart all the nodes, which is not desirable. Attached are the stack trace (thread-dump) and our protocol stack. This jira was originated from discussion at http://sourceforge.net/mailarchive/forum.php?thread_name=4B7BC107.9060304... -- 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

15 years, 7 months

5
12
0 / 0

[JBoss JIRA] Created: (JGRP-1003) deadlock in TP.send - socket write hangs inside a Lock, preventing other threads to do TP.send()

by Victor N (JIRA)

deadlock in TP.send - socket write hangs inside a Lock, preventing other threads to do TP.send() ------------------------------------------------------------------------------------------------ Key: JGRP-1003 URL: https://jira.jboss.org/jira/browse/JGRP-1003 Project: JGroups Issue Type: Bug Affects Versions: 2.7 Environment: Linux (Debian), kernel 2.6.x Reporter: Victor N Assignee: Bela Ban I am using JGroups 2.7.0 GA with the typical protocols stack based on TCP (taken from tcp.xml). Sometimes it occurs that socket write operation hangs inside TP.send() -- this is not so untypical for blocking I/O approach! -- after that JGroups is not working at all because most of threads are blocked inside TP.send() waiting for that first thread releasing "out_stream_lock". Below is a fragment from my stack trace. 1) the thread that hangs in socket write until forever (maybe due to a broken socket or something else); this thread owns "out_stream_lock in TP class": "Timer-1,name,IP:port" daemon prio=10 tid=0x084e5c00 nid=0x15f0 runnable [0x211c1000..0x211c2040] java.lang.Thread.State: RUNNABLE at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) - locked <0x43427300> (a java.io.BufferedOutputStream) at java.io.DataOutputStream.flush(DataOutputStream.java:106) at org.jgroups.blocks.TCPConnectionMap$TCPConnection.doSend(TCPConnectionMap.java:472) at org.jgroups.blocks.TCPConnectionMap$TCPConnection._send(TCPConnectionMap.java:453) at org.jgroups.blocks.TCPConnectionMap$TCPConnection.send(TCPConnectionMap.java:436) at org.jgroups.blocks.TCPConnectionMap$TCPConnection.access$100(TCPConnectionMap.java:341) at org.jgroups.blocks.TCPConnectionMap.send(TCPConnectionMap.java:137) at org.jgroups.protocols.TCP.send(TCP.java:53) at org.jgroups.protocols.BasicTCP.sendToSingleMember(BasicTCP.java:141) at org.jgroups.protocols.TP.doSend(TP.java:1105) at org.jgroups.protocols.TP.send(TP.java:1088) at org.jgroups.protocols.TP.down(TP.java:907) at org.jgroups.protocols.Discovery.down(Discovery.java:363) at org.jgroups.protocols.MERGE2.down(MERGE2.java:169) at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:333) at org.jgroups.protocols.FD.down(FD.java:327) at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:72) at org.jgroups.protocols.BARRIER.down(BARRIER.java:96) at org.jgroups.protocols.pbcast.NAKACK.retransmit(NAKACK.java:1530) at org.jgroups.protocols.pbcast.NAKACK.retransmit(NAKACK.java:1476) at org.jgroups.stack.Retransmitter$Task.run(Retransmitter.java:207) at org.jgroups.util.TimeScheduler$TaskWrapper.run(TimeScheduler.java:218) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - <0x2b5522e0> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) - <0x2b5550f8> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) - <0x434273f0> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) 2) and there are many threads like this blocked "on out_stream_lock.lock()" call inside TP class: "Connection.Receiver [ip:port - ip:port],name,ip:port" prio=10 tid=0x020dc000 nid=0x1fab waiting on condition [0x1365f000..0x1365ffc0] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x2b5550f8> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:747) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:778) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1114) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:186) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:262) at org.jgroups.protocols.TP.send(TP.java:1082) at org.jgroups.protocols.TP.down(TP.java:907) at org.jgroups.protocols.Discovery.up(Discovery.java:274) at org.jgroups.protocols.TP.passMessageUp(TP.java:995) at org.jgroups.protocols.TP.access$100(TP.java:52) at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1451) at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1427) at java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy.rejectedExecution(ThreadPoolExecutor.java:1738) at org.jgroups.util.ShutdownRejectedExecutionHandler.rejectedExecution(ShutdownRejectedExecutionHandler.java:34) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658) at org.jgroups.protocols.TP.dispatchToThreadPool(TP.java:1061) at org.jgroups.protocols.TP.receive(TP.java:1038) at org.jgroups.protocols.BasicTCP.receive(BasicTCP.java:180) at org.jgroups.blocks.TCPConnectionMap$TCPConnection$ConnectionPeerReceiver.run(TCPConnectionMap.java:553) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - None (Since all threads from JGroups' ThreadPool are locked, you can see "rejectedExecution" in the last stack trace). Maybe we could implement some solution for TCP (blocking I/O)? Maybe it is possible to release the lock before socket write? -- 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

15 years, 7 months

2
41
0 / 0

[JBoss JIRA] Created: (JBAS-7274) org.jboss.test.jrmp.test.DynLoadingFromSARUnpackedUnitTestCase

by Shelly McGowan (JIRA)

org.jboss.test.jrmp.test.DynLoadingFromSARUnpackedUnitTestCase -------------------------------------------------------------- Key: JBAS-7274 URL: https://jira.jboss.org/jira/browse/JBAS-7274 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Shelly McGowan -- 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

15 years, 7 months

3
8
0 / 0

[JBoss JIRA] Created: (JGRP-1133) NakReceiverWindow: make non blocking

by Bela Ban (JIRA)

NakReceiverWindow: make non blocking ------------------------------------ Key: JGRP-1133 URL: https://jira.jboss.org/jira/browse/JGRP-1133 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.10 Remove the read/write locks and use ConcurrentHashMap to make adds and removes concurrent -- 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

15 years, 7 months

1
10
0 / 0

[JBoss JIRA] Created: (JBAS-7747) CLONE -Fix oid-sorting in the snmp-adaptor

by Prabhu S (JIRA)

CLONE -Fix oid-sorting in the snmp-adaptor ------------------------------------------ Key: JBAS-7747 URL: https://jira.jboss.org/jira/browse/JBAS-7747 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Management services Reporter: Prabhu S Assignee: Heiko W. Rupp Fix For: JBossAS-5.0.0.Beta1 Sorting of oids still sucks somewhat. Order is currently .1.2.3.1, .1.2.3.10, .1.2.3.2, .1.2.3.3 which makes getnext return less data than desired Also take into account, that management systems might ask for a node and then want to walk the subtree by issuing get and getNext requests. So if a request for a node fails and this node was no leaf (.0 ending), try to get the subnode with the smallest "sub-oid". -- 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

15 years, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-7665) Add Quick start bit on binding JGroups to different interface

by Brian Stansberry (JIRA)

Add Quick start bit on binding JGroups to different interface ------------------------------------------------------------- Key: JBAS-7665 URL: https://jira.jboss.org/jira/browse/JBAS-7665 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Docs/Clustering Guide Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.CR1 Add a bit in the quick start section on how to: ./run.sh -c all -b <eth0> -Djgroups.bind_addr=<eth1> -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-7602) Add cleint classpath requirements for HA-JNDI

by Brian Stansberry (JIRA)

Add cleint classpath requirements for HA-JNDI --------------------------------------------- Key: JBAS-7602 URL: https://jira.jboss.org/jira/browse/JBAS-7602 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Docs/Clustering Guide Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.CR1 The following jars should be on the client classpath for HA-JNDI to work: jboss-ha-client.jar jboss-ha-legacy-client.jar Both can be found in $JBOSS_HOME/client Putting jboss-all.jar on the classpath serves the same purpose. The HA-JNDI chapter in the Clustering Guide should state this. -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-7422) Pick up Rado Husar's Clustering Guide fixes

by Brian Stansberry (JIRA)

Pick up Rado Husar's Clustering Guide fixes ------------------------------------------- Key: JBAS-7422 URL: https://jira.jboss.org/jira/browse/JBAS-7422 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Docs/Clustering Guide Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.Alpha1 See Rado's comments in subtasks under JBPAPP-2617. Incorporate relevant ones in the community docs. -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6348) Problem with QueuedPessimisticEJBLock and Arjuna

by Ole Husgaard (JIRA)

Problem with QueuedPessimisticEJBLock and Arjuna ------------------------------------------------ Key: JBAS-6348 URL: https://jira.jboss.org/jira/browse/JBAS-6348 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Manager (Arjuna) Affects Versions: JBossAS-4.2.3.GA Reporter: Ole Husgaard Assignee: Jonathan Halliday When using Arjuna, QueuedPessimisticEJBLock does not always properly detect that a waiting tx has timed out. The problem is that QueuedPessimisticEJBLock was written for the old TM, which did not rollback transactions on timeout, but only marked them for rollback. Now that Arjuna is in play, it has to check for rolled back transactions too. The isTxExpired() method should be changed to something like this: protected boolean isTxExpired(Transaction miTx) throws Exception { if (miTx != null && (miTx.getStatus() == Status.STATUS_MARKED_ROLLBACK || miTx.getStatus() == Status.STATUS_ROLLEDBACK)) { return true; } return false; } -- 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

15 years, 7 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-6244) document how to properly configure resource recovery in jbossjta-properties.xml

by John Mazzitelli (JIRA)

document how to properly configure resource recovery in jbossjta-properties.xml ------------------------------------------------------------------------------- Key: JBAS-6244 URL: https://jira.jboss.org/jira/browse/JBAS-6244 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Docs/Administration and Configuration Guide Affects Versions: JBossAS-4.2.1.GA Reporter: John Mazzitelli Assignee: Samson Kittoli Currently, people are having a tough time figuring out how to correct this error when their apps hit it while running inside of JBossAS: 21:31:10,147 WARN oggerI18N om.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa om.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa Could not find new XAResource to use for recovering non-serializable XAResource For examples of the types of questions people are asking (yes, I was one of them :): http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146138&start=0&p... http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=78... http://www.nabble.com/JBoss-Integration---recovering-XAResource-td2003557... http://forums.java.net/jive/thread.jspa?messageID=254647 This talks about the problem, but nothing specifically addresses how to actually fix the problem: http://www.jboss.org/community/docs/DOC-12463 This comes close - but it mentions Messaging specific things, so it is not clear how you do this for your own JDBC data sources: https://www.jboss.org/community/docs/DOC-12826 This JIRA is to request that our documentation specifically address this problem and provide explicit hints as to how to fix it. Mention things like: 1) the existance of the Oracle and generic JNDI recovery modules, but how they are not configured/activated out-of-box 2) how to edit jbossjta-properties.xml to configure those modules with the JDBC URL/JNDI URI and db user/pass 3) how to add the recovery modules in jbossjta-properties.xml I talk about how I plan to solve this in that first forum post linked above - that could be used as an example for the kind of docs I was looking for. Even if all this JIRA does is add a commented section in jbossjta-properties.xml, that would go a long way in helping solve this problem for people without them resulting to hair pulling or jumping off bridges. -- 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

15 years, 7 months

9
20
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2042) Investigate performance issue related to use of @SecurityDomain on EJB

by jaikiran pai (JIRA)

Investigate performance issue related to use of @SecurityDomain on EJB ---------------------------------------------------------------------- Key: EJBTHREE-2042 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2042 Project: EJB 3.0 Issue Type: Task Reporter: jaikiran pai Assignee: jaikiran pai A user has reported that the use of @SecurityDomain shows a relatively poor performance (even when a @PermitAll) is applied to the bean. See the referenced forum thread for details. Although, it can't be guaranteed that the performance of a bean method invocation with a @SecurityDomain will be same as that without a @SecurityDomain, the difference in the timings as reported in that thread looks a bit too high. This JIRA is to track to investigate the issue and see if there's any genuine performance bug. -- 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

15 years, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (JBAS-6732) Add a section on configuring logging

by Jason T. Greene (JIRA)

Add a section on configuring logging ------------------------------------ Key: JBAS-6732 URL: https://jira.jboss.org/jira/browse/JBAS-6732 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assignee: David Lloyd -- 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

15 years, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (JBAS-7715) Upgrade BSF (Bean Scripting Framework) to v3.0 (from 2.4.0)

by Richard Opalka (JIRA)

Upgrade BSF (Bean Scripting Framework) to v3.0 (from 2.4.0) ----------------------------------------------------------- Key: JBAS-7715 URL: https://jira.jboss.org/jira/browse/JBAS-7715 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Other Reporter: Richard Opalka Assignee: Dimitris Andreadis Fix For: JBossAS-6.0.0.M3 http://jakarta.apache.org/bsf/index.html BSF 3.0 version is based on standard API (javax.script). We're supporting JDK6 and above where this API is available ;) -- 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

15 years, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-7690) Comply with JBoss Project Versioning guidelines

by Dimitris Andreadis (JIRA)

Comply with JBoss Project Versioning guidelines ----------------------------------------------- Key: JBAS-7690 URL: https://jira.jboss.org/jira/browse/JBAS-7690 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Dimitris Andreadis Assignee: Paul Gier Priority: Critical Fix For: JBossAS-6.0.0.GA According to: http://community.jboss.org/wiki/JBossProjectVersioning The final (GA) version must not contain GA in the zipped distro filename. I suppose it won't matter whether GA will appear in the unzipped base directory, or this needs to be clarified. The produced maven artifacts will maintain the GA, AFAICT. -- 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

15 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-7857) Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03

by Richard Opalka (JIRA)

Upgrade xalan and serializer from 2.7.1.patch01-brew to 2.7.1.patch03 --------------------------------------------------------------------- Key: JBAS-7857 URL: https://jira.jboss.org/jira/browse/JBAS-7857 Project: JBoss Application Server Issue Type: Thirdparty Change Security Level: Public (Everyone can see) Components: XML services Reporter: Richard Opalka Assignee: Richard Opalka Fix For: JBossAS-6.0.0.M3 There's a naming conflict between http://repository.jboss.org/maven2/apache-xalan/xalan/2.7.1.patch01-brew/ and http://repository.jboss.org/maven2-brew/apache-xalan/xalan/2.7.1.patch02/ We need to create another patched xalan release (that will be identical with 2.7.1.patch01-brew) to ensure naming convention will represent upgrade of the component in EAP. -- 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

15 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-7964) Support paravirtualized Embeddable EJB3

by Andrew Lee Rubinger (JIRA)

Support paravirtualized Embeddable EJB3 --------------------------------------- Key: JBAS-7964 URL: https://jira.jboss.org/jira/browse/JBAS-7964 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: JBossAS-6.0.0.M4 The EJB 3.1 Spec mandates the use of an Embedded API for EJBContainer. In the case of AS, we can piggyback atop resources (ie. MC Kernel) already in place. Bring the JBoss EJBContainer API into AS alongside an integration bit which delegates over to the existing runtime. -- 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

15 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2070) PostConstruct (and PreDestroy) of a singleton bean don't run in a transaction context

by jaikiran pai (JIRA)

PostConstruct (and PreDestroy) of a singleton bean don't run in a transaction context -------------------------------------------------------------------------------------- Key: EJBTHREE-2070 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2070 Project: EJB 3.0 Issue Type: Bug Components: singleton Affects Versions: EJB3_1 1.0.7 Reporter: jaikiran pai Assignee: jaikiran pai The EJB3.1 spec states: 4.8.3 Transaction Semantics of Initialization and Destruction PostConstruct and PreDestroy methods of Singletons with container-managed transactions are transac- tional. From the bean developer's view there is no client of a PostConstruct or PreDestroy method. A PostConstruct or PreDestroy method of a Singleton with container-managed transactions has transac- tion attribute REQUIRED, REQUIRES_NEW, or NOT_SUPPORTED (Required , RequiresNew, or NotSupported if the deployment descriptor is used to specify the transaction attribute). Note that the container must start a new transaction if the REQUIRED (Required) transaction attribute is used. This guarantees, for example, that the transactional behavior of the PostConstruct method is the same regardless of whether it is initialized eagerly at container startup time or as a side effect of a first client invocation on the Singleton. The REQUIRED transaction attribute value is allowed so that specification of a transaction attribute for the Singleton PostConstruct/PreDestroy methods can be defaulted. However, the current implementation of singleton (1.0.0-alpha-2) does *not* run the postconstruct and predestroy methods in a transaction context. -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-760) NPE on Instrumentor.instrumentAnnotationIntroductions

by Flavia Rainone (JIRA)

NPE on Instrumentor.instrumentAnnotationIntroductions ----------------------------------------------------- Key: JBAOP-760 URL: https://jira.jboss.org/jira/browse/JBAOP-760 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.6.GA Reporter: Flavia Rainone Fix For: 2.1.7.GA If you try to introduct an annotation with multiple values omitting the brackets, such as: @SuppressWarnings("all") instead of @SuppressWarnings({"all"}), the result is a NPE: [javac] Compiling 30 source files to C:\Users\Flavia\Documents\cursoAOP\10SCJ\conclusao\4265_38312(2)\dukesbankFinal\dukesbank-ejb\classes [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [aopc] log4j:WARN No appenders could be found for logger (org.jboss.aop.instrument.InstrumentorFactory). [aopc] log4j:WARN Please initialize the log4j system properly. [aopc] java.lang.NullPointerException [aopc] at javassist.bytecode.annotation.ArrayMemberValue.write(ArrayMemberValue.java:132) [aopc] at javassist.bytecode.annotation.Annotation.write(Annotation.java:316) [aopc] at javassist.bytecode.AnnotationsAttribute.setAnnotations(AnnotationsAttribute.java:246) [aopc] at javassist.bytecode.AnnotationsAttribute.addAnnotation(AnnotationsAttribute.java:211) [aopc] at org.jboss.aop.instrument.Instrumentor.instrumentAnnotationIntroductions(Instrumentor.java:462) [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:740) [aopc] at org.jboss.aop.instrument.GeneratedAdvisorInstrumentor.transform(GeneratedAdvisorInstrumentor.java:117) [aopc] at org.jboss.aop.ClassicWeavingStrategy.translate(ClassicWeavingStrategy.java:110) [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:1071) [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:1015) [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:391) [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:243) [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:88) [aopc] java.lang.RuntimeException: failed to transform: com.fiap.tutorial.javaee.dukesbank.request.CustomerControllerBean [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:829) [aopc] at org.jboss.aop.instrument.GeneratedAdvisorInstrumentor.transform(GeneratedAdvisorInstrumentor.java:117) [aopc] at org.jboss.aop.ClassicWeavingStrategy.translate(ClassicWeavingStrategy.java:110) [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:1071) [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:1015) [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:391) [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:243) [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:88) [aopc] Caused by: java.lang.NullPointerException [aopc] at javassist.bytecode.annotation.ArrayMemberValue.write(ArrayMemberValue.java:132) [aopc] at javassist.bytecode.annotation.Annotation.write(Annotation.java:316) [aopc] at javassist.bytecode.AnnotationsAttribute.setAnnotations(AnnotationsAttribute.java:246) [aopc] at javassist.bytecode.AnnotationsAttribute.addAnnotation(AnnotationsAttribute.java:211) [aopc] at org.jboss.aop.instrument.Instrumentor.instrumentAnnotationIntroductions(Instrumentor.java:462) [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:740) [aopc] ... 7 more [aopc] Exception in thread "main" java.lang.RuntimeException: java.lang.RuntimeException: failed to transform: com.fiap.tutorial.javaee.dukesbank.request.CustomerControllerBean [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:1081) [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:1015) [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:391) [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:243) [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:88) [aopc] Caused by: java.lang.RuntimeException: failed to transform: com.fiap.tutorial.javaee.dukesbank.request.CustomerControllerBean [aopc] at org.jboss.aop.instrument.GeneratedAdvisorInstrumentor.transform(GeneratedAdvisorInstrumentor.java:146) [aopc] at org.jboss.aop.ClassicWeavingStrategy.translate(ClassicWeavingStrategy.java:110) [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:1071) [aopc] ... 4 more [aopc] Caused by: java.lang.RuntimeException: failed to transform: com.fiap.tutorial.javaee.dukesbank.request.CustomerControllerBean [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:829) [aopc] at org.jboss.aop.instrument.GeneratedAdvisorInstrumentor.transform(GeneratedAdvisorInstrumentor.java:117) [aopc] ... 6 more [aopc] Caused by: java.lang.NullPointerException [aopc] at javassist.bytecode.annotation.ArrayMemberValue.write(ArrayMemberValue.java:132) [aopc] at javassist.bytecode.annotation.Annotation.write(Annotation.java:316) [aopc] at javassist.bytecode.AnnotationsAttribute.setAnnotations(AnnotationsAttribute.java:246) [aopc] at javassist.bytecode.AnnotationsAttribute.addAnnotation(AnnotationsAttribute.java:211) [aopc] at org.jboss.aop.instrument.Instrumentor.instrumentAnnotationIntroductions(Instrumentor.java:462) [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:740) [aopc] ... 7 more BUILD FAILED -- 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

15 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAOP-761) Create an error message for javassist.NotFoundException

by Flavia Rainone (JIRA)

Create an error message for javassist.NotFoundException ------------------------------------------------------- Key: JBAOP-761 URL: https://jira.jboss.org/jira/browse/JBAOP-761 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.1.6.GA Reporter: Flavia Rainone Fix For: 2.1.7.GA It is very usual users forgetting to write the fully qualified name of a class. We should treat javassist.NotFoundExcpetion, pointing to the user the name of the class that was not found and reminding that the name must be fully qualified: [aopc] Exception in thread "main" java.lang.RuntimeException: java.lang.RuntimeException: failed to transform: com.fiap.tutorial.javaee.dukesbank.request.CustomerControllerBean [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:1081) [aopc] at org.jboss.aop.AspectManager.transform(AspectManager.java:1015) [aopc] at org.jboss.aop.standalone.Compiler.compileFile(Compiler.java:391) [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:243) [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:88) [aopc] Caused by: java.lang.RuntimeException: failed to transform: com.fiap.tutorial.javaee.dukesbank.request.CustomerControllerBean [aopc] at org.jboss.aop.instrument.GeneratedAdvisorInstrumentor.transform(GeneratedAdvisorInstrumentor.java:146) [aopc] at org.jboss.aop.ClassicWeavingStrategy.translate(ClassicWeavingStrategy.java:110) [aopc] at org.jboss.aop.AspectManager.translate(AspectManager.java:1071) [aopc] ... 4 more [aopc] Caused by: java.lang.RuntimeException: failed to transform: com.fiap.tutorial.javaee.dukesbank.request.CustomerControllerBean [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:829) [aopc] at org.jboss.aop.instrument.GeneratedAdvisorInstrumentor.transform(GeneratedAdvisorInstrumentor.java:117) [aopc] ... 6 more [aopc] Caused by: javassist.NotFoundException: DeclareRoles [aopc] at javassist.ClassPool.get(ClassPool.java:436) [aopc] at org.jboss.aop.annotation.compiler.AnnotationInfoCreator.createAnnotationInfo(AnnotationInfoCreator.java:166) [aopc] at org.jboss.aop.instrument.Instrumentor.instrumentAnnotationIntroductions(Instrumentor.java:441) [aopc] at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:740) [aopc] ... 7 more -- 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

15 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAOP-721) Binds with similar pointcut expressions are ignored

by Carlo de Wolf (JIRA)

Binds with similar pointcut expressions are ignored --------------------------------------------------- Key: JBAOP-721 URL: https://jira.jboss.org/jira/browse/JBAOP-721 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.0.GA Environment: Branch_5_x @ 87425 Reporter: Carlo de Wolf Priority: Critical Fix For: 2.1.1.GA, 2.2.0.GA Given the following descriptor: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/ejb3/trunk/co... 04-16-2009 09:47:58: ERROR: java.lang.NullPointerException at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:57) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.RunAsSecurityInterceptorv2.invoke(RunAsSecurityInterceptorv2.java:94) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPolicy.invokeInNoTx(TxPolicy.java:66) at org.jboss.ejb3.tx.TxInterceptor$Never.invoke(TxInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:560) at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:53) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) StatefulInstanceInterceptor is not executed. -- 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

15 years, 8 months

3
18
0 / 0

[JBoss JIRA] Created: (JBAOP-757) Fix findbugs bugs and exclude non-issues in exclude files

by Kabir Khan (JIRA)

Fix findbugs bugs and exclude non-issues in exclude files --------------------------------------------------------- Key: JBAOP-757 URL: https://jira.jboss.org/jira/browse/JBAOP-757 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan -- 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

15 years, 8 months

1
8
0 / 0

[JBoss JIRA] Created: (JBBUILD-552) Track down missing licenses in the app server depenedencies and add them to poms

by Paul Gier (JIRA)

Track down missing licenses in the app server depenedencies and add them to poms -------------------------------------------------------------------------------- Key: JBBUILD-552 URL: https://jira.jboss.org/jira/browse/JBBUILD-552 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Fix For: Maven Build - Maint 2009 All dependencies of AS should have license information in the poms -- 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

15 years, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-7858) Add interceptors processing in MergedJBossMetaDataDeployer

by jaikiran pai (JIRA)

Add interceptors processing in MergedJBossMetaDataDeployer ---------------------------------------------------------- Key: JBAS-7858 URL: https://jira.jboss.org/jira/browse/JBAS-7858 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3 Reporter: jaikiran pai Assignee: jaikiran pai Include interceptors processing for JBossMetadata in MergedJBossMetaDataDeployer. This requires the implementation provided by JBMETA-273 -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-273) Implement an annotation processing mechanism for interceptor classes

by jaikiran pai (JIRA)

Implement an annotation processing mechanism for interceptor classes -------------------------------------------------------------------- Key: JBMETA-273 URL: https://jira.jboss.org/jira/browse/JBMETA-273 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Components: ejb Reporter: jaikiran pai Assignee: jaikiran pai Currently, the interceptor classes which are available in a EJB deployment are *not* scanned for annotation during metadata processing. This leads to an incomplete metadata view (through JBossMetaData.getInterceptors()). We need to implement a mechanism which would allow for processing of annotations on interceptor classes. Furthermore, it should be possible to properly merge the xml based interceptor configuration (in ejb-jar.xml) with the InterceptorsMetadata created out of annotation processing. -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-241) Introduce JNDI name resolvers

by jaikiran pai (JIRA)

Introduce JNDI name resolvers ----------------------------- Key: JBMETA-241 URL: https://jira.jboss.org/jira/browse/JBMETA-241 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ejb Reporter: jaikiran pai Assignee: jaikiran pai Introduce JNDI name resolvers which will be responsible for returning the JNDI names of different views of a bean. The resolvers SPI will use the bean metadata to return the appropriate JNDI name. A default implementation can then use a DefaultJNDIBindingPolicy to implement the SPI. This resolvers will be a first step towards getting rid of the decorated metadata. See the referenced forum thread for more details -- 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

15 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1781) Finalize a contract between no-interface and InvokableContext

by jaikiran pai (JIRA)

Finalize a contract between no-interface and InvokableContext -------------------------------------------------------------- Key: EJBTHREE-1781 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1781 Project: EJB 3.0 Issue Type: Task Components: proxy Reporter: jaikiran pai Assignee: jaikiran pai As part of the fix for EJBTHREE-1777, the SessionProxy has now been removed. The no-interface was responsible for passing this to the InvokableContext for invoking on the context. We need to decide on the new contract. Since the InvokableContext just needs a target (=sessionId), the no-interface can pass this information to the InvokableContext. Need to see how this fits in with the proxy-impl which too relies on the InvokableContext. -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1712) Move the ejb3-embedded deployers to ejb3-deployers

by jaikiran pai (JIRA)

Move the ejb3-embedded deployers to ejb3-deployers --------------------------------------------------- Key: EJBTHREE-1712 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1712 Project: EJB 3.0 Issue Type: Sub-task Components: deployers, embedded Affects Versions: 1.0.0-GA Reporter: jaikiran pai Assignee: jaikiran pai For the profile3_1 component to reuse the deployers available in ejb3-embedded, the deployers need to be moved to the ejb3-deployers. That way we can depend on ejb3-deployers instead of adding a dependency on ejb3-embedded. -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1454) Encapsulate Container infomation in TO/VO

by Andrew Lee Rubinger (JIRA)

Encapsulate Container infomation in TO/VO ----------------------------------------- Key: EJBTHREE-1454 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1454 Project: EJB 3.0 Issue Type: Task Components: proxy Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Take for instance: public StatefulSessionProxyFactoryBase(final String name, final String containerName, final String containerGuid, final JBossSessionBeanMetaData metadata, final ClassLoader classloader, final Advisor advisor) Where containerName, containerGuid, metadata, CL, and Advisor are all properties of the target container. This makes for a cluttered API, and affects constructors of Proxy Factories, Handlers, and the JNDI Registrars. Clean it up. -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-909) Injection of Simple Environment Entries Using Resource Annotation without name

by Roland R?z (JIRA)

Injection of Simple Environment Entries Using Resource Annotation without name ------------------------------------------------------------------------------ Key: EJBTHREE-909 URL: http://jira.jboss.com/jira/browse/EJBTHREE-909 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Roland R?z The name of the @Resource annotations should default to the property or method name. The following simple environment injections are not working as expected: @Resource String stringValue; Long longValue = Long.valueOf(1); @Resource void setLongValue(Long longValue) { this.longValue = longValue; } Workaround: @Resource(name = "stringValue") String stringValue = "hi"; Long longValue = Long.valueOf(1); @Resource(name = "longValue") public void setIntValue(Long longValue) { this.longValue = longValue; } -- 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

15 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (SECURITY-437) Tag JBoss Negotiation 2.0.3.SP2

by Darran Lofthouse (JIRA)

Tag JBoss Negotiation 2.0.3.SP2 ------------------------------- Key: SECURITY-437 URL: https://jira.jboss.org/jira/browse/SECURITY-437 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.3.SP2 -- 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

15 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-7880) HornetQ ConnectionFactory is not serializable

by Carlo de Wolf (JIRA)

HornetQ ConnectionFactory is not serializable --------------------------------------------- Key: JBAS-7880 URL: https://jira.jboss.org/jira/browse/JBAS-7880 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (HornetQ) Reporter: Carlo de Wolf Assignee: Clebert Suconic Fix For: JBossAS-6.0.0.M3 java.io.NotSerializableException: org.hornetq.ra.inflow.HornetQActivationSpec - custom writeObject data (class "java.util.concurrent.ConcurrentHashMap") - object (class "java.util.concurrent.ConcurrentHashMap", {org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@5aaf85a3 destination=queue/mdbtest destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxMessages=1 minSession=1 maxSession=1)=org.hornetq.ra.inflow.HornetQActivation(spec=org.hornetq.ra.inflow.HornetQActivationSpec mepf=org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory active=true destination=queue/mdbtest transacted=true), org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@5aaf85a3 destination=queue/consumertest destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxMessages=1 minSession=1 maxSession=15)=org.hornetq.ra.inflow.HornetQActivation(spec=org.hornetq.ra.inflow.HornetQActivationSpec mepf=org.jboss.ejb3.mdb.inflow.JBossMessageEndpointFactory active=true destination=queue/consumertest transacted=true)}) - field (class "org.hornetq.ra.HornetQResourceAdapter", name: "activations", type: "interface java.util.Map") - object (class "org.hornetq.ra.HornetQResourceAdapter", org.hornetq.ra.HornetQResourceAdapter@5aaf85a3) - field (class "org.hornetq.ra.HornetQRAManagedConnectionFactory", name: "ra", type: "class org.hornetq.ra.HornetQResourceAdapter") - object (class "org.hornetq.ra.HornetQRAManagedConnectionFactory", org.hornetq.ra.HornetQRAManagedConnectionFactory@8f0e844) - field (class "org.hornetq.ra.HornetQRAConnectionFactoryImpl", name: "mcf", type: "class org.hornetq.ra.HornetQRAManagedConnectionFactory") - object (class "org.hornetq.ra.HornetQRAConnectionFactoryImpl", org.hornetq.ra.HornetQRAConnectionFactoryImpl@70907b6) - writeExternal data - object (class "org.jboss.ejb3.mdb.ProducerManagerImpl", org.jboss.ejb3.mdb.ProducerManagerImpl@7957f145) - element of array (index: 0) - array (class "[Lorg.jboss.aop.advice.Interceptor;", size: 1) - field (class "org.jboss.ejb3.mdb.ProducerProxy", name: "interceptors", type: "class [Lorg.jboss.aop.advice.Interceptor;") - object (class "org.jboss.ejb3.mdb.ProducerProxy", org.jboss.ejb3.mdb.ProducerProxy@2e195683) - field (class "java.lang.reflect.Proxy", name: "h", type: "interface java.lang.reflect.InvocationHandler") - root object (class "$Proxy139", org.jboss.ejb3.mdb.ProducerProxy@2e195683) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1153) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) at java.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1246) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) at org.jboss.ejb3.mdb.ProducerManagerImpl.writeExternal(ProducerManagerImpl.java:95) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1421) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1390) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1338) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1146) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) at java.rmi.MarshalledObject.<init>(MarshalledObject.java:101) at org.jnp.interfaces.MarshalledValuePair.<init>(MarshalledValuePair.java:65) at org.jboss.ejb3.proxy.JndiSessionProxyObjectFactory.getObjectInstance(JndiSessionProxyObjectFactory.java:119) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) -- 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

15 years, 8 months

7
23
0 / 0

[JBoss JIRA] Created: (JBAS-4363) OSGi Bundle Repository support

by Scott M Stark (JIRA)

OSGi Bundle Repository support ------------------------------ Key: JBAS-4363 URL: http://jira.jboss.com/jira/browse/JBAS-4363 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 The OSGi Bundle Repository support requirements need to be considered. -- 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

15 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (JBASM-36) Set system prop jboss.boot.server.log.level=DEBUG

by Brian Stansberry (JIRA)

Set system prop jboss.boot.server.log.level=DEBUG ------------------------------------------------- Key: JBASM-36 URL: https://jira.jboss.org/jira/browse/JBASM-36 Project: JBoss AS Server Manager Issue Type: Feature Request Reporter: Brian Stansberry Assignee: Shelly McGowan Priority: Minor See http://community.jboss.org/wiki/JBossBootLogging for background Property jboss.boot.server.log.level controls what goes in the boot.log, which currently covers almost the entire server start. AS trunk now has this logging at INFO by default, which means we don't see much startup detail in testsuite logs. Setting jboss.boot.server.log.level=DEBUG will restore the level of startp/shutdown logging we were seeing in 6.0.0.M1 and Branch_5_x. -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBASM-35) CLONE -Allow execution of server:stop for servers that aren't running

by Shelly McGowan (JIRA)

CLONE -Allow execution of server:stop for servers that aren't running --------------------------------------------------------------------- Key: JBASM-35 URL: https://jira.jboss.org/jira/browse/JBASM-35 Project: JBoss AS Server Manager Issue Type: Feature Request Reporter: Brian Stansberry Assignee: Shelly McGowan Fix For: 1.0.3.GA See JBAS-7582 for the use case. If you call server:stop passing the name of a server that isn't running, an ISE is thrown, blowing up the overall testsuite run: exec-jbmcluster: [junit] Running org.jboss.test.jbossmessaging.clustertest.ClusteredTestCase [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 19.861 sec [server:stop] Shutting down server: jbm-cluster1 [server:stop] shutdownTimeout will be=45 [server:stop] Server stopped. BUILD FAILED java.lang.IllegalArgumentException: The jbm-cluster2 is not running; it cannot be stopped. at org.jboss.jbossas.servermanager.ServerController.stopServer(ServerController.java:377) at org.jboss.jbossas.servermanager.ServerManager.stopServer(ServerManager.java:174) at org.jboss.ant.taskdefs.server.StopServerTask.stopServer(StopServerTask.java:74) at org.jboss.ant.taskdefs.server.StopServerTask.execute(StopServerTask.java:61) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:357) at org.apache.tools.ant.Target.performTasks(Target.java:385) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337) at org.apache.tools.ant.Project.executeTarget(Project.java:1306) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1189) at org.apache.tools.ant.Main.runBuild(Main.java:758) at org.apache.tools.ant.Main.startAnt(Main.java:217) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) I request that this condition be handled with a log message rather than an ISE. -- 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

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBASM-32) Revert explicit System Property "xb.builder.useUnorderedSequence=true" when possible

by Andrew Lee Rubinger (JIRA)

Revert explicit System Property "xb.builder.useUnorderedSequence=true" when possible ------------------------------------------------------------------------------------ Key: JBASM-32 URL: https://jira.jboss.org/jira/browse/JBASM-32 Project: JBoss AS Server Manager Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger When it won't throw errors, revert JBASM-30. -- 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

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBASM-37) change "thread dump" capability as needed due to changes in JBAS-7825

by Scott Marlow (JIRA)

change "thread dump" capability as needed due to changes in JBAS-7825 --------------------------------------------------------------------- Key: JBASM-37 URL: https://jira.jboss.org/jira/browse/JBASM-37 Project: JBoss AS Server Manager Issue Type: Task Reporter: Scott Marlow Assignee: Shelly McGowan -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-7460) Detect version from persistence.xml files and pass it to the JPA 2 provider

by Emmanuel Bernard (JIRA)

Detect version from persistence.xml files and pass it to the JPA 2 provider --------------------------------------------------------------------------- Key: JBAS-7460 URL: https://jira.jboss.org/jira/browse/JBAS-7460 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Reporter: Emmanuel Bernard Assignee: Carlo de Wolf Fix For: JBossAS-6.0.0.M2 -- 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

15 years, 8 months

6
21
0 / 0

[JBoss JIRA] Created: (JGRP-1166) Fix processing of Windows batch file arguments

by Richard Achmatowicz (JIRA)

Fix processing of Windows batch file arguments ---------------------------------------------- Key: JGRP-1166 URL: https://jira.jboss.org/jira/browse/JGRP-1166 Project: JGroups Issue Type: Bug Affects Versions: 2.9, 2.8, 2.6.14, 2.4.8 Environment: Windows Reporter: Richard Achmatowicz Assignee: Bela Ban The file build.bat can sometimes take a rather long set of command line arguments, due to specification of JVM system properties; for example, $ build.bat -Djgroups.bind_addr=%MYTESTIP_1% -Djgroups.udp.mcast_addr=%MCAST_ADDR% -Djgroups.tcpping.initial_hosts="%MYTESTIP_1%[7800],%MYTESTIP_1[7801]" all-tests-functional Windows batch files provide positional parameters %0 through %9 to collect the first nine arguments. Windows batch files also process a single parameter -Dfred=barney as two parameters -Dfred and barney. This leads to a limit on the number of system properties we can pass to the build.bat file, due to the way the command line arguments are processed (i.e. using the maximum number of positional parameters). In the worst case, some system properties get lost. One way to fix this is to gather together the all the command line arguments using the shift operator and store them in a variable, BUILD_ARGS. Here is the code: REM ****************************************************** REM ********Save the command line arguments*************** REM ****************************************************** set BUILD_ARGS=%1 if ""%1""=="""" goto completedArgs shift :processArg if ""%1""=="""" goto completedArgs set BUILD_ARGS=%BUILD_ARGS% %1 shift goto processArg :completedArgs The variable BUILD_ARGS can then be passed to the %JAVA_HOME%\bin\java -classpath "%CP%" org.apache.tools.ant.Main -buildfile build.xml %BUILD_ARGS% This gets rid of the limit on command line parameters for batch files. -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-1142) Introduce compaibility testing into the JGroups testsuite

by Richard Achmatowicz (JIRA)

Introduce compaibility testing into the JGroups testsuite --------------------------------------------------------- Key: JGRP-1142 URL: https://jira.jboss.org/jira/browse/JGRP-1142 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Richard Achmatowicz Assignee: Richard Achmatowicz The dgree to which JGroups versions interoperate is determined by their stated compatibility relationships. The purpose of this issue is to: (i) clarify the desired backward compatibility conditions in use for JGroups (ii) devise tests which validate those relationships and incorporate them into the JGroups testsuite -- 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

15 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-6923) jboss provides wrong mailsession properties when multiple mailservices are deployed

by Stefan Schueffler (JIRA)

jboss provides wrong mailsession properties when multiple mailservices are deployed ----------------------------------------------------------------------------------- Key: JBAS-6923 URL: https://jira.jboss.org/jira/browse/JBAS-6923 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.0.0.GA Environment: linux (opensuse 11.1) 64bit Reporter: Stefan Schueffler Having more than one MailService deployed (regardless if they are located each in its own xml-file, or if they are combined into one xml-file containing all the mail-related mbeans), jboss returns the wrong properties when retrieving a javax.mail.Session from jndi-context. After deployment of at least two or more MailService-mbeans, using the jmx-console or twiddle.sh reveals the correct values for the properties in the different MailServices. But: a javax.mail.Session retrieved from jndi-context always is initialized with the properties of the last deployed MailService, regardless of which of the existing jndi-names is used to lookup this particular mailsession. Having multiple, different MailServices worked fine in jboss-4.3.x. This could somehow be related to JBAS-5896 -- 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

15 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-3778) AttributePersistenceService does not allow absolute path for data-directory value

by Darran Lofthouse (JIRA)

AttributePersistenceService does not allow absolute path for data-directory value --------------------------------------------------------------------------------- Key: JBAS-3778 URL: http://jira.jboss.com/jira/browse/JBAS-3778 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.4.GA Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: JBossAS-4.0.6.CR1 AttributePersistenceService does not allow absolute path for data-directory value, any value specified even with a leading '/' is created within the folder of the configuration being executed. Also the default configuration in the jboss-service.xml should take into account the setting for jboss.server.data.dir -- 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

15 years, 8 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-7824) Uncommenting both filter and filter-mapping elements in jmx-console.war\WEB-INF\web.xml results an xml parsing exception

by Radim Hanus (JIRA)

Uncommenting both filter and filter-mapping elements in jmx-console.war\WEB-INF\web.xml results an xml parsing exception ------------------------------------------------------------------------------------------------------------------------ Key: JBAS-7824 URL: https://jira.jboss.org/jira/browse/JBAS-7824 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.1.0.GA Reporter: Radim Hanus Assignee: Darran Lofthouse Priority: Minor I've tried to apply wiki document http://community.jboss.org/wiki/AccessControlForJMXConsole but it produces exception during startup because of order of elements in jmx-console.war\WEB-INF\web.xml: <filter> <filter-name>JmxOpsAccessControlFilter</filter-name> <filter-class>org.jboss.jmx.adaptor.html.JMXOpsAccessControlFilter</filter-class> <init-param> <param-name>updateAttributes</param-name> <param-value>UpdateAttributeRole</param-value> <description>Comma-delimited Roles that define the JMX Operation denoting updation of Attributes</description> </init-param> <init-param> <param-name>invokeOp</param-name> <param-value>InvokeOpRole</param-value> <description>Comma-delimited Roles that define the JMX Operation denoting updation of Attributes</description> </init-param> </filter> <filter-mapping> <filter-name>JmxOpsAccessControlFilter</filter-name> <servlet-name>HtmlAdaptor</servlet-name> </filter-mapping> but in accordance with javaee_5.xsd schema element description should be the first emelent of init-param: ... <init-param> <description>Comma-delimited Roles that define the JMX Operation denoting updation of Attributes</description> <param-name>updateAttributes</param-name> <param-value>UpdateAttributeRole</param-value> </init-param> ... org.jboss.xb.binding.JBossXBException: Failed to parse source: cvc-complex-type.2.4.d: Invalid content was found starting with element 'description'. -- 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

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6845) Queue.jsp does not compile

by Shawn Kerstetter (JIRA)

Queue.jsp does not compile -------------------------- Key: JBAS-6845 URL: https://jira.jboss.org/jira/browse/JBAS-6845 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.0.1.GA Reporter: Shawn Kerstetter Assignee: Darran Lofthouse Priority: Minor I get the following error when using the web console to drill down to a Q that I created: web-console --> jboss domains --> jboss --> j2ee resources --> local jms --> queues --> <my_email_queue> [exec] 16:41:02,476 ERROR [[jsp]] Servlet.service() for servlet jsp threw e xception [exec] org.apache.jasper.JasperException: Unable to compile class for JSP: [exec] [exec] An error occurred at line: 10 in the jsp file: /Queue.jsp [exec] MessageCounter cannot be resolved to a type [exec] 7: <% [exec] 8: String resetUrl = response.encodeURL(request.getRequestURI()) + "?doReset=true&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("O bjectName")); [exec] 9: String myUrl = response.encodeURL(request.getRequestURI()) + "?" + "&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName" )); [exec] 10: MessageCounter counter = queue.getMessageCounter()[0]; [exec] 11: [exec] 12: //check reset first [exec] 13: String doReset = request.getParameter("doReset"); [exec] [exec] [exec] An error occurred at line: 10 in the jsp file: /Queue.jsp [exec] The method getMessageCounter() is undefined for the type QueueMBean [exec] 7: <% [exec] 8: String resetUrl = response.encodeURL(request.getRequestURI()) + "?doReset=true&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("O bjectName")); [exec] 9: String myUrl = response.encodeURL(request.getRequestURI()) + "?" + "&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName" )); [exec] 10: MessageCounter counter = queue.getMessageCounter()[0]; [exec] 11: [exec] 12: //check reset first [exec] 13: String doReset = request.getParameter("doReset"); [exec] [exec] [exec] An error occurred at line: 53 in the jsp file: /Queue.jsp [exec] The method getQueueName() is undefined for the type QueueMBean [exec] 50: <div class="content_block" style="width: 95%; he ight: 95%"> [exec] 51: <h3>JMS Queue</h3> [exec] 52: <h4>Name</h4> [exec] 53: <p><%=queue.getQueueName()%></p> [exec] 54: <h4>JNDI Name</h4> [exec] 55: <p><%=queue.getJNDIName()%></p> [exec] 56: <h4>Receiver Count</h4> [exec] [exec] [exec] An error occurred at line: 57 in the jsp file: /Queue.jsp [exec] The method getReceiversCount() is undefined for the type QueueMBean [exec] 54: <h4>JNDI Name</h4> [exec] 55: <p><%=queue.getJNDIName()%></p> [exec] 56: <h4>Receiver Count</h4> [exec] 57: <p><%=queue.getReceiversCount()% ></p> [exec] 58: <h4>Message statistics:</h4> [exec] 59: <table border="1" cellpadding="0" cellsp acing="0" class="data_table" bordercolor="#111111" width="95%" align="center" id ="AutoNumber1"> [exec] 60: <tr> [exec] [exec] [exec] An error occurred at line: 72 in the jsp file: /Queue.jsp [exec] The method getQueueDepth() is undefined for the type QueueMBean [exec] 69: </td> [exec] 70: </tr> [exec] 71: <tr align="center"> [exec] 72: <td><%=queue.getQueueDepth()%></td> [exec] 73: <td><%=counter.getDepthDelta()%></td> [exec] 74: <td><%=queue.getMaxDepth()%></td> [exec] 75: </tr> [exec] [exec] [exec] An error occurred at line: 74 in the jsp file: /Queue.jsp [exec] The method getMaxDepth() is undefined for the type QueueMBean [exec] 71: <tr align="center"> [exec] 72: <td><%=queue.getQueueDepth()%></td> [exec] 73: <td><%=counter.getDepthDelta()%></td> [exec] 74: <td><%=queue.getMaxDepth()%></td> [exec] 75: </tr> [exec] 76: </table> [exec] 77: <p> </p> [exec] [exec] [exec] Stacktrace: [exec] at org.apache.jasper.compiler.DefaultErrorHandler.javacError(Def aultErrorHandler.java:92) [exec] at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDi spatcher.java:330) [exec] at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompi ler.java:439) [exec] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:335 ) [exec] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:313 ) [exec] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:300 ) [exec] at org.apache.jasper.JspCompilationContext.compile(JspCompilatio nContext.java:585) [exec] at org.apache.jasper.servlet.JspServletWrapper.service(JspServle tWrapper.java:312) [exec] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServle t.java:322) [exec] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java: 249) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFil ter(ApplicationFilterChain.java:290) [exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl icationFilterChain.java:206) [exec] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(Reply HeaderFilter.java:96) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFil ter(ApplicationFilterChain.java:235) [exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl icationFilterChain.java:206) [exec] at org.apache.catalina.core.StandardWrapperValve.invoke(Standard WrapperValve.java:235) [exec] at org.apache.catalina.core.StandardContextValve.invoke(Standard ContextValve.java:191) [exec] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke (SecurityAssociationValve.java:190) [exec] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccCon textValve.java:92) [exec] at org.jboss.web.tomcat.security.SecurityContextEstablishmentVal ve.process(SecurityContextEstablishmentValve.java:126) [exec] at org.jboss.web.tomcat.security.SecurityContextEstablishmentVal ve.invoke(SecurityContextEstablishmentValve.java:70) [exec] at org.apache.catalina.core.StandardHostValve.invoke(StandardHos tValve.java:127) [exec] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepor tValve.java:102) [exec] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke (CachedConnectionValve.java:158) [exec] at org.apache.catalina.core.StandardEngineValve.invoke(StandardE ngineValve.java:109) [exec] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAda pter.java:330) [exec] at org.apache.coyote.http11.Http11Processor.process(Http11Proces sor.java:829) [exec] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandl er.process(Http11Protocol.java:601) [exec] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint .java:447) [exec] at java.lang.Thread.run(Thread.java:619) [exec] 16:41:02,492 ERROR [[jsp]] Servlet.service() for servlet jsp threw e xception [exec] java.lang.ClassNotFoundException: org.apache.jsp.Queue_jsp [exec] at java.net.URLClassLoader$1.run(URLClassLoader.java:200) [exec] at java.security.AccessController.doPrivileged(Native Method) [exec] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [exec] at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader .java:135) [exec] at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader .java:67) [exec] at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInst ance(TomcatInjectionContainer.java:271) [exec] at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspSer vletWrapper.java:145) [exec] at org.apache.jasper.servlet.JspServletWrapper.service(JspServle tWrapper.java:324) [exec] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServle t.java:322) [exec] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java: 249) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFil ter(ApplicationFilterChain.java:290) [exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl icationFilterChain.java:206) [exec] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(Reply HeaderFilter.java:96) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFil ter(ApplicationFilterChain.java:235) [exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl icationFilterChain.java:206) [exec] at org.apache.catalina.core.StandardWrapperValve.invoke(Standard WrapperValve.java:235) [exec] at org.apache.catalina.core.StandardContextValve.invoke(Standard ContextValve.java:191) [exec] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke (SecurityAssociationValve.java:190) [exec] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccCon textValve.java:92) [exec] at org.jboss.web.tomcat.security.SecurityContextEstablishmentVal ve.process(SecurityContextEstablishmentValve.java:126) [exec] at org.jboss.web.tomcat.security.SecurityContextEstablishmentVal ve.invoke(SecurityContextEstablishmentValve.java:70) [exec] at org.apache.catalina.core.StandardHostValve.invoke(StandardHos tValve.java:127) [exec] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepor tValve.java:102) [exec] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke (CachedConnectionValve.java:158) [exec] at org.apache.catalina.core.StandardEngineValve.invoke(StandardE ngineValve.java:109) [exec] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAda pter.java:330) [exec] at org.apache.coyote.http11.Http11Processor.process(Http11Proces sor.java:829) [exec] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandl er.process(Http11Protocol.java:601) [exec] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint .java:447) [exec] at java.lang.Thread.run(Thread.java:619) [exec] 16:41:08,492 ERROR [[jsp]] Servlet.service() for servlet jsp threw e xception [exec] java.lang.ClassNotFoundException: org.apache.jsp.Queue_jsp [exec] at java.net.URLClassLoader$1.run(URLClassLoader.java:200) [exec] at java.security.AccessController.doPrivileged(Native Method) [exec] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [exec] at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader .java:135) [exec] at org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader .java:67) [exec] at org.jboss.web.tomcat.service.TomcatInjectionContainer.newInst ance(TomcatInjectionContainer.java:271) [exec] at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspSer vletWrapper.java:145) [exec] at org.apache.jasper.servlet.JspServletWrapper.service(JspServle tWrapper.java:324) [exec] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServle t.java:322) [exec] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java: 249) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFil ter(ApplicationFilterChain.java:290) [exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl icationFilterChain.java:206) [exec] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(Reply HeaderFilter.java:96) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFil ter(ApplicationFilterChain.java:235) [exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl icationFilterChain.java:206) [exec] at org.apache.catalina.core.StandardWrapperValve.invoke(Standard WrapperValve.java:235) [exec] at org.apache.catalina.core.StandardContextValve.invoke(Standard ContextValve.java:191) [exec] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke (SecurityAssociationValve.java:190) [exec] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccCon textValve.java:92) [exec] at org.jboss.web.tomcat.security.SecurityContextEstablishmentVal ve.process(SecurityContextEstablishmentValve.java:126) [exec] at org.jboss.web.tomcat.security.SecurityContextEstablishmentVal ve.invoke(SecurityContextEstablishmentValve.java:70) [exec] at org.apache.catalina.core.StandardHostValve.invoke(StandardHos tValve.java:127) [exec] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepor tValve.java:102) [exec] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke (CachedConnectionValve.java:158) [exec] at org.apache.catalina.core.StandardEngineValve.invoke(StandardE ngineValve.java:109) [exec] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAda pter.java:330) [exec] at org.apache.coyote.http11.Http11Processor.process(Http11Proces sor.java:829) [exec] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandl er.process(Http11Protocol.java:601) [exec] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint .java:447) [exec] at java.lang.Thread.run(Thread.java:619) [exec] 16:41:08,492 ERROR [[jsp]] Servlet.service() for servlet jsp threw e xception [exec] org.apache.jasper.JasperException: Unable to compile class for JSP: [exec] [exec] An error occurred at line: 10 in the jsp file: /Queue.jsp [exec] MessageCounter cannot be resolved to a type [exec] 7: <% [exec] 8: String resetUrl = response.encodeURL(request.getRequestURI()) + "?doReset=true&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("O bjectName")); [exec] 9: String myUrl = response.encodeURL(request.getRequestURI()) + "?" + "&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName" )); [exec] 10: MessageCounter counter = queue.getMessageCounter()[0]; [exec] 11: [exec] 12: //check reset first [exec] 13: String doReset = request.getParameter("doReset"); [exec] [exec] [exec] An error occurred at line: 10 in the jsp file: /Queue.jsp [exec] The method getMessageCounter() is undefined for the type QueueMBean [exec] 7: <% [exec] 8: String resetUrl = response.encodeURL(request.getRequestURI()) + "?doReset=true&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("O bjectName")); [exec] 9: String myUrl = response.encodeURL(request.getRequestURI()) + "?" + "&ObjectName=" + java.net.URLEncoder.encode(request.getParameter("ObjectName" )); [exec] 10: MessageCounter counter = queue.getMessageCounter()[0]; [exec] 11: [exec] 12: //check reset first [exec] 13: String doReset = request.getParameter("doReset"); [exec] [exec] [exec] An error occurred at line: 53 in the jsp file: /Queue.jsp [exec] The method getQueueName() is undefined for the type QueueMBean [exec] 50: <div class="content_block" style="width: 95%; he ight: 95%"> [exec] 51: <h3>JMS Queue</h3> [exec] 52: <h4>Name</h4> [exec] 53: <p><%=queue.getQueueName()%></p> [exec] 54: <h4>JNDI Name</h4> [exec] 55: <p><%=queue.getJNDIName()%></p> [exec] 56: <h4>Receiver Count</h4> [exec] [exec] [exec] An error occurred at line: 57 in the jsp file: /Queue.jsp [exec] The method getReceiversCount() is undefined for the type QueueMBean [exec] 54: <h4>JNDI Name</h4> [exec] 55: <p><%=queue.getJNDIName()%></p> [exec] 56: <h4>Receiver Count</h4> [exec] 57: <p><%=queue.getReceiversCount()% ></p> [exec] 58: <h4>Message statistics:</h4> [exec] 59: <table border="1" cellpadding="0" cellsp acing="0" class="data_table" bordercolor="#111111" width="95%" align="center" id ="AutoNumber1"> [exec] 60: <tr> [exec] [exec] [exec] An error occurred at line: 72 in the jsp file: /Queue.jsp [exec] The method getQueueDepth() is undefined for the type QueueMBean [exec] 69: </td> [exec] 70: </tr> [exec] 71: <tr align="center"> [exec] 72: <td><%=queue.getQueueDepth()%></td> [exec] 73: <td><%=counter.getDepthDelta()%></td> [exec] 74: <td><%=queue.getMaxDepth()%></td> [exec] 75: </tr> [exec] [exec] [exec] An error occurred at line: 74 in the jsp file: /Queue.jsp [exec] The method getMaxDepth() is undefined for the type QueueMBean [exec] 71: <tr align="center"> [exec] 72: <td><%=queue.getQueueDepth()%></td> [exec] 73: <td><%=counter.getDepthDelta()%></td> [exec] 74: <td><%=queue.getMaxDepth()%></td> [exec] 75: </tr> [exec] 76: </table> [exec] 77: <p> </p> [exec] [exec] [exec] Stacktrace: [exec] at org.apache.jasper.compiler.DefaultErrorHandler.javacError(Def aultErrorHandler.java:92) [exec] at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDi spatcher.java:330) [exec] at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompi ler.java:439) [exec] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:335 ) [exec] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:313 ) [exec] at org.apache.jasper.compiler.Compiler.compile(Compiler.java:300 ) [exec] at org.apache.jasper.JspCompilationContext.compile(JspCompilatio nContext.java:585) [exec] at org.apache.jasper.servlet.JspServletWrapper.service(JspServle tWrapper.java:312) [exec] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServle t.java:322) [exec] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java: 249) [exec] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFil ter(ApplicationFilterChain.java:290) [exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl icationFilterChain.java:206) [exec] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(Reply HeaderFilter.java:96) [exec] at org.apache.catalina.core.ApplicationFilterChain.internalDoFil ter(ApplicationFilterChain.java:235) [exec] at org.apache.catalina.core.ApplicationFilterChain.doFilter(Appl icationFilterChain.java:206) [exec] at org.apache.catalina.core.StandardWrapperValve.invoke(Standard WrapperValve.java:235) [exec] at org.apache.catalina.core.StandardContextValve.invoke(Standard ContextValve.java:191) [exec] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke (SecurityAssociationValve.java:190) [exec] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccCon textValve.java:92) [exec] at org.jboss.web.tomcat.security.SecurityContextEstablishmentVal ve.process(SecurityContextEstablishmentValve.java:126) [exec] at org.jboss.web.tomcat.security.SecurityContextEstablishmentVal ve.invoke(SecurityContextEstablishmentValve.java:70) [exec] at org.apache.catalina.core.StandardHostValve.invoke(StandardHos tValve.java:127) [exec] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorRepor tValve.java:102) [exec] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke (CachedConnectionValve.java:158) [exec] at org.apache.catalina.core.StandardEngineValve.invoke(StandardE ngineValve.java:109) [exec] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAda pter.java:330) [exec] at org.apache.coyote.http11.Http11Processor.process(Http11Proces sor.java:829) [exec] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandl er.process(Http11Protocol.java:601) [exec] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint .java:447) [exec] at java.lang.Thread.run(Thread.java:619) -- 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

15 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-7654) Add methods to ServerInfo to format thread dumps to be read by analysis tools

by Mike Clark (JIRA)

Add methods to ServerInfo to format thread dumps to be read by analysis tools ----------------------------------------------------------------------------- Key: JBAS-7654 URL: https://jira.jboss.org/jira/browse/JBAS-7654 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-6.0.0.M1, JBossAS-5.1.0.GA, JBossAS-6.0.0.GA Reporter: Mike Clark Assignee: Darran Lofthouse This is a follow-up to JBAS-5163. The listThreadDump operation of org.jboss.system.server.ServerInfo outputs the thread stack in a JBoss speicifc format. It would be quite useful to be able to output the thread stack formatted so that it could be read by tools such as TDA and Samurai for analysis. This could be accomplished by adding appropriate methods to the ServerInfo/ServerInfoMBean. -- 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

15 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (SECURITY-353) JBoss Portal Integration

by Darran Lofthouse (JIRA)

JBoss Portal Integration ------------------------ Key: SECURITY-353 URL: https://jira.jboss.org/jira/browse/SECURITY-353 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4.GA -- 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

15 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7060) Unable to set attributes for MBeans with quoted object name

by Jeff Mesnil (JIRA)

Unable to set attributes for MBeans with quoted object name ----------------------------------------------------------- Key: JBAS-7060 URL: https://jira.jboss.org/jira/browse/JBAS-7060 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.1.0.GA Reporter: Jeff Mesnil Assignee: Darran Lofthouse While integration JBoss Messaging 2.0.0.Beta3 to AS 5.1.0.GA, I found an issue when I want to update attributes for one of our MBeans which has a quoted ObjectName. The ObjectName is not properly encoded by the Servlet and an exception is thrown by the MBean registry which claims the mbean is not registered. The ObjectName is: module=JMS,name="DLQ",type=Queue - the *name* value is quoted When I display this mbean in the jmx console, the corresponding form to update the attributes has a field: <input type="hidden" name="name" value="org.jboss.messaging:module=JMS,type=Queue,name="DLQ"" /> The quotes of the ObjectNames are not properly encoded which results in a bogus object name when applying changes: 0:57:16,082 ERROR [[HtmlAdaptor]] "Servlet.service()" pour la servlet HtmlAdaptor a genere une exception javax.management.InstanceNotFoundException: org.jboss.messaging:module=JMS,type=Queue,name= is not registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:526) at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:675) at org.jboss.jmx.adaptor.control.Server.setAttributes(Server.java:172) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet$5.run(HtmlAdaptorServlet.java:403) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet$5.run(HtmlAdaptorServlet.java:401) at java.security.AccessController.doPrivileged(Native Method) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.setAttributes(HtmlAdaptorServlet.java:399) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.updateAttributes(HtmlAdaptorServlet.java:259) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:102) at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:86) This bug prevents to update many MBeans required to managed properly JBoss Messaging when it is integrated in the AS. -- 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

15 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7006) Error starting JMS Destination service via AS admin console

by Howard Gao (JIRA)

Error starting JMS Destination service via AS admin console ----------------------------------------------------------- Key: JBAS-7006 URL: https://jira.jboss.org/jira/browse/JBAS-7006 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.1.0.GA Reporter: Howard Gao Assignee: Darran Lofthouse To reproduce: 1. deploy a queue service in AS_home/server/all/deploy/messaging/destinations-service.xml 2. start AS : run.sh -c all 3. log in to JBoss AS Administration Console, click 'JMS Destinations' then 'Queues'. 4. Then click the queue on the right pane. Client the 'Control' tab. 5. first click 'stop' operation, it will result in success. Then click 'start', it will fail with the following log message: java.lang.reflect.UndeclaredThrowableException: Failed to invoke method 'start' on component 'jboss.messaging.destination:name=123456789012345,service=Queue' with parameters []. at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:201) at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:69) 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:597) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1724) at org.jboss.remoting.Client.invoke(Client.java:629) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aop.generatedproxies.AOPProxy$0.invoke(AOPProxy$0.java) at org.jboss.profileservice.management.ManagedOperationDelegate.invoke(ManagedOperationDelegate.java:64) at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:159) 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:597) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException: No such context: jboss.messaging.destination:name=123456789012345,service=Queue at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:51) at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.invoke(BasicKernelBus.java:92) at org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.invoke(KernelBusRuntimeComponentDispatcher.java:186) at org.jboss.profileservice.management.DelegatingComponentDispatcherImpl.invoke(DelegatingComponentDispatcherImpl.java:69) 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:597) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1724) at org.jboss.remoting.Client.invoke(Client.java:629) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aop.generatedproxies.AOPProxy$0.invoke(AOPProxy$0.java) at org.jboss.profileservice.management.ManagedOperationDelegate.invoke(ManagedOperationDelegate.java:64) at org.rhq.plugins.jbossas5.ManagedComponentComponent.invokeOperation(ManagedComponentComponent.java:159) 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:597) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:482) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) ... 18 more -- 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

15 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-6776) JMX Console render empty page for mbean with UTF-8 chars in attributes description or values

by MariuszS (JIRA)

JMX Console render empty page for mbean with UTF-8 chars in attributes description or values -------------------------------------------------------------------------------------------- Key: JBAS-6776 URL: https://jira.jboss.org/jira/browse/JBAS-6776 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.0.1.GA Environment: JDK6, WindowsXP Reporter: MariuszS Assignee: Darran Lofthouse Using UTF-8 chars (example polish char coded properly in UTF-8) in java code or xmbeans xml description cause JMX Console view to break. JMX MBean View Frame is simply empty. There is no log error, warning etc. This work pretty well in JBoss 4.x series. As workaround I can remove all UTF-8 chars from xml definition of mbeans (convert to ISO-8859-1), but this not work for value of attributes. -- 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

15 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-7207) JMX web console causes 500 error when MBeans throw exceptions

by Russ Hayward (JIRA)

JMX web console causes 500 error when MBeans throw exceptions ------------------------------------------------------------- Key: JBAS-7207 URL: https://jira.jboss.org/jira/browse/JBAS-7207 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.1.0.GA, JBossAS-5.1.0.CR1, JBossAS-5.1.0.Beta1, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA, JBossAS-5.0.0.CR2, JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1, JBossAS-5.0.0.Beta4, JBossAS-5.0.0.Beta3 Environment: Tested on Windows XP SP3 with all JBoss versions. Some versions tested on RedHat EL4 with same results. Reporter: Russ Hayward Assignee: Darran Lofthouse When using the JMX web console an exception thrown when invoking any MBean method causes a 500 server error rather than a stack trace to be displayed. To reproduce follow these steps: . Run JBoss with everything set to the default. . Go to "http://localhost:8080/jmx-console/". . Click on "jboss.ws" in the left frame. . Choose "service=ServerConfig" . Enter "wibble" in the "WebServicePort" field and click the Apply button. This seems to be the same for all exceptions generated by MBeans - whether generated by operations or attributes. The correct exception and stack trace appears in the log file. -- 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

15 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7371) admin-console Seam initialization issues with "default" configuration

by Darryl Miles (JIRA)

admin-console Seam initialization issues with "default" configuration --------------------------------------------------------------------- Key: JBAS-7371 URL: https://jira.jboss.org/jira/browse/JBAS-7371 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console, Management services Affects Versions: JBossAS-5.1.0.GA Environment: JDK6 Reporter: Darryl Miles Assignee: Darran Lofthouse something is wrong with the JBoss AS 5.1.0.GA distribution, using "default" configuration, and trying to access: http://127.0.0.1:8080/admin-console/ when I have my own application EAR that uses a newer version of Seam (2.1.2). I am using JBoss Tooling (JBIDE) to start the AS instance in debug mode on JDK6. It starts up fine enough, but the first access to the /admin-console/ yields the following stack trace. The web-app that is the admin-console seems to continue to remain deployed. So it is a lazy-Seam-initialization issue. The /admin-console/ web-app has not been modified in the distribution, but I do have an EAR project I am trying to develop which is using a different (newer) version of Seam than the one JBoss AS distributes within admin-console.war. But all the libraries my EAR uses are contained inside my EAR so this should make no difference (FWIW I am using Seam 2.1.2 in my app). It looks like admin-console.war uses Seam 2.1.0.SP1 this is inside the admin-console.war/WEB-INF/lib so should be isolated. If I remove my EAR from being deployed and restart the AS then /admin-console/ works. My EAR (that appears to break on JBoss AS) is really simple: ./jboss-seam-2.1.2.jar ./lib/ ./lib/commons-beanutils-1.8.0-BETA.jar ./lib/commons-collections-3.2.1.jar ./lib/commons-digester-1.8.jar ./lib/commons-logging-1.1.1.jar ./lib/drools-api-5.0.1.jar ./lib/drools-core-5.0.1.jar ./lib/jboss-el-1.0_02.CR2.jar ./lib/joda-time-1.6.jar ./lib/richfaces-api-3.3.1.GA.jar ./lib/spring-2.5.6.SEC01.jar ./lib/spring-aspects-2.5.6.SEC01.jar ./META-INF ./META-INF/MANIFEST.MF ./mvel2-2.0.10.jar Here are the last few lines of the server startup (maybe they are of some use ?) They show the deployment of the /admin-console web-app and the lack of any exception during deployment to indicate a failure at that time. 00:21:24,600 INFO [TomcatDeployment] deploy, ctxPath=/admin-console 00:21:24,713 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console' 00:21:28,397 INFO [TomcatDeployment] deploy, ctxPath=/ 00:21:28,543 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console 00:21:28,748 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080 00:21:28,811 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009 00:21:28,835 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 1m:12s:424ms Then upon first access of the webapp the URL http://127.0.0.1:8080/admin-console/ I get: .....START..... java.lang.RuntimeException: error while reading /WEB-INF/components.xml org.jboss.seam.init.Initialization.initComponentsFromXmlDocument(Initialization.java:221) org.jboss.seam.init.Initialization.create(Initialization.java:124) org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) org.jboss.on.embedded.LazyStartupListener.initialize(LazyStartupListener.java:182) org.jboss.on.embedded.LazyStartupListener.requestInitialized(LazyStartupListener.java:240) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Thread.java:619) root cause java.lang.RuntimeException: Error loading element Identity with component name null and component class null org.jboss.seam.init.Initialization.installComponentsFromXmlElements(Initialization.java:342) org.jboss.seam.init.Initialization.initComponentsFromXmlDocument(Initialization.java:217) org.jboss.seam.init.Initialization.create(Initialization.java:124) org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) org.jboss.on.embedded.LazyStartupListener.initialize(LazyStartupListener.java:182) org.jboss.on.embedded.LazyStartupListener.requestInitialized(LazyStartupListener.java:240) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Thread.java:619) ....END.... Then upon subsequent access of the webapp the URL http://127.0.0.1:8080/admin-console/ I get: ....START.... java.lang.NullPointerException org.jboss.seam.servlet.SeamFilter.getSortedFilters(SeamFilter.java:112) org.jboss.seam.servlet.SeamFilter.init(SeamFilter.java:93) org.jboss.on.embedded.LazyStartupFilter.init(LazyStartupFilter.java:104) org.jboss.on.embedded.LazyStartupFilter.doFilter(LazyStartupFilter.java:85) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) ....END.... This problem is simply the filter assuming a something has been correctly/fully initialized when it hasn't. So this points at: * The first exception has failed to initialize something relating to global Seam configuration, but the global initialization status was not rolled back (since the subsequent HTTP request should have resulted in a repeat of the same error) or * The second exception should be checking for null on something that is allowed to remain unconfigured Those matters would be for Seam team to investigate? -- 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

15 years, 8 months

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2010