[JBoss JIRA] (JBJCA-1363) IOException: Could not delete C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\tmp\scortcicsecirar-3.1.0.rar\bouncycastle-1.04.jar
by Francis ANDRE (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1363?page=com.atlassian.jira.plugin... ]
Francis ANDRE commented on JBJCA-1363:
--------------------------------------
This issue appears also in ironjacamar-1.0.17 in which I more interested since I am wokring with JBoss-EAP-6.1.
> IOException: Could not delete C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\tmp\scortcicsecirar-3.1.0.rar\bouncycastle-1.04.jar
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBJCA-1363
> URL: https://issues.jboss.org/browse/JBJCA-1363
> Project: IronJacamar
> Issue Type: Bug
> Components: Deployer
> Affects Versions: 1.2.7.Final
> Environment: C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\bin>"%java_home%\bin\java" -version
> java version "1.7.0_80"
> Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
> Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
> Windows 10
> Reporter: Francis ANDRE
> Priority: Critical
>
> Hi
> Got this exception when deploying a EIS rar
> C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\bin>run
> ===============================================================================
> IronJacamar
> IRON_JACAMAR_HOME: C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final
> JAVA: C:\Program Files\Java\jdk1.7.0_80\bin\java
> JAVA_OPTS: -Xmx512m
> ===============================================================================
> 10:16:49,330 INFO [Fungal] Fungal 0.11.0.Final started
> 10:16:49,908 INFO [Version] HV000001: Hibernate Validator 5.0.1.Final
> 10:16:50,065 INFO [WebServer] Jetty 8.1.3.v20120416 started
> 10:16:50,143 INFO [RADeployer] IJ020001: Required license terms for file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/jdbc-xa.rar
> 10:16:50,221 INFO [RADeployer] IJ020001: Required license terms for file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/jdbc-local.rar
> 10:16:50,268 INFO [RADeployer] IJ020001: Required license terms for file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/scortcicsecirar-3.1.0.rar
> 10:16:50,362 INFO [WARDeployer] Deployed: file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/root.war
> 10:16:50,362 INFO [WARDeployer] Deployed: file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/console.war
> 10:16:50,362 SEVERE [Fungal] Deployment file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/deploy/scortcicsecirar-3.1.0.rar failed: com.github.fungal.spi.deployers.DeployException: Deployment file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/deploy/scortcicsecirar-3.1.0.rar failed
> at org.jboss.jca.deployers.fungal.RADeployer.deploy(RADeployer.java:209)
> at com.github.fungal.impl.MainDeployerImpl.deploy(MainDeployerImpl.java:144)
> at com.github.fungal.impl.KernelImpl$UnitDeployer.run(KernelImpl.java:1947)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.io.IOException: Could not delete C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\tmp\scortcicsecirar-3.1.0.rar\bouncycastle-1.04.jar
> at com.github.fungal.api.util.FileUtil.delete(FileUtil.java:378)
> at com.github.fungal.api.util.FileUtil.extract(FileUtil.java:179)
> at org.jboss.jca.deployers.fungal.RADeployer.deploy(RADeployer.java:131)
> ... 5 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (JBJCA-1363) IOException: Could not delete C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\tmp\scortcicsecirar-3.1.0.rar\bouncycastle-1.04.jar
by Francis ANDRE (JIRA)
Francis ANDRE created JBJCA-1363:
------------------------------------
Summary: IOException: Could not delete C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\tmp\scortcicsecirar-3.1.0.rar\bouncycastle-1.04.jar
Key: JBJCA-1363
URL: https://issues.jboss.org/browse/JBJCA-1363
Project: IronJacamar
Issue Type: Bug
Components: Deployer
Affects Versions: 1.2.7.Final
Environment: C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\bin>"%java_home%\bin\java" -version
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
Windows 10
Reporter: Francis ANDRE
Hi
Got this exception when deploying a EIS rar
C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\bin>run
===============================================================================
IronJacamar
IRON_JACAMAR_HOME: C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final
JAVA: C:\Program Files\Java\jdk1.7.0_80\bin\java
JAVA_OPTS: -Xmx512m
===============================================================================
10:16:49,330 INFO [Fungal] Fungal 0.11.0.Final started
10:16:49,908 INFO [Version] HV000001: Hibernate Validator 5.0.1.Final
10:16:50,065 INFO [WebServer] Jetty 8.1.3.v20120416 started
10:16:50,143 INFO [RADeployer] IJ020001: Required license terms for file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/jdbc-xa.rar
10:16:50,221 INFO [RADeployer] IJ020001: Required license terms for file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/jdbc-local.rar
10:16:50,268 INFO [RADeployer] IJ020001: Required license terms for file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/scortcicsecirar-3.1.0.rar
10:16:50,362 INFO [WARDeployer] Deployed: file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/root.war
10:16:50,362 INFO [WARDeployer] Deployed: file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/system/console.war
10:16:50,362 SEVERE [Fungal] Deployment file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/deploy/scortcicsecirar-3.1.0.rar failed: com.github.fungal.spi.deployers.DeployException: Deployment file:/C:/ProgramFiles/JBoss/ironjacamar-1.2.7.Final/deploy/scortcicsecirar-3.1.0.rar failed
at org.jboss.jca.deployers.fungal.RADeployer.deploy(RADeployer.java:209)
at com.github.fungal.impl.MainDeployerImpl.deploy(MainDeployerImpl.java:144)
at com.github.fungal.impl.KernelImpl$UnitDeployer.run(KernelImpl.java:1947)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Could not delete C:\ProgramFiles\JBoss\ironjacamar-1.2.7.Final\tmp\scortcicsecirar-3.1.0.rar\bouncycastle-1.04.jar
at com.github.fungal.api.util.FileUtil.delete(FileUtil.java:378)
at com.github.fungal.api.util.FileUtil.extract(FileUtil.java:179)
at org.jboss.jca.deployers.fungal.RADeployer.deploy(RADeployer.java:131)
... 5 more
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFLY-9640) Configuring deployment runtime name with XML
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9640?page=com.atlassian.jira.plugin.... ]
Brian Stansberry resolved WFLY-9640.
------------------------------------
Assignee: Brian Stansberry (was: Stuart Douglas)
Resolution: Won't Do
The runtime name needs to be known before any code that could extract it from a deployment descriptor etc could run.
The runtime name can be set in standalone.xml (or domain.xml in a managed domain.)
> Configuring deployment runtime name with XML
> --------------------------------------------
>
> Key: WFLY-9640
> URL: https://issues.jboss.org/browse/WFLY-9640
> Project: WildFly
> Issue Type: Feature Request
> Components: Application Client, Server
> Affects Versions: 10.1.0.Final, 11.0.0.Final
> Reporter: dbdbdb dbdbdb
> Assignee: Brian Stansberry
>
> In my opinion, Wildfly should have an option to define the name and runtime name of a web application (.war) in a XML file.
> Like jboss-web.xml and ejb-jar.xml, it would be great if we could set the runtime name in a XML whatever the .war filename is. It would be very useful, not only to prevent human error when deploying via web console (filling the upload form with wrong runtime name), but also when the applications are deployed by copying the .war file into deployments directory.
> The correct runtime name is important because Wildfly uses this name for object serialization (Infinispan, JMS, etc). And if the runtime name changes, Wildfly can't deserialize objects when it was previously serialized.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFLY-9641) Cluster EJB can not work with "-b 0.0.0.0"
by Fred Ling (JIRA)
Fred Ling created WFLY-9641:
-------------------------------
Summary: Cluster EJB can not work with "-b 0.0.0.0"
Key: WFLY-9641
URL: https://issues.jboss.org/browse/WFLY-9641
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 11.0.0.Final
Reporter: Fred Ling
The ejb cluster does not work when bind to 0.0.0.0, using --server-config=standalone-full-ha.xml -b 0.0.0.0.
The ejb client fails to connect to the cluster nodes because it tries to connect to 0.0.0.0.
For more information please refer to the forum thread.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFLY-9640) Configuring deployment runtime name with XML
by dbdbdb dbdbdb (JIRA)
[ https://issues.jboss.org/browse/WFLY-9640?page=com.atlassian.jira.plugin.... ]
dbdbdb dbdbdb updated WFLY-9640:
--------------------------------
Description:
In my opinion, Wildfly should have an option to define the name and runtime name of a web application (.war) in a XML file.
Like jboss-web.xml and ejb-jar.xml, it would be great if we could set the runtime name in a XML whatever the .war filename is. It would be very useful, not only to prevent human error when deploying via web console (filling the upload form with wrong runtime name), but also when the applications are deployed by copying the .war file into deployments directory.
The correct runtime name is important because Wildfly uses this name for object serialization (Infinispan, JMS, etc). And if the runtime name changes, Wildfly can't deserialize objects when it was previously serialized.
was:
In my opinion, Wildfly should have an option to define the name and runtime name of a web application (.war) in a XML file.
Like jboss-web.xml and ejb-jar.xml, it would be great if we could set the runtime name in a XML whatever the .war filename is. It would be
very useful, not only to prevent human error when deploying via web console (filling the upload form with wrong runtime name), but also when the applications are deployed by copying the .war file into deployments directory.
The correct runtime name is important because Wildfly uses this name for object serialization (Infinispan, JMS, etc). And if the runtime name changes, Wildfly can't deserialize objects when it was previously serialized.
> Configuring deployment runtime name with XML
> --------------------------------------------
>
> Key: WFLY-9640
> URL: https://issues.jboss.org/browse/WFLY-9640
> Project: WildFly
> Issue Type: Feature Request
> Components: Application Client, Server
> Affects Versions: 10.1.0.Final, 11.0.0.Final
> Reporter: dbdbdb dbdbdb
> Assignee: Stuart Douglas
>
> In my opinion, Wildfly should have an option to define the name and runtime name of a web application (.war) in a XML file.
> Like jboss-web.xml and ejb-jar.xml, it would be great if we could set the runtime name in a XML whatever the .war filename is. It would be very useful, not only to prevent human error when deploying via web console (filling the upload form with wrong runtime name), but also when the applications are deployed by copying the .war file into deployments directory.
> The correct runtime name is important because Wildfly uses this name for object serialization (Infinispan, JMS, etc). And if the runtime name changes, Wildfly can't deserialize objects when it was previously serialized.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFLY-9640) Configuring deployment runtime name with XML
by dbdbdb dbdbdb (JIRA)
[ https://issues.jboss.org/browse/WFLY-9640?page=com.atlassian.jira.plugin.... ]
dbdbdb dbdbdb updated WFLY-9640:
--------------------------------
Description:
In my opinion, Wildfly should have an option to define the name and runtime name of a web application (.war) in a XML file.
Like jboss-web.xml and ejb-jar.xml, it would be great if we could set the runtime name in a XML whatever the .war filename is. It would be
very useful, not only to prevent human error when deploying via web console (filling the upload form with wrong runtime name), but also when the applications are deployed by copying the .war file into deployments directory.
The correct runtime name is important because Wildfly uses this name for object serialization (Infinispan, JMS, etc). And if the runtime name changes, Wildfly can't deserialize objects when it was previously serialized.
was:
Wildfly should have a option to define the name and runtime name of a web application (.war) in a XML file.
Like jboss-web.xml and ejb-jar.xml, it would be great if we can set the runtime name in a XML whatever the .war filename is.
Very useful not only to prevent human error when deploying via web console (fill the upload form with wrong runtime name), but also useful when the applications is deployed by copying the .war file into deployments directory.
The correct runtime name is important because Wildfly use this name for object serialization (Infinispan, JMS, etc). And if the runtime name changes, Wildfly can't deserialize objects when it was serialized before.
> Configuring deployment runtime name with XML
> --------------------------------------------
>
> Key: WFLY-9640
> URL: https://issues.jboss.org/browse/WFLY-9640
> Project: WildFly
> Issue Type: Feature Request
> Components: Application Client, Server
> Affects Versions: 10.1.0.Final, 11.0.0.Final
> Reporter: dbdbdb dbdbdb
> Assignee: Stuart Douglas
>
> In my opinion, Wildfly should have an option to define the name and runtime name of a web application (.war) in a XML file.
> Like jboss-web.xml and ejb-jar.xml, it would be great if we could set the runtime name in a XML whatever the .war filename is. It would be
> very useful, not only to prevent human error when deploying via web console (filling the upload form with wrong runtime name), but also when the applications are deployed by copying the .war file into deployments directory.
> The correct runtime name is important because Wildfly uses this name for object serialization (Infinispan, JMS, etc). And if the runtime name changes, Wildfly can't deserialize objects when it was previously serialized.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFLY-9640) Configuring deployment runtime name with XML
by dbdbdb dbdbdb (JIRA)
dbdbdb dbdbdb created WFLY-9640:
-----------------------------------
Summary: Configuring deployment runtime name with XML
Key: WFLY-9640
URL: https://issues.jboss.org/browse/WFLY-9640
Project: WildFly
Issue Type: Feature Request
Components: Application Client, Server
Affects Versions: 11.0.0.Final, 10.1.0.Final
Reporter: dbdbdb dbdbdb
Assignee: Stuart Douglas
Wildfly should have a option to define the name and runtime name of a web application (.war) in a XML file.
Like jboss-web.xml and ejb-jar.xml, it would be great if we can set the runtime name in a XML whatever the .war filename is.
Very useful not only to prevent human error when deploying via web console (fill the upload form with wrong runtime name), but also useful when the applications is deployed by copying the .war file into deployments directory.
The correct runtime name is important because Wildfly use this name for object serialization (Infinispan, JMS, etc). And if the runtime name changes, Wildfly can't deserialize objects when it was serialized before.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months
[JBoss JIRA] (WFLY-9639) Messages are stuck in a Queue that is configured on HornetQ
by Rajendra Mallampati (JIRA)
Rajendra Mallampati created WFLY-9639:
-----------------------------------------
Summary: Messages are stuck in a Queue that is configured on HornetQ
Key: WFLY-9639
URL: https://issues.jboss.org/browse/WFLY-9639
Project: WildFly
Issue Type: Bug
Components: Application Client
Affects Versions: 9.x.x TBD
Environment: RHEL 7.2, JDK 1.8_144
Reporter: Rajendra Mallampati
Assignee: Stuart Douglas
We use WildFly 9.0.2 for hosting our web application and it has both real time and batch processing components. One of the functions supported on the web includes uploading a file with a number of lines any where from 1 to 10K, If the file is valid (virus scan etc passed) it is parsed into that may messages and published to a queue. Each message will have two counters total number of messages that are published to the queue, and the message number.
The consuming side is implemented using Spring DefaultMessageListenerContainer (DMLC) with a concurrency of 50 and maxConcurrency of 75. The listeners that implement MessageListener interface are integrated into DMLC. sometimes, if the producing side published 100 messages the consuming side only receiving 98 (per say) and gets stuck because two more messages should be in the Queue. Those two messages are not delivered and don't know where they are going. We tried even persistent Queues and the result is same (getting stuck).
This is happening in production and any insight into this issue is highly appreciated.
Here are the software details:
App server : Wildfly 9.0.2
HornetQ : 2.4.7
JDK : 1_8_144
If you need additional details I will be very glad to provide.
Thanks
Rajendra
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 4 months