November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6115) Internet connection required for SAR containing mydatasource-ds.xml

by Juergen Zimmermann (JIRA)

Internet connection required for SAR containing mydatasource-ds.xml ------------------------------------------------------------------- Key: JBAS-6115 URL: https://jira.jboss.org/jira/browse/JBAS-6115 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR2 Reporter: Juergen Zimmermann When deploying an exploded EAR containing an exploded SAR an internet connection is necessary. When working offline I get these errors in server.log: 2008-10-20 06:41:32,308 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.0.0.CR2 (build: SVNTag=JBoss_5_0_0_CR2 date=200809171046)] Started in 27s:543ms 2008-10-20 06:41:48,339 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (HDScanner) Error installing to Parse: name=vfsfile:/C:/Software/jboss/server/default/deploy/hska.ear/ state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/Software/jboss/server/default/deploy/hska.ear/hska.sar/hska-ds.xml at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:303) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:275) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:236) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1056) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1056) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:627) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: javax.xml.bind.UnmarshalException - with linked exception: [java.net.UnknownHostException: www.jboss.org] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:213) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:190) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:241) at org.jboss.resource.deployers.ManagedConnectionFactoryParserDeployer.parse(ManagedConnectionFactoryParserDeployer.java:132) at org.jboss.resource.deployers.ManagedConnectionFactoryParserDeployer.parse(ManagedConnectionFactoryParserDeployer.java:70) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256) at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:239) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:336) ... 29 more Caused by: java.net.UnknownHostException: www.jboss.org at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.<init>(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:837) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:778) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:703) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1026) at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source) at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:211) ... 36 more 2008-10-20 06:41:48,341 WARN [org.jboss.system.server.profileservice.hotdeploy.HDScanner] (HDScanner) Failed to process changes org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** CONTEXTS IN ERROR: Name -> Error vfsfile:/C:/Software/jboss/server/default/deploy/hska.ear/ -> java.net.UnknownHostException: www.jboss.org at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:709) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-6019) Upgrade JBoss Aspects to their final version

by Dimitris Andreadis (JIRA)

Upgrade JBoss Aspects to their final version -------------------------------------------- Key: JBAS-6019 URL: https://jira.jboss.org/jira/browse/JBAS-6019 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Aspects Reporter: Dimitris Andreadis Fix For: JBossAS-5.0.0.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBASPECT-30) Transient Failure in RemoteTestCase

by Andrew Lee Rubinger (JIRA)

Transient Failure in RemoteTestCase ----------------------------------- Key: JBASPECT-30 URL: https://jira.jboss.org/jira/browse/JBASPECT-30 Project: JBoss Aspects Issue Type: Bug Components: remoting Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger RemoteTestCase has a Thread.sleep to wait for the forked process to start, which may not be enough time. For now just hack something in place to get a reliable result. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
6
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-438) Preference Values whose length is greater than 255 characters cannot be saved

by Marcelo Mazza (JIRA)

[ https://jira.jboss.org/jira/browse/JBPORTAL-438?page=com.atlassian.jira.p... ] Marcelo Mazza commented on JBPORTAL-438: ---------------------------------------- Why don't you define the field jbp_user_pref_value.jbp_value as TEXT? I do have the same problem, but in the table jbp_portlet_state_entry_value (field jbp_value). > Preference Values whose length is greater than 255 characters cannot be saved > ----------------------------------------------------------------------------- > > Key: JBPORTAL-438 > URL: https://jira.jboss.org/jira/browse/JBPORTAL-438 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Portal Portlet > Affects Versions: 2.0 Final, 2.0 Branch, 2.2 Branch, 2.4 Final > Environment: Windows 2000, JBAS 4.02 > Reporter: Dennis Meers > > If you create a portlet that supports EDIT mode and a logged-in user edits a preference, if the value they put in has more than 255 chars, an error occurs. This is because the table that saves user preference values (jbp_user_pref_value) has a column called 'jbp_value' that is defined as 'VARCHAR(255)'. > I don't know if the portlet spec defines how many characters are allowed in a preference value, but 255 characters seems small for some portlets. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-130) Add deployment unit filtering to AnnotationEnvDeployer

by Ales Justin (JIRA)

Add deployment unit filtering to AnnotationEnvDeployer ------------------------------------------------------ Key: JBDEPLOY-130 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-130 Project: JBoss Deployers Issue Type: Feature Request Components: structure Affects Versions: JBDEPLOY-2.0.0.CR5 Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.0.0.GA As AnnotationEnvironmentDeployer::deploy is costly operation, we should be able to exclude its execution asap. e.g. based on the deployment name --> jbossweb.sar Since we know there is no sense / use in scanning that deployment but it takes a long time to do it due to deployments size. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-857) UDP transport to attempt to validate ability to receive own multicast

by Brian Stansberry (JIRA)

UDP transport to attempt to validate ability to receive own multicast --------------------------------------------------------------------- Key: JGRP-857 URL: https://jira.jboss.org/jira/browse/JGRP-857 Project: JGroups Issue Type: Feature Request Reporter: Brian Stansberry Assignee: Bela Ban Priority: Minor One category of errors JGroups users see is improperly configured multicast on the interface the transport is using. Could the UDP transport help here? Perhaps send a multicast message during the channel connect phase, and block a short period on a future waiting to receive your own message. If the message isn't received, log an ERROR with a nice helpful diagnostic. Probably set a timeout for how long to wait with a default that disables this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6053) Upgrade jboss-jaxbintros to a final release

by Dimitris Andreadis (JIRA)

Upgrade jboss-jaxbintros to a final release ------------------------------------------- Key: JBAS-6053 URL: https://jira.jboss.org/jira/browse/JBAS-6053 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Web Services Reporter: Dimitris Andreadis Assignee: Tom Fennelly Fix For: JBossAS-5.0.0.GA In the AS build we are using: jboss.jaxbintros:jboss-jaxb-intros:jar:1.0.0.beta2:compile I believe, the dependency came in through jbossws. Since AS5 requires all included components to reach a GA state, are you going to provide a final version within the next couple of weeks? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
3
0 / 0

[JBoss JIRA] Commented: (JGRP-155) TP.loopback should always be used

by Bela Ban (JIRA)

[ https://jira.jboss.org/jira/browse/JGRP-155?page=com.atlassian.jira.plugi... ] Bela Ban commented on JGRP-155: ------------------------------- TP.loopback="true" causes ca 20% performance degradation ! Investigate why > TP.loopback should always be used > --------------------------------- > > Key: JGRP-155 > URL: https://jira.jboss.org/jira/browse/JGRP-155 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.8, 2.2.9 > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 2.x > > > Investigate the 3 potential problem areas below: > - Memory leak caused by FC when credits are received too quickly > - Deadlocks caused by same threads calling themselves (e.g. VIEW_OK ack msgs) > - Preemption doesn't work: Scheduler is meaningless here -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMETA-144) JNDI Resolution Decoration on JBossServiceBeanMetaData does not honor "jndi-name"

by Andrew Lee Rubinger (JIRA)

JNDI Resolution Decoration on JBossServiceBeanMetaData does not honor "jndi-name" --------------------------------------------------------------------------------- Key: JBMETA-144 URL: https://jira.jboss.org/jira/browse/JBMETA-144 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR5 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0.CR6 If a JBossServiceBeanMetaData instance is decorated with JBossSessionPolicyDecorator, "mapped-name" is honored, but "jndi-name" is not. Both cases must be accounted for. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1835) Transform work item

by Kris Verlaenen (JIRA)

Transform work item ------------------- Key: JBRULES-1835 URL: https://jira.jboss.org/jira/browse/JBRULES-1835 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-process Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.0.0.M3 Transform work item for transforming data of one type to another using a generic transformation annotation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008