[JBoss JIRA] Assigned: (JBMESSAGING-371) MessageListener times out on inactivity, after receiving at least one message
by Ovidiu Feodorov (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-371?page=all ]
Ovidiu Feodorov reassigned JBMESSAGING-371:
-------------------------------------------
Assignee: Ron Sigal (was: Ovidiu Feodorov)
> MessageListener times out on inactivity, after receiving at least one message
> -----------------------------------------------------------------------------
>
> Key: JBMESSAGING-371
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-371
> Project: JBoss Messaging
> Issue Type: Bug
> Components: JMS Remoting
> Affects Versions: 1.0.1.CR1, 1.2.0.Beta2
> Reporter: Ovidiu Feodorov
> Assigned To: Ron Sigal
> Priority: Blocker
> Fix For: 1.2.0.CR1
>
>
> 15:15:31,530 ERROR [ServerThread] socket timed out
> java.net.SocketTimeoutException: Read timed out
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
> at java.io.FilterInputStream.read(FilterInputStream.java:66)
> at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:140)
> at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:464)
> at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:381)
> at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:498)
> at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:240)
--
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, 3 months
[JBoss JIRA] Closed: (GPD-4) add support for adding Action to Nodes without adding Event
by Koen Aers (JIRA)
[ http://jira.jboss.com/jira/browse/GPD-4?page=all ]
Koen Aers closed GPD-4.
-----------------------
Resolution: Done
> add support for adding Action to Nodes without adding Event
> -----------------------------------------------------------
>
> Key: GPD-4
> URL: http://jira.jboss.com/jira/browse/GPD-4
> Project: JBoss jBPM GPD
> Issue Type: Feature Request
> Components: jpdl
> Affects Versions: jBPM JPDL Designer 3.0.11, jBPM JPDL Designer 3.1.0 alpha1
> Reporter: mehmet bozok
> Assigned To: Koen Aers
> Fix For: jBPM JPDL Designer 3.1.0.alpha2
>
>
> We are extending some parts of GDP in our project, and we need to add Action to Node without adding an Event then show this Aciton on outline tree view. Althought there is a mechanism to add a single Action to Nodes(not in GDP menu but implemented in
> org.jbpm.ui.model.Node), it is not shown at outline tree view. In order to make Action appear on tree view as a Node child we needed to
> add a menu option, and handle ActionTreeEditPart and NodeTreeEditpart relation in a different way. (not by changing GPD code, but instantiating editparts then reflecting org.eclipse.gef.AbstractEditPart and calling its protected methods which is not a very safe way.)
> Therefore it seems neccesary to change iplementation so that single Action (also providing which Action to add) can be added to Node and shown in outline tree view.
--
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, 3 months
[JBoss JIRA] Created: (JBCACHE-951) IdentityLock logs at too high a level
by Brian Stansberry (JIRA)
IdentityLock logs at too high a level
-------------------------------------
Key: JBCACHE-951
URL: http://jira.jboss.com/jira/browse/JBCACHE-951
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.ALPHA2, 1.4.1.GA
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 2.0.0.GA, 1.4.1.SP1
There are several examples of this kind of thing in IdentityLock:
boolean rc = lock_.writeLock().attempt(timeout);
// we don't need to synchronize from here on because we own the semaphore
if (rc == false) {
String errStr = "write lock for " + getFqn() + " could not be acquired after " + timeout + " ms. " +
"Locks: " + map_.printInfo() + " (caller=" + caller + ", lock info: " + toString(true) + ')';
log.error(errStr);
throw new TimeoutException(errStr);
}
The logging should be at TRACE level. The contents of the log message are entirely included in the exception, and are thus available to whatever code handles the exception. They can be logged at that time. Logging at ERROR removes the flexibility for callers to ignore some timeouts w/o disturbing the user via an ERROR logging.
This is particularly an issue for putForExternalRead() and evict(), where the goal is to use a 0 ms timeout.
--
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, 3 months
[JBoss JIRA] Closed: (JBAS-1537) When Tomcat error handler is invoked, JBossGenericPrincipal is returned instead of custom principal
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1537?page=all ]
Scott M Stark closed JBAS-1537.
-------------------------------
Resolution: Done
This works fine under 4.2. See the testCustomPrincipalInErrorPage, testCustomPrincipalIn403Page tests in org.jboss.test.security.test.CustomPrincipalPropagationUnitTestCase.
> When Tomcat error handler is invoked, JBossGenericPrincipal is returned instead of custom principal
> ---------------------------------------------------------------------------------------------------
>
> Key: JBAS-1537
> URL: http://jira.jboss.com/jira/browse/JBAS-1537
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Tomcat) service
> Affects Versions: JBossAS-4.0.1 Final
> Environment: linux i386, jdk 1.4.2_07
> Reporter: Rick Wong
> Assigned To: Scott M Stark
> Fix For: JBossAS-4.2.0.CR1
>
>
> Hi,
> I followed the instruction in the Wiki to set up a custom principal
> http://www.jboss.org/wiki/Wiki.jsp?page=UsingCustomPrincpalsWith
> Normally, this works perfectly such that the call to
> request.getUserPrincipal()
> returns my custom principal type. However, if a JSP error page is invoked either by the default error handler in the web.xml, or by the JSP declaration, a different Principal object is returned.
> A call to request.getUserPrincipal() in the error handler results in an object of type
> org.jboss.web.tomcat.security.JBossGenericPrincipal
> Is this by design? Shouldn't it also return my custom attribute?
> Thanks,
> --
> Rick
--
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, 3 months