[JBoss JIRA] Created: (JBESB-193) Need support for notification generatoin from within ActionProcessor.process method
by Tom Fennelly (JIRA)
Need support for notification generatoin from within ActionProcessor.process method
-----------------------------------------------------------------------------------
Key: JBESB-193
URL: http://jira.jboss.com/jira/browse/JBESB-193
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 4.1
Reporter: Tom Fennelly
Assigned To: Mark Little
Fix For: 4.1
In version 4.0, the Action Processing pipeline management code raises notifications in response to an exception from the ActionProcessor.process method. The pipeline managemnt code calls the getOkNotification (no exception) or getErrorNotification (exception) to get the notification message.
For many reasons, this is a very flawed model. Notifications should be raised from within the process method by means of attaching the notifications (error or otherwise) to the message (the mechanism is a design issue). Once the process method returns, the pipline processing management code can check the message for notifications. If there are errors, it can/should (?) abort the message processing, send the error notification (by whatever notification options are configured on the listener) and signal the failure to the calling process (by whatever failure config is configured on the listener).
The getOk and getErro methods can then be removed.
--
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
2 months, 1 week
[JBoss JIRA] Created: (JGRP-1257) ENCRYPT protocol UnrecoverableKeyException: Given final block not properly padded
by Andres Garcia Garcia (JIRA)
ENCRYPT protocol UnrecoverableKeyException: Given final block not properly padded
---------------------------------------------------------------------------------
Key: JGRP-1257
URL: https://jira.jboss.org/browse/JGRP-1257
Project: JGroups
Issue Type: Bug
Affects Versions: 2.11, 2.8, 2.7
Environment: Windows XP SP3, Java 1.6
Reporter: Andres Garcia Garcia
Assignee: Bela Ban
Recently I updated my jgroups version from 2.4.x to 2.11. Suddenly my applications thrown this exception.
org.jgroups.ChannelException: unable to setup the protocol stack: Given final block not properly padded
at org.jgroups.JChannel.init(JChannel.java:1574)
at org.jgroups.JChannel.<init>(JChannel.java:257)
at org.jgroups.JChannel.<init>(JChannel.java:240)
at org.jgroups.demos.Draw.<init>(Draw.java:52)
at org.jgroups.demos.Draw.main(Draw.java:141)
Caused by: java.security.UnrecoverableKeyException: Given final block not properly padded
at com.sun.crypto.provider.SunJCE_z.a(DashoA13*..)
at com.sun.crypto.provider.JceKeyStore.engineGetKey(DashoA13*..)
at java.security.KeyStore.getKey(Unknown Source)
at org.jgroups.protocols.ENCRYPT.initConfiguredKey(ENCRYPT.java:269)
at org.jgroups.protocols.ENCRYPT.init(ENCRYPT.java:231)
at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:641)
at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:468)
at org.jgroups.JChannel.init(JChannel.java:1570)
... 4 more
The ENCRYPT protocol config is
<ENCRYPT sym_init="448"
sym_algorithm="Blowfish"
encrypt_entire_message="true"
key_store_name="cloudencrypt.keystore"
store_password="password"
alias="test"/>
I tested the same code with different versions. 2.6.15 GA is the last working version, and every version I tested from 2.7 GA to 2.11 GA throw the same exception. I made a little use case with it. Maybe I am missing something?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 months, 1 week
[JBoss JIRA] Created: (AS7-782) Hudson/Jenkins won't work in AS7b3
by Fred Bricon (JIRA)
Hudson/Jenkins won't work in AS7b3
----------------------------------
Key: AS7-782
URL: https://issues.jboss.org/browse/AS7-782
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.0.0.Beta3
Environment: Fedora 14, JDK 1.6.0_24, JBoss AS7 beta 3
Reporter: Fred Bricon
Assignee: Jason Greene
After patching AS7b3 with the latest jboss-vfs from github/master and
deploying hudson ( http://search.maven.org/remotecontent?filepath=org/jvnet/hudson/main/huds...) or jenkins on AS7, an exception is thrown when accessing the homepage (or any page) :
{noformat}
17:39:33,429 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/hudson-war-2.0.0].[Stapler]] (http-localhost.localdomain-127.0.0.1-8080-2) "Servlet.service()" pour la servlet Stapler a généré une exception: java.net.MalformedURLException: unknown protocol: jndi
at java.net.URL.<init>(URL.java:574) [:1.6.0_24]
at java.net.URL.<init>(URL.java:464) [:1.6.0_24]
at java.net.URL.<init>(URL.java:413) [:1.6.0_24]
at org.kohsuke.stapler.Stapler.selectResourceByLocale(Stapler.java:227) [stapler-1.155.jar:]
at org.kohsuke.stapler.Stapler.openResourcePathByLocale(Stapler.java:203) [stapler-1.155.jar:]
at org.kohsuke.stapler.Stapler.service(Stapler.java:145) [stapler-1.155.jar:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94) [hudson-core-2.0.0.jar:]
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86) [hudson-core-2.0.0.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) [hudson-core-2.0.0.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) [hudson-core-2.0.0.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) [hudson-core-2.0.0.jar:]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:388) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:658) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta11.jar:7.0.0.Beta3]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
{noformat}
I first mentioned this issur on irc (see http://echelog.matzon.dk/logs/browse/jboss-as7/1305151200 [13:42:43] -> [13:48:58])
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2 months, 1 week
[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender
by Bela Ban (JIRA)
Optimization: make threads return immediately if NAKACK has another active thread for the same sender
-----------------------------------------------------------------------------------------------------
Key: JGRP-457
URL: http://jira.jboss.com/jira/browse/JGRP-457
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.5
In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up.
If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock.
The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool.
--
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
5 months, 2 weeks
[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener
by Sudip Bhowmik (JIRA)
[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ]
Sudip Bhowmik edited comment on AS7-6819 at 3/31/13 1:58 PM:
-------------------------------------------------------------
>From the log it shows mostly that all component.MessageDrivenBean.* realted symbols are not found during MDB load time. It says "one or more transitive dependencies" issue.
.component.MessageDrivenBean.CREATE
.component.MessageDrivenBean.ejb3.timerService
.component.MessageDrivenBean.VIEW
and so on ...
Please help.
was (Author: sudipsand):
From the log it show shows mostly all .component.MessageDrivenBean.* realted symbols are not found during MDB load time. It says "one or more transitive dependencies" issue.
.component.MessageDrivenBean.CREATE
.component.MessageDrivenBean.ejb3.timerService
.component.MessageDrivenBean.VIEW
and so on ...
Please help.
> MBD @ResourceAdapter deployment issue with JCA inbound listener
> ---------------------------------------------------------------
>
> Key: AS7-6819
> URL: https://issues.jboss.org/browse/AS7-6819
> Project: Application Server 7
> Issue Type: Clarification
> Components: EJB, JCA
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows with Jboss 7.1.3 EAP version.
> Reporter: Sudip Bhowmik
> Labels: jboss
> Fix For: 7.1.3.Final (EAP)
>
> Attachments: SourceCode_MDB_JCA.rar, standalone-full.xml
>
>
> The source set is attached here with.
> =================================================
> 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
> ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
> terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (AS7-6819) MBD @ResourceAdapter deployment issue with JCA inbound listener
by Sudip Bhowmik (JIRA)
[ https://issues.jboss.org/browse/AS7-6819?page=com.atlassian.jira.plugin.s... ]
Sudip Bhowmik commented on AS7-6819:
------------------------------------
>From the log it show shows mostly all .component.MessageDrivenBean.* realted symbols are not found during MDB load time. It says "one or more transitive dependencies" issue.
.component.MessageDrivenBean.CREATE
.component.MessageDrivenBean.ejb3.timerService
.component.MessageDrivenBean.VIEW
and so on ...
Please help.
> MBD @ResourceAdapter deployment issue with JCA inbound listener
> ---------------------------------------------------------------
>
> Key: AS7-6819
> URL: https://issues.jboss.org/browse/AS7-6819
> Project: Application Server 7
> Issue Type: Clarification
> Components: EJB, JCA
> Affects Versions: 7.1.3.Final (EAP)
> Environment: Windows with Jboss 7.1.3 EAP version.
> Reporter: Sudip Bhowmik
> Labels: jboss
> Fix For: 7.1.3.Final (EAP)
>
> Attachments: SourceCode_MDB_JCA.rar, standalone-full.xml
>
>
> The source set is attached here with.
> =================================================
> 13:04:10,050 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "DiameterEAR-1.0.ear" was rolled back with failure message {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.CREATE Missing[jboss.ra.\"DiameterRAInDeploy-1.0\"]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.VIEW.\"com.infyon.DiameterRAIn.DiameterMessageListener\".MESSAGE_ENDPOINT Missing[JBAS014861: <one or more t
> ransitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.ejb3.timerService Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".moduleDeploymentRuntimeInformation Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"DiameterMDB-1.0.jar\".component.MessageDrivenBean.START Missing[JBAS014861: <one or more transitive dependencies>]","jboss.deployment.subunit.\"DiameterEAR-1.0.ear\".\"Diame
> terMDB-1.0.jar\".component.MessageDrivenBean.TimedObjectInvoker Missing[JBAS014861: <one or more transitive dependencies>]"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (AS7-6820) Wrong exception thrown by container for non-existent entity
by Kirill Paliy (JIRA)
Kirill Paliy created AS7-6820:
---------------------------------
Summary: Wrong exception thrown by container for non-existent entity
Key: AS7-6820
URL: https://issues.jboss.org/browse/AS7-6820
Project: Application Server 7
Issue Type: Bug
Reporter: Kirill Paliy
According to spec, if client is trying to make a call to already removed entity, NoSuchObjectException must be thrown:
14.3.9 Non-existing Stateful Session or Entity Object
If a client makes a call to a stateful session or entity object that has been removed, the container should throw the javax.ejb.NoSuchEJBException[80]. If the EJB 2.1 client view is used, the container should throw the java.rmi.NoSuchObjectException (which is a subclass of java.rmi.RemoteException) to a remote client, or the javax.ejb.NoSuchObjectLocalException to a local client.
In realtiy, I'm getting TransactionRolledBackException:
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (DROOLS-92) NPE when removing a rule using a Java object with Drools annotations
by Davide Sottara (JIRA)
Davide Sottara created DROOLS-92:
------------------------------------
Summary: NPE when removing a rule using a Java object with Drools annotations
Key: DROOLS-92
URL: https://issues.jboss.org/browse/DROOLS-92
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.5
Reporter: Davide Sottara
Assignee: Mark Proctor
Priority: Critical
Fix For: 5.6, 6.0.0.Alpha1
- Drools 5.5.x still has Accessors : field readers and writers. They are created consistently (reader+writer) for declared types, but in case of non-declared types (java objects), only readers are created, and only when
a field is involved in a constraint.
- when a rule is added (dynamically) during an incremental construction process, the packagebuilder creates "redeclarations" (TypeDeclarations with
NATURE == DECLARATION) of involved classes, in order to process annotations
such as @Position or @Modifies.
- if a rule triggers the removal/update of a rule in its own KB, AbstractRuleBase.executeQueuedActions() is called, which tries to rewire the accessors
Problem: if the modified rule's package contains a TypeDeclaration for
an annotated java object, only the reader will exist and the rewiring
process will throw a NPE as it tries to rewire the writer.
Possible solutions?
a) make the rewiring process check that an accessor exists before trying to rewire it
OR
b) change AbstractRuleBase.executeQueuedActions() - the code seems to have
been removed in 6.x (master)
OR
c) limit the rewiring to TypeDeclarations with Nature == DEFINITION
OR
d) always create the writer together with the reader
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years