[JBoss JIRA] Created: (JBPORTAL-1096) Error when set/get of portlet property
by Roy Russo (JIRA)
Error when set/get of portlet property
--------------------------------------
Key: JBPORTAL-1096
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1096
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.6.Alpha1
Reporter: Roy Russo
Assigned To: Julien Viet
Priority: Critical
Fix For: 2.6.Alpha1
This fails in the Weather/News portlets: response.setProperty("expiration-cache", request.getPreferences().getValue("expires", "180"));
08:49:54,855 ERROR [ControllerCommand] Rendering portlet window default.News.WeatherPortletWindow triggered the following error :
java.lang.IllegalArgumentException: Scope not recognized response_properties
at org.jboss.portal.common.invocation.AbstractInvocationContext.getAttributeResolver(AbstractInvocationContext.java:88)
at org.jboss.portal.common.invocation.AbstractInvocationContext.setAttribute(AbstractInvocationContext.java:121)
at org.jboss.portal.common.invocation.Invocation.setAttribute(Invocation.java:80)
at org.jboss.portal.portlet.impl.jsr168.PortletResponseImpl.setProperty(PortletResponseImpl.java:103)
at org.jboss.samples.portlet.weather.WeatherPortlet.doView(WeatherPortlet.java:116)
at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:133)
at javax.portlet.GenericPortlet.render(GenericPortlet.java:306)
at org.jboss.portal.portlet.container.PortletContainer.invokeRender(PortletContainer.java:516)
at org.jboss.portal.portlet.container.PortletContainer.dispatch(PortletContainer.java:438)
at org.jboss.portal.portlet.container.PortletContainerInvoker$1.invoke(PortletContainerInvoker.java:73)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:134)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jboss$portal$core$aspects$portlet$TransactionInterceptor$invokeNotSupported$aop(TransactionInterceptor.java:85)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeNotSupported_N4547270787964792031.invokeNext(TransactionInterceptor$invokeNotSupported_N4547270787964792031.java)
at org.jboss.aspects.tx.TxPolicy.invokeInNoTx(TxPolicy.java:66)
at org.jboss.aspects.tx.TxInterceptor$NotSupported.invoke(TxInterceptor.java:101)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeNotSupported_N4547270787964792031.invokeNext(TransactionInterceptor$invokeNotSupported_N4547270787964792031.java)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invokeNotSupported(TransactionInterceptor.java)
at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invoke(TransactionInterceptor.java:55)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118)
at org.jboss.portal.core.aspects.portlet.HeaderInterceptor.invoke(HeaderInterceptor.java:50)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118)
at org.jboss.portal.portlet.aspects.portlet.ProducerCacheInterceptor.invoke(ProducerCacheInterceptor.java:51)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118)
at org.jboss.portal.portlet.aspects.portlet.ModesInterceptor.invoke(ModesInterceptor.java:60)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118)
at org.jboss.portal.bridge.BridgeInterceptor.invoke(BridgeInterceptor.java:46)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118)
at org.jboss.portal.portlet.aspects.portlet.WindowStatesInterceptor.invoke(WindowStatesInterceptor.java:55)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118)
at org.jboss.portal.portlet.aspects.portlet.PortletSessionSynchronizationInterceptor.invoke(PortletSessionSynchronizationInterceptor.java:78)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118)
at org.jboss.portal.portlet.aspects.portlet.ContextTrackerInterceptor.invoke(ContextTrackerInterceptor.java:46)
at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:118)
at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor$InvokeNextCommand.execute(ContextDispatcherInterceptor.java:148)
--
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
[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
[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
[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
[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