October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4734) Flush failures on MuxChannel connection

by Brian Stansberry (JIRA)

Flush failures on MuxChannel connection --------------------------------------- Key: JBAS-4734 URL: http://jira.jboss.com/jira/browse/JBAS-4734 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Vladimir Blagojevic Fix For: JBossAS-5.0.0.CR1 Getting WARN messages about startFlush failures when multiplexed channels connect: 2007-09-18 03:04:02,936 WARN [org.jboss.ha.framework.server.JChannelFactory] Flush failed at 127.0.0.1:51382 DefaultPartition-SFSBCache Adrian took a thread dump before one of those was logged and saw: "main" prio=1 tid=0x80cbdfa0 nid=0x2847 in Object.wait() [0x804d2000..0x804d5130] at java.lang.Object.wait(Native Method) - waiting on <0xaf1e6838> (a org.jgroups.util.Promise) at org.jgroups.util.Promise.doWait(Promise.java:104) at org.jgroups.util.Promise._getResultWithTimeout(Promise.java:60) at org.jgroups.util.Promise.getResultWithTimeout(Promise.java:28) - locked <0xaf1e6838> (a org.jgroups.util.Promise) at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:207) at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:229) at org.jgroups.protocols.pbcast.FLUSH.startFlush(FLUSH.java:229) at org.jgroups.protocols.pbcast.FLUSH.down(FLUSH.java:263) at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:339) at org.jgroups.JChannel.downcall(JChannel.java:1240) at org.jgroups.JChannel.startFlush(JChannel.java:1504) at org.jgroups.JChannelFactory.connect(JChannelFactory.java:364) - locked <0xade09c70> (a org.jgroups.JChannelFactory$Entry) I'll attach a server.log file from a hudson run that shows a bunch of these. Look at lines 4153-4193 for the first one, where the underlying JChannel connection happens. I'm not seeing these on my local system. -- 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

17 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4911) MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver

by Luc Texier (JIRA)

MSSQLValidConnectionChecker throws exception with MS SQL Server 2005 JDBC driver -------------------------------------------------------------------------------- Key: JBAS-4911 URL: http://jira.jboss.com/jira/browse/JBAS-4911 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.2.2.GA Reporter: Luc Texier Assigned To: Weston Price After installing the latest v1.2 version of the MS SQL Server 2005 JDBC driver (http://msdn2.microsoft.com/en-us/data/aa937724.aspx), I've deployed the following datasource <datasources> <local-tx-datasource> <jndi-name>DefaultDS</jndi-name> <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=pubs</connection-url> <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class> <user-name>sa</user-name> <password>jboss</password> <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker</valid-connection-checker-class-name> <metadata> <type-mapping>MS SQLSERVER2000</type-mapping> </metadata> </local-tx-datasource> </datasources> during start-up, the following exception is throwed 2007-10-25 11:26:36,312 DEBUG [org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory] Starting jboss:service=KeyGeneratorFactory,type=HiLo 2007-10-25 11:26:36,328 WARN [org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker] warning: connection validation failed for current managed connection. 2007-10-25 11:26:36,328 WARN [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Destroying connection that is not valid, due to the following exception: com.microsoft.sqlserver.jdbc.SQLServerConnection@9a42ef com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'x'. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source) at org.jboss.resource.adapter.jdbc.vendor.MSSQLValidConnectionChecker.isValidConnection(MSSQLValidConnectionChecker.java:54) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:445) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:231) at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:200) at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:211) at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:500) at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341) at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:315) at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396) -- 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

17 years, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-4388) Place all management web applications, web invokers, etc under a common context root

by Jeff Schnitzer (JIRA)

Place all management web applications, web invokers, etc under a common context root ------------------------------------------------------------------------------------ Key: JBAS-4388 URL: http://jira.jboss.com/jira/browse/JBAS-4388 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Console Reporter: Jeff Schnitzer Assigned To: Darran Lofthouse In any enterprise environment, administrative interfaces are blocked from the public even if they require a password; administrative interfaces can only be accessed through the internal network or a SSL-secured VPN. This means the load balancer (or whatever) must block out all the possible management/invocation web apps: /jmx-console /web-console /invoker /jbossmq-httpil These paths sometimes change between JBoss versions without any significant announcement, plus services are occasionally added. This could easily result in unsecured or poorly secured (basic auth) services exposed to the public. Please put all JBoss-provided webapps under a base context that can easily be blocked to the public: /jboss/jmx-console /jboss/web-console /jboss/invoker /jboss/jbossmq-httpil -- 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

17 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1034) Allow connection factories to be created programmatically

by Tim Fox (JIRA)

Allow connection factories to be created programmatically --------------------------------------------------------- Key: JBMESSAGING-1034 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1034 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta 1 We should allow connection factories to be created programmatically on the client side - this allows people to use JBM when they don't have JNDI. -- 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

17 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (GPD-169) Transition text position not saving

by David Roberts (JIRA)

Transition text position not saving ----------------------------------- Key: GPD-169 URL: http://jira.jboss.com/jira/browse/GPD-169 Project: JBoss jBPM GPD Issue Type: Bug Affects Versions: jBPM JPDL Designer 3.1.0.GA Environment: Eclipse 3.3, EMF: 2.3.1, GEF: 3.3.1, DTP: 1.5, WTP: 2.0, jbpm-jpdl-designer-3.1.0.sp1 Reporter: David Roberts Assigned To: Koen Aers Upgrading to jbpm-jpdl-designer-3.1.0.sp1 gives me the following problem: All my custom aligned/positioned text on all my transitions get reset when re-opening the process in the designer. They stick to the transition line, and if the transition line is quite short, the text then overlaps my nodes etc. It looks terrible. I tried re-positioning all the text again, and saving, but as soon as I close and re-open my process again, the text is snapped back onto the transition lines, and it looks terrible again. -- 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

17 years, 11 months

6
17
0 / 0

[JBoss JIRA] Created: (EJBTHREE-820) Hardcoded Destination Manager Reference

by Juha Lindfors (JIRA)

Hardcoded Destination Manager Reference --------------------------------------- Key: EJBTHREE-820 URL: http://jira.jboss.com/jira/browse/EJBTHREE-820 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: JBoss AS 4.0.5.GA + EJB 3.0 RC9 + JBoss Messaging Reporter: Juha Lindfors Priority: Minor When deploying an MDB that has been configured wrongly with a non existing destination the dubious feature that creates a temporary destination automatically fails due to hard coded destination manager reference that no longer exists if JBoss Messaging is used instead of JBossMQ. MessagingContainer: protected void createTemporaryDestination(Class type, String jndiSuffix) throws Exception 513 ObjectName destinationManagerName = new ObjectName("jboss.mq:service=DestinationManager"); Apologies, did not check if this issue exists still with the current code in the head/trunk, just needed to write it down before I forget 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

17 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3402) Web Console and Firefox

by Vladimir Gendler (JIRA)

Web Console and Firefox ----------------------- Key: JBAS-3402 URL: http://jira.jboss.com/jira/browse/JBAS-3402 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Management services Affects Versions: JBossAS-4.0.4.GA Environment: MS W2000 SP4 Reporter: Vladimir Gendler Assigned To: Dimitris Andreadis Web Console output in Mozilla Firefox (and Seamonkey) is messed up. Compare the attached archive with snapshots from Mozilla Firefox and MSIE. -- 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

17 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-746) Ascertain whether any methods and attributes exposed by TreeCacheMBean can be marked serializable

by Jerry Gauthier (JIRA)

Ascertain whether any methods and attributes exposed by TreeCacheMBean can be marked serializable ------------------------------------------------------------------------------------------------- Key: JBCACHE-746 URL: http://jira.jboss.com/jira/browse/JBCACHE-746 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jerry Gauthier Assigned To: Jerry Gauthier Priority: Minor When TreeCacheMBean is accessed remotely via an mbean server such as jconsole, numerous attributes and methods are marked as problematic because they aren't serializable. While many are undoubtedly not serializable, it's worth reviewing the list to see if it would be appropriate to mark any additional attributes or method parameters as serializable. -- 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

17 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-687) General purpose BRMS query functionality

by Michael Neale (JIRA)

General purpose BRMS query functionality ---------------------------------------- Key: JBRULES-687 URL: http://jira.jboss.com/jira/browse/JBRULES-687 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

17 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-4217) CheckValidConnectionSQL is not Serializable

by Purush Rudrakshala (JIRA)

CheckValidConnectionSQL is not Serializable ------------------------------------------- Key: JBAS-4217 URL: http://jira.jboss.com/jira/browse/JBAS-4217 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.0.CR1, JBossAS-4.0.5.GA, JBossAS-3.2.7 Final Reporter: Purush Rudrakshala Please refer to Bug 1192. This was closed incorrectly. The problem still exists in JBoss 3.2.7, 4.0.5 and 4.2 CR1 -- 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

17 years, 11 months

5
8
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 October 2007