[JBoss JIRA] Created: (JBAS-4917) remote call to LoaderRepository.getPackageClassLoaders throws a NotSerializableException
by Franois Karman (JIRA)
remote call to LoaderRepository.getPackageClassLoaders throws a NotSerializableException
----------------------------------------------------------------------------------------
Key: JBAS-4917
URL: http://jira.jboss.com/jira/browse/JBAS-4917
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX
Environment: I have tested this problems on Windows Platform only.
Reporter: Franois Karman
Assigned To: Dimitris Andreadis
A call to the getPackageClassLoaders operation of the MBean : JMImplementation:name=Default,service=LoaderRepository throws an exception.
The simpliest way to view the bug :
twiddle invoke "JMImplementation:name=Default,service=LoaderRepository" getPackageClassLoaders javax.ejb.EntityBean
Start of the trace :
java.io.NotSerializableException: org.jboss.mx.loading.ClassLoaderUtils$RepositoryClassLoaderComparator
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at java.util.TreeSet.writeObject(TreeSet.java:458)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
The comparator used by the result TreeSet is not serializable and could not be send to the remote client. (twiddle or a J2EE Client application)
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/jmx/src/main/org...
--
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, 7 months
[JBoss JIRA] Created: (JBAS-3859) Initialization of XMBean attributes doesn't occur
by Chris (JIRA)
Initialization of XMBean attributes doesn't occur
-------------------------------------------------
Key: JBAS-3859
URL: http://jira.jboss.com/jira/browse/JBAS-3859
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMX
Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.3 SP1
Environment: Windows XP, Mac OSX 10.4.8, Java 1.5.0_04, 1.6.0
Reporter: Chris
Assigned To: Scott M Stark
The Wiki for initializing XMBean values upon deployment (see http://wiki.jboss.org/wiki/Wiki.jsp?page=HowCanIInitializeXMBeanAttributes) suggests 2 ways to set the initial value. One is to use a <descriptor>, the other is to use a plain <value> tag. This has been confirmed to be the way it should work by Dimitris (see forum thread).
I have tried both ways on JBoss 4.0.3, 4.0.5, and JBoss 5.0.0 (JEE5_TCK) - using JDK1.5 and JDK 1.6, on XP and also on Mac .... and it does not set the initial value. Instead the value is always the default value "I've got the devil inside me" which comes from the String definition within the class file itself.
(Incidentally, as an aside, if you change the value in the JMX Console and restart JBoss, then the value is correctly recovered from the persistence store).
To reproduce, open the file $JBOSS_HOME\docs\examples\jmx\persistent-service.sar\META-INF\jboss-service.xml
and edit the file as per the Wiki's suggestion. e.g. for attribute SomeString add a <value> tag as follows:
<attribute access="read-write" getMethod="getSomeString" setMethod="setSomeString">
<name>SomeString</name>
<type>java.lang.String</type>
<value>This is my initial value</value> <!-- this line is new -->
</attribute>
Copy this to the $JBOSS_HOME\server\default\deploy\ directory and start JBoss.
Then view the XMBean using the JMX console:
http://localhost:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=jb...
You will see that the value for SomeString is "I've got the devil inside me" from the class definition whereas I would expect it to be "This is my initial value" as taken from the XML file.
(Incidentally, setting an MBean initial attribute does work, the persistence service example has such a value for SomeElement:
"<some-message>Welcome to the Athens 2004, Olympic Games!</some-message>"
But setting the XMBean initial attribute does not work)
(Also, if the attribute is changed to read-only then there is no error upon deployment to show that the setting of the value has even been attempted.)
--
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, 7 months
[JBoss JIRA] Created: (JBAS-4028) nosuchmethoderror
by tony anecito (JIRA)
nosuchmethoderror
-----------------
Key: JBAS-4028
URL: http://jira.jboss.com/jira/browse/JBAS-4028
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: Windows 2000 Professional JDK 1.6.0
Reporter: tony anecito
21:10:46,843 ERROR [[/invoker]] Exception sending context initialized event to l
istener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigure
Listener
java.lang.NoSuchMethodError: javax.servlet.ServletContext.getContextPath()Ljava/
lang/String;
at com.sun.faces.config.WebConfiguration.getServletContextName(WebConfig
uration.java:191)
--
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, 7 months
[JBoss JIRA] Created: (JBAS-5325) Out of Memory error: Cannot start new thread. SpyJMSException
by aneesh vasanthan (JIRA)
Out of Memory error: Cannot start new thread. SpyJMSException
-------------------------------------------------------------
Key: JBAS-5325
URL: http://jira.jboss.com/jira/browse/JBAS-5325
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.2RC1
Environment: Windows, jboss 4.0.2
Reporter: aneesh vasanthan
Priority: Critical
Hi ,
we are using jboss4.0.2 as our application server. we are facing a major problem in jms connection. It happens very frequently. After a restart will be fine for sometime n again it crashes.The exception trace is as shown below. expecting ur eteemed reply.
Application server: jboss 4.0.2
Application deployed in : jboss\server\default
2008-03-18 15:03:48,328 DEBUG [org.apache.coyote.tomcat5.CoyoteAdapter] Requested cookie session id is 639091685F164A589266650426F9B40F
2008-03-18 15:14:02,234 DEBUG [org.apache.coyote.tomcat5.CoyoteAdapter] Requested cookie session id is 639091685F164A589266650426F9B40F
2008-03-18 19:22:29,234 WARN [org.jboss.mq.Connection] Connection failure:
org.jboss.mq.SpyJMSException: Exiting on unexpected error in read task; - nested throwable: (java.lang.reflect.UndeclaredThrowableException)
at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
at org.jboss.mq.il.uil2.UILClientILService.asynchFailure(UILClientILService.java:147)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.handleStop(SocketManager.java:398)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:342)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.lang.reflect.UndeclaredThrowableException
... 4 more
Caused by: java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start(Native Method)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor.addThread(PooledExecutor.java:520)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor.execute(PooledExecutor.java:880)
at org.jboss.mq.il.uil2.SocketManager$ReadTask.run(SocketManager.java:296)
... 1 more
2008-03-18 19:27:29,234 WARN [org.jboss.mq.Connection] Connection failure:
org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1378)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1370)
... 2 more
2008-03-18 19:32:29,250 WARN [org.jboss.mq.Connection] Connection failure:
org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1378)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1370)
... 2 more
2008-03-18 19:37:29,265 WARN [org.jboss.mq.Connection] Connection failure:
org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1378)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1370)
... 2 more
2008-03-18 19:42:29,281 WARN [org.jboss.mq.Connection] Connection failure:
org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1378)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1370)
... 2 more
2008-03-18 19:47:29,296 WARN [org.jboss.mq.Connection] Connection failure:
org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
at org.jboss.mq.Connection.asynchFailure(Connection.java:429)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1378)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:536)
--
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, 7 months