[JBoss JIRA] Created: (JBPORTAL-1392) WSRP does not submit the from when enctype set to "multipart/form-data"
by Andrey Adamovich (JIRA)
WSRP does not submit the from when enctype set to "multipart/form-data"
-----------------------------------------------------------------------
Key: JBPORTAL-1392
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1392
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Portal WSRP
Affects Versions: 2.6.CR2
Environment: All
Reporter: Andrey Adamovich
Assigned To: Chris Laprun
We are developing a portlet on BEA WebLogic Portal that is supposed to be consumed later by JBoss Portal. This portlet is used for file data upload. The thing is that portlet contains a form that has enctype attribute set to multipart/form-data to enable file sending. When the form is submitted on the consumer (JBoss) no form parameters are passed to producer. Looking in the WSRP request sent to BEA Portal by JBoss only action name is seen. If enctype attribute is removed from the form then when form is submitted all parameters are sent to producer except file content.
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBAS-6260) Configure JGroups sockets via ServiceBindingManager
by Brian Stansberry (JIRA)
Configure JGroups sockets via ServiceBindingManager
---------------------------------------------------
Key: JBAS-6260
URL: https://jira.jboss.org/jira/browse/JBAS-6260
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering, Management services
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-5.0.1.CR1
Get all port configuration under the SBM; JGroups is the major outlier.
Create a system property for each address or port config item in jgroups-channelfactory-stacks.xml. Add ServiceBinding entries for each in bindings.xml. Set the system properties via SystemPropertyBinder. Add dependency on SystemPropertyBinder to the channel factory bean.
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBBOOT-131) Log Bootstrap Descriptors at DEBUG
by Andrew Lee Rubinger (JIRA)
Log Bootstrap Descriptors at DEBUG
----------------------------------
Key: JBBOOT-131
URL: https://jira.jboss.org/jira/browse/JBBOOT-131
Project: JBoss Bootstrap
Issue Type: Task
Components: impl-mc
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Fix For: 2.1.0-alpha-5
Should be friendlier at DEBUG:
18:41:03,978 INFO [AbstractMCServerBase] Starting Microcontainer, Bootstrap Descriptors: [[UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/vfs.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/classloader.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/stdio.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/kernel.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/aop.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/jmx.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/deployers.xml, [UrlBootstrapDescriptor]: file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/conf/bootstrap/profile.xml]
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBAS-7790) Undeployment of an .ear through HDScanner leads to a deploy() call on the deleted deployment
by jaikiran pai (JIRA)
Undeployment of an .ear through HDScanner leads to a deploy() call on the deleted deployment
--------------------------------------------------------------------------------------------
Key: JBAS-7790
URL: https://jira.jboss.org/jira/browse/JBAS-7790
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ProfileService
Environment: JBoss AS trunk r102035
Reporter: jaikiran pai
Assignee: Scott M Stark
On the current AS trun (r102035):
- Start the "default" profile of the server with a .ear file in the deploy folder
- Once the server has completely started, delete the .ear from the deploy folder
- HDScanner is triggered and it undeploys the deleted .ear *but also* triggers a deploy on this deleted .ear which results in:
19:54:18,225 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Parse: name=file:///NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas-7760-earone.ear state=PreParse mode=Manual requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy: file:///NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas-7760-earone.ear
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1857)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1575)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1516)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:377)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1066)
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1305)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1229)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1122)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:649)
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:2008)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1101)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
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: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:127)
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:115)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
... 26 more
19:54:18,227 WARN [org.jboss.system.server.profileservice.hotdeploy.HDScanner] Failed to process changes: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
file:///NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas-7760-earone.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
file:///NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas-7760-earone.ear -> org.jboss.deployers.spi.DeploymentException: Error during deploy: file:///NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas-7760-earone.ear
Notice that the NPE is triggered through the deploy() flow. A quick look at the code indicates that this is because the org.jboss.system.server.profileservice.repository.HotDeploymentRepository on a call to getModifiedDeployments() returns that .ear as both REMOVED as well as MODIFIED. It returns it as modified because the call to getModifiedDeployments() internally leads to checkForAdditions() method which uses a *cached* VirtualFile for the "deploy" folder. This cached VirtualFile returns the .ear as one of the deployments, even after the deployment has been removed.
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBAS-7644) Enforce unique names for EE modules within an application
by Brian Stansberry (JIRA)
Enforce unique names for EE modules within an application
---------------------------------------------------------
Key: JBAS-7644
URL: https://jira.jboss.org/jira/browse/JBAS-7644
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.M2
Implement following from EE8.1.1:
All Java EE modules have a name. The name can be explicitly set in the
deployment descriptor for the module. If not set, the name of the module is the
pathname of the module in the ear file with any filename extension (.jar, .war,
.rar) removed, but with any directory names included. The name of a module
must be unique within an application. If and only if the name is not unique (e.g.,
because two names are identical after removing different filename extensions) the
deployment tool may choose new unique names for any of the conflicting
modules; module names that do not conflict must not be changed. The algorithm
for choosing unique names in such a case is product specific.
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBAS-7267) Add missing artifacts to the dependency chain
by Andrew Lee Rubinger (JIRA)
Add missing artifacts to the dependency chain
---------------------------------------------
Key: JBAS-7267
URL: https://jira.jboss.org/jira/browse/JBAS-7267
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1
A dependence upon the following should transitively bring in everything AS needs for the runtime:
<!-- AS modules and 3rdparty deps -->
<dependency>
<groupId>org.jboss.jbossas</groupId>
<artifactId>jboss-as-build</artifactId>
<version>${version.org.jboss.jbossas}</version>
<type>pom</type>
</dependency>
However, some modules are in the distribution which are not part of this chain. The following are a list of offenders manually added into the Embedded POM:
<dependency>
<groupId>org.jboss.jbossas</groupId>
<artifactId>jboss-as-management</artifactId>
<version>${version.org.jboss.jbossas}</version>
<classifier>jsr77</classifier>
</dependency>
<dependency>
<groupId>jboss.web</groupId>
<artifactId>jsp-api</artifactId>
<version>${version.jboss.web}</version>
</dependency>
<dependency>
<groupId>jboss.web</groupId>
<artifactId>el-api</artifactId>
<version>${version.jboss.web}</version>
</dependency>
<dependency>
<groupId>jboss.web</groupId>
<artifactId>jasper-jdt</artifactId>
<version>${version.jboss.web}</version>
</dependency>
<dependency>
<groupId>jboss.messaging</groupId>
<artifactId>jboss-messaging</artifactId>
<version>${version.jboss.messaging}</version>
</dependency>
<dependency>
<groupId>org.jboss.slf4j</groupId>
<artifactId>slf4j-jboss-logging</artifactId>
<version>${version.org.slf4j_slf4j.jboss.logging}</version>
</dependency>
--
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
16 years, 3 months