September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-308) Upgrade commons-logging from 1.0.3 to 1.1.0

by Bela Ban (JIRA)

Upgrade commons-logging from 1.0.3 to 1.1.0 ------------------------------------------- Key: JGRP-308 URL: http://jira.jboss.com/jira/browse/JGRP-308 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 Needs some testing -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3560) shutdown.sh fails because it cannot find org/jboss/logging/Logger

by Ovidiu Feodorov (JIRA)

shutdown.sh fails because it cannot find org/jboss/logging/Logger ----------------------------------------------------------------- Key: JBAS-3560 URL: http://jira.jboss.com/jira/browse/JBAS-3560 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.Beta Reporter: Ovidiu Feodorov Priority: Minor org/jboss/logging/Logger is no longer shipped with jbossall-client.jar, so the shutdown script fails: $ ./shutdown.sh -S Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jnp.interfaces.NamingContext.<clinit>(NamingContext.java:159) .... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JGRP-332) Support concurrent flushing

by Vladimir Blagojevic (JIRA)

Support concurrent flushing --------------------------- Key: JGRP-332 URL: http://jira.jboss.com/jira/browse/JGRP-332 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.5 JGroups 2.4 introduces FLUSH protocol that enables stop-the-world model for JGroups nodes. However, FLUSH protocol currently does not support coordination between nodes when it comes to concurrent requests for flush. For example, in JGroups 2.4 if more than one MuxChannel sitting on top of JChannel requests flush the behaviour is nondeterministic. Also, we should investigate how to combine concurrent flush requests coming from state transfer protocol with flush requests coming from GMS protocol. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-3590) JBoss maps java.math.BigDecimal to numeric(19, 2) for Firebird 1.5 DB. Firebird complains precision must be <= 18.

by knaveofhearts (JIRA)

JBoss maps java.math.BigDecimal to numeric(19,2) for Firebird 1.5 DB. Firebird complains precision must be <= 18. ------------------------------------------------------------------------------------------------------------------ Key: JBAS-3590 URL: http://jira.jboss.com/jira/browse/JBAS-3590 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.0.4.GA Environment: JBossAS-4.0.4.GA, Firebird 1.5, Fedora Core 5 Linux. Reporter: knaveofhearts Assigned To: Bill Burke This is a problem with EJB 3 entity persistence with CMP. I have several classes in which member variables are declared as BigDecimal. The classes all work fine with HSQLDB, which I have been using for rapid development, using the create-drop capability. I tried to switch the backend to Firebird 1.5 by changing the two relevant files (if I recall, persistence.xml and the []-ds.xml file), and managed to remove all the problems (e.g., Fireword reserve words like "role", "user", and "type" that I used as class or attribute names) except for BigDecimal fields. The server log says that BigDecimal is being mapped to numeric(19,2), but the maximum precision for Firebird is 18. If I replace all the BigDecimal fields with double, then my basic DB access tests run okay. I have posted this problem to two JBoss forums (EJB3 and Persistence) and to one Firebird forum (Firebird-Java), but have gotten no replies. If there is an easy fix, I would appreciate learning about it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3539) CLONE -jboss-client.jar misses MarshalledInvocation$DeclaredMethods

by Matthew L Daniel (JIRA)

CLONE -jboss-client.jar misses MarshalledInvocation$DeclaredMethods ------------------------------------------------------------------- Key: JBAS-3539 URL: http://jira.jboss.com/jira/browse/JBAS-3539 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.0 Final Reporter: Matthew L Daniel Assigned To: Scott M Stark Fix For: Closed issues from sourceforge Attachments: JBAS-1163_2.patch SourceForge Submitter: igorfie . Latest CVS version of JBoss 4.0.0 is missing org/jboss/invocation/MarshalledInvocation$DeclaredMethodsAction from the jboss-client.jar. As a result org.jboss.ant.JMX fails with NoClassDefFoundError. The following patch should fix the problem. Index: build.xml =================================================================== RCS file: /cvsroot/jboss/jboss/build.xml,v retrieving revision 1.173.2.2 diff -u -r1.173.2.2 build.xml --- build.xml 17 Oct 2004 18:49:28 -0000 1.173.2.2 +++ build.xml 26 Oct 2004 03:57:20 -0000 @@ -470,6 +470,7 @@ <include name="org/jboss/invocation/MarshallingInvokerInterceptor.class"/> <include name="org/jboss/invocation/PayloadKey.class"/> <include name="org/jboss/invocation/MarshalledInvocation.class"/> + <include name="org/jboss/invocation/MarshalledInvocation$DeclaredMethodsAction.class"/> <include name="org/jboss/invocation/MarshalledValue.class"/> <include name="org/jboss/invocation/MarshalledValueInputStream.class"/> <include name="org/jboss/invocation/MarshalledValueOutputStream*.class"/> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3481) Error accessing EJB from Servlet: "Unable to activate POA"

by Peter Rasbora (JIRA)

Error accessing EJB from Servlet: "Unable to activate POA" ---------------------------------------------------------- Key: JBAS-3481 URL: http://jira.jboss.com/jira/browse/JBAS-3481 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: IIOP service, Naming, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1, JBossAS-4.0.1 SP1 Environment: JBoss: 4.0.0, 4.0.1SP1, 4.0.3SP1, 4.0.4GA ( each "out of the box") Java: 1.5.0_06 (build 1.5.0_06-b05) OS: Windows XP SP2 Reporter: Peter Rasbora Assigned To: Francisco Reverbel Priority: Minor When trying to access Stateless SessionBean (JNDI: "vfmcontroller/VFMController") from within a Servlet, it's service() throws a "java.lang.Error: POA: not configured!" JBoss Log warns: "(IIOPListener) Address already in use: JVM_Bind", "org.jboss.corba.ORBFactory:87) Unable to activate POA" and "org.omg.CORBA.INITIALIZE: Could not create server socket" Following to netstat no other processes are bound to specific ports (8080, 1098, 1099, 3528). For further Details (Source, DD, Log-Output) please refer to the following ressources: Stateless SessionBean: http://pastebin.ca/118516 Servlet "Test.java": http://pastebin.ca/118535 jboss.xml: http://pastebin.ca/118520 JBoss Log (Console): http://pastebin.ca/118529 (Hint: Log-Level is DEBUG) Caught Exception in Servlet "Test": http://pastebin.ca/118532 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-159) Refactor modules

by Mark Little (JIRA)

Refactor modules ---------------- Key: JBESB-159 URL: http://jira.jboss.com/jira/browse/JBESB-159 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.1 Do we need 3 modules for the core ESB? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3571) Bad interaction between http session passivation and buddy replication

by Brian Stansberry (JIRA)

Bad interaction between http session passivation and buddy replication ---------------------------------------------------------------------- Key: JBAS-3571 URL: http://jira.jboss.com/jira/browse/JBAS-3571 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta I've seen server startup issues when in the tc6-cluster.sar buddy replication is enabled AND the cache loader used for passivation is enabled. For now I'm disabling passivation by commenting out the cache loader config; need to sort out what is going on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-747) Bad interaction between session passivation and buddy replication

by Brian Stansberry (JIRA)

Bad interaction between session passivation and buddy replication ----------------------------------------------------------------- Key: JBCACHE-747 URL: http://jira.jboss.com/jira/browse/JBCACHE-747 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0 I've seen server startup issues when in the tc6-cluster.sar buddy replication is enabled AND the cache loader used for passivation is enabled. May be a generic JBC issue rather than something in the http session code. JBAS-3571 is the main issue; I'm just opening a parallel one in JBC 'cause 2.0.0.Beta will go out before 5.0.0.Beta and I want to be sure I look at this before 2.0.0.Beta. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAOP-288) Unify API used by AspectDeployer with AOP 2.0

by Kabir Khan (JIRA)

Unify API used by AspectDeployer with AOP 2.0 --------------------------------------------- Key: JBAOP-288 URL: http://jira.jboss.com/jira/browse/JBAOP-288 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 1.5.2.GA The AspectDeployer will be built from Branch_4_0 for both AOP 1.5.x and AOP 2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 5 months

2
6
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 September 2006