[JBoss JIRA] Created: (JBREM-541) null pointer when receiving detection message
by John Mazzitelli (JIRA)
null pointer when receiving detection message
---------------------------------------------
Key: JBREM-541
URL: http://jira.jboss.com/jira/browse/JBREM-541
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.Beta2 (Boon)
Reporter: John Mazzitelli
Assigned To: Tom Elrod
Fix For: 2.0.0.CR1 (Boon)
I am seeing a NullPointerException that causes my multicast detector to fail.
I have a JBoss 4.0.4.CR2 install that has my connector and multicast detector deployed. I also deployed the servlet-invoker war because i am using the servlet transport.
I start up the JBossAS fine. No errors. I then start up a second JVM that contains my J2SE app that also has a JBoss-Remoting connector and multicast detector in it.
After that second VM starts, I can see the JBossAS receives the multicast message, but it throws the following exception:
11:58:53,118 DEBUG [MulticastDetector] Error receiving detection
java.lang.NullPointerException
at org.jboss.remoting.detection.AbstractDetector.detect(AbstractDetector.java:402)
at org.jboss.remoting.detection.multicast.MulticastDetector.listen(MulticastDetector.java:232)
at org.jboss.remoting.detection.multicast.MulticastDetector.access$100(MulticastDetector.java:43)
at org.jboss.remoting.detection.multicast.MulticastDetector$Listener.run(MulticastDetector.java:260)
In that J2SE VM, I get this exception:
12:05:21,106 DEBUG [Remoting Multicast Detector - Listener Thread: 0] (jboss.remoting.detection.multicast.MulticastDetector)- Error receiving detection
java.net.SocketException: socket closed
at java.net.PlainDatagramSocketImpl.receive0(Native Method)
at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
at java.net.DatagramSocket.receive(DatagramSocket.java:712)
at org.jboss.remoting.detection.multicast.MulticastDetector.listen(MulticastDetector.java:244)
at org.jboss.remoting.detection.multicast.MulticastDetector.access$000(MulticastDetector.java:45)
at org.jboss.remoting.detection.multicast.MulticastDetector$Listener.run(MulticastDetector.java:289)
I have trace mode enabled but those are the only messages I see wrt the detector.
--
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
20 years
[JBoss JIRA] Resolved: (JBPORTAL-940) bad jsessionid in form action on login page
by Chris Laprun (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-940?page=all ]
Chris Laprun resolved JBPORTAL-940.
-----------------------------------
Fix Version/s: 2.4 Final
2.2.1 Final
Resolution: Done
Assignee: Julien Viet
> bad jsessionid in form action on login page
> -------------------------------------------
>
> Key: JBPORTAL-940
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-940
> Project: JBoss Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Portal Server
> Affects Versions: 2.2.1 Final, 2.4 Final
> Environment: jboss-portal 2.2.1-SP2 out-of-the-box
> jboss-portal 2.4-RC1 out-of-the-box
> Reporter: Rafal Krupinski
> Assigned To: Julien Viet
> Fix For: 2.4 Final, 2.2.1 Final
>
>
> when i open any page on out-of-the-box portal there is jsessionid in urls.
> It's ok until I open the login page, where it looks like this
> form method="POST" action="j_security_check;jsessionid=...%>" name=... etc.
> the problem is in
> portal-server.war/login.jsp line 22
> there is double '%>'
--
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
20 years
[JBoss JIRA] Closed: (JBAS-2144) Scheduled task interval calculated from stop to start instead of start to start
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2144?page=all ]
Dimitris Andreadis closed JBAS-2144.
------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta
JBossAS-4.0.5.CR1
Resolution: Done
Assignee: Dimitris Andreadis
This is solved now. The behaviour is the same in both jdk1.4 and jdk5, which is fixed-delay by default, unless you override this by setting FixedRate to true (as shown in the configuration files).
To get the full story look at:
JBAS-3281
JBAS-3282
> Scheduled task interval calculated from stop to start instead of start to start
> -------------------------------------------------------------------------------
>
> Key: JBAS-2144
> URL: http://jira.jboss.com/jira/browse/JBAS-2144
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JMX
> Affects Versions: JBossAS-4.0.2 Final
> Environment: Linux, sun jdk 1.5.0_04, JBoss 4.0.2 final
> Reporter: Thomas Roka-Aardal
> Assigned To: Dimitris Andreadis
> Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1
>
>
> When running jboss 4.0.2 final with jdk 1.5.0_04 the calculation of the next start of a scheduled operation becomes (time at END of scheduled operation + interval) instead of (time at START of scheduled operation + interval). This causes scheduled operations to shift in time based on the duration of the scheduled operation. This does NOT happen using jdk 1.4 which might hint at the built-in jmx (and timer instance) in the jvm of 1.5 causing the problem?
--
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
20 years
[JBoss JIRA] Closed: (JBAS-1705) Implement getFixedRate() and add fixed-rate notification inTimerMBean, as of JMX1.2
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1705?page=all ]
Dimitris Andreadis closed JBAS-1705.
------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta
Resolution: Done
Assignee: Dimitris Andreadis
Essentially done as part of JBAS-3281
> Implement getFixedRate() and add fixed-rate notification inTimerMBean, as of JMX1.2
> -----------------------------------------------------------------------------------
>
> Key: JBAS-1705
> URL: http://jira.jboss.com/jira/browse/JBAS-1705
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JMX
> Affects Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.2RC1
> Environment: (jmx) javax.management.timer.Timer
> Reporter: Dimitris Andreadis
> Assigned To: Dimitris Andreadis
> Priority: Minor
> Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1
>
>
> public Integer addNotification(String type, String message, Object userData, Date date, long period, long nbOccurences, boolean fixedRate) throws IllegalArgumentException
> {
> // [todo] implement addNotification
> throw new RuntimeException("NYI");
> }
> public Boolean getFixedRate(Integer id)
> {
> //[todo] implement getFixedRate
> throw new RuntimeException("NYI");
> }
--
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
20 years
[JBoss JIRA] Assigned: (JBAS-1768) Isolating the test harness
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1768?page=all ]
Dimitris Andreadis reassigned JBAS-1768:
----------------------------------------
Assignee: Ruel Loehr
Assign to Ruel, so work on this and the linked tasks can be scheduled, at some point.
> Isolating the test harness
> --------------------------
>
> Key: JBAS-1768
> URL: http://jira.jboss.com/jira/browse/JBAS-1768
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: JBossAS-4.0.1 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1 SP1
> Reporter: Adrian Brock
> Assigned To: Ruel Loehr
> Fix For: JBossAS-4.0.5.CR1
>
>
> Since some projects are already using the test harness
> org.jboss.test (from the testsuite)
> this needs to be isolated to break the circular build dependency.
> Additionally, we should look at making this available to users
> 1) For their own use
> 2) When reporting problems
--
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
20 years
[JBoss JIRA] Commented: (JBAS-3372) Replace Sun javamail (mail.jar) with classpathx-mail.jar v1.0
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3372?page=comments#action_12339598 ]
Dimitris Andreadis commented on JBAS-3372:
------------------------------------------
Sun has relicensed from SBCL to CDDL, so the switch may be avoided.
> Replace Sun javamail (mail.jar) with classpathx-mail.jar v1.0
> -------------------------------------------------------------
>
> Key: JBAS-3372
> URL: http://jira.jboss.com/jira/browse/JBAS-3372
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Other
> Reporter: Dimitris Andreadis
> Priority: Critical
> Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1, JBossAS-3.2.8.SP2
>
>
> GNU JavaMail is a free implementation of the JavaMail API specification, version 1.3.
> We want to use it as a replacement for Sun's mail.jar
> The sources can be downloaded from here:
> http://www.gnu.org/software/classpathx/javamail/javamail.html
> Issues with replacement by classpathx-mail:
> jbossws must be patched to use gnu-handlers instead of sun-handlers
> +//import com.sun.mail.handlers.multipart_mixed;
> +import gnu.mail.handler.MultipartMixed;
> +//import com.sun.mail.handlers.text_html;
> +import gnu.mail.handler.TextHtml;
> +//import com.sun.mail.handlers.text_plain;
> +import gnu.mail.handler.TextPlain;
> testsuite/src/main/org/jboss/test/classloader/resource/ResourceTest.java
> must be patched, because it refers to javamail.default.address.map and javamail.default.providers while in classpathx-mail these are named javamail.address.map and javamail.providers in classpathx-mail This change isn't essential to javamail; those files (+javamail.jar) were chosen because they were supposed to be always there. The real purpose of ResouceTest.java is to check access to resouces, so any adequate resources could be the test objects. But the resource test is executed very often and in different contexts. Therefore the adjustment is important for testsuite.
--
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
20 years